XYLAN-CSM-MIB

All MIBs › XYLAN-CSM-MIB

Category: Xylan OmniSwitch

Description:

Manages Xylan OmniSwitch Cell Switching Module configuration, ATM parameters, and service mappings.

Imported Objects

OBJECT-TYPE

From RFC1155-SMI

Counter
IpAddress

From RFC1213-MIB

DisplayString
ifIndex

From XYLAN-BASE-MIB

xylanCsmArch

OBJECT-IDENTITY

What Is XYLAN-CSM-MIB?

XYLAN-CSM-MIB is a Xylan (later Alcatel OmniSwitch) private MIB for the Cell Switching Module, an ATM-oriented line/service card used in Xylan OmniSwitch chassis. Based on its name and vendor context it would expose ATM interface configuration, cell-switching parameters, and service mapping data for the module. No module description or sample objects were available for this MIB, so specific object-level detail cannot be confirmed from source; its role would nonetheless be to support monitoring of the CSM card's operational and configuration status within the switch chassis. It would depend on the broader Xylan/OmniSwitch chassis and possibly standard ATM MIB concepts for full context. Deployment context is Xylan/Alcatel OmniSwitch chassis-based switches used for ATM/cell-relay services in enterprise or carrier networks. Without vendor documentation available, an administrator would typically load XYLAN-CSM-MIB in a MIB Browser simply to enumerate its object tree and infer likely ATM and cell-switching parameters from naming conventions alone.

IPNetwork Monitor allows you to monitor SNMP objects defined in XYLAN-CSM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Xylan/Alcatel OmniSwitch chassis with Cell Switching Module

Monitoring Examples

No sample objects were provided for this MIB, so no concrete object-level monitoring scenario can be honestly described; based on the module name, an admin would be expected to check CSM card and ATM port/service-mapping status, but the specific tables and object names cannot be confirmed without source access.

OIDs

OID symbolic	OID numeric	Type	Access	Description
INT atmxInterfaceAddressType	1.3.6.1.4.1.800.2.9.1.2.1.1.11	INTEGER	read-only	The type of primary ATM address configured for use at this ATM interface.
atmxInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.2.1.1		not-accessible	This list contains ATM interface configuration parameters and state variables.
atmxInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.2
atmxInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.2.1		not-accessible	This table contains ATM local interface configuration parameters, one entry per ATM interface port.
INT atmxInterfaceConfVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.6	INTEGER	read-only	The number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
INT atmxInterfaceConfVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.5	INTEGER	read-only	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.
INT atmxInterfaceIlmiVci	1.3.6.1.4.1.800.2.9.1.2.1.1.10	INTEGER	read-only	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.
INT atmxInterfaceIlmiVpi	1.3.6.1.4.1.800.2.9.1.2.1.1.9	INTEGER	read-only	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.
INT atmxInterfaceMaxActiveVciBits	1.3.6.1.4.1.800.2.9.1.2.1.1.8	INTEGER	read-write	The maximum number of active VCI bits configured for use at this ATM interface.
INT atmxInterfaceMaxActiveVpiBits	1.3.6.1.4.1.800.2.9.1.2.1.1.7	INTEGER	read-write	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.
INT atmxInterfaceMaxVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.4	INTEGER	read-only	The maximum number of VCCs (PVCs and SVCs) supported at this ATM interface.
INT atmxInterfaceMaxVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.3	INTEGER	read-only	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.
INT atmxInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.2	INTEGER	read-only	The slot number for the CSM board
INT atmxInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.1	INTEGER	read-only	The slot number of the chassis
STR atmxSvcVcCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.7.2.1.9	DisplayString	read-only	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.
atmxSvcVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.2.1		not-accessible	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.
INT atmxSvcVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.6	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.5	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVcCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.11	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.2.1.8	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.7	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.2	INTEGER	not-accessible	The incoming port for this SVC.
INT atmxSvcVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.1	INTEGER	not-accessible	The incoming slot for this SVC.
INT atmxSvcVcCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.10	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.2.1.4	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.2.1.12	INTEGER	read-only	This object is used to indicate the status of the SVC in the atmSvcVcCrossConnectTable.
atmxSvcVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.2		not-accessible	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.
STR atmxSvcVpCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.5.2.1.7	DisplayString	read-only	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.
atmxSvcVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.2.1		not-accessible	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.
INT atmxSvcVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.5	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.4	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVpCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.9	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.6	INTEGER	not-accessible	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.
INT atmxSvcVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.2	INTEGER	not-accessible	The incoming slot for this SVC
INT atmxSvcVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.1	INTEGER	not-accessible	The low slot of the SVC VP cross-connect.
INT atmxSvcVpCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.8	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.2.1.10	INTEGER	read-only	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
atmxSvcVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.2		not-accessible	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.
atmxTrafficDescrGroup	1.3.6.1.4.1.800.2.9.1.8
INT atmxTrafficDescrParam1	1.3.6.1.4.1.800.2.9.1.8.1.1.3	INTEGER	read-write	The first parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam2	1.3.6.1.4.1.800.2.9.1.8.1.1.4	INTEGER	read-write	The second parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam3	1.3.6.1.4.1.800.2.9.1.8.1.1.5	INTEGER	read-write	The third parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam4	1.3.6.1.4.1.800.2.9.1.8.1.1.6	INTEGER	read-write	The fourth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam5	1.3.6.1.4.1.800.2.9.1.8.1.1.7	INTEGER	read-write	The fifth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
atmxTrafficDescrParamEntry	1.3.6.1.4.1.800.2.9.1.8.1.1		not-accessible	This list contains ATM traffic descriptor type and the associated parameters.
ATM atmxTrafficDescrParamIndex	1.3.6.1.4.1.800.2.9.1.8.1.1.1	AtmxTrafficDescrParamIndex	read-only	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
atmxTrafficDescrParamTable	1.3.6.1.4.1.800.2.9.1.8.1		not-accessible	This table contains information on ATM traffic descriptor type and the associated parameters.
INT atmxTrafficDescrRowStatus	1.3.6.1.4.1.800.2.9.1.8.1.1.9	INTEGER	read-write	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
INT atmxTrafficDescrType	1.3.6.1.4.1.800.2.9.1.8.1.1.2	INTEGER	read-write	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.
INT atmxTrafficQoSClass	1.3.6.1.4.1.800.2.9.1.8.1.1.8	INTEGER	read-write	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.
INT atmxVccAal5CpcsReceiveSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.12	INTEGER	read-write	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.
INT atmxVccAal5CpcsTransmitSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.11	INTEGER	read-write	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.
INT atmxVccAal5EncapsType	1.3.6.1.4.1.800.2.9.1.3.1.1.13	INTEGER	read-write	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.
INT atmxVccAalType	1.3.6.1.4.1.800.2.9.1.3.1.1.10	INTEGER	read-write	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.
INT atmxVcCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.10	INTEGER	read-write	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.
atmxVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.1.1		not-accessible	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.
atmxVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.7
STR atmxVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.14	DisplayString	read-only	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.
INT atmxVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.12	INTEGER	read-only	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.
INT atmxVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.7	INTEGER	read-only	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.
INT atmxVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.6	INTEGER	read-only	The high port number
INT atmxVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.1.1.9	INTEGER	read-only	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.
INT atmxVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.8	INTEGER	read-only	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.
INT atmxVcCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.1	INTEGER	read-only	A unique value to identify this VC Cross Connect
STR atmxVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.13	DisplayString	read-only	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.
INT atmxVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.11	INTEGER	read-only	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.
INT atmxVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.3	INTEGER	read-only	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.
INT atmxVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.2	INTEGER	read-only	The low port number
INT atmxVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.1.1.5	INTEGER	read-only	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.
INT atmxVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.4	INTEGER	read-only	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.
INT atmxVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.15	INTEGER	read-write	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.
atmxVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.1		not-accessible	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.
INT atmxVclAdminStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.5	INTEGER	read-write	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.
INT atmxVclBidirect	1.3.6.1.4.1.800.2.9.1.3.1.1.16	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
INT atmxVclCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.3.1.1.14	INTEGER	read-only	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.
atmxVclEntry	1.3.6.1.4.1.800.2.9.1.3.1.1		not-accessible	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.
atmxVclGroup	1.3.6.1.4.1.800.2.9.1.3
STR atmxVclLastChange	1.3.6.1.4.1.800.2.9.1.3.1.1.7	DisplayString	read-only	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.
INT atmxVclOperStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.6	INTEGER	read-only	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.
INT atmxVclPortIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.2	INTEGER	read-only	The port number of the csm board
ATM atmxVclReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.
INT atmxVclRowStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.15	INTEGER	read-write	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.
INT atmxVclSlotIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.1	INTEGER	read-only	The slot number
atmxVclTable	1.3.6.1.4.1.800.2.9.1.3.1		not-accessible	The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table.
ATM atmxVclTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.9	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.
INT atmxVclVci	1.3.6.1.4.1.800.2.9.1.3.1.1.4	INTEGER	read-only	The VCI value of the VCL. The maximum VCI value cannot exceed the value allowable by the atmInterfaceMaxVciBits.
INT atmxVclVpi	1.3.6.1.4.1.800.2.9.1.3.1.1.3	INTEGER	read-only	The VPI value of the VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.
INT atmxVpCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.8	INTEGER	read-write	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.
atmxVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.1.1		not-accessible	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.
atmxVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.5
STR atmxVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.12	DisplayString	read-only	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.
INT atmxVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.10	INTEGER	read-only	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.
INT atmxVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.6	INTEGER	read-only	The high physical port number
INT atmxVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.5	INTEGER	read-only	The value of the high slot number
INT atmxVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.7	INTEGER	read-only	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.
INT atmxVpCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.1	INTEGER	read-only	A unique value to identify this VP Cross Connect
STR atmxVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.11	DisplayString	read-only	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.
INT atmxVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.9	INTEGER	read-only	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.
INT atmxVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.3	INTEGER	read-only	The low physical port number
INT atmxVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.2	INTEGER	read-only	The low slot number
INT atmxVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.4	INTEGER	read-only	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.
INT atmxVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.13	INTEGER	read-write	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.
atmxVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.1		not-accessible	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.
INT atmxVplAdminStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.4	INTEGER	read-write	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.
INT atmxVplBidirect	1.3.6.1.4.1.800.2.9.1.1.1.1.11	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
INT atmxVplCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.1.1.1.9	INTEGER	read-only	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.
atmxVplEntry	1.3.6.1.4.1.800.2.9.1.1.1.1		not-accessible	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.
atmxVplGroup	1.3.6.1.4.1.800.2.9.1.1
STR atmxVplLastChange	1.3.6.1.4.1.800.2.9.1.1.1.1.6	DisplayString	read-only	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.
INT atmxVplOperStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.5	INTEGER	read-only	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.
INT atmxVplPortIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.2	INTEGER	read-only	The port number of the csm board
ATM atmxVplReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.7	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the receive direction of the VPL.
INT atmxVplRowStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.10	INTEGER	read-write	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..
INT atmxVplSlotIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.1	INTEGER	read-only	The slot number of the chassis
atmxVplTable	1.3.6.1.4.1.800.2.9.1.1.1		not-accessible	The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table.
ATM atmxVplTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the transmit direction of the VPL.
INT atmxVplVpi	1.3.6.1.4.1.800.2.9.1.1.1.1.3	INTEGER	read-only	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.
xylanCsmMIB	1.3.6.1.4.1.800.2.9.1
INT xylnatmClockingxCtrlBusLine	1.3.6.1.4.1.800.2.9.1.17.1.1.1	INTEGER	read-only	The Bus Signal function used for clocking CSM modules. This is used as a unique ID to identify a clocking line on the bus.
xylnatmClockingxCtrlEntry	1.3.6.1.4.1.800.2.9.1.17.1.1		not-accessible	An entry in the Clocking Configuration/control table, containing information about Cell Switching Module (CSM) clocking.
xylnatmClockingxCtrlGroup	1.3.6.1.4.1.800.2.9.1.17
INT xylnatmClockingxCtrlPort	1.3.6.1.4.1.800.2.9.1.17.1.1.6	INTEGER	read-write	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.
INT xylnatmClockingxCtrlSlot	1.3.6.1.4.1.800.2.9.1.17.1.1.5	INTEGER	read-write	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.
INT xylnatmClockingxCtrlSrcLevel	1.3.6.1.4.1.800.2.9.1.17.1.1.2	INTEGER	read-only	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.
xylnatmClockingxCtrlTable	1.3.6.1.4.1.800.2.9.1.17.1		not-accessible	A table of Clocking configuration and control information.
INT xylnatmClockingxGlobalCST	1.3.6.1.4.1.800.2.9.1.17.2	INTEGER	read-write	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.
INT xylnatmClockingxSrcOperState	1.3.6.1.4.1.800.2.9.1.17.1.1.3	INTEGER	read-only	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.
INT xylnatmClockingxSrcType	1.3.6.1.4.1.800.2.9.1.17.1.1.4	INTEGER	read-write	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.
INT xylnatmILMIConfAutoCfgCurIf	1.3.6.1.4.1.800.2.9.1.4.3.1.11	INTEGER	read-write	Current operational interface type for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.13	INTEGER	read-only	Current ILMI version running on this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.12	INTEGER	read-only	Current operational signaling version for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgDfltIf	1.3.6.1.4.1.800.2.9.1.4.3.1.9	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgDfltSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.10	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.6	INTEGER	read-write	Indicate whether CSM auto cfg is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgStatus	1.3.6.1.4.1.800.2.9.1.4.3.1.7	INTEGER	read-only	The status of auto configuration procedure on this port, or this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgTrigg	1.3.6.1.4.1.800.2.9.1.4.3.1.8	INTEGER	read-write	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
xylnatmILMIConfEntry	1.3.6.1.4.1.800.2.9.1.4.3.1		not-accessible	This list contains CSM ILMI configuration and state variables
INT xylnatmILMIConfILMIEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.4	INTEGER	read-write	Indicate whether ILMI is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfILMIPollEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.5	INTEGER	read-write	Indicate whether ILMI polling is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfInstance	1.3.6.1.4.1.800.2.9.1.4.3.1.3	INTEGER	read-only	The Virtual UNI/NNI instance this entry represents
INT xylnatmILMIConfPeerDevType	1.3.6.1.4.1.800.2.9.1.4.3.1.16	INTEGER	read-only	The device type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.18	INTEGER	read-only	The ILMI version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerNNISigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.17	INTEGER	read-only	The NNI signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerUniType	1.3.6.1.4.1.800.2.9.1.4.3.1.14	INTEGER	read-only	The UNI type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerUniVer	1.3.6.1.4.1.800.2.9.1.4.3.1.15	INTEGER	read-only	The signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPort	1.3.6.1.4.1.800.2.9.1.4.3.1.2	INTEGER	read-only	The port number this entry represents
INT xylnatmILMIConfSlot	1.3.6.1.4.1.800.2.9.1.4.3.1.1	INTEGER	read-only	The slot number this entry represents
xylnatmILMIConfTable	1.3.6.1.4.1.800.2.9.1.4.3		not-accessible	This table contains CSM ILMI configuration parameters, one entry per CSM physical interface, or per virtual UNI/NNI instance
STR xylnatmInterfaceAtmAddress	1.3.6.1.4.1.800.2.9.1.4.1.1.7	DisplayString	read-write	The AtmAddress @ this interface. The AtmAddress should be a 20 octet hex number.
INT xylnatmInterfaceClearChanStats	1.3.6.1.4.1.800.2.9.1.4.1.1.16	INTEGER	read-write	True clears the chan stats
INT xylnatmInterfaceClearPortStats	1.3.6.1.4.1.800.2.9.1.4.1.1.15	INTEGER	read-write	True clears the stats for this port
INT xylnatmInterfaceClearSlotStats	1.3.6.1.4.1.800.2.9.1.4.1.1.17	INTEGER	read-write	True clears all the port stats in this slot.
xylnatmInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.4.1.1		not-accessible	This list contains xyln specific ATM interface configuration parameters and state variables.
xylnatmInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.4
xylnatmInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.4.1		not-accessible	This table contains the private ATM local interface configuration parameters, one entry per ATM interface port.
INT xylnatmInterfaceCutOverPort	1.3.6.1.4.1.800.2.9.1.4.1.1.14	INTEGER	read-write	The Cut Over Port number of the chassis
INT xylnatmInterfaceCutOverSlot	1.3.6.1.4.1.800.2.9.1.4.1.1.13	INTEGER	read-write	The Cut-Over slot number of the chassis
STR xylnatmInterfaceDescription	1.3.6.1.4.1.800.2.9.1.4.1.1.3	DisplayString	read-write	The name in ascii characters describing the interface
INT xylnatmInterfaceIlmiState	1.3.6.1.4.1.800.2.9.1.4.1.1.19	INTEGER	read-write	The state of Ilmi for the instanced port. Setting this object to disable, would prevent any ILMI queries being sent out on this port.
INT xylnatmInterfaceIlmiStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.11	INTEGER	read-only	The Ilmi Status @ this interface.
INT xylnatmInterfaceLocalSrc	1.3.6.1.4.1.800.2.9.1.4.1.1.21	INTEGER	read-write	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.
INT xylnatmInterfaceMediaType	1.3.6.1.4.1.800.2.9.1.4.1.1.6	INTEGER	read-only	The physical media type from this physical port
INT xylnatmInterfaceOperStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.9	INTEGER	read-only	The Oper status @ this interface is reflected by the status of the object.
INT xylnatmInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.2	INTEGER	read-only	The port number of the chassis
INT xylnatmInterfacePortMode	1.3.6.1.4.1.800.2.9.1.4.1.1.8	INTEGER	read-only	This object describes whether this interface is switched off or allowing traffic to pass thru or is in normal mode.
INT xylnatmInterfaceQsaalStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.10	INTEGER	read-only	The QSAAL status @ this interface is reflected by the status of the object.
INT xylnatmInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.1	INTEGER	read-only	The slot number of the chassis
CTR xylnatmInterfaceStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.10	Counter	read-only	The number of Clp0 cells discarded due to congestion
CTR xylnatmInterfaceStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.11	Counter	read-only	The number of Clp1 cells discarded due to congestion
CTR xylnatmInterfaceStatDxGcrabClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.14	Counter	read-only	The total number of Clp0 cells discarded due to policing on cell loss priority zero cells
CTR xylnatmInterfaceStatDxGcrabClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.15	Counter	read-only	The total number of cell loss prioity one cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.12	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.13	Counter	read-only	The total number of cell loss priority one cells discarded due to policing on Clp0+1 cells
xylnatmInterfaceStatEntry	1.3.6.1.4.1.800.2.9.1.6.1.1		not-accessible	This list contains xylan specific ATM interface configuration parameters and state variables
xylnatmInterfaceStatGroup	1.3.6.1.4.1.800.2.9.1.6
CTR xylnatmInterfaceStatMarkEfciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.7	Counter	read-only	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
CTR xylnatmInterfaceStatMarkGcraCells	1.3.6.1.4.1.800.2.9.1.6.1.1.8	Counter	read-only	The number of cells marked by policing that violated their traffic contract for clp0+1 cells
INT xylnatmInterfaceStatPortIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.2	INTEGER	read-only	The port number in this slot
CTR xylnatmInterfaceStatRemainingRxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.21	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created and cells can be received.
CTR xylnatmInterfaceStatRemainingTxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.22	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created for cells to be transmitted
CTR xylnatmInterfaceStatRxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.3	Counter	read-only	The total number of Received Cells at this interface (OC3, OC12, ATM25...)
CTR xylnatmInterfaceStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.4	Counter	read-only	The total number of received cells at this interface with Cell loss priority of zero
CTR xylnatmInterfaceStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.5	Counter	read-only	The total number of received cells at this interface with Cell loss Priority of zero or one
INT xylnatmInterfaceStatSlotIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.1	INTEGER	read-only	The slot number in the switch
xylnatmInterfaceStatTable	1.3.6.1.4.1.800.2.9.1.6.1		not-accessible	This table contains the statistical information about the interface
CTR xylnatmInterfaceStatTotalDiscardCells	1.3.6.1.4.1.800.2.9.1.6.1.1.9	Counter	read-only	The total number of cells discarded at this interface due to congestion, policing and unknown vpi/vci's
CTR xylnatmInterfaceStatTxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.6	Counter	read-only	The total number of transmitted cells at this interface
INT xylnatmInterfaceStatUniType	1.3.6.1.4.1.800.2.9.1.6.1.1.19	INTEGER	read-only	Type of UNI used on this interface...Public or Private
INT xylnatmInterfaceStatUniVersion	1.3.6.1.4.1.800.2.9.1.6.1.1.20	INTEGER	read-only	UNI Version used in the chassis
CTR xylnatmInterfaceStatUnknownVciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.18	Counter	read-only	The total number of unknown Vci cells recieved at this interface that dont correspond to any channels vci
CTR xylnatmInterfaceStatUnknownVpiCells	1.3.6.1.4.1.800.2.9.1.6.1.1.17	Counter	read-only	The total number of unknown Vpi cells recieved at this interface that dont correspond to any channels vpi
CTR xylnatmInterfaceStatUnknownVpVcCells	1.3.6.1.4.1.800.2.9.1.6.1.1.16	Counter	read-only	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
INT xylnatmInterfaceTimingMode	1.3.6.1.4.1.800.2.9.1.4.1.1.20	INTEGER	read-write	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.
INT xylnatmInterfaceTpRedirect	1.3.6.1.4.1.800.2.9.1.4.1.1.12	INTEGER	read-only	This object indicates whether Cut-Over is enabled or disabled @ this interface
INT xylnatmInterfaceTransmissionType	1.3.6.1.4.1.800.2.9.1.4.1.1.18	INTEGER	read-write	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
INT xylnatmInterfaceTransType	1.3.6.1.4.1.800.2.9.1.4.1.1.4	INTEGER	read-only	The transmission type at this interface. The type is either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b encoding method.
INT xylnatmInterfaceType	1.3.6.1.4.1.800.2.9.1.4.1.1.5	INTEGER	read-write	The signaling type at this interface.
INT xylnatmInterfaceUniVersion	1.3.6.1.4.1.800.2.9.1.4.1.1.22	INTEGER	read-write	UNI Version used in the chassis
INT xylnatmTrafficShaperConfCDV	1.3.6.1.4.1.800.2.9.1.18.1.1.4	INTEGER	read-write	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.
xylnatmTrafficShaperConfEntry	1.3.6.1.4.1.800.2.9.1.18.1.1		not-accessible	An entry in the Traffic Shaper Configuration table containing parameters of the traffic shapers of cell switching module.
xylnatmTrafficShaperConfGroup	1.3.6.1.4.1.800.2.9.1.18
INT xylnatmTrafficShaperConfMBS	1.3.6.1.4.1.800.2.9.1.18.1.1.7	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfPCR	1.3.6.1.4.1.800.2.9.1.18.1.1.5	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfPortIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperConfSCR	1.3.6.1.4.1.800.2.9.1.18.1.1.6	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfSlotIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
xylnatmTrafficShaperConfTable	1.3.6.1.4.1.800.2.9.1.18.1		not-accessible	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.
INT xylnatmTrafficShaperConfTsNumIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.3	INTEGER	read-only	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).
xylnatmTrafficShaperMemEntry	1.3.6.1.4.1.800.2.9.1.19.1.1		not-accessible	An entry in the Traffic Shaper Membership table containing a VPI/VCI number mapping to a traffic shaper number.
xylnatmTrafficShaperMemGroup	1.3.6.1.4.1.800.2.9.1.19
INT xylnatmTrafficShaperMemPortIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemSlotIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
xylnatmTrafficShaperMemTable	1.3.6.1.4.1.800.2.9.1.19.1		not-accessible	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.
INT xylnatmTrafficShaperMemTsNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.3	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemVciNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.5	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVpiNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.4	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVpiOper	1.3.6.1.4.1.800.2.9.1.19.1.1.6	INTEGER	read-write	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.
INT xylnatmVcCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.13.1.1.9	INTEGER	read-only	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.
xylnatmVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.13.1.1		not-accessible	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.
xylnatmVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.13
STR xylnatmVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.14	DisplayString	read-only	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.
INT xylnatmVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.16	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.6	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.5	INTEGER	read-only	The high port number
INT xylnatmVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.13.1.1.8	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.7	INTEGER	read-only	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.
STR xylnatmVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.13	DisplayString	read-only	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.
INT xylnatmVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.15	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.2	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.10	INTEGER	read-write	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.
INT xylnatmVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.1	INTEGER	read-only	The incoming slot number
INT xylnatmVcCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.11	INTEGER	read-write	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.
INT xylnatmVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.13.1.1.4	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.3	INTEGER	read-only	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.
INT xylnatmVcCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.13.1.1.12	INTEGER	read-write	Enable/disable multicast as per the ui
INT xylnatmVcCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.13.1.1.18	INTEGER	read-write	This is required by NMS to identify PVC's across networks
INT xylnatmVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.19	INTEGER	read-write	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
xylnatmVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.13.1		not-accessible	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.
INT xylnatmVcCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.13.1.1.17	INTEGER	read-only	The type of VC...Permanent/Switched/ Soft/control
INT xylnatmVclAAL5Discard	1.3.6.1.4.1.800.2.9.1.10.1.1.19	INTEGER	read-write	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.
INT xylnatmVclAltTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.17	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclChanType	1.3.6.1.4.1.800.2.9.1.10.1.1.6	INTEGER	read-write	The type of Virtual path
STR xylnatmVclConnectionDescr	1.3.6.1.4.1.800.2.9.1.10.1.1.5	DisplayString	read-write	An ascii value for the connection
xylnatmVclEntry	1.3.6.1.4.1.800.2.9.1.10.1.1		not-accessible	List of xylan specific objects
INT xylnatmVclF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.10.1.1.23	INTEGER	read-write	Future release
INT xylnatmVclF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.10.1.1.21	INTEGER	read-write	Future release
INT xylnatmVclF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.22	INTEGER	read-write	Future release
INT xylnatmVclF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.20	INTEGER	read-write	Future release
INT xylnatmVclGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.33	INTEGER	read-only	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
INT xylnatmVclGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.34	INTEGER	read-only	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
xylnatmVclGroup	1.3.6.1.4.1.800.2.9.1.10
INT xylnatmVclLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.10.1.1.18	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVclMcGroupId	1.3.6.1.4.1.800.2.9.1.10.1.1.35	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVclMcIngressEgress	1.3.6.1.4.1.800.2.9.1.10.1.1.36	INTEGER	read-only	Always ingress in this release
INT xylnatmVclModDestPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.6	INTEGER	read-write	Port Instance
INT xylnatmVclModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.5	INTEGER	read-write	Slot Instance
INT xylnatmVclModDestStatus	1.3.6.1.4.1.800.2.9.1.15.1.1.9	INTEGER	read-write	To be in sync with the ui we allow modification
INT xylnatmVclModDestVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.8	INTEGER	read-write	Vci instance
INT xylnatmVclModDestVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.7	INTEGER	read-write	Vpi instance
xylnatmVclModEntry	1.3.6.1.4.1.800.2.9.1.15.1.1		not-accessible	List of xylan specific objects
xylnatmVclModGroup	1.3.6.1.4.1.800.2.9.1.15
INT xylnatmVclModPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclModSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.1	INTEGER	read-only	Slot Instance
xylnatmVclModTable	1.3.6.1.4.1.800.2.9.1.15.1		not-accessible	This table contains xylan implementation specific objects
INT xylnatmVclModVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.4	INTEGER	read-only	Vci instance
INT xylnatmVclModVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVclOamCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.25	INTEGER	read-write	Future release
INT xylnatmVclOamEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.24	INTEGER	read-write	Future release
INT xylnatmVclPortIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclPrTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.13	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.10	INTEGER	read-only	The dest internal pport
INT xylnatmVclRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.30	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.29	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.31	INTEGER	read-write	Future release
INT xylnatmVclRmDiscard	1.3.6.1.4.1.800.2.9.1.10.1.1.32	INTEGER	read-write	Future release
INT xylnatmVclRmFwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.27	INTEGER	read-write	Future release
INT xylnatmVclRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.26	INTEGER	read-write	Future release
INT xylnatmVclRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.28	INTEGER	read-write	Future release
INT xylnatmVclSlotIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.1	INTEGER	read-only	Slot Instance
CTR xylnatmVclStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.9	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.10	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.13	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.14	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.11	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.12	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
xylnatmVclStatEntry	1.3.6.1.4.1.800.2.9.1.12.1.1		not-accessible	Contains the stats objects
xylnatmVclStatGroup	1.3.6.1.4.1.800.2.9.1.12
INT xylnatmVclStatPortIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.2	INTEGER	read-only	The port number of this slot
CTR xylnatmVclStatRxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.5	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi/vci
CTR xylnatmVclStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.7	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi/vci
CTR xylnatmVclStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.8	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi/vci
INT xylnatmVclStatSlotIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVclStatsMode	1.3.6.1.4.1.800.2.9.1.10.1.1.9	INTEGER	read-write	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
xylnatmVclStatTable	1.3.6.1.4.1.800.2.9.1.12.1		not-accessible	This table contains the xylan specific statistical object
CTR xylnatmVclStatTxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.6	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi/vci
INT xylnatmVclStatVci	1.3.6.1.4.1.800.2.9.1.12.1.1.4	INTEGER	read-only	The Vci number for the connection
INT xylnatmVclStatVpi	1.3.6.1.4.1.800.2.9.1.12.1.1.3	INTEGER	read-only	The Vpi number for this connection
xylnatmVclTable	1.3.6.1.4.1.800.2.9.1.10.1		not-accessible	This table contains xylan implementation specific objects
INT xylnatmVclTransportPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.7	INTEGER	read-write	The transport priority...
INT xylnatmVclUserPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.8	INTEGER	read-write	The user priority 0-15, with 0 being the highest
INT xylnatmVclVci	1.3.6.1.4.1.800.2.9.1.10.1.1.4	INTEGER	read-only	Vcl instance
INT xylnatmVclVpi	1.3.6.1.4.1.800.2.9.1.10.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVpCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.14.1.1.7	INTEGER	read-only	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.
xylnatmVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.14.1.1		not-accessible	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.
xylnatmVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.14
STR xylnatmVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.12	DisplayString	read-only	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.
INT xylnatmVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.14	INTEGER	read-only	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.
INT xylnatmVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.5	INTEGER	read-only	The high physical port number
INT xylnatmVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.4	INTEGER	read-only	The value of the high slot number
INT xylnatmVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.6	INTEGER	read-only	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.
STR xylnatmVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.11	DisplayString	read-only	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.
INT xylnatmVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.13	INTEGER	read-only	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.
INT xylnatmVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.2	INTEGER	read-only	The low physical port number
INT xylnatmVpCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.8	INTEGER	read-write	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.
INT xylnatmVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.1	INTEGER	read-only	The low slot number
INT xylnatmVpCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.9	INTEGER	read-write	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.
INT xylnatmVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.3	INTEGER	read-only	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.
INT xylnatmVpCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.14.1.1.10	INTEGER	read-write	Whether Mcast should be enabled/disabled for this connection
INT xylnatmVpCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.14.1.1.16	INTEGER	read-write	This is required by NMS to id PVC's across networks
INT xylnatmVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.17	INTEGER	read-write	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
xylnatmVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.14.1		not-accessible	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.
INT xylnatmVpCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.14.1.1.15	INTEGER	read-only	The type of VC...Permanent/Switched/Soft/control
INT xylnatmVplAAL5Discard	1.3.6.1.4.1.800.2.9.1.9.1.1.18	INTEGER	read-write	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.
INT xylnatmVplAltTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.13	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplChanType	1.3.6.1.4.1.800.2.9.1.9.1.1.5	INTEGER	read-write	The type of Virtual path
STR xylnatmVplConnectionDescr	1.3.6.1.4.1.800.2.9.1.9.1.1.4	DisplayString	read-write	An ascii value for the connection
xylnatmVplEntry	1.3.6.1.4.1.800.2.9.1.9.1.1		not-accessible	List of xylan specific objects
INT xylnatmVplF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.9.1.1.22	INTEGER	read-write	Future release
INT xylnatmVplF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.9.1.1.20	INTEGER	read-write	Future release
INT xylnatmVplF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.21	INTEGER	read-write	Future release
INT xylnatmVplF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.19	INTEGER	read-write	Future release
INT xylnatmVplGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.32	INTEGER	read-only	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
INT xylnatmVplGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.33	INTEGER	read-only	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
xylnatmVplGroup	1.3.6.1.4.1.800.2.9.1.9
INT xylnatmVplLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.9.1.1.17	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVplMcGroupId	1.3.6.1.4.1.800.2.9.1.9.1.1.34	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVplMcIngressEgress	1.3.6.1.4.1.800.2.9.1.9.1.1.35	INTEGER	read-only	Always ingress in this release
INT xylnatmVplModDestPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.5	INTEGER	read-write	Port Instance
INT xylnatmVplModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.4	INTEGER	read-write	Slot Instance
INT xylnatmVplModDestStatus	1.3.6.1.4.1.800.2.9.1.16.1.1.7	INTEGER	read-write	To be in sync with the ui we allow modification
INT xylnatmVplModDestVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.6	INTEGER	read-write	Vpi instance
xylnatmVplModEntry	1.3.6.1.4.1.800.2.9.1.16.1.1		not-accessible	List of xylan specific objects
xylnatmVplModGroup	1.3.6.1.4.1.800.2.9.1.16
INT xylnatmVplModPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplModSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.1	INTEGER	read-only	Slot Instance
xylnatmVplModTable	1.3.6.1.4.1.800.2.9.1.16.1		not-accessible	This table contains xylan implementation specific objects
INT xylnatmVplModVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVplOamCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.24	INTEGER	read-write	Future release
INT xylnatmVplOamEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.23	INTEGER	read-write	Future release
INT xylnatmVplPortIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplPrTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.10	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.9	INTEGER	read-only	The destination internal pport
INT xylnatmVplRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.29	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.28	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.30	INTEGER	read-write	Future release
INT xylnatmVplRmDiscard	1.3.6.1.4.1.800.2.9.1.9.1.1.31	INTEGER	read-write	Future release
INT xylnatmVplRmFwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.26	INTEGER	read-write	Future release
INT xylnatmVplRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.25	INTEGER	read-write	Future release
INT xylnatmVplRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.27	INTEGER	read-write	Future release
INT xylnatmVplSlotIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.1	INTEGER	read-only	Slot Instance
CTR xylnatmVplStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.8	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.9	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.12	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.13	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.10	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.11	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
xylnatmVplStatEntry	1.3.6.1.4.1.800.2.9.1.11.1.1		not-accessible	Contains the stats objects
xylnatmVplStatGroup	1.3.6.1.4.1.800.2.9.1.11
INT xylnatmVplStatPortIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.2	INTEGER	read-only	The port number on this slot
CTR xylnatmVplStatRxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.4	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi
CTR xylnatmVplStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.6	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi
CTR xylnatmVplStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.7	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi
INT xylnatmVplStatSlotIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVplStatsMode	1.3.6.1.4.1.800.2.9.1.9.1.1.8	INTEGER	read-write	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
xylnatmVplStatTable	1.3.6.1.4.1.800.2.9.1.11.1		not-accessible	This table contains the xylan specific statistical object
CTR xylnatmVplStatTxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.5	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi
INT xylnatmVplStatVpi	1.3.6.1.4.1.800.2.9.1.11.1.1.3	INTEGER	read-only	The Vpi number for this connection
xylnatmVplTable	1.3.6.1.4.1.800.2.9.1.9.1		not-accessible	This table contains xylan implementation specific objects
INT xylnatmVplTransportPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.6	INTEGER	read-write	The transport priority...
INT xylnatmVplUserPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.7	INTEGER	read-write	The user priority 0-15 with 0 being the highest
INT xylnatmVplVpi	1.3.6.1.4.1.800.2.9.1.9.1.1.3	INTEGER	read-only	Vpi instance

OID symbolic	OID numeric	Type	Access	Description
xylanCsmMIB	1.3.6.1.4.1.800.2.9.1
atmxVplGroup	1.3.6.1.4.1.800.2.9.1.1
atmxVplTable	1.3.6.1.4.1.800.2.9.1.1.1		not-accessible	The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table.
atmxVplEntry	1.3.6.1.4.1.800.2.9.1.1.1.1		not-accessible	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.
INT atmxVplSlotIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.1	INTEGER	read-only	The slot number of the chassis
INT atmxVplPortIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.2	INTEGER	read-only	The port number of the csm board
INT atmxVplVpi	1.3.6.1.4.1.800.2.9.1.1.1.1.3	INTEGER	read-only	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.
INT atmxVplAdminStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.4	INTEGER	read-write	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.
INT atmxVplOperStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.5	INTEGER	read-only	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.
STR atmxVplLastChange	1.3.6.1.4.1.800.2.9.1.1.1.1.6	DisplayString	read-only	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.
ATM atmxVplReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.7	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the receive direction of the VPL.
ATM atmxVplTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the transmit direction of the VPL.
INT atmxVplCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.1.1.1.9	INTEGER	read-only	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.
INT atmxVplRowStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.10	INTEGER	read-write	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..
INT atmxVplBidirect	1.3.6.1.4.1.800.2.9.1.1.1.1.11	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
atmxInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.2
atmxInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.2.1		not-accessible	This table contains ATM local interface configuration parameters, one entry per ATM interface port.
atmxInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.2.1.1		not-accessible	This list contains ATM interface configuration parameters and state variables.
INT atmxInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.1	INTEGER	read-only	The slot number of the chassis
INT atmxInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.2	INTEGER	read-only	The slot number for the CSM board
INT atmxInterfaceMaxVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.3	INTEGER	read-only	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.
INT atmxInterfaceMaxVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.4	INTEGER	read-only	The maximum number of VCCs (PVCs and SVCs) supported at this ATM interface.
INT atmxInterfaceConfVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.5	INTEGER	read-only	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.
INT atmxInterfaceConfVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.6	INTEGER	read-only	The number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
INT atmxInterfaceMaxActiveVpiBits	1.3.6.1.4.1.800.2.9.1.2.1.1.7	INTEGER	read-write	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.
INT atmxInterfaceMaxActiveVciBits	1.3.6.1.4.1.800.2.9.1.2.1.1.8	INTEGER	read-write	The maximum number of active VCI bits configured for use at this ATM interface.
INT atmxInterfaceIlmiVpi	1.3.6.1.4.1.800.2.9.1.2.1.1.9	INTEGER	read-only	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.
INT atmxInterfaceIlmiVci	1.3.6.1.4.1.800.2.9.1.2.1.1.10	INTEGER	read-only	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.
INT atmxInterfaceAddressType	1.3.6.1.4.1.800.2.9.1.2.1.1.11	INTEGER	read-only	The type of primary ATM address configured for use at this ATM interface.
atmxVclGroup	1.3.6.1.4.1.800.2.9.1.3
atmxVclTable	1.3.6.1.4.1.800.2.9.1.3.1		not-accessible	The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table.
atmxVclEntry	1.3.6.1.4.1.800.2.9.1.3.1.1		not-accessible	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.
INT atmxVclSlotIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.1	INTEGER	read-only	The slot number
INT atmxVclPortIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.2	INTEGER	read-only	The port number of the csm board
INT atmxVclVpi	1.3.6.1.4.1.800.2.9.1.3.1.1.3	INTEGER	read-only	The VPI value of the VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.
INT atmxVclVci	1.3.6.1.4.1.800.2.9.1.3.1.1.4	INTEGER	read-only	The VCI value of the VCL. The maximum VCI value cannot exceed the value allowable by the atmInterfaceMaxVciBits.
INT atmxVclAdminStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.5	INTEGER	read-write	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.
INT atmxVclOperStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.6	INTEGER	read-only	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.
STR atmxVclLastChange	1.3.6.1.4.1.800.2.9.1.3.1.1.7	DisplayString	read-only	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.
ATM atmxVclReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.
ATM atmxVclTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.9	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.
INT atmxVccAalType	1.3.6.1.4.1.800.2.9.1.3.1.1.10	INTEGER	read-write	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.
INT atmxVccAal5CpcsTransmitSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.11	INTEGER	read-write	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.
INT atmxVccAal5CpcsReceiveSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.12	INTEGER	read-write	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.
INT atmxVccAal5EncapsType	1.3.6.1.4.1.800.2.9.1.3.1.1.13	INTEGER	read-write	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.
INT atmxVclCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.3.1.1.14	INTEGER	read-only	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.
INT atmxVclRowStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.15	INTEGER	read-write	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.
INT atmxVclBidirect	1.3.6.1.4.1.800.2.9.1.3.1.1.16	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
xylnatmInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.4
xylnatmInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.4.1		not-accessible	This table contains the private ATM local interface configuration parameters, one entry per ATM interface port.
xylnatmInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.4.1.1		not-accessible	This list contains xyln specific ATM interface configuration parameters and state variables.
INT xylnatmInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.2	INTEGER	read-only	The port number of the chassis
STR xylnatmInterfaceDescription	1.3.6.1.4.1.800.2.9.1.4.1.1.3	DisplayString	read-write	The name in ascii characters describing the interface
INT xylnatmInterfaceTransType	1.3.6.1.4.1.800.2.9.1.4.1.1.4	INTEGER	read-only	The transmission type at this interface. The type is either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b encoding method.
INT xylnatmInterfaceType	1.3.6.1.4.1.800.2.9.1.4.1.1.5	INTEGER	read-write	The signaling type at this interface.
INT xylnatmInterfaceMediaType	1.3.6.1.4.1.800.2.9.1.4.1.1.6	INTEGER	read-only	The physical media type from this physical port
STR xylnatmInterfaceAtmAddress	1.3.6.1.4.1.800.2.9.1.4.1.1.7	DisplayString	read-write	The AtmAddress @ this interface. The AtmAddress should be a 20 octet hex number.
INT xylnatmInterfacePortMode	1.3.6.1.4.1.800.2.9.1.4.1.1.8	INTEGER	read-only	This object describes whether this interface is switched off or allowing traffic to pass thru or is in normal mode.
INT xylnatmInterfaceOperStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.9	INTEGER	read-only	The Oper status @ this interface is reflected by the status of the object.
INT xylnatmInterfaceQsaalStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.10	INTEGER	read-only	The QSAAL status @ this interface is reflected by the status of the object.
INT xylnatmInterfaceIlmiStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.11	INTEGER	read-only	The Ilmi Status @ this interface.
INT xylnatmInterfaceTpRedirect	1.3.6.1.4.1.800.2.9.1.4.1.1.12	INTEGER	read-only	This object indicates whether Cut-Over is enabled or disabled @ this interface
INT xylnatmInterfaceCutOverSlot	1.3.6.1.4.1.800.2.9.1.4.1.1.13	INTEGER	read-write	The Cut-Over slot number of the chassis
INT xylnatmInterfaceCutOverPort	1.3.6.1.4.1.800.2.9.1.4.1.1.14	INTEGER	read-write	The Cut Over Port number of the chassis
INT xylnatmInterfaceClearPortStats	1.3.6.1.4.1.800.2.9.1.4.1.1.15	INTEGER	read-write	True clears the stats for this port
INT xylnatmInterfaceClearChanStats	1.3.6.1.4.1.800.2.9.1.4.1.1.16	INTEGER	read-write	True clears the chan stats
INT xylnatmInterfaceClearSlotStats	1.3.6.1.4.1.800.2.9.1.4.1.1.17	INTEGER	read-write	True clears all the port stats in this slot.
INT xylnatmInterfaceTransmissionType	1.3.6.1.4.1.800.2.9.1.4.1.1.18	INTEGER	read-write	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
INT xylnatmInterfaceIlmiState	1.3.6.1.4.1.800.2.9.1.4.1.1.19	INTEGER	read-write	The state of Ilmi for the instanced port. Setting this object to disable, would prevent any ILMI queries being sent out on this port.
INT xylnatmInterfaceTimingMode	1.3.6.1.4.1.800.2.9.1.4.1.1.20	INTEGER	read-write	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.
INT xylnatmInterfaceLocalSrc	1.3.6.1.4.1.800.2.9.1.4.1.1.21	INTEGER	read-write	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.
INT xylnatmInterfaceUniVersion	1.3.6.1.4.1.800.2.9.1.4.1.1.22	INTEGER	read-write	UNI Version used in the chassis
xylnatmILMIConfTable	1.3.6.1.4.1.800.2.9.1.4.3		not-accessible	This table contains CSM ILMI configuration parameters, one entry per CSM physical interface, or per virtual UNI/NNI instance
xylnatmILMIConfEntry	1.3.6.1.4.1.800.2.9.1.4.3.1		not-accessible	This list contains CSM ILMI configuration and state variables
INT xylnatmILMIConfSlot	1.3.6.1.4.1.800.2.9.1.4.3.1.1	INTEGER	read-only	The slot number this entry represents
INT xylnatmILMIConfPort	1.3.6.1.4.1.800.2.9.1.4.3.1.2	INTEGER	read-only	The port number this entry represents
INT xylnatmILMIConfInstance	1.3.6.1.4.1.800.2.9.1.4.3.1.3	INTEGER	read-only	The Virtual UNI/NNI instance this entry represents
INT xylnatmILMIConfILMIEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.4	INTEGER	read-write	Indicate whether ILMI is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfILMIPollEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.5	INTEGER	read-write	Indicate whether ILMI polling is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.6	INTEGER	read-write	Indicate whether CSM auto cfg is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgStatus	1.3.6.1.4.1.800.2.9.1.4.3.1.7	INTEGER	read-only	The status of auto configuration procedure on this port, or this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgTrigg	1.3.6.1.4.1.800.2.9.1.4.3.1.8	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgDfltIf	1.3.6.1.4.1.800.2.9.1.4.3.1.9	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgDfltSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.10	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgCurIf	1.3.6.1.4.1.800.2.9.1.4.3.1.11	INTEGER	read-write	Current operational interface type for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.12	INTEGER	read-only	Current operational signaling version for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.13	INTEGER	read-only	Current ILMI version running on this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfPeerUniType	1.3.6.1.4.1.800.2.9.1.4.3.1.14	INTEGER	read-only	The UNI type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerUniVer	1.3.6.1.4.1.800.2.9.1.4.3.1.15	INTEGER	read-only	The signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerDevType	1.3.6.1.4.1.800.2.9.1.4.3.1.16	INTEGER	read-only	The device type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerNNISigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.17	INTEGER	read-only	The NNI signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.18	INTEGER	read-only	The ILMI version this port gathered from its peer port through ILMI
atmxVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.5
atmxVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.1		not-accessible	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.
atmxVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.1.1		not-accessible	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.
INT atmxVpCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.1	INTEGER	read-only	A unique value to identify this VP Cross Connect
INT atmxVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.2	INTEGER	read-only	The low slot number
INT atmxVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.3	INTEGER	read-only	The low physical port number
INT atmxVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.4	INTEGER	read-only	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.
INT atmxVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.5	INTEGER	read-only	The value of the high slot number
INT atmxVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.6	INTEGER	read-only	The high physical port number
INT atmxVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.7	INTEGER	read-only	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.
INT atmxVpCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.8	INTEGER	read-write	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.
INT atmxVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.9	INTEGER	read-only	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.
INT atmxVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.10	INTEGER	read-only	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.
STR atmxVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.11	DisplayString	read-only	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.
STR atmxVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.12	DisplayString	read-only	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.
INT atmxVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.13	INTEGER	read-write	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.
atmxSvcVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.2		not-accessible	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.
atmxSvcVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.2.1		not-accessible	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.
INT atmxSvcVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.1	INTEGER	not-accessible	The low slot of the SVC VP cross-connect.
INT atmxSvcVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.2	INTEGER	not-accessible	The incoming slot for this SVC
INT atmxSvcVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.4	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.5	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.6	INTEGER	not-accessible	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.
STR atmxSvcVpCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.5.2.1.7	DisplayString	read-only	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.
INT atmxSvcVpCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.8	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVpCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.9	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.2.1.10	INTEGER	read-only	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
xylnatmInterfaceStatGroup	1.3.6.1.4.1.800.2.9.1.6
xylnatmInterfaceStatTable	1.3.6.1.4.1.800.2.9.1.6.1		not-accessible	This table contains the statistical information about the interface
xylnatmInterfaceStatEntry	1.3.6.1.4.1.800.2.9.1.6.1.1		not-accessible	This list contains xylan specific ATM interface configuration parameters and state variables
INT xylnatmInterfaceStatSlotIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.1	INTEGER	read-only	The slot number in the switch
INT xylnatmInterfaceStatPortIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.2	INTEGER	read-only	The port number in this slot
CTR xylnatmInterfaceStatRxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.3	Counter	read-only	The total number of Received Cells at this interface (OC3, OC12, ATM25...)
CTR xylnatmInterfaceStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.4	Counter	read-only	The total number of received cells at this interface with Cell loss priority of zero
CTR xylnatmInterfaceStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.5	Counter	read-only	The total number of received cells at this interface with Cell loss Priority of zero or one
CTR xylnatmInterfaceStatTxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.6	Counter	read-only	The total number of transmitted cells at this interface
CTR xylnatmInterfaceStatMarkEfciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.7	Counter	read-only	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
CTR xylnatmInterfaceStatMarkGcraCells	1.3.6.1.4.1.800.2.9.1.6.1.1.8	Counter	read-only	The number of cells marked by policing that violated their traffic contract for clp0+1 cells
CTR xylnatmInterfaceStatTotalDiscardCells	1.3.6.1.4.1.800.2.9.1.6.1.1.9	Counter	read-only	The total number of cells discarded at this interface due to congestion, policing and unknown vpi/vci's
CTR xylnatmInterfaceStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.10	Counter	read-only	The number of Clp0 cells discarded due to congestion
CTR xylnatmInterfaceStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.11	Counter	read-only	The number of Clp1 cells discarded due to congestion
CTR xylnatmInterfaceStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.12	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.13	Counter	read-only	The total number of cell loss priority one cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcrabClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.14	Counter	read-only	The total number of Clp0 cells discarded due to policing on cell loss priority zero cells
CTR xylnatmInterfaceStatDxGcrabClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.15	Counter	read-only	The total number of cell loss prioity one cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatUnknownVpVcCells	1.3.6.1.4.1.800.2.9.1.6.1.1.16	Counter	read-only	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
CTR xylnatmInterfaceStatUnknownVpiCells	1.3.6.1.4.1.800.2.9.1.6.1.1.17	Counter	read-only	The total number of unknown Vpi cells recieved at this interface that dont correspond to any channels vpi
CTR xylnatmInterfaceStatUnknownVciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.18	Counter	read-only	The total number of unknown Vci cells recieved at this interface that dont correspond to any channels vci
INT xylnatmInterfaceStatUniType	1.3.6.1.4.1.800.2.9.1.6.1.1.19	INTEGER	read-only	Type of UNI used on this interface...Public or Private
INT xylnatmInterfaceStatUniVersion	1.3.6.1.4.1.800.2.9.1.6.1.1.20	INTEGER	read-only	UNI Version used in the chassis
CTR xylnatmInterfaceStatRemainingRxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.21	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created and cells can be received.
CTR xylnatmInterfaceStatRemainingTxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.22	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created for cells to be transmitted
atmxVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.7
atmxVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.1		not-accessible	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.
atmxVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.1.1		not-accessible	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.
INT atmxVcCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.1	INTEGER	read-only	A unique value to identify this VC Cross Connect
INT atmxVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.2	INTEGER	read-only	The low port number
INT atmxVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.3	INTEGER	read-only	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.
INT atmxVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.4	INTEGER	read-only	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.
INT atmxVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.1.1.5	INTEGER	read-only	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.
INT atmxVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.6	INTEGER	read-only	The high port number
INT atmxVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.7	INTEGER	read-only	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.
INT atmxVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.8	INTEGER	read-only	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.
INT atmxVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.1.1.9	INTEGER	read-only	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.
INT atmxVcCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.10	INTEGER	read-write	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.
INT atmxVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.11	INTEGER	read-only	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.
INT atmxVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.12	INTEGER	read-only	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.
STR atmxVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.13	DisplayString	read-only	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.
STR atmxVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.14	DisplayString	read-only	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.
INT atmxVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.15	INTEGER	read-write	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.
atmxSvcVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.2		not-accessible	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.
atmxSvcVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.2.1		not-accessible	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.
INT atmxSvcVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.1	INTEGER	not-accessible	The incoming slot for this SVC.
INT atmxSvcVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.2	INTEGER	not-accessible	The incoming port for this SVC.
INT atmxSvcVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.2.1.4	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.5	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.6	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.7	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.2.1.8	INTEGER	not-accessible	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.
STR atmxSvcVcCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.7.2.1.9	DisplayString	read-only	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.
INT atmxSvcVcCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.10	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVcCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.11	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.2.1.12	INTEGER	read-only	This object is used to indicate the status of the SVC in the atmSvcVcCrossConnectTable.
atmxTrafficDescrGroup	1.3.6.1.4.1.800.2.9.1.8
atmxTrafficDescrParamTable	1.3.6.1.4.1.800.2.9.1.8.1		not-accessible	This table contains information on ATM traffic descriptor type and the associated parameters.
atmxTrafficDescrParamEntry	1.3.6.1.4.1.800.2.9.1.8.1.1		not-accessible	This list contains ATM traffic descriptor type and the associated parameters.
ATM atmxTrafficDescrParamIndex	1.3.6.1.4.1.800.2.9.1.8.1.1.1	AtmxTrafficDescrParamIndex	read-only	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
INT atmxTrafficDescrType	1.3.6.1.4.1.800.2.9.1.8.1.1.2	INTEGER	read-write	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.
INT atmxTrafficDescrParam1	1.3.6.1.4.1.800.2.9.1.8.1.1.3	INTEGER	read-write	The first parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam2	1.3.6.1.4.1.800.2.9.1.8.1.1.4	INTEGER	read-write	The second parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam3	1.3.6.1.4.1.800.2.9.1.8.1.1.5	INTEGER	read-write	The third parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam4	1.3.6.1.4.1.800.2.9.1.8.1.1.6	INTEGER	read-write	The fourth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam5	1.3.6.1.4.1.800.2.9.1.8.1.1.7	INTEGER	read-write	The fifth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficQoSClass	1.3.6.1.4.1.800.2.9.1.8.1.1.8	INTEGER	read-write	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.
INT atmxTrafficDescrRowStatus	1.3.6.1.4.1.800.2.9.1.8.1.1.9	INTEGER	read-write	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
xylnatmVplGroup	1.3.6.1.4.1.800.2.9.1.9
xylnatmVplTable	1.3.6.1.4.1.800.2.9.1.9.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVplEntry	1.3.6.1.4.1.800.2.9.1.9.1.1		not-accessible	List of xylan specific objects
INT xylnatmVplSlotIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVplPortIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplVpi	1.3.6.1.4.1.800.2.9.1.9.1.1.3	INTEGER	read-only	Vpi instance
STR xylnatmVplConnectionDescr	1.3.6.1.4.1.800.2.9.1.9.1.1.4	DisplayString	read-write	An ascii value for the connection
INT xylnatmVplChanType	1.3.6.1.4.1.800.2.9.1.9.1.1.5	INTEGER	read-write	The type of Virtual path
INT xylnatmVplTransportPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.6	INTEGER	read-write	The transport priority...
INT xylnatmVplUserPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.7	INTEGER	read-write	The user priority 0-15 with 0 being the highest
INT xylnatmVplStatsMode	1.3.6.1.4.1.800.2.9.1.9.1.1.8	INTEGER	read-write	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
INT xylnatmVplPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.9	INTEGER	read-only	The destination internal pport
INT xylnatmVplPrTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.10	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.13	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.9.1.1.17	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVplAAL5Discard	1.3.6.1.4.1.800.2.9.1.9.1.1.18	INTEGER	read-write	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.
INT xylnatmVplF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.19	INTEGER	read-write	Future release
INT xylnatmVplF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.9.1.1.20	INTEGER	read-write	Future release
INT xylnatmVplF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.21	INTEGER	read-write	Future release
INT xylnatmVplF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.9.1.1.22	INTEGER	read-write	Future release
INT xylnatmVplOamEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.23	INTEGER	read-write	Future release
INT xylnatmVplOamCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.24	INTEGER	read-write	Future release
INT xylnatmVplRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.25	INTEGER	read-write	Future release
INT xylnatmVplRmFwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.26	INTEGER	read-write	Future release
INT xylnatmVplRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.27	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.28	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.29	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.30	INTEGER	read-write	Future release
INT xylnatmVplRmDiscard	1.3.6.1.4.1.800.2.9.1.9.1.1.31	INTEGER	read-write	Future release
INT xylnatmVplGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.32	INTEGER	read-only	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
INT xylnatmVplGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.33	INTEGER	read-only	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
INT xylnatmVplMcGroupId	1.3.6.1.4.1.800.2.9.1.9.1.1.34	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVplMcIngressEgress	1.3.6.1.4.1.800.2.9.1.9.1.1.35	INTEGER	read-only	Always ingress in this release
xylnatmVclGroup	1.3.6.1.4.1.800.2.9.1.10
xylnatmVclTable	1.3.6.1.4.1.800.2.9.1.10.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVclEntry	1.3.6.1.4.1.800.2.9.1.10.1.1		not-accessible	List of xylan specific objects
INT xylnatmVclSlotIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVclPortIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclVpi	1.3.6.1.4.1.800.2.9.1.10.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVclVci	1.3.6.1.4.1.800.2.9.1.10.1.1.4	INTEGER	read-only	Vcl instance
STR xylnatmVclConnectionDescr	1.3.6.1.4.1.800.2.9.1.10.1.1.5	DisplayString	read-write	An ascii value for the connection
INT xylnatmVclChanType	1.3.6.1.4.1.800.2.9.1.10.1.1.6	INTEGER	read-write	The type of Virtual path
INT xylnatmVclTransportPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.7	INTEGER	read-write	The transport priority...
INT xylnatmVclUserPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.8	INTEGER	read-write	The user priority 0-15, with 0 being the highest
INT xylnatmVclStatsMode	1.3.6.1.4.1.800.2.9.1.10.1.1.9	INTEGER	read-write	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
INT xylnatmVclPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.10	INTEGER	read-only	The dest internal pport
INT xylnatmVclPrTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.13	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.17	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.10.1.1.18	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVclAAL5Discard	1.3.6.1.4.1.800.2.9.1.10.1.1.19	INTEGER	read-write	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.
INT xylnatmVclF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.20	INTEGER	read-write	Future release
INT xylnatmVclF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.10.1.1.21	INTEGER	read-write	Future release
INT xylnatmVclF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.22	INTEGER	read-write	Future release
INT xylnatmVclF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.10.1.1.23	INTEGER	read-write	Future release
INT xylnatmVclOamEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.24	INTEGER	read-write	Future release
INT xylnatmVclOamCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.25	INTEGER	read-write	Future release
INT xylnatmVclRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.26	INTEGER	read-write	Future release
INT xylnatmVclRmFwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.27	INTEGER	read-write	Future release
INT xylnatmVclRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.28	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.29	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.30	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.31	INTEGER	read-write	Future release
INT xylnatmVclRmDiscard	1.3.6.1.4.1.800.2.9.1.10.1.1.32	INTEGER	read-write	Future release
INT xylnatmVclGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.33	INTEGER	read-only	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
INT xylnatmVclGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.34	INTEGER	read-only	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
INT xylnatmVclMcGroupId	1.3.6.1.4.1.800.2.9.1.10.1.1.35	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVclMcIngressEgress	1.3.6.1.4.1.800.2.9.1.10.1.1.36	INTEGER	read-only	Always ingress in this release
xylnatmVplStatGroup	1.3.6.1.4.1.800.2.9.1.11
xylnatmVplStatTable	1.3.6.1.4.1.800.2.9.1.11.1		not-accessible	This table contains the xylan specific statistical object
xylnatmVplStatEntry	1.3.6.1.4.1.800.2.9.1.11.1.1		not-accessible	Contains the stats objects
INT xylnatmVplStatSlotIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVplStatPortIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.2	INTEGER	read-only	The port number on this slot
INT xylnatmVplStatVpi	1.3.6.1.4.1.800.2.9.1.11.1.1.3	INTEGER	read-only	The Vpi number for this connection
CTR xylnatmVplStatRxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.4	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi
CTR xylnatmVplStatTxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.5	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi
CTR xylnatmVplStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.6	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi
CTR xylnatmVplStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.7	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi
CTR xylnatmVplStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.8	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.9	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.10	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.11	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.12	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.13	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
xylnatmVclStatGroup	1.3.6.1.4.1.800.2.9.1.12
xylnatmVclStatTable	1.3.6.1.4.1.800.2.9.1.12.1		not-accessible	This table contains the xylan specific statistical object
xylnatmVclStatEntry	1.3.6.1.4.1.800.2.9.1.12.1.1		not-accessible	Contains the stats objects
INT xylnatmVclStatSlotIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVclStatPortIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.2	INTEGER	read-only	The port number of this slot
INT xylnatmVclStatVpi	1.3.6.1.4.1.800.2.9.1.12.1.1.3	INTEGER	read-only	The Vpi number for this connection
INT xylnatmVclStatVci	1.3.6.1.4.1.800.2.9.1.12.1.1.4	INTEGER	read-only	The Vci number for the connection
CTR xylnatmVclStatRxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.5	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi/vci
CTR xylnatmVclStatTxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.6	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi/vci
CTR xylnatmVclStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.7	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi/vci
CTR xylnatmVclStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.8	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi/vci
CTR xylnatmVclStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.9	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.10	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.11	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.12	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.13	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.14	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
xylnatmVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.13
xylnatmVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.13.1		not-accessible	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.
xylnatmVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.13.1.1		not-accessible	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.
INT xylnatmVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.1	INTEGER	read-only	The incoming slot number
INT xylnatmVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.2	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.3	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.13.1.1.4	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.5	INTEGER	read-only	The high port number
INT xylnatmVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.6	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.7	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.13.1.1.8	INTEGER	read-only	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.
INT xylnatmVcCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.13.1.1.9	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.10	INTEGER	read-write	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.
INT xylnatmVcCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.11	INTEGER	read-write	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.
INT xylnatmVcCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.13.1.1.12	INTEGER	read-write	Enable/disable multicast as per the ui
STR xylnatmVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.13	DisplayString	read-only	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.
STR xylnatmVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.14	DisplayString	read-only	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.
INT xylnatmVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.15	INTEGER	read-only	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.
INT xylnatmVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.16	INTEGER	read-only	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.
INT xylnatmVcCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.13.1.1.17	INTEGER	read-only	The type of VC...Permanent/Switched/ Soft/control
INT xylnatmVcCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.13.1.1.18	INTEGER	read-write	This is required by NMS to identify PVC's across networks
INT xylnatmVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.19	INTEGER	read-write	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
xylnatmVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.14
xylnatmVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.14.1		not-accessible	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.
xylnatmVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.14.1.1		not-accessible	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.
INT xylnatmVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.1	INTEGER	read-only	The low slot number
INT xylnatmVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.2	INTEGER	read-only	The low physical port number
INT xylnatmVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.3	INTEGER	read-only	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.
INT xylnatmVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.4	INTEGER	read-only	The value of the high slot number
INT xylnatmVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.5	INTEGER	read-only	The high physical port number
INT xylnatmVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.6	INTEGER	read-only	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.
INT xylnatmVpCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.14.1.1.7	INTEGER	read-only	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.
INT xylnatmVpCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.8	INTEGER	read-write	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.
INT xylnatmVpCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.9	INTEGER	read-write	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.
INT xylnatmVpCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.14.1.1.10	INTEGER	read-write	Whether Mcast should be enabled/disabled for this connection
STR xylnatmVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.11	DisplayString	read-only	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.
STR xylnatmVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.12	DisplayString	read-only	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.
INT xylnatmVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.13	INTEGER	read-only	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.
INT xylnatmVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.14	INTEGER	read-only	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.
INT xylnatmVpCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.14.1.1.15	INTEGER	read-only	The type of VC...Permanent/Switched/Soft/control
INT xylnatmVpCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.14.1.1.16	INTEGER	read-write	This is required by NMS to id PVC's across networks
INT xylnatmVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.17	INTEGER	read-write	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
xylnatmVclModGroup	1.3.6.1.4.1.800.2.9.1.15
xylnatmVclModTable	1.3.6.1.4.1.800.2.9.1.15.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVclModEntry	1.3.6.1.4.1.800.2.9.1.15.1.1		not-accessible	List of xylan specific objects
INT xylnatmVclModSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVclModPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclModVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVclModVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.4	INTEGER	read-only	Vci instance
INT xylnatmVclModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.5	INTEGER	read-write	Slot Instance
INT xylnatmVclModDestPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.6	INTEGER	read-write	Port Instance
INT xylnatmVclModDestVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.7	INTEGER	read-write	Vpi instance
INT xylnatmVclModDestVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.8	INTEGER	read-write	Vci instance
INT xylnatmVclModDestStatus	1.3.6.1.4.1.800.2.9.1.15.1.1.9	INTEGER	read-write	To be in sync with the ui we allow modification
xylnatmVplModGroup	1.3.6.1.4.1.800.2.9.1.16
xylnatmVplModTable	1.3.6.1.4.1.800.2.9.1.16.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVplModEntry	1.3.6.1.4.1.800.2.9.1.16.1.1		not-accessible	List of xylan specific objects
INT xylnatmVplModSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVplModPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplModVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVplModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.4	INTEGER	read-write	Slot Instance
INT xylnatmVplModDestPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.5	INTEGER	read-write	Port Instance
INT xylnatmVplModDestVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.6	INTEGER	read-write	Vpi instance
INT xylnatmVplModDestStatus	1.3.6.1.4.1.800.2.9.1.16.1.1.7	INTEGER	read-write	To be in sync with the ui we allow modification
xylnatmClockingxCtrlGroup	1.3.6.1.4.1.800.2.9.1.17
xylnatmClockingxCtrlTable	1.3.6.1.4.1.800.2.9.1.17.1		not-accessible	A table of Clocking configuration and control information.
xylnatmClockingxCtrlEntry	1.3.6.1.4.1.800.2.9.1.17.1.1		not-accessible	An entry in the Clocking Configuration/control table, containing information about Cell Switching Module (CSM) clocking.
INT xylnatmClockingxCtrlBusLine	1.3.6.1.4.1.800.2.9.1.17.1.1.1	INTEGER	read-only	The Bus Signal function used for clocking CSM modules. This is used as a unique ID to identify a clocking line on the bus.
INT xylnatmClockingxCtrlSrcLevel	1.3.6.1.4.1.800.2.9.1.17.1.1.2	INTEGER	read-only	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.
INT xylnatmClockingxSrcOperState	1.3.6.1.4.1.800.2.9.1.17.1.1.3	INTEGER	read-only	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.
INT xylnatmClockingxSrcType	1.3.6.1.4.1.800.2.9.1.17.1.1.4	INTEGER	read-write	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.
INT xylnatmClockingxCtrlSlot	1.3.6.1.4.1.800.2.9.1.17.1.1.5	INTEGER	read-write	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.
INT xylnatmClockingxCtrlPort	1.3.6.1.4.1.800.2.9.1.17.1.1.6	INTEGER	read-write	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.
INT xylnatmClockingxGlobalCST	1.3.6.1.4.1.800.2.9.1.17.2	INTEGER	read-write	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.
xylnatmTrafficShaperConfGroup	1.3.6.1.4.1.800.2.9.1.18
xylnatmTrafficShaperConfTable	1.3.6.1.4.1.800.2.9.1.18.1		not-accessible	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.
xylnatmTrafficShaperConfEntry	1.3.6.1.4.1.800.2.9.1.18.1.1		not-accessible	An entry in the Traffic Shaper Configuration table containing parameters of the traffic shapers of cell switching module.
INT xylnatmTrafficShaperConfSlotIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
INT xylnatmTrafficShaperConfPortIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperConfTsNumIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.3	INTEGER	read-only	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).
INT xylnatmTrafficShaperConfCDV	1.3.6.1.4.1.800.2.9.1.18.1.1.4	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfPCR	1.3.6.1.4.1.800.2.9.1.18.1.1.5	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfSCR	1.3.6.1.4.1.800.2.9.1.18.1.1.6	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfMBS	1.3.6.1.4.1.800.2.9.1.18.1.1.7	INTEGER	read-write	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.
xylnatmTrafficShaperMemGroup	1.3.6.1.4.1.800.2.9.1.19
xylnatmTrafficShaperMemTable	1.3.6.1.4.1.800.2.9.1.19.1		not-accessible	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.
xylnatmTrafficShaperMemEntry	1.3.6.1.4.1.800.2.9.1.19.1.1		not-accessible	An entry in the Traffic Shaper Membership table containing a VPI/VCI number mapping to a traffic shaper number.
INT xylnatmTrafficShaperMemSlotIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
INT xylnatmTrafficShaperMemPortIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemTsNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.3	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemVpiNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.4	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVciNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.5	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVpiOper	1.3.6.1.4.1.800.2.9.1.19.1.1.6	INTEGER	read-write	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.

AtmxTrafficDescrParamIndex (5)
ATM atmxTrafficDescrParamIndex	1.3.6.1.4.1.800.2.9.1.8.1.1.1	AtmxTrafficDescrParamIndex	read-only	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
ATM atmxVclReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.
ATM atmxVclTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.9	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.
ATM atmxVplReceiveTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.7	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the receive direction of the VPL.
ATM atmxVplTransmitTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.8	AtmxTrafficDescrParamIndex	read-write	The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the transmit direction of the VPL.
Counter (38)
CTR xylnatmInterfaceStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.10	Counter	read-only	The number of Clp0 cells discarded due to congestion
CTR xylnatmInterfaceStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.11	Counter	read-only	The number of Clp1 cells discarded due to congestion
CTR xylnatmInterfaceStatDxGcrabClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.14	Counter	read-only	The total number of Clp0 cells discarded due to policing on cell loss priority zero cells
CTR xylnatmInterfaceStatDxGcrabClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.15	Counter	read-only	The total number of cell loss prioity one cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.12	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.13	Counter	read-only	The total number of cell loss priority one cells discarded due to policing on Clp0+1 cells
CTR xylnatmInterfaceStatMarkEfciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.7	Counter	read-only	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
CTR xylnatmInterfaceStatMarkGcraCells	1.3.6.1.4.1.800.2.9.1.6.1.1.8	Counter	read-only	The number of cells marked by policing that violated their traffic contract for clp0+1 cells
CTR xylnatmInterfaceStatRemainingRxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.21	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created and cells can be received.
CTR xylnatmInterfaceStatRemainingTxBandwidth	1.3.6.1.4.1.800.2.9.1.6.1.1.22	Counter	read-only	The remaining bandwidth available on this port thru which connections can be created for cells to be transmitted
CTR xylnatmInterfaceStatRxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.3	Counter	read-only	The total number of Received Cells at this interface (OC3, OC12, ATM25...)
CTR xylnatmInterfaceStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.4	Counter	read-only	The total number of received cells at this interface with Cell loss priority of zero
CTR xylnatmInterfaceStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.6.1.1.5	Counter	read-only	The total number of received cells at this interface with Cell loss Priority of zero or one
CTR xylnatmInterfaceStatTotalDiscardCells	1.3.6.1.4.1.800.2.9.1.6.1.1.9	Counter	read-only	The total number of cells discarded at this interface due to congestion, policing and unknown vpi/vci's
CTR xylnatmInterfaceStatTxCells	1.3.6.1.4.1.800.2.9.1.6.1.1.6	Counter	read-only	The total number of transmitted cells at this interface
CTR xylnatmInterfaceStatUnknownVciCells	1.3.6.1.4.1.800.2.9.1.6.1.1.18	Counter	read-only	The total number of unknown Vci cells recieved at this interface that dont correspond to any channels vci
CTR xylnatmInterfaceStatUnknownVpiCells	1.3.6.1.4.1.800.2.9.1.6.1.1.17	Counter	read-only	The total number of unknown Vpi cells recieved at this interface that dont correspond to any channels vpi
CTR xylnatmInterfaceStatUnknownVpVcCells	1.3.6.1.4.1.800.2.9.1.6.1.1.16	Counter	read-only	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
CTR xylnatmVclStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.9	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.10	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVclStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.13	Counter	read-only	The total number of Clp0 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.14	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.11	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVclStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.12	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVclStatRxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.5	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi/vci
CTR xylnatmVclStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.7	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi/vci
CTR xylnatmVclStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.12.1.1.8	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi/vci
CTR xylnatmVclStatTxCells	1.3.6.1.4.1.800.2.9.1.12.1.1.6	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi/vci
CTR xylnatmVplStatDxCongClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.8	Counter	read-only	The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxCongClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.9	Counter	read-only	The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion
CTR xylnatmVplStatDxGcraBClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.12	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraBClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.13	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.10	Counter	read-only	The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells
CTR xylnatmVplStatDxGcraClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.11	Counter	read-only	The total number of Clp1 cells discarded due to policing on Clp0+1 cells
CTR xylnatmVplStatRxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.4	Counter	read-only	The total number of cells received on this connection identified by the slot/port/vpi
CTR xylnatmVplStatRxClp0Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.6	Counter	read-only	The total number of received cells with Clp0 received on this connection identified by slot/port/vpi
CTR xylnatmVplStatRxClp1Cells	1.3.6.1.4.1.800.2.9.1.11.1.1.7	Counter	read-only	The total number of received cells with Clp1 received on this connection identified by slot/port/vpi
CTR xylnatmVplStatTxCells	1.3.6.1.4.1.800.2.9.1.11.1.1.5	Counter	read-only	The total number of cells transmitted on this connection identified by the slot/port/vpi
DisplayString (16)
STR atmxSvcVcCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.7.2.1.9	DisplayString	read-only	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.
STR atmxSvcVpCrossConnectCreationTime	1.3.6.1.4.1.800.2.9.1.5.2.1.7	DisplayString	read-only	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.
STR atmxVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.14	DisplayString	read-only	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.
STR atmxVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.7.1.1.13	DisplayString	read-only	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.
STR atmxVclLastChange	1.3.6.1.4.1.800.2.9.1.3.1.1.7	DisplayString	read-only	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.
STR atmxVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.12	DisplayString	read-only	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.
STR atmxVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.5.1.1.11	DisplayString	read-only	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.
STR atmxVplLastChange	1.3.6.1.4.1.800.2.9.1.1.1.1.6	DisplayString	read-only	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.
STR xylnatmInterfaceAtmAddress	1.3.6.1.4.1.800.2.9.1.4.1.1.7	DisplayString	read-write	The AtmAddress @ this interface. The AtmAddress should be a 20 octet hex number.
STR xylnatmInterfaceDescription	1.3.6.1.4.1.800.2.9.1.4.1.1.3	DisplayString	read-write	The name in ascii characters describing the interface
STR xylnatmVcCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.14	DisplayString	read-only	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.
STR xylnatmVcCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.13.1.1.13	DisplayString	read-only	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.
STR xylnatmVclConnectionDescr	1.3.6.1.4.1.800.2.9.1.10.1.1.5	DisplayString	read-write	An ascii value for the connection
STR xylnatmVpCrossConnectH2LLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.12	DisplayString	read-only	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.
STR xylnatmVpCrossConnectL2HLastChange	1.3.6.1.4.1.800.2.9.1.14.1.1.11	DisplayString	read-only	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.
STR xylnatmVplConnectionDescr	1.3.6.1.4.1.800.2.9.1.9.1.1.4	DisplayString	read-write	An ascii value for the connection
INTEGER (270)
INT atmxInterfaceAddressType	1.3.6.1.4.1.800.2.9.1.2.1.1.11	INTEGER	read-only	The type of primary ATM address configured for use at this ATM interface.
INT atmxInterfaceConfVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.6	INTEGER	read-only	The number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
INT atmxInterfaceConfVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.5	INTEGER	read-only	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.
INT atmxInterfaceIlmiVci	1.3.6.1.4.1.800.2.9.1.2.1.1.10	INTEGER	read-only	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.
INT atmxInterfaceIlmiVpi	1.3.6.1.4.1.800.2.9.1.2.1.1.9	INTEGER	read-only	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.
INT atmxInterfaceMaxActiveVciBits	1.3.6.1.4.1.800.2.9.1.2.1.1.8	INTEGER	read-write	The maximum number of active VCI bits configured for use at this ATM interface.
INT atmxInterfaceMaxActiveVpiBits	1.3.6.1.4.1.800.2.9.1.2.1.1.7	INTEGER	read-write	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.
INT atmxInterfaceMaxVccs	1.3.6.1.4.1.800.2.9.1.2.1.1.4	INTEGER	read-only	The maximum number of VCCs (PVCs and SVCs) supported at this ATM interface.
INT atmxInterfaceMaxVpcs	1.3.6.1.4.1.800.2.9.1.2.1.1.3	INTEGER	read-only	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.
INT atmxInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.2	INTEGER	read-only	The slot number for the CSM board
INT atmxInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.2.1.1.1	INTEGER	read-only	The slot number of the chassis
INT atmxSvcVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.6	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.5	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVcCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.11	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.2.1.8	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.7	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.2	INTEGER	not-accessible	The incoming port for this SVC.
INT atmxSvcVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.1	INTEGER	not-accessible	The incoming slot for this SVC.
INT atmxSvcVcCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.7.2.1.10	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.2.1.4	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.2.1.12	INTEGER	read-only	This object is used to indicate the status of the SVC in the atmSvcVcCrossConnectTable.
INT atmxSvcVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.5	INTEGER	not-accessible	The outgoing port for this SVC
INT atmxSvcVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.4	INTEGER	not-accessible	The outgoing slot for this SVC
INT atmxSvcVpCrossConnectHighTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.9	INTEGER	read-only	The high connections traffic descriptor index
INT atmxSvcVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.6	INTEGER	not-accessible	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.
INT atmxSvcVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.2	INTEGER	not-accessible	The incoming slot for this SVC
INT atmxSvcVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.1	INTEGER	not-accessible	The low slot of the SVC VP cross-connect.
INT atmxSvcVpCrossConnectLowTDIndex	1.3.6.1.4.1.800.2.9.1.5.2.1.8	INTEGER	read-only	The low end connections Traffic Descriptor Index
INT atmxSvcVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.2.1.3	INTEGER	not-accessible	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.
INT atmxSvcVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.2.1.10	INTEGER	read-only	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
INT atmxTrafficDescrParam1	1.3.6.1.4.1.800.2.9.1.8.1.1.3	INTEGER	read-write	The first parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam2	1.3.6.1.4.1.800.2.9.1.8.1.1.4	INTEGER	read-write	The second parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam3	1.3.6.1.4.1.800.2.9.1.8.1.1.5	INTEGER	read-write	The third parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam4	1.3.6.1.4.1.800.2.9.1.8.1.1.6	INTEGER	read-write	The fourth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrParam5	1.3.6.1.4.1.800.2.9.1.8.1.1.7	INTEGER	read-write	The fifth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.
INT atmxTrafficDescrRowStatus	1.3.6.1.4.1.800.2.9.1.8.1.1.9	INTEGER	read-write	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
INT atmxTrafficDescrType	1.3.6.1.4.1.800.2.9.1.8.1.1.2	INTEGER	read-write	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.
INT atmxTrafficQoSClass	1.3.6.1.4.1.800.2.9.1.8.1.1.8	INTEGER	read-write	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.
INT atmxVccAal5CpcsReceiveSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.12	INTEGER	read-write	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.
INT atmxVccAal5CpcsTransmitSduSize	1.3.6.1.4.1.800.2.9.1.3.1.1.11	INTEGER	read-write	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.
INT atmxVccAal5EncapsType	1.3.6.1.4.1.800.2.9.1.3.1.1.13	INTEGER	read-write	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.
INT atmxVccAalType	1.3.6.1.4.1.800.2.9.1.3.1.1.10	INTEGER	read-write	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.
INT atmxVcCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.10	INTEGER	read-write	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.
INT atmxVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.12	INTEGER	read-only	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.
INT atmxVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.7	INTEGER	read-only	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.
INT atmxVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.6	INTEGER	read-only	The high port number
INT atmxVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.7.1.1.9	INTEGER	read-only	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.
INT atmxVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.8	INTEGER	read-only	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.
INT atmxVcCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.1	INTEGER	read-only	A unique value to identify this VC Cross Connect
INT atmxVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.11	INTEGER	read-only	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.
INT atmxVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.3	INTEGER	read-only	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.
INT atmxVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.7.1.1.2	INTEGER	read-only	The low port number
INT atmxVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.7.1.1.5	INTEGER	read-only	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.
INT atmxVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.7.1.1.4	INTEGER	read-only	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.
INT atmxVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.7.1.1.15	INTEGER	read-write	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.
INT atmxVclAdminStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.5	INTEGER	read-write	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.
INT atmxVclBidirect	1.3.6.1.4.1.800.2.9.1.3.1.1.16	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
INT atmxVclCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.3.1.1.14	INTEGER	read-only	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.
INT atmxVclOperStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.6	INTEGER	read-only	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.
INT atmxVclPortIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.2	INTEGER	read-only	The port number of the csm board
INT atmxVclRowStatus	1.3.6.1.4.1.800.2.9.1.3.1.1.15	INTEGER	read-write	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.
INT atmxVclSlotIndex	1.3.6.1.4.1.800.2.9.1.3.1.1.1	INTEGER	read-only	The slot number
INT atmxVclVci	1.3.6.1.4.1.800.2.9.1.3.1.1.4	INTEGER	read-only	The VCI value of the VCL. The maximum VCI value cannot exceed the value allowable by the atmInterfaceMaxVciBits.
INT atmxVclVpi	1.3.6.1.4.1.800.2.9.1.3.1.1.3	INTEGER	read-only	The VPI value of the VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.
INT atmxVpCrossConnectAdminStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.8	INTEGER	read-write	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.
INT atmxVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.10	INTEGER	read-only	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.
INT atmxVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.6	INTEGER	read-only	The high physical port number
INT atmxVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.5	INTEGER	read-only	The value of the high slot number
INT atmxVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.7	INTEGER	read-only	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.
INT atmxVpCrossConnectIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.1	INTEGER	read-only	A unique value to identify this VP Cross Connect
INT atmxVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.9	INTEGER	read-only	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.
INT atmxVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.3	INTEGER	read-only	The low physical port number
INT atmxVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.5.1.1.2	INTEGER	read-only	The low slot number
INT atmxVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.5.1.1.4	INTEGER	read-only	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.
INT atmxVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.5.1.1.13	INTEGER	read-write	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.
INT atmxVplAdminStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.4	INTEGER	read-write	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.
INT atmxVplBidirect	1.3.6.1.4.1.800.2.9.1.1.1.1.11	INTEGER	read-write	Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection.
INT atmxVplCrossConnectIdentifier	1.3.6.1.4.1.800.2.9.1.1.1.1.9	INTEGER	read-only	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.
INT atmxVplOperStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.5	INTEGER	read-only	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.
INT atmxVplPortIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.2	INTEGER	read-only	The port number of the csm board
INT atmxVplRowStatus	1.3.6.1.4.1.800.2.9.1.1.1.1.10	INTEGER	read-write	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..
INT atmxVplSlotIndex	1.3.6.1.4.1.800.2.9.1.1.1.1.1	INTEGER	read-only	The slot number of the chassis
INT atmxVplVpi	1.3.6.1.4.1.800.2.9.1.1.1.1.3	INTEGER	read-only	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.
INT xylnatmClockingxCtrlBusLine	1.3.6.1.4.1.800.2.9.1.17.1.1.1	INTEGER	read-only	The Bus Signal function used for clocking CSM modules. This is used as a unique ID to identify a clocking line on the bus.
INT xylnatmClockingxCtrlPort	1.3.6.1.4.1.800.2.9.1.17.1.1.6	INTEGER	read-write	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.
INT xylnatmClockingxCtrlSlot	1.3.6.1.4.1.800.2.9.1.17.1.1.5	INTEGER	read-write	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.
INT xylnatmClockingxCtrlSrcLevel	1.3.6.1.4.1.800.2.9.1.17.1.1.2	INTEGER	read-only	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.
INT xylnatmClockingxGlobalCST	1.3.6.1.4.1.800.2.9.1.17.2	INTEGER	read-write	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.
INT xylnatmClockingxSrcOperState	1.3.6.1.4.1.800.2.9.1.17.1.1.3	INTEGER	read-only	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.
INT xylnatmClockingxSrcType	1.3.6.1.4.1.800.2.9.1.17.1.1.4	INTEGER	read-write	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.
INT xylnatmILMIConfAutoCfgCurIf	1.3.6.1.4.1.800.2.9.1.4.3.1.11	INTEGER	read-write	Current operational interface type for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.13	INTEGER	read-only	Current ILMI version running on this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgCurSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.12	INTEGER	read-only	Current operational signaling version for this CSM port or virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgDfltIf	1.3.6.1.4.1.800.2.9.1.4.3.1.9	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgDfltSigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.10	INTEGER	read-write	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
INT xylnatmILMIConfAutoCfgEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.6	INTEGER	read-write	Indicate whether CSM auto cfg is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgStatus	1.3.6.1.4.1.800.2.9.1.4.3.1.7	INTEGER	read-only	The status of auto configuration procedure on this port, or this Virtual UNI/NNI instance
INT xylnatmILMIConfAutoCfgTrigg	1.3.6.1.4.1.800.2.9.1.4.3.1.8	INTEGER	read-write	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
INT xylnatmILMIConfILMIEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.4	INTEGER	read-write	Indicate whether ILMI is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfILMIPollEnable	1.3.6.1.4.1.800.2.9.1.4.3.1.5	INTEGER	read-write	Indicate whether ILMI polling is enabled on this port, or on this Virtual UNI/NNI instance
INT xylnatmILMIConfInstance	1.3.6.1.4.1.800.2.9.1.4.3.1.3	INTEGER	read-only	The Virtual UNI/NNI instance this entry represents
INT xylnatmILMIConfPeerDevType	1.3.6.1.4.1.800.2.9.1.4.3.1.16	INTEGER	read-only	The device type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerILMIVer	1.3.6.1.4.1.800.2.9.1.4.3.1.18	INTEGER	read-only	The ILMI version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerNNISigVer	1.3.6.1.4.1.800.2.9.1.4.3.1.17	INTEGER	read-only	The NNI signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerUniType	1.3.6.1.4.1.800.2.9.1.4.3.1.14	INTEGER	read-only	The UNI type this port gathered from its peer port through ILMI
INT xylnatmILMIConfPeerUniVer	1.3.6.1.4.1.800.2.9.1.4.3.1.15	INTEGER	read-only	The signaling version this port gathered from its peer port through ILMI
INT xylnatmILMIConfPort	1.3.6.1.4.1.800.2.9.1.4.3.1.2	INTEGER	read-only	The port number this entry represents
INT xylnatmILMIConfSlot	1.3.6.1.4.1.800.2.9.1.4.3.1.1	INTEGER	read-only	The slot number this entry represents
INT xylnatmInterfaceClearChanStats	1.3.6.1.4.1.800.2.9.1.4.1.1.16	INTEGER	read-write	True clears the chan stats
INT xylnatmInterfaceClearPortStats	1.3.6.1.4.1.800.2.9.1.4.1.1.15	INTEGER	read-write	True clears the stats for this port
INT xylnatmInterfaceClearSlotStats	1.3.6.1.4.1.800.2.9.1.4.1.1.17	INTEGER	read-write	True clears all the port stats in this slot.
INT xylnatmInterfaceCutOverPort	1.3.6.1.4.1.800.2.9.1.4.1.1.14	INTEGER	read-write	The Cut Over Port number of the chassis
INT xylnatmInterfaceCutOverSlot	1.3.6.1.4.1.800.2.9.1.4.1.1.13	INTEGER	read-write	The Cut-Over slot number of the chassis
INT xylnatmInterfaceIlmiState	1.3.6.1.4.1.800.2.9.1.4.1.1.19	INTEGER	read-write	The state of Ilmi for the instanced port. Setting this object to disable, would prevent any ILMI queries being sent out on this port.
INT xylnatmInterfaceIlmiStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.11	INTEGER	read-only	The Ilmi Status @ this interface.
INT xylnatmInterfaceLocalSrc	1.3.6.1.4.1.800.2.9.1.4.1.1.21	INTEGER	read-write	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.
INT xylnatmInterfaceMediaType	1.3.6.1.4.1.800.2.9.1.4.1.1.6	INTEGER	read-only	The physical media type from this physical port
INT xylnatmInterfaceOperStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.9	INTEGER	read-only	The Oper status @ this interface is reflected by the status of the object.
INT xylnatmInterfacePortIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.2	INTEGER	read-only	The port number of the chassis
INT xylnatmInterfacePortMode	1.3.6.1.4.1.800.2.9.1.4.1.1.8	INTEGER	read-only	This object describes whether this interface is switched off or allowing traffic to pass thru or is in normal mode.
INT xylnatmInterfaceQsaalStatus	1.3.6.1.4.1.800.2.9.1.4.1.1.10	INTEGER	read-only	The QSAAL status @ this interface is reflected by the status of the object.
INT xylnatmInterfaceSlotIndex	1.3.6.1.4.1.800.2.9.1.4.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmInterfaceStatPortIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.2	INTEGER	read-only	The port number in this slot
INT xylnatmInterfaceStatSlotIndex	1.3.6.1.4.1.800.2.9.1.6.1.1.1	INTEGER	read-only	The slot number in the switch
INT xylnatmInterfaceStatUniType	1.3.6.1.4.1.800.2.9.1.6.1.1.19	INTEGER	read-only	Type of UNI used on this interface...Public or Private
INT xylnatmInterfaceStatUniVersion	1.3.6.1.4.1.800.2.9.1.6.1.1.20	INTEGER	read-only	UNI Version used in the chassis
INT xylnatmInterfaceTimingMode	1.3.6.1.4.1.800.2.9.1.4.1.1.20	INTEGER	read-write	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.
INT xylnatmInterfaceTpRedirect	1.3.6.1.4.1.800.2.9.1.4.1.1.12	INTEGER	read-only	This object indicates whether Cut-Over is enabled or disabled @ this interface
INT xylnatmInterfaceTransmissionType	1.3.6.1.4.1.800.2.9.1.4.1.1.18	INTEGER	read-write	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
INT xylnatmInterfaceTransType	1.3.6.1.4.1.800.2.9.1.4.1.1.4	INTEGER	read-only	The transmission type at this interface. The type is either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b encoding method.
INT xylnatmInterfaceType	1.3.6.1.4.1.800.2.9.1.4.1.1.5	INTEGER	read-write	The signaling type at this interface.
INT xylnatmInterfaceUniVersion	1.3.6.1.4.1.800.2.9.1.4.1.1.22	INTEGER	read-write	UNI Version used in the chassis
INT xylnatmTrafficShaperConfCDV	1.3.6.1.4.1.800.2.9.1.18.1.1.4	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfMBS	1.3.6.1.4.1.800.2.9.1.18.1.1.7	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfPCR	1.3.6.1.4.1.800.2.9.1.18.1.1.5	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfPortIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperConfSCR	1.3.6.1.4.1.800.2.9.1.18.1.1.6	INTEGER	read-write	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.
INT xylnatmTrafficShaperConfSlotIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
INT xylnatmTrafficShaperConfTsNumIndex	1.3.6.1.4.1.800.2.9.1.18.1.1.3	INTEGER	read-only	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).
INT xylnatmTrafficShaperMemPortIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.2	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemSlotIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.1	INTEGER	read-only	The slot on which the traffic shaping module resides.
INT xylnatmTrafficShaperMemTsNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.3	INTEGER	read-only	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.
INT xylnatmTrafficShaperMemVciNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.5	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVpiNumIndex	1.3.6.1.4.1.800.2.9.1.19.1.1.4	INTEGER	read-write	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].
INT xylnatmTrafficShaperMemVpiOper	1.3.6.1.4.1.800.2.9.1.19.1.1.6	INTEGER	read-write	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.
INT xylnatmVcCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.13.1.1.9	INTEGER	read-only	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.
INT xylnatmVcCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.16	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.6	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.5	INTEGER	read-only	The high port number
INT xylnatmVcCrossConnectHighVci	1.3.6.1.4.1.800.2.9.1.13.1.1.8	INTEGER	read-only	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.
INT xylnatmVcCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.7	INTEGER	read-only	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.
INT xylnatmVcCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.15	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.2	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.10	INTEGER	read-write	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.
INT xylnatmVcCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.1	INTEGER	read-only	The incoming slot number
INT xylnatmVcCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.13.1.1.11	INTEGER	read-write	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.
INT xylnatmVcCrossConnectLowVci	1.3.6.1.4.1.800.2.9.1.13.1.1.4	INTEGER	read-only	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.
INT xylnatmVcCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.13.1.1.3	INTEGER	read-only	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.
INT xylnatmVcCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.13.1.1.12	INTEGER	read-write	Enable/disable multicast as per the ui
INT xylnatmVcCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.13.1.1.18	INTEGER	read-write	This is required by NMS to identify PVC's across networks
INT xylnatmVcCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.13.1.1.19	INTEGER	read-write	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
INT xylnatmVcCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.13.1.1.17	INTEGER	read-only	The type of VC...Permanent/Switched/ Soft/control
INT xylnatmVclAAL5Discard	1.3.6.1.4.1.800.2.9.1.10.1.1.19	INTEGER	read-write	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.
INT xylnatmVclAltTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.17	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVclChanType	1.3.6.1.4.1.800.2.9.1.10.1.1.6	INTEGER	read-write	The type of Virtual path
INT xylnatmVclF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.10.1.1.23	INTEGER	read-write	Future release
INT xylnatmVclF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.10.1.1.21	INTEGER	read-write	Future release
INT xylnatmVclF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.22	INTEGER	read-write	Future release
INT xylnatmVclF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.20	INTEGER	read-write	Future release
INT xylnatmVclGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.33	INTEGER	read-only	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
INT xylnatmVclGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.10.1.1.34	INTEGER	read-only	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
INT xylnatmVclLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.10.1.1.18	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVclMcGroupId	1.3.6.1.4.1.800.2.9.1.10.1.1.35	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVclMcIngressEgress	1.3.6.1.4.1.800.2.9.1.10.1.1.36	INTEGER	read-only	Always ingress in this release
INT xylnatmVclModDestPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.6	INTEGER	read-write	Port Instance
INT xylnatmVclModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.5	INTEGER	read-write	Slot Instance
INT xylnatmVclModDestStatus	1.3.6.1.4.1.800.2.9.1.15.1.1.9	INTEGER	read-write	To be in sync with the ui we allow modification
INT xylnatmVclModDestVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.8	INTEGER	read-write	Vci instance
INT xylnatmVclModDestVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.7	INTEGER	read-write	Vpi instance
INT xylnatmVclModPortIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclModSlotIndex	1.3.6.1.4.1.800.2.9.1.15.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVclModVclVci	1.3.6.1.4.1.800.2.9.1.15.1.1.4	INTEGER	read-only	Vci instance
INT xylnatmVclModVclVpi	1.3.6.1.4.1.800.2.9.1.15.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVclOamCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.25	INTEGER	read-write	Future release
INT xylnatmVclOamEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.24	INTEGER	read-write	Future release
INT xylnatmVclPortIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVclPrTrackPort1	1.3.6.1.4.1.800.2.9.1.10.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort2	1.3.6.1.4.1.800.2.9.1.10.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPort3	1.3.6.1.4.1.800.2.9.1.10.1.1.13	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVclPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.10.1.1.10	INTEGER	read-only	The dest internal pport
INT xylnatmVclRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.30	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.29	INTEGER	read-write	Future release
INT xylnatmVclRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.31	INTEGER	read-write	Future release
INT xylnatmVclRmDiscard	1.3.6.1.4.1.800.2.9.1.10.1.1.32	INTEGER	read-write	Future release
INT xylnatmVclRmFwdCopy	1.3.6.1.4.1.800.2.9.1.10.1.1.27	INTEGER	read-write	Future release
INT xylnatmVclRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.10.1.1.26	INTEGER	read-write	Future release
INT xylnatmVclRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.10.1.1.28	INTEGER	read-write	Future release
INT xylnatmVclSlotIndex	1.3.6.1.4.1.800.2.9.1.10.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVclStatPortIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.2	INTEGER	read-only	The port number of this slot
INT xylnatmVclStatSlotIndex	1.3.6.1.4.1.800.2.9.1.12.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVclStatsMode	1.3.6.1.4.1.800.2.9.1.10.1.1.9	INTEGER	read-write	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
INT xylnatmVclStatVci	1.3.6.1.4.1.800.2.9.1.12.1.1.4	INTEGER	read-only	The Vci number for the connection
INT xylnatmVclStatVpi	1.3.6.1.4.1.800.2.9.1.12.1.1.3	INTEGER	read-only	The Vpi number for this connection
INT xylnatmVclTransportPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.7	INTEGER	read-write	The transport priority...
INT xylnatmVclUserPriority	1.3.6.1.4.1.800.2.9.1.10.1.1.8	INTEGER	read-write	The user priority 0-15, with 0 being the highest
INT xylnatmVclVci	1.3.6.1.4.1.800.2.9.1.10.1.1.4	INTEGER	read-only	Vcl instance
INT xylnatmVclVpi	1.3.6.1.4.1.800.2.9.1.10.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVpCrossConnectConnectionId	1.3.6.1.4.1.800.2.9.1.14.1.1.7	INTEGER	read-only	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.
INT xylnatmVpCrossConnectH2LOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.14	INTEGER	read-only	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.
INT xylnatmVpCrossConnectHighPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.5	INTEGER	read-only	The high physical port number
INT xylnatmVpCrossConnectHighSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.4	INTEGER	read-only	The value of the high slot number
INT xylnatmVpCrossConnectHighVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.6	INTEGER	read-only	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.
INT xylnatmVpCrossConnectL2HOperStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.13	INTEGER	read-only	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.
INT xylnatmVpCrossConnectLowPortIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.2	INTEGER	read-only	The low physical port number
INT xylnatmVpCrossConnectLowRxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.8	INTEGER	read-write	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.
INT xylnatmVpCrossConnectLowSlotIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.1	INTEGER	read-only	The low slot number
INT xylnatmVpCrossConnectLowTxTrafficDescrIndex	1.3.6.1.4.1.800.2.9.1.14.1.1.9	INTEGER	read-write	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.
INT xylnatmVpCrossConnectLowVpi	1.3.6.1.4.1.800.2.9.1.14.1.1.3	INTEGER	read-only	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.
INT xylnatmVpCrossConnectMCastEnable	1.3.6.1.4.1.800.2.9.1.14.1.1.10	INTEGER	read-write	Whether Mcast should be enabled/disabled for this connection
INT xylnatmVpCrossConnectPvcIdentifier	1.3.6.1.4.1.800.2.9.1.14.1.1.16	INTEGER	read-write	This is required by NMS to id PVC's across networks
INT xylnatmVpCrossConnectRowStatus	1.3.6.1.4.1.800.2.9.1.14.1.1.17	INTEGER	read-write	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
INT xylnatmVpCrossConnectVcType	1.3.6.1.4.1.800.2.9.1.14.1.1.15	INTEGER	read-only	The type of VC...Permanent/Switched/Soft/control
INT xylnatmVplAAL5Discard	1.3.6.1.4.1.800.2.9.1.9.1.1.18	INTEGER	read-write	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.
INT xylnatmVplAltTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.14	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.15	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.16	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplAltTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.13	INTEGER	read-only	Alternate port under failure conditions and will be supported in future release
INT xylnatmVplChanType	1.3.6.1.4.1.800.2.9.1.9.1.1.5	INTEGER	read-write	The type of Virtual path
INT xylnatmVplF4F5CopyEnd2End	1.3.6.1.4.1.800.2.9.1.9.1.1.22	INTEGER	read-write	Future release
INT xylnatmVplF4F5CopySeg	1.3.6.1.4.1.800.2.9.1.9.1.1.20	INTEGER	read-write	Future release
INT xylnatmVplF4F5End2EndEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.21	INTEGER	read-write	Future release
INT xylnatmVplF4F5SegEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.19	INTEGER	read-write	Future release
INT xylnatmVplGcraAPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.32	INTEGER	read-only	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
INT xylnatmVplGcraBPoliceMode	1.3.6.1.4.1.800.2.9.1.9.1.1.33	INTEGER	read-only	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
INT xylnatmVplLgclChanRedirect	1.3.6.1.4.1.800.2.9.1.9.1.1.17	INTEGER	read-write	Permits the user to allow or not allow logical channel redirects
INT xylnatmVplMcGroupId	1.3.6.1.4.1.800.2.9.1.9.1.1.34	INTEGER	read-only	Internal use of multicast group id
INT xylnatmVplMcIngressEgress	1.3.6.1.4.1.800.2.9.1.9.1.1.35	INTEGER	read-only	Always ingress in this release
INT xylnatmVplModDestPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.5	INTEGER	read-write	Port Instance
INT xylnatmVplModDestSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.4	INTEGER	read-write	Slot Instance
INT xylnatmVplModDestStatus	1.3.6.1.4.1.800.2.9.1.16.1.1.7	INTEGER	read-write	To be in sync with the ui we allow modification
INT xylnatmVplModDestVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.6	INTEGER	read-write	Vpi instance
INT xylnatmVplModPortIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplModSlotIndex	1.3.6.1.4.1.800.2.9.1.16.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVplModVplVpi	1.3.6.1.4.1.800.2.9.1.16.1.1.3	INTEGER	read-only	Vpi instance
INT xylnatmVplOamCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.24	INTEGER	read-write	Future release
INT xylnatmVplOamEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.23	INTEGER	read-write	Future release
INT xylnatmVplPortIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.2	INTEGER	read-only	Port Instance
INT xylnatmVplPrTrackPort1	1.3.6.1.4.1.800.2.9.1.9.1.1.10	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort2	1.3.6.1.4.1.800.2.9.1.9.1.1.11	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPort3	1.3.6.1.4.1.800.2.9.1.9.1.1.12	INTEGER	read-only	Used under multicast conditions and will be supported in future releases for load balancing
INT xylnatmVplPrTrackPortBase	1.3.6.1.4.1.800.2.9.1.9.1.1.9	INTEGER	read-only	The destination internal pport
INT xylnatmVplRmBkwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.29	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.28	INTEGER	read-write	Future release
INT xylnatmVplRmBkwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.30	INTEGER	read-write	Future release
INT xylnatmVplRmDiscard	1.3.6.1.4.1.800.2.9.1.9.1.1.31	INTEGER	read-write	Future release
INT xylnatmVplRmFwdCopy	1.3.6.1.4.1.800.2.9.1.9.1.1.26	INTEGER	read-write	Future release
INT xylnatmVplRmFwdEndpt	1.3.6.1.4.1.800.2.9.1.9.1.1.25	INTEGER	read-write	Future release
INT xylnatmVplRmFwdGcraAdv	1.3.6.1.4.1.800.2.9.1.9.1.1.27	INTEGER	read-write	Future release
INT xylnatmVplSlotIndex	1.3.6.1.4.1.800.2.9.1.9.1.1.1	INTEGER	read-only	Slot Instance
INT xylnatmVplStatPortIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.2	INTEGER	read-only	The port number on this slot
INT xylnatmVplStatSlotIndex	1.3.6.1.4.1.800.2.9.1.11.1.1.1	INTEGER	read-only	The slot number of the chassis
INT xylnatmVplStatsMode	1.3.6.1.4.1.800.2.9.1.9.1.1.8	INTEGER	read-write	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
INT xylnatmVplStatVpi	1.3.6.1.4.1.800.2.9.1.11.1.1.3	INTEGER	read-only	The Vpi number for this connection
INT xylnatmVplTransportPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.6	INTEGER	read-write	The transport priority...
INT xylnatmVplUserPriority	1.3.6.1.4.1.800.2.9.1.9.1.1.7	INTEGER	read-write	The user priority 0-15 with 0 being the highest
INT xylnatmVplVpi	1.3.6.1.4.1.800.2.9.1.9.1.1.3	INTEGER	read-only	Vpi instance
No type (64)
atmxInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.2.1.1		not-accessible	This list contains ATM interface configuration parameters and state variables.
atmxInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.2
atmxInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.2.1		not-accessible	This table contains ATM local interface configuration parameters, one entry per ATM interface port.
atmxSvcVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.2.1		not-accessible	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.
atmxSvcVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.2		not-accessible	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.
atmxSvcVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.2.1		not-accessible	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.
atmxSvcVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.2		not-accessible	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.
atmxTrafficDescrGroup	1.3.6.1.4.1.800.2.9.1.8
atmxTrafficDescrParamEntry	1.3.6.1.4.1.800.2.9.1.8.1.1		not-accessible	This list contains ATM traffic descriptor type and the associated parameters.
atmxTrafficDescrParamTable	1.3.6.1.4.1.800.2.9.1.8.1		not-accessible	This table contains information on ATM traffic descriptor type and the associated parameters.
atmxVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.7.1.1		not-accessible	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.
atmxVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.7
atmxVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.7.1		not-accessible	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.
atmxVclEntry	1.3.6.1.4.1.800.2.9.1.3.1.1		not-accessible	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.
atmxVclGroup	1.3.6.1.4.1.800.2.9.1.3
atmxVclTable	1.3.6.1.4.1.800.2.9.1.3.1		not-accessible	The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table.
atmxVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.5.1.1		not-accessible	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.
atmxVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.5
atmxVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.5.1		not-accessible	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.
atmxVplEntry	1.3.6.1.4.1.800.2.9.1.1.1.1		not-accessible	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.
atmxVplGroup	1.3.6.1.4.1.800.2.9.1.1
atmxVplTable	1.3.6.1.4.1.800.2.9.1.1.1		not-accessible	The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table.
xylanCsmMIB	1.3.6.1.4.1.800.2.9.1
xylnatmClockingxCtrlEntry	1.3.6.1.4.1.800.2.9.1.17.1.1		not-accessible	An entry in the Clocking Configuration/control table, containing information about Cell Switching Module (CSM) clocking.
xylnatmClockingxCtrlGroup	1.3.6.1.4.1.800.2.9.1.17
xylnatmClockingxCtrlTable	1.3.6.1.4.1.800.2.9.1.17.1		not-accessible	A table of Clocking configuration and control information.
xylnatmILMIConfEntry	1.3.6.1.4.1.800.2.9.1.4.3.1		not-accessible	This list contains CSM ILMI configuration and state variables
xylnatmILMIConfTable	1.3.6.1.4.1.800.2.9.1.4.3		not-accessible	This table contains CSM ILMI configuration parameters, one entry per CSM physical interface, or per virtual UNI/NNI instance
xylnatmInterfaceConfEntry	1.3.6.1.4.1.800.2.9.1.4.1.1		not-accessible	This list contains xyln specific ATM interface configuration parameters and state variables.
xylnatmInterfaceConfGroup	1.3.6.1.4.1.800.2.9.1.4
xylnatmInterfaceConfTable	1.3.6.1.4.1.800.2.9.1.4.1		not-accessible	This table contains the private ATM local interface configuration parameters, one entry per ATM interface port.
xylnatmInterfaceStatEntry	1.3.6.1.4.1.800.2.9.1.6.1.1		not-accessible	This list contains xylan specific ATM interface configuration parameters and state variables
xylnatmInterfaceStatGroup	1.3.6.1.4.1.800.2.9.1.6
xylnatmInterfaceStatTable	1.3.6.1.4.1.800.2.9.1.6.1		not-accessible	This table contains the statistical information about the interface
xylnatmTrafficShaperConfEntry	1.3.6.1.4.1.800.2.9.1.18.1.1		not-accessible	An entry in the Traffic Shaper Configuration table containing parameters of the traffic shapers of cell switching module.
xylnatmTrafficShaperConfGroup	1.3.6.1.4.1.800.2.9.1.18
xylnatmTrafficShaperConfTable	1.3.6.1.4.1.800.2.9.1.18.1		not-accessible	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.
xylnatmTrafficShaperMemEntry	1.3.6.1.4.1.800.2.9.1.19.1.1		not-accessible	An entry in the Traffic Shaper Membership table containing a VPI/VCI number mapping to a traffic shaper number.
xylnatmTrafficShaperMemGroup	1.3.6.1.4.1.800.2.9.1.19
xylnatmTrafficShaperMemTable	1.3.6.1.4.1.800.2.9.1.19.1		not-accessible	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.
xylnatmVcCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.13.1.1		not-accessible	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.
xylnatmVcCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.13
xylnatmVcCrossConnectTable	1.3.6.1.4.1.800.2.9.1.13.1		not-accessible	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.
xylnatmVclEntry	1.3.6.1.4.1.800.2.9.1.10.1.1		not-accessible	List of xylan specific objects
xylnatmVclGroup	1.3.6.1.4.1.800.2.9.1.10
xylnatmVclModEntry	1.3.6.1.4.1.800.2.9.1.15.1.1		not-accessible	List of xylan specific objects
xylnatmVclModGroup	1.3.6.1.4.1.800.2.9.1.15
xylnatmVclModTable	1.3.6.1.4.1.800.2.9.1.15.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVclStatEntry	1.3.6.1.4.1.800.2.9.1.12.1.1		not-accessible	Contains the stats objects
xylnatmVclStatGroup	1.3.6.1.4.1.800.2.9.1.12
xylnatmVclStatTable	1.3.6.1.4.1.800.2.9.1.12.1		not-accessible	This table contains the xylan specific statistical object
xylnatmVclTable	1.3.6.1.4.1.800.2.9.1.10.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVpCrossConnectEntry	1.3.6.1.4.1.800.2.9.1.14.1.1		not-accessible	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.
xylnatmVpCrossConnectGroup	1.3.6.1.4.1.800.2.9.1.14
xylnatmVpCrossConnectTable	1.3.6.1.4.1.800.2.9.1.14.1		not-accessible	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.
xylnatmVplEntry	1.3.6.1.4.1.800.2.9.1.9.1.1		not-accessible	List of xylan specific objects
xylnatmVplGroup	1.3.6.1.4.1.800.2.9.1.9
xylnatmVplModEntry	1.3.6.1.4.1.800.2.9.1.16.1.1		not-accessible	List of xylan specific objects
xylnatmVplModGroup	1.3.6.1.4.1.800.2.9.1.16
xylnatmVplModTable	1.3.6.1.4.1.800.2.9.1.16.1		not-accessible	This table contains xylan implementation specific objects
xylnatmVplStatEntry	1.3.6.1.4.1.800.2.9.1.11.1.1		not-accessible	Contains the stats objects
xylnatmVplStatGroup	1.3.6.1.4.1.800.2.9.1.11
xylnatmVplStatTable	1.3.6.1.4.1.800.2.9.1.11.1		not-accessible	This table contains the xylan specific statistical object
xylnatmVplTable	1.3.6.1.4.1.800.2.9.1.9.1		not-accessible	This table contains xylan implementation specific objects

RFC description

Vendor-private MIB for Xylan Communications Switch Module (CSM) management.

Start monitoring Xylan/Alcatel OmniSwitch chassis with Cell Switching Module (ATM interface/cell-switching config status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download XYLAN-CSM-MIB

This MIB depends on

Related MIBs

What Is XYLAN-CSM-MIB?

Supported Devices

Monitoring Examples

RFC description