CISCO-VISM-CONN-STAT-MIB
AI MIB Summary
The CISCO-VISM-CONN-STAT-MIB monitors channel-level traffic statistics and connection states for Cisco Visual Information Services (VISM) appliances. It provides specific counters for tracking VISM channel throughput, session activity, and error conditions to facilitate performance analysis and fault isolation in video delivery networks.
The MIB module contain VISM channel counters information.
Main OID:
ciscoVismConnStatMIB.1.3.6.1.4.1.351.150.89
46
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
46 total| Object Name |
|---|
vismChanCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.3.3 |
vismChanCntGrpTablevismChanCntGrpTable contains VISM channels counters. SEQUENCE OF VismChanCntGrpEntry .1.3.6.1.4.1.351.110.5.5.3.3.1 |
vismChanCntGrpEntryAn entry for each voice channel. VismChanCntGrpEntry .1.3.6.1.4.1.351.110.5.5.3.3.1.1 |
vismCntChanNumThis object identifies the LCN(Logical Channel Number) on the VISM.ro Integer32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.1 |
vismCntClrButtonThis object is use to either reset counters or perform no action(do not clear counters).ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.3.1.1.10 |
vismChanAal2HecErrorsThis object keep count of egress AAL2(ATM Adaptation layer 2) CPS(Common Part Sub-layer) PDU(Protocol Data Unit) dropped due to HEC(Header Error Control) error.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.11 |
vismChanAal2CrcErrorsThis object keeps track of egress AAL2 Type3 CPS PDUs dropped due to invalid CRC-10(Cyclic redundancy check) error. CRC validation is for Type 3 packets only. Type 1 packets are not subjected to CRC-10 error validation. Also this counter keeps track of CRC-10 errors for the Type 3 packets which are generated by the the datamover CPU only. It does not take into account of Type 3 packets generated by the DSP(Digital Signal Processing).ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.12 |
vismChanAal2OamLpbLostCellsThis object keeps track of the number of OAM(Operation and management) loopback cells lost. OAM loopback cells are sent on a periodic basis (1 sec) on each PVC(Permanent Virtual Circuit) to monitor the health of the PVC.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.13 |
vismChanAal2InvOsfCellsThis object keeps track of the number AAL2 cells dropped due to invalid OSF (OffSet Field) in the egress direction.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.14 |
vismChanAal2InvParCellsThis object keeps track of the number of AAL2 cells dropped due to invalid Parity bit field in the egress direction.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.15 |
vismChanAal2CpsSentPktsThis object keeps track of the number of AAL2 CPS packets sent to the network.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.16 |
vismChanAal2CpsRcvdPktsThis object keeps track of AAL2 CPS packets received from the network. This does not include the packets which are counted as error packets.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.17 |
vismChanAal2CpsInvCidPktsThis object keeps track of AAL2 CPS packets dropped in the egress direction due to invalid CID(Channel Identifier). The CID may be considered as invalid if it is out of range or not configured.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.18 |
vismChanAal2CpsInvUuiPktsThis object keeps track of AAL2 CPS packets dropped in the egress direction due to invalid UUI (User-to-User Information) field.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.19 |
vismChanAal2CpsInvLenPktsThis object keeps track of AAL2 CPS packets dropped in the egress direction due to invalid length field.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.20 |
vismChanAal5InvCpiPdusThis object counts the number of AAL5 PDUs dropped in the egress direction due to invalid CPI(Common Part Indicator) field in the AAL5 PDU trailer. This is applicable only to the PVCs configured as AAL5 PVCs (VoIP(Voice Over IP) PVCs or CCS(Common Channel Signaling) PVCs in the case of VoAAL2 application.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.21 |
vismChanAal5OversizedSdusRcvdPdusThis object counts the number AAL5 PDUs dropped due to the SDU(Service Data Unit) size bigger than the configured value. This is applicable for AAL5 PVCs only.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.22 |
vismChanAal5InvLenPdusThis object counts the number of AAL5 PDUs dropped due to the length violations. This is applicable to the CCS PVCs. The HDLC(High Level Data Link Control) frames should have a minimum frame size in order for the proper interpretation by the upper layer protocol.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.23 |
vismChanAal5Crc32ErrorPdusThis object counts the number of AAL5 PDUs dropped in the egress direction due to CRC-32 errors detected by the SAR(Segmentation and Reassembly).ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.24 |
vismChanAal5ReassemTimerExpiryPdusThis object counts of AAL5 PDU reassembly timer expirations. The timers are maintained in the egress direction for building an AAL5 PDU from the cells.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.25 |
vismChan24HrPeakXmtCellRateThis object counts the peak transmit cell rate (cells per second) for the channel since midnight with reference to node time; the peak cell rate counter gets reset to 0 every 24 hours at midnight. If the node time is changed, the counter will continue to gather data until the next time midnight is reached.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.26 |
vismChanCurrentXmtCellRateThis object counts the current transmit cell rate (cells per second) for the channel.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.27 |
vismChan24HrPeakRcvCellRateThis object counts the peak receive cell rate (cells per second) for the channel since midnight with reference to node time; the peak cell rate counter gets reset to 0 every 24 hours at midnight. If the node time is changed, the counter will continue to gather data until the next time midnight is reached.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.28 |
vismChanCurrentRcvCellRateThis object counts the current receive cell rate (cells per second) for the channel.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.29 |
vismChanAisSuppressCountThis object holds the number of times that ATM network alarms were successfully suppressed and prevented from propagating onto the TDM side for this PVC.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.30 |
vismChanXmtAisCntsThe number of instances that an ATM AIS alarm was transmitted.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.31 |
vismChanRcvAisCntsThe number of instances that an ATM AIS alarm was received.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.32 |
vismChanXmtFerfCntsThe number of instances that an ATM FERF alarm was transmitted.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.33 |
vismChanRcvFerfCntsThe number of instances that an ATM FERF alarm was received.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.34 |
vismChanAal5PduSentPktsThis object counts the number of AAL5 PDUs transmitted to the network. This is only applicable to the PVCs configured as AAL5 PVCs, VoIP (Voice Over IP) PVCs or CCS (Common Channel Signaling) PVCs in the case of VoAAL2 applications.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.35 |
vismChanAal5PduRcvdPktsThis object counts the number of AAL5 PDUs received from the network. This is only applicable to the PVCs configured as AAL5 PVCs, VoIP (Voice Over IP) PVCs or CCS (Common Channel Signaling) PVCs in the case of VoAAL2 applications.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.36 |
vismChanAisDelayLeftThe real-time number of seconds remaining for the AIS delay timer after which the ATM alarm will be propagated to the TDM side. This object is tied to the vismChanAisDelayTime object in the CISCO-VISM-CONN-MIB. vismChanAisDelayTime will store the configurable AIS delay timer. The delay time left (vismChanAisDelayLeft) will be equal to the delay time in vismChanAisDelayTime until an AIS alarm is received at which point it starts to decrement and could go down to 0 and propagate the alarm to the TDM side.ro Unsigned32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.37 |
vismChanOamLpbkTimeoutCntsThe number of instances that OAM loopback timeout alarm has occurred since the system was last re-initialized.ro Counter32 .1.3.6.1.4.1.351.110.5.5.3.3.1.1.38 |
vismChanOamLpbkTimeoutDurationThe total duration of OAM loopback timeout alarms since the system was last re-initialized.ro Unsigned32 UNITS "seconds" .1.3.6.1.4.1.351.110.5.5.3.3.1.1.39 |
ciscoVismConnStatMIBThe MIB module contain VISM channel counters information. MODULE-IDENTITY .1.3.6.1.4.1.351.150.89 |
ciscoVismConnStatMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.351.150.89.2 |
ciscoVismConnStatMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.351.150.89.2.1 |
ciscoVismConnStatGroupThe collection of objects which are used to represent VISM channel counter group.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.1.1 |
ciscoVismConnStatGroup1The collection of objects which are used to represent VISM channel counter group.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.1.2 |
ciscoVismConnStatGroup2The collection of objects which are used to represent VISM channel counter group.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.1.3 |
ciscoVismConnStatGroup3The collection of objects which are used to represent VISM channel counter group. Unknown .1.3.6.1.4.1.351.150.89.2.1.4 |
ciscoVismConnStatMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.351.150.89.2.2 |
ciscoVismConnStatComplianceThe compliance statement for objects related to VISM channel counters.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.2.1 |
ciscoVismConnStatCompliance1The compliance statement for objects related to VISM channel counters.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.2.2 |
ciscoVismConnStatCompliance2The compliance statement for objects related to VISM channel counters.deprecated Unknown .1.3.6.1.4.1.351.150.89.2.2.3 |
ciscoVismConnStatCompliance3The compliance statement for objects related to VISM channel counters. Unknown .1.3.6.1.4.1.351.150.89.2.2.4 |