jnxBoxAnatomy

The object identifier for the jnxMIBs root branch is {juniperMIB 3} and includes one main subbranch, jnxBoxAnatomy, whose object identifier is {jnxMibs 1}.

The jnxBoxAnatomy MIB is explained in the following sections:

• Top-Level Objects
• jnxContainersTable
• jnxContentsLastChange
• jnxContentsTable
• jnxLEDLastChange
• jnxLEDTable
• jnxFilledLastChange
• jnxFilledTable
• jnxOperatingTable
• jnxRedundancyTable
• jnxFruTable
• jnxBoxKernelMemoryUsedPercent
• jnxBoxSystemDomainType

Top-Level Objects

The following branches of the jnxBoxAnatomy MIB are top-level objects:

• jnxBoxClass—The object identifier for the jnxBoxClass object is {jnxBoxAnatomy 1}. This object classifies the chassis product line.
• jnxBoxDescr—The object identifier for the jnxBoxDescr object is {jnxBoxAnatomy 2}. This object describes the chassis name and model.
• jnxBoxSerialNo—The object identifier for the jnxBoxSerialNo object is {jnxBoxAnatomy 3}. This object indicates the serial number of the chassis. jnxBoxSerialNo remains blank if the serial number is unknown or unavailable.
• jnxBoxRevision—The object identifier for the jnxBoxRevision object is {jnxBoxAnatomy 4}. This object indicates the last revision of the chassis.
• jnxBoxInstalled—The object identifier for the jnxBoxInstalled object is {jnxBoxAnatomy 5}. This object indicates the last time the box was installed and operational, represented by the sysUpTime value.

jnxContainersTable

The object identifier for the jnxContainersTable object is {jnxBoxAnatomy 6}. This object shows the structure of the chassis.

You can use the jnxContainersTable object to retrieve specific information on the router, such as how many of each component the router can contain. For example, the jnxContainersTable of an M20 router indicates that the router can accommodate four Flexible PIC Concentrators (FPCs); however, it does not describe how many FPCs the router actually has.

For more information on how many FPCs are actually on a router, see jnxContentsTable.

Entries within the jnxContainersTable object are represented by the jnxContainersEntry object, whose object identifier is {jnxContainersTable 1}. The jnxContainersEntry object contains the following objects, which describe the contents of a particular router:

• jnxContainersIndex—The index value of an entry in the jnxContainersEntry object that corresponds to jnxContainersType and jnxContainersDescr, and whose object identifier is {jnxContainersEntry 1}.
• jnxContainersView—The orientation of a container from the front of the router and whose object identifier is {jnxContainersEntry 2}. This object also indicates that the container is embedded in the router and how it is accessible from corresponding views. The value of this object is a bitmap represented as a sum. If multiple bits are set, you can access the container from that set of views. The values represent the bit positions and their corresponding views as follows:
  • 1—Front
  • 2—Rear
  • 4—Top
  • 8—Bottom
  • 16—Left side
  • 32—Right side

  For each view plane, if specified counters are scattered in various views, the numbering sequence starts from left to right and then from top to bottom, as follows:

  • Left side
  • Right side
  • Top
  • Bottom
  • Front
  • Rear

    Note: References to left and right sides are based on the view from the front of the chassis.

    Note: In accordance with network management conventions, all indexes in the MIB begin with 1, not 0, although the slot number might be labeled 0.

• jnxContainersLevel—The abstraction level of the box or components for the jnxContainersEntry object and whose object identifier is {jnxContainersEntry 3}. The level is enumerated from the outside to the inside, and from the outer layer to the inner layer.

  For example, if the top level (level 0) of the box refers to the chassis frame, then the next level (level 1) refers to the FPC slot within the chassis frame. Finally, the PIC space within the FPC slot of the chassis corresponds to level 2.

• jnxContainersWithin—The container housing the entry at the next-higher level of the jnxContainersEntry object and whose object identifier is {jnxContainersEntry 4}.

  For example, the within value for jnxMediaCardSpacePIC.0 is 7. Because the jnxM20SlotFPC.0 retains an index value of 7, the FPC houses the PIC.

• jnxContainersType—The component of the Chassis MIB at a specific index, view, level, and within value for the jnxContainersEntry object and whose object identifier is {jnxContainersEntry 5}.
• jnxContainersDescr—The description of the component in the jnxContainersEntry object and whose object identifier is {jnxContainersEntry 6}.
• jnxContainersCount—The maximum number of a given component that the router can accommodate within the jnxContainersEntry object and whose object identifier is {jnxContainersEntry 7}.

  For example, the M20 router can house a specific maximum number of FPCs within the chassis frame. The maximum number is not necessarily the actual number of FPCs; this can change dynamically.

Table 37 through Table 44 provide examples of jnxContainersEntry objects in the jnxContainersTable. The following column headings for each table are abbreviated to correspond to the parts of the jnxContainersEntry objects:

• Index—jnxContainersIndex
• View—jnxContainersView
• Level—jnxContainersLevel
• Within—jnxContainersWithin
• Type—jnxContainersType
• Description—jnxContainersDescr
• Count—jnxContainersCount

Table 37 describes objects contained in a jnxContainersEntry in the jnxContainersTable of an M40 router.

Table 37: jnxContainersEntry Objects in the jnxContainersTable of an M40 Router

Table 38 describes objects in the jnxContainersTable of an M20 router.

Table 38: jnxContainersEntry Objects in the jnxContainersTable of an M20 Router

Table 39 describes objects contained in a jnxContainersEntry in the jnxContainersTable of an M160 router.

Table 39: jnxContainersEntry Objects in the jnxContainersTable of an M160 Router

Table 40 describes objects contained in a jnxContainersEntry in the jnxContainersTable of an M10 router.

Table 40: jnxContainersEntry Objects in the jnxContainersTable of an M10 Router

Table 41 describes objects contained in a jnxContainersEntry in the jnxContainersTable of an M5 router.

Table 41: jnxContainersEntry Objects in the jnxContainersTable of an M5 Router

Table 42 describes objects contained in a jnxContainersEntry in the jnxContainersTable of a T640 router.

Table 42: jnxContainersEntry Objects in the jnxContainersTable of a T640 Router

Table 43 describes objects contained in a jnxContainersEntry in the jnxContainersTable of a T320 router.

Table 43: jnxContainersEntry Objects in the jnxContainersTable of a T320 Router

Table 44 describes objects contained in a jnxContainersEntry in the jnxContainersTable of an M40e router.

Table 44: jnxContainersEntry Objects in the jnxContainersTable of an M40e Router

jnxContentsLastChange

The object identifier for jnxContentsLastChange object is {jnxBoxAnatomy 7}. This object indicates the time at which the box contents last changed, represented by the sysUpTime value.

jnxContentsTable

The object identifier for jnxContentsTable object is {jnxBoxAnatomy 8}. This object specifies the contents of the chassis.

The jnxContentsTable lists the contents of an entry, which are defined as follows:

• jnxContentsContainerIndex—Associates the jnxContainersIndex with the jnxContainersTable. The object identifier is {jnxContentsEntry 1}.
• jnxContentsL1Index—Denotes the level-one index of the container housing the component. The object identifier is {jnxContentsEntry 2}. It indicates the position of the component within different levels of the containers. This value is 0 if the position is unavailable or not applicable.

  Note: MIBs start with a value of 1, whereas the physical count on the router starts with a value of 0. To find the actual location of a component within a router, you must subtract 1 from the L1, L2, or L3 index.

• jnxContentsL2Index—Denotes the level-two index of the container housing the component. The object identifier is {jnxContentsEntry 3}. It indicates the position of the component within different levels of the containers. This value is 0 if the position is unavailable or not applicable.
• jnxContentsL3Index—Denotes the level-three index of the container housing the component. The object identifier is {jnxContentsEntry 4}. It indicates the position of the component within different levels of the containers. This value is 0 if the position is unavailable or not applicable.
• jnxContentsType—Indicates the type of the component at a specific container index or L1, L2, or L3 index. The object identifier is {jnxContentsEntry 5}.
• jnxContentsDescr—Specifies the type of the component in plain English. The object identifier is {jnxContentsEntry 6}.
• jnxContentsSerialNo—Specfies the serial number of the component. The object identifier is {jnxContentsEntry 7}.
• jnxContentsRevision—Contains the revision level of the component. The object identifier is {jnxContentsEntry 8}.
• jnxContentsInstalled—Indicates the time at which the component was last installed and operational, represented by the sysUpTime value. The object identifier is {jnxContentsEntry 9}.
• jnxContentsPartNo—Contains the part number of the component (blank if unknown or unavailable). The object identifier is {jnxContentsEntry 10}.
• jnxContentsChassisId —Contains the ID of the chassis that contains the components. The object identifier is {jnxContentsEntry 11}.
• jnxContentsChassisDescr—Specifies the description of the chassis in plain English. The object identifier is {jnxContentsEntry 12}.
• jnxContentsChassisCleiCode—Contains the CLEI code of the chassis that contains the components listed in the row. 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 two characters indicating the technology or equipment type, and the third and fourth characters denoting the functional subcategory. 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. For more information about CLEI code, see http://www.commonlanguage.com/resources/commonlang/ productshowroom/showroom/equip_id/carriers/overview.html. The object identifier is {jnxContentsEntry 13}.

Table 45 through Table 47 provide examples of jnxContentEntry objects. The following column headings for each table are abbreviated to correspond to the parts of the jnxContentsEntry objects:

• Container index— jnxContentsContainerIndex
• L1 Index—jnxContentsL1Index
• L2 Index—jnxContentsL2Index
• L3 Index—jnxContentsL3Index
• Type—jnxContentsType
• Description—jnxContentsDescr
• Serial Number—jnxContentsSerialNo
• Revision—jnxContentsRevision
• Installed—jnxContentsInstalled
• Part Number—jnxContentsPartNo

Table 45 provides an example of jnxContentEntry objects in the jnxContentTable of an M20 router.

Table 45: jnxContentsEntry Objects in the jnxContentsTable of an M20 Router

To verify the L1, L2, and L3 indexes, use the show chassis hardware command. Sample command output from an M20 router is listed below.

Item    Version  Part number   Serial Number    Description
Chassis53711     M20
Backplane        REV 07   710-001517       AL3280
Power Supply A   REV 05   740-001466          001652      DC
Power Supply B   REV 05   740-001466          001632      DC
Display         REV 04   710-001519      AP9225
Host 0 c900000619e6ba01 teknor
SSB slot 0        REV 01  710-001951        AG0809      Internet Processor
II
FPC 0      REV 01  710-001292  AN1335
 PIC 0     REV 04  750-002992  HD4313      4x F/E, 100 BASE-TX
 PIC 1     REV 04  750-002992  AJ5844      4x F/E, 100 BASE-TX
 PIC 2     REV 04  750-002992  HD4518      4x F/E, 100 BASE-TX
 PIC 3     REV 04  750-002992  HD4515      4x F/E, 100 BASE-TX
FPC 1      REV 01  710-001292  AN1124
 PIC 0     REV 04  750-002992  HD4296      4x F/E, 100 BASE-TX
 PIC 1     REV 04  750-002992  HD4323      4x F/E, 100 BASE-TX
 PIC 2     REV 04  750-002992  HD4129      4x F/E, 100 BASE-TX
 PIC 3     REV 04  750-002992  HD4341      4x F/E, 100 BASE-TX
FPC 2      REV 01  710-001292  AN1726
 PIC 0     REV 07  750-002303  AH4147      4x F/E, 100 BASE-TX
 PIC 1     REV 07  750-002303  AH4238      4x F/E, 100 BASE-TX
 PIC 2     REV 07  750-002303  AH4116      4x F/E, 100 BASE-TX
 PIC 3     REV 07  750-002303  AH4208      4x F/E, 100 BASE-TX
FPC 3      REV 01  710-001292  AN1691
 PIC 0     REV 08  750-001072  AS3697      1x G/E, 1000
BASE-SX
 PIC 1     REV 03  750-001190  AE1110      1x COC12, SMIR
 PIC 3     REV 04  750-003250  AD9599      1x CSTM1, SMIR

Table 46 provides an example of jnxContentEntry objects in the jnxContentTable of a T640 router.

Table 46: jnxContentsEntry Objects in the jnxContentsTable of a T640 Router

To verify the L1, L2, and L3 indexes, use the show chassis hardware command. Sample command output from a T640 router is listed below.

Hardware inventory:
Item       Version Part number Serial number   Description
Chassis    T640
Midplane    REV 04  710-002726  AX5633
FPM GBUS    REV 02  710-002901  HE3245
FPM Display    REV 02  710-002897  HA4873
CIP          REV 05  710-002895  HA4729
PEM 1         RevX02  740-002595  MD21815         Power Entry Module
SCG 0         REV 04  710-003423  HF6023
SCG 1         REV 04  710-003423  HF6061
Host 0    unknown
Host 1    REV 01  740-005022  210865700292   RE-3.0
CB 0          REV 06  710-002728  HE3614
CB 1          REV 06  710-002728  HE3627
FPC 1         REV 01  710-002385  HE3009      FPC Type 1
 CPU          REV 06  710-001726  HC0010
 PIC 0        REV 08  750-001072  AP5542      1x G/E, 1000 BASE-SX
 PIC 1        REV 02  750-002983  AK6894      1x OC-12 ATM, SMIR
 PIC 2        REV 04  750-001894  HD4968      1x G/E, 1000 BASE-SX
 MMB 1        REV 03  710-001723  HE7264      MMB-144mbit
 ICBM         REV 01  710-003384  HE3042
 PPB 0        REV 01  710-003758  HE7173      PPB Type 2
 PPB 1        REV 01  710-003758  HE7170      PPB Type 2
FPC 5         REV 03  710-001721  HD5001      FPC Type 3
 CPU         REV 06  710-001726          HA5080
 PIC 0        REV 01  750-004535  HC0273      1x OC-192 SM SR1
 PIC 1        REV 01  750-004535  HC0271      1x OC-192 SM SR1
 PIC 2        REV 01  750-004535  HC0254      1x OC-192 SM SR1
 MMB 0        REV 03  710-001723  HE7263      MMB-144mbit
 MMB 1        REV 03  710-001723  HE7266      MMB-144mbit
 ICBM         REV 01  710-003384  HE3044
 PPB 0        REV 02  710-002845  HD6027      PPB Type 3
 PPB 1        REV 02  710-002845  HD6039      PPB Type 3
FPC 7         REV 01  710-002385  HE3179      FPC Type 2
 CPU         REV 06  710-001726          HE7915
 PIC 0        REV 01  710-002381  AD3632      2x G/E, 1000 BASE-SX
 PIC 1        REV 05  750-001901  AD3831      4x OC-12 SONET, SMIR
 PIC 2        REV 01  750-001900  AA9603      1x OC-48 SONET, SMIR
 PIC 3        REV 05  750-001900  AD5724      1x OC-48 SONET, SMSR
 MMB 1        REV 02  710-004047  HE3424      MMB-288mbit
 ICBM         REV 04  710-003384  HA4480
 PPB 0        REV 02  710-003758  HE3169      PPB Type 2
 PPB 1        REV 02  710-003758  HA4535      PPB Type 2
SPMB 0       REV 02  710-003229 HF6876
SPMB 1       REV 02  710-003229 HG6237
SIB 0         REV 02  710-005157  HJ9669      SIB-I8-F16
SIB 1         REV 02  710-005157  HJ9668      SIB-I8-F16
SIB 2         REV 02  710-005157  HH3039      SIB-I8-F16
SIB 3         REV 02  710-005157  HH3041      SIB-I8-F16
SIB 4         REV 02  710-005157  HJ9657      SIB-I8-F16

Table 47 provides an example of jnxContentEntry objects in the jnxContentTable of a T320 router.

Table 47: jnxContentsEntry Objects in the jnxContentsTable of a T320 Router

To verify the L1, L2, and L3 indexes, use the show chassis hardware command. Sample command output from a T320 router is listed below.

Hardware inventory:
Item             Version  Part number  Serial number     Description
Chassis  T320
Midplane         REV 01   710-004339   AY4527
FPM GBUS         REV 02   710-004461   AY4514
FPM Display      REV 02   710-002897   HF6097
CIP              REV 05   710-002895   HC0476
PEM 0            Rev 01   740-004359   ML14099           Power Entry
Module
SCG 0            REV 06   710-004455   AY4520
SCG 1            REV 06   710-004455   AY4526
RE 0               REV 01   740-005022   210865700286      RE-3.0
RE 1               REV 01   740-005022   210929000186      RE-3.0
CB 0             REV 11   710-002728   AY4765
CB 1             REV 06   710-002728   HG6051
FPC 1            REV 01   710-004333   AY4507            FPC Type 3
  CPU            REV 06   710-001726   HA4719
  MMB 1          REV 03   710-004047   HD5738            MMB-288mbit
  PPB 0          REV 02   710-002845   HC0988            PPB Type 3
FPC 3            REV 01   710-004333   AY4706            FPC Type 3
  CPU            REV 06   710-001726   HE7916
  MMB 1          REV 03   710-004047   HG6326            MMB-288mbit
  PPB 0          REV 02   710-002845   HC0958            PPB Type 3
SPMB 0           REV 02   710-003229   HB1893
SPMB 1           REV 02   710-003229   HD5520
SIB 0            REV 02   710-005157   BC1509            SIB-I8-F16
SIB 1            REV 02   710-005157   BC1512            SIB-I8-F16
SIB 2            REV 02   710-005157   BC1494            SIB-I8-F16

jnxLEDLastChange

The object identifier for the jnxLEDLastChange object is {jnxBoxAnatomy 9}. This object indicates when the LED last changed state. Its value is 0 if the sysUpTime value is unknown, or if it already existed when the agent was active.

jnxLEDTable

The object identifier for the jnxLEDTable object is {jnxBoxAnatomy 10}. This object indicates the LED status of the router and lists the contents of an entry. Entries in the jnxLEDTable are represented by the jnxLEDEntry object, whose object identifier is {jnxLEDTable 1}.

The jnxLEDTable describes the components of the LED Box Indicators, whose elements are described as follows:

• jnxLEDAssociateTable—The associate table to which the entry is related, whose object identifier is {jnxLEDEntry 1}.
• jnxLEDAssociateIndex—The index of the subject in the associated table to which the entry is related, whose object identifier is {jnxLEDEntry 2}. The associate index is the index of the subject in the associated table, which returns you to the jnxContainersTable.
• jnxLEDL1Index—The level-one index of the associate table to which an entry is related, whose object identifier is {jnxLEDEntry 3}. It indicates the position of the component within the different levels of the containers. This value is 0 if the position is unavailable or not applicable.

  Note: MIBs start with a value of 1, while the physical count on the router starts with a value of 0. To find the actual location of a component within a router, you must subtract 1 from the L1, L2, or L3 index.

• jnxLEDL2Index—The level-two index of the associate table to which an entry is related, whose object identifier is {jnxLEDEntry 4}. It indicates the position of the component within the different levels of the containers. This value is 0 if the position is unavailable or not applicable.
• jnxLEDL3Index—The level-three index of the associate table to which an entry is related, whose object identifier is {jnxLEDEntry 5}. It indicates the position of the component within the different levels of the containers. This value is 0 if the position is unavailable or not applicable.
• jnxLEDOriginator—The chassis component that originated the update, whose object identifier is {jnxLEDEntry 6}.
• jnxLEDDescr—The name or detailed description of the entry, whose object identifier is {jnxLEDEntry 7}.
• jnxLEDState—The state of the LED indicator, whose object identifier is {jnxLEDEntry 8}. The state can be any of the following:
  • Amber—Alarm, offline, not working
  • Blue—Online as the active primary
  • Green—Working normally online as a standby backup if there is an active primary
  • Other—Unknown or unavailable
  • Red—Alert, component failed
  • Yellow—Alarm, warning
• jnxLEDStateOrdered—The state of the LED indicator, whose object identifier is {jnxLEDEntry 9}. jnxLEDStateOrdered provides the same information as jnxLEDState but lists the states in a different order. The state can be any of the following:
  • Blue—Online as the active primary
  • Green—Working normally online as a standby backup if there is an active primary
  • Amber—Alarm, offline, not working
  • Yellow—Alarm, warning
  • Red—Alert, component failed
  • Other—Unknown or unavailable

Table 48 through Table 50 provide examples of jnxLEDEntry objects. The following column headings for each table are abbreviated to correspond to the parts of the jnxLEDEntry objects:

• Associate table—jnxLEDAssociateTable
• Associate index—jnxLEDAssociateIndex
• L1 Index—jnxLEDL1Index
• L2 Index—jnxLEDL2Index
• L3 Index—jnxLEDL3Index
• Originator—jnxLEDOriginator
• Description—jnxLEDDescr
• State—jnxLEDState

Table 48 provides an example of jnxLEDEntry objects in the jnxLEDTable of an M20 router.

Table 48: jnxLEDEntry Objects in the jnxLEDTable of an M20 Router

Table 49 provides an example of jnxLEDEntry objects in the jnxLEDTable of a T640 router.

Table 49: jnxLEDEntry Objects in the jnxLEDTable of a T640 Router

Table 50 provides an example of jnxLEDEntry objects in the jnxLEDTable of a T320 router.

Table 50: jnxLEDEntry Objects in the jnxLEDTable of a T320 Router

jnxFilledLastChange

The object identifier for the jnxFilledLastChange object is {jnxBoxAnatomy 11}. This object indicates when the box filled status last changed. This variable is 0 if the sysUpTime value is unknown or it already existed when the agent was active.

jnxFilledTable

The object identifier for the jnxFilledTable object is {jnxBoxAnatomy 12}. This object indicates whether a specific container in the router is used (filled) or empty. This table is used for inventory and capacity planning.

Entries in the jnxFilledTable are represented by the jnxFilledEntry object, whose object identifier is {jnxFilledTable 1}.

The jnxFilledTable describes the status of specific containers whose component objects are described as follows:

• jnxFilledContainerIndex—The associated jnxContainersIndex in the jnxContainersTable, whose object identifier is {jnxFilledEntry 1}.
• jnxFilledL1Index—The level-one index of the container housing the entry, whose object identifier is {jnxFilledEntry 2}.
• jnxFilledL2Index—The level-two index of the container housing the entry, whose object identifier is {jnxFilledEntry 3}.
• jnxFilledL3Index—The level-three index of the container housing the entry, whose object identifier is {jnxFilledEntry 4}.
• jnxFilledDescr—The entry’s name or detailed description of the entry, whose object identifier is {jnxFilledEntry 5}.
• jnxFilledState—The entry’s state (filled or empty), whose object identifier is {jnxFilledEntry 6}.

Table 51 through Table 53 provide examples of jnxFilledEntry objects in the jnxFilledTable. The following column headings for each table are abbreviated to correspond to the parts of the jnxFilledEntry objects:

• Container index—jnxFilledContainerIndex
• L1—jnxFilledL1Index
• L2—jnxFilledL2Index
• L3—jnxFilledL3Index
• Description—jnxFilledDescr
• State—jnxFilledState

Table 51 provides an example of jnxFilledEntry objects in the jnxFilledTable of an M20 router.

Table 51: jnxFilledEntry Objects in the jnxFilledTable of an M20 Router