Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

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.

Table 1: CIDX’s 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:

Examples of new object IDs in the jnxContentsTable:

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.

Table 2: SNMP Traps 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: