KPI For Juniper Devices

Key Performance Indicators for Juniper Devices
Page 1 of 92 Partner Engineering Network Management

Key Performance Indicators for
Juniper Devices
Version 2.2

Partner Engineering
Foundation Technologies-Network Management
Juniper Networks


Table of Contents

Key Performance Indicators for Juniper Devices ............................................................... 1
General Disclaimer ............................................................................................................. 4
1 Introduction ................................................................................................................. 5
2 Device Information ..................................................................................................... 5
2.1 Basic Information ................................................................................................. 5
2.2 Interface Information............................................................................................ 9
2.2.1 Determining all the interfaces on the device ............................................... 10
2.2.2 Logical and Physical Interfaces .................................................................. 12
2.2.3 Mapping the logical port to a physical port ................................................ 13
2.2.4 Determining the location of the Port on the device .................................... 14
2.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. .............................................................. 30
2.2.5.4 IPv4 Interfaces on JUNOS devices ..................................................... 42
3 Key Performance Indicators Devices ..................................................................... 43
3.1 CPU Utilization .................................................................................................. 44
3.2 Memory Utilization ............................................................................................ 44
3.3 Disk Utilization .................................................................................................. 44
3.4 Operating Temperature ...................................................................................... 45
4 Key Performance Indicators - Interfaces .................................................................. 45
4.1 Interface Utilization............................................................................................ 46
4.2 Interface related counters ................................................................................... 46
5 Key Performance Indicators - Class of Service ........................................................ 53
5.1 Inbound Traffic per Class ................................................................................... 54
5.2 Output bytes per queue ....................................................................................... 54
5.3 Calculating the Dropped Traffic ........................................................................ 54
5.4 Tail Drop Packets ............................................................................................... 54
5.5 Red Drop Packets ............................................................................................... 55
5.6 Counters for measuring CoS .............................................................................. 55
6 Key Performance Indicators - Routing Protocols ..................................................... 71
6.1 Counters for Routing Protocols .......................................................................... 72
6.1.1 BGP Counters ............................................................................................. 73
6.1.2 OSPF Counters............................................................................................ 74
7 Key Performance Indicators Frame Relay ............................................................. 75
7.1 Frame Relay MIB Objects.................................................................................. 75
7.2 Frame Relay interface and subinterface statistics .............................................. 76
7.3 Circuit Statistics ................................................................................................. 77
8 Key Performance Indicators ATM ......................................................................... 78
8.1 ATM state information ....................................................................................... 78
8.2 ATM statistics for the interface .......................................................................... 78
8.3 Error statistics ..................................................................................................... 79

8.4 Error statistics (SAR) ......................................................................................... 80
8.5 ATM related MIB Objects ................................................................................. 80
9 Key Performance Indicators for MPLS .................................................................... 83
10 Key Performance Indicator for VPN ........................................................................ 83
11 Key Performance Indicators for IP Sec .................................................................... 84
11.1 Key Indicators for IP Sec ................................................................................ 84
11.2 IP Sec Counters .............................................................................................. 85
12 Key Performance Indicators for Pseudowires ........................................................... 87
12.1 Pseudowires Indicators ................................................................................... 87
12.2 VPN and Pseudowire related Counters .......................................................... 87
13 Real Time Performance Management RPM .......................................................... 88
13.1 RPM Indicators ............................................................................................... 88
13.2 RPM related counters ..................................................................................... 89
14 Using the Juniper Utility MIB .................................................................................. 90
15 Using Accounting Profiles ........................................................................................ 92


General Disclaimer
Although 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 may
change the programs or products mentioned at any time without prior notice. Mention of non-Juniper
Networks products or services is for information purposes only and constitutes neither an endorsement nor
a recommendation of such products or services or of any company that develops or sells such products or
services.
ALL INFORMATION PROVIDED IN THIS GUIDE IS PROVIDED AS IS, WITH ALL FAULTS,
AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED OR
STATUTORY. JUNIPER NETWORKS AND ITS SUPPLIERS HEREBY DISCLAIM ALL
WARRANTIES 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 AND
NONINFRINGEMENT, OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
JUNIPER NETWORKS AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR REVENUES, COSTS OF REPLACEMENT GOODS OR
SERVICES, LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OF THE GUIDE OR ANY
JUNIPER NETWORKS PRODUCT OR SERVICE, OR DAMAGES RESULTING FROM USE OF OR
RELIANCE ON THE INFORMATION PROVIDED IN THIS GUIDE, EVEN IF JUNIPER NETWORKS
OR 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 subject
to, written software licenses and limited warranties. Those licenses and warranties provide the purchasers
of those products with certain rights. Nothing in this guide shall be deemed to expand, alter, or modify any
warranty or license or any other agreement provided by Juniper Networks with any Juniper Networks
product, or to create any new or additional warranties or licenses.


1 Introduction

This document describes the MIB OIDs that can be polled on Juniper Devices to describe
performance of these devices. The document lists all the OIDs that act as Key
Performance Indicators for any JUNOS Device. The document also lists the indicators in
terms 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 common
across all Juniper platforms. The indicators related to CoS, ATM, Frame Relay and IP
Sec depend on the platforms.

Some of the basic performance indicators mentioned in the document directly map to an
OID 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 System
Details, Details about the Device Inventory and the CPU and the Temperature readings
for those Inventory Items. Also included are High Availability features related data like
VRRP and Virtual Chassis related statistics for EX Series.

The below mentioned System Identification identifiers help in indentifying the type
Juniper Device, and its name.


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 the
system can be obtained using the following counters. This provides the operating status
of subjects of interest in the device.

The Juniper MIB (Juniper Enterprise Specific MIB: Chassis MIB jnx-chassis) provides
generic information about the device like device description, and the operating status of
the device. The operating status information includes the operating state of each item on
the device, namely the box contents. The box contents include the mid-plane, Power
Supply, 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 by
querying 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, Operating
Temperature and Operating state of each item on a M7i Router.


The hardware inventory and the associated details such as the temperature details can be
fetched 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 different
MIB to fetch the basic device details.

JUNIPER-SYRAH-STATISTICS-MIB
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)


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)


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 Juniper
devices. This gives instructions for discovering Physical and logical interfaces in details.
The Interface family and interface address depends on what protocol is configured and
used. This document gives examples for L2 switching interfaces and IPv4 addresses as
examples 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 the
sequence depending on their algorithm and the MIB OID.


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 interfaces
corresponding 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 ipAddrTable
for 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. Using
the ifType , one can determine what interface type it is

Example:

regress@EX4200-2> show snmp mib walk ifDescr
ifDescr.4 = lsi
ifDescr.5 = dsc
ifDescr.6 = lo0
ifDescr.7 = tap
ifDescr.8 = gre
ifDescr.9 = ipip
ifDescr.10 = pime
ifDescr.11 = pimd
ifDescr.12 = mtun
ifDescr.33 = me0-----Management port
ifDescr.34 = me0.0
ifDescr.35 = vme
ifDescr.36 = vme.0
ifDescr.37 = bme0
ifDescr.38 = bme0.32768
ifDescr.49 = vcp-0
ifDescr.50 = vcp-0.32768
ifDescr.51 = vcp-1
ifDescr.52 = vcp-1.32768
ifDescr.116 = ge-0/0/0
ifDescr.117 = ge-0/0/1Find ifType with ifIndex 117
ifDescr.118 = ge-0/0/10


ifDescr.119 = ge-0/0/11
ifDescr.120 = ge-0/0/12
ifDescr.121 = ge-0/0/13
ifDescr.122 = ge-0/0/14
ifDescr.123 = ge-0/0/15
ifDescr.124 = ge-0/0/16
ifDescr.125 = ge-0/0/17
ifDescr.126 = ge-0/0/18
ifDescr.127 = ge-0/0/19
ifDescr.129 = ge-0/0/20
ifDescr.130 = ge-0/0/21
ifDescr.131 = ge-0/0/22
ifDescr.132 = ge-0/0/23
ifDescr.166 = vlan
ifDescr.193 = ge-0/0/0.0
ifDescr.194 = ge-0/0/1.0- Find ifType with ifIndex 194
ifDescr.195 = ge-0/0/2.0
ifDescr.196 = ge-0/0/3.0
ifDescr.197 = ge-0/0/4.0
ifDescr.198 = ge-0/0/5.0
ifDescr.200 = ge-0/0/7.0
ifDescr.202 = ge-0/0/9.0
ifDescr.203 = ge-0/0/10.0
ifDescr.204 = ge-0/0/11.0
ifDescr.205 = ge-0/0/12.0
ifDescr.206 = ge-0/0/13.0
ifDescr.207 = ge-0/0/15.0
ifDescr.208 = ge-0/0/16.0
ifDescr.209 = ge-0/0/17.0
ifDescr.210 = ge-0/0/18.0
ifDescr.211 = ge-0/0/19.0
ifDescr.212 = ge-0/0/20.0
ifDescr.213 = ge-0/0/21.0
ifDescr.214 = ge-0/0/22.0
ifDescr.215 = ge-0/0/23.0
ifDescr.219 = ge-0/0/16.10

ifDescr.220 = ge-0/0/17.20
ifDescr.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.194
ifType.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 value
of the ifChassisLogicalUnit. If the value is 1 then it is Logical else its physical This Table
is indexed by ifIndex of the interfaces, You can see below that for IfIndex 194, the
ifChassisLogicalUnit is 1 meaning that this is a logical interface whereas with 117 is 0.

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


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

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

{master:0}
ifDescr.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 value
of 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 this
is 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. 193
ifDescr. 194 = ge-0/0/1.0
Note 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 the
ifLowerLayerIndex.
This value will give you the ifDescr of the physical port associated with the logical port.


Now walk the ifStackTable, and get the ifStackStatus whose ifHigherIndex value
matches the IfIndex value
That is get the ifStackStatus value whose ifHigherIndex value is 194.

regress@Ex3200-test> show snmp mib get ifStackStatus. 194.117
ifStackStatus. 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 port
corresponding to the logical port.

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

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 the
ifChassisLogicalUnit entry equal to 1.

This approach can be used for any logical interface to determine the corresponding
physical 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 device
itself, PIC , FPC. The JUNOS has a specific Anatomy to determine the location of each
and every component on the device like Fan, Card , Power Supply etc. JUNOS devices
support Juniper specific enterprise MIB called Chassis MIB to find out the physical
components 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 the
ifChassisTable from the jnx-if-extensions.mib. Using the ifChassisPicIndex one can
determine the PIC to which the port belongs to


The ifChassisTable gives the index or indices for the Chassis MIB tables. This is the
instance index which keys into the jnxContentsTable in Chassis MIB.For example, it
could 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 if
nonzero) port number whatever (fourth digit currently unused) - which in turn
could 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 PIC
concentrators which hold one or more PICs(cards). Please see the FPC and PICs
highlighted.
regress@M7i-1> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis J1747 M7i
Midplane REV 05 710-008761 VF1791 M7i Midplane
Power Supply 0 Rev 08 740-008537 UK58001 AC Power Supply
Routing Engine REV 02 740-021833 9009005164 RE-5.0
CFEB REV 10 750-010463 VD3039 Internet Processor II
FPC 0 E-FPC
PIC 0 REV 12 750-012838 VE8559 4x 1GE(LAN), IQ2
Xcvr 0 REV 01 740-011783 PCQ08MC SFP-LX10
PIC 1 REV 12 750-012838 VE8543 4x 1GE(LAN), IQ2
Xcvr 0 REV 01 740-011783 PCQ08LM SFP-LX10
Xcvr 2 REV 01 740-011614 AC0810S00T8 SFP-LX10
FPC 1 E-FPC
PIC 2 BUILTIN BUILTIN 1x Tunnel
PIC 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 as
seen in ifChassisLogicalUnit.138 = 1. Let us first deduce the Physical Port of this logical
port as described previously.


MIB Value from the device M7i displayed
above
Description
ifStackStatus.138.125 = 1 IfIndex 138 is on ifIndex 125

regress@M7i-1> show snmp mib get
ifDescr.125
IFIndex 125 refers to ge-0/1/2, which is the
physical port housing the logical port ge-
0/1/2.0
ifChassisFpc.125 = 1

ifChassisFpc.138 = 1

The number of the FPC card on which the
interface
is located in the chassis. It is the chassis
slot
in which the FPC card is installed for the
specified
interface.

Although the number is labeled from 0 and
up in the
chassis, the return value for this object
always starts
from 1 according to Network Management
convention. Therefore, a value of zero
means there is no real or physical FPC
associated with the specified interface.
NM Systems need to subtract 1 from the
value here.
So Port 125 and 138 are on FPC 0.


ifChassisPic.125 = 2

ifChassisPic.128 = 2

The number of the PIC card on which the
interface
is located in the chassis. It is the PIC
location
on the FPC card for the specified interface.

Although the number is labeled from 0 and
up in the
chassis, the return value for this object
always starts
from 1 according to Network Management
convention. Therefore, a value of zero
means there is no real or physical PIC
associated with the specified interface.

value 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 on
which the
interface is located in the chassis. It is the
port
number on the PIC card for the specified
interface.

value here.
The port location here is 2.

ifChassisChannel.125 = 0

ifChassisChannel.138 = 0

The channel identifier for the specified
interface
if and only if it is part of a channelized
interface.
This is mostly for OC3 channelized
interfaces.

Its not applicable in this example.


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 into
jnxContentsTable in the Chassis MIB.
For example, the octet string of 8.1.2.0
means a PIC ( 8& first digit) at FPC slot
0 (11 , second digit minus one if
nonzero) PIC number 1 (21 , third digit)
minus one if nonzero port number,
whatever (fourth digit currently unused). In
turn, this PIC index can be plugged in by
the NMS directly after any MIB objects in
the jnxContentsTable obtain that PIC
object for the specified interface. This
object is valid only for interfaces having
real and physical PIC cards. Otherwise, it
returns an octet string 0.0.0.0.

Now, let us use the jnxContentsTable and jnxContainers Tables to locate the FPCs and
the 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 displayed
above
Description
jnxContainersTable
jnxBoxClass.0 = jnxProductLineM7i.0
jnxBoxDescr.0 = Juniper M7i Internet
Backbone Router
jnxBoxSerialNo.0 = J1747
jnxBoxInstalled.0 = 208876600
These variables give the Product Line of
Juniper which is M7i and Box serial
number with Box install date.
jnxContainersIndex.1 = 1
jnxContainersIndex gives the Index for
each component


jnxContainersView.1 = 1

The view(s) from which the specific
container appears.
The various values representing the bit
positions
and its corresponding views are:
1 front
2 rear
4 top
8 bottom
16 leftHandSide
32 rightHandSide

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

The container housing the entry at the next-
higher level of the jnxContainersEntry
object, whose object identifier is
{jnxContainersEntry 4}.
For example, the within value for
jnxMediaCardSpacePIC.0 is 7. Because the
jnxM7iSlotFPC.0 retains an index value of
7, the FPC houses the PIC.
jnxContainersType.1 = jnxChassisM7i.0
jnxContainersType.2 = jnxM7iSlotPower.0
jnxContainersType.4 = jnxM7iSlotFan.0
jnxContainersType.6 = jnxM7iSlotCFEB.0
jnxContainersType.7 = jnxM7iSlotFPC.0
jnxContainersType.8 =
jnxM7iMediaCardSpacePIC.0
jnxContainersType.9 = jnxM7iSlotRE.0

The type of this container.
This says what the Container Type is for a
given Container Index. For example:
Container Index 8 refers to
jnxM7iMediaCardSpacePIC.0 which refers
to the PICs on M7i.
jnxContainersDescr.1 = chassis frame
jnxContainersDescr.2 = Power Supply slot
jnxContainersDescr.4 = FAN slot
jnxContainersDescr.6 = CFEB slot
jnxContainersDescr.7 = FPC slot
jnxContainersDescr.8 = PIC slot
jnxContainersDescr.9 = Routing Engine slot
The name or detailed description of this
subject.

Take notice, Container index is for FPC
and 8 for PIC here.


jnxContainersCount.1 = 1
The maximum number of containers of this
level per container of the next higher level.
e.g. if there are six level 2 containers in
level 1 container, then
jnxContainersCount for level 2 is six. The
maximum number of a given component
that the router can accommodate within the
jnxContainersEntry object

For example: Container Index 8 i.e. PIC
show 4 here. This means there can be
maximum of 4 PICs within a FPC on M7i.
jnxContentsTable A list of contents entries. This represents
the contents on a Chassis.

jnxContentsContainerIndex.7.1.0.0 = 7

jnxContentsContainerIndex.8.1.2.0 = 8

The associated jnxContainersIndex in the
jnxContainersTable.

The container Index of 8.1.2.0 is 8 which is
nothing but representing a PIC.
jnxContainersDescr.8 = PIC slot

The container Index of 7.1.0.0 is 7 which is
nothing but FPC.
jnxContainersDescr.7 = FPC slot


jnxContentsL1Index.7.1.0.0 = 1



The level-one index of the container
housing the component, whose 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.

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.

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

Now, the L1 Index for
jnxContentsL1Index.8.1.2.0 = 1 i.e. 0 (1-1).
The jnxContainersLevel.8=2 which means
the component represented by index 8.1.2.0
is at Level 2. Now, Level 1 index for this
component is 0.
To find out which is the Level 1
component housing this Level 2, use the
jnxContainersWithin.8 = 7 (see above).
This indicates that Container Index of the 7
(FPC) houses Container index 8(PIC).
Therefore , look for a jnxContentsTable
entry with index container index 7 and the
Level 1 index 1.
There are two such entries
7.1.0.0
7.1.1.0
Which is the correct one will be clarified
next step




The level-two index of the container
housing the component, whose 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.

The L2 Index of 7.1.0.0 is 0 which is not
applicable.

The L2 position of 8.1.2.0 is 1 (2-1) and
the jnxContainersLevel.8=2 which means
any component with starting index 8(PIC)
is at Level 2 therefore L2 Index represents
the position of the component itself. So
component represented by 8.1.2.0 is PIC 1.
This also means one of the L1 components
houses this L2 component. As seen above,
8.1.2.0 is housed by container index 7 and
L1 Index 1, we got 7.1.0.0 and 7.1.1.0.
Now, the L2 index of 7.1.1.0 is 1 which
means this component has a Level 1 Index
of 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 you
should note that jnxContainersLevel.7 = 1
which is any component with index 7 is at
level 1(FPC) itself, so here L2 Index refers
to something within(part of) the L1
component.

Conclusion is,
If jnxContainersLevel=1 and L2 Index has
a non zero value then the component is part
of the Level 1 component represented by
L1 Index. e.g. 7.1.1.0
If jnxContainersLevel=2 and L2 Index has
a non zero value then the component is
Housed by a Level 1 component
represented by a L1 Index value. E.g.
8.1.2.0
Also, the entry representing the L1

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


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

jnxContentsType.7.1.0.0 = jnxM7iFPC.0

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

The type of this subject. So 7.1.0.0
represents a FPC , 7.1.1.0 represents the
Temperature sensor of the FPC and 8.1.2.0
is 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: 4x
1GE(LAN), IQ2 @ 0/0/*
jnxContentsDescr.8.1.2.0 = PIC: 4x
1GE(LAN), IQ2 @ 0/1/*

The name or detailed description of this
subject.
jnxContentsChassisId.7.1.1.0 = 2


Identifies the chassis on which the contents
of this
row 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 is
housed in 7.1.0.0 and we have detailed descriptions of the component as below


2.2.5 Protocol Specific

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

2.2.5.1 BRIDGE Ports on JUNOS devices

The JUNIPER EX and MX devices support Switching. As per IEEE802.1D , the RFC
4188 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 be
determined as below
dot1dBaseBridgeAddress.0 = 00 1f 12 32 b7 80
dot1dBaseNumPorts.0 = 21
dot1dBaseType.0 = 2
dot1dBasePort.34 = 34
FPC (7.1.0.0): FPC: @
0/*/*

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

ge-0/1/2
ge-0/1/2.0

dot1dBasePortIfIndex.34 = 34

You walk the dot1dBasePortTable and get the dot1dBasePortIfIndex.
Example, you walk the dot1dBasePortTable and note the dot1dBasePortIfIndex 118.
regress@Ex3200-test> show snmp mib get dot1dBasePortIfIndex.118

Get the corresponding ifDescr for the dot1dBasePortIfIndex value.
regress@Ex3200-test> show snmp mib get ifDescr.118
ifDescr.118 = ge-0/0/0.0


Note that this corresponds to the logical interface ge-0/0/0.0 Therefore, for EX, by default
you 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 ports
and NOT logical.

regress@MX240-2> show snmp mib walk dot1dBase
dot1dBaseBridgeAddress.0 = 00 21 59 ad 57 d0
dot1dBasePortIfIndex.41 = 117- IfIndex of Bridge Port 41 is 117
dot1dBasePortCircuit.41 = 0.0
dot1dBasePortDelayExceededDiscards.41 = 0
dot1dBasePortMtuExceededDiscards.41 = 0

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

regress@MX240-2> show snmp mib get ifDescr.117

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

2.2.5.2 Spanning Tree Ports on JUNOS devices

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

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


Querying for VSTP requires a different community string from SNMP. <routing-
instance-name>:: VLAN-ID@ communitystring.
MX and EX support RFC 4318 for RSST Ports.
MSTP is supported by Juniper Networks Enterprise-Specific Multiple Instance Multiple
Spanning 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 some
bug fixes have been done for STP tables from JUNOS 9.5 which is captured here.
2.2.5.2.1 STP Spanning Tree

The following is an example from EX4200 device

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

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


dot1dStpPortEnable.193 = 1
dot1dStpPortPathCost.193 = 20000
dot1dStpPortDesignatedRoot.193 = 20 00 00 1f 12 32 b7 80
dot1dStpPortDesignatedCost.193 = 0


dot1dStpPortDesignatedBridge.193 = 20 00 00 1f 12 32 b7 80
dot1dStpPortDesignatedPort.193 = 10 c1
dot1dStpPortDesignatedPort.195 = 20 c3
dot1dStpPortDesignatedPort.204 = 80 cc
dot1dStpPortDesignatedPort.205 = 80 cd
dot1dStpPortForwardTransitions.193 = 2806
dot1dStpPortPathCost32.193 = 20000
dot1dStpVersion.0 = 2
dot1dStpTxHoldCount.0 = 6
dot1dStpPortProtocolMigration.193 = 2
dot1dStpPortAdminEdgePort.193 = 2
dot1dStpPortOperEdgePort.193 = 2
dot1dStpPortAdminPointToPoint.193 = 2
dot1dStpPortOperPointToPoint.193 = 1
dot1dStpPortAdminPathCost.193 = 20000


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 as
below.

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

{master:0}
ifDescr.193 = ge-0/0/0.0

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

2.2.5.3 RSTP Rapid Spanning Tree.

The following example is from MX device for RSTP configuration

regress@MX240-2> show snmp mib walk dot1dStpVersion

regress@MX240-2> show snmp mib walk dot1dStp
dot1dStpProtocolSpecification.0 = 3
dot1dStpPriority.0 = 32768
dot1dStpTimeSinceTopologyChange.0 = 7789700
dot1dStpTopChanges.0 = 3
dot1dStpDesignatedRoot.0 = 20 00 00 1f 12 32 b7 80
dot1dStpRootCost.0 = 20000
dot1dStpRootPort.0 = 41
dot1dStpMaxAge.0 = 2000
dot1dStpHelloTime.0 = 200
dot1dStpHoldTime.0 = 100
dot1dStpForwardDelay.0 = 1500
dot1dStpBridgeMaxAge.0 = 2000
dot1dStpBridgeHelloTime.0 = 200
dot1dStpBridgeForwardDelay.0 = 1500


dot1dStpPortDesignatedPort.41 = 12 01
dot1dStpTxHoldCount.0 = 6

Lets take RSTP port
regress@MX240-2> show snmp mib get dot1dBasePortIfIndex.41


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

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

regress@MX240-2> show snmp mib walk dot1dStpExtPortTable

NOTE ON Port Identifiers


This is applicable to MX and EX wherever port identifier is encoded. EX supports this
from JUNOS 9.5 ONLY

The Port Identifier will be encoded as per the below clause from IEEE802.1D-2004. The
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 priority component was 8 bits and
the Port Number component also 8 bits). This change acknowledged that modern
switched LAN infrastructures call for increasingly large numbers of Ports to be supported
in a single Bridge. To maintain management compatibility with older implementations,
the priority component is still considered, for management purposes, to be an 8-bit value,
but the values that it can be set to are restricted to those where the least significant 4 bits
are zero (i.e., only the most significant 4 bits are settable).
Example: dot1dStpDesginatedPort uses this encoding. Please note it is encoded in steps
of 16.
From the RSTP example above, dot1dStpPortDesignatedPort.41 = 12 01 which is
0001 0010 0000 0001 in Binary. Taking the most significant 4 bits only for priority will
be 2^4 =16
. The 12 bits used for port will return the value 2^9 + 2^0=512+1 =513. So the
Designated port number is 513 and priority is 16 which is true as shown below

CLAUSE from IEEE802.1D 2004
9.2.7 Encoding of Port Identifiers
A Port Identifier shall be encoded as two octets, taken to represent an unsigned binary
number. If two Port Identifiers are numerically compared, the lesser number denotes the
Port of better priority. The more significant octet of a Port Identifier is a settable priority
component that permits the relative priority of


Ports on the same Bridge to be managed (17.13.7 and Clause 14). The less significant
twelve bits is the Port Number expressed as an unsigned binary number. The value 0 is
not 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 priority
component was 8 bits and the Port Number component also 8 bits). This change
acknowledged that modern switched LAN infrastructures call for increasingly large
numbers of Ports to be supported in a single Bridge. To maintain management
compatibility with older implementations, the priority component is still considered, for
management purposes, to be an 8-bit value, but the values that it can be set to are
restricted to those where the least significant 4 bits are zero (i.e., only the most significant
4 bits are settable).
regress@MX240-2> show spanning-tree interface
Spanning tree interface parameters for instance 0
Interface Port ID Designated Designated Port State Role
port ID bridge ID Cost
ge-1/0/0 128:41 16:513 8192.001f1232b780 20000 FWD ROOT
ge-1/0/1 128:42 32:515 8192.001f1232b780 20000 BLK ALT
2.2.5.3.1 VSTP VLAN Spanning Tree
VLAN Spanning MIBS are supported only for MX. Please note the same dot1dStpTable is
supported 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 Services
router), 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 routing
instance, include default::10@public in the context (SNMPv3) or community (SNMPv1
or v2) string.

Example: Spanning tree interface parameters for VLAN 10

Interface Port ID Designated Designated Port State Role
port ID bridge ID Cost
ge-1/0/0 128:41 128:41 32778.002159ad57d0 20000 FWD DESG
So to query for VSTP for VLAN Id 10, we need to use default::10@public the following
for SNMP querying. Default is the default routing instance
Following is the output of the dot1dStpTable for VSTP


$ snmpwalk -v1 -c default::10@public 116.197.178.7 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

2.2.5.3.2 MSTP Multiple Spanning Tree
MIMMSTP MIBS are supported only on MX platform as of now. EX has supported this
for long but with some port indexing issue which is resolved in JUNOS 9.5. These are
JUNIPER specific MIBs , please see
http://www.juniper.net/techpubs/software/junos/junos94/swconfig-net-mgmt/interpreting-
the-enterprise-specific-mimstp-mib.html#chap-mimstp-mib for more details. This
section 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 Spanning
Tree Instance (MSTI) is identified by a number.


The Common Instance Spanning Tree (CIST) is always MSTI ID 0. Each instance of an
MSTI can be numbered 1 through 64. MSTI IDs are local to each region.

regress@MX240-2> show spanning-tree mstp configuration detail
MSTP configuration information
Context identifier : 0
Revision : 0
Configuration digest : 0xd2b171a8ad95f593c241fc33d419a88c

MSTI Member VLANs
0 0-9,11-4094
10 10

regress@MX240-2> show spanning-tree bridge
STP bridge parameters
Routing instance name : GLOBAL
Context ID : 0
Enabled protocol : MSTP

STP bridge parameters for CIST
Root ID : 32768.00:1f:12:32:b7:80
Root cost : 20000
Root port : ge-1/0/0
CIST regional root : 32768.00:21:59:ad:57:d1
CIST internal root cost : 0
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Hop count : 20
Message age : 1
Number of topology changes : 2
Time since last topology change : 260 seconds
Local parameters
Bridge ID : 32768.00:21:59:ad:57:d1

STP bridge parameters for MSTI 10
MSTI regional root : 32778.00:21:59:ad:57:d1
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 2


Time since last topology change : 260 seconds
Local parameters
Bridge ID : 32778.00:21:59:ad:57:d1

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

regress@MX240-2> show spanning-tree interface detail
Interface name : ge-1/0/0

Port identifier : 128.41
Designated port ID : 128.513
Port cost : 20000
Port state : Forwarding
Designated bridge ID : 32768.00:1f:12:32:b7:80
Port role : Root
Link type : Pt-Pt/NONEDGE
Boundary port : Yes


Interface name : ge-1/0/0
Port identifier : 128.41
Designated port ID : 128.41
Port cost : 20000
Port state : Forwarding
Designated bridge ID : 32768.00:21:59:ad:57:d1
Port role : Master
Link type : Pt-Pt/NONEDGE
Boundary port : Yes

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

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

jnxMIMstCistRoot.0 = 80 00 00 1f 12 32 b7 80
jnxMIMstCistRegionalRoot.0 = 80 00 00 21 59 ad 57 d1

jnxMIMstCistRootCost.0 = 20000
jnxMIMstCistRegionalRootCost.0 = 0
jnxMIMstCistRootPort.0 = 41------ Root port is dot1dBasePort 41
jnxMIMstCistBridgePriority.0 = 32768
jnxMIMstCistBridgeMaxAge.0 = 2000
jnxMIMstCistBridgeForwardDelay.0 = 1500
jnxMIMstCistHoldTime.0 = 100
jnxMIMstCistMaxAge.0 = 2000
jnxMIMstCistForwardDelay.0 = 1500
jnxMIMstMstpUpCount.0 = 2
jnxMIMstMstpDownCount.0 = 1
jnxMIMstPathCostDefaultType.0 = 2
jnxMIMstTrace.0 = 0
jnxMIMstDebug.0 = 0
jnxMIMstForceProtocolVersion.0 = 3
jnxMIMstTxHoldCount.0 = 3
jnxMIMstMstiConfigIdSel.0 = 0
jnxMIMstMstiRegionName.0 = 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
jnxMIMstMstiRegionVersion.0 = 0
jnxMIMstMstiConfigDigest.0 = d2 b1 71 a8 ad 95 f5 93
jnxMIMstBufferOverFlowCount.0 = 0
jnxMIMstMemAllocFailureCount.0 = 0


jnxMIMstRegionConfigChangeCount.0 = 2
jnxMIMstCistBridgeRoleSelectionSemState.0 = 1

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

jnxMIMstMstiBridgeTable- Table containing Bridge Information specific to Spanning
Tree 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 jnxMIMstMstiBridgeTable
jnxMIMstMstiInstanceIndex.0.10 = 10
jnxMIMstMstiBridgeRegionalRoot.0.10 = 80 00 00 21 59 ad 57 d1
jnxMIMstMstiBridgePriority.0.10 = 32768
jnxMIMstMstiRootCost.0.10 = 0
jnxMIMstMstiRootPort.0.10 = 0
jnxMIMstMstiTimeSinceTopologyChange.0.10 = 1241
jnxMIMstMstiTopChanges.0.10 = 2
jnxMIMstMstiNewRootBridgeCount.0.10 = 0
jnxMIMstMstiBridgeRoleSelectionSemState.0.10 = 1
jnxMIMstInstanceUpCount.0.10 = 1
jnxMIMstInstanceDownCount.0.10 = 0
jnxMIMstOldDesignatedRoot.0.10 = 00 00 00 00 00 00 00 00

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

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


jnxMIMstCistPortAdminP2P.41 = 2
jnxMIMstCistPortOperP2P.41 = 1
jnxMIMstCistPortAdminEdgeStatus.41 = 2
jnxMIMstCistPortOperEdgeStatus.41 = 2
jnxMIMstCistPortProtocolMigration.41 = 2
jnxMIMstCistPortState.41 = 5
jnxMIMstCistForcePortState.41 = 1
jnxMIMstCistPortForwardTransitions.41 = 2
jnxMIMstCistPortRxMstBpduCount.41 = 0
jnxMIMstCistPortRxRstBpduCount.41 = 0
jnxMIMstCistPortRxConfigBpduCount.41 = 848
jnxMIMstCistPortRxTcnBpduCount.41 = 0
jnxMIMstCistPortTxMstBpduCount.41 = 9
jnxMIMstCistPortTxRstBpduCount.41 = 0
jnxMIMstCistPortTxConfigBpduCount.41 = 0
jnxMIMstCistPortTxTcnBpduCount.41 = 1
jnxMIMstCistPortInvalidMstBpduRxCount.41 = 0
jnxMIMstCistPortInvalidRstBpduRxCount.41 = 0
jnxMIMstCistPortInvalidConfigBpduRxCount.41 = 0
jnxMIMstCistPortInvalidTcnBpduRxCount.41 = 0
jnxMIMstCistPortTransmitSemState.41 = 5

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

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




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

jnxMIMstMstiPortPathCost.41.10 = 20000
jnxMIMstMstiPortPriority.41.10 = 128
jnxMIMstMstiPortDesignatedRoot.41.10 = 80 00 00 21 59 ad 57 d1
jnxMIMstMstiPortDesignatedBridge.41.10 = 80 00 00 21 59 ad 57 d1
jnxMIMstMstiPortDesignatedPort.41.10 = 80 29
jnxMIMstMstiPortState.41.10 = 5
jnxMIMstMstiForcePortState.41.10 = 1
jnxMIMstMstiPortForwardTransitions.41.10 = 2
jnxMIMstMstiPortReceivedBPDUs.41.10 = 0
jnxMIMstMstiPortTransmittedBPDUs.41.10 = 5
jnxMIMstMstiPortInvalidBPDUsRcvd.41.10 = 0
jnxMIMstMstiPortDesignatedCost.41.10 = 0
jnxMIMstMstiSelectedPortRole.41.10 = 5
jnxMIMstMstiCurrentPortRole.41.10 = 5
jnxMIMstMstiPortInfoSemState.41.10 = 8
jnxMIMstMstiPortRoleTransitionSemState.41.10 = 3
jnxMIMstMstiPortStateTransitionSemState.41.10 = 2
jnxMIMstMstiPortTopologyChangeSemState.41.10 = 2
jnxMIMstMstiPortEffectivePortState.41.10 = 1

The jnxMIMstCistPortProtectTable defines the jnxMIMstCist Port Table for providing
extensions for Root Protect and Loop Protect to the corresponding
jnxMIMstCistPortTable entry.

jnxMIMstCistPortRootProtectEnabled.41 = 2
jnxMIMstCistPortRootProtectState.41 = 0

The jnxMIMstMstiPortProtectTable defines the jnxMIMstMsti Port Table for providing
extensions for Root Protect and Loop Protect to the corresponding
jnxMIMstMstiPortTable entry.


jnxMIMstMstiPortRootProtectState.41.10 = 0
jnxMIDot1sJnxMstSetGlobalTrapOption.0 = 0

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

jnxMIMstMapVlanIndex.0.10 = 1
jnxMIMstUnMapVlanIndex.0.10 = 1
jnxMIMstSetVlanList.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 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 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 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00
jnxMIMstResetVlanList.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 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 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 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00
00
jnxMIMstInstanceVlanMapped.0.10 = 00 40 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00
jnxMIMstInstanceVlanMapped2k.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 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 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 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 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 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 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 00

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

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

2.2.5.4 IPv4 Interfaces on JUNOS devices

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

ipAdEntIfIndex.116.197.178.6 = 36

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


NetMask for this address is /24 as seen below

ipAdEntNetMask.172.25.27.2 = 255.255.255.0

ifDescr.220 = ge-0/0/17.20

regress@EX4200-2> show interfaces terse |grep ge-0/0/17.20
ge-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 of
172.25.27.2/24.

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

ifStackStatus.220.125 = 1

ifDescr.125 = ge-0/0/17

3 Key Performance Indicators Devices
Device Availability- Percentage of time that the device responds to a SNMP request
Device Latency - The latency measures the round-trip delay (in milliseconds) when a
ping 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)


3.1 CPU Utilization

The CPU utilization can be determined by reading the appropriate instance of the OID
jnxOperatingCPU. 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 CPU
accumulated times every 5 seconds from kernel and computes percentage of CPU
utilization over this 5 second interval. Chassis daemon does not compute CPU utilization
at CLI or SNMP query time. It provides the cached value that was computed at the end of
last 5-second period. Kernel accumulates times (actual ticks) for these states at clock
interrupt intervals (it charges that tick to one of these states). Chassis daemon reads these
accumulated times from kernel memory location once every 5 seconds. It then subtracts
the last values thus giving CPU usages since last interval for each CPU state. Percentage
is computed by 100 x CPU-USAGE [CPU-STATE]/total where total is the sum of CPU
time for all states.

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

3.2 Memory Utilization

This jnxOperatingBuffer is the memory utilization and is computed as (total memory -
free memory)/total memory. For percentage, multiply above fraction with 100. Buffer
utilization 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 report
memory utilization in BSD/Junos kernel running on routing engine. Each PFE has its
own memory independent of any other PFE memory. If you want to average, average the
memory utilization of each PFE over duration by taking multiple samples over time. For
example, one cannot average routing engine memory utilization with FPC memory
utilization and provide one result.

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


3.4 Operating Temperature
The operating temperature can be obtained by reading the jnxOperatingTemp.
This is the temperature in Celsius (degrees C) of the component on the JUNOS device
and is zero if unavailable or inapplicable.
4 Key Performance Indicators - Interfaces
The Interface Performance includes the monitoring of both Physical and Logical
interfaces on the device. The ifTable defined in RFC 1213 lists both the physical as well
as the logical interfaces that are present in the device. The ifIndex corresponds to both
Logical 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 Status
This includes the operational status and the administration status of the interface.
Interface operating status is indicated by ifOperStatus
Interface Admin status is indicated by ifAdminStatus
Interface Utilization
Indicates the normal utilization of the interface observed over the last 7 days for this
interface. Normal utilization is based on the hourly maximum value of the inbound and
outbound traffic as a percentage of the interface bandwidth.
The interface utilization is calculated as (ifInOctets + ifOutOctets) * 8 *100 / ifSpeed
Number of Errors on the interface
This is a sum of the number of inbound packets that contained errors, preventing them
from being delivered and the number of outbound packets that contained errors,
preventing them from being transmitted
Number of Errors = ifInErrors + ifOutErrors
Total number of Collisions
This states the number of output collisions detected on the interface.
The OID ifJnxCollisions in the Juniper IF MIB denotes the number of collisions.
Total number of discards
Number of packets discarded, even though no errors were detected
Number of discards = ifInDiscards + ifOutDiscards
Number of packets discarded because of unknown protocol
This number of inbound packets discarded because they were of an unknown protocol.
This is indicated by ifInUnknownProtos in ifTable in MIB 2


Number of Unicast versus Multicast packets
This is calculated as the ratio of the sum of total number of unicast packets (sum of
number of unicast packets going out and coming in) and the sum of the number of
multicast packets (number of multicast packets going out and coming in).
(ifInUcastPkts + ifOutUcastPkts ) /( ifInNUcastPkts + ifOutNUcastPkts )
4.1 Interface Utilization
In order to calculate the interface utilization, you have to consider what kind of
connection you have. The connection can be half-duplex or full-duplex. LAN
connections tend to be half-duplex, while the WAN connections tend to be full-duplex.
In order correctly calculate and report the interface utilization, you need to collect the
number of octets that was transmitted in to the interface and the number of octets that
were transmitted out of the interface.

The interface utilization is calculated as (ifInOctets + ifOutOctets) * 8 *100 / ifSpeed

4.2 Interface related counters
The following counters are available to determine the Key Performance Indicators for
Logical as well as Physical Interfaces.

Interface
ifIndex(.1.3.6.1.2.1.2.2.1.1)
ifDescr(.1.3.6.1.2.1.2.2.1.2)
ifType(.1.3.6.1.2.1.2.2.1.3)
ifMtu(.1.3.6.1.2.1.2.2.1.4)
ifSpeed(.1.3.6.1.2.1.2.2.1.5)
ifPhysAddress(.1.3.6.1.2.1.2.2.1.6)
ifAdminStatus(.1.3.6.1.2.1.2.2.1.7)
ifOperStatus(.1.3.6.1.2.1.2.2.1.8)
ifLastChange(.1.3.6.1.2.1.2.2.1.9)
ifInOctets(.1.3.6.1.2.1.2.2.1.10)
ifInUcastPkts(.1.3.6.1.2.1.2.2.1.11)
ifInNUcastPkts(.1.3.6.1.2.1.2.2.1.12)
ifInDiscards(.1.3.6.1.2.1.2.2.1.13)
ifInErrors(.1.3.6.1.2.1.2.2.1.14)
ifInUnknownProtos(.1.3.6.1.2.1.2.2.1.15)
ifOutOctets(.1.3.6.1.2.1.2.2.1.16)
ifOutUcastPkts(.1.3.6.1.2.1.2.2.1.17)
ifOutNUcastPkts(.1.3.6.1.2.1.2.2.1.18)
ifOutDiscards(.1.3.6.1.2.1.2.2.1.19)
ifOutErrors(.1.3.6.1.2.1.2.2.1.20)


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)


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.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)


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)


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)


.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)


.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)


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 you
must 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, include
all customer traffic from a specific ingress edge interface within one class, or
include all packets of a particular protocol such as voice over IP (VoIP).
Identify the required deterministic behavior for each class. For example, if VoIP
is important, give VoIP traffic the highest priority during times of network
congestion. Conversely, you can downgrade the importance of Web traffic during
congestion, 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 more
deterministic way at egress interfaces, typically by applying different queuing
mechanisms for each class during times of network congestion. You can collect
information from the network to provide customers with reports showing how the
network 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 counter
jnxFWCounterPacketCount
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
jnxCosIfqTxedPkts
The number of tail-dropped or RED-dropped packets per interface per forwarding
class
You can calculate the amount of dropped traffic by subtracting the outbound traffic from
the incoming traffic: Dropped = Inbound Counter Outbound Counter
jnxCosIfqTailDropPkts & jnxCosIfqTotalRedDropPkts


5.1 Inbound Traffic per Class
This measures the number of bytes being counted pertaining to the specified firewall
filter counter.

The jnxFirewalls MIB defines the jnxFirewallCounterTable that provides information
about the number of bytes being counted pertaining to specific firewall filter counter.
The jnxFWCounterPacketCount and jnxFWCounterByteCount defined in the
jnxFirewallCounterTable provide this information.
5.2 Output bytes per queue

You can use the Juniper Networks enterprise ATM CoS MIB to monitor outbound traffic,
per virtual circuit forwarding class, per interface. For Non-ATM interfaces, the counters
are provided by the Juniper Networks enterprise-specific CoS MIB.

With regard to ATM, you can use the Juniper ATM CoS MIB to fetch the number of
bytes belonging to the specified forwarding class that were transmitted on the specified
virtual circuit (jnxCosAtmVcQstatsOutBytes).
Non-ATM interface counters are provided by the Juniper Networks enterprise-specific
JUNIPER-COS-MIB.
The number of transmitted bytes or packets per interface per forwarding class can be
calculated by polling the jnxCosIfqTxedBytes and jnxCosIfqTxedPkts in the
jnxCosIfqStatsTable in the JUNIPER-COS-MIB.
5.3 Calculating the Dropped Traffic
You can calculate the amount of dropped traffic by subtracting the outbound traffic from
the incoming traffic:
Dropped = Inbound Counter Outbound Counter

5.4 Tail Drop Packets
The number of tail-dropped packets per interface per forwarding class can be calculated
by polling the jnxCosIfqTailDropPkts in jnxCosIfqStatsTable in JUNIPER-COS-MIB


5.5 Red Drop Packets
The number of RED-dropped packets per interface per forwarding class can be calculated
by 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 get
supported in the Enterprise CoS MIB is specific to the device type. The following tables
list 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)


.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 (jnxCosQstatLpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.17 (jnxCosQstatLpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.18 (jnxCosQstatLpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.19 (jnxCosQstatHpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.20 (jnxCosQstatHpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.21 (jnxCosQstatHpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.22 (jnxCosQstatHpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.23 (jnxCosQstatTotalRedDropBytes)


.1.3.6.1.4.1.2636.3.15.4.1.24 (jnxCosQstatTotalRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.25 (jnxCosQstatLpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.26 (jnxCosQstatLpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.27 (jnxCosQstatLpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.28 (jnxCosQstatLpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.29 (jnxCosQstatHpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.30 (jnxCosQstatHpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.31 (jnxCosQstatHpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.32 (jnxCosQstatHpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.33 (jnxCosQstatLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.34 (jnxCosQstatLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.35 (jnxCosQstatMLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.36 (jnxCosQstatMLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.37 (jnxCosQstatMHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.38 (jnxCosQstatMHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.39 (jnxCosQstatHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.4.1.40 (jnxCosQstatHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.4.1.41 (jnxCosQstatLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.42 (jnxCosQstatLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.43 (jnxCosQstatMLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.44 (jnxCosQstatMLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.45 (jnxCosQstatMHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.46 (jnxCosQstatMHpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.4.1.47 (jnxCosQstatHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.4.1.48 (jnxCosQstatHpRedDropByteRate)
jnxCosIfstatFlagTable(.1.3.6.1.4.1.2636.3.15.5)
.1.3.6.1.4.1.2636.3.15.5.1.2 (jnxCosIfstatFlags)
jnxCosInvQstatTable(.1.3.6.1.4.1.2636.3.15.6)
.1.3.6.1.4.1.2636.3.15.6.1.3 (jnxCosInvQstatQedPkts)
.1.3.6.1.4.1.2636.3.15.6.1.4 (jnxCosInvQstatQedPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.5 (jnxCosInvQstatQedBytes)
.1.3.6.1.4.1.2636.3.15.6.1.6 (jnxCosInvQstatQedByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.7 (jnxCosInvQstatTxedPkts)
.1.3.6.1.4.1.2636.3.15.6.1.8 (jnxCosInvQstatTxedPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.9 (jnxCosInvQstatTxedBytes)
.1.3.6.1.4.1.2636.3.15.6.1.10 (jnxCosInvQstatTxedByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.11 (jnxCosInvQstatTailDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.12 (jnxCosInvQstatTailDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.13 (jnxCosInvQstatTotalRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.14 (jnxCosInvQstatTotalRedDropPktRate)


.1.3.6.1.4.1.2636.3.15.6.1.15 (jnxCosInvQstatLpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.16 (jnxCosInvQstatLpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.17 (jnxCosInvQstatLpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.18 (jnxCosInvQstatLpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.19 (jnxCosInvQstatHpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.20 (jnxCosInvQstatHpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.21 (jnxCosInvQstatHpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.22 (jnxCosInvQstatHpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.23 (jnxCosInvQstatTotalRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.24 (jnxCosInvQstatTotalRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.25 (jnxCosInvQstatLpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.26 (jnxCosInvQstatLpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.27 (jnxCosInvQstatLpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.28 (jnxCosInvQstatLpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.29 (jnxCosInvQstatHpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.30 (jnxCosInvQstatHpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.31 (jnxCosInvQstatHpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.32 (jnxCosInvQstatHpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.33 (jnxCosInvQstatLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.34 (jnxCosInvQstatLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.35 (jnxCosInvQstatMLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.36 (jnxCosInvQstatMLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.37 (jnxCosInvQstatMHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.38 (jnxCosInvQstatMHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.39 (jnxCosInvQstatHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.6.1.40 (jnxCosInvQstatHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.6.1.41 (jnxCosInvQstatLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.42 (jnxCosInvQstatLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.43 (jnxCosInvQstatMLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.44 (jnxCosInvQstatMLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.45 (jnxCosInvQstatMHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.46 (jnxCosInvQstatMHpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.6.1.47 (jnxCosInvQstatHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.6.1.48 (jnxCosInvQstatHpRedDropByteRate)
jnxCosIngressQstatTable(.1.3.6.1.4.1.2636.3.15.7)
.1.3.6.1.4.1.2636.3.15.7.1.3 (jnxCosIngressQstatQedPkts)
.1.3.6.1.4.1.2636.3.15.7.1.4 (jnxCosIngressQstatQedPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.5 (jnxCosIngressQstatQedBytes)
.1.3.6.1.4.1.2636.3.15.7.1.6 (jnxCosIngressQstatQedByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.7 (jnxCosIngressQstatTxedPkts)


.1.3.6.1.4.1.2636.3.15.7.1.8 (jnxCosIngressQstatTxedPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.9 (jnxCosIngressQstatTxedBytes)
.1.3.6.1.4.1.2636.3.15.7.1.10 (jnxCosIngressQstatTxedByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.11 (jnxCosIngressQstatTailDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.12 (jnxCosIngressQstatTailDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.13 (jnxCosIngressQstatTotalRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.14 (jnxCosIngressQstatTotalRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.15 (jnxCosIngressQstatLpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.16 (jnxCosIngressQstatLpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.17 (jnxCosIngressQstatLpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.18 (jnxCosIngressQstatLpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.19 (jnxCosIngressQstatHpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.20 (jnxCosIngressQstatHpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.21 (jnxCosIngressQstatHpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.22 (jnxCosIngressQstatHpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.23 (jnxCosIngressQstatTotalRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.24 (jnxCosIngressQstatTotalRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.25 (jnxCosIngressQstatLpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.26 (jnxCosIngressQstatLpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.27 (jnxCosIngressQstatLpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.28 (jnxCosIngressQstatLpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.29 (jnxCosIngressQstatHpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.30 jnxCosIngressQstatHpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.31 (jnxCosIngressQstatHpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.32 (jnxCosIngressQstatHpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.33 (jnxCosIngressQstatLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.34 (jnxCosIngressQstatLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.35 (jnxCosIngressQstatMLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.36 (jnxCosIngressQstatMLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.37 (jnxCosIngressQstatMHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.38 (jnxCosIngressQstatMHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.39 (jnxCosIngressQstatHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.40 (jnxCosIngressQstatHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.41 (jnxCosIngressQstatLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.42 (jnxCosIngressQstatLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.43 (jnxCosIngressQstatMLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.44 (jnxCosIngressQstatMLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.45 (jnxCosIngressQstatMHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.46 (jnxCosIngressQstatMHpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.47 (jnxCosIngressQstatHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.48 (jnxCosIngressQstatHpRedDropByteRate)


EX Series - EX 4200
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)
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)
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.5.1.2 (jnxCosIfstatFlags)
1.3.6.1.4.1.2636.3.15.6.1.3 (jnxCosInvQstatQedPkts)
1.3.6.1.4.1.2636.3.15.6.1.4 (jnxCosInvQstatQedPktRate)
1.3.6.1.4.1.2636.3.15.6.1.5 (jnxCosInvQstatQedBytes)
1.3.6.1.4.1.2636.3.15.6.1.6 (jnxCosInvQstatQedByteRate)
1.3.6.1.4.1.2636.3.15.6.1.7 (jnxCosInvQstatTxedPkts)
1.3.6.1.4.1.2636.3.15.6.1.8 (jnxCosInvQstatTxedPktRate)
1.3.6.1.4.1.2636.3.15.6.1.9 (jnxCosInvQstatTxedBytes)
1.3.6.1.4.1.2636.3.15.6.1.10 (jnxCosInvQstatTxedByteRate)
1.3.6.1.4.1.2636.3.15.6.1.11 (jnxCosInvQstatTailDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.12 (jnxCosInvQstatTailDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.13 (jnxCosInvQstatTotalRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.14 (jnxCosInvQstatTotalRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.15 (jnxCosInvQstatLpNonTcpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.16 (jnxCosInvQstatLpNonTcpRDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.17 (jnxCosInvQstatLpTcpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.18 (jnxCosInvQstatLpTcpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.19 (jnxCosInvQstatHpNonTcpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.20 (jnxCosInvQstatHpNonTcpRDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.21 (jnxCosInvQstatHpTcpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.22 (jnxCosInvQstatHpTcpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.23 (jnxCosInvQstatTotalRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.24 (jnxCosInvQstatTotalRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.25 (jnxCosInvQstatLpNonTcpRedDropBytes)


1.3.6.1.4.1.2636.3.15.6.1.26 (jnxCosInvQstatLpNonTcpRDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.27 (jnxCosInvQstatLpTcpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.28 (jnxCosInvQstatLpTcpRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.29 (jnxCosInvQstatHpNonTcpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.30 (jnxCosInvQstatHpNonTcpRDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.31 (jnxCosInvQstatHpTcpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.32 (jnxCosInvQstatHpTcpRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.33 (jnxCosInvQstatLpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.34 (jnxCosInvQstatLpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.35 (jnxCosInvQstatMLpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.36 (jnxCosInvQstatMLpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.37 (jnxCosInvQstatMHpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.38 (jnxCosInvQstatMHpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.39 (jnxCosInvQstatHpRedDropPkts)
1.3.6.1.4.1.2636.3.15.6.1.40 (jnxCosInvQstatHpRedDropPktRate)
1.3.6.1.4.1.2636.3.15.6.1.41 (jnxCosInvQstatLpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.42 (jnxCosInvQstatLpRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.43 (jnxCosInvQstatMLpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.44 (jnxCosInvQstatMLpRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.45 (jnxCosInvQstatMHpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.46 (jnxCosInvQstatMHpRedDropByteRate)
1.3.6.1.4.1.2636.3.15.6.1.47 (jnxCosInvQstatHpRedDropBytes)
1.3.6.1.4.1.2636.3.15.6.1.48 (jnxCosInvQstatHpRedDropByteRate)

M Series
jnxCosIfqStatsTable(.1.3.6.1.4.1.2636.3.15.1)


jnxCosFcTable(.1.3.6.1.4.1.2636.3.15.2)






jnxCosIngressQstatTable(.1.3.6.1.4.1.2636.3.15.7)
.1.3.6.1.4.1.2636.3.15.7.1.3 (jnxCosIngressQstatQedPkts)
.1.3.6.1.4.1.2636.3.15.7.1.4 (jnxCosIngressQstatQedPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.5 (jnxCosIngressQstatQedBytes)
.1.3.6.1.4.1.2636.3.15.7.1.6 (jnxCosIngressQstatQedByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.7 (jnxCosIngressQstatTxedPkts)
.1.3.6.1.4.1.2636.3.15.7.1.8 (jnxCosIngressQstatTxedPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.9 (jnxCosIngressQstatTxedBytes)
.1.3.6.1.4.1.2636.3.15.7.1.10 (jnxCosIngressQstatTxedByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.11 (jnxCosIngressQstatTailDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.12 (jnxCosIngressQstatTailDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.13 (jnxCosIngressQstatTotalRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.14 (jnxCosIngressQstatTotalRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.15 (jnxCosIngressQstatLpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.16 (jnxCosIngressQstatLpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.17 (jnxCosIngressQstatLpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.18 (jnxCosIngressQstatLpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.19 (jnxCosIngressQstatHpNonTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.20 (jnxCosIngressQstatHpNonTcpRDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.21 (jnxCosIngressQstatHpTcpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.22 (jnxCosIngressQstatHpTcpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.23 (jnxCosIngressQstatTotalRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.24 (jnxCosIngressQstatTotalRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.25 (jnxCosIngressQstatLpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.26 (jnxCosIngressQstatLpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.27 (jnxCosIngressQstatLpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.28 (jnxCosIngressQstatLpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.29 (jnxCosIngressQstatHpNonTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.30 jnxCosIngressQstatHpNonTcpRDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.31 (jnxCosIngressQstatHpTcpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.32 (jnxCosIngressQstatHpTcpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.33 (jnxCosIngressQstatLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.34 (jnxCosIngressQstatLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.35 (jnxCosIngressQstatMLpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.36 (jnxCosIngressQstatMLpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.37 (jnxCosIngressQstatMHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.38 (jnxCosIngressQstatMHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.39 (jnxCosIngressQstatHpRedDropPkts)
.1.3.6.1.4.1.2636.3.15.7.1.40 (jnxCosIngressQstatHpRedDropPktRate)
.1.3.6.1.4.1.2636.3.15.7.1.41 (jnxCosIngressQstatLpRedDropBytes)


.1.3.6.1.4.1.2636.3.15.7.1.42 (jnxCosIngressQstatLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.43 (jnxCosIngressQstatMLpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.44 (jnxCosIngressQstatMLpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.45 (jnxCosIngressQstatMHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.46 (jnxCosIngressQstatMHpRedDropByteRate)
.1.3.6.1.4.1.2636.3.15.7.1.47 (jnxCosIngressQstatHpRedDropBytes)
.1.3.6.1.4.1.2636.3.15.7.1.48 (jnxCosIngressQstatHpRedDropByteRate)

J Series
jnxCosIfqStatsTable (.1.3.6.1.4.1.2636.3.15.1)


jnxCosFcTable(.1.3.6.1.4.1.2636.3.15.2)





SRX Series
jnxCosIfqStatsTable (.1.3.6.1.4.1.2636.3.15.1)


jnxCosFcTable(.1.3.6.1.4.1.2636.3.15.2)



6 Key Performance Indicators - Routing Protocols

6.1 Counters for Routing Protocols
The following are the relevant counters that are used to derive the Key Performance
Indicators.


6.1.1 BGP Counters

BGP
.1.3.6.1.2.1.15.1 (bgpVersion)
.1.3.6.1.2.1.15.2 (bgpLocalAs)
.1.3.6.1.2.1.15.3.1.1 (bgpPeerIdentifier)
.1.3.6.1.2.1.15.3.1.2 (bgpPeerState)
.1.3.6.1.2.1.15.3.1.3 (bgpPeerAdminStatus)
.1.3.6.1.2.1.15.3.1.4 (bgpPeerNegotiatedVersion)
.1.3.6.1.2.1.15.3.1.5 (bgpPeerLocalAddr)
.1.3.6.1.2.1.15.3.1.6 (bgpPeerLocalPort)
.1.3.6.1.2.1.15.3.1.7 (bgpPeerRemoteAddr)
.1.3.6.1.2.1.15.3.1.8 (bgpPeerRemotePort)
.1.3.6.1.2.1.15.3.1.9 (bgpPeerRemoteAs)
.1.3.6.1.2.1.15.3.1.10 (bgpPeerInUpdates)
.1.3.6.1.2.1.15.3.1.11 (bgpPeerOutUpdates)
.1.3.6.1.2.1.15.3.1.12 (bgpPeerInTotalMessages)
.1.3.6.1.2.1.15.3.1.13 (bgpPeerOutTotalMessages)
.1.3.6.1.2.1.15.3.1.14 (bgpPeerLastError)
.1.3.6.1.2.1.15.3.1.15 (bgpPeerFsmEstablishedTransitions)
.1.3.6.1.2.1.15.3.1.16 (bgpPeerFsmEstablishedTime)
.1.3.6.1.2.1.15.3.1.17 (bgpPeerConnectRetryInterval)
.1.3.6.1.2.1.15.3.1.18 (bgpPeerHoldTime)
.1.3.6.1.2.1.15.3.1.19 (bgpPeerKeepAlive)
.1.3.6.1.2.1.15.3.1.20 (bgpPeerHoldTimeConfigured)
.1.3.6.1.2.1.15.3.1.21 (bgpPeerKeepAliveConfigured)
.1.3.6.1.2.1.15.3.1.22 (bgpPeerMinASOriginationInterval)
.1.3.6.1.2.1.15.3.1.23 (bgpPeerMinRouteAdvertisementInterval)
.1.3.6.1.2.1.15.3.1.24 (bgpPeerInUpdateElapsedTime)


6.1.2 OSPF Counters

OSPF
.1.3.6.1.2.1.14.1.2 (ospfAdminStat)
.1.3.6.1.2.1.14.1.3 (ospfVersionNumber)
.1.3.6.1.2.1.14.1.4 (ospfAreaBdrRtrStatus)
.1.3.6.1.2.1.14.1.5 (ospfASBdrRtrStatus)
.1.3.6.1.2.1.14.1.6 (ospfExternLsaCount)
.1.3.6.1.2.1.14.1.7 (ospfExternLsaCksumSum)
.1.3.6.1.2.1.14.1.8 (ospfTOSSupport)
.1.3.6.1.2.1.14.1.9 (ospfOriginateNewLsas)
.1.3.6.1.2.1.14.1.10 (ospfRxNewLsas)
.1.3.6.1.2.1.14.1.11 (ospfExtLsdbLimit)
.1.3.6.1.2.1.14.1.12 (ospfMulticastExtensions)
.1.3.6.1.2.1.14.1.13 (ospfExitOverflowInterval)
.1.3.6.1.2.1.14.1.14 (ospfDemandExtensions)
.1.3.6.1.2.1.14.2.1.1 (ospfAreaId)
.1.3.6.1.2.1.14.2.1.2 (ospfAuthType)
.1.3.6.1.2.1.14.2.1.3 (ospfImportAsExtern)
.1.3.6.1.2.1.14.2.1.4 (ospfSpfRuns)
.1.3.6.1.2.1.14.2.1.5 (ospfAreaBdrRtrCount)
.1.3.6.1.2.1.14.2.1.6 (ospfAsBdrRtrCount)
.1.3.6.1.2.1.14.2.1.7 (ospfAreaLsaCount)
.1.3.6.1.2.1.14.2.1.8 (ospfAreaLsaCksumSum)
.1.3.6.1.2.1.14.2.1.9 (ospfAreaSummary)
.1.3.6.1.2.1.14.2.1.10 (ospfAreaStatus)
.1.3.6.1.2.1.14.3.1.1 (ospfStubAreaId)
.1.3.6.1.2.1.14.3.1.2 (ospfStubTOS)
.1.3.6.1.2.1.14.3.1.3 (ospfStubMetric)


.1.3.6.1.2.1.14.3.1.4 (ospfStubStatus)
.1.3.6.1.2.1.14.3.1.5 (ospfStubMetricType)
.1.3.6.1.2.1.14.4.1.1 (ospfLsdbAreaId)
.1.3.6.1.2.1.14.4.1.2 (ospfLsdbType)
.1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid)
.1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId)
.1.3.6.1.2.1.14.4.1.5 (ospfLsdbSequence)
.1.3.6.1.2.1.14.4.1.6 (ospfLsdbAge)
.1.3.6.1.2.1.14.4.1.7 (ospfLsdbChecksum)
.1.3.6.1.2.1.14.4.1.8 (ospfLsdbAdvertisement)
.1.3.6.1.2.1.14.5.1.2 (ospfAreaRangeNet)
.1.3.6.1.2.1.14.5.1.3 (ospfAreaRangeMask)
.1.3.6.1.2.1.14.5.1.4 (ospfAreaRangeStatus)
.1.3.6.1.2.1.14.5.1.5 (ospfAreaRangeEffect)
.1.3.6.1.2.1.14.6.1.1 (ospfHostIpAddress)
.1.3.6.1.2.1.14.6.1.2 (ospfHostTOS)
.1.3.6.1.2.1.14.6.1.3 (ospfHostMetric)
.1.3.6.1.2.1.14.6.1.4 (ospfHostStatus)
.1.3.6.1.2.1.14.6.1.5 (ospfHostAreaID)
.1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)
.1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)
.1.3.6.1.2.1.14.7.1.4 (ospfIfType)

7 Key Performance Indicators Frame Relay

7.1 Frame Relay MIB Objects
The following MIB OIDs are supported for monitoring Frame Relay services on
interfaces for all JUNOS based devices. The Parameters for the Data Link Connection
Management Interface for the frame relay service on an interface is included as a part of
the frDlcmiTable in the RFC 2115.

The following MIB OIDs are supported in the RFC 2115 - Frame Relay DTE MIB.

frDlcmiState
frDlcmiAddress
frDlcmiAddressLen
frDlcmiPollingInterval
frDlcmiFullEnquiryInterval
frDlcmiErrorThreshold
frDlcmiMonitoredEvents
frDlcmiMaxSupportedVCs
frDlcmiMulticast
frDlcmiStatus


Note that Frame Relay Interface and sub-interface statistics and Circuit statistics
are supported on ERX devices

7.2 Frame Relay interface and subinterface statistics

Attribute Description
System Up Time Time since last reported change to the operational status
Poll Interval (sec) Interval in seconds between POLL PDU transmissions
Refresh When button is clicked, the statistics are refreshed
Received Octets
Number of incoming octets received on this interface or
subinterface
Transmitted Octets
Number of outgoing octets transmitted on this interface or
subinterface
Received Packets with
Errors
Number of incoming errors received on this interface or
subinterface
Transmitted Packets with
Errors
Number of outgoing packets with errors on this interface or
subinterface
Unknown Protocol
Packets
Number of packets discarded because of an unknown or
unsupported protocol
Received Ucast Packets Number of received Ucast packets
Transmitted Ucast Packets Number of transmitted Ucast packets
Received Packets
Discarded
Number of received packets without errors discarded
Transmitted Packets
Discarded
Number of transmitted packets without errors discarded
Received Multicast
Packets
Number of received multicast packets
Transmitted Multicast
Packets
Number of transmitted multicast packets


Received Broadcast Packets Number of received broadcast packets
Transmitted Broadcast Packets Number of transmitted broadcast packets

7.3 Circuit Statistics

Attribute Description
Received FECN
Frames
Number of packets received with the forward explicit congestion
notification (FECN) bit set
Transmitted FECN
Frames
Number of packets transmitted with the FECN bit set
Received BECN
Frames
Number of packets received with the backward explicit
congestion notification (BECN) bit set
Transmitted BECN
Frames
Number of packets transmitted with the BECN bit set
Received Frames Number of incoming packets received on the circuit
Transmitted Frames Number of outgoing packets transmitted on the circuit
Received Octets Number of octets received on the circuit
Transmitted Octets Number of octets sent
Received DE Frames
Number of packets received with the discard eligibility (DE) bit
set
Transmitted DE
Frames
Number of packets transmitted with the DE bit set
Received Frames
Discarded
Number of inbound packets dropped


8 Key Performance Indicators ATM

8.1 ATM state information
HCS StateStatus of the header check sequence. ATM uses the HCS field in the cell
header in the cell delineation process to frame ATM cell boundaries. The HCS is an
FCS-8 calculation over the first four octets of the ATM cell header.
LOCCurrent loss of cell (LOC) delineation state. OK means that no LOC is
currently asserted.
8.2 ATM statistics for the interface
Uncorrectable HCS errorsNumber of cells dropped because the cell delineation
failed. These errors most likely indicate that a SONET/SDH layer problem has
occurred.
Correctable HCS errorsNumber of correctable HCS errors that occurred. The cell
delineation process can recover from these errors and locate the ATM cell boundary,
although the framing process is not quite stable. The ATM cell is not dropped. This
counter increases when the cell delineation process changes its state from present to
sync (for example, when a cable is plugged into the interface).


8.3 Error statistics
Tx cell FIFO overrunsNumber of overruns in the transmit FIFO.
Rx cell FIFO overrunsNumber of overruns in the receive FIFO.
Rx cell FIFO underrunsNumber of underruns in the receive FIFO.
Input cell countNumber of ATM cells received by the interface (not including idle
cells).
Output cell countNumber of ATM cells transmitted by the interface (not including
idle cells).
Output idle cell countNumber of idle cells sent by the port. When ATM has
nothing to send, it sends idle cells to fill the time slot.
Output VC queue dropsNumber of packets dropped by a port on the PIC. Packets
are dropped because of queue limits on the VCs.


8.4 Error statistics (SAR)
Input no buffersNumber of AAL5 packets dropped because no channel blocks or
buffers were available to handle them.
Input length errorsNumber of AAL5 packets dropped because their length was
incorrect. Usually, these errors occur because a cell has been corrupted or lost, or
because the length field was corrupted. They can also mean the AAL5 length field
was zero.
Input timeoutsNumber of AAL5 packets dropped because of a reassembly timeout.
Input invalid VCsNumber of AAL5 packets dropped because the header was
unrecognized (because the VC was not correct or not configured).
Input bad CRCsNumber of AAL5 packets dropped because of frame check
sequence errors.
Input OAM cell no buffersNumber of received OAM cells or raw cells dropped
because no buffers were available to handle them.
L2 circuit out-of-sequence packets(Layer 2 AAL5 mode) Number of AAL5
packets that are out of sequential order.

8.5 ATM related MIB Objects
jnxAtmIfPortType
jnxAtmIfEncaps
jnxAtmIfLpBackInfo
jnxAtmIfScrambleEnable
jnxAtmIfTxCellCount
jnxAtmIfRxCellCount
jnxAtmIfTxIdleCellCount
jnxAtmIfUncorrHCSErrs
jnxAtmIfCorrHCSErrs
jnxAtmIfTxCellFIFOOverRuns
jnxAtmIfRxCellFIFOOverRuns
jnxAtmIfRxCellFIFOUnderRuns
jnxAtmIfInInvalidVCCells
jnxAtmIfInNoBufferOAMCells
jnxAtmIfInNoBufDropPkts
jnxAtmIfOutVCQueueDrops
jnxAtmIfInBadCrcs
jnxAtmIfInLenErrPkts
jnxAtmIfInTimeoutPkts
jnxAtmIfL2CircuitMode
jnxAtmVCConnType


jnxAtmVCEncapsulation
jnxAtmVCMpDestIPv4Addr
jnxAtmVCMpDestIPv6Addr
jnxAtmVCFlags
jnxAtmVCTotalDownTime
jnxAtmVCInBytes
jnxAtmVCOutBytes
jnxAtmVCInPkts
jnxAtmVCOutPkts
jnxAtmVCTailQueuePktDrops
jnxAtmVCOAMPeriod
jnxAtmVCOAMUpCellCount
jnxAtmVCOAMDownCellCount
jnxAtmVCInOAMF5LoopCells
jnxAtmVCOutOAMF5LoopCells
jnxAtmVCInOAMF5RDICells
jnxAtmVCOutOAMF5RDICells
jnxAtmVCInOAMF5AISCells
jnxAtmVCOutOAMF5AISCells
jnxAtmVpFlags
jnxAtmVpTotalDownTime
jnxAtmVpOamPeriod
jnxAtmVpOamUpCellCount
jnxAtmVpOamDownCellCount
jnxAtmVpInBytes
jnxAtmVpOutBytes
jnxAtmVpInPkts
jnxAtmVpOutPkts
jnxAtmVpInOamF4Cells
jnxAtmVpOutOamF4Cells
jnxAtmVpInOamF4LoopCells
jnxAtmVpOutOamF4LoopCells
jnxAtmVpInOamF4RdiCells
jnxAtmVpOutOamF4RdiCells
jnxAtmVpInOamF4AisCells
jnxAtmTrunkId
jnxAtmTrunkConnType
jnxAtmTrunkEncapsulation
jnxAtmTrunkFlags
jnxAtmTrunkTotalDownTime
jnxAtmTrunkInBytes
jnxAtmTrunkOutBytes


jnxAtmTrunkInPkts
jnxAtmTrunkOutPkts
jnxAtmTrunkTailQueuePktDrops
jnxAtmTrunkInOAMF4AISCells
jnxAtmTrunkOutOAMF4AISCells

You can also monitor ATM interfaces using the JUNOSscript API. You can refer to
JUNOS documentation to understand how to use JUNOScript APIs.

The JUNOScript RPC <get-interface-information> provides the complete ATM statistics
and status information.

</rpc>
<get-interface-information>
<extensive/>
<statistics/>
<media/>
<detail/>
<terse/>
<brief/>
<descriptions/>
<destination-class>destination-class</destination-class>
<snmp-index>snmp-index</snmp-index>
<interface-name>interface-name</interface-name>
</get-interface-information>
</rpc>


<virtual-circuit-information>
<atm-statistics>
<uncorrectable-hcs-errors>uncorrectable-hcs-errors</uncorrectable-
hcs-errors>
<correctable-hcs-errors>correctable-hcs-errors</correctable-hcs-
errors>
<tx-cell-fifo-overruns>tx-cell-fifo-overruns</tx-cell-fifo-
overruns>
<rx-cell-fifo-overruns>rx-cell-fifo-overruns</rx-cell-fifo-
overruns>
<rx-cell-fifo-underruns>rx-cell-fifo-underruns</rx-cell-fifo-
underruns>
<rx-cell-count>rx-cell-count</rx-cell-count>
<tx-cell-count>tx-cell-count</tx-cell-count>
<tx-idle-cell-count>tx-idle-cell-count</tx-idle-cell-count>
<vc-queue-drops>vc-queue-drops</vc-queue-drops>
<no-buffers>no-buffers</no-buffers>
<length-errors>length-errors</length-errors>
<timeouts>timeouts</timeouts>
<rx-invalid-vcs>rx-invalid-vcs</rx-invalid-vcs>
<bad-crcs>bad-crcs</bad-crcs>
<oam-cell-no-buffers>oam-cell-no-buffers</oam-cell-no-buffers>
</atm-statistics>
</virtual-circuit-information>

9 Key Performance Indicators for MPLS

The following are the Key Performance Indicators for MPLS and associated OIDs that
are used to derive the indicators:

LSP utilization - Utilization of the MPLS label-switched path.( mplsPathBandwidth /
(mplsLspOctets * 8)
Number of Packets forwarded by the Tunnel(mplsTunnelPerfPackets)
Number of Packets in Error(mplsTunnelPerfErrors)
Number of Octets coming in (jnxLdpIngressOctets)
Number of Packets coming in (jnxLdpIngressPackets)
Number of Octets transiting(jnxLdpTransitOctets)
Number of Packets Transiting(jnxLdpTransitPackets)
LSP utilization can be calculated as mplsPathBandwidth / (mplsLspOctets * 8)
10 Key Performance Indicator for VPN
The following are the Key Performance Indicators for Layer 2 and Layer 3 VPNs:


The protocol running over the VPN Interface - jnxVpnIfProtocol
Maximum bandwidth that the CE connected over the VPN interface can send to
the PE, in Kilo (i.e., 1000) Bytes per second - jnxVpnIfInBandwidth
Maximum bandwidth that the PE can send to the CE over the VPN interface, in
Kilo (i.e., 1000) Bytes per second - jnxVpnIfOutBandwidth

11 Key Performance Indicators for IP Sec

The IPSec Monitoring MIB provides a way to monitor IPSec information on J-series
Services Routers and AS PICs installed in M-series and T-series routing platforms by
using SNMP. The MIB provides an IKE tunnel table to monitor IKE security
associations and view related statistics, an IPSec tunnel table to view IPSec tunnel
statistics, and an IPSec security associations table to view all IPSec SAs.
The enterprise-specific IPSec Generic Flow Monitoring Object MIB, whose object ID is
{jnxIpSecMibRoot 1}, defines the objects used to monitor the entries pertaining to IPSec
objects and the management of the IPSec VPN functionalities. This generic MIB models
the standard, dynamic aspects of IPSec, including the counters and objects that are of
management interest in a standard IPSec implementation.
This MIB module is based on the jnxIpSecMonitorMib. Building on the existing Internet
Key Exchange (IKE) infrastructure, the security IKE implementation integrates the
value-added features for the security products.

11.1 Key Indicators for IP Sec

Number of Bytes In
Number of Bytes Out
Number of Packets In
Number of Packets Out
Tunnel Utilization


11.2 IP Sec Counters
jnxIpSecTunnelMonTable
jnxIpSecTunMonRemoteGwAddrType
jnxIpSecTunMonRemoteGwAddr
jnxIpSecTunMonIndex
jnxIpSecTunMonLocalGwAddrType
jnxIpSecTunMonLocalGwAddr
jnxIpSecTunMonLocalProxyId
jnxIpSecTunMonRemoteProxyId
jnxIpSecTunMonKeyType
jnxIpSecTunMonRemotePeerType
jnxIpSecTunMonOutEncryptedBytes
jnxIpSecTunMonOutEncryptedPkts
jnxIpSecTunMonInDecryptedBytes
jnxIpSecTunMonInDecryptedPkts
jnxIpSecTunMonAHInBytes
jnxIpSecTunMonAHInPkts
jnxIpSecTunMonAHOutBytes
jnxIpSecTunMonAHOutPkts
jnxIpSecTunMonReplayDropPkts
jnxIpSecTunMonAhAuthFails
jnxIpSecTunMonEspAuthFails
jnxIpSecTunMonDecryptFails
jnxIpSecTunMonBadHeaders
jnxIpSecTunMonBadTrailers
jnxIpSecTunMonDroppedPkts
jnxIkeTunMonInOctets
jnxIkeTunMonInPkts
jnxIkeTunMonOutOctets
jnxIkeTunMonOutPkts
jnxIkeTunMonInOctets
jnxIkeTunMonInPkts
jnxJsIfMonInIcmp
jnxJsIfMonInSelf
jnxJsIfMonInVpn
jnxJsIfMonInPolicyPermit
jnxJsIfMonOutPolicyPermit
jnxJsIfMonConn
jnxJsIfMonInMcast
jnxJsIfMonOutMcast


jnxJsIfMonPolicyDeny
jnxJsIfMonNoGateParent
jnxJsIfMonTcpProxyDrop
jnxJsIfMonNoDip
jnxJsIfMonNoNspTunnel
jnxJsIfMonNoNatCon
jnxJsIfMonInvalidZone
jnxJsIfMonIpClsFail
jnxJsIfMonAuthDrop
jnxJsIfMonMultiUserAuthDrop
jnxJsIfMonLoopMultiDipDrop
jnxJsIfMonAddrSpoof
jnxJsIfMonLpDrop
jnxJsIfMonNullZone
jnxJsIfMonNoGate
jnxJsIfMonNoMinorSess
jnxJsIfMonNvecErr
jnxJsIfMonTcpSeq
jnxJsIfMonIllegalPak
jnxJsIfMonNoRoute
jnxJsIfMonAuthFail
jnxJsIfMonSaInactive
jnxJsIfMonNoSa
jnxJsIfMonSelfPktDrop
jnxSpSvcSetIfTableName
jnxSpSvcSetIfSvcSets
jnxSpSvcSetIfMemoryUsage
jnxSpSvcSetIfPctMemoryUsage
jnxSpSvcSetIfPolMemoryUsage
jnxSpSvcSetIfPctPolMemoryUsage
jnxSpSvcSetIfMemoryZone
jnxSpSvcSetIfTableName
jnxSpSvcSetIfSvcSets
jnxSpSvcSetIfMemoryUsage
jnxSpSvcSetIfPctMemoryUsage
jnxSpSvcSetIfPolMemoryUsage


12 Key Performance Indicators for Pseudowires

12.1 Pseudowires Indicators
The following are the Key Performance Indicators for Pseudowires.

Number of Missing Packets
Number of Packets Re-order
Number of Jitter Buffer underruns
Number of Misorder packets dropped
Number of Malformed packets
Number of Error Seconds
Number of Severe Error Seconds
Number of Psuedowire transitions
Number of Packets Sent
Number of Packets Received
Time of last Transition
Pseudowire Uptime

The following are the relevant counters that are used to derive the Key Performance
Indicators. Note that Mobile Backhaul implementations use both JUNOS as well BXOS
devices and some of the counters may not be supported by BXOS devices.

12.2 VPN and Pseudowire related Counters

VPN and Pseudowire Counters
jnxpwTDMPerfCurrentMissingPkts
jnxpwTDMPerfCurrentPktsReOrder
jnxpwTDMPerfCurrentJtrBfrUnderruns
jnxpwTDMPerfCurrentMisOrderDropped
jnxpwTDMPerfCurrentMalformedPkt
jnxPwTDMPerfCurrentMissingPkts
jnxPwTDMPerfCurrentPktsReOrder
jnxPwTDMPerfCurrentJtrBfrUnderruns
jnxPwTDMPerfCurrentMisOrderDropped
jnxPwTDMPerfCurrentMalformedPkt
jnxPwTDMPerfCurrentESs
jnxPwTDMPerfCurrentSESs
jnxVpnPwPacketsSent
jnxVpnPwOctetsSent
jnxVpnPwPacketsReceived


jnxVpnPwOctetsReceived
jnxVpnPwLRPacketsSent
jnxVpnPwLROctetsSent
jnxVpnPwLRPacketsReceived
jnxVpnPwLROctetsReceived

13 Real Time Performance Management RPM

RPM is a service available in JUNOS that enables a router to measure metrics such as
round-trip delays and unanswered echo requests. To achieve this, RPM exchanges a set
of probes with other IP hosts in the network for monitoring and network tracking
purposes. These probes are sent from a source node to other destination devices in the
network that require tracking. Data such as transit delay and jitter can be collected from
these probes, and this data can be used to provide an approximation of the delay and jitter
experienced by live traffic in the network. Different live traffic metrics like round-trip
time (RTT), positive egress jitter, negative egress jitter, positive ingress jitter, negative
ingress jitter, positive round-trip jitter, and negative round-trip jitter can be gleaned from
the results. RPM calculates minimum, maximum, average, peak-to-peak, standard
deviation, and sum calculations for each of these measurements. RPM probes can also be
used to verify the path between BGP neighbors.

13.1 RPM Indicators

Minimum, maximum, and average round-trip time as measured over the course
of the test.
Standard deviation of the round-trip time measured over the course of the test.
Jitter over the round-trip time
For ICMP timestamp probes, corresponding one-way measurements such as
ingress and egress times, standard deviation, egress and ingress jitter
Number of probes sent during the test.
Number of probe responses received during the test.
Percentage of lost probes during the test


13.2 RPM related counters

Juniper Enterprise PING MIB (jnx-ping-mib)
jnxPingLastTestResultPeakToPeakJitterRttUs(.1.3.6.1.4.1.2636.3.7.1.5.1.16)
jnxPingLastTestResultPeakToPeakJitterEgressUs(.1.3.6.1.4.1.2636.3.7.1.5.1.17)
jnxPingLastTestResultPeakToPeakJitterIngressUs(.1.3.6.1.4.1.2636.3.7.1.5.1.18
)
jnxPingLastTestResultTime(.1.3.6.1.4.1.2636.3.7.1.5.1.19)
pingResultsOperStatus(.1.3.6.1.2.1.80.1.3.1.1)
pingResultsIpTargetAddressType(.1.3.6.1.2.1.80.1.3.1.2)
pingResultsIpTargetAddress(.1.3.6.1.2.1.80.1.3.1.3)
pingResultsMinRtt(.1.3.6.1.2.1.80.1.3.1.4)
pingResultsMaxRtt(.1.3.6.1.2.1.80.1.3.1.5)
pingResultsAverageRtt(.1.3.6.1.2.1.80.1.3.1.6)
pingResultsProbeResponses(.1.3.6.1.2.1.80.1.3.1.7)
pingResultsSentProbes(.1.3.6.1.2.1.80.1.3.1.8)
pingResultsRttSumOfSquares(.1.3.6.1.2.1.80.1.3.1.9)
pingResultsLastGoodProbe(.1.3.6.1.2.1.80.1.3.1.10)
pingProbeHistoryIndex(.1.3.6.1.2.1.80.1.4.1.1)
pingProbeHistoryResponse(.1.3.6.1.2.1.80.1.4.1.2)
pingProbeHistoryStatus(.1.3.6.1.2.1.80.1.4.1.3)
pingProbeHistoryLastRC(.1.3.6.1.2.1.80.1.4.1.4)
pingProbeHistoryTime(.1.3.6.1.2.1.80.1.4.1.5)
jnxRpmResultsSampleTable
jnxRpmResSampleType(.1.3.6.1.4.1.2636.3.50.1.1.1.1)
jnxRpmResSampleValue(.1.3.6.1.4.1.2636.3.50.1.1.1.2)
jnxRpmResSampleTsType(.1.3.6.1.4.1.2636.3.50.1.1.1.3)
jnxRpmResSampleDate(.1.3.6.1.4.1.2636.3.50.1.1.1.4)
jnxRpmResultsSummaryTable
jnxRpmResSumCollection(.1.3.6.1.4.1.2636.3.50.1.2.1.1)
jnxRpmResSumSent(.1.3.6.1.4.1.2636.3.50.1.2.1.2)
jnxRpmResSumReceived(.1.3.6.1.4.1.2636.3.50.1.2.1.3)
jnxRpmResSumPercentLost(.1.3.6.1.4.1.2636.3.50.1.2.1.4)
jnxRpmResSumDate(.1.3.6.1.4.1.2636.3.50.1.2.1.5)
jnxRpmResultsCalculatedTable
jnxRpmResCalcSet(.1.3.6.1.4.1.2636.3.50.1.3.1.1)
jnxRpmResCalcSamples(.1.3.6.1.4.1.2636.3.50.1.3.1.2)
jnxRpmResCalcMin(.1.3.6.1.4.1.2636.3.50.1.3.1.3)
jnxRpmResCalcMax(.1.3.6.1.4.1.2636.3.50.1.3.1.4)


jnxRpmResCalcAverage(.1.3.6.1.4.1.2636.3.50.1.3.1.5)
jnxRpmResCalcPkToPk(.1.3.6.1.4.1.2636.3.50.1.3.1.6)
jnxRpmResCalcStdDev(.1.3.6.1.4.1.2636.3.50.1.3.1.7)
jnxRpmResCalcSum(.1.3.6.1.4.1.2636.3.50.1.3.1.8)
jnxRpmHistorySampleTable
jnxRpmHistSampleType(.1.3.6.1.4.1.2636.3.50.1.4.1.1)
jnxRpmHistSampleValue(.1.3.6.1.4.1.2636.3.50.1.4.1.2)
jnxRpmHistSampleTsType(.1.3.6.1.4.1.2636.3.50.1.4.1.3)
jnxRpmHistorySummaryTable
jnxRpmHistSumCollection(.1.3.6.1.4.1.2636.3.50.1.5.1.1)
jnxRpmHistSumSent(.1.3.6.1.4.1.2636.3.50.1.5.1.2)
jnxRpmHistSumReceived(.1.3.6.1.4.1.2636.3.50.1.5.1.3)
jnxRpmHistSumPercentLost(.1.3.6.1.4.1.2636.3.50.1.5.1.4)
jnxRpmHistoryCalculatedTable
jnxRpmHistCalcSet(.1.3.6.1.4.1.2636.3.50.1.6.1.1)
jnxRpmHistCalcSamples(.1.3.6.1.4.1.2636.3.50.1.6.1.2)
jnxRpmHistCalcMin(.1.3.6.1.4.1.2636.3.50.1.6.1.3)
jnxRpmHistCalcMax(.1.3.6.1.4.1.2636.3.50.1.6.1.4)
jnxRpmHistCalcAverage(.1.3.6.1.4.1.2636.3.50.1.6.1.5)
jnxRpmHistCalcPkToPk(.1.3.6.1.4.1.2636.3.50.1.6.1.6)
jnxRpmHistCalcStdDev(.1.3.6.1.4.1.2636.3.50.1.6.1.7)
jnxRpmHistCalcSum(.1.3.6.1.4.1.2636.3.50.1.6.1.8)

Please refer to RPM application notes for more information on how to use RPM.

14 Using the Juniper Utility MIB

Since the set of applications, network types, etc. used by each of our customers will be
different; the set of performance metrics that they need to monitor will be different as
well. Rather than trying to design a common performance monitoring feature that
addresses all customer needs, a better approach is to give customers and support staff the
tools to customize their own applications and leverage the infrastructure already available
on the routers. Further, by taking advantage of the ability for the router to monitor itself
and notify a NM application on an exception basis, we can help address the scaling issues
that arise as our customers' networks expand. One of the tools for such customization is
jnx-utility MIB.

Juniper jnx-utility MIB is a powerful tool to expose JUNOS data using SNMP. A generic,
utility mib is defined to hold data populated by op or event scripts. There are 5 separate
tables in this mib, one for each of the following data types: 32-bit counters, 64-bit
counters, signed integers, unsigned integers, and octet strings.


Each data instance is identified by an arbitrary ASCII name defined when the data is
populated. Each data instance will also have a corresponding timestamp identifying
when it was last updated. The data in these mib tables can be populated via hidden cli
commands, which are also accessible from an op script via its 'jcs: invoke rpc API.

One example for the jnxUtilityMIB usage is for power reading on the device which is not
available via SNMP.

For example: The following command gives the power readings on SRX. With a simple
event script we can read the power output every 5 mins and populate the jnx-utility MIB
as shown below. Similarly we can write op scripts or event scripts that can populate
variety of data of different data types

OUTPUT of CLI command

regress@SRX-5600-pet-blore> show chassis environment pem
PEM 0 status:
State Online
Temperature OK
AC Input: OK
DC Output Voltage Current Power Load
50 5 250 14
PEM 1 status:
State Online
Temperature OK
AC Input: OK
DC Output Voltage Current Power Load
50 5 250 14

SNMP output of the jnx-utility populated with power readings from above command
regress@SRX-5600-pet-blore> show snmp mib walk jnxUtil

jnxUtilIntegerValue.80.69.77.48.68.67.45.67.117.114.114.101.110.116 = 5
jnxUtilIntegerValue.80.69.77.48.68.67.45.76.111.97.100 = 14
jnxUtilIntegerValue.80.69.77.48.68.67.45.80.111.119.101.114 = 250
jnxUtilIntegerValue.80.69.77.49.68.67.45.76.111.97.100 = 14
jnxUtilIntegerValue.80.69.77.49.68.67.45.80.111.119.101.114 = 250


15 Using Accounting Profiles

Accounting Profiles are user configurable data exchange parameters for stored files. You
can collect accounting data for the specified physical or logical interface. An accounting
profile specifies what statistics should be collected and written to a log file. To configure
an accounting-data log file, include the file statement at the [edit accounting-options]
hierarchy level.
An accounting profile represents common characteristics of collected accounting data,
including the following:
Collection interval
File to contain accounting data
Specific fields and counter names on which to collect statistics
You can configure multiple accounting profiles, as described in the table below:
Type of Profile Description
Interface profile Collects the specified error and statistic information.
Filter profile Collects the byte and packet counts for the counter names specified
in the filter profile.
MIB profile Collects selected MIB statistics and logs them to a specified file.
Routing Engine
profile
Collects selected Routing Engine statistics and logs them to a
specified file.
Class usage profile Collects class usage statistics and logs them to a specified file.

You can find more information about the accounting profiles at
http://www.juniper.net/techpubs/software/junos/junos94/swconfig-net-mgmt/accounting-
options-overview-junos-nm.html#jN4B64A

KPI For Juniper Devices

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

KPI For Juniper Devices

Загружено:

Авторское право:

Доступные форматы

Key Performance Indicators for Juniper Devices

Page 1 of 92 Partner Engineering Network Management

Вам также может понравиться