EZ5 MIB Catalog

CISCO-ATM-IF-MIB

2002-02-13

A MIB module for an ATM interface configuration.

Download CISCO-ATM-IF-MIB.txt Open CISCO-ATM-IF-MIB.txt in a new tab

SCALARS (2) · TABLES (1) · TRAPS (1)

Scalars (2)

NameOID
ciscoAtmIfIlmiAccessGlobalDefaultFilter1.3.6.1.4.1.9.10.14.1.2
ciscoAtmIfNotifsEnabled1.3.6.1.4.1.9.10.14.1.3

Tables (1)

NameOID
ciscoAtmIfTableaugments atmInterfaceConfTable (ATM-MIB)1.3.6.1.4.1.9.10.14.1.1

Traps (1)

NameOID
ciscoAtmIfEvent1.3.6.1.4.1.9.10.14.0.1

END OF TOC

Scalar details

ciscoAtmIfIlmiAccessGlobalDefaultFilter

1.3.6.1.4.1.9.10.14.1.2

INTEGER1 = permitAll2 = permitPrefix3 = permitPrefixAndWellknownGroups4 = permitPrefixAndAllGroups · Integer32

The global default access filter which set the per-switch default access filter for ILMI address registration on all interfaces. permitAll - This permits all ILMI registered addresses. permitPrefix - The address being registered by ILMI should have their prefix portion of the address match the ILMI prefixes used on this interface. If there are any per-interface ILMI address prefixes configured, then the prefixes derived from the switch addresses are not considered ILMI prefixes for this interface. permitPrefixAndWellknownGroups - This is same as 'permitPrefix' but in addition it also allows the well-known group addresses. The well-known group addresses will be the old LECS address and any address matching the ATM Forum address prefix for well known addresses. (i.e.,C5.0079.0000.0000.0000.0000.0000.00A03E) permitPrefixAndAllGroups - This is same as 'permitPrefix' but in addition it allows all group addresses.

ciscoAtmIfNotifsEnabled

1.3.6.1.4.1.9.10.14.1.3

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Allows enabling/disabling of notifications for ATM Interface events

Table details

ciscoAtmIfTable

1.3.6.1.4.1.9.10.14.1.1

augments atmInterfaceConfTable (ATM-MIB)

Index: ifIndex

This table contains ATM local interface configuration parameters, one entry per ATM interface port.

from IF-MIB

ifIndex

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.

ciscoAtmIfType

1.3.6.1.4.1.9.10.14.1.1.1.1

INTEGER1 = other2 = uni3 = pnni4 = iisp5 = nniPvcOnly6 = aini · Integer32

The type of ATM interface which is either a UNI (User to Network), PNNI, IISP or NNI PVC only. To modify the ciscoAtmIftype, ifAdminStatus has to be down and atmIfIlmiAutoConfiguration disabled.

ciscoAtmIfSide

1.3.6.1.4.1.9.10.14.1.1.1.2

INTEGER1 = user2 = network3 = notApplicable · Integer32

The side of ATM interface which is either a user or network side.NotApplicable value implies that ciscoAtmIftype is other than uni or iisp.

ciscoAtmIfUniType

1.3.6.1.4.1.9.10.14.1.1.1.3

INTEGER1 = public2 = private · Integer32

The type of User to Network interface is either private or public. If ciscoAtmIfType is not uni then ciscoAtmIfUniType value should be ignored.

ciscoAtmIfPVPs

1.3.6.1.4.1.9.10.14.1.1.1.4

Integer32 (0..255)

The number of permanent virtual paths at this interface.

ciscoAtmIfPVCs

1.3.6.1.4.1.9.10.14.1.1.1.5

Integer32 (0..65535)

The number of permanent virtual channels at this interface.

ciscoAtmIfActiveSVPs

1.3.6.1.4.1.9.10.14.1.1.1.6

Gauge32

The number of active switched virtual paths at this interface.

ciscoAtmIfActiveSVCs

1.3.6.1.4.1.9.10.14.1.1.1.7

Gauge32

The number of active switched virtual channels at this interface.

ciscoAtmIfTotalConnections

1.3.6.1.4.1.9.10.14.1.1.1.8

Gauge32

The total number of existing connections at this interface.

ciscoAtmIfConfVplIf

1.3.6.1.4.1.9.10.14.1.1.1.9

Integer32 (0..65535)

The number of configured VP interfaces at this physical interface.

ciscoAtmIfPortType

1.3.6.1.4.1.9.10.14.1.1.1.10

INTEGER1 = other2 = cpu3 = ethernet4 = oc3Utp5 = oc3SingleModeFiber6 = oc3MultiModeFiber7 = oc12SingleModeFiber8 = ds39 = e310 = ds111 = e112 = oc3Utp313 = oc3Utp514 = oc3SmIr15 = oc3SmIrPlus16 = oc3SmLr17 = oc3Pof18 = oc12MultiModeFiber19 = oc12SmIr20 = oc12SmIrPlus21 = oc12SmLr22 = oc12Pof23 = oc12SmLr224 = oc12SmLr325 = atm25 · Integer32

The type of physical layer medium on the port.

ciscoAtmIfXmitLed

1.3.6.1.4.1.9.10.14.1.1.1.11

INTEGER1 = off2 = steadyGreen3 = steadyYellow4 = steadyRed5 = flashGreen6 = flashYellow7 = flashRed · Integer32

The transmit LED color of this port.

ciscoAtmIfRecvLed

1.3.6.1.4.1.9.10.14.1.1.1.12

INTEGER1 = off2 = steadyGreen3 = steadyYellow4 = steadyRed5 = flashGreen6 = flashYellow7 = flashRed · Integer32

The receive LED color of this port.

ciscoAtmIfXmitCells

1.3.6.1.4.1.9.10.14.1.1.1.13

Counter32

The number of cells transmitted of this interface, including p2p and p2mp cells.

ciscoAtmIfRecvCells

1.3.6.1.4.1.9.10.14.1.1.1.14

Counter32

The number of cells received of this interface, including p2p and p2mp cells.

ciscoAtmIfSvcMinVci

1.3.6.1.4.1.9.10.14.1.1.1.15

INTEGER (0..255) · Integer32

The minimum of the range of values from which VCI's are assigned to new SVC connections. By this value being larger, more VCI's are reserved for setting up PVCs. This applies to every VPI of the physical interface and every logical port. The object is deprecated because it is recommended to use ciscoAtmInterfaceConfMinSvccVci of the CISCO-ATM2-MIB which is meant for the same purpose.

ciscoAtmIfIlmiConfiguration

1.3.6.1.4.1.9.10.14.1.1.1.16

INTEGER1 = enabled2 = disabled · Integer32

Enable/Disable ILMI configuration on this interface. The configuration takes effect only on the next interface restart. Disabling this object will also disable atmIfIlmiAddressRegistration and atmIfIlmiAutoConfiguration and atmIfIlmiKeepAlive

ciscoAtmIfIlmiAddressRegistration

1.3.6.1.4.1.9.10.14.1.1.1.17

INTEGER1 = enabled2 = disabled · Integer32

Enable/Disable ILMI Address Registration on on this interface. The configuration takes effect only on the next interface restart.

ciscoAtmIfIlmiAutoConfiguration

1.3.6.1.4.1.9.10.14.1.1.1.18

INTEGER1 = enabled2 = disabled · Integer32

Enable/Disable ILMI link and interface type determination. The configuration takes effect only on the next interface restart.

ciscoAtmIfIlmiKeepAlive

1.3.6.1.4.1.9.10.14.1.1.1.19

Integer32 (0..65535) · seconds

The amount of time that should elapse between successive ILMI keepalive messages sent on this interface. A value of 0 disables ILMI keepalive messages on this interface.

ciscoAtmIfSoftVcDestAddress

1.3.6.1.4.1.9.10.14.1.1.1.20

NsapAtmAddrThe ATM address used by the network entity. The address types are NSAP (20 octets). SIZE (20) · OCTET STRING

The 20 byte ATM address of the destination ATM interface for soft ATM PVC/PVP

ciscoAtmIfUniSignallingVersion

1.3.6.1.4.1.9.10.14.1.1.1.21

INTEGER1 = notApplicable2 = atmfUni3Dot03 = atmfUni3Dot14 = atmfUni4Dot0 · Integer32

The version of UNI signalling that is currently being used on the interface. The appropriate value, either atmfUni3Dot0, atmfUni3Dot1 or atmfUni4Dot0, is used when the interface is an UNI or IISP interface. The value notApplicable is used when the interface is a PNNI interface or when signalling is disabled. This may reflect a manually configured value for the signalling version, or may be determined by other means such as auto-configuration.Setting this variable to a value of 'notApplicable' is not allowed. To modify the ciscoAtmIfUniSignallingVersion, ifAdminStatus has to be down and atmIfIlmiAutoConfiguration disabled.

ciscoAtmIfSvcUpcIntent

1.3.6.1.4.1.9.10.14.1.1.1.22

INTEGER1 = passing2 = tagging3 = dropping · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs. This object has been deprecated in favor of the per-service category objects ciscoAtmIfSvcUpcIntentCbr, ciscoAtmIfSvcUpcIntentVbrRt, ciscoAtmIfSvcUpcIntentVbrNrt, ciscoAtmIfSvcUpcIntentAbr, ciscoAtmIfSvcUpcIntentUbr. Note that if those objects are set to different values, the return value for this object cannot be correct.

ciscoAtmIfAddressType

1.3.6.1.4.1.9.10.14.1.1.1.23

INTEGER1 = nsap2 = esi3 = e1644 = null · Integer32

An indication of the type of the ATM addresses on this interface. To configure a new atm address, set ciscoAtmIfAddress to the address, then set this object to ether nsap(1), or esi(2), or e164(3), depending on the type of address of ciscoAtmIfAddress. To delete the address, set this object to null(4). Adding nsap address type to this interface has the effect of canceling the existing esi address, if there is one. Similarly, adding the esi address on this interface also has the effect of removing the existing nsap address. The value of ciscoAtmIfAddress has no effect when this object is set to null(4). For the switch, the nsap/esi address can only exist on the cpu port for signalling applications.

ciscoAtmIfAddress

1.3.6.1.4.1.9.10.14.1.1.1.24

OCTET STRING SIZE (0 | 6 | 8 | 20)

The ATM address of this interface, which can be either nsap, esi or e164. For the switch, the nsap/esi address can only exist on the cpu port.

ciscoAtmIfWellKnownVcMode

1.3.6.1.4.1.9.10.14.1.1.1.31

INTEGER1 = automatic2 = manual3 = manualDeleteUponEntry · Integer32

Indicates whether well-known VCs should be automatically or manually created for the interface. In automatic(1) mode, well-known VCs will be created with default VPI/VCI values upon startup or upon entry to the automatic mode. While in this mode, well-known VCs will not be allowed to be deleted or modified by user commands. This is the default mode at startup for equipment which supports automatic well-known VC creation. In manual(2) mode, well-known VCs won't be automatically created. Instead, the user will be allowed to delete and create PVCs with the reserved encapsulation types aalQsAal, aal5Ilmi, and aal5Pnni as applicable. And these PVCs will be allowed to have VCI values in the range <5-16383>, instead of <32-16383>. The manualDeleteUponEntry(3) action causes any existing VCs with reserved encapsulation types (aalQsAal, aal5Ilmi or aal5Pnni) to be deleted for this interface as it enters the manual state.

ciscoAtmIfSignallingAdminStatus

1.3.6.1.4.1.9.10.14.1.1.1.32

INTEGER1 = enabled2 = disabled · Integer32

Enable/Disable signalling/sscop on this interface.The disabled(2) action causes all the active SVCs on this interface to be cleared.

ciscoAtmIfCdLed

1.3.6.1.4.1.9.10.14.1.1.1.33

INTEGER1 = off2 = steadyGreen · Integer32

The Cd LED color of this port.

ciscoAtmIfIlmiAccessFilter

1.3.6.1.4.1.9.10.14.1.1.1.34

INTEGER1 = permitAll2 = permitPrefix3 = permitPrefixAndWellknownGroups4 = permitPrefixAndAllGroups5 = useGlobalDefaultFilter · Integer32

The access filter which allows or denies certain ILMI registered addresses on this interface when ciscoAtmIfIlmiAddressRegistration is set to enable(1). permitAll - This permits all ILMI registered addresses. permitPrefix - The address being registered by ILMI should have their prefix portion of the address match the ILMI prefixes used on this interface. If there are any per-interface ILMI address prefixes configured, then the prefixes derived from the switch addresses are not considered ILMI prefixes for this interface. permitPrefixAndWellknownGroups - This is same as 'permitPrefix' but in addition it also allows the well-known group addresses. The well-known group addresses will be the old LECS address and any address matching the ATM Forum address prefix for well known addresses. (i.e.,C5.0079.0000.0000.0000.0000.0000.00A03E) permitPrefixAndAllGroups - This is same as 'permitPrefix' but in addition it allows all group addresses. useGlobalDefaultFilter - It indicates that this interface uses the per-switch global default filter

ciscoAtmIfConfigAESA

1.3.6.1.4.1.9.10.14.1.1.1.35

OCTET STRING SIZE (0 | 7 | 20)

The ATM End System Address (AESA) of this interface can be configured by entering the full 20 octet AESA, or the 6 octet ESI and 1 octet Selector Byte. If the ESI and Selector Byte are entered, the full AESA will be formed using a 13 octet prefix from ILMI. The full AESA can be read using ciscoAtmIfDerivedAESA. A length of zero indicates that no AESA is configured. For the switch, the AESA address can only exist on the cpu port.

ciscoAtmIfDerivedAESA

1.3.6.1.4.1.9.10.14.1.1.1.36

AtmAddrThe ATM address used by the network entity. The address types are: no address (0 octets), E.164 (8 octets), network prefix (13 octets), and NSAP (20 octets). Note: The E.164 address is encoded in BCD format. SIZE (0 | 8 | 13 | 20) · OCTET STRING

The ATM End System Address (AESA) of this interface. The AESA is configured using ciscoAtmIfConfigAESA or can be automatically generated. A length of zero indicates that no AESA is specified. For the switch, the AESA address can only exist on the cpu port.

ciscoAtmIfE164Address

1.3.6.1.4.1.9.10.14.1.1.1.37

AtmAddrThe ATM address used by the network entity. The address types are: no address (0 octets), E.164 (8 octets), network prefix (13 octets), and NSAP (20 octets). Note: The E.164 address is encoded in BCD format. SIZE (0 | 8 | 13 | 20) · OCTET STRING

The ATM E164 address of this interface. When a native E.164 number is configured for this inteface, only native E.164 numbers are transmitted/received as the called/calling party numbers. The presence of an ATM E164 address allows both an algorithmic translation between the native E164 number and E164 AESA address formats (see ciscoAtmIfE164AutoConversionOnly) and use of the ATM E164 Address for the calling/called party number of transmitted/received calls. Entering an address will disable ciscoAtmIfE164AutoConversionOnly. An address of length zero indicates that no address is specified. For the switch, the E164 address cannot exist on the cpu port.

ciscoAtmIfE164AutoConversionOnly

1.3.6.1.4.1.9.10.14.1.1.1.38

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Enable/Disable E164 auto conversion only on this interface. The E164 auto-conversion allows for algorithmic translation between the native E164 number and E164 AESA address formats. This object is used when there is no native E.164 number specified for this interface (see ciscoAtmIfE164Address), to specify that only native E.164 numbers are transmitted/received as the called/calling party numbers and to enable/disable E164 auto-conversion. For the switch, E164 auto-conversion cannot exist on the cpu port.

ciscoAtmIfRxCellUpcViolations

1.3.6.1.4.1.9.10.14.1.1.1.39

Counter32

The total number of nonconforming cells detected by Usage Parameter Control (UPC) for cells received on this interface. This object is not instantiated on systems that do not have support for collecting such statistics.

ciscoAtmIfRxCellDiscards

1.3.6.1.4.1.9.10.14.1.1.1.40

Counter32

The total number of cells that were discarded within the switch. The cells can be discarded due to non conformance detected by Usage Parameter Control (UPC) or queue overflows within the switch. This object is not instantiated on systems that do not have support for collecting such statistics.

ciscoAtmIfIlmiFSMState

1.3.6.1.4.1.9.10.14.1.1.1.41

INTEGER1 = down2 = restarting3 = waitDevType4 = deviceAndPortTypeComplete5 = awaitPnniConfig6 = pnniConfigComplete7 = awaitRestartAck8 = upAndNormal · Integer32

The ILMI states meaningful when the value of ciscoAtmIfIlmiConfiguration indicates that the ILMI is enabled for an ATM interface: down -- Stopped or just booted or interface down restarting -- Establishing link connectivity waitDevType -- Awaiting device type from peer deviceAndPortTypeComplete -- Determined device and/or port type awaitPnniConfig -- Awaiting PNNI configuration from peer pnniConfigComplete -- Completed interface PNNI configuration awaitRestartAck -- Awaiting peer range values after restart upAndNormal -- Up and normal.

ciscoAtmIfIlmiUpDownChanges

1.3.6.1.4.1.9.10.14.1.1.1.42

Counter32

The number of times ILMI enters and leaves the state of upAndNormal.

ciscoAtmIfSscopFSMState

1.3.6.1.4.1.9.10.14.1.1.1.43

INTEGER1 = idle2 = outgoingConnectionPending3 = incomingConnectionPending4 = dataTransferReady5 = outgoingDisconnectionPending6 = outgoingResyncPending7 = incomingResyncPending8 = outgoingRecoveryPending9 = incomingRecoveryPending10 = concurrentResyncPending · Integer32

Reference: ITU-T Recommendation Q.2110 (07/94)

The SSCOP state for an ATM interface as defined by the ITU-T. The state is idle when the interface is down or SSCOP is not enabled on the ATM interface

ciscoAtmIfSscopUpDownChanges

1.3.6.1.4.1.9.10.14.1.1.1.44

Counter32

The number of times SSCOP enters and leaves the state of DataTransferReady.

ciscoAtmIfSvcUpcIntentCbr

1.3.6.1.4.1.9.10.14.1.1.1.45

UpcMethod1 = passing2 = tagging3 = droppingA textual convention defining options for Usage Parameter Control: passing : take no action on cells considered to violate the traffic contract. tagging : set the CLP bit in the header of cells considered to violate the traffic contract. dropping: discard cells considered to violate the traffic contract. · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for Constant Bit Rate SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs.

ciscoAtmIfSvcUpcIntentVbrRt

1.3.6.1.4.1.9.10.14.1.1.1.46

UpcMethod1 = passing2 = tagging3 = droppingA textual convention defining options for Usage Parameter Control: passing : take no action on cells considered to violate the traffic contract. tagging : set the CLP bit in the header of cells considered to violate the traffic contract. dropping: discard cells considered to violate the traffic contract. · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for Variable Bit Rate - Real Time SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs.

ciscoAtmIfSvcUpcIntentVbrNrt

1.3.6.1.4.1.9.10.14.1.1.1.47

UpcMethod1 = passing2 = tagging3 = droppingA textual convention defining options for Usage Parameter Control: passing : take no action on cells considered to violate the traffic contract. tagging : set the CLP bit in the header of cells considered to violate the traffic contract. dropping: discard cells considered to violate the traffic contract. · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for Variable Bit Rate - Non Real Time SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs.

ciscoAtmIfSvcUpcIntentAbr

1.3.6.1.4.1.9.10.14.1.1.1.48

UpcMethod1 = passing2 = tagging3 = droppingA textual convention defining options for Usage Parameter Control: passing : take no action on cells considered to violate the traffic contract. tagging : set the CLP bit in the header of cells considered to violate the traffic contract. dropping: discard cells considered to violate the traffic contract. · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for Available Bit Rate SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs.

ciscoAtmIfSvcUpcIntentUbr

1.3.6.1.4.1.9.10.14.1.1.1.49

UpcMethod1 = passing2 = tagging3 = droppingA textual convention defining options for Usage Parameter Control: passing : take no action on cells considered to violate the traffic contract. tagging : set the CLP bit in the header of cells considered to violate the traffic contract. dropping: discard cells considered to violate the traffic contract. · Integer32

Determines the policing (Usage Parameter Control or UPC) action to take for Unspecified Bit Rate SVCs established through this interface. Values other than passing are allowed only if policing is supported on the interface. Also serves to determine UPC to use on the terminating (destination) half-leg of Soft PVCs.

Trap details

ciscoAtmIfEvent

1.3.6.1.4.1.9.10.14.0.1

This notification is generated when ever ILMI or SSCOP FSM state changes

ciscoAtmIfIlmiFSMState

1.3.6.1.4.1.9.10.14.1.1.1.41

INTEGER1 = down2 = restarting3 = waitDevType4 = deviceAndPortTypeComplete5 = awaitPnniConfig6 = pnniConfigComplete7 = awaitRestartAck8 = upAndNormal · Integer32

The ILMI states meaningful when the value of ciscoAtmIfIlmiConfiguration indicates that the ILMI is enabled for an ATM interface: down -- Stopped or just booted or interface down restarting -- Establishing link connectivity waitDevType -- Awaiting device type from peer deviceAndPortTypeComplete -- Determined device and/or port type awaitPnniConfig -- Awaiting PNNI configuration from peer pnniConfigComplete -- Completed interface PNNI configuration awaitRestartAck -- Awaiting peer range values after restart upAndNormal -- Up and normal.

ciscoAtmIfSscopFSMState

1.3.6.1.4.1.9.10.14.1.1.1.43

INTEGER1 = idle2 = outgoingConnectionPending3 = incomingConnectionPending4 = dataTransferReady5 = outgoingDisconnectionPending6 = outgoingResyncPending7 = incomingResyncPending8 = outgoingRecoveryPending9 = incomingRecoveryPending10 = concurrentResyncPending · Integer32

Reference: ITU-T Recommendation Q.2110 (07/94)

The SSCOP state for an ATM interface as defined by the ITU-T. The state is idle when the interface is down or SSCOP is not enabled on the ATM interface

↑ To TOC