CISCO-ATM-CONN-MIB
AI MIB Summary
The CISCO-ATM-CONN-MIB extends the standard VPL/VCL table to monitor and manage Virtual Path and Virtual Channel connection states, including identifiers, traffic parameters, and status flags, on Cisco ATM switches. This module enables granular tracking of individual ATM circuit configurations and operational health for network troubleshooting and capacity planning.
This MIB module is a cisco extension to VPL/VCL table defined in rfc1695 for ATM switch connection management.
Main OID:
ciscoAtmConnMIB.1.3.6.1.4.1.9.10.13
148
Objects
Active
Status
9
Dependencies
Imported Objects
Objects
148 total| Object Name |
|---|
ciscoAtmConnMIBThis MIB module is a cisco extension to VPL/VCL table defined
in rfc1695 for ATM switch connection management. MODULE-IDENTITY .1.3.6.1.4.1.9.10.13 |
ciscoAtmConnMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1 |
ciscoAtmVpl OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.1 |
ciscoAtmVplTableThe Virtual Path Link extension Table. SEQUENCE OF CiscoAtmVplEntry .1.3.6.1.4.1.9.10.13.1.1.1 |
ciscoAtmVplEntryAn entry in the Vpl table.This entry is used to model
a bi-directional Vpl. This table augments the atmVplTable
defined in RFC 1695. However it uses ifIndex and atmVplVpi
as an Index for historical reasons. The entries are
created/deleted as a by-product of creating and deleting
entries in the atmVplTable. CiscoAtmVplEntry .1.3.6.1.4.1.9.10.13.1.1.1.1 |
ciscoAtmVplCastTypeVpl type is either a point to point connection or point
to multipoint root or leaf.rw CastType .1.3.6.1.4.1.9.10.13.1.1.1.1.1 |
ciscoAtmVplSpanTypeVpl span is either a transit one or a terminating one.ro SpanType .1.3.6.1.4.1.9.10.13.1.1.1.1.2 |
ciscoAtmVplConfigTypeVpl type is either a PVC, SVC, Soft PVC or Soft Passive half leg.
The half leg can be set to Passive through user configuration only.rw ConfigType .1.3.6.1.4.1.9.10.13.1.1.1.1.3 |
ciscoAtmVplRxUpcModeUsage Parameter Control opeartion is pass,tag,drop or
local shaping at this connection.rw UpcStatus .1.3.6.1.4.1.9.10.13.1.1.1.1.4 |
ciscoAtmVplConnStateThe connection state of this VPL.rw ConnState .1.3.6.1.4.1.9.10.13.1.1.1.1.5 |
ciscoAtmVplOamLoopbkTxIntervalFrequency of OAM loopback cells generated.rw Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.6 |
ciscoAtmVplOamSegmentLoopbackEnable segment loopback on this virtual path.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.1.1.1.7 |
ciscoAtmVplOamEndLoopbackEnable end to end loopback on this virtual path.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.1.1.1.8 |
ciscoAtmVplOamAisEnableEnable Alarm Indication Signal OAM cell generation
if the interafce goes down on a crossconnect virtual path.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.1.1.1.9 |
ciscoAtmVplOamRdiEnableEnable Remote Defect Indication OAM cell generation
if an Alarm Indication Signal OAM cell is received.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.1.1.1.10 |
ciscoAtmVplInstallTimeThe time stamp derived from sysUpTime when this VPL gets
created. The VPL entries are created/deleted as a by-product
of creating and deleting entries in the atmVplTable defined
in RFC1695.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.1.1.1.11 |
ciscoAtmVplInCellsThe total number of cells received on this
VPL.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.12 |
ciscoAtmVplOutCellsThe total number of cells transmitted on
this VPL.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.13 |
ciscoAtmVplCrossIfIndexFor point to point, this is the cross-connected VPL's
ifIndex of this VPL. For point to multi-point connection,
this will be the root VPL's ifIndex for a leaf VPL entry in
the multicast chain, or it's the 1st leaf for a root VPL entry.
If it's zero, it means it's not cross-connected yet.
Atomically set ciscoAtmVplConnState, ciscoAtmVplCrossIfIndex
and ciscoAtmVplCrossVpi will create or delete a cross
connection to crossed half leg of this ciscoAtmVplCrossIfindex
and ciscoAtmVplCrossVpi for p2p PVP, or add or drop a multicast
connection of this ciscoAtmVplCrossIfindex and
ciscoAtmVplCrossVpi to/from the root on the multicast chain
for p2mp PVP.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.14 |
ciscoAtmVplCrossVpiThis specifies the VPI value of the VPL to which this VPL is
cross-connected. For point to multi-point connection, this is
the root VPL's VPI for the leaf entry. Similarly it is the
1st leaf's VPI value for the root entry.rw Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.15 |
ciscoAtmVplNextLeafIfIndexFor point to point, this is zero i.e. not used.
For point to multi-point connection, this will be the next
leaf VPL's ifIndex on the multicast chain. This will be 0
if this is the root VPL entry. If it's zero for a leaf VPL,
it means this is the last leaf.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.16 |
ciscoAtmVplNextLeafVpiFor point to point, this is zero i.e. not used.
This apply only to point to multi-point connection,
this will be the next leaf VPL's VPI on the multicast chain.ro Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.17 |
ciscoAtmVplRemoteAddrSoft PVP target address if this is the calling side
Soft PVP source address if this is called side.
Atomically set ConnState, RemoteAddr
and RemoteVpi will create or delete a soft PVP.
Atomically set ConnState, RemoteAddr without RemoteVpi will
also create or delete a soft PVP but let target switch
assign the vpi.rw NsapAtmAddr (CISCO-ATM-IF-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.18 |
ciscoAtmVplRemoteVpiSoft PVP target VPI in calling side. 0 in called side.rw Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.19 |
ciscoAtmVplLocationIndicate calling or called side of a soft PVP.
If ciscoAtmVplConfigType is not soft then
ciscoAtmVplLocation value should be ignored.ro Location .1.3.6.1.4.1.9.10.13.1.1.1.1.20 |
ciscoAtmVplSlowRetryIntvSoft PVP slow retry interval time in seconds.rw Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.21 |
ciscoAtmVplNumAttemptsNumber of retries made to install this soft PVP
connection. If ciscoAtmVplConfigType is not soft then
ciscoAtmVplNumAttempts value should be ignored.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.22 |
ciscoAtmVplLastReleaseCauseValue of the Cause field of the Cause
Information Element in the last Release
Signalling message received for this SPVP.
Indicates the reason for the Release.
ciscoAtmVplConfigType is not soft then
ciscoAtmVplLastReleaseCause value should be ignored.ro Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.23 |
ciscoAtmVplLogicalPortDefIndicates whether the VPC at this VPL interface
is an Atm Logical Port interface.rw Enumeration .1.3.6.1.4.1.9.10.13.1.1.1.1.24 |
ciscoAtmVplLogicalPortIndexThe ifTable index of the Atm logical port
interface associated with this VPL. Only valid if
the value of atmVplLogicalPortDef is isLogicalIf,
and the VPL row is active.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.25 |
ciscoAtmVplUpcViolationsThe total number of nonconforming cells detected
by Usage Parameter Control (UPC) for cells received
on this VPL.
On LS1010 systems, this counter is valid only if
equipped with the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.26 |
ciscoAtmVplEpdTpdCellDropsNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.27 |
ciscoAtmVplEpdTpdPacketDropsNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.28 |
ciscoAtmVplEpdTpdPacketsInNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.29 |
ciscoAtmVplClp1DropsNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.30 |
ciscoAtmVplDefaultRxUpcToleranceIf the tolerance (CDVT for CBR, ABR, UBR connections, Maximum
Burst Size for VBR connectons) requested for Usage
Parameter Control is not explicitly specified in VPL creation,
this object contains the default that is used. If tolerance
is explicitly specified in VPL creation, it can be found in
the Traffic Table row specified by atmVplReceiveTrafficDescrIndex,
and the value of this object is -1.ro Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.31 |
ciscoAtmVplDefaultRxUpcVbrCdvtIf the Cell Delay Variation Tolerance (CDVT) requested for
Usage Parameter Control for a VBR connection is not explicitly
specified in VPL creation, this object contains the default
that is used. If CDVT is explicitly specified in VPL creation,
it can be found in the Traffic Table row specified by
atmVplReceiveTrafficDescrIndex, and the value of this object
is -1.ro Integer32 .1.3.6.1.4.1.9.10.13.1.1.1.1.32 |
ciscoAtmVplLsPerVcqWrrWeightConfigure the weighting specified for a VP half-leg
within a service class to make the scheduling decision
among other active VPLs in the service class. This
is for transmit on the VPL on the interface. This
parameter only applies to transit VPs. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.rw INTEGER .1.3.6.1.4.1.9.10.13.1.1.1.1.33 |
ciscoAtmVplLsPerVcqTunnelIsShapedDetermines whether this is to be a -shaped- VP, per
the Lightstream per-VC queueing chipset. If the value
specified is TRUE, the VP is to be a shaped VP Tunnel.
Such a VP cannot be cross-connected. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.1.1.1.34 |
ciscoAtmVplLsPerVcqXmtQueuedCellsNumber of cells received on this VPL and
residing on the per-connection queue. Note that
this value is not valid until the VPL is in an
active cross-connect. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.ro Gauge32 .1.3.6.1.4.1.9.10.13.1.1.1.1.35 |
ciscoAtmVplLsPerVcQThreshGrpThe Threshold Group to which the cell-queue for
cells received by this VP are queued. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.ro LsPerVcqThresholdGroup (CISCO-ATM-RM-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.36 |
ciscoAtmVplInClp0CellsThe total number of cells with the CLP bit clear
received on this VPL. Note that these cells may
subsequently be discarded.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.37 |
ciscoAtmVplInClp1CellsThe total number of cells with the CLP bit set
received on this VPL. Note that these cells may
subsequently be discarded.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.38 |
ciscoAtmVplOutClp0CellsThe total number of cells with the CLP bit clear
transmitted on this VPL.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.39 |
ciscoAtmVplOutClp1CellsThe total number of cells with the CLP bit set
transmitted on this VPL.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.40 |
ciscoAtmVplCellDropsThe total number of cells received on this
VPL, but discarded.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.41 |
ciscoAtmVplClp0VcqFullCellDropsThe total number of cells received on this
VPL with the CLP bit clear, discarded because
the per-VC queue limit is exceeded.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.43 |
ciscoAtmVplVcqClpThreshCellDropsThe total number of cells received on this
VPL, discarded because the discard threshold
(as opposed to the queue-limit) is exceeded
on the per-VC queue, and the CLP bit is set.
This counter is valid only:
- if the VPL is not a Logical Interface (tunnel).
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.44 |
ciscoAtmVplLsPerVcqTunnelIsHierarchicalDetermines whether this is to be a -Hierarchical- VP, per
the Lightstream per-VC queueing chipset. If the value
specified is TRUE, the VP is to be a Hierarchical VP Tunnel.
Such a VP cannot be cross-connected. This object
is defined on a LS1010 only when the switch is equipped with
the Lightstream per-VC queueing chipset.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.1.1.1.45 |
ciscoAtmVplRxNegTraffDescrIndexIdentifies the entry in the atmTrafficDescrParamTable which
contains negotiated traffic parameters applied to the receive
direction of this VPL.
This object is not instantiated if this VPL is not the calling
side of a soft VP, or if there was no traffic negotiation.ro AtmTrafficDescrParamIndex .1.3.6.1.4.1.9.10.13.1.1.1.1.46 |
ciscoAtmVplTxNegTraffDescrIndexIdentifies the entry in the atmTrafficDescrParamTable which
contains negotiated traffic parameters applied to the transmit
direction of this VPL.
This object is not instantiated if this VPL is not the calling
side of a soft VP, or if there was no traffic negotiation.ro AtmTrafficDescrParamIndex .1.3.6.1.4.1.9.10.13.1.1.1.1.47 |
ciscoAtmVplSwFabOutCellsThe total number of cells transmitted on
this VPL by the Switch Fabric. This object is not
instantiated on systems that do not have support for
collecting such statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.48 |
ciscoAtmVplSwFabOutClp0CellsThe total number of cells with the CLP bit clear
transmitted on this VPL by the Switch Fabric. This object
is not instantiated for a VPL that is a logical interface
(VP Tunnel). This object is not instantiated on systems
that do not have support for collecting such statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.49 |
ciscoAtmVplSwFabOutClp1CellsThe total number of cells with the CLP bit set transmitted
on this VPL by the Switch Fabric. This object is not
instantiated for a VPL that is a logical interface
(VP Tunnel). This object is not instantiated on systems
that do not have support for collecting such statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.1.1.1.50 |
ciscoAtmVplConnNameA human readable string that identifies this connection.
This object will return a zero-length string if value is
not set.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.10.13.1.1.1.1.51 |
ciscoAtmVplConnTypeThis object represent the PVP Type for this connection.
- local connection within the node
- endToEnd across several nodes
This object serves as an information object for a
management system and has no functional meaning to
the switch.rw Enumeration .1.3.6.1.4.1.9.10.13.1.1.1.1.52 |
ciscoAtmVcl OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.2 |
ciscoAtmVclTableThe Virtual Channel Link extension Table. SEQUENCE OF CiscoAtmVclEntry .1.3.6.1.4.1.9.10.13.1.2.1 |
ciscoAtmVclEntryAn entry in the Vcl table.This entry is used to model
a bi-directional Vcl. This table augments the atmVclTable
defined in RFC 1695. However it uses ifIndex, atmVclVpi
and atmVclVci as an Index for historical reasons.
The entries are created/deleted as a by-product of
creating and deleting entries in the atmVclTable. CiscoAtmVclEntry .1.3.6.1.4.1.9.10.13.1.2.1.1 |
ciscoAtmVclCastTypeVcl type is either a point to point connection or point
to multipoint root or leaf.rw CastType .1.3.6.1.4.1.9.10.13.1.2.1.1.1 |
ciscoAtmVclSpanTypeVcl span is either a transit one or a terminating one.ro SpanType .1.3.6.1.4.1.9.10.13.1.2.1.1.2 |
ciscoAtmVclConfigTypeVcl type is either a PVC, SVC, Soft PVC or Soft Passive half leg.
The half leg can be set to Passive through user configuration only.rw ConfigType .1.3.6.1.4.1.9.10.13.1.2.1.1.3 |
ciscoAtmVclRxUpcModeUsage Parameter Control opeartion is pass,tag,drop or
local shaping at this connection.rw UpcStatus .1.3.6.1.4.1.9.10.13.1.2.1.1.4 |
ciscoAtmVclEpdEnableEarly Packet Discard option used for this VCL.
The use is as follows:
enable(1)
Packet-discard is enabled.
disable(2)
Packet-discard is disabled.
useTrafficDescr(3)
Packet-discard in the receive direction is as specified by
the atmTrafficFrameDiscard value in row corresponding to
atmVclReceiveTrafficDescrIndex. For VCLs of type
spvcInitiator, the packet-discard in the reverse direction
is as specified by the atmTrafficFrameDiscard value in row
corresponding to atmVclTransmitTrafficDescrIndex.rw Enumeration .1.3.6.1.4.1.9.10.13.1.2.1.1.5 |
ciscoAtmVclConnStateThe connection state of this VCL.rw ConnState .1.3.6.1.4.1.9.10.13.1.2.1.1.6 |
ciscoAtmVclOamLoopbkTxIntervalFrequency of OAM loopback cell are generated on this
virtual channel.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.7 |
ciscoAtmVclOamSegmentLoopbackEnable segment loopback on this virtual channel.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.2.1.1.8 |
ciscoAtmVclOamEndLoopbackEnable end to end loopback on this virtual channel.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.2.1.1.9 |
ciscoAtmVclOamAisEnableEnable Alarm Indication Signal OAM cell generation
if the interafce goes down on a crossconnect virtual
channel.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.2.1.1.10 |
ciscoAtmVclOamRdiEnableEnable Remote Defect Indication OAM cell generation
if an Alarm Indication Signal OAM cell is received.rw EnableStatus .1.3.6.1.4.1.9.10.13.1.2.1.1.11 |
ciscoAtmVclInstallTimeThe time stamp derived from sysUpTime when this VCL gets
created. The VCL entries are created/deleted as a by-product
of creating and deleting entries in the atmVclTable defined
in RFC1695.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.2.1.1.12 |
ciscoAtmVclInCellsThe total number of cells received on
this VCL.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.13 |
ciscoAtmVclOutCellsThe total number of cells transmitted on
this VCL.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.14 |
ciscoAtmVclCrossIfIndexFor point to point, this is the cross-connected VCL's
ifIndex of this VCL. For point to multi-point connection,
this will be the root VCL's ifIndex for a leaf VCL entry in
the multicast chain, or it's the 1st leaf VCL for a root
VCL entry. If it's zero, it means it's not cross-connected
yet. Atomically set ciscoAtmVclConnState,
ciscoAtmVclCrossIfindex, ciscoAtmVclCrossVpi and
ciscoAtmVclCrossVci will create or delete a cross
connection to crossed half leg of this
ciscoAtmVclCrossIfindex, ciscoAtmVclCrossVpi and
ciscoAtmVclCrossVci for p2p PVC, or add or drop a multicast
connection to/from the root of this ciscoAtmVclCrossIfindex,
ciscoAtmVclCrossVpi and ciscoAtmVclCrossVci on the multicast
chain for p2mp PVC.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.2.1.1.15 |
ciscoAtmVclCrossVpiThis specifies the VPI value of the VCL to which this
VCL is cross-connected. For point to multi-point
connection, this is the root VCL's VPI for the leaf entry.
Similarly it is the 1st leaf's VPI value for the root entry.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.16 |
ciscoAtmVclCrossVciThis specifies the VCI value of the VCL to which this
VCL is cross-connected. For point to multi-point
connection, this is the root VCL's VCI for the leaf
entry. Similarly it is the 1st leaf's VCI value for
the root entry.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.17 |
ciscoAtmVclNextLeafIfIndexFor point to point, this is zero i.e. not used.
For point to multi-point connection, this will be
the next leaf VCL's ifIndex on the multicast chain.
This will be 0 if this is the root VCL entry.
If it's zero for a leaf VCL, it means this is the
last leaf.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.2.1.1.18 |
ciscoAtmVclNextLeafVpiFor point to point, this is zero i.e. not used.
This apply only to point to multi-point connection,
this will be the next leaf VCL's VPI on the multicast
chain.ro Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.19 |
ciscoAtmVclNextLeafVciFor point to point, this is zero i.e. not used.
This apply only to point to multi-point connection,
this will be the next leaf VCL's VCI on the multicast
chain.ro Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.20 |
ciscoAtmVclAalEncapFlagEncapsulation type for terminating VC.rw Enumeration .1.3.6.1.4.1.9.10.13.1.2.1.1.21 |
ciscoAtmVclAalEncapProtocolProtocol for terminating VC if EncapFlag is aal5Mux.rw Enumeration .1.3.6.1.4.1.9.10.13.1.2.1.1.22 |
ciscoAtmVclAalUserVcTypeFollowing is the list of user virtual circuit types in
case aal5Lane encapusation on this virtual channel.
boxConfigure
Configure VCC
busForward
busSend
clientConfigure
Direct VCC
clientData
clientDirect
Direct VCC
clientDistribute
Distribute VCC
clientForward
Forward VCC
clientSend
Send VCC
configure
serverConfigure
serverDirect
Direct VCC.rw Enumeration .1.3.6.1.4.1.9.10.13.1.2.1.1.23 |
ciscoAtmVclAtmInArpIntervalTime interval in minutes to send InArp on a PVC for
IP over ATM. 0 will disable the InArp for this pvc.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.24 |
ciscoAtmVclRemoteAddrSoft PVC target address if this is the calling side
Soft PVC source address if this is called side.
Atomically set ConnState, RemoteAddr, RemoteVpi
and RemoteVci will create or delete a soft PVC.
Atomically set ConnState, RemoteAddr without RemoteVpi,
Remote Vci will also create or delete a soft PVC but let
target switch assign the vpi and vci.rw NsapAtmAddr (CISCO-ATM-IF-MIB) .1.3.6.1.4.1.9.10.13.1.2.1.1.25 |
ciscoAtmVclRemoteVpiSoft PVC target VPI in calling side. 0 in called side.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.26 |
ciscoAtmVclRemoteVciSoft PVC target VCI in calling side. 0 in called side.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.27 |
ciscoAtmVclLocationIndicate calling or called side of a soft PVC.
If ciscoAtmVclConfigType is not soft then
ciscoAtmVclLocation value should be ignored.ro Location .1.3.6.1.4.1.9.10.13.1.2.1.1.28 |
ciscoAtmVclSlowRetryIntvSoft PVC slow retry interval in seconds.rw Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.29 |
ciscoAtmVclNumAttemptsNumber of retries made to install this soft PVC
connection. If ciscoAtmVclConfigType is not soft then
ciscoAtmVclNumAttempts value should be ignored.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.30 |
ciscoAtmVclLastReleaseCauseValue of the Cause field of the Cause
Information Element in the last Release
Signalling message received for this SPVC.
Indicates the reason for the Release.
ciscoAtmVclConfigType is not soft then
ciscoAtmVclLastReleaseCause value should be
ignored.ro Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.31 |
ciscoAtmVclUpcViolationsThe total number of nonconforming cells detected
by Usage Parameter Control (UPC) for cells received
on this VCL.
On LS1010 systems, this counter is valid only on those
equipped with the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.32 |
ciscoAtmVclEpdTpdCellDropsNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.33 |
ciscoAtmVclEpdTpdPacketDropsThe total number of EPD/TPD packet drops of
packets received on this VCL.
This counter is valid only:
- if EPD is enabled on this VCL.
- on LS1010 systems, only those equipped with
the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.34 |
ciscoAtmVclEpdTpdPacketsInThe total number of packets received in their
entirety on this VPL.
This counter is valid only:
- if EPD is enabled on this VCL.
- on LS1010 systems, only those equipped with
the Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.35 |
ciscoAtmVclClp1DropsNever implemented.roobsolete Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.37 |
ciscoAtmVclDefaultRxUpcToleranceIf the tolerance (CDVT for CBR, ABR, UBR connections, Maximum
Burst Size for VBR connectons) requested for Usage
Parameter Control is not explicitly specified in VCL creation,
this object contains the default that is used.If tolerance
is explicitly specified in VCL creation, it can be found in
the Traffic Table row specified by atmVclReceiveTrafficDescrIndex,
and the value of this object is -1.ro Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.38 |
ciscoAtmVclDefaultRxUpcVbrCdvtIf the Cell Delay Variation Tolerance (CDVT) requested for
Usage Parameter Control for a VBR connection is not explicitly
specified in VCL creation, this object contains the default
that is used. If CDVT is explicitly specified in VCL creation,
it can be found in the Traffic Table row specified by
atmVclReceiveTrafficDescrIndex, and the value of this object
is -1.ro Integer32 .1.3.6.1.4.1.9.10.13.1.2.1.1.39 |
ciscoAtmVclLsPerVcqWrrWeightConfigure the weighting specified for a VC half-leg
within a service class to make the scheduling decision
among other active VCLs in the service class. This
is for transmit on the VCL on the interface. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.rw INTEGER .1.3.6.1.4.1.9.10.13.1.2.1.1.40 |
ciscoAtmVclLsPerVcqXmtQueuedCellsNumber of cells received on this VCL and
residing on the per-connection queue. Note that
this value is not valid until the VCL is in an
active cross-connect. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.ro Gauge32 .1.3.6.1.4.1.9.10.13.1.2.1.1.41 |
ciscoAtmVclLsPerVcQThreshGrpThe Threshold Group to which the cell-queue
for cells received by this VC are queued.
Note that this value is not valid until the
VCL is in an active cross-connect. This object
is defined only when the switch is equipped with
the Lightstream per-VC queueing chipset.ro LsPerVcqThresholdGroup (CISCO-ATM-RM-MIB) .1.3.6.1.4.1.9.10.13.1.2.1.1.42 |
ciscoAtmVclInClp0CellsThe total number of cells with the CLP bit clear
received on this VCL. Note that these cells may
subsequently be discarded.
This counter is valid only:
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.43 |
ciscoAtmVclInClp1CellsThe total number of cells with the CLP bit set
received on this VCL. Note that these cells may
subsequently be discarded.
This counter is valid only:
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.44 |
ciscoAtmVclOutClp0CellsThe total number of cells with the CLP bit clear
transmitted on this VCL.
This counter is valid only:
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.45 |
ciscoAtmVclOutClp1CellsThe total number of cells with the CLP bit set
transmitted on this VCL.
This counter is valid only:
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.46 |
ciscoAtmVclCellDropsThe total number of cells received on this
VCL, but discarded.
This counter is valid only:
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.47 |
ciscoAtmVclClp0VcqFullCellDropsThe total number of cells received on this
VCL with the CLP bit clear, discarded because
the per-VC queue limit is exceeded.
This counter is valid only:
- if EPD is disabled on the VCL.
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.48 |
ciscoAtmVclVcqClpThreshCellDropsThe total number of cells received on this
VCL, discarded because the discard threshold
(as opposed to the queue-limit) is exceeded
on the per-VC queue, and the CLP bit is set.
This counter is valid only:
- if EPD is disabled on the VCL.
- on LS1010 systems, only those equipped with
Feature Card - Per Flow Queueing.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.49 |
ciscoAtmVclRxNegTraffDescrIndexIdentifies the entry in the atmTrafficDescrParamTable which
contains negotiated traffic parameters applied to the receive
direction of this VCL.
This object is not instantiated if this VCL is not the calling
side of a soft VC, or if there was no traffic negotiation.ro AtmTrafficDescrParamIndex .1.3.6.1.4.1.9.10.13.1.2.1.1.50 |
ciscoAtmVclTxNegTraffDescrIndexIdentifies the entry in the atmTrafficDescrParamTable which
contains negotiated traffic parameters applied to the transmit
direction of this VCL.
This object is not instantiated if this VCL is not the calling
side of a soft VC, or if there was no traffic negotiation.ro AtmTrafficDescrParamIndex .1.3.6.1.4.1.9.10.13.1.2.1.1.51 |
ciscoAtmVclSwFabOutCellsThe total number of cells transmitted on
this VCL by the Switch Fabric. This object is not
instantiated on systems that do not have support for
collecting such statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.52 |
ciscoAtmVclSwFabOutClp0CellsThe total number of cells with the CLP bit clear
transmitted on this VCL by the Switch Fabric.
This object is not instantiated on systems
that do not have support for collecting such
statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.53 |
ciscoAtmVclSwFabOutClp1CellsThe total number of cells with the CLP bit set
transmitted on this VCL by the Switch Fabric.
This object is not instantiated on systems that
do not have support for collecting such statistics.ro Counter32 .1.3.6.1.4.1.9.10.13.1.2.1.1.54 |
ciscoAtmVclConnNameA human readable string that identifies this connection.
This object will return a zero-length string if value is
not set.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.10.13.1.2.1.1.55 |
ciscoAtmVclConnTypeThis object represent the PVC Type for this connection.
- local connection within the node
- endToEnd across several nodes.
This object serves as an information object for a
management system and has no functional meaning to
the switch.rw Enumeration .1.3.6.1.4.1.9.10.13.1.2.1.1.56 |
ciscoAtmSvp OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.3 |
ciscoAtmSvpAddrTableSwitched virtual path link address table. SEQUENCE OF CiscoAtmSvpAddrEntry .1.3.6.1.4.1.9.10.13.1.3.1 |
ciscoAtmSvpAddrEntryAn entry in the Switched Vrtual Path address table. CiscoAtmSvpAddrEntry .1.3.6.1.4.1.9.10.13.1.3.1.1 |
ciscoAtmSvpAddrIt depends on the direction.This could be p2pCallingSide
address on a called side VPL, or p2pCalledSide address on a
calling side VPL or p2mpRoot address on a p2mp leaf side
VPL or p2mpLeaf address on a p2mp root side VPL. OCTET STRING .1.3.6.1.4.1.9.10.13.1.3.1.1.1 |
ciscoAtmSvpVpiThis SVP's VPI value on this interface. INTEGER .1.3.6.1.4.1.9.10.13.1.3.1.1.2 |
ciscoAtmSvpDirectionIndicate whether this VPL is calling side, called side,
root or leaf for this address.ro Direction .1.3.6.1.4.1.9.10.13.1.3.1.1.3 |
ciscoAtmSvc OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.4 |
ciscoAtmSvcAddrTableSwitched virtual channel link address table. SEQUENCE OF CiscoAtmSvcAddrEntry .1.3.6.1.4.1.9.10.13.1.4.1 |
ciscoAtmSvcAddrEntryAn entry in the SVC address table. CiscoAtmSvcAddrEntry .1.3.6.1.4.1.9.10.13.1.4.1.1 |
ciscoAtmSvcAddrIt depends on the direction.This could be p2pCallingSide
address on a called side VCL, or p2pCalledSide address on a
calling side VCL or p2mpRoot address on a p2mp leaf side VCL
or p2mpLeaf address on a p2mp root side VCL. OCTET STRING .1.3.6.1.4.1.9.10.13.1.4.1.1.1 |
ciscoAtmSvcVpiThis SVC's VPI value on this interface. Integer32 .1.3.6.1.4.1.9.10.13.1.4.1.1.2 |
ciscoAtmSvcVciThis SVC's VCI value on this interface. Integer32 .1.3.6.1.4.1.9.10.13.1.4.1.1.3 |
ciscoAtmSvcDirectionIndicate whether this VCL is calling side, called side,
root or leaf for this address.ro Direction .1.3.6.1.4.1.9.10.13.1.4.1.1.4 |
ciscoAtmSvcFrameDiscardUsesAal5IeDetermines mechanism to use on interfaces
to specify frame discard.
Specifying a value of true causes the presence
of the AAL5 IE to influence whether frame discard
is used on an SVC. If AAL5 IE is present in a received
SETUP, frame discard is used.
Specifying a value of false results in no influence on
presence of the frame discard by the AAL5 IE.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.4.2 |
ciscoAtmSnoopVc OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.5 |
ciscoAtmSnoopVcTableSnooping VC Table. SEQUENCE OF CiscoAtmSnoopVcEntry .1.3.6.1.4.1.9.10.13.1.5.1 |
ciscoAtmSnoopVcEntryAn entry in the Snoop VC table. This entry models a VC snooping
connection. The ifIndex indicates the snooping interface, the
atmVclVpi and atmVclVci specifies the VPI and VCI value of the
snooping connection. To create or destroy a snooping connection
at an ATM interface, the following procedures are used:
Configure VC Snooping
A snooping connection is configured in one step by a set-request
with all necessary snoop parameter values and set-request to the
object ciscoAtmSnoopVcRowStatus to createAndGo(4). This may fail
for the following reasons:
- The selected snooping VPI/VCI values are unavailable,
- The selected snooping VPI/VCI values are in use.
- The selected snooping interface is CPU interface.
- The selected snooped connection doesn't exist.
- There is no traffic in the selected snoop direction.
- Resource failure during configuration of snooping connection.
De-Configure VC Snooping
A snooping connection is deconfigured by a set-request to the
object ciscoAtmSnoopVcRowStatus to destroy(6), and the agent
releases all associated resources. CiscoAtmSnoopVcEntry .1.3.6.1.4.1.9.10.13.1.5.1.1 |
ciscoAtmSnoopVcSnoopedIfIndexThis specifies the ifIndex of the snooped interface.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.5.1.1.1 |
ciscoAtmSnoopVcSnoopedVpiThis specifies the VPI value of the snooped connection endpoint.rw Integer32 .1.3.6.1.4.1.9.10.13.1.5.1.1.2 |
ciscoAtmSnoopVcSnoopedVciThis specifies the VCI value of the snooped connection endpoint.rw Integer32 .1.3.6.1.4.1.9.10.13.1.5.1.1.3 |
ciscoAtmSnoopVcDirThis specifies the traffic direction at the snooped connection
endpoint.rw SnoopDirType .1.3.6.1.4.1.9.10.13.1.5.1.1.4 |
ciscoAtmSnoopVcStateThe connection state of this Snooping connetion.ro ConnState .1.3.6.1.4.1.9.10.13.1.5.1.1.5 |
ciscoAtmSnoopVcRowStatusThis object is used to create a new row or delete an existing row
in this table. This gives the way to configure one-shot per-vc
snooping connectionrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.5.1.1.6 |
ciscoAtmSnoopVp OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.1.6 |
ciscoAtmSnoopVpTableSnooping VP Table. SEQUENCE OF CiscoAtmSnoopVpEntry .1.3.6.1.4.1.9.10.13.1.6.1 |
ciscoAtmSnoopVpEntryAn entry in the Snoop VP table. This entry models a VP snooping
connection. The ifIndex indicates the snooping interface, the
atmVclVpi specifies the VPI value of the snooping connection. To
create or destroy a snooping connection at an ATM interface, the
following procedures are used:
Configure VP Snooping
A snooping connection is configured in one step by a set-request
with all necessary snoop parameter values and set-request to the
object ciscoAtmSnoopVpRowStatus to createAndGo(4). This may fail
for the following reasons:
- The selected snooping VPI values are unavailable,
- The selected snooping VPI values are in use.
- The selected snooping interface is CPU interface.
- The selected snooped connection doesn't exist.
- There is no traffic in the selected snoop direction.
- Resource failure during configuration of snooping connection.
De-Configure VP Snooping
A snooping connection is deconfigured by a set-request to the
object ciscoAtmSnoopVpRowStatus to destroy(6), and the agent
releases all associated resources. CiscoAtmSnoopVpEntry .1.3.6.1.4.1.9.10.13.1.6.1.1 |
ciscoAtmSnoopVpSnoopedIfIndexThis specifies the ifIndex of the snooped interface.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.10.13.1.6.1.1.1 |
ciscoAtmSnoopVpSnoopedVpiThis specifies the VPI value of the snooped connection endpoint.rw Integer32 .1.3.6.1.4.1.9.10.13.1.6.1.1.2 |
ciscoAtmSnoopVpDirThis specifies the traffic direction at the snooped connection
endpoint.rw SnoopDirType .1.3.6.1.4.1.9.10.13.1.6.1.1.3 |
ciscoAtmSnoopVpStateThe connection state of this Snooping connection .ro ConnState .1.3.6.1.4.1.9.10.13.1.6.1.1.4 |
ciscoAtmSnoopVpRowStatusThis object is used to create a new row or delete an existing row
in this table. This gives the way to configure one-shot per-vp
snooping connectionrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.10.13.1.6.1.1.5 |
ciscoAtmConnMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.3 |
ciscoAtmConnMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.3.1 |
ciscoAtmConnMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.10.13.3.2 |