CISCO-ATM-PVC-MIB: View SNMP OID List / Download MIB
VENDOR: CISCO
| Home | MIB: CISCO-ATM-PVC-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| 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 | no-access |
A table of all the PVCs configured on an ATM uplink card. |
|
| 1.3.6.1.4.1.9.9.94.1.1.1.1 | no-access |
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. |
||
| capvcPort | 1.3.6.1.4.1.9.9.94.1.1.1.1.1 | unsigned32 | no-access |
The port number in the ATM module on which this PVC is being configured. |
| capvcVPI | 1.3.6.1.4.1.9.9.94.1.1.1.1.2 | unsigned32 | no-access |
The Virtual Path Identifier for the PVC. |
| capvcVCI | 1.3.6.1.4.1.9.9.94.1.1.1.1.3 | unsigned32 | no-access |
The Virtual Channel Identifier for the PVC. |
| 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. |
| capvcType | 1.3.6.1.4.1.9.9.94.1.1.1.1.5 | integer | read-only |
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. Enumeration: 'aal5snap': 1, 'ilmi': 2, 'qsaal': 3. |
| capvcPCR | 1.3.6.1.4.1.9.9.94.1.1.1.1.6 | unsigned32 | read-only |
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. |
| capvcOAM | 1.3.6.1.4.1.9.9.94.1.1.1.1.7 | truthvalue | read-only |
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. |
| capvcFrequency | 1.3.6.1.4.1.9.9.94.1.1.1.1.8 | unsigned32 | read-only |
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. |
| capvcVlanId | 1.3.6.1.4.1.9.9.94.1.1.1.1.9 | unsigned32 | read-only |
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. |
| capvcRowStatus | 1.3.6.1.4.1.9.9.94.1.1.1.1.10 | rowstatus | read-only |
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. |
||