cc/td/doc/product/wanbu/mgx8850/20x
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

ATM MIB File

ATM MIB File

This chapter describes the individual Management Information Base (MIB) objects that comprise the ATM MIB file. The ATM MIB resides in the ATM-MIB.my file.

Contents of this chapter include:

ATM Interface Configuration Parameters Table

This table contains ATM specific configuration information that is associated with an ATM interface beyond those supported using the ifTable.

The object identifier for each MIB object is listed in Table 3-1.


Table 3-1: ATM Interface Configuration Parameters Table Object Identifiers
Name Object Identifier

atmInterfaceConfTable

::= { atmMIBObjects 2 }

atmInterfaceConfEntry

::= { atmInterfaceConfTable1}

atmInterfaceMaxVpcs

::= { atmInterfaceConfEntry 1}

atmInterfaceMaxVccs

::= { atmInterfaceConfEntry 2}

atmInterfaceConfVpcs

::= { atmInterfaceConfEntry 3}

atmInterfaceConfVccs

::= { atmInterfaceConfEntry 4}

atmInterfaceMaxActiveVpiBits

::= { atmInterfaceConfEntry 5}

atmInterfaceMaxActiveVciBits

::= { atmInterfaceConfEntry 6}

atmInterfaceIlmiVpi

::= { atmInterfaceConfEntry 7}

atmInterfaceIlmiVci

::= { atmInterfaceConfEntry 8}

atmInterfaceAddressType

::= { atmInterfaceConfEntry 9 }

atmInterfaceAdminAddress

::= { atmInterfaceConfEntry 10 }

atmInterfaceMyNeighborIpAddress

::= { atmInterfaceConfEntry 11 }

atmInterfaceMyNeighborIfName

::= { atmInterfaceConfEntry 12 }

atmInterfaceCurrentMaxVpiBits

::= { atmInterfaceConfEntry 13 }

atmInterfaceCurrentMaxVciBits

::= { atmInterfaceConfEntry 14 }

atmInterfaceSubscrAddress

::= { atmInterfaceConfEntry 15 }

The MIB objects are listed in Table 3-2.


Table 3-2: ATM Interface Configuration Parameters Table MIB Objects
Name Syntax Description Default Value

atmInterfaceConfTable

Sequence of AtmInterfaceConfEntry

Contains the ATM local interface configuration parameters. This table is used for one entry per ATM interface port.

Max-Access: not-accessible

Status: current

none

atmInterfaceConfEntry

AtmInterfaceConfEntry

Contains the ATM interface configuration parameters and state variables. This list is indexed by ifIndex values of ATM interfaces.

Max-Access: not-accessible

Status: current

The ifindex is listed as the index.

none

atmInterfaceMaxVpcs

INTEGER (0..4096)

Specifies the maximum number of Virtual Path Links (VPC), for example, Permanent Virtual Path Circuits (PVPC) and Switched Virtual Path Circuits (SVPC), which are supported at this ATM interface. At the ATM UNI, the maximum number of VPCs used for PVPCs and SVPCs range from 0 to 256.

Max-Access: read-write

Status: current

none

atmInterfaceMaxVccs

INTEGER (0..65536)

Specifies the maximum number of Virtual Channel Connections (VCC); for example, PVCCs and SVCCs, are supported at this ATM interface.

Max-Access: read-write

Status: current

none

atmInterfaceConfVpcs

INTEGER (0..4096)

Specifies the number of VPCs, for example, PVPC, Soft PVPC, and SVPC established at the ATM interface.

At the ATM UNI, the configured number of VPCs used for PVPCs and SVPCs range from 0 to 256.

Max-Access: read-only

Status: current

none

atmInterfaceConfVccs

INTEGER (0..65536)

Specifies the number of VCCs, for example, PVCC, Soft PVCC, and SVCC established at the ATM interface.

Max-Access: read-only

Status: current

none

atmInterfaceMaxActive
VpiBits

INTEGER (0..12)

Specifies the maximum number of active Virtual Path Identifier (VPI) bits configured for this ATM interface. At the ATM UNI, the maximum number of active VPI bits configured ranges from 0 to 8.

Max-Access: read-write

Status: current

none

atmInterfaceMaxActive
VciBits

INTEGER (0..16)

Specifies the maximum number of active Virtual Channel Identifier (VCI) bits configured for this ATM interface.

Max-Access: read-write

Status: current

none

atmInterfaceIlmiVpi

AtmVpIdentifier

Specifies the VPI value of the VCC that supports the Interim Local Management Interface (ILMI) at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero, ILMI is not supported at this ATM interface.

Max-Access: read-write

Status: current

0

atmInterfaceIlmiVci

AtmVcIdentifier

Specifies the VCI value of the VCC that supports the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero, ILMI is not supported at this ATM interface

Max-Access: read-write

Status: current

16

atmInterfaceAddress
Type

INTEGER {
private (1),
nsapE164 (2),
nativeE164 (3),other (4)}

Specifies the type of primary ATM address that is configured for this ATM interface.

Max-Access: read-only

Status: deprecated

none

atmInterfaceAdmin
Address

AtmAddr

Specifies the primary address assigned for administrative purposes, for example, an address associated with the service provider side of a public network UNI. Thus, the value of this address corresponds with the value of ifPhysAddress at the host side. If this interface has no assigned administrative address, or the address used for administrative purposes is the same as that used for ifPhysAddress, this is an octet string of zero length.

Max-Access: read-only

Status: deprecated


Note   The atmInterfaceAdminAddress object is replaced by atmInterfaceSubscrAddress.

none

atmInterfaceMyNeighborIpAddress

IpAddress

Specifies the IP address of the neighbor system that is connected to the far end of this interface. A Network Management Station can send SNMP messages as IP datagrams. These messages are sent to UDP port 161 to access network management information, which concerns the operation of the system.


Note   The value of this object is obtained in different ways, for example, manual configuration, or through ILMI interaction with the neighbor system.

Max-Access: read-only

Status: current

none

atmInterfaceMyNeighborIfName

DisplayString

Specifies the textual name of the interface on the neighbor system on the far end of this interface and to where this interface connects. If the neighbor system is manageable through SNMP and supports the object ifName, the value of this object must be identical with ifName for the ifEntry of the lowest-level physical interface for this port. If this interface does not have a textual name, the value of this object is a zero length string.


Note   The value of this object can be obtained in different ways, for example, manual configuration, or through ILMI interaction with the neighbor system.

Max-Access: read-only

Status: current

none

atmInterfaceCurrentMaxVpiBits

INTEGER (0..12)

Determines the maximum number of VPI Bits that are currently used at this ATM interface. The value is the minimum of atmInterfaceMaxActiveVpiBits, and the atmInterfaceMaxActiveVpiBits of this interface UNI or NNI peer.

If the interface does not negotiate with the peer to determine the number of VPI Bits that are used on the interface, the value of this object must equal atmInterfaceMaxActiveVpiBits.

Max-Access: read-only

Status: current

none

atmInterfaceCurrentMaxVciBits

INTEGER (0..16)

Determines the maximum number of VCI Bits that are currently used at this ATM interface. The value is the minimum of atmInterfaceMaxActiveVciBits, and the atmInterfaceMaxActiveVciBits of this interface UNI or NNI peer.

If the interface does not negotiate with the peer to determine the number of VCI Bits that is used on the interface, the value of this object must equal atmInterfaceMaxActiveVciBits.

Max-Access: read-only

Status: current

none

atmInterfaceSubscr
Address

AtmAddr

Specifies the identifier that is assigned by a service provider to the network side of a public network UNI. If this interface has no assigned service provider address for other interfaces, this is an octet string of zero length.

Max-Access: read-write

Status: current

none

ATM Interface DS3 Physical Layer Convergence Procedure Table

This table contains the DS3 Physical Layer Convergence Procedure (PLCP) configuration and state parameters for the ATM interfaces, which use DS3 PLCP for carrying ATM cells over DS3.

The object identifier for each MIB object is listed in Table 3-3.


Table 3-3: ATM Interface DS3 PLCP Table Object Identifiers
Name Object Identifier

atmInterfaceDs3PlcpTable

::= { atmMIBObjects 3}

atmInterfaceDs3PlcpEntry

::= { atmInterfaceDs3PlcpTable 1}

atmInterfaceDs3PlcpSEFSs

::= { atmInterfaceDs3PlcpEntry 1}

atmInterfaceDs3PlcpAlarmState

::= { atmInterfaceDs3PlcpEntry 2}

atmInterfaceDs3PlcpUASs

::= { atmInterfaceDs3PlcpEntry 3}

The MIB objects are listed in Table 3-4.


Table 3-4: ATM Interface DS3 PLCP Table MIB Objects
Name Syntax Description Default Value

atmInterfaceDs3Plcp
Table

Sequence of AtmInterfaceDs3PlcpEntry

Contains the ATM interface DS3 PLCP parameters and state variables that are used for one entry per ATM interface port.

Max-Access: not-accessible

Status: current

none

atmInterfaceDs3Plcp
Entry

AtmInterfaceDs3PlcpEntry

Contains the DS3 PLCP parameters and state variables at the ATM interface. It is indexed by the ifIndex value of the ATM interface.

Max-Access: not-accessible

Status: current

The index contains ifIndex.

none

atmInterfaceDs3Plcp
SEFSs

Counter32

Specifies the number of DS3 PLCP Severely Errored Framing Seconds (SEFS). Each SEFS represents a one-second interval that contains one or more SEF events.

Max-Access: read-only

Status: current

none

atmInterfaceDs3Plcp
AlarmState

Integer {noAlarm (1), receivedFarEndAlarm (2), incomingLOF(3)}

Indicates if there is an alarm present for the DS3 PLCP.

The following are the values:

  • receivedFarEndAlarm—Specifies the DS3 PLCP has received an incoming Yellow Signal.

  • incomingLOF—Specifies the DS3 PLCP has declared a loss of frame (LOF) failure condition.

  • noAlarm—Specifies no alarms are present.

A transition from the failure to the no alarm state occurs when no defects, for example, LOF, are received for more than ten seconds.

Max-Access: read-only

Status: current

none

atmInterfaceDs3Plcp
UASs

Counter32

Specifies the counter that is associated with the number of unavailable seconds encountered by PLCP.

Max-Access: read-only

Status: current

none

ATM Interface Transmission Convergence Sublayer Table

This table contains the transmission convergence (TC) sublayer configuration and state parameters of the ATM interfaces, which use TC sublayer to carry ATM cells over SONET/SDH or DS3.

The object identifier for each MIB object is listed in Table 3-5.


Table 3-5: ATM Interface TC Sublayer Table Object Identifiers
Name Object Identifier

atmInterfaceTCTable

::= { atmMIBObjects 4}

atmInterfaceTCEntry

::= { atmInterfaceTCTable 1}

atmInterfaceOCDEvents

::= { atmInterfaceTCEntry 1}

atmInterfaceTCAlarmState

:= { atmInterfaceTCEntry 2}

The MIB objects are listed in Table 3-6.


Table 3-6: ATM Interface TC Sublayer Table MIB Objects
Name Syntax Description Default Value

atmInterfaceTCTable

Sequence of AtmInterfaceTCEntry

Contains the ATM interface TC sublayer parameters and state variables that are used for one entry per ATM interface port.

Max-Access: not-accessible

Status: current

none

atmInterfaceTCEntry

AtmInterfaceTCEntry

Contains the TC subpolar parameters and state variables at the ATM interface. It is indexed by the ifIndex value of the ATM interface.

Max-Access: not-accessible

Status: current

The index contains ifIndex.

none

atmInterfaceOCD
Events

Counter32

Determines the number of times the Out of Cell Delineation (OCD) events occur. If seven consecutive ATM cells have Header Error Control (HEC) violations, an OCD event occurs. A high number of OCD events can indicate a problem with the TC sublayer.

Max-Access: read-only

Status: current

none

atmInterfaceTCAlarm
State

Integer{noAlarm (1), lcdFailure(2)}

Indicates if there is an alarm present for the TC sublayer.

The following are the values used for the atmInterfaceTCAlarmState:

  • lcdFailure(2)—Indicates the TC sublayer is currently in the Loss of Cell Delineation (LCD) defect maintenance state.

  • value noAlarm(1)—Indicates the TC sublayer is currently not in the LCD defect maintenance state.

Max-Access: read-only

Status: current

none


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Sep 15 11:14:44 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.