What can I see in the NE Inventory view?

NE child objects

The NE Inventory view shows a tree structure of individual inventory objects (child objects). Object names and basic administrative and operational state information are displayed. The color of an inventory object indicates its state.

Note: The inventory details available in NSP depend on the adaptors installed and managed NE configuration.

NE inventory information is grouped by type of object:

• Equipment inventory: objects configured on the NE, such as shelves, cards, and ports, are grouped in the inventory view as an Equipment Group.

  If an Extended Services Appliance (ESA) is configured on a model-driven NE, an ESA group appears in the Equipment Group, showing all configured ESA VMs and ports.

• Logical inventory: if applicable, supported logical entities such as LAGs and routing instances are also displayed, grouped as a Logical Group. The Logical Group appears below the Equipment Group in the inventory tree.

Available equipment objects

The following object types are supported in the Equipment Group. The hierarchy depends on the NE type.

Shelf Card Port Module Fan Power Supply

Radio Radio Folder Extended Services Appliance VM (virtual machine) Virtual Port

Available logical objects

The following object types are supported in the Logical Group:

• Link Aggregation Groups

  • MC LAGs

• Routing Instances

  • Routers

    - - Interfaces

    - - - IPv4 Addresses

    - - - IPv6 Addresses

    - - BGP Instances

    - - - BGP Peer Groups

    - - - - BGP Peers

    - - OSPFv2 Instances

    - - - OSPFv2 Areas

    - - - - OSPFv2 Interfaces

    - - - - - OSPFv2 Neighbors

    - - - - OSPFv2 Sham Links

    - - - - OSPFv2 Virtual Links

    - - OSPFv3 Instances

    - - - OSPFv3 Areas

    - - - - OSPFv3 Interfaces

    - - - - - OSPFv3 Neighbors

    - - - - OSPFv3 Virtual Links

    - - ISIS Instances

    - - - ISIS Levels

    - - - ISIS Interfaces

    - - PIM Instances

    - - - PIM Rendezvous Points

    - - - PIM Interfaces

    - - MPLS

    - - - MPLS Instances

    - - - MPLS Interfaces

    - - RSVP

    - - - RSVP Interfaces

    - - - RSVP Neighbors

    - - LDP

    - - - LDP Instances

    - - - LDP Interfaces

    - - - LDP Neighbors

  • L3 Routing Instances

    - - BGP Peer Groups

    - - - BGP Peers

    - - OSPFv2 Instances

    - - - OSPFv2 Areas

    - - - - OSPFv2 Interfaces

    - - - - - OSPFv2 Neighbors

    - - - - OSPFv2 Sham Links

    - - - - OSPFv2 Virtual Links

    - - OSPFv3 Instances

    - - - OSPFv3 Areas

    - - - - OSPFv3 Interfaces

    - - - - - OSPFv3 Neighbors

    - - - - OSPFv3 Virtual links

    - - ISIS Instances

    - - - ISIS Levels

    - - - ISIS Interfaces

    - - PIM Instances

    - - - PIM Rendezvous Points

    - - - PIM Interfaces

• ACL Sets

  • ACL v4 Sets

    - - ACL v4 Entries

  • ACL v6 Sets

    - - ACL v6 Entries

  • ACL L2 Sets

    - - ACL L2 Entries

• BFD

  • BFD Templates

  • BFD Reflectors

Filtering object lists

At the top of the NE Inventory view, choose Equipment type filters or Logical type filters, click (Add filter) to choose filter criteria, and click APPLY FILTERS. When a filter is applied, objects that don’t match the filter are dimmed.

Note: If you filter on Ports, virtual ports are included in the results if present.

You can apply type filters, state filters, or a combination, for example, cards with operational state enabled.

Equipment type filters

The following equipment type filters are supported:

• Shelf

• Slot

• Card

• Port

• Module

• Fan

• Power Supply

• Rack

• Radio

Choose an equipment type from the drop-down list. The default filtering logic is All, for example, all shelves. Click on a type to refine the filter, for example, to add a number.

Logical type filters

The following logical type filters are supported. Choose a type filter and click (Add filter) again to add a sub-type filter, for example, to filter by interface, choose Router, add another filter, and choose Interface. Click on a type or sub-type to refine the filter, for example, to add a number.

• Router

  • Interface

  • IPv4 Address

  • IPv6 Address

  • BGP Instance

  • OSPFv2 Interface

  • OSPFv2 Neighbor

  • OSPFv3 Interface

  • OSPFv3 Neighbor

  • MPLS Interface

  • LDP Interface

• L3 Routing Instance

  • L3 Routing Instance

  • BGP Instance

  • OSPFv2 Interface

  • OSPFv2 Neighbor

  • OSPFv3 Interface

  • OSPFv3 Neighbor

• LAG

• LAG Port

• MC LAG Peer

• MC Lag

State filters

You can add filters for Operational State, Administrative State, and, for ports, Configuration Deployment Status. Add a type filter, then choose a state from the drop-down list. Available criteria depends on the filter types.

Expanding object lists

In the equipment inventory tree, you can select an inventory object and click to open the tree item actions menu.

From the Equipment Group object, you can expand or export all objects in the equipment group:

• Expand all: shows all objects in the equipment inventory tree.

• Export all: download a file to your local computer, containing the equipment inventory of the NE. The export file is in .xlsx format, with a sheet for each object type configured on the NE.

  For example, if there are ports configured, the export file includes a sheet called ports, populated with the ports and their properties.

• Export filtered: this action is available if a filter is applied in the NE Inventory view. The export filtered option allows you to download an inventory file of the filtered data.

From any other equipment object, Expand all shows all child objects of the selected object.

Accessing related views

Select an inventory object and click to open the tree item actions menu. Options in the tree item actions menu depend on the object. The following table lists the commands available for various objects, and the NSP view that opens for each command.

Table 7-1: Cross-launch options from NE Inventory objects

Cross-launch command	Opens NSP view	Available for objects
Open in Current Alarms	Current Alarms List	NE, Port
Open object	Model Driven Configurator, filtered to the object.	Any equipment object on a model-driven NE
Open NE Session	CLI	NE
Plot Utilization Statistics	Data Collection and Analysis Visualizations	Port
Show in Event Timeline	Object Troubleshooting event timeline, filtered to the NE	NE

If an option in the object tree item actions menu is dimmed, the action is not available.

If this occurs, check the following:

• adaptors:

  • MDC adaptors must be present for the NE for Model Driven Configurator to be opened

  • an alarm adaptor must be present for NSP to display alarms

  • telemetry mappings must be present to plot statistics

• Mediation: for NE session, a CLI mediation policy must be configured in the discovery rule used to manage the NE.

If the problem persists, contact Nokia support.