MIBs Depot

CISCO-WAN-BBIF-ATM-CONN-MIB

Registered at
1.3.6.1.4.1.351.150.35
Last updated
2002-09-09 00:00
Organization
Cisco Systems, Inc.
Revisions
2002-09-09 00:00
Namespace
cisco
Source file
CISCO-WAN-BBIF-ATM-CONN-MIB
Digest
sha256:de41c819eaf5c2590baa8e78e4b3b144c1f8b51664b28285c59ed2b37d04c59a

Description

The MIB module to configure the ATM Connections on a broad band interface in PXM1 Service module.

Contact

Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-wanatm@cisco.com

Imports

FromSymbols
BASIS-MIBbbChanCnfGrp, bbChanStateGrp
CISCOWAN-SMIciscoWan
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIInteger32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

BASIS-MIB
CISCO-WAN-BBIF-ATM-CONN-MIB
CISCOWAN-SMI
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Textual conventions

NameOIDSyntaxAccessStatus
IfNsapAddress
TEXTUAL-CONVENTION
ATM address used by the networking entity. The only address type presently supported is NSAP (20 octets)
current

Objects

NameOIDSyntaxAccessStatus
bbChanCnfGrpTable
OBJECT-TYPE
The Broadband Channel config table is for a channel on logical interface. There will an entry for each of the channel added on the logical partition of the physical line. Following parameters are needed if the connection is from a PXM user port and policing is enabled. These apply to connection on PXM lines confiured as user port only. PCR/CDVT is used for GCRA1 and SCR/MBS is used for GCRA2 UpcEnable UpcPCR UpcCDVT UpcSCRPolicing for CBR conns. UpcPCR0 UpcCDVT0 for non CBR conns. UpcSCR UpcMBS
1.3.6.1.4.1.351.110.5.2.7.1.1not-accessiblecurrent
bbChanCnfGrpEntry
OBJECT-TYPE
The config table is for logical channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1not-accessiblecurrent
bbChanCnfNum
OBJECT-TYPE
This identifies a channel on the PXM logical interface, used as PXM port.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.1Integer32 (16..4111)read-onlycurrent
bbChanRowStatus
OBJECT-TYPE
This object is used for adding/deleting/modifying entries in the table. add(1) : Adds the entry. delete(2) : Deletes the entry modify(3) : Set this before modifying any entries in the table. Following parameters need to be available before creating the entry: bbChanConnType, bbChanServiceType.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.2INTEGER {add(1), delete(2), modify(3)}read-writecurrent
bbChanConnType
OBJECT-TYPE
This specifies the connection type vpc(1) : Virtual Path Connection vcc(2) : Virtual Channel Connection This object can not be modified once the connection is created.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.3INTEGER {vpc(1), vcc(2)}read-writecurrent
bbChanServiceType
OBJECT-TYPE
This specifies the service type cbr(1) : Constant Bit Rate vbr(2) : Variable Bit Rate abr(3) : Available Bit Rate ubr(4) : Unspecified Bit Rate vbr-rt(5): Variable Bit Rate - Real Time This object can not be modified once the connection is created.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.4INTEGER {cbr(1), vbr(2), abr(3), ubr(4), vbr-rt(5)}read-writecurrent
bbChanConnDesc
OBJECT-TYPE
A string that has been defined to give a descriptive name to the connection.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.5DisplayString (SIZE(0..20))read-writecurrent
bbChanSvcFlag
OBJECT-TYPE
This specifies the connection type svc(1) : SVC connection pvc(2) : PVC connection, used by PAR(Portable Auto Route) spvc(3) : Soft PVC connection, used by PNNI
1.3.6.1.4.1.351.110.5.2.7.1.1.1.6INTEGER {svc(1), pvc(2), spvc(3)}read-writecurrent
bbChanSvcConnId
OBJECT-TYPE
This connection ID is for future use Currently not supported.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.7Integer32read-writecurrent
bbChanIfNum
OBJECT-TYPE
Channel's logical Interface from which traffic of the connection will be received.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.8Integer32 (1..32)read-writecurrent
bbChanVpi
OBJECT-TYPE
VPI for the connection.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.9Integer32 (0..4095)read-writecurrent
bbChanVci
OBJECT-TYPE
VCI for the connection.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.10Integer32 (0..65535)read-writecurrent
bbChanUpcEnable
OBJECT-TYPE
enables/disables UPC for Ingress cells.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.11INTEGER {disable(1), enable(2)}read-writecurrent
bbChanUpcPCR
OBJECT-TYPE
PCR(0+1), Peak Cell Rate, specifies an upper bound on rate at which traffic can be submitted on an ATM connection. This object applies to the First Leaky Bucket for leaving cells with Cell Loss Priority of 0 or 1. . Units: cells per second. . Applicable connection types: UBR, CBR, VBR, ABR . Default: 50 . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 PCR is used for GCRA1.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.12Integer32 (50..1412832)read-writecurrent
bbChanUpcCDVT
OBJECT-TYPE
Compliant Cell Delay Variation. Also known as CDVT(0+1), Cell Delay Variation Tolerance, which specifies the maximum time period for accumulated violations of cell-arrival time parameters. This object applies to the First Leaky bucket for cells with Cell Loss Priority of 0 or 1. . Units: microseconds. . Applicable connection types: UBR, CBR, VBR, ABR . Default: CBR: 10000 Others: 250000
1.3.6.1.4.1.351.110.5.2.7.1.1.1.13Integer32 (1..5000000)read-writecurrent
bbChanUpcSCR
OBJECT-TYPE
SCR, Sustainable Cell Rate, is an upper bound on the conforming average rate of an ATM connection, over time scales which are long relative to those for which the PCR is defined. Enforcement of this bound by the UPC could allow the network to allocate sufficient resources, but less than thos based on the PCR, and still ensure that the performance objectives (e.g., Cell Loss Ratio) can be achieved. . Units: cell per second. . Applicable connection types: . VBR, ABR . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 . Default: 50
1.3.6.1.4.1.351.110.5.2.7.1.1.1.14Integer32 (1..1412832)read-writecurrent
bbChanUpcMBS
OBJECT-TYPE
Maximum Burst Size (MBS). Also known as Compliant Burst Size (CBS). . Units: cells . Applicable connection types: . VBR, ABR . Default: 1000 . Range : 1-5000000
1.3.6.1.4.1.351.110.5.2.7.1.1.1.15Integer32 (1..5000000)read-writecurrent
bbChanGcra1Action
OBJECT-TYPE
GCRA1 Action. 1 = No Action 2 = Tag Untagged cells 3 = Tag untagged cells and discard tagged cells 4 = Discard all (0+1) non-comforming cells.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.16INTEGER {noAction(1), tagCells(2), tagAndDiscard(3), discardAllNonComformCells(4)}read-writecurrent
bbChanGcra2Action
OBJECT-TYPE
GCRA2 Action. 1 = No Action 2 = Tag Untagged cells 3 = Tag untagged cells and discard tagged cells 4 = Discard all (0+1) non-comforming cells.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.17INTEGER {noAction(1), tagCells(2), tagAndDiscard(3), discardAllNonComformCells(4)}read-writecurrent
bbChanUpcSCRPolicing
OBJECT-TYPE
Selects SCR policing for CLP = 0 or all cells.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.18INTEGER {clp0(1), clp0and1(2), off(3)}read-writecurrent
bbChanEfciThreshold
OBJECT-TYPE
Threshold above which EFCI bit is to be set. Default Value is 3/4 of max cell count.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.19Integer32 (0..491520)read-writecurrent
bbChanDiscardOption
OBJECT-TYPE
Enable Frame Discard or CLP Hysteresis.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.20INTEGER {clpHysteresis(1), frameDiscard(2)}read-writecurrent
bbChanFrmDiscardThreshold
OBJECT-TYPE
Ingress Frame Discard Threshold. Valid only when Ingress Frame Discard option is selected.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.21Integer32 (0..491520)read-writecurrent
bbChanClpHiThreshold
OBJECT-TYPE
Ingress CLP High Threshold. Default is 3/4 of max cell count.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.22Integer32 (0..491520)read-writecurrent
bbChanClpLoThreshold
OBJECT-TYPE
Ingress CLP Low Threshold. Valid only when Ingress CLP Hysteresis option is selected. Default Value is 1/2 of max cell count.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.23Integer32 (0..491520)read-writecurrent
bbChanCongstUpdateCode
OBJECT-TYPE
Ingress Channel Congestion Update Code.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.24INTEGER {dontUpdate(1), setCiBit(2), setEfciBit(3), clearEfciBit(4)}read-writecurrent
bbChanMaxCellMemThreshold
OBJECT-TYPE
Maximum number of cells of that connection in the memory. Assuming Total Cell Memory is 512K cells, this is defaulted to half of total size.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.25Integer32 (0..512000)read-writecurrent
bbChanIngrPercentUtil
OBJECT-TYPE
Percentage Utilization of the IngrService Rate. This is used for connection admission control.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.26Integer32 (0..100)read-writecurrent
bbChanEgrPercentUtil
OBJECT-TYPE
Percentage Utilization of the EgrService Rate. This is used for egress bandwidth calculation and connection admission control.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.27Integer32 (0..100)read-writecurrent
bbChanEgrSrvRate
OBJECT-TYPE
Egress service rate - This is used for egress bandwidth calculation and for connection admission control. The actual value depends on the speed of the logical interface.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.28Integer32 (1..1412832)read-writecurrent
bbChanOvrSubOvrRide
OBJECT-TYPE
Channel Over Subscrive Override This MIB variable allows one to add a new connection on a port even if it is over subscribed.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.29INTEGER {disable(1), enable(2)}read-writecurrent
bbChanLocalVpi
OBJECT-TYPE
The VPI value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.30Integer32 (0..4095)read-onlycurrent
bbChanLocalVci
OBJECT-TYPE
The VCI value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.31Integer32 (0..65535)read-onlycurrent
bbChanLocalNsapAddr
OBJECT-TYPE
The Near End NSAP Address value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.32IfNsapAddressread-writecurrent
bbChanRemoteVpi
OBJECT-TYPE
The VPI value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.33Integer32 (0..4095)read-writecurrent
bbChanRemoteVci
OBJECT-TYPE
The VCI value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.34Integer32 (0..65535)read-writecurrent
bbChanRemoteNsapAddr
OBJECT-TYPE
The Far End NSAP Address value for this channel.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.35IfNsapAddressread-writecurrent
bbChanMaster
OBJECT-TYPE
This is used by the PXM switch platform module, to determine if this endpoint ia master or slave.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.36INTEGER {master(1), slave(2), unknown(3)}read-writecurrent
bbChanRtePriority
OBJECT-TYPE
This is also known as class of service, it is used by PXM to determine how important this connection is when selecting connections to route.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.37Integer32 (1..15)read-writecurrent
bbChanMaxCost
OBJECT-TYPE
Maximum allowed cost. It is related to Cost Based Routing. This is used by PXM so that it won't choose a path with a cost greater than this configured level.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.38Integer32 (1..65535)read-writecurrent
bbChanRestrictTrkType
OBJECT-TYPE
Restricted trunk type for routind, used by PXM. It specifies that the connection either cannot be routed over satellite trunks or terrestrial trunks, or it can be on any type of trunk.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.39INTEGER {noRestriction(1), terrestrialTrunk(2), satelliteTrunk(3)}read-writecurrent
bbChanTestType
OBJECT-TYPE
The chanTestType starts testing the continuity or delay of a connection. It sends specific cell patterns toward the network and the terminating end of this connection has to be an AXIS or ASI of a BPX in order for this test to be working. The receiving node would loop back when it receives these cells. The test should be done in about couple of seconds. testcon(1) : The testcon tests the continuity of the connection and testdelay uses the same test except that it measures for delay through the network. To test the delay follow this procedure: a- set chanTestType to testdelay b- read chanTestState till it is Pass or Fail c- Read chanTestResult for the delay if it is Pass * Note that the chanTestType would go back to notest when the test is completed To test the continuity follow this procedure: a- set chanTestType to testcon b- read chanTestState till it is Pass or Fail * Note that the chanTestType would go back to notest when the test is completed You CAN NOT select 2 tests back to back, you have to select one and wait for the result and then start the other one.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.40INTEGER {testcon(1), testdelay(2), notest(3)}read-writecurrent
bbChanTestState
OBJECT-TYPE
This object provides the state of the test performed on a connection. When you add a connection then the chanTestState becomes notinprogress and when you select any test, it would go to inprogress state and after it completes the test, it will go to failed or passed state. 1 = Passed 2 = Failed 3 = In Progress 4 = Not In Progress
1.3.6.1.4.1.351.110.5.2.7.1.1.1.41INTEGER {passed(1), failed(2), inprogress(3), notinprogress(4)}read-onlycurrent
bbChanTestResult
OBJECT-TYPE
This is round trip delay in milliseconds. When you select testdelay option for the chanTestType, the result of the test that is measured in milliseconds can be read in chanTestResult.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.42Integer32 (1..65535)read-onlycurrent
bbChanTestTypeCPESide
OBJECT-TYPE
The chanTestType starts testing the segment continuity of a connection. It sends OAM Segment loopback cell towards port side (CPE) The CPE would loop back the cell To test the continuity follow this procedure: a- set chanTestTypeCPEside to testconseg b- read chanTestState till it is Pass or Fail *Note that the chanTestType would go back to notest when the test is completed.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.43INTEGER {testconseg(1), notest(2)}read-writecurrent
bbChanTestStateCPESide
OBJECT-TYPE
This shows the state of the test When you add a connection then the chanTestState becomes notinprogress and when you select any test, it would go to inprogress state and after it completes the test, it will go to failed or passed state. 1 = Passed 2 = Failed 3 = In Progress 4 = Not In Progress
1.3.6.1.4.1.351.110.5.2.7.1.1.1.44INTEGER {passed(1), failed(2), inprogress(3), notinprogress(4)}read-onlycurrent
bbConnVpcFlag
OBJECT-TYPE
This represents the connection type, used for PXM to identify VPC/VCC.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.45INTEGER {vpc(1), vcc(2)}read-writecurrent
bbConnServiceType
OBJECT-TYPE
This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 4 ==> Unspecified Bit Rate 6 ==> Available Bit Rate ( standard ) 8 ==> Variable Bit Rate - Real-Time Note that this is used by PXM card, Also to make it compatible with existing AUSM MIB definition, value 3 is not used. foresight ABR is not supported in PXM , i.e Virtual Service Module
1.3.6.1.4.1.351.110.5.2.7.1.1.1.46INTEGER {cbr(1), vbr(2), ubr(4), abrstd(6), vbrrt(8)}read-writecurrent
bbConnPCR
OBJECT-TYPE
Peak cell rate, could be derived from the end point parameter
1.3.6.1.4.1.351.110.5.2.7.1.1.1.47Integer32read-writecurrent
bbConnSCR
OBJECT-TYPE
Sustained cell rate, could be derived from the end point parameter
1.3.6.1.4.1.351.110.5.2.7.1.1.1.48Integer32read-writecurrent
bbConnPercentUtil
OBJECT-TYPE
This is the expected long-term utilization of the channel by this end-point.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.49Integer32 (0..100)read-writecurrent
bbRemoteConnPCR
OBJECT-TYPE
Peak cell rate of the other end, if not set, will be set to the same as local end PCR (bbChanUpcPCR). However, note that if the PCRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end PCR.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.50Integer32read-writecurrent
bbRemoteConnSCR
OBJECT-TYPE
Sustained cell rate of the other end, if not set, will be set to the same as local end SCR (bbChanUpcSCR). However, note that if the PCRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end SCR.
1.3.6.1.4.1.351.110.5.2.7.1.1.1.51Integer32read-writecurrent
bbRemoteConnPercentUtil
OBJECT-TYPE
This is the expected long-term utilization of the channel by this end-point. If this is not specified in the connection setup request, it'll be defaulted to 100 percent
1.3.6.1.4.1.351.110.5.2.7.1.1.1.52Integer32 (0..100)read-writecurrent
bbChanUpcMCR
OBJECT-TYPE
SCR, Sustainable Cell Rate, is an upper bound on the conforming average rate of an ATM connection, over time scales which are long relative to those for which the PCR is defined. Enforcement of this bound by the UPC could allow the network to allocate sufficient resources, but less than thos based on the PCR, and still ensure that the performance objectives (e.g., Cell Loss Ratio) can be achieved. . Units: cell per second. . Applicable connection types: . ABR . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 . Default: 50
1.3.6.1.4.1.351.110.5.2.7.1.1.1.53Integer32 (1..1412832)read-writecurrent
bbChanNumNextAvailable
OBJECT-TYPE
This variable contains the next unused channel number of the possible 4096 . This number can be used in channel config table. ChanNumNextAvailable gets updated whenever this number is used to create a new logical channel. Value 0 for this variable indicates that no more channels are available.
1.3.6.1.4.1.351.110.5.2.7.1.2Integer32 (16..4111)read-onlycurrent
bbChanVpIdNextAvailable
OBJECT-TYPE
This in only valid for a Service Module, will NOT be used in PXM. This variable contains the next unused local VPId of the possible 1 to 4095. This number can be used in channel config table. It gets updated if the number is used to create a new vp connection. The max. no. of VP conn.s is limited to the VPI range configured for this logical interface. Value of 0 for this variable indicates that no more vp connections are available
1.3.6.1.4.1.351.110.5.2.7.1.3Integer32 (1..4095)read-onlycurrent
bbChanStateGrpTable
OBJECT-TYPE
The Broadband Channel state table is for a channel on logical interface. There will an entry for each of the channel added on the logical partition of the physical line.
1.3.6.1.4.1.351.110.5.2.7.2.1not-accessiblecurrent
bbChanStateGrpEntry
OBJECT-TYPE
The state table is for logical channel. The available number of channels on the broadband interface (user ports) on the PXM card is restricted to 4K. The PXM card has 2 Queue Engines ( QE0 and QE1). Current calculations allow 31954 GLCNs on QE0, and 31748 GLCNs on QE1.
1.3.6.1.4.1.351.110.5.2.7.2.1.1not-accessiblecurrent
bbChanStateNum
OBJECT-TYPE
Refers to the logical channel number.
1.3.6.1.4.1.351.110.5.2.7.2.1.1.1Integer32 (16..4111)read-onlycurrent
bbChanState
OBJECT-TYPE
This variable indicates the state of the VC (channel).
1.3.6.1.4.1.351.110.5.2.7.2.1.1.2INTEGER {notconfigured(1), normal(2), alarm(3)}read-onlycurrent
bbChanEgrXmtState
OBJECT-TYPE
Indicates the status of port transmit(Egress).
1.3.6.1.4.1.351.110.5.2.7.2.1.1.3INTEGER {other(1), normal(2), sendingAis(3), sendingFerf(4)}read-onlycurrent
bbChanIngrRcvState
OBJECT-TYPE
indicates the status of port receive(Ingress).
1.3.6.1.4.1.351.110.5.2.7.2.1.1.4INTEGER {other(1), normal(2), receivingAis(3), receivingFerf(4), alarm(5)}read-onlycurrent
cwbAtmConnMIBConformance
OBJECT-IDENTITY
1.3.6.1.4.1.351.150.35.2
cwbAtmConnMIBGroups
OBJECT-IDENTITY
1.3.6.1.4.1.351.150.35.2.1
cwbAtmConnMIBCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.351.150.35.2.2

Conformance

NameOIDStatus
cwbAtmConnGroup
OBJECT-GROUP
A collection of objects providing information applicable to an ATM Connection on broad band interfaces.
1.3.6.1.4.1.351.150.35.2.1.1current
cwbAtmConnStateGroup
OBJECT-GROUP
A collection of objects related to state of ATM Connections on Broad band interface.
1.3.6.1.4.1.351.150.35.2.1.2current
cwbAtmConnGeneralGroup
OBJECT-GROUP
A collection of objects related to next available channeli number and next available VPI value of connections supported.
1.3.6.1.4.1.351.150.35.2.1.3current
cwbAtmConnCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities which support Frame realy connection MIB.
1.3.6.1.4.1.351.150.35.2.2.1current