XYLAN-CSM-MIB

File: XYLAN-CSM-MIB.mib (257812 bytes)

Imported modules

RFC1213-MIB RFC-1212 RFC1155-SMI
XYLAN-BASE-MIB

Imported symbols

DisplayString ifIndex OBJECT-TYPE
IpAddress Counter xylanCsmArch

Defined Types

AtmxTrafficDescrParamIndex  
INTEGER 0..2147483647    

AtmxInterfaceConfEntry  
SEQUENCE    
  atmxInterfaceSlotIndex INTEGER
  atmxInterfacePortIndex INTEGER
  atmxInterfaceMaxVpcs INTEGER
  atmxInterfaceMaxVccs INTEGER
  atmxInterfaceConfVpcs INTEGER
  atmxInterfaceConfVccs INTEGER
  atmxInterfaceMaxActiveVpiBits INTEGER
  atmxInterfaceMaxActiveVciBits INTEGER
  atmxInterfaceIlmiVpi INTEGER
  atmxInterfaceIlmiVci INTEGER
  atmxInterfaceAddressType INTEGER

AtmxTrafficDescrParamEntry  
SEQUENCE    
  atmxTrafficDescrParamIndex AtmxTrafficDescrParamIndex
  atmxTrafficDescrType INTEGER
  atmxTrafficDescrParam1 INTEGER
  atmxTrafficDescrParam2 INTEGER
  atmxTrafficDescrParam3 INTEGER
  atmxTrafficDescrParam4 INTEGER
  atmxTrafficDescrParam5 INTEGER
  atmxTrafficQoSClass INTEGER
  atmxTrafficDescrRowStatus INTEGER

AtmxVplEntry  
SEQUENCE    
  atmxVplSlotIndex INTEGER
  atmxVplPortIndex INTEGER
  atmxVplVpi INTEGER
  atmxVplAdminStatus INTEGER
  atmxVplOperStatus INTEGER
  atmxVplLastChange DisplayString
  atmxVplReceiveTrafficDescrIndex AtmxTrafficDescrParamIndex
  atmxVplTransmitTrafficDescrIndex AtmxTrafficDescrParamIndex
  atmxVplCrossConnectIdentifier INTEGER
  atmxVplRowStatus INTEGER
  atmxVplBidirect INTEGER

AtmxVclEntry  
SEQUENCE    
  atmxVclSlotIndex INTEGER
  atmxVclPortIndex INTEGER
  atmxVclVpi INTEGER
  atmxVclVci INTEGER
  atmxVclAdminStatus INTEGER
  atmxVclOperStatus INTEGER
  atmxVclLastChange DisplayString
  atmxVclReceiveTrafficDescrIndex AtmxTrafficDescrParamIndex
  atmxVclTransmitTrafficDescrIndex AtmxTrafficDescrParamIndex
  atmxVccAalType INTEGER
  atmxVccAal5CpcsTransmitSduSize INTEGER
  atmxVccAal5CpcsReceiveSduSize INTEGER
  atmxVccAal5EncapsType INTEGER
  atmxVclCrossConnectIdentifier INTEGER
  atmxVclRowStatus INTEGER
  atmxVclBidirect INTEGER

AtmxVpCrossConnectEntry  
SEQUENCE    
  atmxVpCrossConnectIndex INTEGER
  atmxVpCrossConnectLowSlotIndex INTEGER
  atmxVpCrossConnectLowPortIndex INTEGER
  atmxVpCrossConnectLowVpi INTEGER
  atmxVpCrossConnectHighSlotIndex INTEGER
  atmxVpCrossConnectHighPortIndex INTEGER
  atmxVpCrossConnectHighVpi INTEGER
  atmxVpCrossConnectAdminStatus INTEGER
  atmxVpCrossConnectL2HOperStatus INTEGER
  atmxVpCrossConnectH2LOperStatus INTEGER
  atmxVpCrossConnectL2HLastChange DisplayString
  atmxVpCrossConnectH2LLastChange DisplayString
  atmxVpCrossConnectRowStatus INTEGER

AtmxSvcVpCrossConnectEntry  
SEQUENCE    
  atmxSvcVpCrossConnectLowSlotIndex INTEGER
  atmxSvcVpCrossConnectLowPortIndex INTEGER
  atmxSvcVpCrossConnectLowVpi INTEGER
  atmxSvcVpCrossConnectHighSlotIndex INTEGER
  atmxSvcVpCrossConnectHighPortIndex INTEGER
  atmxSvcVpCrossConnectHighVpi INTEGER
  atmxSvcVpCrossConnectLowTDIndex INTEGER
  atmxSvcVpCrossConnectHighTDIndex INTEGER
  atmxSvcVpCrossConnectCreationTime DisplayString
  atmxSvcVpCrossConnectRowStatus INTEGER

AtmxVcCrossConnectEntry  
SEQUENCE    
  atmxVcCrossConnectIndex INTEGER
  atmxVcCrossConnectLowSlotIndex INTEGER
  atmxVcCrossConnectLowPortIndex INTEGER
  atmxVcCrossConnectLowVpi INTEGER
  atmxVcCrossConnectLowVci INTEGER
  atmxVcCrossConnectHighSlotIndex INTEGER
  atmxVcCrossConnectHighPortIndex INTEGER
  atmxVcCrossConnectHighVpi INTEGER
  atmxVcCrossConnectHighVci INTEGER
  atmxVcCrossConnectAdminStatus INTEGER
  atmxVcCrossConnectL2HOperStatus INTEGER
  atmxVcCrossConnectH2LOperStatus INTEGER
  atmxVcCrossConnectL2HLastChange DisplayString
  atmxVcCrossConnectH2LLastChange DisplayString
  atmxVcCrossConnectRowStatus INTEGER

AtmxSvcVcCrossConnectEntry  
SEQUENCE    
  atmxSvcVcCrossConnectLowSlotIndex INTEGER
  atmxSvcVcCrossConnectLowPortIndex INTEGER
  atmxSvcVcCrossConnectLowVpi INTEGER
  atmxSvcVcCrossConnectLowVci INTEGER
  atmxSvcVcCrossConnectHighSlotIndex INTEGER
  atmxSvcVcCrossConnectHighPortIndex INTEGER
  atmxSvcVcCrossConnectHighVpi INTEGER
  atmxSvcVcCrossConnectHighVci INTEGER
  atmxSvcVcCrossConnectLowTDIndex INTEGER
  atmxSvcVcCrossConnectHighTDIndex INTEGER
  atmxSvcVcCrossConnectCreationTime DisplayString
  atmxSvcVcCrossConnectRowStatus INTEGER

XylnAtmInterfaceConfEntry  
SEQUENCE    
  xylnatmInterfaceSlotIndex INTEGER
  xylnatmInterfacePortIndex INTEGER
  xylnatmInterfaceDescription DisplayString
  xylnatmInterfaceTransType INTEGER
  xylnatmInterfaceType INTEGER
  xylnatmInterfaceMediaType INTEGER
  xylnatmInterfaceAtmAddress DisplayString
  xylnatmInterfacePortMode INTEGER
  xylnatmInterfaceOperStatus INTEGER
  xylnatmInterfaceQsaalStatus INTEGER
  xylnatmInterfaceIlmiStatus INTEGER
  xylnatmInterfaceTpRedirect INTEGER
  xylnatmInterfaceCutOverSlot INTEGER
  xylnatmInterfaceCutOverPort INTEGER
  xylnatmInterfaceClearPortStats INTEGER
  xylnatmInterfaceClearChanStats INTEGER
  xylnatmInterfaceClearSlotStats INTEGER
  xylnatmInterfaceTransmissionType INTEGER
  xylnatmInterfaceIlmiState INTEGER
  xylnatmInterfaceTimingMode INTEGER
  xylnatmInterfaceLocalSrc INTEGER
  xylnatmInterfaceUniVersion INTEGER

XylnatmILMIConfEntry  
SEQUENCE    
  xylnatmILMIConfSlot INTEGER
  xylnatmILMIConfPort INTEGER
  xylnatmILMIConfInstance INTEGER
  xylnatmILMIConfILMIEnable INTEGER
  xylnatmILMIConfILMIPollEnable INTEGER
  xylnatmILMIConfAutoCfgEnable INTEGER
  xylnatmILMIConfAutoCfgStatus INTEGER
  xylnatmILMIConfAutoCfgTrigg INTEGER
  xylnatmILMIConfAutoCfgDfltIf INTEGER
  xylnatmILMIConfAutoCfgDfltSigVer INTEGER
  xylnatmILMIConfAutoCfgCurIf INTEGER
  xylnatmILMIConfAutoCfgCurSigVer INTEGER
  xylnatmILMIConfAutoCfgCurILMIVer INTEGER
  xylnatmILMIConfPeerUniType INTEGER
  xylnatmILMIConfPeerUniVer INTEGER
  xylnatmILMIConfPeerDevType INTEGER
  xylnatmILMIConfPeerNNISigVer INTEGER
  xylnatmILMIConfPeerILMIVer INTEGER

XylnatmInterfaceStatEntry  
SEQUENCE    
  xylnatmInterfaceStatSlotIndex INTEGER
  xylnatmInterfaceStatPortIndex INTEGER
  xylnatmInterfaceStatRxCells Counter
  xylnatmInterfaceStatRxClp0Cells Counter
  xylnatmInterfaceStatRxClp1Cells Counter
  xylnatmInterfaceStatTxCells Counter
  xylnatmInterfaceStatMarkEfciCells Counter
  xylnatmInterfaceStatMarkGcraCells Counter
  xylnatmInterfaceStatTotalDiscardCells Counter
  xylnatmInterfaceStatDxCongClp0Cells Counter
  xylnatmInterfaceStatDxCongClp1Cells Counter
  xylnatmInterfaceStatDxGcraClp0Cells Counter
  xylnatmInterfaceStatDxGcraClp1Cells Counter
  xylnatmInterfaceStatDxGcrabClp0Cells Counter
  xylnatmInterfaceStatDxGcrabClp1Cells Counter
  xylnatmInterfaceStatUnknownVpVcCells Counter
  xylnatmInterfaceStatUnknownVpiCells Counter
  xylnatmInterfaceStatUnknownVciCells Counter
  xylnatmInterfaceStatUniType INTEGER
  xylnatmInterfaceStatUniVersion INTEGER
  xylnatmInterfaceStatRemainingRxBandwidth Counter
  xylnatmInterfaceStatRemainingTxBandwidth Counter

XylnatmVclEntry  
SEQUENCE    
  xylnatmVclSlotIndex INTEGER
  xylnatmVclPortIndex INTEGER
  xylnatmVclVpi INTEGER
  xylnatmVclVci INTEGER
  xylnatmVclConnectionDescr DisplayString
  xylnatmVclChanType INTEGER
  xylnatmVclTransportPriority INTEGER
  xylnatmVclUserPriority INTEGER
  xylnatmVclStatsMode INTEGER
  xylnatmVclPrTrackPortBase INTEGER
  xylnatmVclPrTrackPort1 INTEGER
  xylnatmVclPrTrackPort2 INTEGER
  xylnatmVclPrTrackPort3 INTEGER
  xylnatmVclAltTrackPortBase INTEGER
  xylnatmVclAltTrackPort1 INTEGER
  xylnatmVclAltTrackPort2 INTEGER
  xylnatmVclAltTrackPort3 INTEGER
  xylnatmVclLgclChanRedirect INTEGER
  xylnatmVclAAL5Discard INTEGER
  xylnatmVclF4F5SegEndpt INTEGER
  xylnatmVclF4F5CopySeg INTEGER
  xylnatmVclF4F5End2EndEndpt INTEGER
  xylnatmVclF4F5CopyEnd2End INTEGER
  xylnatmVclOamEndpt INTEGER
  xylnatmVclOamCopy INTEGER
  xylnatmVclRmFwdEndpt INTEGER
  xylnatmVclRmFwdCopy INTEGER
  xylnatmVclRmFwdGcraAdv INTEGER
  xylnatmVclRmBkwdEndpt INTEGER
  xylnatmVclRmBkwdCopy INTEGER
  xylnatmVclRmBkwdGcraAdv INTEGER
  xylnatmVclRmDiscard INTEGER
  xylnatmVclGcraAPoliceMode INTEGER
  xylnatmVclGcraBPoliceMode INTEGER
  xylnatmVclMcGroupId INTEGER
  xylnatmVclMcIngressEgress INTEGER

XylnatmVclStatEntry  
SEQUENCE    
  xylnatmVclStatSlotIndex INTEGER
  xylnatmVclStatPortIndex INTEGER
  xylnatmVclStatVpi INTEGER
  xylnatmVclStatVci INTEGER
  xylnatmVclStatRxCells Counter
  xylnatmVclStatTxCells Counter
  xylnatmVclStatRxClp0Cells Counter
  xylnatmVclStatRxClp1Cells Counter
  xylnatmVclStatDxCongClp0Cells Counter
  xylnatmVclStatDxCongClp1Cells Counter
  xylnatmVclStatDxGcraClp0Cells Counter
  xylnatmVclStatDxGcraClp1Cells Counter
  xylnatmVclStatDxGcraBClp0Cells Counter
  xylnatmVclStatDxGcraBClp1Cells Counter

XylnatmVplEntry  
SEQUENCE    
  xylnatmVplSlotIndex INTEGER
  xylnatmVplPortIndex INTEGER
  xylnatmVplVpi INTEGER
  xylnatmVplConnectionDescr DisplayString
  xylnatmVplChanType INTEGER
  xylnatmVplTransportPriority INTEGER
  xylnatmVplUserPriority INTEGER
  xylnatmVplStatsMode INTEGER
  xylnatmVplPrTrackPortBase INTEGER
  xylnatmVplPrTrackPort1 INTEGER
  xylnatmVplPrTrackPort2 INTEGER
  xylnatmVplPrTrackPort3 INTEGER
  xylnatmVplAltTrackPortBase INTEGER
  xylnatmVplAltTrackPort1 INTEGER
  xylnatmVplAltTrackPort2 INTEGER
  xylnatmVplAltTrackPort3 INTEGER
  xylnatmVplLgclChanRedirect INTEGER
  xylnatmVplAAL5Discard INTEGER
  xylnatmVplF4F5SegEndpt INTEGER
  xylnatmVplF4F5CopySeg INTEGER
  xylnatmVplF4F5End2EndEndpt INTEGER
  xylnatmVplF4F5CopyEnd2End INTEGER
  xylnatmVplOamEndpt INTEGER
  xylnatmVplOamCopy INTEGER
  xylnatmVplRmFwdEndpt INTEGER
  xylnatmVplRmFwdCopy INTEGER
  xylnatmVplRmFwdGcraAdv INTEGER
  xylnatmVplRmBkwdEndpt INTEGER
  xylnatmVplRmBkwdCopy INTEGER
  xylnatmVplRmBkwdGcraAdv INTEGER
  xylnatmVplRmDiscard INTEGER
  xylnatmVplGcraAPoliceMode INTEGER
  xylnatmVplGcraBPoliceMode INTEGER
  xylnatmVplMcGroupId INTEGER
  xylnatmVplMcIngressEgress INTEGER

XylnatmVplStatEntry  
SEQUENCE    
  xylnatmVplStatSlotIndex INTEGER
  xylnatmVplStatPortIndex INTEGER
  xylnatmVplStatVpi INTEGER
  xylnatmVplStatRxCells Counter
  xylnatmVplStatTxCells Counter
  xylnatmVplStatRxClp0Cells Counter
  xylnatmVplStatRxClp1Cells Counter
  xylnatmVplStatDxCongClp0Cells Counter
  xylnatmVplStatDxCongClp1Cells Counter
  xylnatmVplStatDxGcraClp0Cells Counter
  xylnatmVplStatDxGcraClp1Cells Counter
  xylnatmVplStatDxGcraBClp0Cells Counter
  xylnatmVplStatDxGcraBClp1Cells Counter

XylnatmVpCrossConnectEntry  
SEQUENCE    
  xylnatmVpCrossConnectLowSlotIndex INTEGER
  xylnatmVpCrossConnectLowPortIndex INTEGER
  xylnatmVpCrossConnectLowVpi INTEGER
  xylnatmVpCrossConnectHighSlotIndex INTEGER
  xylnatmVpCrossConnectHighPortIndex INTEGER
  xylnatmVpCrossConnectHighVpi INTEGER
  xylnatmVpCrossConnectConnectionId INTEGER
  xylnatmVpCrossConnectLowRxTrafficDescrIndex INTEGER
  xylnatmVpCrossConnectLowTxTrafficDescrIndex INTEGER
  xylnatmVpCrossConnectMCastEnable INTEGER
  xylnatmVpCrossConnectL2HLastChange DisplayString
  xylnatmVpCrossConnectH2LLastChange DisplayString
  xylnatmVpCrossConnectL2HOperStatus INTEGER
  xylnatmVpCrossConnectH2LOperStatus INTEGER
  xylnatmVpCrossConnectVcType INTEGER
  xylnatmVpCrossConnectPvcIdentifier INTEGER
  xylnatmVpCrossConnectRowStatus INTEGER

XylnatmVcCrossConnectEntry  
SEQUENCE    
  xylnatmVcCrossConnectLowSlotIndex INTEGER
  xylnatmVcCrossConnectLowPortIndex INTEGER
  xylnatmVcCrossConnectLowVpi INTEGER
  xylnatmVcCrossConnectLowVci INTEGER
  xylnatmVcCrossConnectHighSlotIndex INTEGER
  xylnatmVcCrossConnectHighPortIndex INTEGER
  xylnatmVcCrossConnectHighVpi INTEGER
  xylnatmVcCrossConnectHighVci INTEGER
  xylnatmVcCrossConnectConnectionId INTEGER
  xylnatmVcCrossConnectLowRxTrafficDescrIndex INTEGER
  xylnatmVcCrossConnectLowTxTrafficDescrIndex INTEGER
  xylnatmVcCrossConnectMCastEnable INTEGER
  xylnatmVcCrossConnectL2HLastChange DisplayString
  xylnatmVcCrossConnectH2LLastChange DisplayString
  xylnatmVcCrossConnectL2HOperStatus INTEGER
  xylnatmVcCrossConnectH2LOperStatus INTEGER
  xylnatmVcCrossConnectVcType INTEGER
  xylnatmVcCrossConnectPvcIdentifier INTEGER
  xylnatmVcCrossConnectRowStatus INTEGER

XylnatmVplModEntry  
SEQUENCE    
  xylnatmVplModSlotIndex INTEGER
  xylnatmVplModPortIndex INTEGER
  xylnatmVplModVplVpi INTEGER
  xylnatmVplModDestSlotIndex INTEGER
  xylnatmVplModDestPortIndex INTEGER
  xylnatmVplModDestVplVpi INTEGER
  xylnatmVplModDestStatus INTEGER

XylnatmVclModEntry  
SEQUENCE    
  xylnatmVclModSlotIndex INTEGER
  xylnatmVclModPortIndex INTEGER
  xylnatmVclModVclVpi INTEGER
  xylnatmVclModVclVci INTEGER
  xylnatmVclModDestSlotIndex INTEGER
  xylnatmVclModDestPortIndex INTEGER
  xylnatmVclModDestVclVpi INTEGER
  xylnatmVclModDestVclVci INTEGER
  xylnatmVclModDestStatus INTEGER

XylnatmClockingxCtrlEntry  
SEQUENCE    
  xylnatmClockingxCtrlBusLine INTEGER
  xylnatmClockingxCtrlSrcLevel INTEGER
  xylnatmClockingxSrcOperState INTEGER
  xylnatmClockingxSrcType INTEGER
  xylnatmClockingxCtrlSlot INTEGER
  xylnatmClockingxCtrlPort INTEGER

XylnatmTrafficShaperConfEntry  
SEQUENCE    
  xylnatmTrafficShaperConfSlotIndex INTEGER
  xylnatmTrafficShaperConfPortIndex INTEGER
  xylnatmTrafficShaperConfTsNumIndex INTEGER
  xylnatmTrafficShaperConfCDV INTEGER
  xylnatmTrafficShaperConfPCR INTEGER
  xylnatmTrafficShaperConfSCR INTEGER
  xylnatmTrafficShaperConfMBS INTEGER

XylnatmTrafficShaperMemEntry  
SEQUENCE    
  xylnatmTrafficShaperMemSlotIndex INTEGER
  xylnatmTrafficShaperMemPortIndex INTEGER
  xylnatmTrafficShaperMemTsNumIndex INTEGER
  xylnatmTrafficShaperMemVpiNumIndex INTEGER
  xylnatmTrafficShaperMemVciNumIndex INTEGER
  xylnatmTrafficShaperMemVpiOper INTEGER

Defined Values

xylanCsmMIB 1.1.800.2.9.1
OBJECT IDENTIFIER    

atmxVplGroup 1.1.800.2.9.1.1
OBJECT IDENTIFIER    

atmxInterfaceConfGroup 1.1.800.2.9.1.2
OBJECT IDENTIFIER    

atmxVclGroup 1.1.800.2.9.1.3
OBJECT IDENTIFIER    

xylnatmInterfaceConfGroup 1.1.800.2.9.1.4
OBJECT IDENTIFIER    

atmxVpCrossConnectGroup 1.1.800.2.9.1.5
OBJECT IDENTIFIER    

xylnatmInterfaceStatGroup 1.1.800.2.9.1.6
OBJECT IDENTIFIER    

atmxVcCrossConnectGroup 1.1.800.2.9.1.7
OBJECT IDENTIFIER    

atmxTrafficDescrGroup 1.1.800.2.9.1.8
OBJECT IDENTIFIER    

xylnatmVplGroup 1.1.800.2.9.1.9
OBJECT IDENTIFIER    

xylnatmVclGroup 1.1.800.2.9.1.10
OBJECT IDENTIFIER    

xylnatmVplStatGroup 1.1.800.2.9.1.11
OBJECT IDENTIFIER    

xylnatmVclStatGroup 1.1.800.2.9.1.12
OBJECT IDENTIFIER    

xylnatmVcCrossConnectGroup 1.1.800.2.9.1.13
OBJECT IDENTIFIER    

xylnatmVpCrossConnectGroup 1.1.800.2.9.1.14
OBJECT IDENTIFIER    

xylnatmVclModGroup 1.1.800.2.9.1.15
OBJECT IDENTIFIER    

xylnatmVplModGroup 1.1.800.2.9.1.16
OBJECT IDENTIFIER    

xylnatmClockingxCtrlGroup 1.1.800.2.9.1.17
OBJECT IDENTIFIER    

xylnatmTrafficShaperConfGroup 1.1.800.2.9.1.18
OBJECT IDENTIFIER    

xylnatmTrafficShaperMemGroup 1.1.800.2.9.1.19
OBJECT IDENTIFIER    

atmxInterfaceConfTable 1.1.800.2.9.1.2.1
This table contains ATM local interface configuration parameters, one entry per ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxInterfaceConfEntry

atmxInterfaceConfEntry 1.1.800.2.9.1.2.1.1
This list contains ATM interface configuration parameters and state variables.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxInterfaceConfEntry  

atmxInterfaceSlotIndex 1.1.800.2.9.1.2.1.1.1
The slot number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxInterfacePortIndex 1.1.800.2.9.1.2.1.1.2
The slot number for the CSM board
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

atmxInterfaceMaxVpcs 1.1.800.2.9.1.2.1.1.3
The maximum number of VPCs (PVCs and SVCs) supported at this ATM interface. At the ATM UNI, the maximum number of VPCs (PVCs and SVCs) ranges from 0 to 256 only.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4096  

atmxInterfaceMaxVccs 1.1.800.2.9.1.2.1.1.4
The maximum number of VCCs (PVCs and SVCs) supported at this ATM interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65536  

atmxInterfaceConfVpcs 1.1.800.2.9.1.2.1.1.5
The number of VPCs (PVCs and SVCs) configured for use at this ATM interface. At the ATM UNI, the configured number of VPCs (PVCs and SVCs) can range from 0 to 256 only.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4096  

atmxInterfaceConfVccs 1.1.800.2.9.1.2.1.1.6
The number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65536  

atmxInterfaceMaxActiveVpiBits 1.1.800.2.9.1.2.1.1.7
The maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum number of active VPI bits configured for use ranges from 0 to 8 only.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..12  

atmxInterfaceMaxActiveVciBits 1.1.800.2.9.1.2.1.1.8
The maximum number of active VCI bits configured for use at this ATM interface.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..16  

atmxInterfaceIlmiVpi 1.1.800.2.9.1.2.1.1.9
The VPI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..255  

atmxInterfaceIlmiVci 1.1.800.2.9.1.2.1.1.10
The VCI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

atmxInterfaceAddressType 1.1.800.2.9.1.2.1.1.11
The type of primary ATM address configured for use at this ATM interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER private(1), nsapE164(2), nativeE164(3), other(4)  

atmxTrafficDescrParamTable 1.1.800.2.9.1.8.1
This table contains information on ATM traffic descriptor type and the associated parameters.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxTrafficDescrParamEntry

atmxTrafficDescrParamEntry 1.1.800.2.9.1.8.1.1
This list contains ATM traffic descriptor type and the associated parameters.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxTrafficDescrParamEntry  

atmxTrafficDescrParamIndex 1.1.800.2.9.1.8.1.1.1
This object is used by the virtual link table (i.e., VPL or VCL table) to identify the row of this table. For NMS to create a specific entry, the index is limited from 1-16000. Instances greater than 16000 are created internally by the switch for use by SVC's etc
Status: mandatory Access: read-only
OBJECT-TYPE    
  AtmxTrafficDescrParamIndex  

atmxTrafficDescrType 1.1.800.2.9.1.8.1.1.2
The value of this object identifies the type of ATM traffic descriptor. The type may indicate no traffic descriptor or traffic descriptor with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmxTrafficDescrParam1 atmxTrafficDescrParam2 atmxTrafficDescrParam3 atmxTrafficDescrParam4 atmxTrafficDescrParam5.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER atmxNoTrafficDescriptor(1), atmxNoClpNoScr(2), atmxClpNoTaggingNoScr(3), atmxClpTaggingNoScr(4), atmxNoClpScr(5), atmxClpNoTaggingScr(6), atmxClpTaggingScr(7)  

atmxTrafficDescrParam1 1.1.800.2.9.1.8.1.1.3
The first parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

atmxTrafficDescrParam2 1.1.800.2.9.1.8.1.1.4
The second parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

atmxTrafficDescrParam3 1.1.800.2.9.1.8.1.1.5
The third parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

atmxTrafficDescrParam4 1.1.800.2.9.1.8.1.1.6
The fourth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

atmxTrafficDescrParam5 1.1.800.2.9.1.8.1.1.7
The fifth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

atmxTrafficQoSClass 1.1.800.2.9.1.8.1.1.8
The value of this object identifies the QoS Class. Four Service classes have been specified in the ATM Forum UNI Specification: Service Class A: Constant bit rate video and Circuit emulation Service Class B: Variable bit rate video/audio Service Class C: Connection-oriented data Service Class D: Connectionless data Four QoS classes numbered 1, 2, 3, and 4 have been specified with the aim to support service classes A, B, C, and D respectively. An unspecified QoS Class numbered `0' is used for best effort traffic.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..255  

atmxTrafficDescrRowStatus 1.1.800.2.9.1.8.1.1.9
This object is used to create a new row or modify or delete an existing row in this table. An entry cannot be deleted or modified if any VC/VP is using the row
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

atmxVplTable 1.1.800.2.9.1.1.1
The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxVplEntry

atmxVplEntry 1.1.800.2.9.1.1.1.1
An entry in the VPL table. This entry is used to model a bi-directional VPL. To create a VPL at an ATM interface, either of the following procedures are used: Negotiated VPL establishment (1) The management application creates a VPL entry in the atmxVplTable by setting atmxVplRowStatus to createAndWait(5). This may fail for the following reasons: - The selected VPI value is unavailable, - The selected VPI value is in use. Otherwise, the agent creates a row and reserves the VPI value on that port. (2) The manager selects an existing row(s) in the atmxTrafficDescrParamTable, thereby, selecting a set of self-consistent ATM traffic parameters and the QoS Class for receive and transmit directions of the VPL. (2a) If no suitable row(s) in the atmxTrafficDescrParamTable exists, the manager must create a new row(s) in that table. (2b) The manager characterizes the VPL's traffic parameters through setting the atmxVplReceiveTrafficDescrIndex and the atmxVplTransmitTrafficDescrIndex values in the VPL table, which point to the rows containing desired ATM traffic parameter values in the atmxTrafficDescrParamTable. The agent will check the availability of resources and may refuse the request. (3) The manager activates the VPL by setting the the atmxVplRowStatus to active(1). If this set is successful, the agent has reserved the resources to satisfy the requested traffic parameter values and the QoS Class for that VPL. (4) If the VPL terminates a VPC in the ATM host or switch, the manager turns on the atmxVplAdminStatus to up(1) to turn the VPL traffic flow on. Otherwise, the atmxVpCrossConnectTable must be used to cross-connect the VPL to another VPL(s) in an ATM switch or network. One-Shot VPL Establishment A VPL may also be established in one step by a set-request with all necessary VPL parameter values and atmxVplRowStatus set to createAndGo(4). In contrast to the negotiated VPL establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VPL establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VPL Retirement A VPL is released by setting atmxVplRowStatus to destroy(6), and the agent may release all associated resources.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxVplEntry  

atmxVplSlotIndex 1.1.800.2.9.1.1.1.1.1
The slot number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxVplPortIndex 1.1.800.2.9.1.1.1.1.2
The port number of the csm board
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

atmxVplVpi 1.1.800.2.9.1.1.1.1.3
The VPI value of the VPL. Note that the VPI=0 is not used for a VPL not associated with a VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..4095  

atmxVplAdminStatus 1.1.800.2.9.1.1.1.1.4
This object is implemented only for a VPL which terminates a VPC (i.e., one which is NOT cross-connected to other VPLs). Its value specifies the desired administrative state of the VPL. The up and down states indicate that the traffic flow is enabled and disabled respectively for this VPL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER up(1), down(2)  

atmxVplOperStatus 1.1.800.2.9.1.1.1.1.5
This object indicates the current operational status of the VPL. The up and down states indicate that the VPL is currently operational, or not operational, respectively. The unknown state indicates that the status of this VPL cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVplLastChange 1.1.800.2.9.1.1.1.1.6
The value of MIB II's sysUpTime object at the time this VPL entered its current operational state. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVplReceiveTrafficDescrIndex 1.1.800.2.9.1.1.1.1.7
The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the receive direction of the VPL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  AtmxTrafficDescrParamIndex  

atmxVplTransmitTrafficDescrIndex 1.1.800.2.9.1.1.1.1.8
The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the transmit direction of the VPL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  AtmxTrafficDescrParamIndex  

atmxVplCrossConnectIdentifier 1.1.800.2.9.1.1.1.1.9
This object is implemented only for a VPL which is cross-connected to other VPLs that belong to the same VPC. All such associated VPLs have the same value of this object, and all their cross-connections are identified by entries in the atmxVpCrossConnectTable for which atmxVpCrossConnectIndex has the same value. The value of this object is initialized by the agent after the associated entries in the atmxVpCrossConnectTable have been created.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..2147483647  

atmxVplRowStatus 1.1.800.2.9.1.1.1.1.10
This object is used to create, delete or modify a row in this table. To create a new VCL, 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: atmxVplReceiveTrafficDescrIndex and atmxVplTransmitTrafficDescrIndex. Xylan implemnts createAndWait and createAndGo as just Create..
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

atmxVplBidirect 1.1.800.2.9.1.1.1.1.11
Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER off(1), on(2)  

atmxVclTable 1.1.800.2.9.1.3.1
The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxVclEntry

atmxVclEntry 1.1.800.2.9.1.3.1.1
An entry in the VCL table. This entry is used to model a bi-directional VCL. To create a VCL at an ATM interface, either of the following procedures are used: Negotiated VCL establishment (1) The management application creates a VCL entry in the atmxVclTable by setting atmxVclRowStatus to createAndWait(5). This may fail for the following reasons: - The selected VPI/VCI values are unavailable, - The selected VPI/VCI values are in use. Otherwise, the agent creates a row and reserves the VPI/VCI values on that port. (2) The manager selects an existing row(s) in the atmxTrafficDescrParamTable, thereby, selecting a set of self-consistent ATM traffic parameters and the QoS Class for receive and transmit directions of the VCL. (2a) If no suitable row(s) in the atmxTrafficDescrParamTable exists, the manager must create a new row(s) in that table. (2b) The manager characterizes the VCL's traffic parameters through setting the atmxVclReceiveTrafficDescrIndex and the atmxVclTransmitTrafficDescrIndex values in the VCL table, which point to the rows containing desired ATM traffic parameter values in the atmxTrafficDescrParamTable. The agent will check the availability of resources and may refuse the request. (3) The manager activates the VCL by setting the the atmxVclRowStatus to active(1). If this set is successful, the agent has reserved the resources to satisfy the requested traffic parameter values and the QoS Class for that VCL. (4) If the VCL terminates a VCC in the ATM host or switch, the manager turns on the atmxVclAdminStatus to up(1) to turn the VCL traffic flow on. Otherwise, the atmxVcCrossConnectTable must be used to cross-connect the VCL to another VCL(s) in an ATM switch or network. One-Shot VCL Establishment A VCL may also be established in one step by a set-request with all necessary VCL parameter values and atmxVclRowStatus set to createAndGo(4). In contrast to the negotiated VCL establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VCL establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VCL Retirement A VCL is released by setting atmxVclRowStatus to destroy(6), and the agent may release all associated resources.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxVclEntry  

atmxVclSlotIndex 1.1.800.2.9.1.3.1.1.1
The slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxVclPortIndex 1.1.800.2.9.1.3.1.1.2
The port number of the csm board
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

atmxVclVpi 1.1.800.2.9.1.3.1.1.3
The VPI value of the VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

atmxVclVci 1.1.800.2.9.1.3.1.1.4
The VCI value of the VCL. The maximum VCI value cannot exceed the value allowable by the atmInterfaceMaxVciBits.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

atmxVclAdminStatus 1.1.800.2.9.1.3.1.1.5
This object is implemented only for a VCL which terminates a VCC (i.e., one which is NOT cross-connected to other VCLs). Its value specifies the desired administrative state of the VCL. The up and down states indicate that the traffic flow is enabled and disabled respectively for this VCL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER up(1), down(2)  

atmxVclOperStatus 1.1.800.2.9.1.3.1.1.6
This object indicates the current operational status of the VCL. The up and down states indicate that the VCL is currently operational, or not operational, respectively. The unknown state indicates that the status of this VCL cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVclLastChange 1.1.800.2.9.1.3.1.1.7
The value of MIB II's sysUpTime object at the time this VCL entered its current operational state. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVclReceiveTrafficDescrIndex 1.1.800.2.9.1.3.1.1.8
The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  AtmxTrafficDescrParamIndex  

atmxVclTransmitTrafficDescrIndex 1.1.800.2.9.1.3.1.1.9
The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.
Status: mandatory Access: read-write
OBJECT-TYPE    
  AtmxTrafficDescrParamIndex  

atmxVccAalType 1.1.800.2.9.1.3.1.1.10
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL is in use. The type of AAL used on this VCC. The AAL type includes AAL1, AAL3/4, and AAL5. The other(4) may be user-defined AAL type. The unknown type indicates that the AAL type cannot be determined.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER aal1(1), aal34(2), aal5(3), other(4), unknown(5)  

atmxVccAal5CpcsTransmitSduSize 1.1.800.2.9.1.3.1.1.11
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the transmit direction of this VCC.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..65535  

atmxVccAal5CpcsReceiveSduSize 1.1.800.2.9.1.3.1.1.12
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the receive direction of this VCC.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..65535  

atmxVccAal5EncapsType 1.1.800.2.9.1.3.1.1.13
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The type of data encapsulation used over the AAL5 SSCS layer. The definitions reference RFC 1483 Multiprotocol Encapsulation over ATM AAL5 and to the ATM Forum LAN Emulation specification.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER vcMultiplexRoutedProtocol(1), vcMultiplexBridgedProtocol8023(2), vcMultiplexBridgedProtocol8025(3), vcMultiplexBridgedProtocol8026(4), vcMultiplexLANemulation8023(5), vcMultiplexLANemulation8025(6), llcEncapsulation(7), multiprotocolFrameRelaySscs(8), other(9), unknown(10)  

atmxVclCrossConnectIdentifier 1.1.800.2.9.1.3.1.1.14
This object is implemented only for a VCL which is cross-connected to other VCLs that belong to the same VCC. All such associated VCLs have the same value of this object, and all their cross-connections are identified by entries in the atmxVcCrossConnectTable for which atmxVcCrossConnectIndex has the same value. The value of this object is initialized by the agent after the associated entries in the atmxVcCrossConnectTable have been created.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..2147483647  

atmxVclRowStatus 1.1.800.2.9.1.3.1.1.15
This object is used to create, delete or modify a row in this table. To create a new VCL, 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: atmxVclReceiveTrafficDescrIndex, atmxVclTransmitTrafficDescrIndex. Xylan implements createAndWait along with create&Go as create. Create is basically a superset. In addition, if the local VCL end-point is also the VCC end-point: atmVccAalType. In addition, for AAL5 connections only: atmVccAal5CpcsTransmitSduSize, atmVccAal5CpcsReceiveSduSize, and atmVccAal5EncapsType.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

atmxVclBidirect 1.1.800.2.9.1.3.1.1.16
Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER off(1), on(2)  

atmxVpCrossConnectTable 1.1.800.2.9.1.5.1
The ATM VP Cross Connect table. A bi- directional VP cross-connect which cross-connects two VPLs is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxVpCrossConnectEntry

atmxVpCrossConnectEntry 1.1.800.2.9.1.5.1.1
An entry in the ATM VP Cross Connect table. This entry is used to model a bi-directional ATM VP cross-connect which cross-connects two VPLs. Step-wise Procedures to set up a VP Cross-connect Once the entries in the atmxVplTable are created, the following procedures are used to cross-connect the VPLs together. (1) The manager obtains a unique atmxVpCrossConnectIndex by reading the atmxVpCrossConnectIndexNext object. (2) Next, the manager creates a set of one or more rows in the ATM VP Cross Connect Table, one for each cross-connection between two VPLs. Each row is indexed by the ATM interface port numbers and VPI values of the two ends of that cross-connection. This set of rows specifies the topology of the VPC cross-connect and is identified by a single value of atmxVpCrossConnectIndex. Negotiated VP Cross-Connect Establishment (2a) The manager creates a row in this table by setting atmxVpCrossConnectRowStatus to createAndWait(5). The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and QoS Classes, i.e., the row creation fails if: - the requested topology is not supported by the agent, - the traffic/QoS parameter values associated with the requested row are incompatible with those of already existing rows for this VP cross-connect. [For example, for setting up a point-to-point VP cross-connect, the ATM traffic parameters in the receive direction of a VPL at the low end of the cross-connect must equal to the traffic parameters in the transmit direction of the other VPL at the high end of the cross-connect, otherwise, the row creation fails.] The agent also checks for internal errors in building the cross-connect. The atmxVpCrossConnectIndex values in the corresponding atmxVplTable rows are filled in by the agent at this point. (2b) The manager promotes the row in the atmxVpCrossConnectTable by setting atmxVpCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the resources specified by the ATM traffic parameter and QoS Class values for each direction of the VP cross-connect in an ATM switch or network. (3) The manager sets the atmxVpCrossConnectAdminStatus to up(1) in all rows of this VP cross-connect to turn the traffic flow on. One-Shot VP Cross-Connect Establishment A VP cross-connect may also be established in one step by a set-request with all necessary parameter values and atmxVpCrossConnectRowStatus set to createAndGo(4). In contrast to the negotiated VP cross-connect establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VP cross-connect establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VP Cross-Connect Retirement A VP cross-connect identified by a particular value of atmxVpCrossConnectIndex is released by: (1) Setting atmxVpCrossConnectRowStatus of all rows identified by this value of atmxVpCrossConnectIndex to destroy(6). The agent may release all associated resources, and the atmxVpCrossConnectIndex values in the corresponding atmxVplTable row are removed. Note that a situation when only a subset of the associated rows are deleted corresponds to a VP topology change. (2) After deletion of the appropriate atmxVpCrossConnectEntries, the manager may set atmxVplRowStatus to destroy(6) the associated VPLs. The agent releases the resources and removes the associated rows in the atmxVplTable. VP Cross-connect Reconfiguration At the discretion of the agent, a VP cross-connect may be reconfigured by adding and/or deleting leafs to/from the VP topology as per the VP cross-connect establishment/retirement procedures. Reconfiguration of traffic/QoS parameter values requires release of the VP cross-connect before those parameter values may by changed for individual VPLs.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxVpCrossConnectEntry  

atmxVpCrossConnectIndex 1.1.800.2.9.1.5.1.1.1
A unique value to identify this VP Cross Connect
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..2147483647  

atmxVpCrossConnectLowSlotIndex 1.1.800.2.9.1.5.1.1.2
The low slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxVpCrossConnectLowPortIndex 1.1.800.2.9.1.5.1.1.3
The low physical port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVpCrossConnectLowVpi 1.1.800.2.9.1.5.1.1.4
The value of this object is equal to the VPI value at the ATM interface associated with the VP cross-connect that is identified by atmxVpCrossConnectLow (Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..4095  

atmxVpCrossConnectHighSlotIndex 1.1.800.2.9.1.5.1.1.5
The value of the high slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVpCrossConnectHighPortIndex 1.1.800.2.9.1.5.1.1.6
The high physical port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVpCrossConnectHighVpi 1.1.800.2.9.1.5.1.1.7
The value of this object is equal to the VPI value at the ATM interface associated with the VP cross-connect that is identified by atmxVpCrossConnectHigh(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..4095  

atmxVpCrossConnectAdminStatus 1.1.800.2.9.1.5.1.1.8
The value of this object identifies the desired administrative status of this bi-directional VP cross-connect. The up and down states indicate that the traffic flow is enabled and disabled respectively on this VP cross-connect.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER up(1), down(2)  

atmxVpCrossConnectL2HOperStatus 1.1.800.2.9.1.5.1.1.9
The value of this object identifies the current operational status of the VP cross-connect in one direction; (i.e., from the low to high direction). The up and down states indicate that this ATM VP cross-connect from low to high direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVpCrossConnectH2LOperStatus 1.1.800.2.9.1.5.1.1.10
The value of this object identifies the current operational status of the VP cross-connect in one direction; (i.e., from the high to low direction). The up and down states indicate that this ATM VP cross-connect from high to low direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVpCrossConnectL2HLastChange 1.1.800.2.9.1.5.1.1.11
The value of MIB II's sysUpTime object at the time this VP cross-connect entered its current operational state in the low to high direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVpCrossConnectH2LLastChange 1.1.800.2.9.1.5.1.1.12
The value of MIB II's sysUpTime object at the time this VP cross-connect entered its current operational state in the high to low direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVpCrossConnectRowStatus 1.1.800.2.9.1.5.1.1.13
The status of this entry in the atmxVpCrossConnectTable. This object is used to create a cross-connect for cross-connecting VPLs which are created using the atmxVplTable or to change or delete an existing cross-connect. This object must be initially set to `createAndWait' or 'createAndGo'. This object cannot be set to `active' unless the following columnar object exists in this row: atmxVpCrossConnectAdminStatus. To turn on a VP cross-connect, the atmxVpCrossConnectAdminStatus is set to `up'. Xylan implements createAndWait along with create&Go as create. Create is basically a superset.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

atmxSvcVpCrossConnectTable 1.1.800.2.9.1.5.2
The ATM SVC VP Cross Connect table. A bi- directional VP cross-connect which cross-connects two SVC VPLs is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxSvcVpCrossConnectEntry

atmxSvcVpCrossConnectEntry 1.1.800.2.9.1.5.2.1
An entry in the ATM SVC VP Cross Connect table. This entry is used to model a bi-directional ATM SVC VP cross-connect which cross-connects two VPLs.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxSvcVpCrossConnectEntry  

atmxSvcVpCrossConnectLowSlotIndex 1.1.800.2.9.1.5.2.1.1
The low slot of the SVC VP cross-connect.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..9  

atmxSvcVpCrossConnectLowPortIndex 1.1.800.2.9.1.5.2.1.2
The incoming slot for this SVC
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..25  

atmxSvcVpCrossConnectLowVpi 1.1.800.2.9.1.5.2.1.3
The value of this object is equal to the VPI value at the ATM interface associated with the SVC VP cross-connect that is identified by atmSvcVpCrossConnectLow(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..4095  

atmxSvcVpCrossConnectHighSlotIndex 1.1.800.2.9.1.5.2.1.4
The outgoing slot for this SVC
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..9  

atmxSvcVpCrossConnectHighPortIndex 1.1.800.2.9.1.5.2.1.5
The outgoing port for this SVC
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..25  

atmxSvcVpCrossConnectHighVpi 1.1.800.2.9.1.5.2.1.6
The value of this object is equal to the VPI value at the ATM interface associated with the SVC VP cross-connect that is identified by atmSvcVpCrossConnectHigh(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..4095  

atmxSvcVpCrossConnectCreationTime 1.1.800.2.9.1.5.2.1.7
The value of MIB II's sysUpTime object at the time this bi-directional SVC VP cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxSvcVpCrossConnectLowTDIndex 1.1.800.2.9.1.5.2.1.8
The low end connections Traffic Descriptor Index
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxSvcVpCrossConnectHighTDIndex 1.1.800.2.9.1.5.2.1.9
The high connections traffic descriptor index
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxSvcVpCrossConnectRowStatus 1.1.800.2.9.1.5.2.1.10
This object can be used to delete rows in the atmSvcVpCrossConnectTable. But unless we require it for specific reasons we will not allow creation/deletion
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVcCrossConnectTable 1.1.800.2.9.1.7.1
The ATM VC Cross Connect table. A bi- directional VC cross-connect which cross-connects two end points (i.e., VCLs) is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxVcCrossConnectEntry

atmxVcCrossConnectEntry 1.1.800.2.9.1.7.1.1
An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points. Step-wise Procedures to set up a VC Cross-connect Once the entries in the atmxVclTable are created, the following procedures are used to cross-connect the VCLs together to form a VCC segment. (1) The manager obtains a unique atmxVcCrossConnectIndex by reading the atmxVcCrossConnectIndexNext object. (2) Next, the manager creates a set of one or more rows in the ATM VC Cross Connect Table, one for each cross-connection between two VCLs. Each row is indexed by the ATM interface port numbers and VPI/VCI values of the two ends of that cross-connection. This set of rows specifies the topology of the VCC cross-connect and is identified by a single value of atmxVcCrossConnectIndex. Negotiated VC Cross-Connect Establishment (2a) The manager creates a row in this table by setting atmxVcCrossConnectRowStatus to createAndWait(5). The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and QoS Classes, i.e., the row creation fails if: - the requested topology is not supported by the agent, - the traffic/QoS parameter values associated with the requested row are incompatible with those of already existing rows for this VC cross-connect. [For example, for setting up a point-to-point VC cross-connect, the ATM traffic parameters in the receive direction of a VCL at the low end of the cross-connect must equal to the traffic parameters in the transmit direction of the other VCL at the high end of the cross-connect, otherwise, the row creation fails.] The agent also checks for internal errors in building the cross-connect. The atmxVcCrossConnectIndex values in the corresponding atmxVclTable rows are filled in by the agent at this point. (2b) The manager promotes the row in the atmxVcCrossConnectTable by setting atmxVcCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the resources specified by the ATM traffic parameter and QoS Class values for each direction of the VC cross-connect in an ATM switch or network. (3) The manager sets the atmxVcCrossConnectAdminStatus to up(1) in all rows of this VC cross-connect to turn the traffic flow on. One-Shot VC Cross-Connect Establishment A VC cross-connect may also be established in one step by a set-request with all necessary parameter values and atmxVcCrossConnectRowStatus set to createAndGo(4). In contrast to the negotiated VC cross-connect establishment which allows for detailed error checking i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VC cross-connect establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VC Cross-Connect Retirement A VC cross-connect identified by a particular value of atmxVcCrossConnectIndex is released by: (1) Setting atmxVcCrossConnectRowStatus of all rows identified by this value of atmxVcCrossConnectIndex to destroy(6). The agent may release all associated resources, and the atmxVcCrossConnectIndex values in the corresponding atmxVclTable row are removed. Note that a situation when only a subset of the associated rows are deleted corresponds to a VC topology change. (2) After deletion of the appropriate atmxVcCrossConnectEntries, the manager may set atmxVclRowStatus to destroy(6) the associated VCLs. The agent releases the resources and removes the associated rows in the atmxVclTable. VC Cross-Connect Reconfiguration At the discretion of the agent, a VC cross-connect may be reconfigured by adding and/or deleting leafs to/from the VC topology as per the VC cross-connect establishment/retirement procedures. Reconfiguration of traffic/QoS parameter values requires release of the VC cross-connect before those parameter values may by changed for individual VCLs.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxVcCrossConnectEntry  

atmxVcCrossConnectIndex 1.1.800.2.9.1.7.1.1.1
A unique value to identify this VC Cross Connect
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..2147483647  

atmxVcCrossConnectLowSlotIndex 1.1.800.2.9.1.7.1.1.2
The low port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxVcCrossConnectLowPortIndex 1.1.800.2.9.1.7.1.1.3
The value of this object is equal to the ATM interface port in this slot for this VC cross-connect. The term low implies that this ATM interface has the numerically lower PortIndex value than the other ATM interface identified in the same atmxVcCrossConnectEntry.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVcCrossConnectLowVpi 1.1.800.2.9.1.7.1.1.4
The value of this object is equal to the VPI value at the ATM interface associated with the VC cross-connect that is identified by atmxVcCrossConnectLow(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

atmxVcCrossConnectLowVci 1.1.800.2.9.1.7.1.1.5
The value of this object is equal to the VCI value at the ATM interface associated with this VC cross-connect that is identified by atmxVcCrossConnectLow(Slot/Port)index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

atmxVcCrossConnectHighSlotIndex 1.1.800.2.9.1.7.1.1.6
The high port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

atmxVcCrossConnectHighPortIndex 1.1.800.2.9.1.7.1.1.7
The value of this object is equal to the ATM interface port in this slot for this VC cross-connect. The term high implies that this VC cross-connect that this ATM interface has the numerically higher slot/port value than the other ATM interface identified in the same atmxVcCrossConnectEntry.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxVcCrossConnectHighVpi 1.1.800.2.9.1.7.1.1.8
The value of this object is equal to the VPI value at the ATM interface associated with the VC cross-connect that is identified by atmxVcCrossConnectHigh(slot/port)index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

atmxVcCrossConnectHighVci 1.1.800.2.9.1.7.1.1.9
The value of this object is equal to the VCI value at the ATM interface associated with the VC cross-connect that is identified by atmxVcCrossConnectHigh(Slot/port)Index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

atmxVcCrossConnectAdminStatus 1.1.800.2.9.1.7.1.1.10
The value of this object identifies the desired administrative status of this bi-directional VC cross-connect. The up and down states indicate that the traffic flow is enabled or disabled respectively on this VC cross-connect.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER up(1), down(2)  

atmxVcCrossConnectL2HOperStatus 1.1.800.2.9.1.7.1.1.11
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the low to high direction). The up and down states indicate that this ATM VC cross-connect from low to high direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVcCrossConnectH2LOperStatus 1.1.800.2.9.1.7.1.1.12
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the high to low direction). The up and down states indicate that this ATM VC cross-connect from high to low direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

atmxVcCrossConnectL2HLastChange 1.1.800.2.9.1.7.1.1.13
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in low to high direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVcCrossConnectH2LLastChange 1.1.800.2.9.1.7.1.1.14
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in high to low direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxVcCrossConnectRowStatus 1.1.800.2.9.1.7.1.1.15
The status of this entry in the atmxVcCrossConnectTable. This object is used to create a new cross-connect for cross-connecting VCLs which are created using the atmxVclTable or to change or delete existing cross-connect. This object must be initially set to `createAndWait' or 'createAndGo'. This object cannot be set to `active' unless the following columnar object exists in this row: atmxVcCrossConnectAdminStatus. To turn on a VC cross-connect, the atmxVcCrossConnectAdminStatus is set to `up'. Xylan implements createAndWait along with create&Go as create. Create is basically a superset.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

atmxSvcVcCrossConnectTable 1.1.800.2.9.1.7.2
The ATM SVC VC Cross Connect table. A bi- directional SVC VC cross-connect which cross-connects two end points (i.e., VCLs) is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AtmxSvcVcCrossConnectEntry

atmxSvcVcCrossConnectEntry 1.1.800.2.9.1.7.2.1
An entry in the ATM SVC VC Cross Connect table. This entry is used to model a bi-directional ATM SVC VC cross-connect cross-connecting two end points.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  AtmxSvcVcCrossConnectEntry  

atmxSvcVcCrossConnectLowSlotIndex 1.1.800.2.9.1.7.2.1.1
The incoming slot for this SVC.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..9  

atmxSvcVcCrossConnectLowPortIndex 1.1.800.2.9.1.7.2.1.2
The incoming port for this SVC.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..25  

atmxSvcVcCrossConnectLowVpi 1.1.800.2.9.1.7.2.1.3
The value of this object is equal to the VPI value at the ATM interface associated with the SVC VC cross-connect that is identified by atmSvcVcCrossConnectLow(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..4095  

atmxSvcVcCrossConnectLowVci 1.1.800.2.9.1.7.2.1.4
The value of this object is equal to the VCI value at the ATM interface associated with this SVC VC cross-connect that is identified by atmSvcVcCrossConnectLow(Slot/Port)Index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the low ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..65535  

atmxSvcVcCrossConnectHighSlotIndex 1.1.800.2.9.1.7.2.1.5
The outgoing slot for this SVC
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..9  

atmxSvcVcCrossConnectHighPortIndex 1.1.800.2.9.1.7.2.1.6
The outgoing port for this SVC
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER  

atmxSvcVcCrossConnectHighVpi 1.1.800.2.9.1.7.2.1.7
The value of this object is equal to the VPI value at the ATM interface associated with the SVC VC cross-connect that is identified by atmSvcVcCrossConnectHigh(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..4095  

atmxSvcVcCrossConnectHighVci 1.1.800.2.9.1.7.2.1.8
The value of this object is equal to the VCI value at the ATM interface associated with the SVC VC cross-connect that is identified by atmSvcVcCrossConnectHigh(Slot/Port)Index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the high ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..65535  

atmxSvcVcCrossConnectCreationTime 1.1.800.2.9.1.7.2.1.9
The value of MIB II's sysUpTime object at the time this bi-directional SVC VC cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

atmxSvcVcCrossConnectLowTDIndex 1.1.800.2.9.1.7.2.1.10
The low end connections Traffic Descriptor Index
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxSvcVcCrossConnectHighTDIndex 1.1.800.2.9.1.7.2.1.11
The high connections traffic descriptor index
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

atmxSvcVcCrossConnectRowStatus 1.1.800.2.9.1.7.2.1.12
This object is used to indicate the status of the SVC in the atmSvcVcCrossConnectTable.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmInterfaceConfTable 1.1.800.2.9.1.4.1
This table contains the private ATM local interface configuration parameters, one entry per ATM interface port.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnAtmInterfaceConfEntry

xylnatmInterfaceConfEntry 1.1.800.2.9.1.4.1.1
This list contains xyln specific ATM interface configuration parameters and state variables.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnAtmInterfaceConfEntry  

xylnatmInterfaceSlotIndex 1.1.800.2.9.1.4.1.1.1
The slot number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmInterfacePortIndex 1.1.800.2.9.1.4.1.1.2
The port number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..25  

xylnatmInterfaceDescription 1.1.800.2.9.1.4.1.1.3
The name in ascii characters describing the interface
Status: mandatory Access: read-write
OBJECT-TYPE    
  DisplayString  

xylnatmInterfaceTransType 1.1.800.2.9.1.4.1.1.4
The transmission type at this interface. The type is either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b encoding method.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), sonetSts3(2), ds3(3), fourb5b(4), eightb10b(5), e3(6), sonetSts12(7), ds1(8), e1(9), internal(20)  

xylnatmInterfaceType 1.1.800.2.9.1.4.1.1.5
The signaling type at this interface.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER public(1), private(2), pnni10(3), nni-iisp-network(4), nni-iisp-user(5), other(6)  

xylnatmInterfaceMediaType 1.1.800.2.9.1.4.1.1.6
The physical media type from this physical port
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), coax(2), singlemode(3), multimode(4), stp(5), utp(6), internal(7)  

xylnatmInterfaceAtmAddress 1.1.800.2.9.1.4.1.1.7
The AtmAddress @ this interface. The AtmAddress should be a 20 octet hex number.
Status: mandatory Access: read-write
OBJECT-TYPE    
  DisplayString  

xylnatmInterfacePortMode 1.1.800.2.9.1.4.1.1.8
This object describes whether this interface is switched off or allowing traffic to pass thru or is in normal mode.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER off(1), passthru(2), normal(3)  

xylnatmInterfaceOperStatus 1.1.800.2.9.1.4.1.1.9
The Oper status @ this interface is reflected by the status of the object.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2)  

xylnatmInterfaceQsaalStatus 1.1.800.2.9.1.4.1.1.10
The QSAAL status @ this interface is reflected by the status of the object.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2)  

xylnatmInterfaceIlmiStatus 1.1.800.2.9.1.4.1.1.11
The Ilmi Status @ this interface.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2)  

xylnatmInterfaceTpRedirect 1.1.800.2.9.1.4.1.1.12
This object indicates whether Cut-Over is enabled or disabled @ this interface
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

xylnatmInterfaceCutOverSlot 1.1.800.2.9.1.4.1.1.13
The Cut-Over slot number of the chassis
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmInterfaceCutOverPort 1.1.800.2.9.1.4.1.1.14
The Cut Over Port number of the chassis
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..25  

xylnatmInterfaceClearPortStats 1.1.800.2.9.1.4.1.1.15
True clears the stats for this port
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER true(1), false(2)  

xylnatmInterfaceClearChanStats 1.1.800.2.9.1.4.1.1.16
True clears the chan stats
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER true(1), false(2)  

xylnatmInterfaceClearSlotStats 1.1.800.2.9.1.4.1.1.17
True clears all the port stats in this slot.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER true(1), false(2)  

xylnatmInterfaceTransmissionType 1.1.800.2.9.1.4.1.1.18
The type of physical media for transmission on the port Sonet or SDH. SDH is primarily used in Europe and Sonet in the US. The S bit in the payload pointer is 00 for Sonet and 01 for SDH
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER sonet3c(1), sdh(2), sonet12c(3), notApplicable(4)  

xylnatmInterfaceIlmiState 1.1.800.2.9.1.4.1.1.19
The state of Ilmi for the instanced port. Setting this object to disable, would prevent any ILMI queries being sent out on this port.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmInterfaceTimingMode 1.1.800.2.9.1.4.1.1.20
This object selects the method used by the port to generate the clock used for transmit data. local(1) selects local clock source. loop(2) selects the derived clock from the receive data.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER local(1), loop(2)  

xylnatmInterfaceLocalSrc 1.1.800.2.9.1.4.1.1.21
This object selects which local clock source used to drive the transmit data for the port. This option is not available when the port's timing mode is loop. oscillator(1) selects the on board oscillator. busLine8K(2) selects the 8 KHz clocking bus line. All CSM-interface types except for OC3 and OC12 can use an 8 KHz clock from the bus to generate their local timing. busLine19M(3) selects the 19.44 MHz clocking bus line. All CSM OC3, OC12 and CSM-AB-CE-T1 and CSM-AB-CE-E1 interface types can use a 19.44 Mhz clock from the bus to generate their local timing. In the case of the CSM-AB-CE the adapter board does a divide operation on the 19.44 Mhz clock to get an 8 Khz clock to use. Currently, only the CSM-AB-CE T1 and E1 adapter boards have the ability to support either busLine8K and busLine19M options.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER oscillator(1), busLine8K(2), busLine19M(3)  

xylnatmInterfaceUniVersion 1.1.800.2.9.1.4.1.1.22
UNI Version used in the chassis
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER uni30(1), uni31(2), uniIisp(3)  

xylnatmILMIConfTable 1.1.800.2.9.1.4.3
This table contains CSM ILMI configuration parameters, one entry per CSM physical interface, or per virtual UNI/NNI instance
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmILMIConfEntry

xylnatmILMIConfEntry 1.1.800.2.9.1.4.3.1
This list contains CSM ILMI configuration and state variables
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmILMIConfEntry  

xylnatmILMIConfSlot 1.1.800.2.9.1.4.3.1.1
The slot number this entry represents
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmILMIConfPort 1.1.800.2.9.1.4.3.1.2
The port number this entry represents
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmILMIConfInstance 1.1.800.2.9.1.4.3.1.3
The Virtual UNI/NNI instance this entry represents
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmILMIConfILMIEnable 1.1.800.2.9.1.4.3.1.4
Indicate whether ILMI is enabled on this port, or on this Virtual UNI/NNI instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER disable(1), enable(2)  

xylnatmILMIConfILMIPollEnable 1.1.800.2.9.1.4.3.1.5
Indicate whether ILMI polling is enabled on this port, or on this Virtual UNI/NNI instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER disable(1), enable(2)  

xylnatmILMIConfAutoCfgEnable 1.1.800.2.9.1.4.3.1.6
Indicate whether CSM auto cfg is enabled on this port, or on this Virtual UNI/NNI instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER disable(1), enable(2)  

xylnatmILMIConfAutoCfgStatus 1.1.800.2.9.1.4.3.1.7
The status of auto configuration procedure on this port, or this Virtual UNI/NNI instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER cfgDone(1), idle(2), inProgress(3)  

xylnatmILMIConfAutoCfgTrigg 1.1.800.2.9.1.4.3.1.8
Indicate how auto configuration procedure is triggerred on this port or virtual UNI/NNI instance, phy indicates auto configuration is only triggered when the port detects physical layer connection is from down to up, logic indicates auto configuration procedure is triggerred when CSM port receives trap from peer port, while phy_logic indicate auto configuration procedure is triggerred by both phy and logic, which are situations described by above narrative
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER unknown(1), phyLogic(2), phy(3), logic(4)  

xylnatmILMIConfAutoCfgDfltIf 1.1.800.2.9.1.4.3.1.9
The default interface type this port or virtual UNI/NNI instance will take when auto configuration procedure fails to detect its peer port's interface type
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER privateUNI(1), pnni(2), iispNetwork(3), iispUser(4), publicUNI(5)  

xylnatmILMIConfAutoCfgDfltSigVer 1.1.800.2.9.1.4.3.1.10
The default signaling version this port or virtual UNI/NNI instance will take when auto configuration procedure fails to detect its peer port's signaling version
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER uni30(1), uni31(2), uni40(3)  

xylnatmILMIConfAutoCfgCurIf 1.1.800.2.9.1.4.3.1.11
Current operational interface type for this CSM port or virtual UNI/NNI instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER privateUNI(1), pnni(2), iispNetwork(3), iispUser(4), publicUNI(5)  

xylnatmILMIConfAutoCfgCurSigVer 1.1.800.2.9.1.4.3.1.12
Current operational signaling version for this CSM port or virtual UNI/NNI instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER uni30(1), uni31(2), uni40(3)  

xylnatmILMIConfAutoCfgCurILMIVer 1.1.800.2.9.1.4.3.1.13
Current ILMI version running on this CSM port or virtual UNI/NNI instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unsupported(1), ilmi40(2)  

xylnatmILMIConfPeerUniType 1.1.800.2.9.1.4.3.1.14
The UNI type this port gathered from its peer port through ILMI
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER public(1), private(2)  

xylnatmILMIConfPeerUniVer 1.1.800.2.9.1.4.3.1.15
The signaling version this port gathered from its peer port through ILMI
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER uni30(1), uni31(2), uni40(3)  

xylnatmILMIConfPeerDevType 1.1.800.2.9.1.4.3.1.16
The device type this port gathered from its peer port through ILMI
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER user(1), node(2)  

xylnatmILMIConfPeerNNISigVer 1.1.800.2.9.1.4.3.1.17
The NNI signaling version this port gathered from its peer port through ILMI
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unsupported(1), iisp(2), pnni10(3)  

xylnatmILMIConfPeerILMIVer 1.1.800.2.9.1.4.3.1.18
The ILMI version this port gathered from its peer port through ILMI
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unsupported(1), ilmi40(2)  

xylnatmInterfaceStatTable 1.1.800.2.9.1.6.1
This table contains the statistical information about the interface
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmInterfaceStatEntry

xylnatmInterfaceStatEntry 1.1.800.2.9.1.6.1.1
This list contains xylan specific ATM interface configuration parameters and state variables
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmInterfaceStatEntry  

xylnatmInterfaceStatSlotIndex 1.1.800.2.9.1.6.1.1.1
The slot number in the switch
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmInterfaceStatPortIndex 1.1.800.2.9.1.6.1.1.2
The port number in this slot
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmInterfaceStatRxCells 1.1.800.2.9.1.6.1.1.3
The total number of Received Cells at this interface (OC3, OC12, ATM25...)
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatRxClp0Cells 1.1.800.2.9.1.6.1.1.4
The total number of received cells at this interface with Cell loss priority of zero
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatRxClp1Cells 1.1.800.2.9.1.6.1.1.5
The total number of received cells at this interface with Cell loss Priority of zero or one
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatTxCells 1.1.800.2.9.1.6.1.1.6
The total number of transmitted cells at this interface
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatMarkEfciCells 1.1.800.2.9.1.6.1.1.7
The number of cells that are marked with efci (explicit forward congestion notification) in the payload type identifier field of the atm cell. This EFCI notification is used in conjunction with backward RM cells so that the destination can notify the source that there is congestion on the path to the destination
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatMarkGcraCells 1.1.800.2.9.1.6.1.1.8
The number of cells marked by policing that violated their traffic contract for clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatTotalDiscardCells 1.1.800.2.9.1.6.1.1.9
The total number of cells discarded at this interface due to congestion, policing and unknown vpi/vci's
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxCongClp0Cells 1.1.800.2.9.1.6.1.1.10
The number of Clp0 cells discarded due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxCongClp1Cells 1.1.800.2.9.1.6.1.1.11
The number of Clp1 cells discarded due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxGcraClp0Cells 1.1.800.2.9.1.6.1.1.12
The total number of Clp0 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxGcraClp1Cells 1.1.800.2.9.1.6.1.1.13
The total number of cell loss priority one cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxGcrabClp0Cells 1.1.800.2.9.1.6.1.1.14
The total number of Clp0 cells discarded due to policing on cell loss priority zero cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatDxGcrabClp1Cells 1.1.800.2.9.1.6.1.1.15
The total number of cell loss prioity one cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatUnknownVpVcCells 1.1.800.2.9.1.6.1.1.16
The total number of cells received on this interface which has a vpi/vci combination that doesnt correspond to any channels vpi/vci for this physical interface
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatUnknownVpiCells 1.1.800.2.9.1.6.1.1.17
The total number of unknown Vpi cells recieved at this interface that dont correspond to any channels vpi
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatUnknownVciCells 1.1.800.2.9.1.6.1.1.18
The total number of unknown Vci cells recieved at this interface that dont correspond to any channels vci
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatUniType 1.1.800.2.9.1.6.1.1.19
Type of UNI used on this interface...Public or Private
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER public(1), private(2)  

xylnatmInterfaceStatUniVersion 1.1.800.2.9.1.6.1.1.20
UNI Version used in the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER uni30(1), uni31(2)  

xylnatmInterfaceStatRemainingRxBandwidth 1.1.800.2.9.1.6.1.1.21
The remaining bandwidth available on this port thru which connections can be created and cells can be received.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmInterfaceStatRemainingTxBandwidth 1.1.800.2.9.1.6.1.1.22
The remaining bandwidth available on this port thru which connections can be created for cells to be transmitted
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclTable 1.1.800.2.9.1.10.1
This table contains xylan implementation specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVclEntry

xylnatmVclEntry 1.1.800.2.9.1.10.1.1
List of xylan specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVclEntry  

xylnatmVclSlotIndex 1.1.800.2.9.1.10.1.1.1
Slot Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclPortIndex 1.1.800.2.9.1.10.1.1.2
Port Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclVpi 1.1.800.2.9.1.10.1.1.3
Vpi instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclVci 1.1.800.2.9.1.10.1.1.4
Vcl instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclConnectionDescr 1.1.800.2.9.1.10.1.1.5
An ascii value for the connection
Status: mandatory Access: read-write
OBJECT-TYPE    
  DisplayString  

xylnatmVclChanType 1.1.800.2.9.1.10.1.1.6
The type of Virtual path
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER unknown(1), vcNni(3), vcUni(4)  

xylnatmVclTransportPriority 1.1.800.2.9.1.10.1.1.7
The transport priority...
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER qosCbrPrs(2), qosCbr(3), qosVbrRt(5), qosVbrNrt(6), qosAbr(7), qosUbr(8)  

xylnatmVclUserPriority 1.1.800.2.9.1.10.1.1.8
The user priority 0-15, with 0 being the highest
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVclStatsMode 1.1.800.2.9.1.10.1.1.9
This allows the user one of the 4 choices. When the user selects cntGcraDxCell = count clp0 & 1 and discard cell mrkGcraDxCell = count clp0 & 1, mark efci &clp, discard cell cntGcraPsCell = count clp0 &1 and pass the cell mrkGcraPsCell = count clp0 &1, mark efci and clp, pass cell
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER cntGcraDxCell(1), mrkGcraDxCell(2), cntGcraPsCell(3), mrkGcraPsCell(4)  

xylnatmVclPrTrackPortBase 1.1.800.2.9.1.10.1.1.10
The dest internal pport
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclPrTrackPort1 1.1.800.2.9.1.10.1.1.11
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclPrTrackPort2 1.1.800.2.9.1.10.1.1.12
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclPrTrackPort3 1.1.800.2.9.1.10.1.1.13
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclAltTrackPortBase 1.1.800.2.9.1.10.1.1.14
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclAltTrackPort1 1.1.800.2.9.1.10.1.1.15
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclAltTrackPort2 1.1.800.2.9.1.10.1.1.16
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclAltTrackPort3 1.1.800.2.9.1.10.1.1.17
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclLgclChanRedirect 1.1.800.2.9.1.10.1.1.18
Permits the user to allow or not allow logical channel redirects
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER notAllowed(1), allowed(2)  

xylnatmVclAAL5Discard 1.1.800.2.9.1.10.1.1.19
This field configures an action that IOP should take against cells when traffic congestion occurs. earlyPktDiscard(1) is treated as 'enable' for IOP version 1 since it doesn't support early packet discard feature. Early packet discard is an IOP 2 feature. In this mode, IOP either passes or discards all the cells of a packet. It passes all cells of a packet during congestion if the first cell of the packet has been passed. Cells are marked when GCRA contract is violated. This option does not apply to VBR_RT and CBR and CBR_PRS. disable(2) is selected to disable early packet discard and partial discard feature. Cells are discarded when needed during congestion. Cells are marked when GCRA contract is violated. partialPktDiscard(3) is an IOP 2 feature. IOP starts discarding cells--all of the remaining cells except for the last cell of the packet-when congestion occurs. When congestion ends, the first cell of a new packet is passed. Cells are marked when GCRA contract is violated. This option does not apply to VBR_RT and CBR and CBR_PRS. The default value for IOP 1 is 'disable'. The default value is 'earlyPktDiscard' for IOP 2 if the transport type of the circuit is UBR, ABR, and VBR_NRT. 'disable' is the default for VBR_RT and CBR and CBR_PRS.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER earlyPktDiscard(1), disable(2), partialPktDiscard(3)  

xylnatmVclF4F5SegEndpt 1.1.800.2.9.1.10.1.1.20
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclF4F5CopySeg 1.1.800.2.9.1.10.1.1.21
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclF4F5End2EndEndpt 1.1.800.2.9.1.10.1.1.22
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclF4F5CopyEnd2End 1.1.800.2.9.1.10.1.1.23
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclOamEndpt 1.1.800.2.9.1.10.1.1.24
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclOamCopy 1.1.800.2.9.1.10.1.1.25
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmFwdEndpt 1.1.800.2.9.1.10.1.1.26
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmFwdCopy 1.1.800.2.9.1.10.1.1.27
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmFwdGcraAdv 1.1.800.2.9.1.10.1.1.28
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmBkwdEndpt 1.1.800.2.9.1.10.1.1.29
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmBkwdCopy 1.1.800.2.9.1.10.1.1.30
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmBkwdGcraAdv 1.1.800.2.9.1.10.1.1.31
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclRmDiscard 1.1.800.2.9.1.10.1.1.32
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVclGcraAPoliceMode 1.1.800.2.9.1.10.1.1.33
Enforcement mode of GcraA as following gcraEmDxAll = Discard all cells on congestion gcraEmMarkClp0DxClp1 = On congestion discard Clp1 cells gcraEmMarkAllDxAll = On congestion mark all gcraEmMarkClp0DxAll = on congestion mark clp0 and discard all
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER gcraEmDxAll(1), gcraEmMarkClp0DxClp1(2), gcraEmMarkAllDxAll(3), gcraEmMarkClp0DxAll(4)  

xylnatmVclGcraBPoliceMode 1.1.800.2.9.1.10.1.1.34
Enforcement mode of GcraB as following gcraEmDxAll = Discard all cells on congestion gcraEmMarkClp0DxClp1 = On congestion discard Clp1 cells gcraEmMarkAllDxAll = On congestion mark all gcraEmMarkClp0DxAll = on congestion mark clp0 and discard all
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER gcraEmDxAll(1), gcraEmMarkClp0DxClp1(2), gcraEmMarkAllDxAll(3), gcraEmMarkClp0DxAll(4)  

xylnatmVclMcGroupId 1.1.800.2.9.1.10.1.1.35
Internal use of multicast group id
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclMcIngressEgress 1.1.800.2.9.1.10.1.1.36
Always ingress in this release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER ingress(1), egress(2)  

xylnatmVclStatTable 1.1.800.2.9.1.12.1
This table contains the xylan specific statistical object
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVclStatEntry

xylnatmVclStatEntry 1.1.800.2.9.1.12.1.1
Contains the stats objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVclStatEntry  

xylnatmVclStatSlotIndex 1.1.800.2.9.1.12.1.1.1
The slot number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclStatPortIndex 1.1.800.2.9.1.12.1.1.2
The port number of this slot
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..25  

xylnatmVclStatVpi 1.1.800.2.9.1.12.1.1.3
The Vpi number for this connection
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclStatVci 1.1.800.2.9.1.12.1.1.4
The Vci number for the connection
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclStatRxCells 1.1.800.2.9.1.12.1.1.5
The total number of cells received on this connection identified by the slot/port/vpi/vci
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatTxCells 1.1.800.2.9.1.12.1.1.6
The total number of cells transmitted on this connection identified by the slot/port/vpi/vci
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatRxClp0Cells 1.1.800.2.9.1.12.1.1.7
The total number of received cells with Clp0 received on this connection identified by slot/port/vpi/vci
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatRxClp1Cells 1.1.800.2.9.1.12.1.1.8
The total number of received cells with Clp1 received on this connection identified by slot/port/vpi/vci
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxCongClp0Cells 1.1.800.2.9.1.12.1.1.9
The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxCongClp1Cells 1.1.800.2.9.1.12.1.1.10
The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxGcraClp0Cells 1.1.800.2.9.1.12.1.1.11
The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxGcraClp1Cells 1.1.800.2.9.1.12.1.1.12
The total number of Clp1 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxGcraBClp0Cells 1.1.800.2.9.1.12.1.1.13
The total number of Clp0 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVclStatDxGcraBClp1Cells 1.1.800.2.9.1.12.1.1.14
The total number of Clp1 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplTable 1.1.800.2.9.1.9.1
This table contains xylan implementation specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVplEntry

xylnatmVplEntry 1.1.800.2.9.1.9.1.1
List of xylan specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVplEntry  

xylnatmVplSlotIndex 1.1.800.2.9.1.9.1.1.1
Slot Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplPortIndex 1.1.800.2.9.1.9.1.1.2
Port Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplVpi 1.1.800.2.9.1.9.1.1.3
Vpi instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplConnectionDescr 1.1.800.2.9.1.9.1.1.4
An ascii value for the connection
Status: mandatory Access: read-write
OBJECT-TYPE    
  DisplayString  

xylnatmVplChanType 1.1.800.2.9.1.9.1.1.5
The type of Virtual path
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER unknown(1), vpNNI(5), vpUni(6)  

xylnatmVplTransportPriority 1.1.800.2.9.1.9.1.1.6
The transport priority...
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER qosCbrPrs(2), qosCbr(3), qosVbrRt(5), qosVbrNrt(6), qosAbr(7), qosUbr(8)  

xylnatmVplUserPriority 1.1.800.2.9.1.9.1.1.7
The user priority 0-15 with 0 being the highest
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVplStatsMode 1.1.800.2.9.1.9.1.1.8
This allows the user one of the 4 choices. When the user selects cntGcraDxCell = count clp0 & 1 and discard cell mrkGcraDxCell = count clp0 & 1, mark efci &clp, discard cell cntGcraPsCell = count clp0 &1 and pass the cell mrkGcraPsCell = count clp0 &1, mark efci and clp, pass cell
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER cntGcraDxCell(1), mrkGcraDxCell(2), cntGcraPsCell(3), mrkGcraPsCell(4)  

xylnatmVplPrTrackPortBase 1.1.800.2.9.1.9.1.1.9
The destination internal pport
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplPrTrackPort1 1.1.800.2.9.1.9.1.1.10
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplPrTrackPort2 1.1.800.2.9.1.9.1.1.11
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplPrTrackPort3 1.1.800.2.9.1.9.1.1.12
Used under multicast conditions and will be supported in future releases for load balancing
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplAltTrackPortBase 1.1.800.2.9.1.9.1.1.13
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplAltTrackPort1 1.1.800.2.9.1.9.1.1.14
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplAltTrackPort2 1.1.800.2.9.1.9.1.1.15
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplAltTrackPort3 1.1.800.2.9.1.9.1.1.16
Alternate port under failure conditions and will be supported in future release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplLgclChanRedirect 1.1.800.2.9.1.9.1.1.17
Permits the user to allow or not allow logical channel redirects
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER notAllowed(1), allowed(2)  

xylnatmVplAAL5Discard 1.1.800.2.9.1.9.1.1.18
This field configures an action that IOP should take against cells when traffic congestion occurs. earlyPktDiscard(1) is treated as 'enable' for IOP version 1 since it doesn't support early packet discard feature. Early packet discard is an IOP 2 feature. In this mode, IOP either passes or discards all the cells of a packet. It passes all cells of a packet during congestion if the first cell of the packet has been passed. Cells are marked when GCRA contract is violated. This option does not apply to VBR_RT and CBR and CBR_PRS. disable(2) is selected to disable early packet discard and partial discard feature. Cells are discarded when needed during congestion. Cells are marked when GCRA contract is violated. partialPktDiscard(3) is an IOP 2 feature. IOP starts discarding cells--all of the remaining cells except for the last cell of the packet-when congestion occurs. When congestion ends, the first cell of a new packet is passed. Cells are marked when GCRA contract is violated. This option does not apply to VBR_RT and CBR and CBR_PRS. The default value for IOP 1 is 'disable'. The default value is 'earlyPktDiscard' for IOP 2 if the transport type of the circuit is UBR, ABR, and VBR_NRT. 'disable' is the default VBR_RT and CBR.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER earlyPktDiscard(1), disable(2), partialPktDiscard(3)  

xylnatmVplF4F5SegEndpt 1.1.800.2.9.1.9.1.1.19
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplF4F5CopySeg 1.1.800.2.9.1.9.1.1.20
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplF4F5End2EndEndpt 1.1.800.2.9.1.9.1.1.21
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplF4F5CopyEnd2End 1.1.800.2.9.1.9.1.1.22
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplOamEndpt 1.1.800.2.9.1.9.1.1.23
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplOamCopy 1.1.800.2.9.1.9.1.1.24
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmFwdEndpt 1.1.800.2.9.1.9.1.1.25
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmFwdCopy 1.1.800.2.9.1.9.1.1.26
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmFwdGcraAdv 1.1.800.2.9.1.9.1.1.27
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmBkwdEndpt 1.1.800.2.9.1.9.1.1.28
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmBkwdCopy 1.1.800.2.9.1.9.1.1.29
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmBkwdGcraAdv 1.1.800.2.9.1.9.1.1.30
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplRmDiscard 1.1.800.2.9.1.9.1.1.31
Future release
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVplGcraAPoliceMode 1.1.800.2.9.1.9.1.1.32
Enforcement mode of GcraA as following gcraEmDxAll = Discard all cells on congestion gcraEmMarkClp0DxClp1 = On congestion discard Clp1 cells gcraEmMarkAllDxAll = On congestion mark all gcraEmMarkClp0DxAll = on congestion mark clp0 and discard all
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER gcraEmDxAll(1), gcraEmMarkClp0DxClp1(2), gcraEmMarkAllDxAll(3), gcraEmMarkClp0DxAll(4)  

xylnatmVplGcraBPoliceMode 1.1.800.2.9.1.9.1.1.33
Enforcement mode of GcraB as following gcraEmDxAll = Discard all cells on congestion gcraEmMarkClp0DxClp1 = On congestion discard Clp1 cells gcraEmMarkAllDxAll = On congestion mark all gcraEmMarkClp0DxAll = on congestion mark clp0 and discard all
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER gcraEmDxAll(1), gcraEmMarkClp0DxClp1(2), gcraEmMarkAllDxAll(3), gcraEmMarkClp0DxAll(4)  

xylnatmVplMcGroupId 1.1.800.2.9.1.9.1.1.34
Internal use of multicast group id
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplMcIngressEgress 1.1.800.2.9.1.9.1.1.35
Always ingress in this release
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER ingress(1), egress(2)  

xylnatmVplStatTable 1.1.800.2.9.1.11.1
This table contains the xylan specific statistical object
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVplStatEntry

xylnatmVplStatEntry 1.1.800.2.9.1.11.1.1
Contains the stats objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVplStatEntry  

xylnatmVplStatSlotIndex 1.1.800.2.9.1.11.1.1.1
The slot number of the chassis
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplStatPortIndex 1.1.800.2.9.1.11.1.1.2
The port number on this slot
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..25  

xylnatmVplStatVpi 1.1.800.2.9.1.11.1.1.3
The Vpi number for this connection
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplStatRxCells 1.1.800.2.9.1.11.1.1.4
The total number of cells received on this connection identified by the slot/port/vpi
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatTxCells 1.1.800.2.9.1.11.1.1.5
The total number of cells transmitted on this connection identified by the slot/port/vpi
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatRxClp0Cells 1.1.800.2.9.1.11.1.1.6
The total number of received cells with Clp0 received on this connection identified by slot/port/vpi
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatRxClp1Cells 1.1.800.2.9.1.11.1.1.7
The total number of received cells with Clp1 received on this connection identified by slot/port/vpi
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxCongClp0Cells 1.1.800.2.9.1.11.1.1.8
The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxCongClp1Cells 1.1.800.2.9.1.11.1.1.9
The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxGcraClp0Cells 1.1.800.2.9.1.11.1.1.10
The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxGcraClp1Cells 1.1.800.2.9.1.11.1.1.11
The total number of Clp1 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxGcraBClp0Cells 1.1.800.2.9.1.11.1.1.12
The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVplStatDxGcraBClp1Cells 1.1.800.2.9.1.11.1.1.13
The total number of Clp1 cells discarded due to policing on Clp0+1 cells
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

xylnatmVpCrossConnectTable 1.1.800.2.9.1.14.1
The Xyln specific ATM VP Cross Connect table. A bi- directional VP cross-connect which cross-connects two end points (i.e., VPLs) is modeled as one entry in this table. This table along with the xylan VcCrossConnect Table contains all the objects which would enable xylan NMS to create a cross connection without creating VCL's and then cross connecting them. The reason why we prefer this approach is to prevent creation of VCL's which in our architecture is actually a cross connect with all the cells coming in on that vc going to the fabric and then getting switched back on the same vc that it came in. We have also duplicated all the objects in the Vcl table so that they can be set in a single set request.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVpCrossConnectEntry

xylnatmVpCrossConnectEntry 1.1.800.2.9.1.14.1.1
An entry in the ATM VP Cross Connect table. This entry is used to model a bi-directional ATM VP cross-connect cross-connecting two end points.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVpCrossConnectEntry  

xylnatmVpCrossConnectLowSlotIndex 1.1.800.2.9.1.14.1.1.1
The low slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmVpCrossConnectLowPortIndex 1.1.800.2.9.1.14.1.1.2
The low physical port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVpCrossConnectLowVpi 1.1.800.2.9.1.14.1.1.3
The value of this object is equal to the VPI value at the ATM interface associated with the VP cross-connect that is identified by atmVpCrossConnectLow(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

xylnatmVpCrossConnectHighSlotIndex 1.1.800.2.9.1.14.1.1.4
The value of the high slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmVpCrossConnectHighPortIndex 1.1.800.2.9.1.14.1.1.5
The high physical port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVpCrossConnectHighVpi 1.1.800.2.9.1.14.1.1.6
The value of this object is equal to the VPI value at the ATM interface associated with the VP cross-connect that is identified by atmVpCrossConnectHigh(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

xylnatmVpCrossConnectConnectionId 1.1.800.2.9.1.14.1.1.7
The status of this object indicates whether the said Vc Cross Connection is the parent or a child. If the connection status is unknown, then the value of this object is unknown. Only deletion of the parent is possible when all the child connections have been disconnected. To delete all all parent and child connections, use the VCL table to delete the low VCL.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER multicastParent(1), multicastChild(2), nonMulticastParent(3), unknown(4)  

xylnatmVpCrossConnectLowRxTrafficDescrIndex 1.1.800.2.9.1.14.1.1.8
The receive traffic descriptor index. The reason why we duplicate this index is to allow the user to change the traffic descriptor without deleting the connection AND without any changes to the RFC1695.mib. RFC1695 describes the traffic descriptor indices only the vcl/vpl tables. Hence if the user wishes to change the TD after creating the cross-connection, then the user has to delete the cross connection to ensire that the receive direction of the low end of the cross connect is equal to the transmit direction of the other VCL at the high end of the cross connect. 10/18/96. Since we dont want to create Vcl without cross connecting them, NMS will now call this table which would allow the creation/deletion and modification of Cross Connect Entries.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVpCrossConnectLowTxTrafficDescrIndex 1.1.800.2.9.1.14.1.1.9
The transmit traffic descriptor index. The reason why we duplicate this index is to allow the user to change the traffic descriptor without deleting the connection AND without any changes to the RFC1695.mib. RFC1695 describes the traffic descriptor indices only the vcl/vpl tables. Hence if the user wishes to change the TD after creating the cross-connection, then the user has to delete the cross connection to ensire that the receive direction of the low end of the cross connect is equal to the transmit direction of the other VCL at the high end of the cross connect. 10/18/96. Since we dont want to create Vcl without cross connecting them, NMS will now call this table which would allow the creation/deletion and modification of Cross Connect Entries.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVpCrossConnectMCastEnable 1.1.800.2.9.1.14.1.1.10
Whether Mcast should be enabled/disabled for this connection
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

xylnatmVpCrossConnectL2HLastChange 1.1.800.2.9.1.14.1.1.11
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in low to high direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

xylnatmVpCrossConnectH2LLastChange 1.1.800.2.9.1.14.1.1.12
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in high to low direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

xylnatmVpCrossConnectL2HOperStatus 1.1.800.2.9.1.14.1.1.13
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the low to high direction). The up and down states indicate that this ATM VC cross-connect from low to high direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

xylnatmVpCrossConnectH2LOperStatus 1.1.800.2.9.1.14.1.1.14
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the high to low direction). The up and down states indicate that this ATM VC cross-connect from high to low direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

xylnatmVpCrossConnectVcType 1.1.800.2.9.1.14.1.1.15
The type of VC...Permanent/Switched/Soft/control
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER pvc(1), svc(2), softPvc(3), control(4)  

xylnatmVpCrossConnectPvcIdentifier 1.1.800.2.9.1.14.1.1.16
This is required by NMS to id PVC's across networks
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVpCrossConnectRowStatus 1.1.800.2.9.1.14.1.1.17
This object is used to create, delete or modify a row in this table. To create a new CrossConnect, 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: xylnatmVcCrossConnectLowRxTrafficDescrIndex, xylnatmVcCrossConnectLowTxTrafficDescrIndex. Xylan implements createAndWait along with create&Go as create. Create is basically a superset. In addition, if the local VCL end-point is also the VCC end-point
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

xylnatmVcCrossConnectTable 1.1.800.2.9.1.13.1
The ATM VC Cross Connect table. A bi- directional VC cross-connect which cross-connects two end points (i.e., VCLs) is modeled as one entry in this table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVcCrossConnectEntry

xylnatmVcCrossConnectEntry 1.1.800.2.9.1.13.1.1
An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVcCrossConnectEntry  

xylnatmVcCrossConnectLowSlotIndex 1.1.800.2.9.1.13.1.1.1
The incoming slot number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectLowPortIndex 1.1.800.2.9.1.13.1.1.2
The value of this object is equal to the ATM interface port in this slot for this VC cross-connect. The term low implies that this ATM interface has the numerically lower slot/port value than the other ATM interface identified in the same atmVcCrossConnectEntry.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectLowVpi 1.1.800.2.9.1.13.1.1.3
The value of this object is equal to the VPI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectLow(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

xylnatmVcCrossConnectLowVci 1.1.800.2.9.1.13.1.1.4
The value of this object is equal to the VCI value at the ATM interface associated with this VC cross-connect that is identified by atmVcCrossConnectLow(Slot/Port)Index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the low ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

xylnatmVcCrossConnectHighSlotIndex 1.1.800.2.9.1.13.1.1.5
The high port number
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmVcCrossConnectHighPortIndex 1.1.800.2.9.1.13.1.1.6
The value of this object is equal to the ATM interface port in this slot for this VC cross-connect. The term high implies that this VC cross-connect that this ATM interface has the numerically higher slot/port value than the other ATM interface identified in the same atmVcCrossConnectEntry.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectHighVpi 1.1.800.2.9.1.13.1.1.7
The value of this object is equal to the VPI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectHigh(Slot/Port)Index. The VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..4095  

xylnatmVcCrossConnectHighVci 1.1.800.2.9.1.13.1.1.8
The value of this object is equal to the VCI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectHigh(Slot/Port)Index. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the high ATM interface port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..65535  

xylnatmVcCrossConnectConnectionId 1.1.800.2.9.1.13.1.1.9
The status of this object indicates whether the said Vc Cross Connection is the parent or a child. If the connection status is unknown, then the value of this object is unknown. Only deletion of the parent is possible when all the child connections have been disconnected. To delete all all parent and child connections, use the VCL table to delete the low VCL.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER multicastParent(1), multicastChild(2), nonMulticastParent(3), unknown(4)  

xylnatmVcCrossConnectLowRxTrafficDescrIndex 1.1.800.2.9.1.13.1.1.10
The receive traffic descriptor index. The reason why we duplicate this index is to allow the user to change the traffic descriptor without deleting the connection AND without any changes to the RFC1695.mib. RFC1695 describes the traffic descriptor indices only the vcl/vpl tables. Hence if the user wishes to change the TD after creating the cross-connection, then the user has to delete the cross connection to ensire that the receive direction of the low end of the cross connect is equal to the transmit direction of the other VCL at the high end of the cross connect. 10/18/96. Since we dont want to create Vcl without cross connecting them, NMS will now call this table which would allow the creation/deletion and modification of Cross Connect Entries.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectLowTxTrafficDescrIndex 1.1.800.2.9.1.13.1.1.11
The transmit traffic descriptor index. The reason why we duplicate this index is to allow the user to change the traffic descriptor without deleting the connection AND without any changes to the RFC1695.mib. RFC1695 describes the traffic descriptor indices only the vcl/vpl tables. Hence if the user wishes to change the TD after creating the cross-connection, then the user has to delete the cross connection to ensire that the receive direction of the low end of the cross connect is equal to the transmit direction of the other VCL at the high end of the cross connect. 10/18/96. Since we dont want to create Vcl without cross connecting them, NMS will now call this table which would allow the creation/deletion and modification of Cross Connect Entries.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectMCastEnable 1.1.800.2.9.1.13.1.1.12
Enable/disable multicast as per the ui
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

xylnatmVcCrossConnectL2HLastChange 1.1.800.2.9.1.13.1.1.13
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in low to high direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

xylnatmVcCrossConnectH2LLastChange 1.1.800.2.9.1.13.1.1.14
The value of MIB II's sysUpTime object at the time this VC cross-connect entered its current operational state in high to low direction. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

xylnatmVcCrossConnectL2HOperStatus 1.1.800.2.9.1.13.1.1.15
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the low to high direction). The up and down states indicate that this ATM VC cross-connect from low to high direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

xylnatmVcCrossConnectH2LOperStatus 1.1.800.2.9.1.13.1.1.16
The value of this object identifies the current operational status of the VC cross-connect in one direction; (i.e., from the high to low direction). The up and down states indicate that this ATM VC cross-connect from high to low direction is operational or not operational respectively. The unknown state indicates that the state of it cannot be determined.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), end2endup(2), end2endDown(3), localUpEndToEndUnknown(4), localDown(5)  

xylnatmVcCrossConnectVcType 1.1.800.2.9.1.13.1.1.17
The type of VC...Permanent/Switched/ Soft/control
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER pvc(1), svc(2), softPvc(3), control(4)  

xylnatmVcCrossConnectPvcIdentifier 1.1.800.2.9.1.13.1.1.18
This is required by NMS to identify PVC's across networks
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVcCrossConnectRowStatus 1.1.800.2.9.1.13.1.1.19
This object is used to create, delete or modify a row in this table. To create a new CrossConnect, 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: xylnatmVcCrossConnectLowRxTrafficDescrIndex, xylnatmVcCrossConnectLowTxTrafficDescrIndex. Xylan implements createAndWait along with create&Go as create. Create is basically a superset. In addition, if the local VCL end-point is also the VCC end-point
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4), notActive(5)  

xylnatmVplModTable 1.1.800.2.9.1.16.1
This table contains xylan implementation specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVplModEntry

xylnatmVplModEntry 1.1.800.2.9.1.16.1.1
List of xylan specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVplModEntry  

xylnatmVplModSlotIndex 1.1.800.2.9.1.16.1.1.1
Slot Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplModPortIndex 1.1.800.2.9.1.16.1.1.2
Port Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplModVplVpi 1.1.800.2.9.1.16.1.1.3
Vpi instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVplModDestSlotIndex 1.1.800.2.9.1.16.1.1.4
Slot Instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVplModDestPortIndex 1.1.800.2.9.1.16.1.1.5
Port Instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVplModDestVplVpi 1.1.800.2.9.1.16.1.1.6
Vpi instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVplModDestStatus 1.1.800.2.9.1.16.1.1.7
To be in sync with the ui we allow modification
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4)  

xylnatmVclModTable 1.1.800.2.9.1.15.1
This table contains xylan implementation specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmVclModEntry

xylnatmVclModEntry 1.1.800.2.9.1.15.1.1
List of xylan specific objects
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmVclModEntry  

xylnatmVclModSlotIndex 1.1.800.2.9.1.15.1.1.1
Slot Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclModPortIndex 1.1.800.2.9.1.15.1.1.2
Port Instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclModVclVpi 1.1.800.2.9.1.15.1.1.3
Vpi instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclModVclVci 1.1.800.2.9.1.15.1.1.4
Vci instance
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

xylnatmVclModDestSlotIndex 1.1.800.2.9.1.15.1.1.5
Slot Instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVclModDestPortIndex 1.1.800.2.9.1.15.1.1.6
Port Instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVclModDestVclVpi 1.1.800.2.9.1.15.1.1.7
Vpi instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVclModDestVclVci 1.1.800.2.9.1.15.1.1.8
Vci instance
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmVclModDestStatus 1.1.800.2.9.1.15.1.1.9
To be in sync with the ui we allow modification
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER create(1), modify(2), delete(3), active(4)  

xylnatmClockingxCtrlTable 1.1.800.2.9.1.17.1
A table of Clocking configuration and control information.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmClockingxCtrlEntry

xylnatmClockingxCtrlEntry 1.1.800.2.9.1.17.1.1
An entry in the Clocking Configuration/control table, containing information about Cell Switching Module (CSM) clocking.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmClockingxCtrlEntry  

xylnatmClockingxCtrlBusLine 1.1.800.2.9.1.17.1.1.1
The Bus Signal function used for clocking CSM modules. This is used as a unique ID to identify a clocking line on the bus.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER eightKhz(1), nineteenMhz(2)  

xylnatmClockingxCtrlSrcLevel 1.1.800.2.9.1.17.1.1.2
This object identifies which source entry type for this row in the table. Primary is the preffered source, if the primary source clock is not available, then the secondary source (if configured) will be used to drive the bus line. If the primary and secondary are both configured but not available, then the tertiary (if configured) source will be used. If no clock sources are available for this bus line, then all port configured to use the bus line for their local (transmit) clocking, then those ports will switch to their local on-board oscillator.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER primary(1), secondary(2), tertiary(3)  

xylnatmClockingxSrcOperState 1.1.800.2.9.1.17.1.1.3
This object identifies the state of the clock source. inactive(1) indicates the source is not available for use. active(2) indicates the source is currently being used to drive the bus. standby(3) indicates the source is currently availble for use, but another source is currently being used.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER inactive(1), active(2), standby(3)  

xylnatmClockingxSrcType 1.1.800.2.9.1.17.1.1.4
This object controls the type of clock used as the source for the bus line. If 'notConfigured', then this source isn't configured. If 'receiveDataDerived' then the source of the clock comes from the specified port's receive data (e.g. calculated using a Phase Lock loop off the receive data line). If 'onboardOscillator' then the source of the clock comes from the on-board oscillator associated with this port. Currently (as of release 3.2) this is only valid with 19.44 Mhz clocking, and not valid for 8 Khz clocking.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER notConfigured(1), receiveDataDerived(2), onboardOscillator(3)  

xylnatmClockingxCtrlSlot 1.1.800.2.9.1.17.1.1.5
This object is used to configure the slot of the port used to drive the bus. This object will return 0 if not configured. For setting this object only a non-zero value is allowed and it must be a valid CSM slot.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..9  

xylnatmClockingxCtrlPort 1.1.800.2.9.1.17.1.1.6
This object is used to configure the port number used to drive the bus. This object will return 0 if not configured. For setting this object only a non-zero value is allowed and it must be a valid CSM port that can drive the bus at the proper 8 Khz or 19.44 Mhz speed.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..64  

xylnatmClockingxGlobalCST 1.1.800.2.9.1.17.2
This object is used to specify the time period (in seconds) that the primary clock source should be up before the switching software resumes its role in driving the bus line. If the clock source goes down within this time period, the secondary source continues to drive the bus line. This prevents the software from doing the switching too often when the clock source isn't stable.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..10000  

xylnatmTrafficShaperConfTable 1.1.800.2.9.1.18.1
A table of Traffic Shapers' configuration information. Currently, traffic shaping function is available on module types CSM-AB-OC3 and CSM-AB-DS3/E3 only.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmTrafficShaperConfEntry

xylnatmTrafficShaperConfEntry 1.1.800.2.9.1.18.1.1
An entry in the Traffic Shaper Configuration table containing parameters of the traffic shapers of cell switching module.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmTrafficShaperConfEntry  

xylnatmTrafficShaperConfSlotIndex 1.1.800.2.9.1.18.1.1.1
The slot on which the traffic shaping module resides.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmTrafficShaperConfPortIndex 1.1.800.2.9.1.18.1.1.2
The port on which traffic shaping circuitry resides. A CSM-AB module can have either one or two traffic shaping ports. If the module has one traffic shaping port, then the traffic shaping circuitry is always installed on the first port of the module.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

xylnatmTrafficShaperConfTsNumIndex 1.1.800.2.9.1.18.1.1.3
This object identifies the traffic shaper number on the port. On each port, there are eight traffic shapers whose bandwidth are allocated based on configurabled parameters Cell Delay Variation (CDV), Peak Cell Rate (PCR), Sustainable Cell Rate (SCR) and Maximum Brust Size (MBS).
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..8  

xylnatmTrafficShaperConfCDV 1.1.800.2.9.1.18.1.1.4
This object is used to specify the Cell Delay Variation of the outgoing cell stream of a shaper. CDV is one of the parameters configured to alter the characteristics of the cell streams to acquire a desired QOS objective. It is the variation in the delay time, induced by buffering cell scheduling, experienced by a cell at network entry and exit points. CDV must be between 7 and 1000 uSec.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 7..1000  

xylnatmTrafficShaperConfPCR 1.1.800.2.9.1.18.1.1.5
This object is used to configure the Peak Cell Rate of a shaper. PCR is one of the parameters set to alter the characteristics of the cell streams to acquire a desired QOS objective. It is the maximum instantaneous cell rate at which the cell streams are transmited. PCR must be greater than 0 and not exceeds the maximum bandwidth of the physical interface. The bandwidth of the physical interface is devided up to 8 shapers, by default, shaper 8 has the highest bandwidth. PCR value must not exceed the remaining bandwidth of the interface.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmTrafficShaperConfSCR 1.1.800.2.9.1.18.1.1.6
This object is used to configure the Sustainable Cell Rate of a shaper. SCR is the average conforming cell rate an ATM connection measured over a time interval. This measurement allows the network to allocate sufficient resources that are less than those based on PCR and still ensure the achievement of the desired QOS. SCR could be unspecified, value set to 0. If specified, SCR value must be less than the PCR value.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmTrafficShaperConfMBS 1.1.800.2.9.1.18.1.1.7
This object is used to configure the Maximum Brust Size of the outgoing cell streams of a shaper. MBS is one of the parameters set to alter the characteristics of the cell streams to acquire a desired QOS objective. It is the maximum number of back to back cells that can be sent at the peak cell rate. MBS could be unspecified, value set to 0.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmTrafficShaperMemTable 1.1.800.2.9.1.19.1
A table of Traffic Shapers' VPI/VCI Membership information. Currently, traffic shaping function is available on module types CSM-AB-OC3 and CSM-AB-DS3/E3 only. To have the outgoing cell streams of a connection shaped to a desired characteristic of a shaper, its VPI/VCI needs to be registered to one of the traffic shapers (1..7) of the port. Shaper number eight is designated as the default shaper where cell streams of non-specified VPI/VCI's are routed to. Therefore, VPI/VCI is not registrable to shaper eight.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    XylnatmTrafficShaperMemEntry

xylnatmTrafficShaperMemEntry 1.1.800.2.9.1.19.1.1
An entry in the Traffic Shaper Membership table containing a VPI/VCI number mapping to a traffic shaper number.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  XylnatmTrafficShaperMemEntry  

xylnatmTrafficShaperMemSlotIndex 1.1.800.2.9.1.19.1.1.1
The slot on which the traffic shaping module resides.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..9  

xylnatmTrafficShaperMemPortIndex 1.1.800.2.9.1.19.1.1.2
The port on which traffic shaping circuitry resides. A CSM-AB module can have either one or two traffic shaping ports. If the module has one traffic shaping port, then the traffic shaping circuitry is always installed on the first port of the module.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

xylnatmTrafficShaperMemTsNumIndex 1.1.800.2.9.1.19.1.1.3
This object identifies the traffic shaper number on the port. Each port provides mapping of up to 512 VPI/VCI to the eight shapers. Non-specified VPI/VCI is logically mapped to the default shaper (shaper 8). Therefore, VPI/VCI is not registrable to shaper 8.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..7  

xylnatmTrafficShaperMemVpiNumIndex 1.1.800.2.9.1.19.1.1.4
This object is used to register a VPI to a traffic shaper. The outgoing cell streams with this VPI is shaped by the traffic shaper it registers to. The valid range is 1-[2^(max_vpi_bits of slot/port) -1].
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmTrafficShaperMemVciNumIndex 1.1.800.2.9.1.19.1.1.5
This object is used to register a VCI to a traffic shaper. The outgoing cell streams with this VCI is shaped by the traffic shaper it registers to. The valid range is 1-[2^(9-max_vpi_bits of slot port) -1].
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

xylnatmTrafficShaperMemVpiOper 1.1.800.2.9.1.19.1.1.6
This object is used to register or de-register a VPI/VCI to or out of a traffic shaper. none(1) when VPI/VCI is not registered/ de-register to/from the shaper. No operation. add(2) registers the VPI/VCI to the shaper. Its outgoing cell stream is shaped based on the characteristics of the shaper. rem(3) de-registers the VPI/VCI out of the shaper. When a VPI/VCI is not register to one of the seven shapers (1..7), its outgoing traffic is logically routed to the default shaper (shaper 8) and shaped based on traffic characteristics of shaper 8.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER none(1), add(2), rem(3)  

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor