Chassis MIB Support (Junos Fusion)
The Chassis MIB has been enhanced to enable satellite devices to be represented in the chassis MIB. Satellite devices are represented as FPCs/slots (100, 101,102,..) in the aggregation device. The support is enabled using a separate range of container indices (CIDX), which allows the SNMP process to redirect relevant SNMP requests to the satellite device management process.
The CIDX for representing satellite device hardware components in Junos Fusion are offset by 100 from indices for hardware components on Junos devices; for example a regular CIDX 2 (Power Supply) is 102 for the power supply of the satellite device. Using these indices you can distinguish the satellite device hardware from the aggregate device. The L1 index for satellite device entries refers to their FPC slot identifiers. As per the chassis MIB convention, identifiers are 1-based. For example, satellite device 100 will have an L1 index of 101, satellite device 101 will have an L1 index of 102, and so on.
Table 1shows the CIDXs used for satellite devices.
CIDX |
Component Type |
|---|---|
102 |
Power Supply |
104 |
Fan |
107 |
FPC |
108 |
PIC |
The following tables have been enhanced to include object IDs for satellite devices:
jnxContainersTable
jnxContentsTable
jnxFilledTable
jnxOperatingTable
jnxFRUTable
Examples of new object IDs in the jnxContainersTable:
jnxContainersType.102 = jnxSatelliteDeviceSlotPower.0 jnxContainersType.104 = jnxSatelliteDeviceSlotFan.0 jnxContainersType.107 = jnxSatelliteDeviceSlotFPC.0 jnxContainersType.108 = jnxSatelliteDeviceMediaCardSpacePIC.0 … … jnxContainersDescr.102 = SD PEM slot jnxContainersDescr.104 = SD FAN slot jnxContainersDescr.107 = SD FPC slot jnxContainersDescr.108 = SD PIC slot
Examples of new object IDs in the jnxContentsTable:
jnxContentsType.102.102.1.0 = jnxSatelliteDeviceSlotPower jnxContentsType.102.102.2.0 = jnxSatelliteDeviceSlotPower jnxContentsType.104.102.1.0 = jnxSatelliteDeviceSlotFan jnxContentsType.104.102.2.0 = jnxSatelliteDeviceSlotFan jnxContentsType.104.102.3.0 = jnxSatelliteDeviceSlotFan jnxContentsType.104.102.4.0 = jnxSatelliteDeviceSlotFan jnxContentsType.104.102.5.0 = jnxSatelliteDeviceSlotFan jnxContentsType.107.102.0.0 = jnxSatelliteDeviceSlotFPC jnxContentsType.108.102.1.0 = jnxSatelliteDeviceMediaCardSpacePIC … jnxContentsDescr.102.102.1.0 = SD101 PEM 0 jnxContentsDescr.102.102.2.0 = SD101 PEM 1 jnxContentsDescr.104.102.1.0 = SD101 Fan Tray 0 jnxContentsDescr.104.102.2.0 = SD101 Fan Tray 1 jnxContentsDescr.104.102.3.0 = SD101 Fan Tray 2 jnxContentsDescr.104.102.4.0 = SD101 Fan Tray 3 jnxContentsDescr.104.102.5.0 = SD101 Fan Tray 4 jnxContentsDescr.107.102.0.0 = SD101 FPC: QFX5100-48S-6Q @ 101/*/* jnxContentsDescr.108.102.1.0 = SD101 PIC: 48x10G-6x40G @ 101/0/*
The following SNMP traps are generated for Satellite Devices, which are also logged as syslog messages:
Satellite Device (as FPC) add (online) or remove
Satellite Device Fan add (online) or remove
Satellite Device PSU add (online) or remove
Satellite Device PIC add (online) or remove
Satellite Device FAN failure or status
Satellite Device PSU failure or status
Table 2 shows the SNMP traps that can be generated for satellite devices.
Trap |
Condition |
|---|---|
jnxFruRemoval |
Sent when the specified FRU (FAN/PSU) has been removed from the chassis, or the satellite device has been removed from the aggregation device's database |
jnxFruInsertion |
Sent when the specified FRU (FAN/PSU) has been inserted into the satellite device |
jnxFruPowerOff |
Sent when the specified FRU (FAN/PSU) has been powered off in the satellite device |
jnxFruPowerOn |
Sent when the specified FRU (FAN/PSU) has been powered on in the satellite device |
jnxFruFailed |
Sent when the specified FRU (FAN/PSU) has failed in the satellite device. Typically, this is due to the FRU not powering up or being unable to load software. FRU replacement might be required |
jnxFruOK |
|
jnxFruOffline |
Sent when FPC's new reported state is not online or PSU/FAN/PIC is not present due to satellite device removal |
jnxFruOnline |
Sent when specified FRU (FPC,PIC,PSU,FAN) gets added in the aggregation device database |
jnxFruCheck |
Sent when the specified FRU (FAN/PSU) has encountered operational errors |
Given below are examples of the system log messages generated:
messages:Apr 15 21:28:36 card spmd[6706]: SPMD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 102, jnxFruL1Index 109, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName SD108 PEM 0, jnxFruType 7, jnxFruSlot 0, jnxFruOfflineReason 1, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
messages:Apr 15 21:28:36 card spmd[6706]: SPMD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 104, jnxFruL1Index 109, jnxFruL2Index 1, jnxFruL3Index 1, jnxFruName SD108 Fan Tray 0, jnxFruType 13, jnxFruSlot 0, jnxFruOfflineReason 1, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
messages:Apr 15 21:28:57 card spmd[8847]: SPMD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 107, jnxFruL1Index 103, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName SD102 FPC: @ 102/*/*, jnxFruType 3, jnxFruSlot 102)
messages:Apr 15 21:28:36 card spmd[6706]: SPMD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 108, jnxFruL1Index 109, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName SD108 PIC: 48x 10/100/1000 Base-T @ 108/0/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 1, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)