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

#

Standard SNMP MIBs

Contents

1 | About Standard SNMP MIBs
1.1 | Supported Standard SNMP MIBs
2 | Understanding Notifications
3 | Using IEEE8021-CFM-MIB
4 | Using IF-MIB on Ericsson Systems
4.1 | Related CLI Commands
4.2 | IF-MIB Circuits
4.3 | IF-MIB Objects
4.4 | IF-MIB Groups
4.5 | ifIndex Persistency
5 | Using IP-MIB on Ericsson Systems
5.1 | IP-MIB Objects
6 | Using ENTITY-MIB on Ericsson Systems
6.1 | ENTITY-MIB Objects

Copyright | © Ericsson AB 2009–2011. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
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.

# 1 About Standard SNMP MIBs

Simple Network Management Protocol (SNMP) consists of three key components:

- Managed devices - A device that has an SNMP agent and resides on a managed network. The managed network can consist of routers and access server, switches and bridges, hubs, computer hosts, or printers.
- Agents - A software application residing on a device. The agent translates information into a format compatible with SNMP.
- Network-Management Systems (NMSs) - Runs the monitoring applications. These applications provide the bulk of processing and memory resources required for network management.

SNMP uses Management Information Base (MIB) to collect system data. A MIB is a collection of information organized hierarchically. There are two types of MIBs objects:

- Scalar - Define a single object instance.
- Tabular - Define multiple related object instances grouped in MIB tables.

Object Identifiers (OIDs) uniquely identify managed objects in a MIB hierarchy. For Ericsson MIB hierarchy information, see Enterprise MIBs.

Note:
  SNMP examples that are provided 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.

## 1.1 Supported Standard SNMP MIBs

This document applies to both the Ericsson SmartEdge® and SM family routers. However, the software that applies to the SM family of systems is a subset of the SmartEdge OS; some of the functionality described in this document may not apply to SM family routers.

For information specific to the SM family chassis, including line cards, refer to the SM family chassis documentation.

For specific information about the differences between the SmartEdge and SM family routers, refer to the Technical Product Description SM Family of Systems (part number 5/221 02-CRA 119 1170/1) in the `Product Overview` folder of this Customer Product Information library.

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

Note:
  This document only provides specific details on supported objects for the IEEE8021-CFM-MIB, IF-MIB, IP-MIB, and ENTITY-MIB.

- APS-MIB - RFC 3498, SONET Linear Automatic Protection Switching (APS) MIB.
- 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-ITU-ALARM-TC-MIB - RFC 3877, Definitions of Managed Objects for IANA-ITU-Alarm-TC.
- IANA-MAU-MIB - RFC 4836, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units.
- ITU-ALARM-TC-MIB - RFC 3877, Definitions of Managed Objects for ITU-Alarm-MIB.
- 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 Section 4.
- INET-ADDRESS-MIB - RFC 3291, Textual Conventions for Internet Network Addresses.
- IP-FORWARD-MIB - RFC 4292, IP Forwarding Table MIB.
- IP-MIB - RFC 4293, Management Information Base for the Internet Protocol (IP).
- ISIS-MIB - RFC 4444, Management Information Base for Intermediate System to Intermediate System (IS-IS).
- MAU-MIB - RFC 4836, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs). Supported for the following port types:
  - 60-port Fast Ethernet
  - 10-port Gigabit Ethernet 1020
  - 20-port Gigabit Ethernet 1020
  - 1-port 10 Gigabit Ethernet
  - 4-port 10 Gigabit Ethernet DDR
  - 5-port Gigabit Ethernet
  - 1-port 10 Gigabit Ethernet/OC-192c DDR
  - 10-port Gigabit Ethernet DDR
  - 20-port Gigabit Ethernet DDR
  - 4-port Gigabit Ethernet 3
  Note:
    The SmartEdge 100 router does not support this MIB.

  Write access to read-write objects is not allowed.

  Note:
    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 and traceroute 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.
- RMON2-MIB - RFC 2021, Remote Network Monitoring Management Information Base Version 2 using SMIv2.
- 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-CONF - RFC 2580, Conformance Statements for SMIv2.
- 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 4022, Management Information Base for the Transmission Control Protocol (TCP).
- TOKEN-RING-RMON-MIB - RFC 1513, Definitions of Managed Objects for Token-Ring-Remote Network Monitoring.
- TRACEROUTE-MIB - RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Supported for ping and traceroute operations.
- UDP-MIB - RFC 4113, Management Information Base for the User Datagram Protocol (UDP).
- VRRP-MIB - RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol.

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

# 2 Understanding Notifications

To enable the linkUp and linkDown notifications on the IF-MIB encapsulation layers, issue the `traps` CLI command in SNMP server configuration mode. For more information on the notifications in IF-MIB, see SNMP MIB Notifications.

# 3 Using IEEE8021-CFM-MIB

The IEEE8021-CFM-MIB is the Connectivity Fault Management (CFM) module for managing IEEE 802.1ag.

To access objects in IEEE8021-CFM-MIB, the SNMP configuration might need to be modified. This MIB is located within the IEEE 802 branch of the OID tree. All other supported MIBs are a part of the Internet branch of the OID tree.

The following IEEE8021-CFM-MIB objects are supported:

- `dot1agCfmMepTable`: The Maintenance Association End Point (MEP) table.
- `dot1agCfmMepDbTable`: The MEP Database. A database, maintained by every MEP, that maintains received information about the remote MEPs in the Maintenance Domain (MD). The indexing of the MepDbTable uses the Local MEP ID to which the remote MEP is associated.
- `dot1agCfmMdTable`: Maintenance Domain (MD) table. Each row in the table represents a different MD.
- `dot1agCfmLtrTable`: Extension of the MEP table that contains a list of Link-Trace Reply (LTR) messages received by a specific MEP in response to a Link-Trace Message (LTM).
- `dot1agCfmMaNetTable`: Maintenance Association (MA) table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance.

To add the IEEE8021-CFM-MIB to the SNMP view that was defined when configuring SNMP, do the following:

| Set the SNMP all view to include all MIBs from the Internet branch.

    [local]Redback(config)#snmp view all internet include

| Set the SNMP all view to include all MIBs from the ieee8021CfmMib branch.

    [local]Redback(config)#snmp view all ieee8021CfmMib include

To find information about the configured maintenance association endpoints (MEPs), do the following:

1. Configure a new view name (Everything) using the CLI.

    [local]Redback(config)# snmp view Everything internet included
    [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#

2. In your SNMP management tool, perform an SNMP snmpwalk for the Everything view.

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

# 4 Using IF-MIB on Ericsson Systems

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` CLI command (in global configuration mode) with the `enhance ifmib` keyword to enable IF-MIB enhancements, such as selected circuit support.

## 4.1 Related 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

## 4.2 IF-MIB Circuits

The following sections provide details on supported IF-MIB circuits.

### 4.2.1 Line Cards

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

Table 1 Line Card for IF-MIB
Line Card | Port Types | Encapsulation | ifType Value | ifDescr Value Format
--- | --- | --- | --- | ---
10ge-1-port 10ge-oc192-1-port ge-5-port ge-10-port ge2-10-port ge-20-port ge3-4-port ge4-20-port fege-60-2-port | Ethernet | N/A | 6—ethernetCsmacd | port ethernet <slot>/<port> For example: port ethernet 1/1
atm-oc12e-2-port atm-oc3e-8-port | ATM | aal5 | 37—atm 49—aal5 | port atm-oc3 1/1:1
SONET path | aal5 | 50—sonetPath | N/A
SONET | aal5 | 39—sonet | port atm-oc3 2 1/1
82—ds0Bundle | port ch-ds3 1/1:1
81—ds0 | port ch-ds3 1/1:1 DS0 1
oc48-4-port oc3e-8-port oc12e-4-port oc192-1-port 10ge-oc192-1-port | POS ds0 ds1 ds3 | cisco-hdlc frame-relay ppp | 18—ds1 23—ppp 30—ds3 32—frameRelay 51—sonetVT 81—ds0 82—ds0Bundle 118—hdlc | port pos 1/1 port pos 1/1 port pos 1/1
SONET Path | N/A | 50—sonetPath | port pos 1/1
SONET | N/A | 39—sonet | port pos 1/1
ch-oc3oc12-8or2-port | POS channelized-oc3 channelized-oc12 channelized-stm1 channelized-stm4 ds0 ds1 channelized-ds1 ds3 channelized-d3 | cisco-hdlc frame-relay ppp | 18—ds1 23—ppp 30—ds3 32—frameRelay 51—sonetVT 81—ds0 82—ds0Bundle 118—hdlc | port pos 1/1 port pos 1/1 port pos 1/1

### 4.2.2 Other IF-MIB Circuits

Table 2 describes circuits for IF-MIB.

Table 2 Circuits for IF-MIB
Circuit Name | ifType Value | ifDescr Value Format
--- | --- | ---
Port Pseudowire | 6—ethernetCsmacd | <port pseudowire name>Type: port pseudowire ID: <id>
aps pseudo circuit | 23—ppp or hdlc (118) | <aps group name> Type:Protect channel: <chan>[:<subchan>[:<subsubchan>]]
Loopback | 24—softwareLoopback | <interface name>
IP interfaces | 53—propVirtual | <interface name>
Link group multilink PPP | 108—pppMultilinkBundle | <lg_name> Type:mp ID: <lg_id>
Link group HDLC | 118—hdlc | <lg_name> Type:hdlc ID: <lg_id>
GRE tunnel | 131—tunnel | GRE <circuitIndex>
Link group 802.1Q | 135—l2vlan | <lg_name> Type:dot1q pvc <pvc_num> ID: <lg_id>
Link group Ethernet | 161—ieee8023adLag | <lg_name> Type:ether ID: <lg_id>
Link group multilink FR | 163—frf16MfrBundle | <lg_name> Type:mfr ID: <lg_id>
MPLS LSP | 166—mpls | MPLS LSP <circuitIndex>
POS APS group | 171—pos | <aps group name> Type:Protect ID:<aps group id>

## 4.3 IF-MIB Objects

The following sections contain information about IF-MIB objects.

### 4.3.1 IF-MIB Global Objects

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

Table 3 Global Objects in IF-MIB
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ifNumber interfaces 1 | Integer32 | -2147483648..2147483647 | Number of network interfaces (regardless of their current state) present on this system.
ifTableLastChange ifMIBObjects 5 | TimeTicks | 0..4294967295 | 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).

### 4.3.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 OID | Type | Value Range | Description
--- | --- | --- | ---
ifIndex ifEntry 1 | InterfaceIndex Integer32 | 1..2147483647 | Unique value, greater than zero, for each interface. 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 | 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.
ifType ifEntry 3 | IANAifType Integer | 6..246 | Type of interface. See Table 5 for details
ifMtu ifEntry 4 | Integer32 | 2147483648..2147483647 | Size of the largest packet sent or received on the interface, specified in octets. For interfaces that are used for transmitting network data grams, the value of this object is the size of the largest network datagram that can be sent on the interface.
ifSpeed ifEntry 5 | Gauge32 | 0..4294967295 | 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.
ifPhysAddress ifEntry 6 | PhysAddress Octet String | 0..255 | Interface address at the protocol sublayer. For example, for an 802.x interface, this object normally contains a MAC address.
ifAdminStatus ifEntry 7 | Integer | 1—up 2—down 3—testing | Interface status. 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.
ifOperStatus ifEntry 8 | Integer | 1—up 2—down 3—testing 4—unknown 5—dormant 6—notPresent 7—lowerLayerDown | Current interface operational status.
ifLastChange ifEntry 9 | TimeTicks | 0..4294967295 | Value, in seconds, of the sysUpTime object when the interface entered its current operational state..
ifInOctets ifEntry 10 | Counter32 | 0..4294967295 | Total number of octets received on the interface, including framing characters.
ifInUcastPkts ifEntry 11 | Counter32 | 0..4294967295 | Number of packets, delivered by this sublayer to a higher layer or sublayer, not addressed to a multicast or broadcast address at this sublayer.
ifInDiscards ifEntry 13 | Counter32 | 0..4294967295 | Number of discarded inbound packets with detected errors that could prevent delivery to a higher-layer protocol (for example, to free buffer space).
ifInErrors ifEntry 14 | Counter32 | 0..4294967295 | 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 contain errors preventing them from being deliverable to a higher-layer protocol.
ifInUnknownProtos ifEntry 15 | Counter32 | 0..4294967295 | 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 zero.
ifOutOctets ifEntry 16 | Counter32 | 0..4294967295 | Total number of octets transmitted from the interface, including framing characters.
ifOutUcastPkts ifEntry 17 | Counter32 | 0..4294967295 | 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.
ifOutDiscards ifEntry 19 | Counter32 | 0..4294967295 | 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.
ifOutErrors ifEntry 20 | Counter32 | 0..4294967295 | 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.

#### 4.3.2.1 ifType Details

Table 5 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 5 ifType in IF-MIB
IANAifType-MIB | ifType
--- | ---
6 | ethernetCsmacd
18 | ds1
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
133 | ces
135 | l2vlan
161 | ieee8023adLag
163 | frf16MfrBundle
166 | mpls
171 | POS APS group

#### 4.3.2.2 Understanding ifName and ifDescr

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

The ifName object is the interface type in textual format, that is, 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.

To create an 802.1Q PVC in an 802.1Q tunnel with the CLI, do the following:

    [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

When using snmpwalk, 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.

To view the SNMP configuration, do the following:

    test 91: snmpwalk -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.67108864 = mgmt

#### 4.3.2.3 Collecting Port Statistics with ifTable

The ifTable table provides collection of port statistics that the management system needs. The ifTable object is indexed by the ifIndex object, the ifIndex values are assigned for each interface.

To collect ifTable port statistics, do the following:

    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::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

To view port statistics using the CLI, issue the following `show` commands:

    [local]Redback#show port 10/1 detail
    ethernet 10/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]Redback#

    [local]Redback#show port counters 10/1 detail
    Counters for port ethernet 10/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]Redback#

### 4.3.3 ifXTable

The ifXTable table contains a list of interface entries. The ifNumber object provides the number of entries. This table contains additional objects for the interface table.

Table 6 describes the objects in ifXTable. All objects are read-only.

Table 6 Global ifXTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ifName ifXEntry 1 | DisplayString Octet String | 0..255 | 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.
ifInMulticastPkts ifXEntry 2 | Counter32 | 0..4294967295 | Number of packets, delivered by this sublayer to a higher layer or sublayer, that were addressed to a multicast address at this sublayer.
ifInBroadcastPkts ifXEntry 3 | Counter32 | 0..4294967295 | Number of packets, delivered by this sublayer to a higher layer or sublayer, that are addressed to a broadcast address at this sublayer.
ifOutMulticastPkts ifXEntry 4 | Counter32 | 0..4294967295 | Total number of packets that higher-level protocols requested and are addressed to a multicast address at this sublayer.
ifOutBroadcastPkts ifXEntry 5 | Counter32 | 0..4294967295 | Total number of packets that higher-level protocols requested and were addressed to a broadcast address at this sublayer.

Note:
  Table 7 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 are read-only.

Table 7 High-Capacity Counter ifXTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ifHCInOctets ifXEntry 6 | Counter64 | 0..18446744073709551615 | Total number of octets received on the interface, including framing characters.
ifHCInUcastPkts ifXEntry 7 | Counter64 | 0..18446744073709551615 | 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.
ifHCInMulticastPkts ifXEntry 8 | Counter64 | 0..18446744073709551615 | 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.
ifHCInBroadcastPkts ifXEntry 9 | Counter64 | 0..18446744073709551615 | Number of packets, delivered by this sublayer to a higher layer or sublayer, that were addressed to a broadcast address at this sublayer.
ifHCOutOctets ifXEntry 10 | Counter64 | 0..18446744073709551615 | The total number of octets transmitted out of the interface, including framing characters.
ifHCOutUcastPkts ifXEntry 11 | Counter64 | 0..18446744073709551615 | The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.
ifHCOutMulticastPkts ifXEntry 12 | Counter64 | 0..18446744073709551615 | The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses.
ifHCOutBroadcastPkts ifXEntry 13 | Counter64 | 0..18446744073709551615 | The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent.
ifLinkUpDownTrapEnable ifXEntry 14 | Integer | 1—enabled 2—disabled | Indicates whether linkUp/linkDown traps should be generated for this interface. By default, this object is enabled for interfaces which do not operate on top of any other interface (as defined in the ifStackTable).
ifHighSpeed ifXEntry 15 | Gauge32 | 0..4294967295 | An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of `n' then the speed of the interface is somewhere in the range of `n-500,000' to `n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be 0 (zero).
ifPromiscuousMode ifXEntry 16 | TruthValue Integer | 1—true 2—false | true (1): When the station accepts all packets/frames transmitted on the media. false (2): The interface only accepts packets/frames that are addressed to this station.
ifConnectorPresent ifXEntry 17 | TruthValue Integer | 1—true 2—false | This object is true when the interface sublayer has a physical connector.
ifAlias ifXEntry 18 | DisplayString | 0..64 | This object is an alias name for the interface as specified by a network manager, and provides a non-volatile handle for the interface.
ifCounterDiscontinuityTime ifXEntry 19 | TimeStamp TimeTicks | 0..4294967295 | The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the ifTable or ifXTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a 0 (zero) value.

### 4.3.4 ifStackTable

Implementation of the Interface Stack group (ifStackTable) is optional but recommended for all systems. This table contains information on the relationships between the multiple network interface sublayers. 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 8 describes the objects in ifStackTable. All objects are read-only.

Table 8 Objects in IfStackTable
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ifStackHigherLayer ifStackEntry 1 | InterfaceIndexOrZero Integer32 | 0..2147483647 | 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 (zero).
ifStackLowerLayer ifStackEntry 2 | InterfaceIndexOrZero Integer32 | 0..2147483647 | 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 (zero).
ifStackStatus ifStackEntry 3 | RowStatus Integer | 1—active 2—notInService 3—notReady 4—createAndGo 5—createAndWait 6—destroy | Status of the relationship between two sublayers.
ifStackLastChange ifMIBObjects 6 | TimeTicks | 0..4294967295 | 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 0 (zero).

### 4.3.5 ifRcvAddressTable

The Generic Receive Address group (ifRcvAddressTable) is mandatory for all interface types 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 interface types:

- 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 any unicast address as a source address that corresponds to an entry in this table.

`Index:` ifIndex, ifRcvAddressAddress

Table 9 describes the objects in ifRcvAddressTable. All objects are read-create, unless otherwise noted.

Table 9 Objects in ifRcvAddressTable
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ifRcvAddressAddress ifRcvAddressEntry 1 | PhysAddress Octet string | 0..255 | An address for which the system will accept packets/frames on this entry's interface. This object is not-accessible.
ifRcvAddressStatus ifRcvAddressEntry 2 | RowStatus Integer | 1—active 2—notInService 3—notReady 4—createAndGo 5—createAndWait 6—destroy | Object that creates and deletes rows in ifRcvAddressTable.
ifRcvAddressType ifRcvAddressEntry 3 | Integer | 1—other 2—volatile 3—nonVolatile | Entries with the value nonVolatile are saved when the managed system restarts. Entries with the value volatile are valid and exist but are not saved after the next restart of the managed system. Entries having the value other are valid and exist but may not exist after the next restart.

## 4.4 IF-MIB Groups

IF-MIB contains several groups. In addition to the group required for all IF-MIB users, ifGeneralInformationGroup, other groups might be required.

### 4.4.1 ifGeneralInformationGroup

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

Table 10 lists objects and tables inifGeneralInformationGroup.

Table 10 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

`Object Group Identifier:` ifGroups 10

### 4.4.2 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 11 describes these groups.

Table 11 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 12 lists objects and tables in ifFixedLengthGroup.

Table 12 Objects in ifFixedLengthGroup
Object | Table
--- | ---
ifInOctets | ifTable
ifOutOctets | ifTable
ifInUnknownProtos | ifTable
ifInErrors | ifTable
ifOutErrors | ifTable

`Object Group Identifier:` ifGroups 2

Table 13 describes objects and tables in ifHCFixedLengthGroup.

Table 13 Objects in ifHCFixedLengthGroup
Object | Table
--- | ---
ifHCInOctets | ifXTable
ifHCOutOctets | ifXTable
ifInOctets | ifTable
ifOutOctets | ifTable
ifInUnknownProtos | ifTable
ifInErrors | ifTable
ifOutErrors | ifTable

`Object Group Identifier:` ifGroups 3

### 4.4.3 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 14 describes these groups.

Table 14 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 15 lists objects and tables in ifPacketGroup.

Table 15 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

`Object Group Identifier:` ifGroups 4

Table 16 describes objects in ifHCPacketGroup.

Table 16 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

`Object Group Identifier:` ifGroups 5

Table 17 lists objects and tables in ifVHCPacketGroup.

Table 17 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

`Object Group Identifier:` ifGroups 6

### 4.4.4 ifCounterDiscontinuityGroup

This group is mandatory for 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.

`Object Group Identifier:` ifGroups 13

## 4.5 ifIndex Persistency

The ifIndex is a unique value, greater than zero, for each interface. SmartEdge supports an ifIndex value that persists across reboots and switchovers for a subset of interfaces, specifically IP interfaces, ports, and static circuits. To do this, ifIndex persistence maps the ifName and ifIndex object values and retains this mapping across reboots and switchovers.

ifIndex persistence occurs when an ifIndex value assigned to a specific circuit, port (ports can have a range of ifIndex values) or IP interface is reapplied after SNMP restarts. In SmartEdge , the persistent ifIndex assignment uses the range 0 to 0x08ffffff, as shown in Table 18.

ifIndex persistence for ports, IP interfaces, and static circuits must be configured when they are created during the SmartEdge configuration. ifIndex persistent assignments are based on the startup CLI configuration file or the binary database if the configuration file has not changed between reboots.

IF-MIB persistence of ports are lost when the port configuration in the startup CLI configuration file changes.

IF-MIB persistence of static circuits and IP interfaces are lost in the following situations:

- When the redback.cfg checksum changes. This occurs when a user modifies redback.cfg and the `save config` CLI command is not issued.
- When the redback.bin checksum changes. This occurs if the binary database is corrupt.
- When the router configuration manager (RCM) is modified or upgraded.
- When SEOS is upgraded.
- When pvcs or interfaces are deleted with the `no` CLI command and then reinstated, they are assigned new ifIndex values.

Note:
  If the `save config` CLI command is issued, the newly assigned ifIndex values will be persistent at reboot. If the command is not issued, the ifIndex values that were used in the last saved configuration will be persistent at reboot.

Table 18 lists the range of values for the ifIndex and Interface Groups for which the values are reserved.

Table 18 Non-persistent Index Values
IfIndex Value | Interface Group
--- | ---
0—x03ffffff | Physical ports, channels, and subchannels
0x04000000—0x07ffffff | IP interfaces
0x08000000—0x08ffffff | L1 and L2 circuits with RCM authority
0x09000000—0x7fffffff | All other interfaces

# 5 Using IP-MIB on Ericsson Systems

This MIB is composed of a small number of discrete objects and a series of tables meant to form the base for managing IPv4 and IPv6 entities. While some of the objects are meant to be included in all entities, some of the objects are only conditionally mandatory. The unconditionally mandatory objects are mostly counters for IP and ICMP statistics.

## 5.1 IP-MIB Objects

The conditionally mandatory objects for IP-MIB fall into one of several groups:

- objects for use in higher bandwidth situations
- objects for use with IPv4
- objects for use with IPv6
- objects for use on IPv6 routers

### 5.1.1 ipSystemStatsTable

The table containing system wide, IP version specific traffic statistics. This table and the ipIfStatsTable contain similar objects whose difference is in their granularity. Where this table contains system wide traffic statistics, the ipIfStatsTable contains the same statistics but counted on a per-interface basis.

`Index:` ipSystemStatsIPVersion

Table 19 describes the objects in ipSystemStatsTable. All objects in the table are read-only, unless otherwise noted.

Table 19 ipSystemStatsTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ipSystemStatsIPVersion ipSystemStatsEntry 1 | InetVersion Integer | 0—unknown 1—ipv4 2—ipv6 | A value representing a version of the IP protocol. This object is not-accessible.
ipSystemStatsInReceives ipSystemStatsEntry 3 | Counter32 | 0..4294967295 | The total number of input IP datagrams received, including those received in error.
ipSystemStatsHCInReceives ipSystemStatsEntry 4 | Counter64 | 0..18446744073709551615 | The total number of input IP datagrams received, including those received in error. This object counts the same datagrams as ipSystemStatsInReceives, but allows for larger values.
ipSystemStatsInOctets ipSystemStatsEntry 5 | Counter32 | 0..4294967295 | The total number of octets received in input IP datagrams, including those received in error. Octets from datagrams counted in ipSystemStatsInReceives MUST be counted here.
ipSystemStatsHCInOctets ipSystemStatsEntry 6 | Counter64 | 0..18446744073709551615 | The total number of octets received in input IP datagrams, including those received in error.
ipSystemStatsInHdrErrors ipSystemStatsEntry 7 | Counter32 | 0..4294967295 | The number of input IP datagrams discarded due to errors in their IP headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IP options, etc.
ipSystemStatsInNoRoutes ipSystemStatsEntry 8 | Counter32 | 0..4294967295 | The number of input IP datagrams discarded because no route could be found to transmit them to their destination.
ipSystemStatsInAddrErrors ipSystemStatsEntry 9 | Counter32 | 0..4294967295 | The number of input IP datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., ::0). For entities that are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
ipSystemStatsInUnknownProtos ipSystemStatsEntry 10 | Counter32 | 0..4294967295 | The number of locally-addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol
ipSystemStatsInTruncatedPkts ipSystemStatsEntry 11 | Counter32 | 0..4294967295 | The number of input IP datagrams discarded because the datagram frame didn't carry enough data.
ipSystemStatsInForwDatagrams ipSystemStatsEntry 12 | Counter32 | 0..4294967295 | The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful.
ipSystemStatsHCInForwDatagrams ipSystemStatsEntry 13 | Counter64 | 0..18446744073709551615 | The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination.
ipSystemStatsReasmReqds ipSystemStatsEntry 14 | Counter32 | 0..4294967295 | The number of IP fragments received that needed to be reassembled at this interface.
ipSystemStatsReasmOKs ipSystemStatsEntry 15 | Counter32 | 0..4294967295 | The number of IP datagrams successfully reassembled.
ipSystemStatsReasmFails ipSystemStatsEntry 16 | Counter32 | 0..4294967295 | The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
ipSystemStatsInDiscards ipSystemStatsEntry 17 | Counter32 | 0..4294967295 | The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
ipSystemStatsInDelivers ipSystemStatsEntry 18 | Counter32 | 0..4294967295 | The total number of datagrams successfully delivered to IP user-protocols (including ICMP).
ipSystemStatsHCInDelivers ipSystemStatsEntry 19 | Counter64 | 0..18446744073709551615 | The total number of datagrams successfully delivered to IP user-protocols (including ICMP). This object counts the same packets as ipSystemStatsInDelivers, but allows for larger values.
ipSystemStatsOutRequests ipSystemStatsEntry 20 | Counter32 | 0..4294967295 | The total number of IP datagrams that local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipSystemStatsOutForwDatagrams.
ipSystemStatsHCOutRequests ipSystemStatsEntry 21 | Counter64 | 0..18446744073709551615 | The total number of IP datagrams that local IP user-protocols (including ICMP) supplied to IP in requests for transmission. This object counts the same packets as ipSystemStatsOutRequests, but allows for larger values.
ipSystemStatsOutNoRoutes ipSystemStatsEntry 22 | Counter32 | 0..4294967295 | The number of locally generated IP datagrams discarded because no route could be found to transmit them to their destination.
ipSystemStatsOutForwDatagrams ipSystemStatsEntry 23 | Counter32 | 0..4294967295 | The number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path to their final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful.
ipSystemStatsHCOutForwDatagrams ipSystemStatsEntry 24 | Counter64 | 0..18446744073709551615 | This object counts the same packets as ipSystemStatsOutForwDatagrams, but allows for larger values.
ipSystemStatsOutDiscards ipSystemStatsEntry 25 | Counter32 | 0..4294967295 | The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipSystemStatsOutForwDatagrams if any such datagrams met this (discretionary) discard criterion.
ipSystemStatsOutFragReqds ipSystemStatsEntry 26 | Counter32 | 0..4294967295 | The number of IP datagrams that would require fragmentation in order to be transmitted.
ipSystemStatsOutFragOKs ipSystemStatsEntry 27 | Counter32 | 0..4294967295 | The number of IP datagrams that have been successfully fragmented.
ipSystemStatsOutFragFails ipSystemStatsEntry 28 | Counter32 | 0..4294967295 | The number of IP datagrams that have been discarded because they needed to be fragmented but could not be. This includes IPv4 packets that have the DF bit set and IPv6 packets that are being forwarded and exceed the outgoing link MTU.
ipSystemStatsOutFragCreates ipSystemStatsEntry 29 | Counter32 | 0..4294967295 | The number of output datagram fragments that have been generated as a result of IP fragmentation.
ipSystemStatsOutTransmits ipSystemStatsEntry 30 | Counter32 | 0..4294967295 | The total number of IP datagrams that this entity supplied to the lower layers for transmission. This includes datagrams generated locally and those forwarded by this entity.
ipSystemStatsHCOutTransmits ipSystemStatsEntry 31 | Counter64 | 0..18446744073709551615 | This object counts the same datagrams as ipSystemStatsOutTransmits, but allows for larger values.
ipSystemStatsOutOctets ipSystemStatsEntry 32 | Counter32 | 0..4294967295 | The total number of octets in IP datagrams delivered to the lower layers for transmission. Octets from datagrams counted in ipSystemStatsOutTransmits MUST be counted here.
ipSystemStatsHCOutOctets ipSystemStatsEntry 33 | Counter64 | 0..18446744073709551615 | This objects counts the same octets as ipSystemStatsOutOctets, but allows for larger values
ipSystemStatsInMcastPkts ipSystemStatsEntry 34 | Counter32 | 0..4294967295 | The number of IP multicast datagrams received.
ipSystemStatsHCInMcastPkts ipSystemStatsEntry 35 | Counter64 | 0..18446744073709551615 | This object counts the same datagrams as ipSystemStatsInMcastPkts but allows for larger values.
ipSystemStatsInMcastOctets ipSystemStatsEntry 36 | Counter32 | 0..4294967295 | The total number of octets received in IP multicast datagrams. Octets from datagrams counted in ipSystemStatsInMcastPkts MUST be counted here.
ipSystemStatsHCInMcastOctets ipSystemStatsEntry 37 | Counter64 | 0..18446744073709551615 | This object counts the same octets as ipSystemStatsInMcastOctets, but allows for larger values.
ipSystemStatsOutMcastPkts ipSystemStatsEntry 38 | Counter32 | 0..4294967295 | The number of IP multicast datagrams transmitted.
ipSystemStatsHCOutMcastPkts ipSystemStatsEntry 39 | Counter64 | 0..18446744073709551615 | This object counts the same datagrams as ipSystemStatsOutMcastPkts, but allows for larger values.
ipSystemStatsOutMcastOctets ipSystemStatsEntry 40 | Counter32 | 0..4294967295 | The total number of octets transmitted in IP multicast datagrams. Octets from datagrams counted in ipSystemStatsOutMcastPkts MUST be counted here.
ipSystemStatsHCOutMcastOctets ipSystemStatsEntry 41 | Counter64 | 0..18446744073709551615 | This object counts the same octets as ipSystemStatsOutMcastOctets, but allows for larger values.
ipSystemStatsDiscontinuityTime ipSystemStatsEntry 46 | TimeStamp TimeTicks | 0..4294967295 | The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity.
ipSystemStatsRefreshRate ipSystemStatsEntry 47 | Unsigned32 | 0..4294967295 | The minimum reasonable polling interval for this entry. This object provides an indication of the minimum amount of time required to update the counters in this entry. Value is milliseconds.

### 5.1.2 ipAddressTable

This table contains addressing information relevant to the entity's interfaces. This table does not contain multicast address information.

`Index:` ipAddressAddrType, ipAddressAddr

Table 20 describes the objects in ipAddressTable.

Table 20 ipAddressTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
ipAddressSpinLock ip 33 | TestAndIncr | 0..2147483647 | An advisory lock used to allow cooperating SNMP managers to coordinate their use of the set operation in creating or modifying rows within this table. This object is read-write.
ipAddressAddrType ipAddressEntry 1 | InetAddressType Integer | 0—unknown 1—ipv4 2—ipv6 16—dns | The address type of ipAddressAddr. This object is not-accessible.
ipAddressAddr ipAddressEntry 2 | InetAddress Octet String | 0..255 | The IP address to which this entry's addressing information pertains. This object is not-accessible.
ipAddressIfIndex ipAddressEntry 3 | InterfaceIndex Integer32 | 1..2147483647 | The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex. This object is read-create.
ipAddressType ipAddressEntry 4 | Integer | 1—unicast 2—anycast 3—broadcast | The type of address. broadcast(3) is not a valid value for IPv6 addresses (RFC 3513). The default value is unicast (1). This object is read-create.
ipAddressPrefix ipAddressEntry 5 | RowPointer | ObjectID | A pointer to the row in the prefix table to which this address belongs. May be { 0 0 } if there is no such row. The default value is zeroDotZero. This object is read-only.
ipAddressOrigin ipAddressEntry 6 | IpAddressOriginTC | 1—other 2—manual 4—dhcp 5—linklayer 6—random | The origin of the address. manual(2), indicates that the address was manually configured to a specified address, e.g., by user configuration. dhcp(4), indicates an address that was assigned to this system by a DHCP server. linklayer(5) indicates an address created by IPv6 stateless auto-configuration. random(6) indicates an address chosen by the system at random, e.g., an IPv4 address within 169.254/16, or an RFC 041 privacy address. This object is read-only.
ipAddressStatus ipAddressEntry 7 | IpAddressStatusTC Integer | 1—preferred 2—deprecated 3—invalid 4—inaccessible 5—unknown 6—tentative 7—duplicate 8—optimistic | The status of the address. preferred(1) state indicates that this is a valid address that can appear as the destination or source address of a packet. deprecated(2) state indicates that this is a valid but deprecated address that should no longer be used as a source address in new communications, but packets addressed to such an address are processed as expected. invalid(3) state indicates that this isn't a valid address and it shouldn't appear as the destination or source address of a packet. inaccessible(4) state indicates that the address is not accessible because the interface to which this address is assigned is not operational. unknown(5) state indicates that the status cannot be determined for some reason. tentative(6) state indicates that the uniqueness of the address on the link is being verified. Addresses in this state should not be used for general communication and should only be used to determine the uniqueness of the address. duplicate(7) state indicates the address has been determined to be non-unique on the link and so must not be used. optimistic(8) state indicates the address is available for use, subject to restrictions, while its uniqueness on a link is being verified. In the absence of other information, an IPv4 address is always preferred(1). This object is read-create.
ipAddressCreated ipAddressEntry 8 | TimeStamp TimeTicks | 0..4294967295 | The value of sysUpTime at the time this entry was created. If this entry was created prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. This object is read-only.
ipAddressLastChanged ipAddressEntry 9 | TimeStamp TimeTicks | 0..4294967295 | The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. This object is read-only.
ipAddressRowStatus ipAddressEntry 10 | ipAddressRowStatus RowStatus Integer | 1—active 2—notInService 3—notReady 4—createAndGo 5—createAndWait 6—destroy | The status of this conceptual row. Entries with a value of active cannot be modified. Any attempt to modify an object in this entry while the rcfJobRowStatus object equals 'active' results in an inconsistentValue error. To modify objects in an active entry, the rcfJobRowStatus object must first be set to notInService. This object is read-create.
ipAddressStorageType ipAddressEntry 11 | StorageType Integer | 1—other 2—volatile 3—nonVolatile 4—permanent 5—readOnly | The storage type for this conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. The default value is volatile. This object is read-create.

### 5.1.3 Finding Information for Each IP Address

To find the context and the interface, circuit name, or identifier for a given IP address, use the ipAddrTable object in IP-MIB to retrieve the ifIndex object for a given IP address.

To obtain a list of the contexts that reside on the SmartEdge router, do the following:

1. Perform an snmpbulkwalk of vacmContextTable.

    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$

2. Perform an snmpwalk of ifAdEntIfIndex with the IP address index.

    sh$ snmpwalk -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$ snmpwalk -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.

View the same information as above with the CLI, as follows:

    [local]Redback#show context all
    Context Name               Context ID        VPN-RD               Description
    ------------------------------------------------------------------------------
    local                      0x40080001
    BASIC                      0x40080002
    SECURE                     0x40080003
    LNS_BASIC                  0x40080005
    LNS_SECURE                 0x40080006
    [local]Redback#

    [local]Redback#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]Redback#

# 6 Using ENTITY-MIB on Ericsson Systems

ENTITY-MIB contains a mapping table that is used to identify physical components that have identifiers from other standard MIBs. For example, this table can be used along with the physical mapping table to identify the physical location of each repeater port in the rptrPortTable, or each interface in the ifTable.

## 6.1 ENTITY-MIB Objects

The SNMP management system ENTITY-MIB collects information about the chassis type, card type, and number of ports. EntPhysicalTable in ENTITY-MIB is indexed by the PhysicalIndex, 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. Performing an snmpwalk on entAliasMappingTable and ifTable displays mapping between ifIndex and physical ports. The mapping should happen regardless of line card or platform.

### 6.1.1 Global Objects

Global objects are a collection of objects used to represent general entity information, for which a single agent provides management information.

Table 21 describes the global objects in ENTITY-MIB. All objects in the table are read-only.

Table 21 Global Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
entLastChangeTime entityGeneral 1 | TimeStamp TimeTicks | 0..4294967295 | The value of sysUpTime at the time a conceptual row is created, modified, or deleted in any of these tables: entPhysicalTable entAliasMappingTable

### 6.1.2 entPhysicalTable

This table contains one row per physical entity. There is always at least one row for an overall physical entity.

`Index:` entPhysicalIndex

Table 22 describes the objects in entPhysicalTable. All objects in the table are read-only.

Table 22 entPhysicalTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
entPhysicalIndex entPhysicalEntry 1 | PhysicalIndex Integer32 | 1..2147483647 | The index for this entry.
entPhysicalDescr entPhysicalEntry 2 | SnmpAdminString OctetString | 0..255 | A textual description of the physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity, and should be set to a distinct value for each version or model of the physical entity
entPhysicalVendorType entPhysicalEntry 3 | AutonomousType | ObjectID | An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID. An agent should set this object to an enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device. If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.
entPhysicalContainedIn entPhysicalEntry 4 | PhysicalIndexOrZero Integer32 | 0..2147483647 | The value of entPhysicalIndex for the physical entity which 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed. In the event that a physical entity is contained by more than one physical entity (e.g., double-wide modules), this object should identify the containing entity with the lowest value of entPhysicalIndex.
entPhysicalClass entPhysicalEntry 5 | PhysicalClass Integer | 1—other 2—unknown 3—chassis 4—backplane 5—container 6—powerSupply 7—fan 8—sensor 9—module 10—port 11—stack 12—cpu | An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one entity. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned.
entPhysicalParentRelPos entPhysicalEntry 6 | Integer32 | -1..2147483647 | An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.
entPhysicalName entPhysicalEntry 7 | SnmpAdminString OctetString | 0..255 | The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'.

### 6.1.3 entAliasMappingTable

This table contains zero or more rows, representing mappings of logical entity and physical component to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical entity's naming scope. A 'wildcard' mechanism is provided to indicate that an identifier is associated with more than one logical entity.

`Index:` entPhysicalIndex, entAliasLogicalIndexOrZero

Table 23 describes the objects in entAliasMappingTable. All objects in the table are read-only.

Table 23 entAliasMappingTable Objects
Object and OID | Type | Value Range | Description
--- | --- | --- | ---
entAliasLogicalIndexOrZero entAliasMappingEntry 1 | Integer32 | 0..2147483647 | The value of this object identifies the logical entity that defines the naming scope for the associated instance of the entAliasMappingIdentifier object.
entAliasMappingIdentifier entAliasMappingEntry 2 | RowPointer | ObjectID | The value of this object identifies a particular conceptual row associated with the indicated entPhysicalIndex and entLogicalIndex pair.

### 6.1.4 Collecting System Information

To view the chassis, backplane, fan tray, card, and port information using SNMP, do the following.

1. Perform an snmpwalk of entPhysicalDescr in entPhysicalTable.

    sh$ snmpwalk -v2c -c public -m ENTITY-MIB <ip_address> entPhysicalDescr
    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 = Ge-10-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

2. Perform an snmpwalk of entAliasMappingIdentifier in entAliasMappingTable.
   Note:
     The value 0.0 indicates that the particular entity does not map to an existing entry in ifTable.

    sh$ snmpwalk -v2c -c public -m ENTITY-MIB <ip_address> entAliasMappingIdentifier
    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

3. Perform an snmpwalk of ifDescr in ifTable.

    sh$ snmpwalk -v2c -c public -m ENTITY-MIB <ip_address> ifDescr
    ifDescr.1 = port ethernet 7/1
    ifDescr.2 = port ethernet 14/1
    ifDescr.3 = port ethernet 14/8
    ifDescr.67108864 = mgmt

4. Issue the `show hardware` CLI command at the command prompt to view the hardware configured on the system.

    [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   ge-10-port           7U215050701363  21   4 13-FEB-2008 OK       NORMAL