All MIBs › CISCO-VISM-ATM-TRUNK-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2004-04-14
Category: ATM, Cisco Devices, Telephony and VoIP
Description: Manages ATM trunk connections carrying TDM voice traffic on Cisco VISM Voice Interworking Service Module for MGX.
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-VISM-ATM-TRUNK-MIB?
CISCO-VISM-ATM-TRUNK-MIB is used with the Cisco Voice Interworking Service Module (VISM) on MGX voice/ATM gateway platforms, exposing the ATM bearer trunk and channel-identifier (CID) connections that carry TDM voice traffic over ATM. It provides per-connection configuration (endpoint number, CID, logical channel number) and real-time performance counters for packets and octets sent/received. Its principal monitoring value is voice-quality assurance: it surfaces bearerLostPkts, bearerJitter, and bearerLatency per connection, letting operators detect degraded call quality caused by packet loss or excessive delay on a specific ATM voice trunk, functioning much like a hardware/link health indicator for that bearer path. It is a Cisco-specific extension built on top of standard ATM connection concepts and is scoped to VISM hardware rather than a general IETF ATM MIB. It is deployed in legacy Cisco MGX-based voice gateway networks carrying TDM voice over ATM backbone links, and engineers supporting these platforms can download the CISCO-VISM-ATM-TRUNK-MIB file to load into their MIB browser for reference.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-VISM-ATM-TRUNK-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 VISM (Voice Interworking Service Module)
- Cisco MGX ATM voice gateway platforms
Monitoring Examples
An operator would poll bearerConnTable entries keyed by bearerEndptNum and bearerCid to check bearerJitter and bearerLatency for a specific voice trunk, flagging calls at risk of audible quality problems. A rising bearerLostPkts counter alongside falling bearerRcvdPkts on the same bearerConnEntry would indicate the ATM bearer path is dropping voice cells, while bearerSentOctets/bearerRcvdOctets give the byte-level throughput baseline for that connection.
What Can Be Monitored
- packet/octet counts per bearer connection
- packet loss
- jitter
- latency
- channel identifier (CID) and logical channel status
This MIB depends on
Related MIBs
Imported Objects
From BASIS-MIB
| vismChanGrp | OBJECT-IDENTITY |
| voice | OBJECT-IDENTITY |
From CISCOWAN-SMI
| ciscoWan | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| C32 bearerAal2ConnAISCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.13 | Counter32 | read-only | This object contains the number of external Conn AIS AAL2 Type2 packets received. External Conn AIS - is transmitted in the downstream direction from the AAL Type 2 connecting point that first detects a defect affecting the AAL Type 2 connection; this includes defects indicated by lower layers. |
| C32 bearerAal2ConnRDICnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.14 | Counter32 | read-only | This object contains the number of external Conn RDI(Remote Defect Indication) AAL2 Type2 packets received. External Conn RDI - is a signal transmitted upstream by an AAL Type 2 endpoint that is in an alarm state as the result of having received an AAL Type2 connection AIS or having detected a defect that affects the AAL Type2 connection. |
| C32 bearerAal2ExtAISCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.11 | Counter32 | read-only | This object contains the number of external AIS (Alarm Indication Signal) AAL2 Type3 packets received. External AIS - is associated with a maintenance alarm detected on a defective maintenance span, that is transmitted in the direction of the defect as a substitute for normal signal. The purpose is to show the downstream entities that a defect has been identified and to prevent other maintenance alrams consequent to this first defect. External AIS bit stream is represented by an all 1's signal. |
| C32 bearerAal2ExtRAICnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.12 | Counter32 | read-only | This object contains the number of external RAI (Remote Alarm Indication) AAL2 Type3 packets received. External RAI - is a signal that is transmitted upstream from an entity that has detected defects persisting long enough to constitute a received signal failure. Its purpose is to report in the backward direction that there is an interruption of service in the forward direction. |
| I32 bearerCid | 1.3.6.1.4.1.351.110.5.5.9.1.1.2 | Integer32 | read-only | This attribute defines the CID associated with this bearer connection. This refers to the same value as vismAal2CidNum in the vismAal2CidCnfTable. |
| INT bearerCntClrButton | 1.3.6.1.4.1.351.110.5.5.9.1.1.15 | INTEGER | read-write | This object is used to clear bearerSentPkts, bearerRcvdPkts, bearerSentOctets, and bearerRcvdOctets. |
| bearerConnEntry | 1.3.6.1.4.1.351.110.5.5.9.1.1 | not-accessible | Each entry in this table corresponds to a bearer connection, that was setup by binding an endpoint with a VC(Virtual channel)/CID pair, either through CLI or SNMP. The statistical counters in this table are generic voice quality parameters that are equally applicable in all types of Voice Over Packet adapations (VoIP, VoAAL1 and VoAAL2). However, they are maintained only in the PVC(Permanent virtual circuit) trunking model because, these counters get reset in the switching model on a per call basis. The entries in this table are implicitly created/deleted at the time of creation/deletion of entries in the vismAal2CidCnfTable. | |
| bearerConnGrp | 1.3.6.1.4.1.351.110.5.5.9 | |||
| bearerConnTable | 1.3.6.1.4.1.351.110.5.5.9.1 | not-accessible | This table describes the statistical information available on a per-bearer connection basis. These values are applicable equally to an endpoint. | |
| C32 bearerCurrentConnAISCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.22 | Counter32 | read-only | This object contains count of external Connection AIS AAL2 (Type 2) received in this bearerEndptNum since its creation. |
| C32 bearerCurrentConnRDICnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.23 | Counter32 | read-only | This object contains the count of external Connection RDI (Remote Defect Indication) AAL2 (Type 2) received in this bearerEndptNum since its creation. |
| C32 bearerCurrentExtAISRcvCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.20 | Counter32 | read-only | This object contains the count of external AIS AAL2 (Type 2) received on this bearerEndptNum since its creation. |
| C32 bearerCurrentExtAISXmtCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.24 | Counter32 | read-only | This object contains the count of external AIS AAL2 (Type 2) transmitted in this bearerEndptNum since its creation. |
| C32 bearerCurrentExtRAIRcvCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.21 | Counter32 | read-only | This object contains the number of external RAI AAL2 (Type 2) received in this bearerEndptNum since its creation. |
| C32 bearerCurrentExtRAIXmtCnts | 1.3.6.1.4.1.351.110.5.5.9.1.1.25 | Counter32 | read-only | This object contains the count of external RAI AAL2 (Type 2) transmitted in this bearerEndptNum since its creation. |
| U32 bearerCurrentRcvCellRate | 1.3.6.1.4.1.351.110.5.5.9.1.1.19 | Unsigned32 | read-only | Current receive ATM cell rate is the ATM cells required to receive current AAL2 packets on a CID per second. |
| U32 bearerCurrentXmtCellRate | 1.3.6.1.4.1.351.110.5.5.9.1.1.17 | Unsigned32 | read-only | Current transmit ATM cell rate is the ATM cells required to transmit current AAL2 packets on a CID per second. |
| I32 bearerEndptNum | 1.3.6.1.4.1.351.110.5.5.9.1.1.1 | Integer32 | read-only | This attribute defines the index for the Bearer Connection Table. This refers to the same value as the index to the mgEndpointTable ie. mgEndpointNumber. This is define in CISCO-WAN-MG-MIB MIB. |
| I32 bearerJitter | 1.3.6.1.4.1.351.110.5.5.9.1.1.9 | Integer32 | read-only | This attribute defines the jitter (a.k.a interarrival jitter) This value is determined by the DSP(Digital Signal Processing) and obtained by the HOST processor upon querying the DSP on a periodic basis. |
| I32 bearerLatency | 1.3.6.1.4.1.351.110.5.5.9.1.1.10 | Integer32 | read-only | This attribute defines the latency (a.k.a end-to-end average transmission delay for a voice packet). |
| I32 bearerLcn | 1.3.6.1.4.1.351.110.5.5.9.1.1.3 | Integer32 | read-only | This attribute defines the PVC or LCN(Logical Channel Number) number to which this bearer connection is associated with. This refers to the same value as in vismCnfChanNum in vismChanCnfGrp table. This is define in CISCO-VISM-CONN-MIB MIB. |
| C32 bearerLostPkts | 1.3.6.1.4.1.351.110.5.5.9.1.1.8 | Counter32 | read-only | This attribute defines the count of packets lost in the egress direction (from the network). This is a computed number based on the expected number of packets and the actual number of packets arrived from the network. |
| U32 bearerPeakRcvCellRate | 1.3.6.1.4.1.351.110.5.5.9.1.1.18 | Unsigned32 | read-only | Peak receive ATM cell rate is the ATM cells required to receive peak AAL2 packets on a CID per second since midnight as per system time; the peak cell rate gets cleared every 24 hours at midnight as per system time. |
| U32 bearerPeakXmtCellRate | 1.3.6.1.4.1.351.110.5.5.9.1.1.16 | Unsigned32 | read-only | Peak transmit ATM cell rate is the ATM cells required to transmit peak AAL2 packets on a CID per second since midnight as per system time; the peak cell rate gets cleared every 24 hours at midnight as per system time. |
| C32 bearerRcvdOctets | 1.3.6.1.4.1.351.110.5.5.9.1.1.7 | Counter32 | read-only | This attribute defines the count of bytes received from the network since this connection setup. |
| C32 bearerRcvdPkts | 1.3.6.1.4.1.351.110.5.5.9.1.1.5 | Counter32 | read-only | This attribute defines the count of packets received from the network since this connection setup. |
| C32 bearerSentOctets | 1.3.6.1.4.1.351.110.5.5.9.1.1.6 | Counter32 | read-only | This attribute defines the count of bytes sent towards the network since this connection setup. |
| C32 bearerSentPkts | 1.3.6.1.4.1.351.110.5.5.9.1.1.4 | Counter32 | read-only | This attribute defines the count of packets sent towards the network since this connection setup. |
| ciscoVismAAl2CidGroup | 1.3.6.1.4.1.351.150.87.2.1.2 | The collection of objects which are used to represent VISM AAL2 CID connection. | ||
| ciscoVismAAl2CidGroupRev1 | 1.3.6.1.4.1.351.150.87.2.1.3 | The collection of objects which are used to represent VISM AAL2 CID connection. | ||
| ciscoVismAtmTrunkMIB | 1.3.6.1.4.1.351.150.87 | The MIB module contain the Bearer and CID (Channel Identifier) connection information. | ||
| ciscoVismBearerConnGroup | 1.3.6.1.4.1.351.150.87.2.1.1 | The collection of objects which are used to represent VISM Bearer connection. | ||
| ciscoVismBearerConnGroupRev1 | 1.3.6.1.4.1.351.150.87.2.1.4 | The collection of objects which are used to represent VISM Bearer connection. | ||
| cvismAtmTrunkCompliance | 1.3.6.1.4.1.351.150.87.2.2.1 | The compliance statement for objects related to VISM Bearer and CID Connection. | ||
| cvismAtmTrunkComplianceRev1 | 1.3.6.1.4.1.351.150.87.2.2.2 | The compliance statement for objects related to VISM Bearer and CID Connection. | ||
| cvismAtmTrunkComplianceRev2 | 1.3.6.1.4.1.351.150.87.2.2.3 | The compliance statement for objects related to VISM Bearer and CID Connection. | ||
| cvismAtmTrunkMIBCompliances | 1.3.6.1.4.1.351.150.87.2.2 | |||
| cvismAtmTrunkMIBConformance | 1.3.6.1.4.1.351.150.87.2 | |||
| cvismAtmTrunkMIBGroups | 1.3.6.1.4.1.351.150.87.2.1 | |||
| INT vismAal2CidAdminState | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.18 | INTEGER | read-write | This attribute defines the operational administrative state of the bearer connection. cidInService: This is an operational state of the bearer connection where it is ready to transmit/receive data/voice packets. The user can take the bearer connection into cidInService. cidCommandedOutOfService: This is an operational state of the bearer connection where it is not ready to transmit/receive data/voice packets. The user can take the bearer connection into cidPendingOutOfService. cidPendingInService: It is a transient state. In this state the bearer connection is waiting for the user to transition it to the cidInService state. This value cannot be specified in a management protocol set operation. cidPendingOutOfService: It is a transient state. In this state the bearer connection is waiting for the user to transition it to the cidOutOfService state. This value cannot be specified in a management protocol set operation. cidUnknownState: This is an abnormal state of the bearer connection. This state would indicate to the user that there is some data integrity issue on the bearer administrative state. |
| T/F vismAal2CidCasTransport | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.11 | TruthValue | read-write | This attribute defines whether the CAS(Channel Associated Signaling) bits need to be transported to the other endpoint. In the case of switching application, the CAS bits are backhauled to the call agent through xGCP(Gateway Control Protocol)-CAS protocol. Note that if the line signaling type is CAS the default value is 'true(1)', else the default value is 'false(2)'. |
| vismAal2CidCnfTable | 1.3.6.1.4.1.351.110.5.5.3.4.1 | not-accessible | This table is defined to establish the binding between an endpoint and a PVC/CID pair in the case of AAL2 adaptation. This table is created and used in trunking mode VISM application only. The maximum number of CIDs that can be configured depends on the current codec template being used as represented by vismAppliedTemplate object. The signaling type of the line has to be configured before adding any CID on that line. | |
| INT vismAal2CidCodecType | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.9 | INTEGER | read-write | This attribute defines the codec Type used for the connection. 'g711u' represents PCMU with 64 kbps. 'g711a' represents PCMA with 64 kbps. 'g726r32000' represents G.726 at rate 32 kbps 'g726r16000' represents G.726 at rate 16 kbps 'g726r24000' represents G.726 at rate 24 kbps 'g726r40000' represents G.726 at rate 40 kbps 'g729a' represents G.729 Annex A algorithm. 'g729ab' represents G.729 Annex A and Annex B algorithm. 'clearChannel' represents CCD with 64 kbps. 'g723h' represents G.723.1-H at rate 6.3kbps. 'g723ah' represents G.723.1-H at rate 6.3kbps with Silence Supression ON. 'g723l' represents G.723.1-L at rate 5.3kbps. 'g723al' represents G.723.1-L at rate 5.3kbps with Silence Supression ON. 'lossless' represents Lossless Note : 1. When codec type is 'clearChannel', vismAal2CidProfileType and vismAal2CidProfileNum are not applicable and will be ignored. 2. Value 10 is RESERVED. |
| T/F vismAal2CidDtmfTransport | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.10 | TruthValue | read-write | This attribute defines whether the DTMF (Dual Tone Multi Frequency) digits need to be transported to the other end-point. |
| T/F vismAal2CidEcanEnable | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.12 | TruthValue | read-write | This attribute defines whether Echo Cancellation has to be enabled on this connection. If it is set to 'true(1)', echo cancellation is enabled. If it is set to 'false(2)', echo cancellation is disabled. |
| vismAal2CidEntry | 1.3.6.1.4.1.351.110.5.5.3.4.1.1 | not-accessible | Identifies an entry for vismAal2CidCnfTable. | |
| INT vismAal2CidFailReason | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.17 | INTEGER | read-only | This object is used to indicate the CID failure reason. 'self': fail because of non-PVC alarm 'highLevel': fail because of PVC alarm 'both': fail because of both PVC and non-PVC alarm 'notFail': not fail |
| vismAal2CidGrp | 1.3.6.1.4.1.351.110.5.5.3.4 | |||
| T/F vismAal2CidICSEnable | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.15 | TruthValue | read-write | This object is used to enable or disable the ICS(Idle Channel Suppression) for a CID. This can be specified while adding the CID and cannot be modified. When the Idle Channel Suppression is enabled the DSP will look for the idle CAS (ABCD bits) pattern specified in ds0IdleCode in CISCO-VISM-DSX0-MIB MIB. If the idle pattern is present the DSP stops generating voice packets towards ATM side. By default the ds0IdleCode will be zero unless the user has configured it before adding the CID. If the ds0IdleCode is changed after the CID is added it will have no affect unless the card is reset. ICS is applicable only for trunking application, in case of switching there is no need for ICS as the calls are teared down and set up dynamically. |
| I32 vismAal2CidLcn | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.2 | Integer32 | read-only | This attribute defines part of the index for the vismAal2CidCnfTable. Since CID is unique to a PVC, a combination of LCN and CID uniquely identifies a voice connection. This field refers to vismCnfChanNum defined in vismChanCnfGrp of CISCO-VISM-CONN-MIB MIB. |
| I32 vismAal2CidNum | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.1 | Integer32 | read-only | This attribute defines part of the index for this table. vismAal2CidNum is the CID of a voice channel. CID has to be the same at both endpoints for a connection. CID is unique only within the context of a Virtual Circuit (PVC or SVC). |
| I32 vismAal2CidProfileNum | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.8 | Integer32 | read-write | This attribute defines the profile number. A profile is a set of entries, where each entry specifies an encoding format with a UUI(User-to-User Indication) range and length. This set defines a mapping that informs the receiver of a Type 1 packet how to interpret the packet contents, i.e. which encoding format in the profile is being used. |
| INT vismAal2CidProfileType | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.7 | INTEGER | read-write | This attribute defines the profile type. The profile type defines which group of the profile tables the profile number should correspond to. There are three possible groups: 'itu' - corresponding to the tables in ITU format in the profile is being used. 'atm' - This is not supported 'custom' - VISM specific custom profiles. |
| INT vismAal2CidRowStatus | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.4 | INTEGER | read-write | This variable allows to add or delete a CID. A CID can only be added or deleted. Once added, modifying an entry is not allowed. 'createAndGo': Use this to add an entry in this table. 'active': This values is returned, once the row is created. 'destroy': Use this to delete an entry from this table. |
| INT vismAal2CidState | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.16 | INTEGER | read-only | Indicates the state of the CID. 'cidStateActive' : The CID is in service and operational. 'cidStateFailed' : The CID is in service but not operational, e.g. because the PVC that the CID belongs to is receiving F5(Operation, Administration and Maintenance Flow) level alarm. When VISM sees alarm on a CID (network side) sets this object to 'cidStateFailed', and an AIS will be sent on the ds0(Time Division Multiplexed voice channel) that this CID corresponds to. If the whole PVC is in alarm then all the CIDs on that PVC will be set to 'cidStateFailed', trapVismChanFailed trap will be sent and all the ds0's that corresponds to each of the CIDs on this PVC will be in alarm. If VISM sees an alarm on a ds0 in a line then an RAI(Remote Alarm Indication) will be sent on the CID that corresponds to this ds0, however the CID will not be put in failed state. |
| T/F vismAal2CidType3Redundancy | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.5 | TruthValue | read-write | This attribute defines whether the triple redundancy is supported for type 3 packets in AAL2 for this channel. When Triple redundancy is enabled for a channel, the Type 3 packets (CAS bits, dialled digits and user state control packets) are transmitted in triplicates with an interval defined as per the standards I.366.2. For channels which are quite reliable, triple redundancy can be disabled in order to save the bandwidth and the processing overheads. The default value of this object is 'true(1)' if either vismAal2CidCasTransport or vismAal2CidDtmfTransport is 'true(1)', otherwise the default value is 'false(2)'. |
| T/F vismAal2CidVad | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.6 | TruthValue | read-write | This attribute defines whether the VAD (Voice Activity Detection) has to be applied on this channel, upon detection of silence. For algorithms that do not have VAD standards, Cisco-proprietary VAD can be applied and the generic SID(Silence Information Descriptor) packet as specified in I.366.2 standards can be sent to the other end. When the codec specify in vismAal2CidCodecType is 'clearChannel' VAD has to be off. |
| INT vismAal2CnfPktPeriod | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.14 | INTEGER | read-write | This object is used to configure the packetization period for a given codec. This packetization period has to be a valid entry in the profile table. Profile type and number identify a unique profile table and one codec type in this table might have one or more packetization period. This is applicable only if the vismAal2CidCodecType is 'g729a'. The configurable values for 'g729a' are 10,20,30 & 40. If a CID entry is configured with a codec other than 'g729a' then the user cannot configure the pkt period for that codec and the pkt period is picked from the profile table. Hence when we do get/walk on this entry/table any one of the above values could be returned. |
| I32 vismAal2EndptNum | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.3 | Integer32 | read-write | This attribute defines the endpoint number to which this CID is associated. It is the same as mgEndpointNumber defined in mgEndpointTable of CISCO-WAN-MG-MIB MIB. |
| I32 vismAal2InitVadTimer | 1.3.6.1.4.1.351.110.5.5.3.4.1.1.13 | Integer32 | read-write | This attribute defines the hangover time for VAD. Once the voice inactivity is detected, the gateway will wait for this duration before activating silence suppression. |
RFC description
A Cisco SNMP MIB for the Voice and Signaling Module (VISM) containing bearer and channel identifier connection information, statistics counters, and voice quality parameters for voice-over-ATM.
Start monitoring Cisco MGX/VISM ATM voice gateways 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.