Support for Chassis Devices

casp1042
F65629-FEX support 10.4.2
When a device model uses a
DX NetOps Spectrum
certified proprietary chassis MIB or the Entity MIB,
DX NetOps Spectrum
identifies that device model as a chassis device.
DX NetOps Spectrum
models and arranges all the identified chassis devices with their components or modules under the
Chassis Manager
node in the navigation pane of OneClick. This arrangement is based on the vendor names of your chassis devices.
From 10.4.2, you can discover the Cisco FEX module. The FEX module is displayed under the Chasis Manager view.
For active-active FEX configuration, both monitoring device displays all the FEX modules, since both entity mib contains all the FEX modules.
For example, devices of "Cisco" that are identified as chassis devices are arranged in a folder with the name "Cisco". Similarly, devices of "Juniper" identified as chassis devices are arranged in the "Juniper" folder.
The following image shows how chassis devices are modeled and arranged under the
Chassis Manager
node. Each vendor folder contains its chassis devices:
chassis_module
As a result, you can monitor the health of your chassis devices and their modules at one place in OneClick, the
Chassis Manager
node. This node provides a consolidated location to view and manage chassis devices that are modeled in the Universe topology. After selecting a chassis device from this node and then accessing chassis views from the Component Detail pane, you can view the status of all interfaces, and can assess the health of each module. For more information about the chassis views that give detailed information about each module of your chassis device, see Chassis Views.
Identification of Chassis Devices
DX NetOps Spectrum
identifies your device as a chassis device based on the following two types of MIBs:
  • Proprietary MIB
    When a device supports a
    DX NetOps Spectrum
    certified proprietary chassis MIB, it is identified as a chassis device. For example, when a "Juniper" device supports the "jnxBoxAnatomy", it is identified as a chassis device based on that MIB.
    DX NetOps Spectrum
    always prefers the
    DX NetOps Spectrum
    certified proprietary chassis MIB to the Entity MIB of a device model for its identification as a chassis device. Only when the proprietary chassis MIB is absent, the device model is identified as a chassis device using the Entity MIB.
     An attribute(createChassisModules) is added (available on device) to enable or disable modeling of Slots/Chassis Modules for Juniper devices. By default, this attribute is set to True and all the chassis modules are discovered and modeled for Juniper devices. To disable modeling of chassis modules, set this attribute value to False and perform reconfiguration on the device.
  • Entity MIB
    When a device model supports the Entity MIB and the value of the "
    EnableEntityModuleModeling
    " attribute is "Yes" for that device model, it is identified as a chassis device. By default, the value of this attribute is "Yes" on a case-by-case basis for the following reasons:
    • Some vendors do not implement this MIB indexing scheme correctly.
    • Some vendors support the Entity MIB even for non-chassis devices.
    If you do not want
    DX NetOps Spectrum
    to identify a device model as a chassis device, set the value of this attribute to "No" and reconfigure the model.
Chassis Views
To view the details of your chassis devices,
DX NetOps Spectrum
displays the following three types of chassis views in OneClick:
  • The Basic Module-Level View
    This view of your chassis device can be viewed at the Chassis Manager node. This view gives you visibility into your chassis device by displaying all the modules of it. The following image shows the various modules displayed under a Cisco chassis device:
    cisco_chassis_view_NP.png
    The following image shows the various modules displayed under a Juniper chassis device:
    jun_chassis_view_no_mic.png
    If you select a particular module under any chassis device, you can see the hardware description of that module. The hardware description lets you know whether the module is Fan, Linecard, Power Supply, Routing Engine, PIC, MIC, and so on. The following images show how the hardware description of a Cisco and Juniper module is displayed in the
    Component Detail> Information:
    cisco_module_description.png
    Juniper_module_descriptions.png
  • The Interfaces View
    This view is an elaborated view of all interfaces present in each module of your chassis device. For a selected chassis device, this view shows all of its interface modules, interfaces within each module, the status of modules and its interfaces, and other information under the Interfaces tab of the Component Detail pane. From 10.4.2, all the FEX down ports are listed under the FEX modules. The following image shows how a "Cisco" chassis device is populated under the Interfaces tab:
    cisco_interface_view.png
    The following image shows how a "Juniper" chassis device is populated under the interfaces tab:
    juniper_rtr_comp_detail_interface.JPG
  • The Entity View
    DX NetOps Spectrum
    populates this view only for those chassis devices which support the Entity MIB. The
    Entity View
    is populated when you expand the "
    Entity View
    " under the
    Information
    tab of the
    Component Detail
    pane. This view has the following two sections:
    • Physical Entities
      This section populates the information about each module that exists in your chassis device.
    • Logical Entities
      This section populates the information about the logical entities that exist in each module of your chassis device.
    The following image shows how the
    Entity View
    is populated for a selected "Cisco" chassis device view under the Chassis Manager node:
    SPEC--Cisco_Chassis_View
The Locater Search
DX NetOps Spectrum
allows you to find all your modeled chassis devices and their modules in the
Chassis
node of the Locater tab in the Navigation pane. To find all your modeled chassis devices and their modules, use the following five search criteria available under the
Chassis
node:
  • All Chassis
    This search criteria finds all your chassis devices that are modeled and arranged under the
    Chassis Manager
    node of your landscape. The result of this search lists all of your modeled chassis devices.
  • All Chassis Managed Devices
    This search criteria finds each SNMP capable device model existing on all your modeled chassis devices. The result of this search lists each SNMP capable device model with name of its chassis device.
  • All Modules
    This search criteria finds all your existing modules that are modeled and arranged under each modeled chassis device. The result of this search lists all modeled modules existing in each modeled chassis device.
  • All FEX Modules
    This search criteria finds all your existing modules that are modeled and arranged under each modeled chassis device. The result of this search lists all modeled modules existing in each modeled chassis device.
  • Managed Devices By Chassis Name
    This search criteria finds each SNMP capable device model by the name of its chassis device. The result of this search lists all SNMP capable devices that are mounted on the chassis device you specify.
  • Modules by Chassis Name
    This search criteria finds each modeled module by the name of its chassis device. The result of this search lists all the modeled modules of the chassis device you specify.
  • Stack
    From Spectrum 10.3.2 onwards, the 'All switches' option (as shown in the screenshot) fetches details such as the ModelName, Serial Number, ModelNumber, IPAddress of all the switches in a selected landscapes, including the details of the members of the stack devices.
    switches Locator search.JPG
Chassis Alarms
When
DX NetOps Spectrum
identifies a device model as a chassis device, the
Chassis Fault Domain
is associated with that chassis device. This condition correlation domain correlates various alarms on a chassis device and its modules to raise different root cause alarms. For more information about condition correlation domains, see section. The existing alarm modules take care of the FEX down scenarios.
The following alarms are the Chassis Fault Domain alarms:
  • Chassis Down (0x00010f69)
    This alarm is raised when the contact with a chassis device is lost. This alarm is the root cause alarm that suppresses the following alarms that are raised on a chassis device:
    • ContactLost_Red (0x00010d35)
    • Blade Status Unkown (0x00010f71)
    • InferConnectorContactLost_red (0x00010d90)
    • Linkdown (0x00010d11)
  • Blade Status Unkown (0x00010f71)
    This alarm is raised when
    DX NetOps Spectrum
    is not able to contact the chassis on-board agent. This alarm is the root cause alarm that suppresses the following alarms that are raised on a module of a chassis device:
    • Catalyst Dev Module Failed (0x011c0488)
    • Dev Module Failed (0x00010f70)
    • Dev Module Offline (0x00010f86)
    • Dev Module Pulled (0x00010f6b)
    • Module Offline (0x00010f87)
    • Module Pulled (0x00010f6d)
  • Module Offline (0x00010f87)
    This alarm is raised when the state of a Module is reported as "Offline". This alarm is the root cause alarm that suppresses the following alarms that are raised on a module of a chassis device:
    • ContactLost_Grey (0x00010d36)
    • ContactLost_red (0x000103d5)
    • Physical Host Down (0x056e000c)
  • Module Pulled (0x00010f6d)
    This alarm is raised when a Module is pulled out from the chassis. This alarm is the root cause alarm that suppresses the following alarms that are raised on a module of a chassis device:
    • ContactLost_Grey (0x00010d36)
    • ContactLost_red (0x000103d5)
    • Physical Host Down (0x056e000c)