XYLAN-CSM-MIB: View SNMP OID List / Download MIB

The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table.

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.

The slot number of the chassis

The port number of the csm board

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.

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. Enumeration: 'down': 2, 'up': 1.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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.

The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the receive direction of the VPL.

The value of this object identifies the row in the atmxTrafficDescrParamTable which applies to the transmit direction of the VPL.

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.

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.. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection. Enumeration: 'on': 2, 'off': 1.

This table contains ATM local interface configuration parameters, one entry per ATM interface port.

This list contains ATM interface configuration parameters and state variables.

The slot number of the chassis

The slot number for the CSM board

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.

The maximum number of VCCs (PVCs and SVCs) supported at this ATM interface.

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.

The number of VCCs (PVCs and SVCs) configured for use at the ATM interface.

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.

The maximum number of active VCI bits configured for use at this ATM interface.

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.

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.

The type of primary ATM address configured for use at this ATM interface. Enumeration: 'nsapE164': 2, 'nativeE164': 3, 'other': 4, 'private': 1.

The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table.

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.

The slot number

The port number of the csm board

The VPI value of the VCL. The maximum VPI value cannot exceed the value allowable by the atmInterfaceMaxVpiBits.

The VCI value of the VCL. The maximum VCI value cannot exceed the value allowable by the atmInterfaceMaxVciBits.

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. Enumeration: 'down': 2, 'up': 1.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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.

The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.

The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.

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. Enumeration: 'unknown': 5, 'aal1': 1, 'other': 4, 'aal34': 2, 'aal5': 3.

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.

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.

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. Enumeration: 'vcMultiplexLANemulation8023': 5, 'vcMultiplexBridgedProtocol8023': 2, 'vcMultiplexLANemulation8025': 6, 'llcEncapsulation': 7, 'unknown': 10, 'multiprotocolFrameRelaySscs': 8, 'other': 9, 'vcMultiplexRoutedProtocol': 1, 'vcMultiplexBridgedProtocol8025': 3, 'vcMultiplexBridgedProtocol8026': 4.

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.

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. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

Indicates whether the same traffic parameters are used for both the transmit and receive sides of a virtual connection. Enumeration: 'on': 2, 'off': 1.

This table contains the private ATM local interface configuration parameters, one entry per ATM interface port.

This list contains xyln specific ATM interface configuration parameters and state variables.

The slot number of the chassis

The port number of the chassis

The name in ascii characters describing the interface

The transmission type at this interface. The type is either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b encoding method. Enumeration: 'fourb5b': 4, 'unknown': 1, 'ds3': 3, 'ds1': 8, 'sonetSts3': 2, 'sonetSts12': 7, 'eightb10b': 5, 'e1': 9, 'internal': 20, 'e3': 6.

The signaling type at this interface. Enumeration: 'nni-iisp-network': 4, 'nni-iisp-user': 5, 'private': 2, 'other': 6, 'pnni10': 3, 'public': 1.

The physical media type from this physical port Enumeration: 'coax': 2, 'unknown': 1, 'utp': 6, 'internal': 7, 'stp': 5, 'singlemode': 3, 'multimode': 4.

The AtmAddress @ this interface. The AtmAddress should be a 20 octet hex number.

This object describes whether this interface is switched off or allowing traffic to pass thru or is in normal mode. Enumeration: 'passthr': 2, 'off': 1, 'normal': 3.

The Oper status @ this interface is reflected by the status of the object. Enumeration: 'down': 2, 'up': 1.

The QSAAL status @ this interface is reflected by the status of the object. Enumeration: 'down': 2, 'up': 1.

The Ilmi Status @ this interface. Enumeration: 'down': 2, 'up': 1.

This object indicates whether Cut-Over is enabled or disabled @ this interface Enumeration: 'disabled': 2, 'enabled': 1.

The Cut-Over slot number of the chassis

The Cut Over Port number of the chassis

True clears the stats for this port Enumeration: 'false': 2, 'true': 1.

True clears the chan stats Enumeration: 'false': 2, 'true': 1.

True clears all the port stats in this slot. Enumeration: 'false': 2, 'true': 1.

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 Enumeration: 'sonet12c': 3, 'sdh': 2, 'sonet3c': 1, 'notApplicable': 4.

The state of Ilmi for the instanced port. Setting this object to disable, would prevent any ILMI queries being sent out on this port. Enumeration: 'enable': 1, 'disable': 2.

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. Enumeration: 'local': 1, 'loop': 2.

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. Enumeration: 'oscillator': 1, 'busLine19M': 3, 'busLine8K': 2.

UNI Version used in the chassis Enumeration: 'uni30': 1, 'uni31': 2, 'uniIisp': 3.

This table contains CSM ILMI configuration parameters, one entry per CSM physical interface, or per virtual UNI/NNI instance

This list contains CSM ILMI configuration and state variables

The slot number this entry represents

The port number this entry represents

The Virtual UNI/NNI instance this entry represents

Indicate whether ILMI is enabled on this port, or on this Virtual UNI/NNI instance Enumeration: 'enable': 2, 'disable': 1.

Indicate whether ILMI polling is enabled on this port, or on this Virtual UNI/NNI instance Enumeration: 'enable': 2, 'disable': 1.

Indicate whether CSM auto cfg is enabled on this port, or on this Virtual UNI/NNI instance Enumeration: 'enable': 2, 'disable': 1.

The status of auto configuration procedure on this port, or this Virtual UNI/NNI instance Enumeration: 'inProgress': 3, 'idle': 2, 'cfgDone': 1.

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 Enumeration: 'unknown': 1, 'phy': 3, 'phyLogic': 2, 'logic': 4.

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 Enumeration: 'pnni': 2, 'iispNetwork': 3, 'publicUNI': 5, 'iispUser': 4, 'privateUNI': 1.

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 Enumeration: 'uni30': 1, 'uni31': 2, 'uni40': 3.

Current operational interface type for this CSM port or virtual UNI/NNI instance Enumeration: 'pnni': 2, 'iispNetwork': 3, 'publicUNI': 5, 'iispUser': 4, 'privateUNI': 1.

Current operational signaling version for this CSM port or virtual UNI/NNI instance Enumeration: 'uni30': 1, 'uni31': 2, 'uni40': 3.

Current ILMI version running on this CSM port or virtual UNI/NNI instance Enumeration: 'ilmi40': 2, 'unsupported': 1.

The UNI type this port gathered from its peer port through ILMI Enumeration: 'public': 1, 'private': 2.

The signaling version this port gathered from its peer port through ILMI Enumeration: 'uni30': 1, 'uni31': 2, 'uni40': 3.

The device type this port gathered from its peer port through ILMI Enumeration: 'node': 2, 'user': 1.

The NNI signaling version this port gathered from its peer port through ILMI Enumeration: 'iisp': 2, 'pnni10': 3, 'unsupported': 1.

The ILMI version this port gathered from its peer port through ILMI Enumeration: 'ilmi40': 2, 'unsupported': 1.

The ATM VP Cross Connect table. A bi- directional VP cross-connect which cross-connects two VPLs is modeled as one entry in this table.

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.

A unique value to identify this VP Cross Connect

The low slot number

The low physical port number

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.

The value of the high slot number

The high physical port number

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.

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. Enumeration: 'down': 2, 'up': 1.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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.

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.

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. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

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.

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.

The low slot of the SVC VP cross-connect.

The incoming slot for this SVC

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.

The outgoing slot for this SVC

The outgoing port for this SVC

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.

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.

The low end connections Traffic Descriptor Index

The high connections traffic descriptor index

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

This table contains the statistical information about the interface

This list contains xylan specific ATM interface configuration parameters and state variables

The slot number in the switch

The port number in this slot

The total number of Received Cells at this interface (OC3, OC12, ATM25...)

The total number of received cells at this interface with Cell loss priority of zero

The total number of received cells at this interface with Cell loss Priority of zero or one

The total number of transmitted cells at this interface

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

The number of cells marked by policing that violated their traffic contract for clp0+1 cells

The total number of cells discarded at this interface due to congestion, policing and unknown vpi/vci's

The number of Clp0 cells discarded due to congestion

The number of Clp1 cells discarded due to congestion

The total number of Clp0 cells discarded due to policing on Clp0+1 cells

The total number of cell loss priority one cells discarded due to policing on Clp0+1 cells

The total number of Clp0 cells discarded due to policing on cell loss priority zero cells

The total number of cell loss prioity one cells discarded due to policing on Clp0+1 cells

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

The total number of unknown Vpi cells recieved at this interface that dont correspond to any channels vpi

The total number of unknown Vci cells recieved at this interface that dont correspond to any channels vci

Type of UNI used on this interface...Public or Private Enumeration: 'public': 1, 'private': 2.

UNI Version used in the chassis Enumeration: 'uni30': 1, 'uni31': 2.

The remaining bandwidth available on this port thru which connections can be created and cells can be received.

The remaining bandwidth available on this port thru which connections can be created for cells to be transmitted

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.

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.

A unique value to identify this VC Cross Connect

The low port number

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.

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.

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.

The high port number

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.

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.

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.

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. Enumeration: 'down': 2, 'up': 1.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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.

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.

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. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

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.

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.

The incoming slot for this SVC.

The incoming port for this SVC.

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.

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.

The outgoing slot for this SVC

The outgoing port for this SVC

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.

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.

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.

The low end connections Traffic Descriptor Index

The high connections traffic descriptor index

This object is used to indicate the status of the SVC in the atmSvcVcCrossConnectTable.

This table contains information on ATM traffic descriptor type and the associated parameters.

This list contains ATM traffic descriptor type and the associated parameters.

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

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. Enumeration: 'atmxNoClpNoScr': 2, 'atmxClpTaggingScr': 7, 'atmxNoTrafficDescriptor': 1, 'atmxClpTaggingNoScr': 4, 'atmxClpNoTaggingNoScr': 3, 'atmxNoClpScr': 5, 'atmxClpNoTaggingScr': 6.

The first parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.

The second parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.

The third parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.

The fourth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.

The fifth parameter of the ATM traffic descriptor used according to the value of atmxTrafficDescrType.

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.

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 Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

This table contains xylan implementation specific objects

List of xylan specific objects

Slot Instance

Port Instance

Vpi instance

An ascii value for the connection

The type of Virtual path Enumeration: 'unknown': 1, 'vpNNI': 5, 'vpUni': 6.

The transport priority... Enumeration: 'qosAbr': 7, 'qosUbr': 8, 'qosCbr': 3, 'qosVbrNrt': 6, 'qosCbrPrs': 2, 'qosVbrRt': 5.

The user priority 0-15 with 0 being the highest

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 Enumeration: 'mrkGcraDxCell': 2, 'cntGcraDxCell': 1, 'cntGcraPsCell': 3, 'mrkGcraPsCell': 4.

The destination internal pport

Used under multicast conditions and will be supported in future releases for load balancing

Used under multicast conditions and will be supported in future releases for load balancing

Used under multicast conditions and will be supported in future releases for load balancing

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Permits the user to allow or not allow logical channel redirects Enumeration: 'allowed': 2, 'notAllowed': 1.

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. Enumeration: 'earlyPktDiscard': 1, 'partialPktDiscard': 3, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

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 Enumeration: 'gcraEmMarkClp0DxClp1': 2, 'gcraEmDxAll': 1, 'gcraEmMarkAllDxAll': 3, 'gcraEmMarkClp0DxAll': 4.

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 Enumeration: 'gcraEmMarkClp0DxClp1': 2, 'gcraEmDxAll': 1, 'gcraEmMarkAllDxAll': 3, 'gcraEmMarkClp0DxAll': 4.

Internal use of multicast group id

Always ingress in this release Enumeration: 'ingress': 1, 'egress': 2.

This table contains xylan implementation specific objects

List of xylan specific objects

Slot Instance

Port Instance

Vpi instance

Vcl instance

An ascii value for the connection

The type of Virtual path Enumeration: 'vcUni': 4, 'unknown': 1, 'vcNni': 3.

The transport priority... Enumeration: 'qosAbr': 7, 'qosUbr': 8, 'qosCbr': 3, 'qosVbrNrt': 6, 'qosCbrPrs': 2, 'qosVbrRt': 5.

The user priority 0-15, with 0 being the highest

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 Enumeration: 'mrkGcraDxCell': 2, 'cntGcraDxCell': 1, 'cntGcraPsCell': 3, 'mrkGcraPsCell': 4.

The dest internal pport

Used under multicast conditions and will be supported in future releases for load balancing

Used under multicast conditions and will be supported in future releases for load balancing

Used under multicast conditions and will be supported in future releases for load balancing

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Alternate port under failure conditions and will be supported in future release

Permits the user to allow or not allow logical channel redirects Enumeration: 'allowed': 2, 'notAllowed': 1.

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. Enumeration: 'earlyPktDiscard': 1, 'partialPktDiscard': 3, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

Future release Enumeration: 'enable': 1, 'disable': 2.

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 Enumeration: 'gcraEmMarkClp0DxClp1': 2, 'gcraEmDxAll': 1, 'gcraEmMarkAllDxAll': 3, 'gcraEmMarkClp0DxAll': 4.

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 Enumeration: 'gcraEmMarkClp0DxClp1': 2, 'gcraEmDxAll': 1, 'gcraEmMarkAllDxAll': 3, 'gcraEmMarkClp0DxAll': 4.

Internal use of multicast group id

Always ingress in this release Enumeration: 'ingress': 1, 'egress': 2.

This table contains the xylan specific statistical object

Contains the stats objects

The slot number of the chassis

The port number on this slot

The Vpi number for this connection

The total number of cells received on this connection identified by the slot/port/vpi

The total number of cells transmitted on this connection identified by the slot/port/vpi

The total number of received cells with Clp0 received on this connection identified by slot/port/vpi

The total number of received cells with Clp1 received on this connection identified by slot/port/vpi

The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion

The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion

The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells

The total number of Clp1 cells discarded due to policing on Clp0+1 cells

The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells

The total number of Clp1 cells discarded due to policing on Clp0+1 cells

This table contains the xylan specific statistical object

Contains the stats objects

The slot number of the chassis

The port number of this slot

The Vpi number for this connection

The Vci number for the connection

The total number of cells received on this connection identified by the slot/port/vpi/vci

The total number of cells transmitted on this connection identified by the slot/port/vpi/vci

The total number of received cells with Clp0 received on this connection identified by slot/port/vpi/vci

The total number of received cells with Clp1 received on this connection identified by slot/port/vpi/vci

The total number of cell loss priority zero cells discarded on this connection at this interface identified by the slot/port due to congestion

The total number of cell loss priority one cells discarded on this connection at this interface identified by the slot/port due to congestion

The number of Clp0 cells discarded on this connection due to policing on Clp0+1 cells

The total number of Clp1 cells discarded due to policing on Clp0+1 cells

The total number of Clp0 cells discarded due to policing on Clp0+1 cells

The total number of Clp1 cells discarded due to policing on Clp0+1 cells

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.

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.

The incoming slot number

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.

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.

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.

The high port number

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.

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.

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.

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. Enumeration: 'unknown': 4, 'multicastChild': 2, 'nonMulticastParent': 3, 'multicastParent': 1.

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.

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.

Enable/disable multicast as per the ui Enumeration: 'disabled': 2, 'enabled': 1.

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.

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.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

The type of VC...Permanent/Switched/ Soft/control Enumeration: 'control': 4, 'pvc': 1, 'svc': 2, 'softPvc': 3.

This is required by NMS to identify PVC's across networks

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 Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

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.

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.

The low slot number

The low physical port number

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.

The value of the high slot number

The high physical port number

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.

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. Enumeration: 'unknown': 4, 'multicastChild': 2, 'nonMulticastParent': 3, 'multicastParent': 1.

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.

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.

Whether Mcast should be enabled/disabled for this connection Enumeration: 'enable': 1, 'disable': 2.

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.

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.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

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. Enumeration: 'unknown': 1, 'end2endup': 2, 'end2endDown': 3, 'localDown': 5, 'localUpEndToEndUnknown': 4.

The type of VC...Permanent/Switched/Soft/control Enumeration: 'control': 4, 'pvc': 1, 'svc': 2, 'softPvc': 3.

This is required by NMS to id PVC's across networks

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 Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

This table contains xylan implementation specific objects

List of xylan specific objects

Slot Instance

Port Instance

Vpi instance

Vci instance

Slot Instance

Port Instance

Vpi instance

Vci instance

To be in sync with the ui we allow modification Enumeration: 'active': 4, 'create': 1, 'modify': 2, 'delete': 3.

This table contains xylan implementation specific objects

List of xylan specific objects

Slot Instance

Port Instance

Vpi instance

Slot Instance

Port Instance

Vpi instance

To be in sync with the ui we allow modification Enumeration: 'active': 4, 'create': 1, 'modify': 2, 'delete': 3.

A table of Clocking configuration and control information.

An entry in the Clocking Configuration/control table, containing information about Cell Switching Module (CSM) clocking.

The Bus Signal function used for clocking CSM modules. This is used as a unique ID to identify a clocking line on the bus. Enumeration: 'nineteenMhz': 2, 'eightKhz': 1.

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. Enumeration: 'primary': 1, 'tertiary': 3, 'secondary': 2.

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. Enumeration: 'active': 2, 'standby': 3, 'inactive': 1.

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. Enumeration: 'receiveDataDerived': 2, 'onboardOscillator': 3, 'notConfigured': 1.

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.

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.

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.

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.

An entry in the Traffic Shaper Configuration table containing parameters of the traffic shapers of cell switching module.

The slot on which the traffic shaping module resides.

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.

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).

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.

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.

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.

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.

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.

An entry in the Traffic Shaper Membership table containing a VPI/VCI number mapping to a traffic shaper number.

The slot on which the traffic shaping module resides.

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.

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.

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].

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].

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. Enumeration: 'none': 1, 'add': 2, 'rem': 3.