Home/Catalog/CISCO-WAN-LAPD-TRUNK-MIB

CISCO-WAN-LAPD-TRUNK-MIB

AI MIB Summary

The CISCO-WAN-LAPD-TRUNK-MIB monitors and manages the state of LAPD trunk interfaces on Cisco routers, specifically tracking the transport of PRI signaling over Reliable UDP (RUDP) connections for Common Channel Signaling (CCS) VoIP applications. Key metrics include trunk operational status, RUDP session establishment and termination events, and the synchronization state of the LAPD signaling channel between the router and the VoIP gateway.

The MIB module is defined for establishing a Trunk to transport PRI (Primary Rate Interface) signaling information over a RUDP (Reliable UDP) connection for CCS (Common Channel Signaling) VoIP(Voice Over IP) Trunking application.
Main OID:
ciscoWanLapdTrunkMIB.1.3.6.1.4.1.351.150.23
64
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

64 total
Object Name
vismLapdGrp
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.110.5.5.12
vismLapdTableThis table is used for maintaining the configuration of the LAPD channel on VISM.
SEQUENCE OF VismLapdEntry
.1.3.6.1.4.1.351.110.5.5.12.1
vismLapdEntryAn entry for vismLapdTable.
VismLapdEntry
.1.3.6.1.4.1.351.110.5.5.12.1.1
vismLapdIndexThis is an index to vismLapdTable. This is derived from the following formula: index = 31 * (DS1# - 1) + DS0# where : DS1# - The T1/E1 line number in the range 1 - 8. DS0# - The DS0 channel number ranging from 1 to 24 for T1 and 1 to 31 for E1.ro
Integer32
.1.3.6.1.4.1.351.110.5.5.12.1.1.1
vismLapdAppTypeThis object indicates the type of the LAPD interface. When the user creates a LAPD entry this object need to be specified. After creation it cannot be modified. 'pri' - level of service provided by ISDN(Integrated Services Digital Network) that carries voice, data, other services with control and signaling information in D-channel. 'gr-303' - standard interfaces for integrated digital loop carrier systems.rw
Enumeration
.1.3.6.1.4.1.351.110.5.5.12.1.1.2
vismLapdWinSizeThe window size - maximum number of sequentially numbered I-frames that may be outstanding.rw
Integer32
.1.3.6.1.4.1.351.110.5.5.12.1.1.3
vismLapdN200The maximum number of retransmissions of a frame.rw
Integer32
.1.3.6.1.4.1.351.110.5.5.12.1.1.4
vismLapdT200The maximum number of time in milliseconds to wait for acknowledgement for a transmit frame. This value should be less than vismLapdT203. For PRI, the range is 1000 ms to 1023000 ms. The default is 1000 ms. For GR-303, the range is 100 ms to 350 ms in increments of 50 ms. The default value is 150 ms.rw
Integer32
.1.3.6.1.4.1.351.110.5.5.12.1.1.5
vismLapdT203The maximum time (in milliseconds) allowed without frames being exchanged. This value should be greater than vismLapdT200. For PRI, the range is 1000 to 1023000 and the default is 10000 ms. For GR-303, the range is 10000 to 300000 ms in increments of 10000 ms. The default is 30000 ms.rw
Integer32
.1.3.6.1.4.1.351.110.5.5.12.1.1.6
vismLapdTypeThis object specifies what type of interface the LAPD stack will be used with. ccitt(1) : CCITT att5EssPRA(3) : AT&T 5ESS PRA att4Ess(4) : AT&T 4ESS ntDMS100PRA(6) : NT dms100 PRA vn2or3(7) : VN 2 or VN 3 insNet(8) : INS Net tr6MPC(9) : tr6 MPC tr6PBX(10) : tr6 PBX ausp(12) : Austel Primary ni1(13) : National ISDN-1 etsi(14) : ETSI bc303TMC(15) : Bellcorp tr303 tmc bc303CSC(16) : Bellcorp tr303 csc ntDMS250(17) : NT dms250 bellcore(18) : Bellcore ni2(19) : National ISDN-2rw
Enumeration
.1.3.6.1.4.1.351.110.5.5.12.1.1.7
vismLapdRowStatusRow status allows users to create or delete a LAPD entry. 'createAndGo' - this option is use to create an entry in the table. Before a LAPD entry is created, the session manager should be set up(add a PRI backhaul session set, and session group between VISM and the call agent). Before creating a LAPD entry the entry in HDLC table will implicitly created first. If the DS0 has already been used then the request of creating a LAPD channel on the same DS0 on the same line will be rejected. After creating the LAPD entry the corresponding entry in vismLapdStatsTable will be implicitly created. 'active' - When an entry is created it becomes active. 'destroy' - Use this to delete an entry in this table. After implicitly deleting all the entries(if there is any) in vismLapdDlcEntry table for the specific D channel the entry in vismLapdEntry will be deleted, then the entry in vismLapdStatsTable will be implicitly deleted, followed by the deletion of the HDLC entry.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.351.110.5.5.12.1.1.8
vismLapdSideThis object specifies whether LAPD stack is on the user side or network side. This object can be set when the row is created. It cannot be modified for an existing row.rw
Enumeration
.1.3.6.1.4.1.351.110.5.5.12.1.1.9
vismLapdTrunkTypeThis object indicates if the line is configured for Trunking or PRI Backhaul. This object is set to the appropriate type when the vismRudpSessionType (defined in CISCO-VISM-SESSION-MIB MIB) parameter in the vismRudpSessionCnfEntry(specify in the same MIB) table is set. The motivation to have similar such objects at two places is for convenience.ro
Enumeration
.1.3.6.1.4.1.351.110.5.5.12.1.1.10
vismLapdStatsTableThis table contains statistics information for all LAPD (D channel Data Link) interfaces on VISM.
SEQUENCE OF VismLapdStatsEntry
.1.3.6.1.4.1.351.110.5.5.12.2
vismLapdStatsEntryAn entry in the LAPD Table.
VismLapdStatsEntry
.1.3.6.1.4.1.351.110.5.5.12.2.1
vismLapdStatsIndexThis is the index for this table. It is the same as vismLapdIndex. An entry of this table will be implicitly created when a LAPD entry is added.ro
Integer32
.1.3.6.1.4.1.351.110.5.5.12.2.1.1
vismLapdRxInfoFramesThis counter contains received information frames on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.2
vismLapdTxInfoFramesThis counter contains information frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.3
vismLapdRxReadyFramesThis counter contains Receiver Ready frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.4
vismLapdTxReadyFramesThis counter contains Receiver Ready frames transmitted on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.5
vismLapdRxNotReadyFramesThis counter contains Receiver Not Ready frames received on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.6
vismLapdTxNotReadyFramesThis counter contains Receiver Not Ready frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.7
vismLapdRxSABMFramesThis counter contains Set Asynchronous Balanced Mode frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.8
vismLapdTxSABMFramesThis counter contains Set Asynchronous Balanced Mode frames transmitted on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.9
vismLapdRxDisconFramesThis counter contains Disconnect frames received on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.10
vismLapdTxDisconFramesThis counter contains Disconnect frames transmitted on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.11
vismLapdRxUAFramesThis counter contains Unnumbered Acknowledge frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.12
vismLapdTxUAFramesThis counter contains Unnumbered Acknowledge frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.13
vismLapdRxDiscModeFramesThis counter contains Disconnect Mode frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.14
vismLapdTxDiscModeFramesThis counter contains Disconnect Mode frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.15
vismLapdRxFrmRejectFramesThis counter contains Frame Reject frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.16
vismLapdTxFrmRejectFramesThis counter contains Frame Reject frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.17
vismLapdRxExchIdFramesThis counter contains Exchange Id frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.18
vismLapdTxExchIdFramesThis counter contains Exchange Id frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.19
vismLapdRxUnumInfoFramesThis counter contains Unnumbered Information frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.20
vismLapdTxUnumInfoFramesThis counter contains Unnumbered Information frames transmitted on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.21
vismLapdRxRejectFramesThis counter contains Received Reject Frames on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.22
vismLapdTxRejectFramesThis counter contains Reject frames transmitted on LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.23
vismLapdRxInvalidFramesThis counter contains Invalid frames received on a LAPD.ro
Counter32
.1.3.6.1.4.1.351.110.5.5.12.2.1.24
vismLapdDlcTableThis table is used for maintaining the link state of different DLCs on a LAPD channel. An entry of this table will be implicitly created when a LAPD entry is added.
SEQUENCE OF VismLapdDlcEntry
.1.3.6.1.4.1.351.110.5.5.12.3
vismLapdDlcEntryAn entry for vismLapdDlcTable.
VismLapdDlcEntry
.1.3.6.1.4.1.351.110.5.5.12.3.1
vismLapdDlcIndexThis object identifies the corresponding LAPD index. It is the same as vismLapdIndex.ro
Integer32
.1.3.6.1.4.1.351.110.5.5.12.3.1.1
vismLapdDlcSapiThis is the SAPI(Service Access Point Identifier) of a specific DLC(Data Link Control).ro
Integer32
.1.3.6.1.4.1.351.110.5.5.12.3.1.2
vismLapdDlcTeiThis is the TEI(Terminal Endpoint Identifier) of a specific DLC.ro
Integer32
.1.3.6.1.4.1.351.110.5.5.12.3.1.3
vismLapdDlcLinkStateThis object indicate the linking state on a given DLC.ro
Enumeration
.1.3.6.1.4.1.351.110.5.5.12.3.1.4
ciscoWanLapdTrunkMIBThe MIB module is defined for establishing a Trunk to transport PRI (Primary Rate Interface) signaling information over a RUDP (Reliable UDP) connection for CCS (Common Channel Signaling) VoIP(Voice Over IP) Trunking application.
MODULE-IDENTITY
.1.3.6.1.4.1.351.150.23
ciscoWanLapdTrunkMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.1
vismLapdTrunkGrp
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.1.1
vismLapdTrunkGrpTableThis table defines attributes used to set up a Trunked LAPD (Link Access Procedure on the D-channel) connection over RUDP between 2 VISM's to transport PRI D channel information. Such a Trunked connection over RUDP can only be created if the D-channel has already not been configured for PRI Backhaul. The object vismLapdTrunkType in vismLapdTable indicate PRI Backhaul or Trunking is configured, also an entry will be created for each D channel. PRI Backhaul and PRI Trunking can co-exist on the same card but not on the same line, a line (DS1) is associated with a LAPD RUDP through vismLapdTrunkRudpIndex.
SEQUENCE OF VismLapdTrunkGrpEntry
.1.3.6.1.4.1.351.150.23.1.1.1
vismLapdTrunkGrpEntryAn entry in the vismLapdTrunkGrpTable.
VismLapdTrunkGrpEntry
.1.3.6.1.4.1.351.150.23.1.1.1.1
vismLapdTrunkNumThis is the index of vismLapdTrunkGrpTable.
Integer32
.1.3.6.1.4.1.351.150.23.1.1.1.1.1
vismLapdTrunkState'oos' - Out of service state. The LAPD Trunk state is independent of the RUDP session state in the sense that the LAPD state could be 'oos' while the RUDP session state is 'is' and vice versa. 'is' - In service state. 'unknown' - This is the state other than the above states. If the communication is lost between the 2 VISM's, the state of this connection becomes 'oos'.ro
Enumeration
.1.3.6.1.4.1.351.150.23.1.1.1.1.2
vismLapdTrunkRudpIndexAll LAPD Trunk connections are over RUDP. Each RUDP connection is characterized by a set of negotiable and non-negotiable parameters. These parameters are in vismRudpSessionCnfEntry(defined in CISCO-VISM-SESSION-MIB MIB) table. This object is an index into that table. Before creating an entry in this table the corresponding RUDP session entry must be created in the vismRudpSessionCnfEntry table with the vismRudpSessionType(defined in the same MIB) as LAPD Trunking. The RUDP session cannot be deleted if the corresponding LAPD Trunk still exist. The LAPD Trunk needs to be deleted before deleting RUDP session as specified in CISCO-VISM-SESSION-MIB.rw
Integer32
.1.3.6.1.4.1.351.150.23.1.1.1.1.3
vismLapdTrunkRowStatusThis variable allows the user to add or delete the entry for this table. 'createAndGo': Use this to add a LAPD Trunk connection in this table. The vismLapdTrunkRudpIndex for this corresponding entry has to be specified also. 'active': This value is returned, once the row is created. 'destroy': Use this to delete a LAPD Trunk connection from this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.351.150.23.1.1.1.1.4
vismLapdTrunkNotificationPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.2
vismLapdTrunkNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.2.0
vismLapdTrunkMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.3
vismLapdTrunkMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.3.1
vismLapdTrunkMIBComplianceThe complaince statement for LAPD Trunk group which implements vismLapdTrunkGrp MIB.
Unknown
.1.3.6.1.4.1.351.150.23.3.1.1
vismLapdTrunkMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.351.150.23.3.2
vismLapdTrunkGroupThis group contains objects related to configuration of LAPD Trunk connections over RUDP.
Unknown
.1.3.6.1.4.1.351.150.23.3.2.1
ciscoVismLapdGroupThe collection of objects which are used to represent VISM LAPD information.
Unknown
.1.3.6.1.4.1.351.150.23.3.2.2
ciscoVismLapdStatsGroupThe collection of objects which are used to represent VISM LAPD Statistics information.
Unknown
.1.3.6.1.4.1.351.150.23.3.2.3
ciscoVismLapdDlcTableThe collection of objects which are used to represent VISM LAPD link State of different DLCs on a LAPD channel.
Unknown
.1.3.6.1.4.1.351.150.23.3.2.4
CISCO-WAN-LAPD-TRUNK-MIB - SNMP MIB Reference | MIBs Explorer