Retrieving Chassis Inventory and Interfaces
SRX Series chassis cluster inventory and interface information is gathered to monitor the hardware components and the interfaces on the cluster. The primary node contains information about the secondary node components and interfaces.
Using the Junos OS XML Management Protocol or NETCONF XML Management Protocol
Use the
get-chassis-inventory
remote procedure call (RPC) to get the chassis inventory. This RPC reports components on both the primary and secondary nodes. For more information, see Managing SRX Series Chassis Clusters Using RPCs.Use the
get-interface-information
RPC to get the interfaces inventory. This RPC reports information about the interfaces on the secondary node except for the fxp0 interface.
See the Junos XML API Operational Developer Reference for details about using the RPCs and their responses.
Using SNMP
Use the
jnx-chas-defines
MIB to understand the SRX Series chassis structure and modeling. This MIB is not for querying. It is only used to understand the chassis cluster modeling.Sample Chassis Definition MIB
jnxProductLineSRX3600 OBJECT IDENTIFIER ::= { jnxProductLine 34 } jnxProductNameSRX3600 OBJECT IDENTIFIER ::= { jnxProductName 34 } jnxProductModelSRX3600 OBJECT IDENTIFIER ::= { jnxProductModel 34 } jnxProductVariationSRX3600 OBJECT IDENTIFIER ::= { jnxProductVariation 34 } jnxChassisSRX3600 OBJECT IDENTIFIER ::= { jnxChassis 34 } jnxSlotSRX3600 OBJECT IDENTIFIER ::= { jnxSlot 34 } jnxSRX3600SlotFPC OBJECT IDENTIFIER ::= { jnxSlotSRX3600 1 } jnxSRX3600SlotHM OBJECT IDENTIFIER ::= { jnxSlotSRX3600 2 } jnxSRX3600SlotPower OBJECT IDENTIFIER ::= { jnxSlotSRX3600 3 } jnxSRX3600SlotFan OBJECT IDENTIFIER ::= { jnxSlotSRX3600 4 } jnxSRX3600SlotCB OBJECT IDENTIFIER ::= { jnxSlotSRX3600 5 } jnxSRX3600SlotFPB OBJECT IDENTIFIER ::= { jnxSlotSRX3600 6 } jnxMediaCardSpaceSRX3600 OBJECT IDENTIFIER ::= { jnxMediaCardSpace 34 } jnxSRX3600MediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceSRX3600 1 } jnxMidplaneSRX3600 OBJECT IDENTIFIER ::= { jnxBackplane 34 }
Use the following command to view the SNMP MIB.
user@host>
show snmp mib ?
Possible completions: get Get SNMP object value get-next Get next SNMP object value walk Walk SNMP object values {secondary:node0} user@host>show snmp mib get ?
Possible completions: <name> ascii Convert string indices to 'ascii-keys' representation decimal Decimal format (default) {secondary:node0} user@host>show snmp mib walk ?
Possible completions: <name> Requested SNMP object names ascii Convert string indices to 'ascii-keys' representation decimal Decimal format (default)Use the jnx-chassis MIB to get the chassis inventory.
Table 1: jnx-chassis MIB Information MIB Item
Description
Top of MIB
Use the top-level objects to show chassis details such as the jnxBoxClass, jnxBoxDescr, jnxBoxSerialNo, jnxBoxRevision, and jnxBoxInstalled MIB objects.
jnxContainersTable
Use to show the containers that the device supports.
jnxContentsTable
Use to show the chassis contents.
jnxContentsChassisId
Use to show which components belong to which node.
jnxLedTable
Use to check the LED status of the components. This MIB only reports the LED status of the primary node.
jnxFilledTable
Use to show the empty/filled status of the container in the device containers table.
jnxOperatingTable
Use to show the operating status of Operating subjects in the box contents table.
jnxRedundancyTable
Use to show redundancy details on both nodes. Note that currently this MIB only reports on the Routing Engines. Both Routing Engines are reported as the primary of the respective nodes. Do not use this to determine the active and backup status.
jnxFruTable
Use to show the field-replaceable unit (FRU) in the chassis. Note that even the empty slots are reported.
Note:The jnx-chassis MIB is not supported on SRX Series branch devices in cluster mode. It is supported on standalone SRX Series branch devices.
Chassis MIB Walk Example
JUNIPER-MIB::jnxContentsDescr.1.1.0.0 = STRING: node0 midplane JUNIPER-MIB::jnxContentsDescr.1.2.0.0 = STRING: node1 midplane JUNIPER-MIB::jnxContentsDescr.2.1.0.0 = STRING: node0 PEM 0 JUNIPER-MIB::jnxContentsDescr.2.2.0.0 = STRING: node0 PEM 1 JUNIPER-MIB::jnxContentsDescr.2.5.0.0 = STRING: node1 PEM 0 JUNIPER-MIB::jnxContentsDescr.2.6.0.0 = STRING: node1 PEM 1 JUNIPER-MIB::jnxContentsDescr.4.1.0.0 = STRING: node0 Left Fan Tray JUNIPER-MIB::jnxContentsDescr.4.1.1.0 = STRING: node0 Top Rear Fan JUNIPER-MIB::jnxContentsDescr.4.1.2.0 = STRING: node0 Bottom Rear Fan JUNIPER-MIB::jnxContentsDescr.4.1.3.0 = STRING: node0 Top Middle Fan JUNIPER-MIB::jnxContentsDescr.4.1.4.0 = STRING: node0 Bottom Middle Fan JUNIPER-MIB::jnxContentsDescr.4.1.5.0 = STRING: node0 Top Front Fan JUNIPER-MIB::jnxContentsDescr.4.1.6.0 = STRING: node0 Bottom Front Fan JUNIPER-MIB::jnxContentsDescr.4.2.0.0 = STRING: node1 Left Fan Tray JUNIPER-MIB::jnxContentsDescr.4.2.1.0 = STRING: node1 Top Rear Fan JUNIPER-MIB::jnxContentsDescr.1.1.0.0 = STRING: node0 midplane JUNIPER-MIB::jnxContentsDescr.1.2.0.0 = STRING: node1 midplane JUNIPER-MIB::jnxContentsDescr.2.1.0.0 = STRING: node0 PEM 0 JUNIPER-MIB::jnxContentsDescr.2.2.0.0 = STRING: node0 PEM 1 JUNIPER-MIB::jnxContentsDescr.2.5.0.0 = STRING: node1 PEM 0 JUNIPER-MIB::jnxContentsDescr.2.6.0.0 = STRING: node1 PEM 1 JUNIPER-MIB::jnxContentsDescr.4.1.0.0 = STRING: node0 Left Fan Tray JUNIPER-MIB::jnxContentsDescr.4.1.1.0 = STRING: node0 Top Rear Fan JUNIPER-MIB::jnxContentsDescr.4.1.2.0 = STRING: node0 Bottom Rear Fan JUNIPER-MIB::jnxContentsDescr.4.1.3.0 = STRING: node0 Top Middle Fan JUNIPER-MIB::jnxContentsDescr.4.1.4.0 = STRING: node0 Bottom Middle Fan JUNIPER-MIB::jnxContentsDescr.4.1.5.0 = STRING: node0 Top Front Fan JUNIPER-MIB::jnxContentsDescr.4.1.6.0 = STRING: node0 Bottom Front Fan JUNIPER-MIB::jnxContentsDescr.4.2.0.0 = STRING: node1 Left Fan Tray JUNIPER-MIB::jnxContentsDescr.4.2.1.0 = STRING: node1 Top Rear Fan
ifTable—Use to show all the interfaces on the cluster. Note that except for the fxp0 interface on the secondary node, all interfaces of the secondary node are reported by the primary node.
jnx-if-extensions/ifChassisTable—Use to show the interface mapping to the respective PIC and FPC.
ifStackStatusTable—Use to show the sub-interfaces and respective parent interfaces.