CISCO-ATM-PVC-MIB

All MIBs › CISCO-ATM-PVC-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2002-04-11

Category: ATM

Description: Manages ATM Permanent Virtual Circuits (PVCs) configuration and statistics on Cisco devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-ATM-PVC-MIB?

CISCO-ATM-PVC-MIB is a Cisco proprietary MIB for configuring and monitoring ATM Permanent Virtual Circuits (PVCs) on Cisco ATM uplink cards, such as those found in Catalyst 5000 series switches, including binding a PVC to a VLAN for bridged PDU transport per RFC 1483. The data it exposes is primarily configuration-oriented: per-PVC port, VPI/VCI/VCD identifiers, PVC type, peak cell rate (PCR), OAM settings, polling frequency, and VLAN binding, alongside row-status for circuit provisioning. As a software/configuration-status MIB it lets an administrator confirm a PVC is correctly provisioned, active, and correctly bound to its target VLAN rather than reporting hardware faults directly. It builds on standard ATM MIB concepts as a Cisco-specific complement, implying reliance on the broader IETF ATM MIB framework for underlying ATM interface objects. It is typically deployed on legacy Cisco Catalyst 5000 ATM uplink modules used to bridge VLAN traffic over ATM permanent virtual circuits. Engineers can download the CISCO-ATM-PVC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ATM-PVC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco Catalyst 5000 series switch with ATM uplink card

Monitoring Examples

An administrator walks capvcTable / capvcEntry to enumerate configured PVCs, checking capvcPort, capvcVPI, and capvcVCI to identify a specific circuit, and capvcRowStatus to confirm it is active rather than stuck in notInService. Reading capvcVlanId alongside capvcPCR and capvcOAM reveals whether a PVC is correctly bound to the expected VLAN and whether its configured peak cell rate matches provisioning intent. A PVC entry with an unexpected capvcRowStatus or a VLAN binding mismatch would indicate a misconfigured bridge path causing traffic to be dropped or delivered to the wrong VLAN.

What Can Be Monitored

PVC provisioning status
VPI/VCI identifiers
peak cell rate
OAM cell settings
VLAN binding of a PVC
PVC row status

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoAtmPvcMIB	1.3.6.1.4.1.9.9.94			PVC's (Permanent Virtual Channel) can carry bridged PDUs (BPDUs) using the encapsulation method detailed in RFC1483. This is an alternative to using LAN Emulation to transfer BPDUs. This MIB allows users to configure a PVC on an ATM uplink card of a Catalyst 5000 device, and then bind that PVC to a Virtual LAN (VLAN).
ciscoAtmPvcMIBObjects	1.3.6.1.4.1.9.9.94.1
ciscoAtmPvcCreateBindGroup	1.3.6.1.4.1.9.9.94.1.1
capvcTable	1.3.6.1.4.1.9.9.94.1.1.1		not-accessible	A table of all the PVCs configured on an ATM uplink card.
capvcEntry	1.3.6.1.4.1.9.9.94.1.1.1.1		not-accessible	An entry in the PVC table containing information about a single PVC that has been configured. To create a PVC at an ATM interface and bind it to a VLAN, either of the following procedures are used : Multi step process (1) The management application creates a PVC entry in the capvcTable by setting the capvcRowStatus to createAndWait(5). This may fail for the following reasons: - The selected vpi/vci is already being used. - The selected port is not available. Otherwise, the agent creates a row and reserves the vpi/vci on that port. (2) The manager then sets the values for the capvcVlanId, capvcType and optionally, the capvcPCR, capvcOAM and capvcFrequency. (3) The manager activates the PVC by setting the capvcRowStatus to active(1). One-Shot PVC establishment (1) A PVC may also be established in one step by a set-request with all necessary PVC parameter values and the capvcRowStatus set to createAndGo(4). In contrast to the multi step process which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot PVC establishment performs the setup on one operation but does not have the advantage of step-wise error checking. PVC Retirement A PVC is released by setting the capvcRowStatus to destroy(6), and the agent may release all associated resources.
U32 capvcPort	1.3.6.1.4.1.9.9.94.1.1.1.1.1	Unsigned32	not-accessible	The port number in the ATM module on which this PVC is being configured.
U32 capvcVPI	1.3.6.1.4.1.9.9.94.1.1.1.1.2	Unsigned32	not-accessible	The Virtual Path Identifier for the PVC.
U32 capvcVCI	1.3.6.1.4.1.9.9.94.1.1.1.1.3	Unsigned32	not-accessible	The Virtual Channel Identifier for the PVC.
U32 capvcVCD	1.3.6.1.4.1.9.9.94.1.1.1.1.4	Unsigned32	read-only	This is the Virtual Channel Descriptor, a value which uniquely identifies the PVC. This is a read-only variable and is not set by the user. When the PVC is created successfully, it is assigned a unique VCD number by the system.
INT capvcType	1.3.6.1.4.1.9.9.94.1.1.1.1.5	INTEGER	read-create	The type of traffic that will flow through the PVC. The user can configure the PVC as: (1) aal5snap PVC which carries network interconnect traffic over ATM AAL5 (RFC1483). (2) ilmi PVC which carries Interim Link Management Interface protocol traffic. (3) qsaal PVC which carries ATM UNI 3.x signalling traffic.
U32 capvcPCR	1.3.6.1.4.1.9.9.94.1.1.1.1.6	Unsigned32	read-create	The Peak Cell Rate for the PVC. This value denotes the bandwidth allocated for this PVC. The default value for this field is the maximum speed of the interface. This is 155000 Kbps for an OC3 Module and 45000 Kbps for a DS3 Module.
T/F capvcOAM	1.3.6.1.4.1.9.9.94.1.1.1.1.7	TruthValue	read-create	A boolean that indicates if a F5 OAM loopback cell will be sent on this PVC or not. The default value for this field is false.
U32 capvcFrequency	1.3.6.1.4.1.9.9.94.1.1.1.1.8	Unsigned32	read-create	Indicates how often will a F5 OAM loopback cell be transmitted. If the value of capvcOAM is true, then the default value for this variable is 10 seconds. If the value of capvcOAM is false, then this variable is ignored.
U32 capvcVlanId	1.3.6.1.4.1.9.9.94.1.1.1.1.9	Unsigned32	read-create	The VLAN number of the VLAN that the PVC is bound to. Binding a PVC say with VCD number x, to a VLAN with a VlanId y, causes the traffic on VLAN y to pass through PVC x. Also a PVC that is bound to a VLAN can be unbound by the user. After the unbind operation the VLAN traffic stops flowing through the PVC. If the user changes the value of this variable then the PVC is unbound from the original VLAN and bound to the new VLAN.
ROW capvcRowStatus	1.3.6.1.4.1.9.9.94.1.1.1.1.10	RowStatus	read-create	This object is used to create, delete or modify a row in this table. To create a new PVC, this object is initially set to 'createAndWait' or 'createAndGo'. This object must not be set to 'active' unless the following columnar objects exist in this row: capvcType and capvcVlanId. To delete a row, this object is set to 'destroy'(6).
ciscoAtmPvcMIBConformance	1.3.6.1.4.1.9.9.94.3
ciscoAtmPvcMIBCompliances	1.3.6.1.4.1.9.9.94.3.1
ciscoAtmPvcMIBCompliance	1.3.6.1.4.1.9.9.94.3.1.1			The compliance statement for entities which implement the Cisco Atm PVC MIB. This MIB is mandatory for all ATM uplink cards on the Catalyst 5000 device.
ciscoAtmPvcMIBGroups	1.3.6.1.4.1.9.9.94.3.2
ciscoAtmPvcMIBGroup	1.3.6.1.4.1.9.9.94.3.2.1			A collection of objects providing ATM PVC configuration and VLAN binding.

RFC description

Manages ATM Permanent Virtual Channel (PVC) creation and binding to VLANs on Cisco Catalyst switches.

Start monitoring Cisco Catalyst switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-ATM-PVC-MIB

What Is CISCO-ATM-PVC-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description