JUNIPER-MIB: View SNMP OID List / Download MIB

The MIB modules representing Juniper Networks' implementation of enterprise specific MIBs supported by a single SNMP agent.

The class of the box, indicating which product line the box is about, for example, 'Internet Router'.

The name, model, or detailed description of the box, indicating which product the box is about, for example 'M40'.

The serial number of this subject, blank if unknown or unavailable.

The revision of this subject, blank if unknown or unavailable.

The value of sysUpTime when the subject was last installed, up-and-running. Zero if unknown or already up-and-running when the agent was up.

A list of containers entries.

An entry of containers table.

The index for this entry.

The view(s) from which the specific container appears. This variable indicates that the specific container is embedded and accessible from the corresponding view(s). The value is a bit map represented as a sum. If multiple bits are set, the specified container(s) are located and accessible from that set of views. The various values representing the bit positions and its corresponding views are: 1 front 2 rear 4 top 8 bottom 16 leftHandSide 32 rightHandSide Note 1: LefHandSide and rightHandSide are referred to based on the view from the front. Note 2: If the specified containers are scattered around various views, the numbering is according to the following sequence: front -> rear -> top -> bottom -> leftHandSide -> rightHandSide For each view plane, the numbering sequence is first from left to right, and then from up to down. Note 3: Even though the value in chassis hardware (e.g. slot number) may be labelled from 0, 1, 2, and up, all the indices in MIB start with 1 (not 0) according to network management convention.

The abstraction level of the box or chassis. It is enumerated from the outside to the inside, from the outer layer to the inner layer. For example, top level (i.e. level 0) refers to chassis frame, level 1 FPC slot within chassis frame, level 2 PIC space within FPC slot.

The index of its next higher level container housing this entry. The associated jnxContainersIndex in the jnxContainersTable represents its next higher level container.

The type of this container.

The name or detailed description of this subject.

The maximum number of containers of this level per container of the next higher level. e.g. if there are six level 2 containers in level 1 container, then jnxContainersCount for level 2 is six.

The value of sysUpTime when the box contents table last changed. Zero if unknown or already existing when the agent was up.

A list of contents entries.

An entry of contents table.

The associated jnxContainersIndex in the jnxContainersTable.

The level one index of the container housing this subject. Zero if unavailable or inapplicable.

The level two index of the container housing this subject. Zero if unavailable or inapplicable.

The level three index of the container housing this subject. Zero if unavailable or inapplicable.

The type of this subject. zeroDotZero if unknown.

The name or detailed description of this subject.

The serial number of this subject, blank if unknown or unavailable.

The revision of this subject, blank if unknown or unavailable.

The value of sysUpTime when the subject was last installed, up-and-running. Zero if unknown or already up-and-running when the agent was up.

The part number of this subject, blank if unknown or unavailable.

Identifies the chassis on which the contents of this row exists.

A textual description of the chassis on which the contents of this row exists.

The clei code of this subject, blank if unknown or unavailable. A CLEI code is an intelligent code that consists of 10 alphanumeric characters with 4 data elements. The first data element is considered the basic code with the first 2 characters indicating the technology or equipment type, and the third and fourth characters denoting the functional sub-category. The second data element represents the features, and its three characters denote functional capabilities or changes. The third data element has one character and denotes a reference to a manufacturer, system ID, specification, or drawing. The fourth data element consists of two characters and contains complementary data. These two characters provide a means of differentiating or providing uniqueness between the eight character CLEI codes by identifying the manufacturing vintage of the product. Names are assigned via procedures defined in [GR485]. The assigned maintenance agent for the CLEI code, Telcordia Technologies, is responsible for assigning certain equipment and other identifiers (e.g., location, manufacturer/supplier) for the telecommunications industry.

The value of sysUpTime when the box LED table last changed. Zero if unknown or already at that state when the agent was up.

A list of status entries.

An entry of status table.

The associated table that this entry is related. Enumeration: 'jnxContainersTable': 2, 'other': 1, 'jnxContentsTable': 3.

The index of the associated table that this entry is related.

The level one index of the associated table that this entry is related. Zero if unavailable or inapplicable.

The level two index of the associated table that this entry is related. Zero if unavailable or inapplicable.

The level three index of the associated table that this entry is related. Zero if unavailable or inapplicable.

The originator of the this entry.

The name or detailed description of this subject.

The state of the LED indicator. Enumeration: 'blue': 5, 'amber': 6, 'yellow': 3, 'other': 1, 'green': 2, 'red': 4.

The state of the LED indicator. Identical to jnxLEDState, but with enums ordered from 'most operational' to 'least operational' states. Enumeration: 'blue': 1, 'amber': 3, 'yellow': 4, 'other': 6, 'green': 2, 'red': 5.

The value of sysUpTime when the box filled status table last changed. Zero if unknown or already at that state when the agent was up.

A list of filled status entries.

An entry of filled status table.

The associated jnxContainersIndex in the jnxContainersTable.

The level one index of the container housing this subject. Zero if unavailable or inapplicable.

The level two index of the container housing this subject. Zero if unavailable or inapplicable.

The level three index of the container housing this subject. Zero if unavailable or inapplicable.

The name or detailed description of this subject.

The filled state of this subject. Enumeration: 'unknown': 1, 'filled': 3, 'empty': 2.

Identifies the chassis on which the contents of this row exists.

A textual description of the chassis on which the contents of this row exists.

A list of operating status entries.

An entry of operating status table.

The associated jnxContentsContainerIndex in the jnxContentsTable.

The level one index associated with this subject. Zero if unavailable or inapplicable.

The level two index associated with this subject. Zero if unavailable or inapplicable.

The level three index associated with this subject. Zero if unavailable or inapplicable.

The name or detailed description of this subject.

The operating state of this subject. Enumeration: 'reset': 4, 'standby': 7, 'unknown': 1, 'down': 6, 'runningAtFullSpeed': 5, 'running': 2, 'ready': 3.

The temperature in Celsius (degrees C) of this subject. Zero if unavailable or inapplicable.

The CPU utilization in percentage of this subject. Zero if unavailable or inapplicable.

The CPU utilization in percentage of this subject spending in interrupt service routine (ISR). Zero if unavailable or inapplicable.

The DRAM size in bytes of this subject. Zero if unavailable or inapplicable.

The buffer pool utilization in percentage of this subject. Zero if unavailable or inapplicable.

The heap utilization in percentage of this subject. Zero if unavailable or inapplicable.

The time interval in 10-millisecond period that this subject has been up and running. Zero if unavailable or inapplicable.

The value of sysUpTime when this subject last restarted. Zero if unavailable or inapplicable.

The installed memory size in Megabytes of this subject. Zero if unavailable or inapplicable.

The operating state of this subject. Identical to jnxOperatingState, but with enums ordered from 'most operational' to 'least operational' states. Enumeration: 'reset': 5, 'standby': 2, 'unknown': 7, 'down': 6, 'runningAtFullSpeed': 4, 'running': 1, 'ready': 3.

Identifies the chassis on which the contents of this row exists.

A textual description of the chassis on which the contents of this row exists.

The time at which this entity last restarted.

The CPU Load Average over the last 1 minutes Here it will be shown as percentage value Zero if unavailable or inapplicable.

The CPU Load Average over the last 5 minutes Here it will be shown as percentage value Zero if unavailable or inapplicable.

The CPU Load Average over the last 15 minutes Here it will be shown as percentage value Zero if unavailable or inapplicable.

A list of redundancy information entries.

An entry in the redundancy information table.

The associated jnxContentsContainerIndex in the jnxContentsTable.

The level one index associated with this subject. Zero if unavailable or inapplicable.

The level two index associated with this subject. Zero if unavailable or inapplicable.

The level three index associated with this subject. Zero if unavailable or inapplicable.

The name or detailed description of this subject.

The election priority of redundancy configuration for this subject. The value 'notApplicable' means no specific instance is configured to be master or backup; whichever component boots up first becomes a master. Enumeration: 'disabled': 4, 'unknown': 1, 'master': 2, 'backup': 3, 'notApplicable': 5.

The current running state for this subject. Enumeration: 'disabled': 4, 'unknown': 1, 'master': 2, 'backup': 3.

The total number of switchover as perceived by this subject since routing engine is up and running. The switchover is defined as a change in state of jnxRedundancyState from master to backup or vice versa. Its value is reset when the routing engine is reset or rebooted.

The value of sysUpTime when the jnxRedundancyState of this subject was last switched over from master to backup or vice versa. Zero if unknown or never switched over since the routing engine is up and running.

The reason of the last switchover for this subject. Enumeration: 'userSwitched': 3, 'other': 1, 'neverSwitched': 2, 'autoSwitched': 4.

The period of sending keepalive messages between the master and backup subsystems. It is a system-wide preset value in seconds used by internal mastership resolution. Zero if unavailable or inapplicable.

The timeout period in seconds, by the keepalive watchdog timer, before initiating a switch over to the backup subsystem. Zero if unavailable or inapplicable.

The elapsed time in seconds by this subject since receiving the last keepalive message from the other subsystems. Zero if unavailable or inapplicable.

The total number of losses on keepalive messages between the master and backup subsystems as perceived by this subject since the system is up and running. Zero if unavailable or inapplicable.

Identifies the chassis on which the contents of this row exists.

A textual description of the chassis on which the contents of this row exists.

A list of FRU status entries.

An entry in the FRU status table.

The associated jnxContentsContainerIndex in the jnxContentsTable.

The level one index associated with this subject. Zero if unavailable or inapplicable.

The level two index associated with this subject. Zero if unavailable or inapplicable.

The level three index associated with this subject. Zero if unavailable or inapplicable.

The name or detailed description of this subject.

The FRU type for this subject. Enumeration: 'craftInterfacePanel': 12, 'routingEngine': 6, 'lineCardChassis': 14, 'flexiblePicConcentrator': 3, 'controlBoard': 5, 'portInterfaceCard': 11, 'forwardingEngineBoard': 15, 'powerEntryModule': 7, 'switchingAndForwardingModule': 4, 'other': 1, 'fan': 13, 'clockGenerator': 2, 'frontPanelModule': 8, 'switchInterfaceBoard': 9, 'protectedSystemDomain': 16, 'processorMezzanineBoardForSIB': 10.

The slot number of this subject. This is equivalent to jnxFruL1Index in meaning. Zero if unavailable or inapplicable.

The current state for this subject. Enumeration: 'announceOnline': 5, 'standby': 10, 'unknown': 1, 'anounceOffline': 7, 'diagnostic': 9, 'empty': 2, 'online': 6, 'ready': 4, 'offline': 8, 'present': 3.

The temperature in Celsius (degrees C) of this subject. Zero if unavailable or inapplicable.

The offline reason of this subject. Enumeration: 'spuFlowdDownNoCore': 52, 'spuResetRequest': 36, 'pfeVersionMismatch': 25, 'cppDisconnect': 43, 'spuFlowdDown': 37, 'fruAntiCounterfeitRetry': 64, 'noPower': 4, 'spuFlowdCoreDumpComplete': 54, 'reconnectFpcFail': 49, 'febCfgChange': 68, 'badVoltage': 74, 'minorErrors': 19, 'fpcMisconfig': 27, 'fruReconnectNotReady': 61, 'fruPfeReset': 60, 'unresponsiveRestart': 15, 'fruServiceRestartRequest': 35, 'reconnect': 23, 'fruFabricDown': 63, 'picBounce': 73, 'configPowerOff': 5, 'spuSpi4Down': 38, 'fpcAppFailed': 50, 'configHoldInReset': 6, 'fruConfigOffline': 34, 'singleSfmModeChange': 12, 'spuFlowdCoreDumpIncomplete': 53, 'febRddCfgChange': 26, 'powerCycle': 22, 'unknown': 1, 'fpgaSpi4LinkDown': 41, 'spuCoreDump': 40, 'fruInServSoftUpgradeError': 32, 'fruFpcUnsupported': 70, 'masterClockDown': 11, 'fruFPCChassisClusterDisable': 65, 'fruReconnectFail': 28, 'spuIdpdCoreDumpComplete': 57, 'softRstOnSpcSpuFailure': 47, 'fruSfLinkDown': 62, 'routeLocalizationRoleChange': 69, 'fruResetThresholdExceeded': 72, 'spuIdpdDownNoCore': 55, 'packetSchedulingModeChange': 13, 'rstOnSpcSpuFailure': 46, 'spuWatchdogTimeout': 39, 'spuCoreDumpComplete': 45, 'spuCoreDumpIncomplete': 58, 'buttonPress': 8, 'spuIdpdDown': 59, 'cliRestart': 9, 'hwAuthenticationFailure': 48, 'cpuNotBoot': 44, 'fpcKernelCrash': 51, 'fruFPCFabricDownOffline': 67, 'lccHardRestart': 20, 'spuIdpdCoreDumpIncomplete': 56, 'spuFipsError': 66, 'sonetClockAbsent': 16, 'fruChasdPowerRatingExceed': 33, 'none': 2, 'i3Spi4LinkDown': 42, 'fruFwddReset': 29, 'rddPowerOff': 17, 'cliCommand': 7, 'psdVersionMismatch': 71, 'overtempShutdown': 10, 'fruFebSwitch': 30, 'overvoltage': 24, 'lccVersionMismatch': 21, 'error': 3, 'fruFebOffline': 31, 'majorErrors': 18, 'physicalRemoval': 14.

The value of sysUpTime when this subject was last powered off. Zero if unavailable or inapplicable.

The value of sysUpTime when this subject was last powered on. Zero if unavailable or inapplicable.

The time interval in 10-millisecond period that this subject has been up and running since the last power on time. Zero if unavailable or inapplicable.

Identifies the chassis on which the contents of this row exists.

A textual description of the chassis on which the contents of this row exists.

The PSD assignment of this subject. Zero if unavailable or not applicable.

The percentage of kernel memory used of this subject. 0 if unavailable or inapplicable.

The system domain type of this subject, notApplicable will be returned if this feature is not supported. Enumeration: 'notApplicable': 1, 'protectedSystemDomain': 3, 'rootSystemDomain': 2.

A jnxPowerSupplyFailure trap signifies that the SNMP entity, acting in an agent role, has detected that the specified power supply in the chassis has been in the failure (bad DC output) condition.

A jnxFanFailure trap signifies that the SNMP entity, acting in an agent role, has detected that the specified cooling fan or impeller in the chassis has been in the failure (not spinning) condition.

A jnxOverTemperature trap signifies that the SNMP entity, acting in an agent role, has detected that the specified hardware component in the chassis has experienced over temperature condition.

A jnxRedundancySwitchover trap signifies that the SNMP entity, acting in an agent role, has detected that the specified hardware component in the chassis has experienced a redundancy switchover event defined as a change in state of jnxRedundancyState from master to backup or vice versa.

A jnxFruRemoval trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has been removed from the chassis.

A jnxFruInsertion trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has been inserted into the chassis.

A jnxFruPowerOff trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has been powered off in the chassis.

A jnxFruPowerOn trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has been powered on in the chassis.

This indicates the specified FRU (Field Replaceable Unit) has failed in the chassis. Most probably this is due toi some hard error such as fru is not powering up or not able to load ukernel. In these cases, fru is replaced.

A jnxFruOffline trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has gone offline in the chassis.

A jnxFruOnline trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has gone online in the chassis.

A jnxFruCheck trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has encountered some operational errors and gone into check state in the chassis.

A jnxFEBSwitchover trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FEB (Forwarding Engine Board) has switched over.

A jnxHardDiskFailed trap signifies that the SNMP entity, acting in an agent role, has detected that the Disk in the specified Routing Engine has encountered some operational errors and gone into failed state in the chassis.

A DiskMissing trap signifies that the SNMP entity, acting in an agent role, has detected that hard disk in the specified outing Engine is missing from boot device list.

A jnxBootFromBackup trap signifies that the SNMP entity, acting in an agent role, has detected that the specified routing-engine/member has booted from the back up root partition

A jnxPowerSupplyOK trap signifies that the SNMP entity, acting in an agent role, has detected that the specified power supply in the chassis has recovered from the failure (bad DC output) condition.

A jnxFanOK trap signifies that the SNMP entity, acting in an agent role, has detected that the specified cooling fan or impeller in the chassis has recovered from the failure (not spinning) condition.

A jnxTemperatureOK trap signifies that the SNMP entity, acting in an agent role, has detected that the specified hardware component in the chassis has recovered from over temperature condition.

A jnxFruOK trap signifies that the SNMP entity, acting in an agent role, has detected that the specified FRU (Field Replaceable Unit) has recovered from previous operational errors and it is in ok state in the chassis.