FILE DESCRIPTION 3/198 18-CRA 119 1170/1-V1 Uen B

Standard SNMP MIBs

Copyright

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

SmartEdge		is a registered trademark of Telefonaktiebolaget LM Ericsson.
NetOp		is a trademark of Telefonaktiebolaget LM Ericsson.

Contents

1	About Standard SNMP MIBs
2	Examples of Standard MIBs
2.1	Examples: Collecting System Information by Using ENTITY-MIB
2.2	Examples: Finding Information for Each IP Address Using IP-MIB
2.3	Example: Finding MEP Information Using IEEE8021-CFM-MIB
3	Notifications
4	Configure SNMP to Use IEEE8021-CFM-MIB
5	Implement IF-MIB on the System
5.1	CLI Commands
5.2	Traffic Card Circuits for IF-MIB
5.3	Other Circuits for IF-MIB
5.4	Objects for IF-MIB

1 About Standard SNMP MIBs

Note:: Simple network management protocol (SNMP) examples given in this document use the open source tool Net-SNMP. Depending on the product you use to monitor your network, the examples may appear different from your system.

Note:: The SmartEdge 100 router does not support all MIBs listed in this table. Unsupported MIBs are indicated in the MIB descriptions.

Note:: If you have a support contract, you can download the Enterprise MIBs after you log on at https://ebusiness.ericsson.net.

The following list identifies the standard IETF MIBs supported by the SmartEdge OS :

ALARM-MIB - RFC 3877, Alarm Management Information Base (MIB).
ATM-TC-MIB - RFC 2514, Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management.
ATM-MIB - RFC 2515, Definitions of Managed Objects for ATM Management.
ATM2-MIB - RFC 3606, Definitions of Supplemental Managed Objects for ATM Interface.
BGP4-MIB - RFC 4273, Definitions of Managed Objects for Border Gateway Protocol (BGP-4).
BRIDGE-MIB - RFC 4188, Definitions of Managed Objects for Bridges.
DS1-MIB - RFC 2495, Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types. Unsupported on the SmartEdge 100 router.
DS3-MIB - RFC 2496, Definitions of Managed Objects for the DS3/E3 Interface Type. Unsupported on the SmartEdge 100 router.
ENTITY-MIB - RFC 4133, ENTITY-MIB (Version 3).
ETHERLIKE-MIB - RFC 2665, Definitions of Managed Objects for the Ethernet-like Interface Types.
ETHER-WIS-MIB - RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer .
FRAME-RELAY-DTE-MIB - RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2. Unsupported on the SmartEdge 100 router.
IANAifType-MIB - RFC 1573, Evolution of the Interfaces Group of MIB-II.
IANA-MAU-MIB - RFC 4836, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units.
IEEE8021-CFM-MIB - IEEE Std 802.1ag-2007 (Amendment to IEEE Std 802.1Q-2005) IEEE Standard for Local and metropolitan area networks - Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management. Read access to write objects is not allowed.
IF-INVERTED-STACK-MIB, RFC 2864,The Inverted Stack Table Extension to the Interfaces Group MIB .
IF-MIB - RFC 2863, The Interfaces Group MIB. Detailed information on this MIB is available in the “ Section 5” section.
INET-ADDRESS-MIB - RFC 3291, Textual Conventions for Internet Network Addresses.
IP-FORWARD-MIB - RFC 2096, IP Forwarding Table MIB.
IP-MIB - RFC 2011, SNMPv2 Management Information Base for the Internet Protocol using SMIv2.
MAU-MIB - RFC 4836, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs). Supported for the following port types:
- 60-port FE
- 10-port GE
- 1x10 GE
- ge3-4-port GE
The SmartEdge 100 router does not support this MIB.

Write access to read-write objects is not allowed.

The SmartEdge OS does not support traps for this MIB.
MPLS-L3VPN-STD-MIB - RFC 4382 MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base.
OSPF-MIB - RFC 4750, OSPF Version 2 Management Information Base.
OSPF-TRAP-MIB - RFC 4750, OSPF Version 2 Management Information Base.
PerfHist-TC-MIB - RFC 3593, Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals.
PING-MIB - RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Supported for ping operation. Unsupported for traceroute and lookup operations.
Q-BRIDGE-MIB - RFC 4363, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions.
RADIUS-ACC-CLIENT-MIB - RFC 2620, RADIUS Accounting Client MIB.
RADIUS-AUTH-CLIENT-MIB - RFC 2618, RADIUS Authentication Client MIB.
RFC1213-MIB - RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.
RMON-MIB - RFC 2819, Remote Network Monitoring Management Information Base.
RSTP-MIB - RFC 4318, Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol.
SNMP-COMMUNITY-MIB - RFC 2576, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework. For security reasons, supports the snmpCommunityTable MIB object only through the command-line interface (CLI).
SNMP-FRAMEWORK-MIB - RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.
SNMP-MPD-MIB - RFC 3412, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP).
SNMP-NOTIFICATION-MIB - RFC 3413, Simple Network Management Protocol (SNMP) Applications.
SNMP-TARGET-MIB - RFC 3413, Simple Network Management Protocol (SNMP) Application.
SNMP-USER-BASED-SM-MIB - RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3).
SNMPv2-MIB - RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP).
SNMPv2-SMI - RFC 2578, Structure of Management Information Version 2 (SMIv2).
SNMPV2-TC - RFC 2579, Textual Conventions for SMIv2.
SNMP-VIEW-BASED-ACM-MIB - RFC 3415, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP).
SONET-MIB - RFC 2558, Definitions of Managed Objects for the SONET/SDH Interface Type. Unsupported on the SmartEdge 100 router.
TCP-MIB - RFC 2012, SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2.
UDP-MIB - RFC 2013, SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2.
VRRP-MIB - RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol.

2 Examples of Standard MIBs

The following sections provide examples of standard MIBs.

2.1 Examples: Collecting System Information by Using ENTITY-MIB

The SNMP management system collects information about the chassis type, card type, and number of ports. The EntPhysicalTable table in ENTITY-MIB is indexed by the PhysicalIndex object, which is an arbitrary unique value to identify each physical entity in the chassis. The entAliasMappingTable table in ENTITY-MIB version 3 provides a mechanism to map ifIndex to entPhysicalIndex. A MIB walk on entAliasMappingTable and ifTable shows mapping between ifIndex and physical ports. The mapping should happen regardless of traffic card or platform. A MIB walk on the EntPhysicalTable table returns the chassis, backplane, fan tray, card, and port information as shown in the following example.

The following example displays:

A MIB walk of entPhysicalDescr object in entPhysicalTable.
A MIB walk of entAliasMappingIdentifier object in entAliasMappingTable. The value 0.0 indicates that the particular entity does not map to an existing entry in ifTable.
A MIB walk of the ifDescr object in ifTable.
CLI output of the show hardware command.

entPhysicalDescr.1 = SE800s Chassis
entPhysicalDescr.2 = SE800s Backplane SN:B2014100400106 Rev:1 ID:5a Ver:4
 Mfg.Dt:28-JAN-2005 MAC Address 0:30:88:1:45:8D CLEI code:SPLENDACHS
entPhysicalDescr.3 = SE800s Fan Tray SN:9W024100400130 Rev:2 ID:5a Ver:4
 Mfg.Dt:28-JAN-2005 CLEI code:SNPQCUHXAA
entPhysicalDescr.4 = SE800s Data Slot
entPhysicalDescr.5 = SE800s Data Slot
entPhysicalDescr.6 = SE800s Data Slot
entPhysicalDescr.7 = SE800s Data Slot
entPhysicalDescr.8 = SE800s Data Slot
entPhysicalDescr.9 = SE800s Data Slot
entPhysicalDescr.10 = SE800s Data Slot
entPhysicalDescr.11 = SE800s Data Slot
entPhysicalDescr.12 = SE800s Data Slot
entPhysicalDescr.13 = SE800s Data Slot
entPhysicalDescr.14 = SE800s Data Slot
entPhysicalDescr.15 = SE800s Data Slot
entPhysicalDescr.16 = SE800s Data Slot
entPhysicalDescr.17 = SE800s Data Slot
entPhysicalDescr.18 = Xcrp4-bas - T1/E1 Card SN:D201D5107R0264 Rev:0 ID:5a 
Ver:4 Mfg.Dt:20-DEC-2007 Entitle All Mem Max CLEI code:SNPQCDACHA
entPhysicalDescr.19 = Ethernet Port 7/1
entPhysicalDescr.20 = Ether-12-port Card SN:7U215050701363 Rev:21 ID:5a 
Ver:4 Mfg.Dt:13-FEB-2007 Entitle All Ports All CLEI code:SPLENUHXAA
entPhysicalDescr.21 = Ethernet Port 14/1
entPhysicalDescr.22 = Ethernet Port 14/2
entPhysicalDescr.23 = Ethernet Port 14/3
entPhysicalDescr.24 = Ethernet Port 14/4
entPhysicalDescr.25 = Ethernet Port 14/5
entPhysicalDescr.26 = Ethernet Port 14/6
entPhysicalDescr.27 = Ethernet Port 14/7
entPhysicalDescr.28 = Ethernet Port 14/8
entPhysicalDescr.29 = Ethernet Port 14/9
entPhysicalDescr.30 = Ethernet Port 14/10
entPhysicalDescr.31 = Ethernet Port 14/11
entPhysicalDescr.32 = Ethernet Port 14/12

entAliasMappingIdentifier.19.0 = ifIndex.1
entAliasMappingIdentifier.21.0 = ifIndex.2
entAliasMappingIdentifier.22.0 = 0.0
entAliasMappingIdentifier.23.0 = 0.0
entAliasMappingIdentifier.24.0 = 0.0
entAliasMappingIdentifier.25.0 = 0.0
entAliasMappingIdentifier.26.0 = 0.0
entAliasMappingIdentifier.27.0 = 0.0
entAliasMappingIdentifier.28.0 = ifIndex.3
entAliasMappingIdentifier.29.0 = 0.0
entAliasMappingIdentifier.30.0 = 0.0
entAliasMappingIdentifier.31.0 = 0.0
entAliasMappingIdentifier.32.0 = 0.0

ifDescr.1 = port ethernet 7/1
ifDescr.2 = port ethernet 14/1
ifDescr.3 = port ethernet 14/8
ifDescr.67108864 = mgmt

[local]redback#show  hardware

Fan Tray Status            Present
Fan(s) Status              Normal
Power Supply A Status      No Power
Power Supply B Status      Normal
Active Alarms              Chassis power failure - side A

Slot Type                 Serial No      Rev Ver Mfg Date    Voltage  Temp
---- -------------------- -------------- --- --- ----------- -------- -------
N/A  backplane            B2014100400106   1   4 28-JAN-2005 N/A      N/A
N/A  fan tray             9W024100400130   2   4 28-JAN-2005 N/A      N/A
7    xcrp4-base           D201D5107R0264   0   4 20-DEC-2007 OK       NORMAL
14   ether-12-port        7U215050701363  21   4 13-FEB-2007 OK       NORMAL

2.2 Examples: Finding Information for Each IP Address Using IP-MIB

In this example, you need to find the context and the interface, circuit name, or identifier for a given IP address. You can use the ipAddrTable object in IP-MIB to retrieve the ifIndex object for a given IP address. You must gain access to the ipAddrTable object at the context level. You can obtain a list of the contexts that reside on the SmartEdge router by using syntax similar to the following example:

sh$ snmpbulkwalk -v public -v2c -m SNMPv3-VACM-MIB SE-test vacmContextTable
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."" = STRING:
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."BASIC" = STRING: BASIC
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."local" = STRING: local
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."SECURE" = STRING: SECURE
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."LNS_BASIC" = STRING: LNS_BASIC
SNMP-VIEW-BASED-ACM-MIB::vacmContextName."LNS_SECURE" = STRING: LNS_SECURE
sh-3.00$

Perform the get operation on the ifAdEntIfIndex object with the IP address index as shown in the following example. It is assumed in this example that the IP address is unique in the node across contexts:

sh$ snmpget -c public@BASIC -v2c -m IP-MIB SE-lab2 ipAdEntIfIndex.2.2.2.2
IP-MIB::ipAdEntIfIndex.2.2.2.2 = No Such Instance currently exists at this OID
sh$ snmpget -c public@local -v2c -m IP-MIB SE-lab2 ipAdEntIfIndex.2.2.2.2
IP-MIB::ipAdEntIfIndex.2.2.2.2 = INTEGER: 33554436

Use the ifIndex object to retrieve information about the interface and circuit from the ifTable table.

The following example shows how the same information is displayed in the CLI by using the show context all command:

[local]#show context all
Context Name               Context ID        VPN-RD               Description
------------------------------------------------------------------------------
local                      0x40080001
BASIC                      0x40080002
SECURE                     0x40080003
LNS_BASIC                  0x40080005
LNS_SECURE                 0x40080006
[local]# 
[local]# show ip interface brief
Tue May  6 13:30:07 2008
Name              Address                   MTU   State    Bindings
loop-back1     2.2.2.2/32        1500  Up       (Loopback)
mgmt              10.192.16.214/20          1500  Up       ethernet 7/1
pool              10.192.43.1/24            1500  Up       (Loopback)
server            10.192.100.4/24           1500  Up       ethernet 12/3
victoria          30.1.1.2/24               1500  Bound    ethernet 12/8
[local]#

2.3 Example: Finding MEP Information Using IEEE8021-CFM-MIB

In this example, you perform a mibwalk to discover information about configured maintenence association endpoints (MEPs). You must first configure a new view name using the CLI, then perform the MIB walk using your SNMP management tool. Using the CLI you configure the new Everything view, by doing the following:

Example 1

[local] Redback(config)# snmp view Everything ieee8021CfmMib included 
[local] Redback(config)# snmp community public view Everything 
read-write
[local] Redback(config)# commit 
[local] Redback(config)# end 
[local] Redback#

In your SNMP managment tool, you perform a MIB walk for the Everything view:

getmany -v2c pixie.lab public dot1agCfmMepTable
dot1agCfmMepIfIndex.1.1.2 = 134217744
dot1agCfmMepDirection.1.1.2 = up(2)
dot1agCfmMepPrimaryVid.1.1.2 = 10
dot1agCfmMepActive.1.1.2 = true(1)
dot1agCfmMepFngState.1.1.2 = fngReset(1)
dot1agCfmMepCciEnabled.1.1.2 = true(1)
dot1agCfmMepCcmLtmPriority.1.1.2 = 1
dot1agCfmMepMacAddress.1.1.2 = 00 30 88 02 f2 d8
dot1agCfmMepLowPrDef.1.1.2 = macRemErrXcon(2)
dot1agCfmMepFngAlarmTime.1.1.2 = 1000
dot1agCfmMepFngResetTime.1.1.2 = 1000
dot1agCfmMepHighestPrDefect.1.1.2 = none(0)
dot1agCfmMepDefects.1.1.2 = bDefRDICCM(0)
dot1agCfmMepErrorCcmLastFailure.1.1.2 =
dot1agCfmMepXconCcmLastFailure.1.1.2 =
dot1agCfmMepCcmSequenceErrors.1.1.2 = 0
dot1agCfmMepCciSentCcms.1.1.2 = 107933
dot1agCfmMepNextLbmTransId.1.1.2 = 23
dot1agCfmMepLbrIn.1.1.2 = 40
dot1agCfmMepLbrInOutOfOrder.1.1.2 = 0
dot1agCfmMepLbrBadMsdu.1.1.2 = 0
dot1agCfmMepLtmNextSeqNumber.1.1.2 = 23
dot1agCfmMepUnexpLtrIn.1.1.2 = 0
dot1agCfmMepLbrOut.1.1.2 = 0
dot1agCfmMepTransmitLbmStatus.1.1.2 = true(1)
dot1agCfmMepTransmitLbmDestMacAddress.1.1.2 = 00 00 00 00 00 00
dot1agCfmMepTransmitLbmDestMepId.1.1.2 = 0
dot1agCfmMepTransmitLbmDestIsMepId.1.1.2 = false(2)
dot1agCfmMepTransmitLbmMessages.1.1.2 = 0
dot1agCfmMepTransmitLbmDataTlv.1.1.2 =
dot1agCfmMepTransmitLbmVlanPriority.1.1.2 = 0
dot1agCfmMepTransmitLbmVlanDropEnable.1.1.2 = false(2)
dot1agCfmMepTransmitLbmResultOK.1.1.2 = false(2)
dot1agCfmMepTransmitLbmSeqNumber.1.1.2 = 0
dot1agCfmMepTransmitLtmStatus.1.1.2 = true(1)
dot1agCfmMepTransmitLtmFlags.1.1.2 = useFDBonly(0)
dot1agCfmMepTransmitLtmTargetMacAddress.1.1.2 = 00 00 00 00 00 00
dot1agCfmMepTransmitLtmTargetMepId.1.1.2 = 0
dot1agCfmMepTransmitLtmTargetIsMepId.1.1.2 = false(2)
dot1agCfmMepTransmitLtmTtl.1.1.2 = 64
dot1agCfmMepTransmitLtmResult.1.1.2 = false(2)
dot1agCfmMepTransmitLtmSeqNumber.1.1.2 = 0
dot1agCfmMepTransmitLtmEgressIdentifier.1.1.2 = 00 00  00 00   00 00  00 00
dot1agCfmMepRowStatus.1.1.2 = active(1)

3 Notifications

Use the traps command (in SNMP server configuration mode) to enable the linkUp and linkDown notifications on the IF-MIB encapsulation layers. For more information on the notifications in IF-MIB, see SNMP MIB Notifications.

4 Configure SNMP to Use IEEE8021-CFM-MIB

You may need to modify your SNMP configuration to access objects in IEEE8021-CFM-MIB. This MIB lies within the IEEE 802 branch of the OID tree. All other supported MIBs are a part of the Internet branch of the OID tree.

Add the IEEE8021-CFM-MIB to the view which you defined when configuring SNMP. If you have set your SNMP view to include all MIBs from the internet branch, you must also set your SNMP view to include all MIBs from the ieee8021CfmMib branch. For example, if you set up your SNMP view as follows

snmp view all internet include

Then, you should also include the following command to include the ieee8021CfmMib branch:

snmp view all ieee8021CfmMib include

5 Implement IF-MIB on the System

IF-MIB is a standard MIB as referenced in RFC 2863, The Interfaces Group MIB. Use IF-MIB to display port, IP interface, and selected circuit information.

Use the snmp server command (in global configuration mode) with the enhance ifmib keyword to enable IF-MIB enhancements, such as selected circuit support.

5.1 CLI Commands

Use the following CLI commands to configure IF-MIB on the SmartEdge router . More information on individual commands is available in Command List.

snmp server
traps
context-filter ifmib

5.2 Traffic Card Circuits for IF-MIB

Table 1 describes the traffic card circuits for IF-MIB.

Table 1 Traffic Card Circuits for IF-MIB
Traffic Card	Port Types	Encapsulation	ifType Value	ifDescr Value Format
10ge-1-port ether-12-port ge-10-port ge-20-port ge-4-port ge3-4-port fege-60-2-port	Ethernet		6—ethernetCsmacd	port ethernet <slot>/<port> For example: port ethernet 1/1
atm-ds3-12-port	ATM	aal5	37—atm 49—aal5	port atm <slot>/<port>
	DS-3	aal5	30—ds3
atm-oc12e-1-port atm-oc12-1-port	ATM	aal5	37—atm 49—aal5	port atm-oc12 1/1:1
	SONET path	aal5	50—sonetPath
	SONET	aal5	39—sonet	port atm-oc12 1/1
atm-oc3-2-port atm-oc3-4-port atm-oc3-8-port	ATM	aal5	37—atm 49—aal5	port atm-oc3 1/1:1
	SONET path	aal5	50—sonetPath
	SONET	aal5	39—sonet	port atm-oc3 2 1/1
ch-ds3-12-port ch-ds3-3-port	DS-0s DS-0	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 118—hdlc	port ch-ds3 1/1:1
			82—ds0Bundle	port ch-ds3 1/1:1
			81—ds0	port ch-ds3 1/1:1 DS0 1
	DS-1	cisco-hdlc frame-relay ppp	18—ds1 23—ppp 32—frameRelay 118—hdlc	port ds3 1/1:1 port ds3 1/1:1 port ds3 1/1:1 port ds3 1/1:1
	DS-3	cisco-hdlc frame-relay ppp	23—ppp 30—ds3 32—frameRelay 118—hdlc	port ds3 1/1 port ds3 1/1 port ds3 1/1 port ds3 1/1
ch-e1ds0-24-port	DS-0s DS-0	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 81—ds0 82—ds0Bundle 118—hdlc	port e1 1/1:1 port e1 1/1:1 port e1 1/1:1 port e1 1/1 port e1 1/1 E0 1
	E1	cisco-hdlc frame-relay ppp	18—ds1	port e1 1/1
ch-oc12ds1-1-port	DS-0s DS-0	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 118—hdlc	port ch-oc12 1/1:1
			82—ds0Bundle	port ch-oc12 1/1:1
			80—ds0	port ch-oc12 1/1:1 DS01
	DS-1	cisco-hdlc frame-relay ppp	18—ds1 23—ppp 32—frameRelay 118—hdlc	port ch-oc12 1/1:1
	DS-3	cisco-hdlc frame-relay ppp	23—ppp 30—ds3 32—frameRelay 118—hdlc	port ch-oc12 1/1:1
	SONET Path	cisco-hdlc frame-relay ppp	50—sonetPath	port ch-oc12 1/1:1
	SONET	cisco-hdlc frame-relay ppp	39—sonet	port ch-oc12 1/1
ch-oc12ds3-1-port	DS-3	cisco-hdlc frame-relay ppp	23—ppp 30—ds3 32—frameRelay 118—hdlc	port ch-oc12 1/1:1 port ch-oc12 1/1:1 port ch-oc12 1/1:1 port ch-oc12 1/1:1
	SONET Path	cisco-hdlc frame-relay ppp	50—sonetPath	port ch-oc12 1/1:1
	SONET	cisco-hdlc frame-relay ppp	39—sonet	port ch-oc12 1/1
ch-stm1ds0-3-port AU3	DS-0s DS-0	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 81—ds0 82—ds0Bundle 118—hdlc	port ch-stm1 1/1:1 VC31:1:1 port ch-stm1 1/1:1 VC31:1:1 port ch-stm1 1/1:1 VC31:1:1 port ch-stm1 1/1:1 VC31:1:1 port ch-stm1 1/1:1 VC31:1:1 E0 1
	DS-1	cisco-hdlc frame-relay ppp	18—ds1	port ch-stm1 1/1:1 VC31:1:1
	SONET VT	cisco-hdlc frame-relay ppp	51—sonetVT	port ch-stm1 1/1:1 VC4 1:1:1:1
	SONET Path	cisco-hdlc frame-relay ppp	50—sonetPath	port ch-stm1 1/1 VC3 1
	SONET	cisco-hdlc frame-relay ppp	39—sonet	port ch-stm1 1/1
ch-stm1ds0-3-port AU4	DS-0s DS-0	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 81—ds0 82—ds0Bundle 118—hdlc	port ch-stm1 1/1:1 VC41:1:1 port ch-stm1 1/1:1 VC41:1:1 port ch-stm1 1/1:1 VC41:1:1 port ch-stm1 1/1:1 VC41:1:1 port ch-stm1 1/1:1 VC41:1:1 E0 1
	DS-1	cisco-hdlc frame-relay ppp	18—ds1	port ch-stm1 1/1:1 VC41:1:1
	SONET VT	cisco-hdlc frame-relay ppp	51—sonetVT	port ch-stm1 1/1:1 VC4 1:1:1:1
	SONET path	cisco-hdlc frame-relay ppp	50—sonetPath	port ch-stm1 1/1 VC4 1
	SONET	cisco-hdlc frame-relay ppp	39—sonet	port ch-stm1 1/1
ds3-12-port	DS-3	cisco-hdlc frame-relay ppp	23—ppp 30—ds3 32—frameRelay 118—hdlc	port ds3 1/1 port ds3 1/1 port ds3 1/1 port ds3 1/1
e3-6-port	DS-3	cisco-hdlc frame-relay ppp	23—ppp 30—ds3 32—frameRelay 118—hdlc	port e3 1/1 port e3 1/1 port e3 1/1 port e3 1/1
oc3-8-port oc12-4-port oc48-1-port oc48-4-port	POS	cisco-hdlc frame-relay ppp	23—ppp 32—frameRelay 118—hdlc	port pos 1/1 port pos 1/1 port pos 1/1
	SONET Path	cisco-hdlc frame-relay ppp	50—sonetPath	port pos 1/1
	SONET	cisco-hdlc frame-relay ppp	39—sonet	port pos 1/1

5.3 Other Circuits for IF-MIB

Table 2 describes circuits for IF-MIB.

Table 2 Circuits for IF-MIB
Circuit Name	ifType Value	ifDescr Value Format
MPLS LSP	166—mpls	MPLS LSP <circuitIndex>
GRE tunnel	131—tunnel	GRE <circuitIndex>
Link group access	135-l2vlan	<lg_name> Type:access pvc <pvc_num> ID: <lg_id>
Link group Ethernet	161—ieee8023adLag	<lg_name> Type:ether ID: <lg_id>
Link group HDLC	118—hdlc	<lg_name> Type:hdlc ID: <lg_id>
Link group multilink FR	163—frf16MfrBundle	<lg_name> Type:mfr ID: <lg_id>
Link group multilink PPP	108—pppMultilinkBundle	<lg_name> Type:mp ID: <lg_id>
Link group 802.1Q	135—l2vlan	<lg_name> Type:dot1q pvc <pvc_num> ID: <lg_id>
IP interfaces	53—propVirtual	<interface name>
Loopback	24—softwareLoopback	<interface name>

5.4 Objects for IF-MIB

The following sections contain information about objects for IF-MIB. Index objects for each table are identified before each table by the word “index” in bold.

5.4.1 Non-Table Objects for IF-MIB

Table 3 describes the objects for IF-MIB. All objects in the table are read-only.

Table 3 Non-Table Objects in IF-MIB
Object and Object Identifier	Type	Value Range	Description
ifNumber interfaces 1	Integer32	N/A	Number of network interfaces (regardless of their current state) present on this system.
ifTableLastChange ifMIBObjects 5	TimeTicks	N/A	Value of the sysUpTime object as of the last creation or deletion of an entry in the ifTable. If the number of entries is unchanged since the last reinitialization of the local network management subsystem, this object contains a value of 0 (zero).
ifStackLastChange	TimeTicks	N/A	Value of the sysUpTime object at the time of the last change of the whole interface stack. A change of the interface stack is any creation, deletion, or change in value of any instance of ifStackStatus. If the interface stack is unchanged since the last reinitialization of the local network management subsystem, then this object contains a value of zero.

5.4.2 ifTable

The ifTable table contains information about the interface of an entity. Each sublayer below the internetwork layer of a network interface is considered an interface.

Index: ifIndex

Table 4 describes the objects in ifTable. All objects in the table are read-only.

Table 4 Objects in ifTable
Object and Object Identifier	Type	Value Range	Description
ifIndex ifEntry 1	InterfaceIndex	N/A	Unique value, greater than zero, for each interface. We recommend that values be assigned contiguously starting from 1. The value for each interface sublayer must remain constant from at least one reinitialization of the network management system for the entity to the next reinitialization.
ifDescr ifEntry 2	DisplayString	SIZE (0—255)	Text string containing information about the interface. This string should include the name of the manufacturer, the product name, and the version of the interface hardware or software. The value of this object is the same as the value of the ifName object, which is the textual name of the interface. If several entries represent a single interface, they should have the same ifName value or a common ifName prefix. The prefix is set equal to the corresponding port, channel, or subchannel of the ifName object, with the addition of a suffix.
ifType ifEntry 3	IANAifType	N/A	Type of interface. The Internet Assigned Numbers Authority (IANA) assigns additional values for the ifType object by updating the syntax of the IANAifType text convention. For a list of possible values, their descriptions, and requirements for this object, see Table 17.
ifMtu ifEntry 4	Integer32	N/A	Size of the largest packet sent or received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, the value of this object is the size of the largest network datagram that can be sent on the interface.
ifSpeed ifEntry 5	Gauge32	N/A	Estimate of the current bandwidth of the interface in bits per second. For interfaces with no or an undetermined variance in bandwidth, the value of this object is the nominal bandwidth. If the interface bandwidth is greater than the maximum value of this object, then this object reports its maximum value (4,294,967,295) and the value of the ifHighSpeed object is the interface speed. For a sublayer with no bandwidth, this object is zero.
ifPhysAddress ifEntry 6	PhysAddress	N/A	Interface address at the protocol sublayer. For example, for an 802.x interface, this object normally contains a MAC address. The media-specific MIB of the interface defines the bit and byte ordering and the format of the value of this object. For interfaces with no interface address (for example, a serial line), this object should contain an octet string of zero length.
ifAdminStatus ifEntry 7	Integer	1—up, ready to pass packets 2—down 3—testing	Desired state of the interface. The testing (3) state indicates that no operational packets can pass. When a managed system is initialized, all interfaces start with the ifAdminStatus object in the down (2) state. As a result of either explicit management action or from configuration information retained by the managed system, the ifAdminStatus object is then changed to either the up (1) or testing (3) state or remains in the down (2) state.
ifOperStatus ifEntry 8	Integer	1—up 2—down 3—testing 4—unknown 5—dormant 6—notPresent 7—lowerLayerDown	Current operational state of the interface. The testing (3) state indicates that no operational packets can be passed. If the ifAdminStatus object is down (2), then the ifOperStatus object is down (2). If the ifAdminStatus object changes to up (1), then the ifOperStatus object changes to up (1) if the interface is ready to transmit and receive network traffic. The value of this object changes to dormant (5) if the interface waits for external actions (such as a serial line waiting for an incoming connection). The system remains in the down (2) state if an error prevents it from transitioning to the up (1) state. This object remains in the notPresent (6) state if the interface misses components (for example, hardware).
ifLastChange ifEntry 9	TimeTicks	N/A	Value of the sysUpTime object when the interface entered its current operational state. If the current state was entered before the local network management system was last reinitialized, then this object contains a value of 0 (zero).
ifInOctets ifEntry 10	Counter32	N/A	Total number of octets received on the interface, including framing characters. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifInUcastPkts ifEntry 11	Counter32	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, not addressed to a multicast or broadcast address at this sublayer. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifInDiscards ifEntry 13	Counter32	N/A	Number of discarded inbound packets with detected errors that could prevent delivery to a higher-layer protocol (for example, to free buffer space). Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifInErrors ifEntry 14	Counter32	N/A	Number of inbound packets for packet-oriented interfaces that contain errors, which prevents them from being delivered to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifInUnknownProtos ifEntry 15	Counter32	N/A	Number of packets for packet-oriented interfaces that were received through the interface but discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing, this value is the number of transmission units received through the interface that were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter is always 0. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutOctets ifEntry 16	Counter32	N/A	Total number of octets transmitted from the interface, including framing characters. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutUcastPkts ifEntry 17	Counter32	N/A	Total number of packets that higher-level protocols requested be transmitted and that were not addressed to a multicast or broadcast address at this sublayer, including those that were discarded or not sent. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutDiscards ifEntry 19	Counter32	N/A	Number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their transmission. These packets may be discarded to free buffer space. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutErrors ifEntry 20	Counter32	N/A	Number of outbound packets for packet-oriented interfaces that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the value of this object is the number of outbound transmission units that could not be transmitted because of errors. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.

The following sections provide examples of ifTable.

5.4.2.1 Example: MIB Walk to Collect Port Statistics

Use the ifTable object to collect port statistics that the management system needs. The IfTable object is indexed by the ifIndex object, and the ifIndex values, unique values greater than zero, are assigned for each interface. The MIB walk and snmpget command limit the operation to the maximum value of the ifIndex object. The following example shows sample output from a MIB walk:

sh-3.00# snmpbulkwalk -v2c –c public -m IF-MIB smartedge-lab-1 ifTable

IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
IF-MIB::ifIndex.5 = INTEGER: 5
IF-MIB::ifIndex.6 = INTEGER: 6
IF-MIB::ifIndex.7 = INTEGER: 7
IF-MIB::ifIndex.8 = INTEGER: 8
IF-MIB::ifIndex.9 = INTEGER: 9
IF-MIB::ifIndex.10 = INTEGER: 10
IF-MIB::ifIndex.11 = INTEGER: 11
IF-MIB::ifIndex.12 = INTEGER: 12
IF-MIB::ifIndex.13 = INTEGER: 13
IF-MIB::ifIndex.14 = INTEGER: 14
IF-MIB::ifIndex.15 = INTEGER: 15
IF-MIB::ifIndex.16 = INTEGER: 16
IF-MIB::ifIndex.17 = INTEGER: 17
IF-MIB::ifIndex.29 = INTEGER: 29
IF-MIB::ifIndex.30 = INTEGER: 30
IF-MIB::ifIndex.56 = INTEGER: 56
IF-MIB::ifDescr.1 = STRING: port ethernet 7/1
IF-MIB::ifDescr.2 = STRING: port ethernet 10/1
IF-MIB::ifDescr.3 = STRING: test_mp Type:mp ID:273
IF-MIB::ifDescr.4 = STRING: goo Type:ether ID:278
IF-MIB::ifDescr.5 = STRING: mmpp Type:mp ID:274
IF-MIB::ifDescr.6 = STRING: foo Type:hdlc ID:275
IF-MIB::ifDescr.7 = STRING: moo Type:hdlc ID:276
IF-MIB::ifDescr.8 = STRING: boo Type:hdlc ID:277
IF-MIB::ifDescr.9 = STRING: port ethernet 1/1
IF-MIB::ifDescr.10 = STRING: port ethernet 1/2
IF-MIB::ifDescr.11 = STRING: port ethernet 1/4
IF-MIB::ifDescr.12 = STRING: port ethernet 1/5
IF-MIB::ifDescr.13 = STRING: port ethernet 1/6
IF-MIB::ifDescr.14 = STRING: port ethernet 1/8
IF-MIB::ifDescr.15 = STRING: port ethernet 1/10
IF-MIB::ifDescr.16 = STRING: port ch-oc12 2/1
IF-MIB::ifDescr.17 = STRING: port ch-oc12 2/1:1
IF-MIB::ifDescr.29 = STRING: port ch-oc12 2/1:1
IF-MIB::ifDescr.30 = STRING: port ch-oc12 2/1:1:1
IF-MIB::ifDescr.56 = STRING: port ch-oc12 2/1:1:2
IF-MIB::ifSpeed.1 = Gauge32: 100000000
IF-MIB::ifSpeed.2 = Gauge32: 4294967295
IF-MIB::ifSpeed.3 = Gauge32: 1536000
IF-MIB::ifSpeed.4 = Gauge32: 10000000
IF-MIB::ifSpeed.5 = Gauge32: 3072000
IF-MIB::ifSpeed.6 = Gauge32: 451008000
IF-MIB::ifSpeed.7 = Gauge32: 0
IF-MIB::ifSpeed.8 = Gauge32: 0
IF-MIB::ifSpeed.9 = Gauge32: 10000000
IF-MIB::ifSpeed.10 = Gauge32: 10000000
IF-MIB::ifSpeed.11 = Gauge32: 10000000
IF-MIB::ifSpeed.12 = Gauge32: 10000000
IF-MIB::ifSpeed.13 = Gauge32: 10000000
IF-MIB::ifSpeed.14 = Gauge32: 10000000
IF-MIB::ifSpeed.15 = Gauge32: 10000000
IF-MIB::ifSpeed.16 = Gauge32: 622080000
IF-MIB::ifSpeed.17 = Gauge32: 50112000
IF-MIB::ifSpeed.29 = Gauge32: 44736000
IF-MIB::ifSpeed.30 = Gauge32: 1544000
IF-MIB::ifSpeed.56 = Gauge32: 1544000
IF-MIB::ifPhysAddress.1 = STRING: 0:30:88:0:1c:1
IF-MIB::ifPhysAddress.2 = STRING: 0:0:0:0:0:0
IF-MIB::ifPhysAddress.3 = STRING:
IF-MIB::ifPhysAddress.4 = STRING: 0:30:88:0:32:99
IF-MIB::ifPhysAddress.5 = STRING:
IF-MIB::ifPhysAddress.6 = STRING:
IF-MIB::ifPhysAddress.7 = STRING:
IF-MIB::ifPhysAddress.8 = STRING:
IF-MIB::ifPhysAddress.9 = STRING: 0:30:88:0:32:99
IF-MIB::ifPhysAddress.10 = STRING: 0:30:88:0:32:9a
IF-MIB::ifPhysAddress.11 = STRING: 0:30:88:0:32:9c
IF-MIB::ifPhysAddress.12 = STRING: 0:30:88:0:32:9d
IF-MIB::ifPhysAddress.13 = STRING: 0:30:88:0:32:9e
IF-MIB::ifPhysAddress.14 = STRING: 0:30:88:0:32:a0
IF-MIB::ifPhysAddress.15 = STRING: 0:30:88:0:32:a2
IF-MIB::ifPhysAddress.16 = STRING:
IF-MIB::ifPhysAddress.17 = STRING:
IF-MIB::ifPhysAddress.29 = STRING:
IF-MIB::ifPhysAddress.30 = STRING:
IF-MIB::ifPhysAddress.56 = STRING:
IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifAdminStatus.2 = INTEGER: down(2)
IF-MIB::ifAdminStatus.3 = INTEGER: up(1)
IF-MIB::ifAdminStatus.4 = INTEGER: up(1)
IF-MIB::ifAdminStatus.5 = INTEGER: up(1)
IF-MIB::ifAdminStatus.6 = INTEGER: up(1)
IF-MIB::ifAdminStatus.7 = INTEGER: up(1)
IF-MIB::ifAdminStatus.8 = INTEGER: up(1)
IF-MIB::ifAdminStatus.9 = INTEGER: up(1)
IF-MIB::ifAdminStatus.10 = INTEGER: down(2)
IF-MIB::ifAdminStatus.11 = INTEGER: down(2)
IF-MIB::ifAdminStatus.12 = INTEGER: up(1)
IF-MIB::ifAdminStatus.13 = INTEGER: up(1)
IF-MIB::ifAdminStatus.14 = INTEGER: down(2)
IF-MIB::ifAdminStatus.15 = INTEGER: down(2)
IF-MIB::ifAdminStatus.16 = INTEGER: down(2)
IF-MIB::ifAdminStatus.17 = INTEGER: down(2)
IF-MIB::ifAdminStatus.29 = INTEGER: down(2)
IF-MIB::ifAdminStatus.30 = INTEGER: down(2)
IF-MIB::ifAdminStatus.56 = INTEGER: down(2)
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: notPresent(6)
IF-MIB::ifOperStatus.3 = INTEGER: down(2)
IF-MIB::ifOperStatus.4 = INTEGER: down(2)
IF-MIB::ifOperStatus.5 = INTEGER: down(2)
IF-MIB::ifOperStatus.6 = INTEGER: down(2)
IF-MIB::ifOperStatus.7 = INTEGER: down(2)
IF-MIB::ifOperStatus.8 = INTEGER: down(2)
IF-MIB::ifOperStatus.9 = INTEGER: down(2)
IF-MIB::ifOperStatus.10 = INTEGER: down(2)
IF-MIB::ifOperStatus.11 = INTEGER: down(2)
IF-MIB::ifOperStatus.12 = INTEGER: down(2)
IF-MIB::ifOperStatus.13 = INTEGER: down(2)
IF-MIB::ifOperStatus.14 = INTEGER: down(2)
IF-MIB::ifOperStatus.15 = INTEGER: down(2)
IF-MIB::ifOperStatus.16 = INTEGER: notPresent(6)
IF-MIB::ifOperStatus.17 = INTEGER: lowerLayerDown(7)
IF-MIB::ifOperStatus.29 = INTEGER: lowerLayerDown(7)
IF-MIB::ifOperStatus.30 = INTEGER: lowerLayerDown(7)
IF-MIB::ifOperStatus.56 = INTEGER: lowerLayerDown(7)
IF-MIB::ifLastChange.1 = Timeticks: (1932) 0:00:19.32
IF-MIB::ifLastChange.2 = Timeticks: (1938) 0:00:19.38
IF-MIB::ifLastChange.3 = Timeticks: (2654275) 7:22:22.75
IF-MIB::ifLastChange.4 = Timeticks: (2654276) 7:22:22.76
IF-MIB::ifLastChange.5 = Timeticks: (2654276) 7:22:22.76
IF-MIB::ifLastChange.6 = Timeticks: (2654276) 7:22:22.76
IF-MIB::ifLastChange.7 = Timeticks: (2654276) 7:22:22.76
IF-MIB::ifLastChange.8 = Timeticks: (2654276) 7:22:22.76
IF-MIB::ifLastChange.9 = Timeticks: (2654819) 7:22:28.19
IF-MIB::ifLastChange.10 = Timeticks: (2654838) 7:22:28.38
IF-MIB::ifLastChange.11 = Timeticks: (2654888) 7:22:28.88
IF-MIB::ifLastChange.12 = Timeticks: (2654893) 7:22:28.93
IF-MIB::ifLastChange.13 = Timeticks: (2655096) 7:22:30.96
IF-MIB::ifLastChange.14 = Timeticks: (2655104) 7:22:31.04
IF-MIB::ifLastChange.15 = Timeticks: (2655135) 7:22:31.35
IF-MIB::ifLastChange.16 = Timeticks: (2655241) 7:22:32.41
IF-MIB::ifLastChange.17 = Timeticks: (2655241) 7:22:32.41
IF-MIB::ifLastChange.29 = Timeticks: (2655241) 7:22:32.41
IF-MIB::ifLastChange.30 = Timeticks: (2655241) 7:22:32.41
IF-MIB::ifLastChange.56 = Timeticks: (2655241) 7:22:32.41
IF-MIB::ifInOctets.2 = Counter32: 0
IF-MIB::ifInOctets.3 = Counter32: 0
IF-MIB::ifInOctets.4 = Counter32: 0
IF-MIB::ifInOctets.5 = Counter32: 0
IF-MIB::ifInOctets.6 = Counter32: 0
IF-MIB::ifInOctets.7 = Counter32: 0
IF-MIB::ifInOctets.8 = Counter32: 0
IF-MIB::ifInOctets.9 = Counter32: 0
IF-MIB::ifInOctets.10 = Counter32: 0
IF-MIB::ifInOctets.11 = Counter32: 0
IF-MIB::ifInOctets.12 = Counter32: 0
IF-MIB::ifInOctets.13 = Counter32: 0
IF-MIB::ifInOctets.14 = Counter32: 0
IF-MIB::ifInOctets.15 = Counter32: 0
IF-MIB::ifInUcastPkts.2 = Counter32: 0
IF-MIB::ifInUcastPkts.3 = Counter32: 0
IF-MIB::ifInUcastPkts.4 = Counter32: 0
IF-MIB::ifInUcastPkts.5 = Counter32: 0
IF-MIB::ifInUcastPkts.6 = Counter32: 0
IF-MIB::ifInUcastPkts.7 = Counter32: 0
IF-MIB::ifInUcastPkts.8 = Counter32: 0
IF-MIB::ifInUcastPkts.9 = Counter32: 0
IF-MIB::ifInUcastPkts.10 = Counter32: 0
IF-MIB::ifInUcastPkts.11 = Counter32: 0
IF-MIB::ifInUcastPkts.12 = Counter32: 0
IF-MIB::ifInUcastPkts.13 = Counter32: 0
IF-MIB::ifInUcastPkts.14 = Counter32: 0
IF-MIB::ifInUcastPkts.15 = Counter32: 0
IF-MIB::ifInNUcastPkts.2 = Counter32: 0
IF-MIB::ifInNUcastPkts.3 = Counter32: 0
IF-MIB::ifInNUcastPkts.4 = Counter32: 0
IF-MIB::ifInNUcastPkts.5 = Counter32: 0
IF-MIB::ifInNUcastPkts.6 = Counter32: 0
IF-MIB::ifInNUcastPkts.7 = Counter32: 0
IF-MIB::ifInNUcastPkts.8 = Counter32: 0
IF-MIB::ifInNUcastPkts.9 = Counter32: 0
IF-MIB::ifInNUcastPkts.10 = Counter32: 0
IF-MIB::ifInNUcastPkts.11 = Counter32: 0
IF-MIB::ifInNUcastPkts.12 = Counter32: 0
IF-MIB::ifInNUcastPkts.13 = Counter32: 0
IF-MIB::ifInNUcastPkts.14 = Counter32: 0
IF-MIB::ifInNUcastPkts.15 = Counter32: 0

5.4.2.2 Example: Statistics Collection for ifDescr

Use the ifTable object to collect statistics for port-facing Ethernet port 10/1 that the management system needs. Before collecting statistics for any port, you must retrieve its ifIndex value. A MIB walk of the ifDescr object retrieves the value of the ifIndex object and the corresponding port information as shown in the following example of MIB walk output:

IF-MIB::ifDescr.2 = STRING: port ethernet 10/1

The system compares a string returned for each ifDescr value in a MIB walk with the related port. After the MIB walk returns the desired value, the ifIndex value is obtained from the object index. In this case, the ifIndex value for the Ethernet port 10/1 is 2.

Enter the get command for the ifIndex object to retrieve required statistics. The following examples show how to retrieve port statistics in the CLI by using different show commands:

[local]victoria#show port 7/1 detail
ethernet 7/1 state is Up
Description                :
Line state                 : Up
Admin state                : Up
Encapsulation              : ethernet
MTU size                   : 1500 Bytes
MAC address                : 00:30:88:00:03:47
Media type                 : 100Base-Tx
Speed                      : 100 Mbps
Duplex mode                : full
Active Alarms              : NONE


[local]victoria#show port counters 7/1 detail
Counters for port ethernet 7/1
General Counters
packets sent       : 2037126            packets recvd      : 1191801
bytes sent         : 2316558829         bytes recvd        : 288753306
mcast pkts sent    : 3                  mcast pkts recvd   : 512541
bcast pkts sent    : 0                  bcast pkts recvd   : 0
dropped pkts out   : 0                  dropped pkts in    : 0
pending pkts out   : 0                  pending pkts in    : 0
port drops out     : 0                  port drops in      : 0
invalid ctx out    : 0                  invalid ctx in     : 0
[local]victoria#

5.4.3 ifXTable

The ifXTable table contains a list of interface entries. The number of entries is given by the value of the ifNumber object. This table contains additional objects for the interface table.

Index: ifIndex

Table 5 describes the attributes in ifXTable. All objects in the table are read-only.

Table 5 Objects in ifXTable
Object and Object Identifier	Type	Value Range	Description
ifName ifXEntry 1	DisplayString	N/A	Name of the interface in text. The value of this object is the name of the interface as assigned by the local device and is suitable for use in commands entered at the device console. This value might be a text name, such as “le0,” or a simple port number, such as “1,” depending on the interface-naming syntax of the device. If several entries in the ifTable together represent a single interface named by the device, then each entry has the same value as the ifName object. Note that for an agent that responds to SNMP queries about an interface on some other (proxied) device, the value of the ifName object for that interface is the local name of the proxied device. If no local name exists or this object is otherwise not applicable for an instance, then this object contains a zero-length string.
ifInMulticastPkts ifXEntry 2	Counter32	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, that were addressed to a multicast address at this sublayer. For a MAC layer protocol, the value includes both group and functional addresses. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifInBroadcastPkts ifXEntry 3	Counter32	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, that are addressed to a broadcast address at this sublayer. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutMulticastPkts ifXEntry 4	Counter32	N/A	Total number of packets that higher-level protocols requested and are addressed to a multicast address at this sublayer. This object includes packets that were discarded or not sent. For a MAC layer protocol, this value includes both group and functional addresses. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifOutBroadcastPkts ifXEntry 5	Counter32	N/A	Total number of packets that higher-level protocols requested and were addressed to a broadcast address at this sublayer. This object includes packets that were discarded or not sent. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.

5.4.4 High-Capacity Counter Objects

Table 6 describes high-capacity counter objects. These objects are all 64-bit versions of the basic ifTable counters. All these objects have the same basic semantics as their 32-bit counterparts; however, their syntax has been extended to 64 bits. All objects in the table are read-only.

Table 6 Objects in IfStackTable
Object and Object Identifier	Type	Value Range	Description
ifHCInOctets ifXEntry 6	Counter64	N/A	Total number of octets received on the interface, including framing characters. This object is a 64-bit version of the ifInOctets object. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifHCInUcastPkts ifXEntry 7	Counter64	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, that were not addressed to a multicast or broadcast address at this sublayer. This object is a 64-bit version of the ifInUcastPkts object. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifHCInMulticastPkts ifXEntry 8	Counter64	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, that were addressed to a multicast address at this sublayer. For a MAC layer protocol, this value includes both group and functional addresses. This object is a 64-bit version of the ifInMulticastPkts object. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.
ifHCInBroadcastPkts ifXEntry 9	Counter64	N/A	Number of packets, delivered by this sublayer to a higher layer or sublayer, that were addressed to a broadcast address at this sublayer. This object is a 64-bit version of the ifInBroadcastPkts object. Inconsistencies in the value of this counter can occur when the management system is reinitialized and as indicated by the value of the ifCounterDiscontinuityTime object.

5.4.5 ifStackTable (Interface Stack Group)

Implementation of the Interface Stack group is optional but recommended for all systems. This table contains information on the relationships between the multiple sublayers of network interfaces. In particular, it contains information on which sublayers overlap other sublayers and where each sublayer corresponds to a conceptual row in ifTable. For example, when the sublayer with the ifIndex value x is stacked on the sublayer with ifIndex value y, this table contains:

ifStackStatus.x.y=active

For each ifIndex value, I, that identifies an active interface, at least two instantiated rows in this table are always associated with I. For one of these rows, I is the value of the ifStackHigherLayer object; for the other row, I is the value of the ifStackLowerLayer object. (If I is not involved in multiplexing, then these rows are the only two rows associated with I.)

For example, two rows exist even for an interface that has no other rows stacked above or below it:

ifStackStatus.0.x=active
ifStackStatus.x.0=active

Index: ifStackHigherLayer, ifStackLowerLayer

Table 7 describes the attributes in ifStackTable. All objects in the table are read-only.

Table 7 Objects in IfStackTable
Object and Object Identifier	Type	Value Range	Description
ifStackHigherLayer ifStackEntry 1	InterfaceIndexOrZero	N/A	Value of the ifIndex object that corresponds to the higher sublayer of the relationship. The higher sublayer lays on top of the sublayer identified by the corresponding instance of the ifStackLowerLayer object. If no higher sublayer (below the internetwork layer) exists, then this object has the value 0.
ifStackLowerLayer ifStackEntry 2	InterfaceIndexOrZero	N/A	Value of the ifIndex object that corresponds to the lower sublayer of the relationship. The higher sublayer lays below the sublayer identified by the corresponding instance of the ifStackHigherLayer object. If no lower sublayer exists, then this object has the value 0.
ifStackStatus ifStackEntry 3	RowStatus	N/A	Status of the relationship between two sublayers.
ifStackLastChange ifMIBObjects 6	TimeTicks	N/A	Value of the sysUpTime object at the time of the last change of the whole interface stack. A change of the interface stack is a creation, deletion, or change in value of any instance of the ifStackStatus object. If the interface stack is unchanged since the last reinitialization of the local network management subsystem, then the value of this object is zero.

5.4.6 ifRcvAddressTable (Generic Receive Address Table)

This group of objects is mandatory for all types of interfaces that receive packets and frames addressed to more than one address.

This table contains an entry for each address (broadcast, multicast, or unicast) for which the system receives packets and frames on an interface, except the following types of interfaces:

Interfaces operating in promiscuous mode. Entries are required for addresses for which the system would receive frames if it were not operating in promiscuous mode.
Addresses that have the functional address bit and the bit mask of all functional addresses for which the interface accepts frames. For 802.5 functional addresses, only one entry is required.

A system can use as a source address any unicast address that corresponds to an entry in this table.

Index: ifIndex, ifRcvAddressAddress

Table 8 describes the attributes in ifRcvAddressTable.

Table 8 Objects in ifRcvAddressTable
Object and Object Identifier	Type	Value Range	Description
ifRcvAddressStatus ifRcvAddressEntry 2	RowStatus		Object that creates and deletes rows in ifRcvAddressTable. This object is read-create.
ifRcvAddressType ifRcvAddressEntry 3	Integer	1—other 2—volatile 3—nonVolatile	Entries with the value nonVolatile(3) are saved when the managed system restarts. Entries with the value volatile(2) are valid and exist but are not saved after the next restart of the managed system. Entries having the value other(1) are valid and exist but may not exist after the next restart. This object is read-create.

5.4.7 IF-MIB Groups

IF-MIB contains several groups. In addition to the group required for all IF-MIB users, ifGeneralInformationGroup, additional groups may be mandatory, depending on your network settings. Group Identifiers for each group are listed after each group table below by the word “group identifier” in bold.

5.4.7.1 Fixed-Length Groups

The fixed-length groups for IF-MIB are:

ifFixedLengthGroup
ifHCFixedLengthGroup

One of these two groups is mandatory for network interfaces that use CLIs or that transmit data in fixed-length transmission units. The one you use depends on the speed of your network (the ifSpeed object).

Table 9 describes these groups.

Table 9 ifSpeed Values of Fixed-Length Groups Used by IF-MIB
ifSpeed Value (Bits per Second)	Packet Group
0–20,000,000	ifFixedLengthGroup
20,000,001 or higher	ifHCFixedLengthGroup

Table 10 lists objects and tables for ifFixedLengthGroup packet group.

Table 10 Objects in ifFixedLengthGroup
Object	Table
ifInOctets	ifTable
ifOutOctets	ifTable
ifInUnknownProtos	ifTable
ifInErrors	ifTable
ifOutErrors	ifTable

Group Identifier: ifGroups 2

Table 11 describes objects and tables for the ifHCFixedLengthGroup packet group.

Table 11 Objects in ifHCFixedLengthGroup
Object	Table
ifHCInOctets	ifXTable
ifHCOutOctets	ifXTable
ifInOctets	ifTable
ifOutOctets	ifTable
ifInUnknownProtos	ifTable
ifInErrors	ifTable
ifOutErrors	ifTable

Group Identifier: ifGroups 3

5.4.7.2 Packet Groups

The packet groups for IF-MIB are:

ifPacketGroup
ifHCPacketGroup
ifVHCPacketGroup

One of these three groups is mandatory for network interfaces that are packet-oriented. The one you use depends on the speed of your network (the ifSpeed object).

Table 12 describes these groups.

Table 12 ifSpeed Values of Packet Groups Used by IF-MIB
ifSpeed Value Bits per Second)	Packet Group
0–20,000,000	ifPacketGroup
20,000,001–649,999,999	ifHCPacketGroup
650,000,000 or higher	ifVHCPacketGroup

Table 13 lists objects and tables for the ifPacketGroup packet group.

Table 13 Objects in ifPacketGroup
Object	Table
ifInOctets	ifTable
ifOutOctets	ifTable
ifInUnknownProtos	ifTable
ifInErrors	ifTable
ifOutErrors	ifTable
ifMtu	ifTable
ifInUcastPkts	ifTable
ifInMulticastPkts	ifXTable
ifInBroadcastPkts	ifXTable
ifInDiscards	ifTable
ifOutUcastPkts	ifTable
ifOutMulticastPkts	ifXTable
ifOutBroadcastPkts	ifXTable
ifOutDiscards	ifTable
ifPromiscuousMode	ifXTable

Group Identifier: ifGroups 4

Table 14 describes objects for ifHCPacketGroup.

Table 14 Objects in iifHCPacketGroup
Object	Table
ifHCInOctets	ifXTable
ifHCOutOctets	ifXTable
ifInOctets	ifTable
ifOutOctets	ifTable
ifInUnknownProtos	ifTable
ifInErrors	ifTable
ifOutErrors	ifTable
ifMtu	ifTable
ifInUcastPkts	ifTable
ifInMulticastPkts	ifXTable
ifInBroadcastPkts	ifXTable
ifInDiscards	ifTable
ifOutUcastPkts	ifTable
ifOutMulticastPkts	ifXTable
ifOutBroadcastPkts	ifXTable
ifOutDiscards	ifTable
ifPromiscuousMode	ifXTable

Group Identifier: ifGroups 5

Table 15 lists objects and tables for ifVHCPacketGroup packet group.

Table 15 Objects in ifVHCPacketGroup
Object	Table
ifHCInUcastPkts	ifXTable
ifHCInMulticastPkts	ifXTable
ifHCInBroadcastPkts	ifXTable
ifHCOutUcastPkts	ifXTable
ifHCOutMulticastPkts	ifXTable
ifHCOutBroadcastPkts	ifXTable
ifHCInOctets	ifXTable
ifHCOutOctets	ifXTable
ifInOctets	ifTable
ifOutOctets	ifTable
ifInUnknownProtos	ifTable
ifInErrors	ifTable
ifOutErrors	ifTable
ifMtu	ifTable
ifInUcastPkts	ifTable
ifInMulticastPkts	ifXTable
ifInBroadcastPkts	ifXTable
ifInDiscards	ifTable
ifOutUcastPkts	ifTable
ifOutMulticastPkts	ifXTable
ifOutBroadcastPkts	ifXTable
ifOutDiscards	ifTable
ifPromiscuousMode	ifXTable

Group Identifier: ifGroups 6

5.4.7.3 ifCounterDiscontinuityGroup

This group is mandatory for those network interfaces that maintain counters (that is, those for which one of the ifFixedLengthGroup, ifHCFixedLengthGroup, ifPacketGroup, ifHCPacketGroup, or ifVHCPacketGroup counters is mandatory).

This group contains only one object: ifCounterDiscontinuityTime.

Group Identifier: ifGroups 13

5.4.7.4 ifGeneralInformationGroup

This group is a collection of objects providing information applicable to all network interfaces.

Table 16 lists objects and tables for the ifGeneralInformationGroup packet group.

Table 16 Objects in ifGeneralInformationGroup
Object	Table
ifIndex	ifTable
ifDescr	ifTable
ifType	ifTable
ifSpeed	ifTable
ifPhysAddress	ifTable
ifAdminStatus	ifTable
ifOperStatus	ifTable
ifLastChange	ifTable
ifLinkUpDownTrapEnable	ifXTable
ifConnectorPresent	ifXTable
ifHighSpeed	ifXTable
ifName	ifXTable
ifNumber	none
ifAlias	ifXTable
ifTableLastChange	none

Group Identifier: ifGroups 10

5.4.8 IF-MIB Object Detail

The following sections describe detail for IF-MIB objects.

5.4.8.1 ifAlias

The ifAlias object is the nonvolatile alias name for the interface, port, or circuit that is created by using the description command. This interface name is saved as a string when the router restarts and XCRP reloads. The interface name is automatically set to an octet string of zero length if the description command is not set or the command is not available for that circuit. The object, ifAlias, is available for link-group and 802.1Q circuits.

5.4.8.2 ifDescr and ifName

The ifDescr object contains the same value as ifName when IF-MIB is enabled through SNMP configuration.

The ifName object is the type of the interface in text (for example, the port, channel, or subchannel name). If several entries represent a single interface, they should have the same ifName value or a common ifName prefix and unique suffix.

The IfName and ifDescr objects are set to the value of the ifName object. The value of the ifName object is the port, channel, or subchannel and a prefix and suffix that provide more information about the location and type of port, channel, circuit, or interface.

In the following example, an 802.1Q PVC in an 802.1Q tunnel is created using the CLI. A MIB walk displays the same information as the CLI configuration: the ifName object for an 802.1Q PVC in an 802.1Q tunnel. The system adds the prefix port to each ifName object and a suffix of numbers that provides more information about the location of the port. The CLI configuration is as follows:

[local]Redback(config)#port ethernet 2/3
[local]Redback(config-port)#no shutdown
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 1 encapsulation lqtunnel
[local]Redback(config-port)#dot1q pvc 1 encapsulation 1qtunnel
[local]Redback(config-dot1q-pvc)#dot1q pvc 1:100
[local]Redback(config-dot1q-pvc)#dot1q pvc 1:200
[local]Redback(config-dot1q-pvc)#dot1q pvc 1:300
[local]Redback(config)#port ethernet 2/4
[local]Redback(config-port)#no shutdown
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 2
[local]Redback(config-port)#dot1q pvc 3 encapsulation 1qtunnel
[local]Redback(config-dot1q-pvc)#dot1q pvc 3:100
[local]Redback(config-dot1q-pvc)#dot1q pvc 3:200

The MIB walk output for the above CLI configuration is as follows:

test 91: getmany -v2c test.lab public ifName
ifName.1 = port ethernet 1/1
ifName.2 = port ethernet 2/3
ifName.3 = port ethernet 2/4
ifName.16777222 = port ethernet 2/3 dot1q pvc 1 1/2/6
ifName.16777223 = port ethernet 2/3 dot1q pvc 1:100 1/2/7
ifName.16777224 = port ethernet 2/3 dot1q pvc 1:200 1/2/8
ifName.16777225 = port ethernet 2/3 dot1q pvc 1:300 1/2/9
ifName.16777228 = port ethernet 2/4 dot1q pvc 2 1/2/12
ifName.16777229 = port ethernet 2/4 dot1q pvc 3 1/2/13 
ifName.16777230 = port ethernet 2/4 dot1q pvc 3:100 1/2/14
ifName.16777231 = port ethernet 2/4 dot1q pvc 3:200 1/2/15
ifName.33554432 = mgmt

5.4.8.3 ifType in IF-MIB

Table 17 lists supported values for the ifType object in IF-MIB. For more information, see the IETF document IANAifType-MIB Definitions at http://www.iana.org/assignments/ianaiftype-mib.

Table 17 ifType in IF-MIB
IANAifType-MIB	ifType
6	ethernetCsmacd
18	ds1
19	e1
23	ppp
30	ds3
32	frameRelay
37	atm
39	sonet
49	aal5
50	sonetPath
51	sonetVT
53	propVirtual
81	ds0
82	ds0Bundle
108	pppMultilinkBundle
118	hdlc
131	tunnel
135	l2vlan
161	ieee8023adLag
163	frf16MfrBundle
166	mpls

5.4.8.4 IfIndex Persistence

According to the IETF standard, the system reassigns the value of the ifIndex object to a different interface. When the ifIndex object is assigned to the same interface before SNMP restarts, IF-MIB persistence occurs. Persistence occurs when an ifIndex value is assigned to a specific circuit and that mapping of the ifIndex value to a specific circuit is reapplied after SNMP restarts. In the SmartEdge router , persistence occurs when the value of the ifIndex object is in the range 0 to 0x08ffffff, as shown in Table 18. Dynamic circuits, which are created on demand or by processes other than the router configuration manager (RCM), are not assigned a persistent ifIndex value.

ifIndex persistence exists only for static circuits. A static circuit is created during the configuration of the SmartEdge router and is contained in the startup CLI configuration file or binary database if the configuration file has not changed between reboots.

Table 18 lists the range of values for the ifIndex and ifType objects for which the values are reserved.

Table 18 ifIndex Values for ifType
IfIndex Value	ifType
0—x03ffffff	Physical ports, channels, and subchannels
0x04000000—0x07ffffff	IP interfaces
0x08000000—0x08ffffff	L1 and L2 circuits with RCM authority
0x09000000—0x7fffffff	Nonpersistent index values.