kpi for juniper devices

8/12/2019 KPI for Juniper Devices

1/92

Key Performance Indicators for Juniper Devices

Page 1 of 92 Partner Engineering Network Management

Key Performance Indicators forJuniper Devices

Version 2.2

Partner EngineeringFoundation Technologies-Network Management

Juniper Networks


2/92



Table of Contents

Key Performance Indicators for Juniper Devices ............................................................... 1

General Disclaimer ............................................................................................................. 4

1 Introduction ................................................................................................................. 52 Device Information ..................................................................................................... 5

2.1 Basic Information ................................................................................................. 52.2 Interface Information............................................................................................ 9

2.2.1 Determining all the interfaces on the device ............................................... 102.2.2 Logical and Physical Interfaces .................................................................. 122.2.3 Mapping the logical port to a physical port ................................................ 132.2.4 Determining the location of the Port on the device .................................... 142.2.5 Protocol Specific ......................................................................................... 24

2.2.5.1 BRIDGE Ports on JUNOS devices ...................................................... 24

2.2.5.2

Spanning Tree Ports on JUNOS devices ............................................. 26

2.2.5.3 RSTP Rapid Spanning Tree. .............................................................. 302.2.5.4 IPv4 Interfaces on JUNOS devices ..................................................... 42

3 Key Performance Indicators Devices ..................................................................... 433.1 CPU Utilization .................................................................................................. 443.2 Memory Utilization ............................................................................................ 443.3 Disk Utilization .................................................................................................. 443.4 Operating Temperature ...................................................................................... 45

4 Key Performance Indicators - Interfaces .................................................................. 454.1 Interface Utilization............................................................................................ 464.2 Interface related counters ................................................................................... 46

5 Key Performance Indicators - Class of Service ........................................................ 535.1

Inbound Traffic per Class ................................................................................... 54

5.2 Output bytes per queue ....................................................................................... 545.3 Calculating the Dropped Traffic ........................................................................ 545.4 Tail Drop Packets ............................................................................................... 545.5 Red Drop Packets ............................................................................................... 555.6 Counters for measuring CoS .............................................................................. 55

6 Key Performance Indicators - Routing Protocols ..................................................... 716.1 Counters for Routing Protocols .......................................................................... 72

6.1.1 BGP Counters ............................................................................................. 736.1.2 OSPF Counters............................................................................................ 74

7 Key Performance Indicators Frame Relay ............................................................. 757.1

Frame Relay MIB Objects.................................................................................. 75

7.2 Frame Relay interface and subinterface statistics .............................................. 767.3 Circuit Statistics ................................................................................................. 77

8 Key Performance Indicators ATM ......................................................................... 788.1 ATM state information ....................................................................................... 788.2 ATM statistics for the interface .......................................................................... 788.3 Error statistics ..................................................................................................... 79


3/92



8.4 Error statistics (SAR) ......................................................................................... 808.5 ATM related MIB Objects ................................................................................. 80

9 Key Performance Indicators for MPLS .................................................................... 8310 Key Performance Indicator for VPN ........................................................................ 8311 Key Performance Indicators for IP Sec .................................................................... 84

11.1

Key Indicators for IP Sec ................................................................................ 84

11.2 IP Sec Counters .............................................................................................. 8512 Key Performance Indicators for Pseudowires ........................................................... 87

12.1 Pseudowires Indicators ................................................................................... 8712.2 VPN and Pseudowire related Counters .......................................................... 87

13 Real Time Performance Management RPM .......................................................... 8813.1 RPM Indicators ............................................................................................... 8813.2 RPM related counters ..................................................................................... 89

14 Using the Juniper Utility MIB .................................................................................. 9015 Using Accounting Profiles ........................................................................................ 92


4/92



General DisclaimerAlthough Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks

does not warrant or guarantee the accuracy of the information provided herein. Juniper Networks maychange the programs or products mentioned at any time without prior notice. Mention of non-JuniperNetworks products or services is for information purposes only and constitutes neither an endorsement nora recommendation of such products or services or of any company that develops or sells such products orservices.

ALL INFORMATION PROVIDED IN THIS GUIDE IS PROVIDED AS IS, WITH ALL FAULTS,AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED ORSTATUTORY. JUNIPER NETWORKS AND ITS SUPPLIERS HEREBY DISCLAIM ALLWARRANTIES RELATED TO THIS GUIDE AND THE INFORMATION CONTAINED HEREIN,WHETHER EXPRESSED OR IMPLIED OR STATUTORY INCLUDING, WITHOUT LIMITATION,THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT, OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADEPRACTICE.

JUNIPER NETWORKS AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR REVENUES, COSTS OF REPLACEMENT GOODS ORSERVICES, LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OF THE GUIDE OR ANYJUNIPER NETWORKS PRODUCT OR SERVICE, OR DAMAGES RESULTING FROM USE OF ORRELIANCE ON THE INFORMATION PROVIDED IN THIS GUIDE, EVEN IF JUNIPER NETWORKSOR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Many of the Juniper Networks products and services identified in this guide are provided with, and subjectto, written software licenses and limited warranties. Those licenses and warranties provide the purchasersof those products with certain rights. Nothing in this guide shall be deemed to expand, alter, or modify anywarranty or license or any other agreement provided by Juniper Networks with any Juniper Networksproduct, or to create any new or additional warranties or licenses.


5/92



1 Introduction

This document describes the MIB OIDs that can be polled on Juniper Devices to describeperformance of these devices. The document lists all the OIDs that act as KeyPerformance Indicators for any JUNOS Device. The document also lists the indicators interms of solutions like Carrier Ethernet VPNs and Mobile Backhaul.

The Devices that are considered in the document are as follows:

T Series

MX Series

M Series

EX Series

J Series

SRX Series BX Series (BX 7000 running BX OS)

Note that the Key Performance Indicators related to the Device and Interface are commonacross all Juniper platforms. The indicators related to CoS, ATM, Frame Relay and IPSec depend on the platforms.

Some of the basic performance indicators mentioned in the document directly map to anOID in the Junipers Enterprise specific MIB or an OID in one of the Standard MIBs.

2 Device Information

2.1 Basic Information

The basic device indicators are classified in to basic device information like the SystemDetails, Details about the Device Inventory and the CPU and the Temperature readingsfor those Inventory Items. Also included are High Availability features related data likeVRRP and Virtual Chassis related statistics for EX Series.

The below mentioned System Identification identifiers help in indentifying the type

Juniper Device, and its name.


6/92



System Identification (from RFC 1213 MIB 2 System Group)

sysDescr(.1.3.6.1.2.1.1.1.0)

sysObjectID(.1.3.6.1.2.1.1.2.0)

sysName(.1.3.6.1.2.1.1.5.0)

The information related to CPU, Memory and the Operating temperature values for thesystem can be obtained using the following counters. This provides the operating statusof subjects of interest in the device.

The Juniper MIB (Juniper Enterprise Specific MIB: Chassis MIB jnx-chassis) providesgeneric information about the device like device description, and the operating status ofthe device. The operating status information includes the operating state of each item onthe device, namely the box contents. The box contents include the mid-plane, PowerSupply, temperature sensor, Fan Tray, Fan, FPC, PIC and the Routing Engine (RE).

One can obtain the CPU and the Memory information about the contents in the box byquerying the instances of the following OIDs.

CPU & Memory Information

jnxOperatingTemp(.1.3.6.1.4.1.2636.3.1.13.1.7)

jnxOperatingCPU(.1.3.6.1.4.1.2636.3.1.13.1.8)

jnxOperatingBuffer(.1.3.6.1.4.1.2636.3.1.13.1.11)

jnxOperatingState(.1.3.6.1.4.1.2636.3.1.13.1.6) hrStorageDescr(.1.3.6.1.2.1.25.2.3.1.3)

hrStorageAllocationUnits(.1.3.6.1.2.1.25.2.3.1.4)

hrStorageSize(.1.3.6.1.2.1.25.2.3.1.5)hrStorageUsed(.1.3.6.1.2.1.25.2.3.1.6)

hrStorageAllocationFailures(.1.3.6.1.2.1.25.2.3.1.7)

For example, the below picture provides a screenshot of the CPU, Memory, OperatingTemperature and Operating state of each item on a M7i Router.


7/92



The hardware inventory and the associated details such as the temperature details can befetched using the following OIDs.

Hardware Inventory

jnxFruName(.1.3.6.1.4.1.2636.3.1.15.1.5.9.1)jnxFruType(.1.3.6.1.4.1.2636.3.1.15.1.6.9.1)

jnxFruSlot(.1.3.6.1.4.1.2636.3.1.15.1.7.9.1)

jnxFruState.9.1(.1.3.6.1.4.1.2636.3.1.15.1.8.9.1)

jnxFruTemp.9.1(.1.3.6.1.4.1.2636.3.1.15.1.9.9.1 )

jnxFruOfflineReason.9.1(.1.3.6.1.4.1.2636.3.1.15.1.10.9.1)

jnxFruLastPowerOff.9.1(.1.3.6.1.4.1.2636.3.1.15.1.11.9.1 )

jnxFruLastPowerOn.9.1(.1.3.6.1.4.1.2636.3.1.15.1.12.9.1)

jnxFruPowerUpTime.9.1(.1.3.6.1.4.1.2636.3.1.15.1.13.9.1)

Note that BX 7000 (BX Series) Devices run BXOS operating system and have a differentMIB to fetch the basic device details.

jnxProcessCount(.1.3.6.1.4.1.2636.3.50.5.1.1.1.1)jnxProcessSleeping(.1.3.6.1.4.1.2636.3.50.5.1.1.1.2)jnxProcessRunning .(.1.3.6.1.4.1.2636.3.50.5.1.1.1.3)jnxProcessStopped (.1.3.6.1.4.1.2636.3.50.5.1.1.1.4)jnxProcessZombie(.1.3.6.1.4.1.2636.3.50.5.1.1.1.5)


8/92



jnxProcessTable (.1.3.6.1.4.1.2636.3.50.5.1.1.1.6)jnxSyrahMemAvail(.1.3.6.1.4.1.2636.3.50.5.1.1.2.1)jnxSyrahMemUsed (.1.3.6.1.4.1.2636.3.50.5.1.1.2.2)

jnxSyrahMemFree (.1.3.6.1.4.1.2636.3.50.5.1.1.2.3)jnxSyrahMemShared(.1.3.6.1.4.1.2636.3.50.5.1.1.2.4)jnxSyrahMemBuffered (.1.3.6.1.4.1.2636.3.50.5.1.1.2.5)jnxSyrahMemCached (.1.3.6.1.4.1.2636.3.50.5.1.1.2.6)jnxSyrahSwapAvail(.1.3.6.1.4.1.2636.3.50.5.1.1.2.7)jnxSyrahSwapUsed (.1.3.6.1.4.1.2636.3.50.5.1.1.2.8)jnxSyrahSwapfree (.1.3.6.1.4.1.2636.3.50.5.1.1.2.9)jnxSyrahCpuUser(.1.3.6.1.4.1.2636.3.50.5.1.1.3.1)jnxSyrahCpuSystem (.1.3.6.1.4.1.2636.3.50.5.1.1.3.2)jnxSyrahCpuIdle (.1.3.6.1.4.1.2636.3.50.5.1.1.3.3)jnxSyrahCpuNice (.1.3.6.1.4.1.2636.3.50.5.1.1.3.4)

jnxSyrahCpuIOWait(.1.3.6.1.4.1.2636.3.50.5.1.1.3.5)jnxSyrahCpuUsed (.1.3.6.1.4.1.2636.3.50.5.1.1.3.6)

High Availability - Virtual Chassis Information

jnxVirtualChassisMemberId(.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.1)

jnxVirtualChassisMemberSerialnumber (.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.2)

jnxVirtualChassisMemberRole (.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.3)


9/92



jnxVirtualChassisMemberMacAddBase(.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.1)

jnxVirtualChassisMemberSWVersion(.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.1)

jnxVirtualChassisMemberPriority (.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.1)

jnxVirtualChassisMemberUptime (.1.3.6.1.4.1.2636.3.40.1.4.1.1.1.1)jnxVirtualChassisFpcId

jnxVirtualChassisPortName

jnxVirtualChassisPortAdminStatus

jnxVirtualChassisPortOperStatus

High Availability VRRP

1.3.6.1.2.1.68.2.1 (vrrpRouterChecksumErrors)1.3.6.1.2.1.68.2.2 (vrrpRouterVersionErrors)1.3.6.1.2.1.68.2.3 (vrrpRouterVrIdErrors)1.3.6.1.2.1.68.2.4.1.1 (vrrpStatsBecomeMaster)1.3.6.1.2.1.68.2.4.1.2 (vrrpStatsAdvertiseRcvd)

1.3.6.1.2.1.68.2.4.1.3 (vrrpStatsAdvertiseIntervalErrors)1.3.6.1.2.1.68.2.4.1.4 (vrrpStatsAuthFailures)1.3.6.1.2.1.68.2.4.1.5 (vrrpStatsIpTtlErrors)1.3.6.1.2.1.68.2.4.1.6 (vrrpStatsPriorityZeroPktsRcvd)1.3.6.1.2.1.68.2.4.1.7 (vrrpStatsPriorityZeroPktsSent)1.3.6.1.2.1.68.2.4.1.8 (vrrpStatsInvalidTypePktsRcvd)1.3.6.1.2.1.68.2.4.1.9 (vrrpStatsAddressListErrors)1.3.6.1.2.1.68.2.4.1.10 (vrrpStatsInvalidAuthType)1.3.6.1.2.1.68.2.4.1.11 (vrrpStatsAuthTypeMismatch)1.3.6.1.2.1.68.2.4.1.12 (vrrpStatsPacketLengthErrors)

2.2 Interface Information

The following gives instructions of discovering interfaces on JUNOS based Juniperdevices. This gives instructions for discovering Physical and logical interfaces in details.The Interface family and interface address depends on what protocol is configured andused. This document gives examples for L2 switching interfaces and IPv4 addresses asexamples for the same. Others protocols can be deduced similarly.

This is list of all the tables that needs to be queried. The NM system can chose thesequence depending on their algorithm and the MIB OID.


10/92



Query the ifTable(RFC 2863). This gives all the interfaces on the devices physical and logical interfaces.

Query the ifChassisTable( Juniper specific jnx-if-extensions.mib) to find out the

location and the type of the interface (physical vs logical) Query the Juniper Chassis MIB for all the physical Entities including the PICs

and Cards. This is required for finding out the ports belonging to a Card.

Query for ifStackTable (RFC 2863) to find out the physical interfacescorresponding the actual logical ports

Query for protocol specific tables to find out the ports. For example:dot1dBasePort for Bridge ports, dot1dStpTable for STP ports and ipAddrTablefor IPv4 based ports.

2.2.1 Determining all the interfaces on the device

This can be done using the ifTable. ifTable gives all the interfaces on the device. Usingthe ifType , one can determine what interface type it is

Example:

regress@EX4200-2> show snmp mib walk ifDescrifDescr.4 = lsiifDescr.5 = dscifDescr.6 = lo0

ifDescr.7 = tapifDescr.8 = greifDescr.9 = ipipifDescr.10 = pimeifDescr.11 = pimdifDescr.12 = mtunifDescr.33 = me0-----Management portifDescr.34 = me0.0ifDescr.35 = vmeifDescr.36 = vme.0ifDescr.37 = bme0

ifDescr.38 = bme0.32768ifDescr.49 = vcp-0ifDescr.50 = vcp-0.32768ifDescr.51 = vcp-1ifDescr.52 = vcp-1.32768ifDescr.116 = ge-0/0/0ifDescr.117 = ge-0/0/1Find ifType with ifIndex 117ifDescr.118 = ge-0/0/10


11/92



ifDescr.119 = ge-0/0/11ifDescr.120 = ge-0/0/12ifDescr.121 = ge-0/0/13

ifDescr.122 = ge-0/0/14ifDescr.123 = ge-0/0/15ifDescr.124 = ge-0/0/16ifDescr.125 = ge-0/0/17ifDescr.126 = ge-0/0/18ifDescr.127 = ge-0/0/19ifDescr.128 = ge-0/0/2ifDescr.129 = ge-0/0/20ifDescr.130 = ge-0/0/21ifDescr.131 = ge-0/0/22ifDescr.132 = ge-0/0/23

ifDescr.133 = ge-0/0/3ifDescr.134 = ge-0/0/4ifDescr.135 = ge-0/0/5ifDescr.136 = ge-0/0/6ifDescr.137 = ge-0/0/7ifDescr.138 = ge-0/0/8ifDescr.139 = ge-0/0/9ifDescr.166 = vlanifDescr.193 = ge-0/0/0.0ifDescr.194 = ge-0/0/1.0-Find ifType with ifIndex 194ifDescr.195 = ge-0/0/2.0ifDescr.196 = ge-0/0/3.0ifDescr.197 = ge-0/0/4.0ifDescr.198 = ge-0/0/5.0ifDescr.200 = ge-0/0/7.0ifDescr.202 = ge-0/0/9.0ifDescr.203 = ge-0/0/10.0ifDescr.204 = ge-0/0/11.0ifDescr.205 = ge-0/0/12.0ifDescr.206 = ge-0/0/13.0ifDescr.207 = ge-0/0/15.0ifDescr.208 = ge-0/0/16.0ifDescr.209 = ge-0/0/17.0ifDescr.210 = ge-0/0/18.0ifDescr.211 = ge-0/0/19.0ifDescr.212 = ge-0/0/20.0ifDescr.213 = ge-0/0/21.0ifDescr.214 = ge-0/0/22.0ifDescr.215 = ge-0/0/23.0ifDescr.219 = ge-0/0/16.10


12/92



ifDescr.220 = ge-0/0/17.20ifDescr.221 = ge-0/0/14.0

ifType of ifIndex 117 is 6 which is ethernetCsmacd(IANAifType)regress@EX4200-2> show snmp mib get ifType.117

ifType.117 = 6

ifType of ifIndex 194 is 53 which is propVirtual(IANAifType)

regress@EX4200-2> show snmp mib get ifType.194ifType.194 = 53

Snapshot of a IF MIB Table from a SNMP tool

2.2.2 Logical and Physical Interfaces

To know if an interface is a logical or physical, use the ifChassisTable and get the valueof the ifChassisLogicalUnit. If the value is 1 then it is Logical else its physical This Tableis indexed by ifIndex of the interfaces, You can see below that for IfIndex 194, theifChassisLogicalUnit is 1 meaning that this is a logical interface whereas with 117 is 0.

regress@EX4200-2> show snmp mib get ifChassisLogicalUnit.194ifChassisLogicalUnit.194 = 1----------------------------------------Logical Port


13/92



{master:0}regress@EX4200-2> show snmp mib get ifChassisLogicalUnit.117ifChassisLogicalUnit.117 = 0-------------------------------------------Physical port

regress@EX4200-2> show snmp mib get ifDescr.194ifDescr.194 = ge-0/0/1.0----------------------------------------Logical Port

{master:0}regress@EX4200-2> show snmp mib get ifDescr.117ifDescr.117 = ge-0/0/1-------------------------------------------Physical port

2.2.3 Mapping the logical port to a physical port

To find out the physical port corresponding to the logical port, you need use the ifTable(MIB 2 RFC 1213) and the ifStackTable (RFC 2863).

This can be done using the ifStackTable as follows.

To know if an interface is a logical or physical, use the ifChassisTable and get the valueof the ifChassisLogicalUnit. This Table is indexed by ifIndex of the interfaces,You can see below that for IfIndex 194, the ifChassisLogicalUnit is 1 meaning that thisis a logical interface.Example:

ifChassisLogicalUnit.194 = 1

Get the logical interface name (ifDescr of the interface) for the corresponding ifIndex

Get the corresponding ifDescr for the IfIndex value.regress@Ex3200-test> show snmp mib get ifDescr. 193ifDescr. 194 = ge-0/0/1.0Note that this corresponds to the logical interface ge-0/0/1.0

Search for the ifIndex value in the ifStackTable.ifStackStatus.Now search for the ifStackTable.ifStackStatus value whose ifHigherLayerIndex matches

the ifIndex value of the logical interface.Now get the ifLowerlayerIndex value corresponding to this entry in the ifStackTable.Now search for the ifDescr value corresponding to the ifIndex value equal to theifLowerLayerIndex.This value will give you the ifDescr of the physical port associated with the logical port.


14/92



Now walk the ifStackTable, and get the ifStackStatus whose ifHigherIndex valuematches the IfIndex valueThat is get the ifStackStatus value whose ifHigherIndex value is 194.

regress@Ex3200-test> show snmp mib get ifStackStatus. 194.117ifStackStatus. 194.117 = 1

Now get the corresponding ifLowerIfIndex value. This value as you can see is 117.

Now get the corresponding ifDescr for the ifIndex equal to the ifLowerIfIndex value.That is, get the ifDescr corresponding to the ifIndex 117. This gives you the physical portcorresponding to the logical port.

regress@Ex3200-test> show snmp mib get ifDescr.117

ifDescr.117 = ge-0/0/1

Hence, the physical port corresponding to the logical port ge-0/0/1.0 is ge-0/0/1.

Repeat the above for each entry (ifIndex) in the ifChassisTable which has theifChassisLogicalUnit entry equal to 1.

This approach can be used for any logical interface to determine the correspondingphysical interface on any of the Juniper Platforms

2.2.4 Determining the location of the Port on the device

Each interface on JUNOS devices belong to a Chassis component, it can be the deviceitself, PIC , FPC. The JUNOS has a specific Anatomy to determine the location of eachand every component on the device like Fan, Card , Power Supply etc. JUNOS devicessupport Juniper specific enterprise MIB called Chassis MIB to find out the physicalcomponents on the device.This is similar to the RFC 2737 ENTITY MIB to determine the entities.

Please refer to http://www.juniper.net/techpubs/software/junos/junos94/swconfig-net-mgmt/interpreting-the-enterprise-specific-chassis-mibs.html for details of all the Juniper

devices.Each Chassis component has a unique index

NM systems need to discover the Chassis components using the jnx-chassis.mib and theifChassisTable from the jnx-if-extensions.mib. Using the ifChassisPicIndex one candetermine the PIC to which the port belongs to


15/92



The ifChassisTable gives the index or indices for the Chassis MIB tables. This is theinstance index which keys into the jnxContentsTable in Chassis MIB.For example, itcould return an octet string of 8.1.2.0' - meaning a PIC ('8', first digit) at FPC slot 0 ('1-

1', second digit minus one if nonzero) PIC number 1 ('2-1', third digit minus one ifnonzero) port number whatever (fourth digit currently unused) - which in turncould be plugged in by NMS directly after any MIB objects in the jnxContentsTable, say'jnxContentsDescr.8.1.2.0', so NMS could get that PIC object for the specified interface.This object is valid only for those interfaces having real and physical PIC cards.Otherwise, it returns an octet string of four zeros '0.0.0.0.'

Here is an example,The following shows an M-series router with two FPCs which are Flexible PICconcentrators which hold one or more PICs(cards). Please see the FPC and PICs

highlighted.regress@M7i-1> show chassis hardwareHardware inventory:Item Version Part number Serial number DescriptionChassis J1747 M7iMidplane REV 05 710-008761 VF1791 M7i MidplanePower Supply 0 Rev 08 740-008537 UK58001 AC Power SupplyRouting Engine REV 02 740-021833 9009005164 RE-5.0CFEB REV 10 750-010463 VD3039 Internet Processor IIFPC 0 E-FPCPIC 0 REV 12 750-012838 VE8559 4x 1GE(LAN), IQ2Xcvr 0 REV 01 740-011783 PCQ08MC SFP-LX10

PIC 1 REV 12 750-012838 VE8543 4x 1GE(LAN), IQ2Xcvr 0 REV 01 740-011783 PCQ08LM SFP-LX10Xcvr 2 REV 01 740-011614 AC0810S00T8 SFP-LX10

FPC 1 E-FPCPIC 2 BUILTIN BUILTIN 1x TunnelPIC 3 REV 09 750-009099 VC5207 1x G/E, 1000 BASE

Fan Tray Rear Fan Tray

Lets take a port on the device , ifDescr.138 = ge-0/1/2.0 which is a logical interface asseen in ifChassisLogicalUnit.138 = 1. Let us first deduce the Physical Port of this logicalport as described previously.


16/92



MIB Value from the device M7i displayedabove

Description

ifStackStatus.138.125 = 1 IfIndex 138 is on ifIndex 125

regress@M7i-1> show snmp mib getifDescr.125ifDescr.125 = ge-0/1/2

IFIndex 125 refers to ge-0/1/2, which is thephysical port housing the logical port ge-0/1/2.0

ifChassisFpc.125 = 1

ifChassisFpc.138 = 1

The number of the FPC card on which theinterfaceis located in the chassis. It is the chassisslotin which the FPC card is installed for thespecifiedinterface.

Although the number is labeled from 0 andup in thechassis, the return value for this objectalways startsfrom 1 according to Network Managementconvention. Therefore, a value of zeromeans there is no real or physical FPCassociated with the specified interface.NM Systems need to subtract 1 from thevalue here.

So Port 125 and 138 are on FPC 0.


17/92



ifChassisPic.125 = 2

ifChassisPic.128 = 2

The number of the PIC card on which theinterfaceis located in the chassis. It is the PIC

locationon the FPC card for the specified interface.

Although the number is labeled from 0 andup in thechassis, the return value for this objectalways startsfrom 1 according to Network Managementconvention. Therefore, a value of zeromeans there is no real or physical PICassociated with the specified interface.

NM Systems need to subtract 1 from thevalue here.So Port 125 and 138 are on PIC 1.

ifChassisPort.125 = 3

ifChassisPort.138 = 3

The number of the port on the PIC card onwhich theinterface is located in the chassis. It is theportnumber on the PIC card for the specifiedinterface.

NM Systems need to subtract 1 from thevalue here.The port location here is 2.

ifChassisChannel.125 = 0

ifChassisChannel.138 = 0

The channel identifier for the specifiedinterfaceif and only if it is part of a channelizedinterface.This is mostly for OC3 channelizedinterfaces.

Its not applicable in this example.


18/92



ifChassisPicIndex.125 = 08 01 02 00

ifChassisPicIndex.138 = 08 01 02 00

The indexes for the Chassis MIB tables.This is the instance index that keys intojnxContentsTable in the Chassis MIB.

For example, the octet string of 8.1.2.0means a PIC ( 8& first digit) at FPC slot0 (11 , second digit minus one ifnonzero) PIC number 1 (21 , third digit)minus one if nonzero port number,whatever (fourth digit currently unused). Inturn, this PIC index can be plugged in bythe NMS directly after any MIB objects inthe jnxContentsTable obtain that PICobject for the specified interface. Thisobject is valid only for interfaces having

real and physical PIC cards. Otherwise, itreturns an octet string 0.0.0.0.

Now, let us use the jnxContentsTable and jnxContainers Tables to locate the FPCs andthe Cards. We now know that port ge-0/1/2 is on FPC 0 and PIC 1 and port position is 2.The following only shows relevant MIB attributes for simplicity.

MIB Value from the device M7i displayedabove

Description

jnxContainersTable

jnxBoxClass.0 = jnxProductLineM7i.0

jnxBoxDescr.0 = Juniper M7i InternetBackbone RouterjnxBoxSerialNo.0 = J1747jnxBoxInstalled.0 = 208876600

These variables give the Product Line of

Juniper which is M7i and Box serialnumber with Box install date.

jnxContainersIndex.1 = 1jnxContainersIndex.2 = 2jnxContainersIndex.4 = 4jnxContainersIndex.6 = 6jnxContainersIndex.7 = 7jnxContainersIndex.8 = 8jnxContainersIndex.9 = 9

jnxContainersIndex gives the Index foreach component


19/92



jnxContainersView.1 = 1jnxContainersView.2 = 2jnxContainersView.4 = 16

jnxContainersView.6 = 2jnxContainersView.7 = 1jnxContainersView.8 = 1jnxContainersView.9 = 1

The view(s) from which the specificcontainer appears.The various values representing the bit

positionsand its corresponding views are:1 front2 rear4 top8 bottom16 leftHandSide32 rightHandSide

jnxContainersLevel.1 = 0jnxContainersLevel.2 = 1

jnxContainersLevel.4 = 1jnxContainersLevel.6 = 1jnxContainersLevel.7 = 1jnxContainersLevel.8 = 2jnxContainersLevel.9 = 1

The abstraction level of the box or chassis.It is enumerated from the outside to the

inside, from the outer layer to the innerlayerFor example, top level (i.e. level 0)refers to chassis frame, level 1 FPC slotwithin chassis frame, level 2 PIC spacewithin FPC slot.

jnxContainersWithin.1 = 0jnxContainersWithin.2 = 1jnxContainersWithin.4 = 1jnxContainersWithin.6 = 1jnxContainersWithin.7 = 1jnxContainersWithin.8 = 7

jnxContainersWithin.9 = 1

The container housing the entry at the next-higher level of the jnxContainersEntryobject, whose object identifier is{jnxContainersEntry 4}.For example, the within value forjnxMediaCardSpacePIC.0 is 7. Because the

jnxM7iSlotFPC.0 retains an index value of7, the FPC houses the PIC.

jnxContainersType.1 = jnxChassisM7i.0jnxContainersType.2 = jnxM7iSlotPower.0jnxContainersType.4 = jnxM7iSlotFan.0jnxContainersType.6 = jnxM7iSlotCFEB.0jnxContainersType.7 = jnxM7iSlotFPC.0jnxContainersType.8 =jnxM7iMediaCardSpacePIC.0jnxContainersType.9 = jnxM7iSlotRE.0

The type of this container.This says what the Container Type is for agiven Container Index. For example:Container Index 8 refers tojnxM7iMediaCardSpacePIC.0 which refersto the PICs on M7i.

jnxContainersDescr.1 = chassis framejnxContainersDescr.2 = Power Supply slotjnxContainersDescr.4 = FAN slotjnxContainersDescr.6 = CFEB slotjnxContainersDescr.7 = FPC slotjnxContainersDescr.8 = PIC slotjnxContainersDescr.9 = Routing Engine slot

The name or detailed description of thissubject.

Take notice, Container index is for FPCand 8 for PIC here.


20/92


21/92



jnxContentsL1Index.7.1.0.0 = 1jnxContentsL1Index.7.1.1.0 = 1

jnxContentsL1Index.7.2.0.0 = 2


The level-one index of the containerhousing the component, whose objectidentifier is {jnxContentsEntry 2}. It

indicates the position of the componentwithin different levels of the containers.This value is 0 if the position is unavailableor not applicable.

MIBs start with a value of 1, whereas thephysical count on the router starts with avalue of 0. To find the actual location of acomponent within a router, you mustsubtract 1 from the L1, L2, or L3 index.

So Level 1 Index for 7.1.0.0 is 0 (1-1) andthe Level for Container Type 7(FPC) isjnxContainersLevel.7 = 1 which meansFPC is at Level 1 and the L1 Index hererefers to the FPC position itself. Therefore ,7.1.0.0 refers to FPC 0. Similarly, 7.2.0.0refers to FPC 1.

Now, the L1 Index forjnxContentsL1Index.8.1.2.0 = 1 i.e. 0 (1-1).

The jnxContainersLevel.8=2 which meansthe component represented by index 8.1.2.0is at Level 2. Now, Level 1 index for thiscomponent is 0.To find out which is the Level 1component housing this Level 2, use thejnxContainersWithin.8 = 7 (see above).This indicates that Container Index of the 7(FPC) houses Container index 8(PIC).Therefore , look for a jnxContentsTableentry with index container index 7 and theLevel 1 index 1.There are two such entries7.1.0.07.1.1.0Which is the correct one will be clarifiednext step


22/92





The level-two index of the containerhousing the component, whose object

identifier is {jnxContentsEntry 3}. Itindicates the position of the componentwithin different levels of the containers.This value is 0 if the position is unavailableor not applicable.

The L2 Index of 7.1.0.0 is 0 which is notapplicable.

The L2 position of 8.1.2.0 is 1 (2-1) andthe jnxContainersLevel.8=2 which means

any component with starting index 8(PIC)is at Level 2 therefore L2 Index representsthe position of the component itself. Socomponent represented by 8.1.2.0 is PIC 1.This also means one of the L1 componentshouses this L2 component. As seen above,8.1.2.0 is housed by container index 7 andL1 Index 1, we got 7.1.0.0 and 7.1.1.0.Now, the L2 index of 7.1.1.0 is 1 whichmeans this component has a Level 1 Indexof 1 which is position 0 (1-1 ;FPC 0) and

level 2 index of 1 which is position 0(1-1)within the FPC(part of the FPC). Here youshould note that jnxContainersLevel.7 = 1which is any component with index 7 is atlevel 1(FPC) itself, so here L2 Index refersto something within(part of) the L1component.

Conclusion is,If jnxContainersLevel=1 and L2 Index hasa non zero value then the component is partof the Level 1 component represented byL1 Index. e.g. 7.1.1.0If jnxContainersLevel=2 and L2 Index hasa non zero value then the component isHoused by a Level 1 componentrepresented by a L1 Index value. E.g.8.1.2.0Also, the entry representing the L1


23/92



component by itself and housing other L2components will have the L2 Index of 0always. E.g. 7.1.0.0



The level three index of the containerhousing this subject. Zero if unavailable

or inapplicable.

jnxContentsType.7.1.0.0 = jnxM7iFPC.0

jnxContentsType.7.1.1.0 =jnxChassisTempSensor.0jnxContentsType.8.1.2.0 =jnxPicType1IQ24X1GE

The type of this subject. So 7.1.0.0represents a FPC , 7.1.1.0 represents theTemperature sensor of the FPC and 8.1.2.0is a PIC of type IQ2 4X1GE

jnxContentsDescr.7.1.0.0 = FPC: @ 0/*/*

jnxContentsDescr.7.1.1.0 = FPC: @ 0/*/*temp sensor

jnxContentsDescr.8.1.1.0 = PIC: 4x1GE(LAN), IQ2 @ 0/0/*jnxContentsDescr.8.1.2.0 = PIC: 4x1GE(LAN), IQ2 @ 0/1/*

The name or detailed description of thissubject.

jnxContentsChassisId.7.1.1.0 = 2

jnxContentsChassisId.8.1.1.0 = 2jnxContentsChassisId.8.1.2.0 = 2

Identifies the chassis on which the contents

of thisrow exists.

The other attributes are left out as it is not relevant for port identification

So, we now know ge-0/1/2 is part of FPC 0 and PIC 1 and port 2. We know the 8.1.2.0 ishoused in 7.1.0.0 and we have detailed descriptions of the component as below


24/92



2.2.5 Protocol Specific

This section covers the protocol\family specific examples. This mainly covers Bridgeinterfaces and STP interfaces with IPv4 interfaces.

2.2.5.1BRIDGE Ports on JUNOS devices

The JUNIPER EX and MX devices support Switching. As per IEEE802.1D , the RFC4188 MIBS should represent the Switching ports.

The dot1dBase Table will give all the Bridge ports on the device.Using the dot1dBasePortIfIndex, the description and ifEntry of the port can bedetermined as belowdot1dBaseBridgeAddress.0 = 00 1f 12 32 b7 80dot1dBaseNumPorts.0 = 21

dot1dBaseType.0 = 2dot1dBasePort.34 = 34dot1dBasePort.193 = 193dot1dBasePort.194 = 194dot1dBasePort.195 = 195dot1dBasePort.196 = 196dot1dBasePort.197 = 197dot1dBasePort.198 = 198

FPC (7.1.0.0): FPC: @0/*/*

PIC 1( 8.1.2.0): = PIC: 4x1GE(LAN), IQ2 @ 0/0/*

ge-0/1/2

ge-0/1/2.0


25/92


26/92



Note that this corresponds to the logical interface ge-0/0/0.0 Therefore, for EX, by defaultyou will get only the logical interfaces from Bridge MIB tables.

You can find the Physical port of the corresponding logical port as described in above

sections.

NOTE: JUNIPER MX devices represent the dot1dBase Ports which are Physical portsand NOT logical.

regress@MX240-2> show snmp mib walk dot1dBasedot1dBaseBridgeAddress.0 = 00 21 59 ad 57 d0dot1dBasePort.41 = 41dot1dBasePort.101 = 101dot1dBasePort.102 = 102

dot1dBasePortIfIndex.41 = 117-

IfIndex of Bridge Port 41 is 117dot1dBasePortIfIndex.101 = 189dot1dBasePortIfIndex.102 = 190dot1dBasePortCircuit.41 = 0.0dot1dBasePortCircuit.101 = 0.0dot1dBasePortCircuit.102 = 0.0dot1dBasePortDelayExceededDiscards.41 = 0dot1dBasePortDelayExceededDiscards.101 = 0dot1dBasePortDelayExceededDiscards.102 = 0dot1dBasePortMtuExceededDiscards.41 = 0dot1dBasePortMtuExceededDiscards.101 = 0dot1dBasePortMtuExceededDiscards.102 = 0

regress@MX240-2> show snmp mib get ifChassisLogicalUnit.117ifChassisLogicalUnit.117 = 0 -Not Logical. This is a Physical Port.

regress@MX240-2> show snmp mib get ifDescr.117ifDescr.117 = ge-1/0/0

The port ge-1\0\0 is a Bridge port participating in Switching on MX.

2.2.5.2Spanning Tree Ports on JUNOS devices

The ports configured for STP, RSTP and VSTP are represented by dot1dStp Table whichin turn refers to dot1dBase Table as in RFC 4188.

Please noteVSTP is applicable ONLY FOR MX platforms. VSTP on EX is not supported.


27/92



Querying for VSTP requires a different community string from SNMP. :: VLAN-ID@ communitystring.MX and EX support RFC 4318 for RSST Ports.

MSTP is supported by Juniper Networks Enterprise-Specific Multiple Instance MultipleSpanning Tree MIB (mib-jnx-mimstp.txt)Supports 802.1s (2002) for MSTP.All Juniper Switching devices uses IEEE802.1D-2004 version.MX supports the Bridge dot1dBase tables starting JUNOS 9.4R2 and also in 9.2R4.EX support for correct Bridge MIB is from JUNOS 9.2R3. The port identifier and somebug fixes have been done for STP tables from JUNOS 9.5 which is captured here.

2.2.5.2.1STP Spanning Tree

The following is an example from EX4200 device

regress@EX4200-2# run show snmp mib walk dot1dStpVersiondot1dStpVersion.0 = 0----------------------STP compatible protocol

regress@EX4200-2> show snmp mib walk dot1dStpdot1dStpProtocolSpecification.0 = 3dot1dStpPriority.0 = 8192dot1dStpTimeSinceTopologyChange.0 = 7763200dot1dStpTopChanges.0 = 2922dot1dStpDesignatedRoot.0 = 20 00 00 1f 12 32 b7 80dot1dStpRootCost.0 = 0dot1dStpRootPort.0 = 0dot1dStpMaxAge.0 = 2000dot1dStpHelloTime.0 = 200dot1dStpHoldTime.0 = 100dot1dStpForwardDelay.0 = 1500dot1dStpBridgeMaxAge.0 = 2000dot1dStpBridgeHelloTime.0 = 200dot1dStpBridgeForwardDelay.0 = 1500dot1dStpPort.193 = 193dot1dStpPort.195 = 195dot1dStpPort.204 = 204dot1dStpPort.205 = 205dot1dStpPortPriority.193 = 16dot1dStpPortPriority.195 = 32dot1dStpPortPriority.204 = 128dot1dStpPortPriority.205 = 128dot1dStpPortState.193 = 5dot1dStpPortState.195 = 5


28/92



dot1dStpPortState.204 = 2dot1dStpPortState.205 = 2dot1dStpPortEnable.193 = 1

dot1dStpPortEnable.195 = 1dot1dStpPortEnable.204 = 2dot1dStpPortEnable.205 = 2dot1dStpPortPathCost.193 = 20000dot1dStpPortPathCost.195 = 20000dot1dStpPortPathCost.204 = 20000dot1dStpPortPathCost.205 = 20000dot1dStpPortDesignatedRoot.193 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedRoot.195 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedRoot.204 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedRoot.205 = 20 00 00 1f 12 32 b7 80

dot1dStpPortDesignatedCost.193 = 0dot1dStpPortDesignatedCost.195 = 0


29/92



dot1dStpPortDesignatedCost.204 = 0dot1dStpPortDesignatedCost.205 = 0dot1dStpPortDesignatedBridge.193 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedBridge.195 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedBridge.204 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedBridge.205 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedPort.193 = 10 c1dot1dStpPortDesignatedPort.195 = 20 c3dot1dStpPortDesignatedPort.204 = 80 ccdot1dStpPortDesignatedPort.205 = 80 cddot1dStpPortForwardTransitions.193 = 2806dot1dStpPortForwardTransitions.195 = 2802dot1dStpPortForwardTransitions.204 = 0dot1dStpPortForwardTransitions.205 = 0dot1dStpPortPathCost32.193 = 20000dot1dStpPortPathCost32.195 = 20000dot1dStpPortPathCost32.204 = 20000dot1dStpPortPathCost32.205 = 20000dot1dStpVersion.0 = 2dot1dStpTxHoldCount.0 = 6dot1dStpPortProtocolMigration.193 = 2dot1dStpPortProtocolMigration.195 = 2dot1dStpPortProtocolMigration.204 = 2dot1dStpPortProtocolMigration.205 = 2dot1dStpPortAdminEdgePort.193 = 2dot1dStpPortAdminEdgePort.195 = 2dot1dStpPortAdminEdgePort.204 = 2dot1dStpPortAdminEdgePort.205 = 2dot1dStpPortOperEdgePort.193 = 2dot1dStpPortOperEdgePort.195 = 2dot1dStpPortOperEdgePort.204 = 2dot1dStpPortOperEdgePort.205 = 2dot1dStpPortAdminPointToPoint.193 = 2dot1dStpPortAdminPointToPoint.195 = 2dot1dStpPortAdminPointToPoint.204 = 2dot1dStpPortAdminPointToPoint.205 = 2dot1dStpPortOperPointToPoint.193 = 1

dot1dStpPortOperPointToPoint.195 = 1dot1dStpPortOperPointToPoint.204 = 1dot1dStpPortOperPointToPoint.205 = 1dot1dStpPortAdminPathCost.193 = 20000dot1dStpPortAdminPathCost.195 = 20000dot1dStpPortAdminPathCost.204 = 20000dot1dStpPortAdminPathCost.205 = 20000


30/92



Lets take STP port 193 -dot1dStpPort.193 = 193. Port 193 is nothing but Bridge port 193.Lets get the ifIndex of this from dot1dBase Table and the description for the Ifindex asbelow.

regress@EX4200-2> show snmp mib get dot1dBasePortIfIndex.193dot1dBasePortIfIndex.193 = 193

{master:0}regress@EX4200-2> show snmp mib get ifDescr.193ifDescr.193 = ge-0/0/0.0

As mentioned before , EX ports participating in Switching are logical, you can now usethe same method described above for finding out the corresponding physical port.

2.2.5.3RSTP Rapid Spanning Tree.

The following example is from MX device for RSTP configuration

regress@MX240-2> show snmp mib walk dot1dStpVersiondot1dStpVersion.0 = 2

regress@MX240-2> show snmp mib walk dot1dStpdot1dStpProtocolSpecification.0 = 3dot1dStpPriority.0 = 32768dot1dStpTimeSinceTopologyChange.0 = 7789700dot1dStpTopChanges.0 = 3dot1dStpDesignatedRoot.0 = 20 00 00 1f 12 32 b7 80dot1dStpRootCost.0 = 20000dot1dStpRootPort.0 = 41dot1dStpMaxAge.0 = 2000dot1dStpHelloTime.0 = 200dot1dStpHoldTime.0 = 100dot1dStpForwardDelay.0 = 1500dot1dStpBridgeMaxAge.0 = 2000dot1dStpBridgeHelloTime.0 = 200dot1dStpBridgeForwardDelay.0 = 1500dot1dStpPort.41 = 41dot1dStpPortPriority.41 = 128dot1dStpPortState.41 = 5dot1dStpPortEnable.41 = 1dot1dStpPortPathCost.41 = 20000dot1dStpPortDesignatedRoot.41 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedCost.41 = 0


31/92



dot1dStpPortDesignatedBridge.41 = 20 00 00 1f 12 32 b7 80dot1dStpPortDesignatedPort.41 = 12 01dot1dStpPortForwardTransitions.41 = 3

dot1dStpPortPathCost32.41 = 20000dot1dStpVersion.0 = 2dot1dStpTxHoldCount.0 = 6dot1dStpPortProtocolMigration.41 = 2dot1dStpPortAdminEdgePort.41 = 2dot1dStpPortOperEdgePort.41 = 2dot1dStpPortAdminPointToPoint.41 = 2dot1dStpPortOperPointToPoint.41 = 1dot1dStpPortAdminPathCost.41 = 20000

Lets take RSTP port

regress@MX240-2> show snmp mib get dot1dBasePortIfIndex.41dot1dBasePortIfIndex.41 = 117


This is physical port on MX. EX will be similar except that logical port is used in thatcase.

Please note MX and EX supports, RFC 4318, the dot1dStpExtPortTable which is a tablethat contains port-specific Rapid Spanning Tree information.

regress@MX240-2> show snmp mib walk dot1dStpExtPortTabledot1dStpPortProtocolMigration.41 = 2dot1dStpPortAdminEdgePort.41 = 2dot1dStpPortOperEdgePort.41 = 2dot1dStpPortAdminPointToPoint.41 = 2dot1dStpPortOperPointToPoint.41 = 1dot1dStpPortAdminPathCost.41 = 20000

NOTE ON Port Identifiers


32/92


33/92



Ports on the same Bridge to be managed (17.13.7 and Clause 14). The less significanttwelve bits is the Port Number expressed as an unsigned binary number. The value 0 isnot used as a Port Number.NOTEThe number of bits that are considered to be part of the Port Number (12 bits)differs from the 1998 and prior versions of this standard (formerly, the prioritycomponent was 8 bits and the Port Number component also 8 bits). This changeacknowledged that modern switched LAN infrastructures call for increasingly largenumbers of Ports to be supported in a single Bridge. To maintain managementcompatibility with older implementations, the priority component is still considered, formanagement purposes, to be an 8-bit value, but the values that it can be set to arerestricted to those where the least significant 4 bits are zero (i.e., only the most significant4 bits are settable).regress@MX240-2> show spanning-tree interfaceSpanning tree interface parameters for instance 0Interface Port ID Designated Designated Port State Role

port ID bridge ID Costge-1/0/0 128:41 16:513 8192.001f1232b780 20000 FWD ROOTge-1/0/1 128:42 32:515 8192.001f1232b780 20000 BLK ALT

2.2.5.3.1VSTP VLAN Spanning Tree

VLAN Spanning MIBS are supported only for MX. Please note the same dot1dStpTable issupported for VSTP as well. But the SNMP query will be slightly different for VSTP

To identify a VLAN spanning tree instance (VSTP on MX series Ethernet Servicesrouter), specify the routing instance name followed by a double colon (::) and the VLAN

ID. For example, to identify VSTP instance for VLAN 10 in the global default routinginstance, include default::10@public in the context (SNMPv3) or community (SNMPv1or v2) string.

Example: Spanning tree interface parameters for VLAN 10

Interface Port ID Designated Designated Port State Roleport ID bridge ID Cost

ge-1/0/0 128:41 128:41 32778.002159ad57d0 20000 FWD DESGSo to query for VSTP for VLAN Id 10, we need to use default::10@public the followingfor SNMP querying. Default is the default routing instance

Following is the output of the dot1dStpTable for VSTP


34/92



$ snmpwalk -v1 -c default::[email protected] 1.3.6.1.2.1.17.2.15

SNMPv2-SMI::mib-2.17.2.15.1.1.41 = INTEGER: 41STP port 41

SNMPv2-SMI::mib-2.17.2.15.1.2.41 = INTEGER: 128




SNMPv2-SMI::mib-2.17.2.15.1.6.41 = Hex-STRING: 80 0A 00 21 59 AD 57 D0


SNMPv2-SMI::mib-2.17.2.15.1.8.41 = Hex-STRING: 80 0A 00 21 59 AD 57 D0

SNMPv2-SMI::mib-2.17.2.15.1.9.41 = Hex-STRING: 80 29

SNMPv2-SMI::mib-2.17.2.15.1.10.41 = Counter32: 1


Now , you can use the normal query and find out the ifDescr of the STP port 41 as below

regress@MX240-2> show snmp mib get dot1dBasePortIfIndex.41

dot1dBasePortIfIndex.41 = 117


2.2.5.3.2MSTP Multiple Spanning Tree

MIMMSTP MIBS are supported only on MX platform as of now. EX has supported thisfor long but with some port indexing issue which is resolved in JUNOS 9.5. These areJUNIPER specific MIBs , please seehttp://www.juniper.net/techpubs/software/junos/junos94/swconfig-net-mgmt/interpreting-the-enterprise-specific-mimstp-mib.html#chap-mimstp-mibfor more details. Thissection only gives brief explanation of MSTP MIBs. This requires additional

reading and understanding from the link above.

MSTP BRIDGE configuration details below. CLI shown here for easy understanding.You can see two instances configured with ID 0 and 10. Each MSTP Multiple SpanningTree Instance (MSTI) is identified by a number.


35/92


36/92



Time since last topology change : 260 secondsLocal parametersBridge ID : 32778.00:21:59:ad:57:d1

The following showing the STP interfaces per instance , here same interface ge-1/0/0 ispart of instance 0 and 10

regress@MX240-2> show spanning-tree interface detailSpanning tree interface parameters for instance 0Interface name : ge-1/0/0

Port identifier : 128.41Designated port ID : 128.513

Port cost : 20000Port state : ForwardingDesignated bridge ID : 32768.00:1f:12:32:b7:80Port role : RootLink type : Pt-Pt/NONEDGEBoundary port : Yes

Spanning tree interface parameters for instance 10

Interface name : ge-1/0/0Port identifier : 128.41Designated port ID : 128.41Port cost : 20000Port state : ForwardingDesignated bridge ID : 32768.00:21:59:ad:57:d1Port role : MasterLink type : Pt-Pt/NONEDGEBoundary port : Yes

The MIB walk for jnxMIDot1sJuniperMstTable which provides MSTP moduleparameters for a given virtual context. Here the context is 0.

jnxMIMstGlobalDebug.0 = 2jnxMIMstSystemControl.0 = 1jnxMIMstModuleStatus.0 = 1jnxMIMstMaxMstInstanceNumber.0 = 64jnxMIMstNoOfMstiSupported.0 = 64jnxMIMstMaxHopCount.0 = 2000jnxMIMstBrgAddress.0 = 00 21 59 ad 57 d1 -Bridge ID(see CLI output above)


37/92


38/92



jnxMIMstRegionConfigChangeCount.0 = 2jnxMIMstCistBridgeRoleSelectionSemState.0 = 1

jnxMIMstCistTimeSinceTopologyChange.0 = 670jnxMIMstCistTopChanges.0 = 2jnxMIMstCistNewRootBridgeCount.0 = 3jnxMIMstCistHelloTime.0 = 200jnxMIMstCistBridgeHelloTime.0 = 200jnxMIMstCistDynamicPathcostCalculation.0 = 2

jnxMIMstMstiBridgeTable- Table containing Bridge Information specific to SpanningTree Instance. This table maintains context ID as one more index to support Multiple

Instances. Therefore, the below table lists the details for MSTI 10 within context 0.

regress@MX240-2> show snmp mib walk jnxMIMstMstiBridgeTablejnxMIMstMstiInstanceIndex.0.10 = 10jnxMIMstMstiBridgeRegionalRoot.0.10 = 80 00 00 21 59 ad 57 d1jnxMIMstMstiBridgePriority.0.10 = 32768jnxMIMstMstiRootCost.0.10 = 0jnxMIMstMstiRootPort.0.10 = 0jnxMIMstMstiTimeSinceTopologyChange.0.10 = 1241jnxMIMstMstiTopChanges.0.10 = 2jnxMIMstMstiNewRootBridgeCount.0.10 = 0jnxMIMstMstiBridgeRoleSelectionSemState.0.10 = 1jnxMIMstInstanceUpCount.0.10 = 1jnxMIMstInstanceDownCount.0.10 = 0jnxMIMstOldDesignatedRoot.0.10 = 00 00 00 00 00 00 00 00

The jnxMIMstCistPortTable lists the Common Spanning Tree Port Information. In thefollowing example, the port 41 (index) is the CIST port, which is nothing but thedot1dBasePort 41. You can use the dot1dBasePortIfIndex value to find out the ifEntry ofthis MSTP port as below

jnxMIMstCistPortPathCost.41 = 20000jnxMIMstCistPortPriority.41 = 128jnxMIMstCistPortDesignatedRoot.41 = 80 00 00 1f 12 32 b7 80jnxMIMstCistPortDesignatedBridge.41 = 80 00 00 1f 12 32 b7 80jnxMIMstCistPortDesignatedPort.41 = 82 01


39/92



jnxMIMstCistPortAdminP2P.41 = 2jnxMIMstCistPortOperP2P.41 = 1jnxMIMstCistPortAdminEdgeStatus.41 = 2

jnxMIMstCistPortOperEdgeStatus.41 = 2jnxMIMstCistPortProtocolMigration.41 = 2jnxMIMstCistPortState.41 = 5jnxMIMstCistForcePortState.41 = 1jnxMIMstCistPortForwardTransitions.41 = 2jnxMIMstCistPortRxMstBpduCount.41 = 0jnxMIMstCistPortRxRstBpduCount.41 = 0jnxMIMstCistPortRxConfigBpduCount.41 = 848jnxMIMstCistPortRxTcnBpduCount.41 = 0jnxMIMstCistPortTxMstBpduCount.41 = 9jnxMIMstCistPortTxRstBpduCount.41 = 0

jnxMIMstCistPortTxConfigBpduCount.41 = 0jnxMIMstCistPortTxTcnBpduCount.41 = 1jnxMIMstCistPortInvalidMstBpduRxCount.41 = 0jnxMIMstCistPortInvalidRstBpduRxCount.41 = 0jnxMIMstCistPortInvalidConfigBpduRxCount.41 = 0jnxMIMstCistPortInvalidTcnBpduRxCount.41 = 0jnxMIMstCistPortTransmitSemState.41 = 5

jnxMIMstCistPortReceiveSemState.41 = 1jnxMIMstCistPortProtMigrationSemState.41 = 2jnxMIMstCistProtocolMigrationCount.41 = 3jnxMIMstCistPortDesignatedCost.41 = 0jnxMIMstCistPortRegionalRoot.41 = 80 00 00 21 59 ad 57 d1jnxMIMstCistPortRegionalPathCost.41 = 0jnxMIMstCistSelectedPortRole.41 = 3jnxMIMstCistCurrentPortRole.41 = 3jnxMIMstCistPortInfoSemState.41 = 8jnxMIMstCistPortRoleTransitionSemState.41 = 3jnxMIMstCistPortStateTransitionSemState.41 = 2jnxMIMstCistPortTopologyChangeSemState.41 = 2jnxMIMstCistPortHelloTime.41 = 200jnxMIMstCistPortOperVersion.41 = 0jnxMIMstCistPortEffectivePortState.41 = 1jnxMIMstCistPortAutoEdgeStatus.41 = 1

Now , you can use the normal query and find out the ifDescr of the STP port 41 as below


40/92



regress@MX240-2> show snmp mib get dot1dBasePortIfIndex.41dot1dBasePortIfIndex.41 = 117


The jnxMIMstMstiPortTable gives the Spanning Tree Instance Specific Port Information.As seen below, dot1dBasePort 41 on MSTI instances 10 has the following attributesassociated with it.

jnxMIMstMstiPortPathCost.41.10 = 20000jnxMIMstMstiPortPriority.41.10 = 128jnxMIMstMstiPortDesignatedRoot.41.10 = 80 00 00 21 59 ad 57 d1

jnxMIMstMstiPortDesignatedBridge.41.10 = 80 00 00 21 59 ad 57 d1jnxMIMstMstiPortDesignatedPort.41.10 = 80 29jnxMIMstMstiPortState.41.10 = 5jnxMIMstMstiForcePortState.41.10 = 1jnxMIMstMstiPortForwardTransitions.41.10 = 2jnxMIMstMstiPortReceivedBPDUs.41.10 = 0jnxMIMstMstiPortTransmittedBPDUs.41.10 = 5jnxMIMstMstiPortInvalidBPDUsRcvd.41.10 = 0jnxMIMstMstiPortDesignatedCost.41.10 = 0jnxMIMstMstiSelectedPortRole.41.10 = 5jnxMIMstMstiCurrentPortRole.41.10 = 5jnxMIMstMstiPortInfoSemState.41.10 = 8jnxMIMstMstiPortRoleTransitionSemState.41.10 = 3jnxMIMstMstiPortStateTransitionSemState.41.10 = 2jnxMIMstMstiPortTopologyChangeSemState.41.10 = 2jnxMIMstMstiPortEffectivePortState.41.10 = 1

The jnxMIMstCistPortProtectTable defines the jnxMIMstCist Port Table for providingextensions for Root Protect and Loop Protect to the correspondingjnxMIMstCistPortTable entry.

jnxMIMstCistPortRootProtectEnabled.41 = 2jnxMIMstCistPortRootProtectState.41 = 0

The jnxMIMstMstiPortProtectTable defines the jnxMIMstMsti Port Table for providingextensions for Root Protect and Loop Protect to the correspondingjnxMIMstMstiPortTable entry.


41/92



jnxMIMstMstiPortRootProtectState.41.10 = 0jnxMIDot1sJnxMstSetGlobalTrapOption.0 = 0

jnxMIMstVlanInstanceMappingTable -This table contains one entry for each instance ofMSTP.This table maintains context ID as one more index to support Multiple Instances.

jnxMIMstMapVlanIndex.0.10 = 1jnxMIMstUnMapVlanIndex.0.10 = 1jnxMIMstSetVlanList.0.10 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00jnxMIMstResetVlanList.0.10 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000jnxMIMstInstanceVlanMapped.0.10 = 00 40 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00jnxMIMstInstanceVlanMapped2k.0.10 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


42/92



00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00jnxMIMstInstanceVlanMapped3k.0.10 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00jnxMIMstInstanceVlanMapped4k.0.10 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00

Other Variables of the MIMSTP MIB are as below. Please refer to standarddocumentation for explanation

jnxMIMstGlobalErrTrapType.0 = 0jnxMIMstSetTraps.0 = 2jnxMIMstGenTrapType.0 = 0jnxMIMstPortTrapIndex.41 = 41jnxMIMstPortMigrationType.41 = 0jnxMIMstPktErrType.41 = 0jnxMIMstPktErrVal.41 = 0

2.2.5.4 IPv4 Interfaces on JUNOS devices

The ipv4 interfaces are represented in the ipAddrTable.The ifIndex of interfaces onwhich the IP address is configured can be retrieved using ipAdEntIfIndex

ipAdEntIfIndex.116.197.178.6 = 36ipAdEntIfIndex.128.0.0.1 = 38ipAdEntIfIndex.128.0.0.16 = 38ipAdEntIfIndex.128.0.0.32 = 38ipAdEntIfIndex.172.25.25.2 = 219ipAdEntIfIndex.172.25.27.2 = 220

Now determine the ifDescr from the ifIndex retrieved above

For example:ipAdEntIfIndex.172.25.27.2 = 220---ifIndex 220 has IP of 172.25.27.2


43/92



NetMask for this address is /24 as seen below

ipAdEntNetMask.172.25.27.2 = 255.255.255.0

regress@EX4200-2> show snmp mib get ifDescr.220ifDescr.220 = ge-0/0/17.20

regress@EX4200-2> show interfaces terse |grep ge-0/0/17.20ge-0/0/17.20 up up inet 172.25.27.2/24

Therefore , NM systems can show interface ge-0/0/17.20 logical interface has IP of172.25.27.2/24.

The same logic of Step 2 can be used to determine the physical interface correspondingthe above logical interface

ifStackStatus.220.125 = 1

regress@EX4200-2> show snmp mib get ifDescr.125ifDescr.125 = ge-0/0/17

3 Key Performance Indicators DevicesDevice Availability- Percentage of time that the device responds to a SNMP requestDevice Latency - The latency measures the round-trip delay (in milliseconds) when aping request is sent to a monitored device

CPU Utilization per card (RE/FPC)(Average utilization over the past minute of a CPU jnxOperatingCPU)

Memory Utilization (jnxOperatingBuffer)

Temperature Monitoring for each FRU/RE

High Availability Monitoring Number of Virtual Router Errors Received

High Availability Percentage of time for which the redundant system/node is available

Disk Utilization(Utilization of disk space within the Juniper Networks router

hrStorageSize/hrStorageUsed)


44/92



3.1 CPU Utilization

The CPU utilization can be determined by reading the appropriate instance of the OIDjnxOperatingCPU. Note each FPC and RE has its own CPU. The

jnxOperatingCPU OID defined in the jnxOPeratingTable gives you

information for each RE and FPC. The Chassis daemon on JUNOS reads CPUaccumulated times every 5 seconds from kernel and computes percentage of CPUutilization over this 5 second interval. Chassis daemon does not compute CPU utilizationat CLI or SNMP query time. It provides the cached value that was computed at the end oflast 5-second period. Kernel accumulates times (actual ticks) for these states at clockinterrupt intervals (it charges that tick to one of these states). Chassis daemon reads theseaccumulated times from kernel memory location once every 5 seconds. It then subtractsthe last values thus giving CPU usages since last interval for each CPU state. Percentageis computed by 100 x CPU-USAGE [CPU-STATE]/total where total is the sum of CPUtime for all states.

The "show chassis routing" CLI on JUNOS prints the cached values that were computedin the latest 5-second interval. These values are not computed at CLI commandexecution time.

3.2 Memory Utilization

ThisjnxOperatingBufferis the memory utilization and is computed as (total memory -

free memory)/total memory. For percentage, multiply above fraction with 100. Bufferutilization mib jnxOperatingBuffer applies to all PFEs (SFM, SCB, SPMB, FPC, etc.)and is not limited to routing engine. For routing engine, same OID is used to reportmemory utilization in BSD/Junos kernel running on routing engine. Each PFE has itsown memory independent of any other PFE memory. If you want to average, average thememory utilization of each PFE over duration by taking multiple samples over time. Forexample, one cannot average routing engine memory utilization with FPC memoryutilization and provide one result.

3.3 Disk Utilization

The utilization of disk space within the Juniper Networks router can be calculated usingthe Host Resources MIB (HOST-RESOURCES-MIB (RFC 2790)). The disk utilization iscalculated as hrStorageSize/hrStorageUsed.


45/92



3.4 Operating Temperature

The operating temperature can be obtained by reading thejnxOperatingTemp.

This is the temperature in Celsius (degrees C) of the component on the JUNOS deviceand is zero if unavailable or inapplicable.

4 Key Performance Indicators - InterfacesThe Interface Performance includes the monitoring of both Physical and Logicalinterfaces on the device. The ifTable defined in RFC 1213 lists both the physical as wellas the logical interfaces that are present in the device. The ifIndex corresponds to bothLogical as well as Physical interfaces on a device.

Juniper also defines an extension to the ifTable in the Enterprise MIB (Juniper IF MIB -mib-jnx-if-extensions.txt). This MIB should be used to derive the interface related

information and indicators.

Interface StatusThis includes the operational status and the administration status of the interface.Interface operating status is indicated by ifOperStatusInterface Admin status is indicated by ifAdminStatus

Interface Utilization

Indicates the normal utilization of the interface observed over the last 7 days for thisinterface. Normal utilization is based on the hourly maximum value of the inbound andoutbound traffic as a percentage of the interface bandwidth.The interface utilization is calculated as (ifInOctets + ifOutOctets) * 8 *100 / ifSpeed

Number of Errors on the interfaceThis is a sum of the number of inbound packets that contained errors, preventing themfrom being delivered and the number of outbound packets that contained errors,preventing them from being transmittedNumber of Errors = ifInErrors + ifOutErrors

Total number of Collisions

This states the number of output collisions detected on the interface.The OID ifJnxCollisionsin the Juniper IF MIB denotes the number of collisions.

Total number of discards

Number of packets discarded, even though no errors were detectedNumber of discards = ifInDiscards + ifOutDiscards

Number of packets discarded because of unknown protocolThis number of inbound packets discarded because they were of an unknown protocol.This is indicated by ifInUnknownProtosin ifTable in MIB 2


46/92


47/92



ifIn1SecRate(.1.3.6.1.4.1.2636.3.3.1.1.1)ifIn1SecOctets(.1.3.6.1.4.1.2636.3.3.1.1.2)ifIn1SecPkts(.1.3.6.1.4.1.2636.3.3.1.1.3)

ifOut1SecRate(.1.3.6.1.4.1.2636.3.3.1.1.4)ifOut1SecOctets(.1.3.6.1.4.1.2636.3.3.1.1.5)ifOut1SecPkts(.1.3.6.1.4.1.2636.3.3.1.1.6)ifHCIn1SecRate(.1.3.6.1.4.1.2636.3.3.1.1.7)ifHCOut1SecRate(.1.3.6.1.4.1.2636.3.3.1.1.8)ifJnxInErrors(.1.3.6.1.4.1.2636.3.3.1.1.9)ifJnxInFrameErrors(.1.3.6.1.4.1.2636.3.3.1.1.10)ifJnxInQDrops(.1.3.6.1.4.1.2636.3.3.1.1.11)ifJnxInRunts(.1.3.6.1.4.1.2636.3.3.1.1.12)ifJnxInGiants(.1.3.6.1.4.1.2636.3.3.1.1.13)ifJnxInDiscards(.1.3.6.1.4.1.2636.3.3.1.1.14)

ifJnxInHslCrcErrors(.1.3.6.1.4.1.2636.3.3.1.1.15)ifJnxInHslFifoOverFlows(.1.3.6.1.4.1.2636.3.3.1.1.16)ifJnxInL3Incompletes(.1.3.6.1.4.1.2636.3.3.1.1.17)ifJnxInL2ChanErrors(.1.3.6.1.4.1.2636.3.3.1.1.18)ifJnxInL2MismatchTimeouts(.1.3.6.1.4.1.2636.3.3.1.1.19)ifJnxInInvalidVCs(.1.3.6.1.4.1.2636.3.3.1.1.20)ifJnxInFifoErrors(.1.3.6.1.4.1.2636.3.3.1.1.21)ifJnxBucketDrops(.1.3.6.1.4.1.2636.3.3.1.1.22)ifJnxSramErrors(.1.3.6.1.4.1.2636.3.3.1.1.23)ifJnxOutErrors(.1.3.6.1.4.1.2636.3.3.1.1.24)ifJnxCollisions(.1.3.6.1.4.1.2636.3.3.1.1.25)ifJnxCarrierTrans(.1.3.6.1.4.1.2636.3.3.1.1.26)ifJnxOutQDrops(.1.3.6.1.4.1.2636.3.3.1.1.27)ifJnxOutAgedErrors(.1.3.6.1.4.1.2636.3.3.1.1.28)ifJnxOutFifoErrors(.1.3.6.1.4.1.2636.3.3.1.1.29)ifJnxOutHslFifoUnderFlows(.1.3.6.1.4.1.2636.3.3.1.1.30)ifJnxOutHslCrcErrors(.1.3.6.1.4.1.2636.3.3.1.1.31)Ethernet Statistics

1.3.6.1.2.1.16.1.1.1.1 (etherStatsIndex)1.3.6.1.2.1.16.1.1.1.2 (etherStatsDataSource)1.3.6.1.2.1.16.1.1.1.3 (etherStatsDropEvents)1.3.6.1.2.1.16.1.1.1.4 (etherStatsOctets)

1.3.6.1.2.1.16.1.1.1.5 (etherStatsPkts)1.3.6.1.2.1.16.1.1.1.6 (etherStatsBroadcastPkts)1.3.6.1.2.1.16.1.1.1.7 (etherStatsMulticastPkts)1.3.6.1.2.1.16.1.1.1.8 (etherStatsCRCAlignErrors)1.3.6.1.2.1.16.1.1.1.9 (etherStatsUndersizePkts)1.3.6.1.2.1.16.1.1.1.10 (etherStatsOversizePkts)1.3.6.1.2.1.16.1.1.1.11 (etherStatsFragments)


48/92



1.3.6.1.2.1.16.1.1.1.12 (etherStatsJabbers)1.3.6.1.2.1.16.1.1.1.13 (etherStatsCollisions)1.3.6.1.2.1.16.1.1.1.14 (etherStatsPkts64Octets)

1.3.6.1.2.1.16.1.1.1.15 (etherStatsPkts65to127Octets)1.3.6.1.2.1.16.1.1.1.16 (etherStatsPkts128to255Octets)1.3.6.1.2.1.16.1.1.1.17 (etherStatsPkts256to511Octets)1.3.6.1.2.1.16.1.1.1.18 (etherStatsPkts512to1023Octets)1.3.6.1.2.1.16.1.1.1.19 (etherStatsPkts1024to1518Octets)1.3.6.1.2.1.16.1.1.1.20 (etherStatsOwner)1.3.6.1.2.1.16.1.1.1.21 (etherStatsStatus)1.3.6.1.2.1.16.2.1.1.1 (historyControlIndex)1.3.6.1.2.1.16.2.1.1.2 (historyControlDataSource)1.3.6.1.2.1.16.2.1.1.3 (historyControlBucketsRequested)1.3.6.1.2.1.16.2.1.1.4 (historyControlBucketsGranted)

1.3.6.1.2.1.16.2.1.1.5 (historyControlInterval)1.3.6.1.2.1.16.2.1.1.6 (historyControlOwner)1.3.6.1.2.1.16.2.1.1.7 (historyControlStatus)1.3.6.1.2.1.16.2.2.1.1 (etherHistoryIndex)1.3.6.1.2.1.16.2.2.1.2 (etherHistorySampleIndex)1.3.6.1.2.1.16.2.2.1.3 (etherHistoryIntervalStart)1.3.6.1.2.1.16.2.2.1.4 (etherHistoryDropEvents)1.3.6.1.2.1.16.2.2.1.5 (etherHistoryOctets)1.3.6.1.2.1.16.2.2.1.6 (etherHistoryPkts)1.3.6.1.2.1.16.2.2.1.7 (etherHistoryBroadcastPkts)1.3.6.1.2.1.16.2.2.1.8 (etherHistoryMulticastPkts)1.3.6.1.2.1.16.2.2.1.9 (etherHistoryCRCAlignErrors)1.3.6.1.2.1.16.2.2.1.10 (etherHistoryUndersizePkts)1.3.6.1.2.1.16.2.2.1.11 (etherHistoryOversizePkts)1.3.6.1.2.1.16.2.2.1.12 (etherHistoryFragments)1.3.6.1.2.1.16.2.2.1.13 (etherHistoryJabbers)1.3.6.1.2.1.16.2.2.1.14 (etherHistoryCollisions)1.3.6.1.2.1.16.2.2.1.15 (etherHistoryUtilization)Ether-Like Statistics

1.3.6.1.2.1.10.7.2.1.1 (dot3StatsIndex)1.3.6.1.2.1.10.7.2.1.2 (dot3StatsAlignmentErrors)1.3.6.1.2.1.10.7.2.1.3 (dot3StatsFCSErrors)

1.3.6.1.2.1.10.7.2.1.4 (dot3StatsSingleCollisionFrames)1.3.6.1.2.1.10.7.2.1.5 (dot3StatsMultipleCollisionFrames)1.3.6.1.2.1.10.7.2.1.6 (dot3StatsSQETestErrors)1.3.6.1.2.1.10.7.2.1.7 (dot3StatsDeferredTransmissions)1.3.6.1.2.1.10.7.2.1.8 (dot3StatsLateCollisions)1.3.6.1.2.1.10.7.2.1.9 (dot3StatsExcessiveCollisions)1.3.6.1.2.1.10.7.2.1.10 (dot3StatsInternalMacTransmitErrors)


49/92



1.3.6.1.2.1.10.7.2.1.11 (dot3StatsCarrierSenseErrors)1.3.6.1.2.1.10.7.2.1.13 (dot3StatsFrameTooLongs)1.3.6.1.2.1.10.7.2.1.16 (dot3StatsInternalMacReceiveErrors)


50/92



1.3.6.1.2.1.10.7.2.1.17 (dot3StatsEtherChipSet)1.3.6.1.2.1.10.7.2.1.18 (dot3StatsSymbolErrors)1.3.6.1.2.1.10.7.2.1.19 (dot3StatsDuplexStatus)Multicast

.1.3.6.1.2.1.83.1.1.1 (ipMRouteEnable)

.1.3.6.1.2.1.83.1.1.2.1.4 (ipMRouteUpstreamNeighbor)

.1.3.6.1.2.1.83.1.1.2.1.5 (ipMRouteInIfIndex)

.1.3.6.1.2.1.83.1.1.2.1.6 (ipMRouteUpTime)

.1.3.6.1.2.1.83.1.1.2.1.7 (ipMRouteExpiryTime)

.1.3.6.1.2.1.83.1.1.2.1.8 (ipMRoutePkts)

.1.3.6.1.2.1.83.1.1.2.1.9 (ipMRouteDifferentInIfPackets)

.1.3.6.1.2.1.83.1.1.2.1.10 (ipMRouteOctets)

.1.3.6.1.2.1.83.1.1.2.1.11 (ipMRouteProtocol)

.1.3.6.1.2.1.83.1.1.2.1.12 (ipMRouteRtProto)

.1.3.6.1.2.1.83.1.1.2.1.13 (ipMRouteRtAddress)

.1.3.6.1.2.1.83.1.1.2.1.14 (ipMRouteRtMask)

.1.3.6.1.2.1.83.1.1.2.1.15 (ipMRouteRtType)

.1.3.6.1.2.1.83.1.1.2.1.16 (ipMRouteHCOctets)

.1.3.6.1.2.1.83.1.1.3.1.6 (ipMRouteNextHopState)

.1.3.6.1.2.1.83.1.1.3.1.7 (ipMRouteNextHopUpTime)

.1.3.6.1.2.1.83.1.1.3.1.8 (ipMRouteNextHopExpiryTime)

.1.3.6.1.2.1.83.1.1.3.1.9 (ipMRouteNextHopClosestMemberHops)

.1.3.6.1.2.1.83.1.1.3.1.10 (ipMRouteNextHopProtocol)

.1.3.6.1.2.1.83.1.1.3.1.11 (ipMRouteNextHopPkts)

.1.3.6.1.2.1.83.1.1.4.1.2 (ipMRouteInterfaceTtl)

.1.3.6.1.2.1.83.1.1.4.1.3 (ipMRouteInterfaceProtocol)

.1.3.6.1.2.1.83.1.1.4.1.4 (ipMRouteInterfaceRateLimit)

.1.3.6.1.2.1.83.1.1.4.1.5 (ipMRouteInterfaceInMcastOctets)

.1.3.6.1.2.1.83.1.1.4.1.6 (ipMRouteInterfaceOutMcastOctets)

.1.3.6.1.2.1.83.1.1.4.1.7 (ipMRouteInterfaceHCInMcastOctets)

.1.3.6.1.2.1.83.1.1.4.1.8 (ipMRouteInterfaceHCOutMcastOctets)

.1.3.6.1.2.1.83.1.1.5.1.4 (ipMRouteBoundaryStatus)

.1.3.6.1.2.1.83.1.1.6.1.4 (ipMRouteScopeNameString)

.1.3.6.1.2.1.83.1.1.6.1.5 (ipMRouteScopeNameDefault)

.1.3.6.1.2.1.83.1.1.6.1.6 (ipMRouteScopeNameStatus)

.1.3.6.1.3.59.1.1.1.1.2 (igmpInterfaceQueryInterval)

.1.3.6.1.3.59.1.1.1.1.3 (igmpInterfaceStatus)

.1.3.6.1.3.59.1.1.1.1.4 (igmpInterfaceVersion)

.1.3.6.1.3.59.1.1.1.1.5 (igmpInterfaceQuerier)

.1.3.6.1.3.59.1.1.1.1.6 (igmpInterfaceQueryMaxResponseTime)

.1.3.6.1.3.59.1.1.1.1.9 (igmpInterfaceVersion1QuerierTimer)

.1.3.6.1.3.59.1.1.1.1.10 (igmpInterfaceWrongVersionQueries)


51/92



.1.3.6.1.3.59.1.1.1.1.11 (igmpInterfaceJoins)

.1.3.6.1.3.59.1.1.1.1.13 (igmpInterfaceGroups)

.1.3.6.1.3.59.1.1.1.1.14 (igmpInterfaceRobustness)

.1.3.6.1.3.59.1.1.1.1.15 (igmpInterfaceLastMembQueryIntvl).1.3.6.1.3.59.1.1.1.1.16 (igmpInterfaceProxyIfIndex)

.1.3.6.1.3.59.1.1.1.1.17 (igmpInterfaceQuerierUpTime)

.1.3.6.1.3.59.1.1.1.1.18 (igmpInterfaceQuerierExpiryTime)

.1.3.6.1.3.59.1.1.2.1.3 (igmpCacheSelf)

.1.3.6.1.3.59.1.1.2.1.4 (igmpCacheLastReporter)

.1.3.6.1.3.59.1.1.2.1.5 (igmpCacheUpTime)

.1.3.6.1.3.59.1.1.2.1.6 (igmpCacheExpiryTime)

.1.3.6.1.3.59.1.1.2.1.7 (igmpCacheStatus)

.1.3.6.1.3.59.1.1.2.1.8 (igmpCacheVersion1HostTimer)

.1.3.6.1.3.61.1.1.1 (pimJoinPruneInterval)

.1.3.6.1.3.61.1.1.2.1.2 (pimInterfaceAddress).1.3.6.1.3.61.1.1.2.1.3 (pimInterfaceNetMask)

.1.3.6.1.3.61.1.1.2.1.4 (pimInterfaceMode)

.1.3.6.1.3.61.1.1.2.1.5 (pimInterfaceDR)

.1.3.6.1.3.61.1.1.2.1.6 (pimInterfaceHelloInterval)

.1.3.6.1.3.61.1.1.2.1.7 (pimInterfaceStatus)

.1.3.6.1.3.61.1.1.2.1.8 (pimInterfaceJoinPruneInterval)

.1.3.6.1.3.61.1.1.2.1.9 (pimInterfaceCBSRPreference)

.1.3.6.1.3.61.1.1.3.1.2 (pimNeighborIfIndex)

.1.3.6.1.3.61.1.1.3.1.3 (pimNeighborUpTime)

.1.3.6.1.3.61.1.1.3.1.4 (pimNeighborExpiryTime)

.1.3.6.1.3.61.1.1.3.1.5 (pimNeighborMode)

.1.3.6.1.3.61.1.1.4.1.1 (pimIpMRouteUpstreamAssertTimer)

.1.3.6.1.3.61.1.1.4.1.2 (pimIpMRouteAssertMetric)

.1.3.6.1.3.61.1.1.4.1.3 (pimIpMRouteAssertMetricPref)

.1.3.6.1.3.61.1.1.4.1.4 (pimIpMRouteAssertRPTBit)

.1.3.6.1.3.61.1.1.4.1.5 (pimIpMRouteFlags)

.1.3.6.1.3.61.1.1.6.1.4 (pimRPSetHoldTime)

.1.3.6.1.3.61.1.1.6.1.5 (pimRPSetExpiryTime)

.1.3.6.1.3.61.1.1.7.1.2 (pimIpMRouteNextHopPruneReason)

.1.3.6.1.3.61.1.1.11.1.3 (pimCandidateRPAddress)

.1.3.6.1.3.61.1.1.11.1.4 (pimCandidateRPRowStatus)

.1.3.6.1.3.61.1.1.12.1.2 (pimComponentBSRAddress)

.1.3.6.1.3.61.1.1.12.1.3 (pimComponentBSRExpiryTime)

.1.3.6.1.3.61.1.1.12.1.4 (pimComponentCRPHoldTime)

.1.3.6.1.3.61.1.1.12.1.5 (pimComponentStatus)IPv6

.1.3.6.1.2.1.55.1.5.1.9 (ipv6IfAdminStatus)

.1.3.6.1.2.1.55.1.5.1.10 (ipv6IfOperStatus)


52/92



.1.3.6.1.2.1.55.1.5.1.11 (ipv6IfLastChange)

.1.3.6.1.2.1.55.1.6.1.1 (ipv6IfStatsInReceives)

.1.3.6.1.2.1.55.1.6.1.2 (ipv6IfStatsInHdrErrors)

.1.3.6.1.2.1.55.1.6.1.3 (ipv6IfStatsInTooBigErrors).1.3.6.1.2.1.55.1.6.1.4 (ipv6IfStatsInNoRoutes)

.1.3.6.1.2.1.55.1.6.1.5 (ipv6IfStatsInAddrErrors)

.1.3.6.1.2.1.55.1.6.1.6 (ipv6IfStatsInUnknownProtos)

.1.3.6.1.2.1.55.1.6.1.7 (ipv6IfStatsInTruncatedPkts)

.1.3.6.1.2.1.55.1.6.1.8 (ipv6IfStatsInDiscards)

.1.3.6.1.2.1.55.1.6.1.9 (ipv6IfStatsInDelivers)

.1.3.6.1.2.1.55.1.6.1.10 (ipv6IfStatsOutForwDatagrams)

.1.3.6.1.2.1.55.1.6.1.11 (ipv6IfStatsOutRequests)

.1.3.6.1.2.1.55.1.6.1.12 (ipv6IfStatsOutDiscards)

.1.3.6.1.2.1.55.1.6.1.13 (ipv6IfStatsOutFragOKs)

.1.3.6.1.2.1.55.1.6.1.14 (ipv6IfStatsOutFragFails).1.3.6.1.2.1.55.1.6.1.15 (ipv6IfStatsOutFragCreates)

.1.3.6.1.2.1.55.1.6.1.16 (ipv6IfStatsReasmReqds)

.1.3.6.1.2.1.55.1.6.1.17 (ipv6IfStatsReasmOKs)

.1.3.6.1.2.1.55.1.6.1.18 (ipv6IfStatsReasmFails)

.1.3.6.1.2.1.55.1.6.1.19 (ipv6IfStatsInMcastPkts)

.1.3.6.1.2.1.55.1.6.1.20 (ipv6IfStatsOutMcastPkts)

.1.3.6.1.2.1.55.1.7.1.3 (ipv6AddrPrefixOnLinkFlag)

.1.3.6.1.2.1.55.1.7.1.4 (ipv6AddrPrefixAutonomousFlag)

.1.3.6.1.2.1.55.1.7.1.5 (ipv6AddrPrefixAdvPreferredLifetime)

.1.3.6.1.2.1.55.1.7.1.6 (ipv6AddrPrefixAdvValidLifetime)

.1.3.6.1.2.1.55.1.8.1.2 (ipv6AddrPfxLength)

.1.3.6.1.2.1.55.1.8.1.3 (ipv6AddrType)

.1.3.6.1.2.1.55.1.8.1.4 (ipv6AddrAnycastFlag)

.1.3.6.1.2.1.55.1.8.1.5 (ipv6AddrStatus)

.1.3.6.1.2.1.55.1.9 (ipv6RouteNumber)

.1.3.6.1.2.1.55.1.10 (ipv6DiscardedRoutes)


53/92



5 Key Performance Indicators - Class of Service

You can use class-of-service (CoS) mechanisms to regulate how certain classes of

packets are handled within your network during times of peak congestion. Typically youmust perform the following steps when implementing a class-of-service mechanism:

Identify the type of packets that will be applied to this class. For example, includeall customer traffic from a specific ingress edge interface within one class, orinclude all packets of a particular protocol such as voice over IP (VoIP).

Identify the required deterministic behavior for each class. For example, if VoIPis important, give VoIP traffic the highest priority during times of networkcongestion. Conversely, you can downgrade the importance of Web traffic duringcongestion, as it may not impact customers too much.

With this information, you can configure mechanisms at the network ingress to monitor,mark, and police traffic classes. Marked traffic can then be handled in a moredeterministic way at egress interfaces, typically by applying different queuingmechanisms for each class during times of network congestion. You can collectinformation from the network to provide customers with reports showing how thenetwork is behaving during times of congestion

To generate these reports, routers must provide the following information:

Submitted trafficAmount of traffic received per class. Delivered trafficAmount of traffic transmitted per class.

Dropped trafficAmount of traffic dropped because of CoS limits.

Number of bytes being counted pertaining to the specified firewall filter counter

jnxFWCounterByteCount

Number of packets being counted pertaining to the specified firewall filter counterjnxFWCounterPacketCount

Number of bytes belonging to the specified forwarding class that were transmitted

on the specified virtual circuit. jnxCosAtmVcQstatsOutBytes

Number of transmitted bytes or packets per interface per forwarding class

jnxCosIfqTxedPktsThe number of tail-dropped or RED-dropped packets per interface per forwarding

classYou can calculate the amount of dropped traffic by subtracting the outbound traffic fromthe incoming traffic: Dropped = Inbound Counter Outbound CounterjnxCosIfqTailDropPkts & jnxCosIfqTotalRedDropPkts


54/92


55/92



5.5 Red Drop Packets

The number of RED-dropped packets per interface per forwarding class can be calculatedby polling the jnxCosIfqTotalRedDropPkts in jnxCosIfqStatsTable in JUNIPER-COS-

MIB

5.6 Counters for measuring CoS

The following OIDs can be used to monitor the CoS performace. The OIDs that getsupported in the Enterprise CoS MIB is specific to the device type. The following tableslist the applicable OIDs for each Juniper Device type.

MX Series

jnxCosIfqStatsTable(.1.3.6.1.4.1.2636.3.15.1)

.1.3.6.1.4.1.2636.3.15.1.1.3 (jnxCosIfqQedPkts)

.1.3.6.1.4.1.2636.3.15.1.1.4 (jnxCosIfqQedPktRate).1.3.6.1.4.1.2636.3.15.1.1.5 (jnxCosIfqQedBytes)

.1.3.6.1.4.1.2636.3.15.1.1.6 (jnxCosIfqQedByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.7 (jnxCosIfqTxedPkts)

.1.3.6.1.4.1.2636.3.15.1.1.8 (jnxCosIfqTxedPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.9 (jnxCosIfqTxedBytes)

.1.3.6.1.4.1.2636.3.15.1.1.10 (jnxCosIfqTxedByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.11 (jnxCosIfqTailDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.12 (jnxCosIfqTailDropPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.13 (jnxCosIfqTotalRedDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.14 (jnxCosIfqTotalRedDropPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.15 (jnxCosIfqLpNonTcpRedDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.16 (jnxCosIfqLpNonTcpRedDropPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.17 (jnxCosIfqLpTcpRedDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.18 (jnxCosIfqLpTcpRedDropPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.19 (jnxCosIfqHpNonTcpRedDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.20 (jnxCosIfqHpNonTcpRedDropPktRate)


56/92



.1.3.6.1.4.1.2636.3.15.1.1.21 (jnxCosIfqHpTcpRedDropPkts)

.1.3.6.1.4.1.2636.3.15.1.1.22 (jnxCosIfqHpTcpRedDropPktRate)

.1.3.6.1.4.1.2636.3.15.1.1.23 (jnxCosIfqTotalRedDropBytes)

.1.3.6.1.4.1.2636.3.15.1.1.24 (jnxCosIfqTotalRedDropByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.25 (jnxCosIfqLpNonTcpRedDropBytes)

.1.3.6.1.4.1.2636.3.15.1.1.26 (jnxCosIfqLpNonTcpRedDropByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.27 (jnxCosIfqLpTcpRedDropBytes)

.1.3.6.1.4.1.2636.3.15.1.1.28 (jnxCosIfqLpTcpRedDropByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.29 (jnxCosIfqHpNonTcpRedDropBytes)

.1.3.6.1.4.1.2636.3.15.1.1.30 (jnxCosIfqHpNonTcpRedDropByteRate)

.1.3.6.1.4.1.2636.3.15.1.1.31 (jnxCosIfqHpTcpRedDropBytes)

.1.3.6.1.4.1.2636.3.15.1.1.32 (jnxCosIfqHpTcpRedDropByteRate)jnxCosFcTable(.1.3.6.1.4.1.2636.3.15.2).1.3.6.1.4.1.2636.3.15.2.1.2 (jnxCosFcQueueNr)

.1.3.6.1.4.1.2636.3.15.2.1.3 (jnxCosRestrictedQNr)

jnxCosFcIdTable(.1.3.6.1.4.1.2636.3.15.3)

.1.3.6.1.4.1.2636.3.15.3.1.2 (jnxCosFcIdToFcName)

.1.3.6.1.4.1.2636.3.15.3.1.3 (jnxCosFcFabricPriority)

jnxCosQstatTable(.1.3.6.1.4.1.2636.3.15.4)

.1.3.6.1.4.1.2636.3.15.4.1.3 (jnxCosQstatQedPkts)

.1.3.6.1.4.1.2636.3.15.4.1.4 (jnxCosQstatQedPktRate)

.1.3.6.1.4.1.2636.3.15.4.1.5 (jnxCosQstatQedBytes)

.1.3.6.1.4.1.2636.3.15.4.1.6 (jnxCosQstatQedByteRate)

.1.3.6.1.4.1.2636.3.15.4.1.7 (jnxCosQstatTxedPkts)

.1.3.6.1.4.1.2636.3.15.4.1.8 (jnxCosQstatTxedPktRate)

.1.3.6.1.4.1.2636.3.15.4.1.9 (jnxCosQstatTxedBytes)

.1.3.6.1.4.1.2636.3.15.4.1.10 (jnxCosQstatTxedByteRate)

.1.3.6.1.4.1.2636.3.15.4.1.11 (jnxCosQstatTailDropPkts)

.1.3.6.1.4.1.2636.3.15.4.1.12 (jnxCosQstatTailDropPktRate)

.1.3.6.1.4.1.2636.3.15.4.1.13 (jnxCosQstatTotalRedDropPkts)

.1.3.6.1.4.1.2636.3.15.4.1.14 (jnxCosQstatTotalRedDropPktRate)

.1.3.6.1.4.1.2636.3.15.4.1.15 (jnxCosQstatLpNonTcpRedDropPkts)

.1.3.6.1.4.1.2636.3.15.4.1.16

kpi for juniper devices

Documents