XYLAN-CSM-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for XYLAN-CSM-MIB.
394
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
394 total| Object Name |
|---|
xylanCsmMIB OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1 |
RFC1213-MIB Unknown .1.3.6.1.4.1.800.2.9.1 |
atmxVplGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.1 |
atmxVplTableThe Virtual Path Link (VPL) table. A
bi-directional VPL is modeled as one entry
in this table. SEQUENCE OF AtmxVplEntry .1.3.6.1.4.1.800.2.9.1.1.1 |
atmxVplEntryAn 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. AtmxVplEntry .1.3.6.1.4.1.800.2.9.1.1.1.1 |
atmxVplSlotIndexThe slot number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.1.1.1.1 |
atmxVplPortIndexThe port number of the csm boardro INTEGER .1.3.6.1.4.1.800.2.9.1.1.1.1.2 |
atmxVplVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.1.1.1.3 |
atmxVplAdminStatusThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.1.1.1.4 |
atmxVplOperStatusThis 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.1.1.1.5 |
atmxVplLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.1.1.1.6 |
atmxVplReceiveTrafficDescrIndexThe value of this object identifies the row
in the atmxTrafficDescrParamTable which
applies to the receive direction of the VPL.rw AtmxTrafficDescrParamIndex .1.3.6.1.4.1.800.2.9.1.1.1.1.7 |
atmxVplTransmitTrafficDescrIndexThe value of this object identifies the row
in the atmxTrafficDescrParamTable which
applies to the transmit direction of the VPL.rw AtmxTrafficDescrParamIndex .1.3.6.1.4.1.800.2.9.1.1.1.1.8 |
atmxVplCrossConnectIdentifierThis 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.1.1.1.9 |
atmxVplRowStatusThis 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..rw Enumeration .1.3.6.1.4.1.800.2.9.1.1.1.1.10 |
atmxVplBidirectIndicates whether the same traffic parameters are used
for both the transmit and receive sides of a virtual
connection.rw Enumeration .1.3.6.1.4.1.800.2.9.1.1.1.1.11 |
atmxInterfaceConfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.2 |
atmxInterfaceConfTableThis table contains ATM local interface
configuration parameters, one entry per ATM
interface port. SEQUENCE OF AtmxInterfaceConfEntry .1.3.6.1.4.1.800.2.9.1.2.1 |
atmxInterfaceConfEntryThis list contains ATM interface configuration
parameters and state variables. AtmxInterfaceConfEntry .1.3.6.1.4.1.800.2.9.1.2.1.1 |
atmxInterfaceSlotIndexThe slot number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.1 |
atmxInterfacePortIndexThe slot number for the CSM boardro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.2 |
atmxInterfaceMaxVpcsThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.3 |
atmxInterfaceMaxVccsThe maximum number of VCCs (PVCs and SVCs)
supported at this ATM interface.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.4 |
atmxInterfaceConfVpcsThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.5 |
atmxInterfaceConfVccsThe number of VCCs (PVCs and SVCs)
configured for use at the ATM interface.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.6 |
atmxInterfaceMaxActiveVpiBitsThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.7 |
atmxInterfaceMaxActiveVciBitsThe maximum number of active VCI bits
configured for use at this ATM interface.rw INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.8 |
atmxInterfaceIlmiVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.9 |
atmxInterfaceIlmiVciThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.2.1.1.10 |
atmxInterfaceAddressTypeThe type of primary ATM address configured
for use at this ATM interface.ro Enumeration .1.3.6.1.4.1.800.2.9.1.2.1.1.11 |
atmxVclGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.3 |
atmxVclTableThe Virtual Channel Link (VCL) table. A
bi-directional VCL is modeled as one entry
in this table. SEQUENCE OF AtmxVclEntry .1.3.6.1.4.1.800.2.9.1.3.1 |
atmxVclEntryAn 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. AtmxVclEntry .1.3.6.1.4.1.800.2.9.1.3.1.1 |
atmxVclSlotIndexThe slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.1 |
atmxVclPortIndexThe port number of the csm boardro INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.2 |
atmxVclVpiThe VPI value of the VCL.
The maximum VPI value cannot
exceed the value allowable by the
atmInterfaceMaxVpiBits.ro INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.3 |
atmxVclVciThe VCI value of the VCL.
The maximum VCI value cannot
exceed the value allowable by the
atmInterfaceMaxVciBits.ro INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.4 |
atmxVclAdminStatusThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.5 |
atmxVclOperStatusThis 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.6 |
atmxVclLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.3.1.1.7 |
atmxVclReceiveTrafficDescrIndexThe value of this object identifies the row
in the ATM Traffic Descriptor Table which
applies to the receive direction of this VCL.rw AtmxTrafficDescrParamIndex .1.3.6.1.4.1.800.2.9.1.3.1.1.8 |
atmxVclTransmitTrafficDescrIndexThe value of this object identifies the row
of the ATM Traffic Descriptor Table which applies
to the transmit direction of this VCL.rw AtmxTrafficDescrParamIndex .1.3.6.1.4.1.800.2.9.1.3.1.1.9 |
atmxVccAalTypeAn 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.10 |
atmxVccAal5CpcsTransmitSduSizeAn 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.11 |
atmxVccAal5CpcsReceiveSduSizeAn 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.12 |
atmxVccAal5EncapsTypeAn 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.13 |
atmxVclCrossConnectIdentifierThis 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.3.1.1.14 |
atmxVclRowStatusThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.15 |
atmxVclBidirectIndicates whether the same traffic parameters are used
for both the transmit and receive sides of a virtual
connection.rw Enumeration .1.3.6.1.4.1.800.2.9.1.3.1.1.16 |
xylnatmInterfaceConfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.4 |
xylnatmInterfaceConfTableThis table contains the private ATM local interface
configuration parameters, one entry per ATM
interface port. SEQUENCE OF XylnAtmInterfaceConfEntry .1.3.6.1.4.1.800.2.9.1.4.1 |
xylnatmInterfaceConfEntryThis list contains xyln specific ATM interface
configuration parameters and state variables. XylnAtmInterfaceConfEntry .1.3.6.1.4.1.800.2.9.1.4.1.1 |
xylnatmInterfaceSlotIndexThe slot number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.4.1.1.1 |
xylnatmInterfacePortIndexThe port number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.4.1.1.2 |
xylnatmInterfaceDescriptionThe name in ascii characters describing the interfacerw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.4.1.1.3 |
xylnatmInterfaceTransTypeThe transmission type at this interface. The type is
either an unknown type or sonet/ds3/ds12/4b-5b/8b_10b
encoding method.ro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.4 |
xylnatmInterfaceTypeThe signaling type at this interface.rw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.5 |
xylnatmInterfaceMediaTypeThe physical media type from this physical portro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.6 |
xylnatmInterfaceAtmAddressThe AtmAddress @ this interface. The AtmAddress should
be a 20 octet hex number.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.4.1.1.7 |
xylnatmInterfacePortModeThis object describes whether this interface is
switched off or allowing traffic to pass thru or
is in normal mode.ro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.8 |
xylnatmInterfaceOperStatusThe Oper status @ this interface is reflected by
the status of the object.ro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.9 |
xylnatmInterfaceQsaalStatusThe QSAAL status @ this interface is reflected by
the status of the object.ro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.10 |
xylnatmInterfaceIlmiStatusThe Ilmi Status @ this interface.ro Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.11 |
xylnatmInterfaceTpRedirectThis object indicates whether Cut-Over is enabled or
disabled @ this interfacero Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.12 |
xylnatmInterfaceCutOverSlotThe Cut-Over slot number of the chassisrw INTEGER .1.3.6.1.4.1.800.2.9.1.4.1.1.13 |
xylnatmInterfaceCutOverPortThe Cut Over Port number of the chassisrw INTEGER .1.3.6.1.4.1.800.2.9.1.4.1.1.14 |
xylnatmInterfaceClearPortStatsTrue clears the stats for this portrw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.15 |
xylnatmInterfaceClearChanStatsTrue clears the chan statsrw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.16 |
xylnatmInterfaceClearSlotStatsTrue clears all the port stats in this slot.rw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.17 |
xylnatmInterfaceTransmissionTypeThe 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 SDHrw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.18 |
xylnatmInterfaceIlmiStateThe state of Ilmi for the instanced port. Setting this
object to disable, would prevent any ILMI queries being
sent out on this port.rw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.19 |
xylnatmInterfaceTimingModeThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.20 |
xylnatmInterfaceLocalSrcThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.21 |
xylnatmInterfaceUniVersionUNI Version used in the chassisrw Enumeration .1.3.6.1.4.1.800.2.9.1.4.1.1.22 |
xylnatmILMIConfTableThis table contains CSM ILMI configuration parameters,
one entry per CSM physical interface, or per virtual
UNI/NNI instance SEQUENCE OF XylnatmILMIConfEntry .1.3.6.1.4.1.800.2.9.1.4.3 |
xylnatmILMIConfEntryThis list contains CSM ILMI configuration and state
variables XylnatmILMIConfEntry .1.3.6.1.4.1.800.2.9.1.4.3.1 |
xylnatmILMIConfSlotThe slot number this entry representsro INTEGER .1.3.6.1.4.1.800.2.9.1.4.3.1.1 |
xylnatmILMIConfPortThe port number this entry representsro INTEGER .1.3.6.1.4.1.800.2.9.1.4.3.1.2 |
xylnatmILMIConfInstanceThe Virtual UNI/NNI instance this entry representsro INTEGER .1.3.6.1.4.1.800.2.9.1.4.3.1.3 |
xylnatmILMIConfILMIEnableIndicate whether ILMI is enabled on this port, or on
this Virtual UNI/NNI instancerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.4 |
xylnatmILMIConfILMIPollEnableIndicate whether ILMI polling is enabled on this port, or
on this Virtual UNI/NNI instancerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.5 |
xylnatmILMIConfAutoCfgEnableIndicate whether CSM auto cfg is enabled on this port, or
on this Virtual UNI/NNI instancerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.6 |
xylnatmILMIConfAutoCfgStatusThe status of auto configuration procedure on this port, or
this Virtual UNI/NNI instancero Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.7 |
xylnatmILMIConfAutoCfgTriggIndicate 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
narrativerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.8 |
xylnatmILMIConfAutoCfgDfltIfThe default interface type this port or virtual UNI/NNI instance
will take when auto configuration procedure fails to detect its
peer port's interface typerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.9 |
xylnatmILMIConfAutoCfgDfltSigVerThe default signaling version this port or virtual UNI/NNI instance
will take when auto configuration procedure fails to detect its
peer port's signaling versionrw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.10 |
xylnatmILMIConfAutoCfgCurIfCurrent operational interface type for this CSM port or virtual
UNI/NNI instancerw Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.11 |
xylnatmILMIConfAutoCfgCurSigVerCurrent operational signaling version for this CSM port or virtual
UNI/NNI instancero Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.12 |
xylnatmILMIConfAutoCfgCurILMIVerCurrent ILMI version running on this CSM port or virtual UNI/NNI
instancero Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.13 |
xylnatmILMIConfPeerUniTypeThe UNI type this port gathered from its peer port through ILMIro Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.14 |
xylnatmILMIConfPeerUniVerThe signaling version this port gathered from its peer port through ILMIro Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.15 |
xylnatmILMIConfPeerDevTypeThe device type this port gathered from its peer port through ILMIro Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.16 |
xylnatmILMIConfPeerNNISigVerThe NNI signaling version this port gathered from its peer port through ILMIro Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.17 |
xylnatmILMIConfPeerILMIVerThe ILMI version this port gathered from its peer port through ILMIro Enumeration .1.3.6.1.4.1.800.2.9.1.4.3.1.18 |
atmxVpCrossConnectGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.5 |
atmxVpCrossConnectTableThe ATM VP Cross Connect table. A bi-
directional VP cross-connect which
cross-connects two VPLs is modeled
as one entry in this table. SEQUENCE OF AtmxVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.5.1 |
atmxVpCrossConnectEntryAn 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. AtmxVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.5.1.1 |
atmxVpCrossConnectIndexA unique value to identify this VP Cross Connectro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.1 |
atmxVpCrossConnectLowSlotIndexThe low slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.2 |
atmxVpCrossConnectLowPortIndexThe low physical port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.3 |
atmxVpCrossConnectLowVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.4 |
atmxVpCrossConnectHighSlotIndexThe value of the high slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.5 |
atmxVpCrossConnectHighPortIndexThe high physical port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.6 |
atmxVpCrossConnectHighVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.5.1.1.7 |
atmxVpCrossConnectAdminStatusThe 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.5.1.1.8 |
atmxVpCrossConnectL2HOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.5.1.1.9 |
atmxVpCrossConnectH2LOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.5.1.1.10 |
atmxVpCrossConnectL2HLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.5.1.1.11 |
atmxVpCrossConnectH2LLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.5.1.1.12 |
atmxVpCrossConnectRowStatusThe 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.5.1.1.13 |
atmxSvcVpCrossConnectTableThe 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. SEQUENCE OF AtmxSvcVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.5.2 |
atmxSvcVpCrossConnectEntryAn 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. AtmxSvcVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.5.2.1 |
atmxSvcVpCrossConnectLowSlotIndexThe low slot of the SVC VP cross-connect. INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.1 |
atmxSvcVpCrossConnectLowPortIndexThe incoming slot for this SVC INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.2 |
atmxSvcVpCrossConnectLowVpiThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.3 |
atmxSvcVpCrossConnectHighSlotIndexThe outgoing slot for this SVC INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.4 |
atmxSvcVpCrossConnectHighPortIndexThe outgoing port for this SVC INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.5 |
atmxSvcVpCrossConnectHighVpiThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.6 |
atmxSvcVpCrossConnectCreationTimeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.5.2.1.7 |
atmxSvcVpCrossConnectLowTDIndexThe low end connections Traffic Descriptor Indexro INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.8 |
atmxSvcVpCrossConnectHighTDIndexThe high connections traffic descriptor indexro INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.9 |
atmxSvcVpCrossConnectRowStatusThis object can be used to delete rows in the
atmSvcVpCrossConnectTable. But unless we require it
for specific reasons we will not allow creation/deletionro INTEGER .1.3.6.1.4.1.800.2.9.1.5.2.1.10 |
xylnatmInterfaceStatGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.6 |
xylnatmInterfaceStatTableThis table contains the statistical information about
the interface SEQUENCE OF XylnatmInterfaceStatEntry .1.3.6.1.4.1.800.2.9.1.6.1 |
xylnatmInterfaceStatEntryThis list contains xylan specific ATM interface
configuration parameters and state variables XylnatmInterfaceStatEntry .1.3.6.1.4.1.800.2.9.1.6.1.1 |
xylnatmInterfaceStatSlotIndexThe slot number in the switchro INTEGER .1.3.6.1.4.1.800.2.9.1.6.1.1.1 |
xylnatmInterfaceStatPortIndexThe port number in this slotro INTEGER .1.3.6.1.4.1.800.2.9.1.6.1.1.2 |
xylnatmInterfaceStatRxCellsThe total number of Received Cells at this interface
(OC3, OC12, ATM25...)ro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.3 |
xylnatmInterfaceStatRxClp0CellsThe total number of received cells at this interface
with Cell loss priority of zeroro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.4 |
xylnatmInterfaceStatRxClp1CellsThe total number of received cells at this interface with
Cell loss Priority of zero or onero Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.5 |
xylnatmInterfaceStatTxCellsThe total number of transmitted cells at this interfacero Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.6 |
xylnatmInterfaceStatMarkEfciCellsThe 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 destinationro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.7 |
xylnatmInterfaceStatMarkGcraCellsThe number of cells marked by policing that violated
their traffic contract for clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.8 |
xylnatmInterfaceStatTotalDiscardCellsThe total number of cells discarded at this interface due
to congestion, policing and unknown vpi/vci'sro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.9 |
xylnatmInterfaceStatDxCongClp0CellsThe number of Clp0 cells discarded due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.10 |
xylnatmInterfaceStatDxCongClp1CellsThe number of Clp1 cells discarded due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.11 |
xylnatmInterfaceStatDxGcraClp0CellsThe total number of Clp0 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.12 |
xylnatmInterfaceStatDxGcraClp1CellsThe total number of cell loss priority one cells discarded
due to policing on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.13 |
xylnatmInterfaceStatDxGcrabClp0CellsThe total number of Clp0 cells discarded due to policing
on cell loss priority zero cellsro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.14 |
xylnatmInterfaceStatDxGcrabClp1CellsThe total number of cell loss prioity one cells discarded
due to policing on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.15 |
xylnatmInterfaceStatUnknownVpVcCellsThe 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 interfacero Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.16 |
xylnatmInterfaceStatUnknownVpiCellsThe total number of unknown Vpi cells recieved at this
interface that dont correspond to any channels vpiro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.17 |
xylnatmInterfaceStatUnknownVciCellsThe total number of unknown Vci cells recieved at this
interface that dont correspond to any channels vciro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.18 |
xylnatmInterfaceStatUniTypeType of UNI used on this interface...Public or Privatero Enumeration .1.3.6.1.4.1.800.2.9.1.6.1.1.19 |
xylnatmInterfaceStatUniVersionUNI Version used in the chassisro Enumeration .1.3.6.1.4.1.800.2.9.1.6.1.1.20 |
xylnatmInterfaceStatRemainingRxBandwidthThe remaining bandwidth available on this port thru
which connections can be created and cells can be
received.ro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.21 |
xylnatmInterfaceStatRemainingTxBandwidthThe remaining bandwidth available on this port thru
which connections can be created for cells to be
transmittedro Counter .1.3.6.1.4.1.800.2.9.1.6.1.1.22 |
atmxVcCrossConnectGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.7 |
atmxVcCrossConnectTableThe 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. SEQUENCE OF AtmxVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.7.1 |
atmxVcCrossConnectEntryAn 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. AtmxVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.7.1.1 |
atmxVcCrossConnectIndexA unique value to identify this VC Cross Connectro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.1 |
atmxVcCrossConnectLowSlotIndexThe low port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.2 |
atmxVcCrossConnectLowPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.3 |
atmxVcCrossConnectLowVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.4 |
atmxVcCrossConnectLowVciThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.5 |
atmxVcCrossConnectHighSlotIndexThe high port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.6 |
atmxVcCrossConnectHighPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.7 |
atmxVcCrossConnectHighVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.8 |
atmxVcCrossConnectHighVciThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.1.1.9 |
atmxVcCrossConnectAdminStatusThe 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.7.1.1.10 |
atmxVcCrossConnectL2HOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.7.1.1.11 |
atmxVcCrossConnectH2LOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.7.1.1.12 |
atmxVcCrossConnectL2HLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.7.1.1.13 |
atmxVcCrossConnectH2LLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.7.1.1.14 |
atmxVcCrossConnectRowStatusThe 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.7.1.1.15 |
atmxSvcVcCrossConnectTableThe 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. SEQUENCE OF AtmxSvcVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.7.2 |
atmxSvcVcCrossConnectEntryAn 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. AtmxSvcVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.7.2.1 |
atmxSvcVcCrossConnectLowSlotIndexThe incoming slot for this SVC. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.1 |
atmxSvcVcCrossConnectLowPortIndexThe incoming port for this SVC. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.2 |
atmxSvcVcCrossConnectLowVpiThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.3 |
atmxSvcVcCrossConnectLowVciThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.4 |
atmxSvcVcCrossConnectHighSlotIndexThe outgoing slot for this SVC INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.5 |
atmxSvcVcCrossConnectHighPortIndexThe outgoing port for this SVC INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.6 |
atmxSvcVcCrossConnectHighVpiThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.7 |
atmxSvcVcCrossConnectHighVciThe 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. INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.8 |
atmxSvcVcCrossConnectCreationTimeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.7.2.1.9 |
atmxSvcVcCrossConnectLowTDIndexThe low end connections Traffic Descriptor Indexro INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.10 |
atmxSvcVcCrossConnectHighTDIndexThe high connections traffic descriptor indexro INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.11 |
atmxSvcVcCrossConnectRowStatusThis object is used to indicate the status of the SVC in
the atmSvcVcCrossConnectTable.ro INTEGER .1.3.6.1.4.1.800.2.9.1.7.2.1.12 |
atmxTrafficDescrGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.8 |
atmxTrafficDescrParamTableThis table contains information on ATM traffic
descriptor type and the associated parameters. SEQUENCE OF AtmxTrafficDescrParamEntry .1.3.6.1.4.1.800.2.9.1.8.1 |
atmxTrafficDescrParamEntryThis list contains ATM traffic descriptor
type and the associated parameters. AtmxTrafficDescrParamEntry .1.3.6.1.4.1.800.2.9.1.8.1.1 |
atmxTrafficDescrParamIndexThis 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 etcro AtmxTrafficDescrParamIndex .1.3.6.1.4.1.800.2.9.1.8.1.1.1 |
atmxTrafficDescrTypeThe 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.8.1.1.2 |
atmxTrafficDescrParam1The first parameter of the ATM traffic descriptor
used according to the value of
atmxTrafficDescrType.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.3 |
atmxTrafficDescrParam2The second parameter of the ATM traffic descriptor
used according to the value of
atmxTrafficDescrType.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.4 |
atmxTrafficDescrParam3The third parameter of the ATM traffic descriptor
used according to the value of
atmxTrafficDescrType.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.5 |
atmxTrafficDescrParam4The fourth parameter of the ATM traffic descriptor
used according to the value of
atmxTrafficDescrType.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.6 |
atmxTrafficDescrParam5The fifth parameter of the ATM traffic descriptor
used according to the value of
atmxTrafficDescrType.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.7 |
atmxTrafficQoSClassThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.8.1.1.8 |
atmxTrafficDescrRowStatusThis 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 rowrw Enumeration .1.3.6.1.4.1.800.2.9.1.8.1.1.9 |
xylnatmVplGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.9 |
xylnatmVplTableThis table contains xylan implementation specific
objects SEQUENCE OF XylnatmVplEntry .1.3.6.1.4.1.800.2.9.1.9.1 |
xylnatmVplEntryList of xylan specific objects XylnatmVplEntry .1.3.6.1.4.1.800.2.9.1.9.1.1 |
xylnatmVplSlotIndexSlot Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.1 |
xylnatmVplPortIndexPort Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.2 |
xylnatmVplVpiVpi instancero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.3 |
xylnatmVplConnectionDescrAn ascii value for the connectionrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.9.1.1.4 |
xylnatmVplChanTypeThe type of Virtual pathrw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.5 |
xylnatmVplTransportPriorityThe transport priority...rw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.6 |
xylnatmVplUserPriorityThe user priority 0-15 with 0 being the highestrw INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.7 |
xylnatmVplStatsModeThis 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 cellrw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.8 |
xylnatmVplPrTrackPortBaseThe destination internal pportro INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.9 |
xylnatmVplPrTrackPort1Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.10 |
xylnatmVplPrTrackPort2Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.11 |
xylnatmVplPrTrackPort3Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.12 |
xylnatmVplAltTrackPortBaseAlternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.13 |
xylnatmVplAltTrackPort1Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.14 |
xylnatmVplAltTrackPort2Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.15 |
xylnatmVplAltTrackPort3Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.16 |
xylnatmVplLgclChanRedirectPermits the user to allow or not allow logical channel
redirectsrw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.17 |
xylnatmVplAAL5DiscardThis 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
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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.18 |
xylnatmVplF4F5SegEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.19 |
xylnatmVplF4F5CopySegFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.20 |
xylnatmVplF4F5End2EndEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.21 |
xylnatmVplF4F5CopyEnd2EndFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.22 |
xylnatmVplOamEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.23 |
xylnatmVplOamCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.24 |
xylnatmVplRmFwdEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.25 |
xylnatmVplRmFwdCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.26 |
xylnatmVplRmFwdGcraAdvFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.27 |
xylnatmVplRmBkwdEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.28 |
xylnatmVplRmBkwdCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.29 |
xylnatmVplRmBkwdGcraAdvFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.30 |
xylnatmVplRmDiscardFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.31 |
xylnatmVplGcraAPoliceModeEnforcement 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
allro Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.32 |
xylnatmVplGcraBPoliceModeEnforcement 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
allro Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.33 |
xylnatmVplMcGroupIdInternal use of multicast group idro INTEGER .1.3.6.1.4.1.800.2.9.1.9.1.1.34 |
xylnatmVplMcIngressEgressAlways ingress in this releasero Enumeration .1.3.6.1.4.1.800.2.9.1.9.1.1.35 |
xylnatmVclGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.10 |
xylnatmVclTableThis table contains xylan implementation specific
objects SEQUENCE OF XylnatmVclEntry .1.3.6.1.4.1.800.2.9.1.10.1 |
xylnatmVclEntryList of xylan specific objects XylnatmVclEntry .1.3.6.1.4.1.800.2.9.1.10.1.1 |
xylnatmVclSlotIndexSlot Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.1 |
xylnatmVclPortIndexPort Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.2 |
xylnatmVclVpiVpi instancero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.3 |
xylnatmVclVciVcl instancero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.4 |
xylnatmVclConnectionDescrAn ascii value for the connectionrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.10.1.1.5 |
xylnatmVclChanTypeThe type of Virtual pathrw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.6 |
xylnatmVclTransportPriorityThe transport priority...rw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.7 |
xylnatmVclUserPriorityThe user priority 0-15, with 0 being the highestrw INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.8 |
xylnatmVclStatsModeThis 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 cellrw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.9 |
xylnatmVclPrTrackPortBaseThe dest internal pportro INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.10 |
xylnatmVclPrTrackPort1Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.11 |
xylnatmVclPrTrackPort2Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.12 |
xylnatmVclPrTrackPort3Used under multicast conditions and will be supported
in future releases for load balancingro INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.13 |
xylnatmVclAltTrackPortBaseAlternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.14 |
xylnatmVclAltTrackPort1Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.15 |
xylnatmVclAltTrackPort2Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.16 |
xylnatmVclAltTrackPort3Alternate port under failure conditions and will be
supported in future releasero INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.17 |
xylnatmVclLgclChanRedirectPermits the user to allow or not allow logical channel
redirectsrw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.18 |
xylnatmVclAAL5DiscardThis 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
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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.19 |
xylnatmVclF4F5SegEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.20 |
xylnatmVclF4F5CopySegFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.21 |
xylnatmVclF4F5End2EndEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.22 |
xylnatmVclF4F5CopyEnd2EndFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.23 |
xylnatmVclOamEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.24 |
xylnatmVclOamCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.25 |
xylnatmVclRmFwdEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.26 |
xylnatmVclRmFwdCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.27 |
xylnatmVclRmFwdGcraAdvFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.28 |
xylnatmVclRmBkwdEndptFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.29 |
xylnatmVclRmBkwdCopyFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.30 |
xylnatmVclRmBkwdGcraAdvFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.31 |
xylnatmVclRmDiscardFuture releaserw Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.32 |
xylnatmVclGcraAPoliceModeEnforcement 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
allro Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.33 |
xylnatmVclGcraBPoliceModeEnforcement 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
allro Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.34 |
xylnatmVclMcGroupIdInternal use of multicast group idro INTEGER .1.3.6.1.4.1.800.2.9.1.10.1.1.35 |
xylnatmVclMcIngressEgressAlways ingress in this releasero Enumeration .1.3.6.1.4.1.800.2.9.1.10.1.1.36 |
xylnatmVplStatGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.11 |
xylnatmVplStatTableThis table contains the xylan specific statistical object SEQUENCE OF XylnatmVplStatEntry .1.3.6.1.4.1.800.2.9.1.11.1 |
xylnatmVplStatEntryContains the stats objects XylnatmVplStatEntry .1.3.6.1.4.1.800.2.9.1.11.1.1 |
xylnatmVplStatSlotIndexThe slot number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.11.1.1.1 |
xylnatmVplStatPortIndexThe port number on this slotro INTEGER .1.3.6.1.4.1.800.2.9.1.11.1.1.2 |
xylnatmVplStatVpiThe Vpi number for this connectionro INTEGER .1.3.6.1.4.1.800.2.9.1.11.1.1.3 |
xylnatmVplStatRxCellsThe total number of cells received on this connection
identified by the slot/port/vpiro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.4 |
xylnatmVplStatTxCellsThe total number of cells transmitted on this connection
identified by the slot/port/vpiro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.5 |
xylnatmVplStatRxClp0CellsThe total number of received cells with Clp0 received
on this connection identified by slot/port/vpiro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.6 |
xylnatmVplStatRxClp1CellsThe total number of received cells with Clp1 received
on this connection identified by slot/port/vpiro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.7 |
xylnatmVplStatDxCongClp0CellsThe total number of cell loss priority zero cells
discarded on this connection at this interface identified
by the slot/port due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.8 |
xylnatmVplStatDxCongClp1CellsThe total number of cell loss priority one cells
discarded on this connection at this interface identified
by the slot/port due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.9 |
xylnatmVplStatDxGcraClp0CellsThe number of Clp0 cells discarded on this connection
due to policing on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.10 |
xylnatmVplStatDxGcraClp1CellsThe total number of Clp1 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.11 |
xylnatmVplStatDxGcraBClp0CellsThe number of Clp0 cells discarded on this connection
due to policing on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.12 |
xylnatmVplStatDxGcraBClp1CellsThe total number of Clp1 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.11.1.1.13 |
xylnatmVclStatGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.12 |
xylnatmVclStatTableThis table contains the xylan specific statistical object SEQUENCE OF XylnatmVclStatEntry .1.3.6.1.4.1.800.2.9.1.12.1 |
xylnatmVclStatEntryContains the stats objects XylnatmVclStatEntry .1.3.6.1.4.1.800.2.9.1.12.1.1 |
xylnatmVclStatSlotIndexThe slot number of the chassisro INTEGER .1.3.6.1.4.1.800.2.9.1.12.1.1.1 |
xylnatmVclStatPortIndexThe port number of this slotro INTEGER .1.3.6.1.4.1.800.2.9.1.12.1.1.2 |
xylnatmVclStatVpiThe Vpi number for this connectionro INTEGER .1.3.6.1.4.1.800.2.9.1.12.1.1.3 |
xylnatmVclStatVciThe Vci number for the connectionro INTEGER .1.3.6.1.4.1.800.2.9.1.12.1.1.4 |
xylnatmVclStatRxCellsThe total number of cells received on this connection
identified by the slot/port/vpi/vciro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.5 |
xylnatmVclStatTxCellsThe total number of cells transmitted on this connection
identified by the slot/port/vpi/vciro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.6 |
xylnatmVclStatRxClp0CellsThe total number of received cells with Clp0 received
on this connection identified by slot/port/vpi/vciro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.7 |
xylnatmVclStatRxClp1CellsThe total number of received cells with Clp1 received
on this connection identified by slot/port/vpi/vciro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.8 |
xylnatmVclStatDxCongClp0CellsThe total number of cell loss priority zero cells
discarded on this connection at this interface identified
by the slot/port due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.9 |
xylnatmVclStatDxCongClp1CellsThe total number of cell loss priority one cells
discarded on this connection at this interface identified
by the slot/port due to congestionro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.10 |
xylnatmVclStatDxGcraClp0CellsThe number of Clp0 cells discarded on this connection
due to policing on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.11 |
xylnatmVclStatDxGcraClp1CellsThe total number of Clp1 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.12 |
xylnatmVclStatDxGcraBClp0CellsThe total number of Clp0 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.13 |
xylnatmVclStatDxGcraBClp1CellsThe total number of Clp1 cells discarded due to policing
on Clp0+1 cellsro Counter .1.3.6.1.4.1.800.2.9.1.12.1.1.14 |
xylnatmVcCrossConnectGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.13 |
xylnatmVcCrossConnectTableThe 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. SEQUENCE OF XylnatmVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.13.1 |
xylnatmVcCrossConnectEntryAn 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. XylnatmVcCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.13.1.1 |
xylnatmVcCrossConnectLowSlotIndexThe incoming slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.1 |
xylnatmVcCrossConnectLowPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.2 |
xylnatmVcCrossConnectLowVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.3 |
xylnatmVcCrossConnectLowVciThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.4 |
xylnatmVcCrossConnectHighSlotIndexThe high port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.5 |
xylnatmVcCrossConnectHighPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.6 |
xylnatmVcCrossConnectHighVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.7 |
xylnatmVcCrossConnectHighVciThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.8 |
xylnatmVcCrossConnectConnectionIdThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.9 |
xylnatmVcCrossConnectLowRxTrafficDescrIndexThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.10 |
xylnatmVcCrossConnectLowTxTrafficDescrIndexThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.11 |
xylnatmVcCrossConnectMCastEnableEnable/disable multicast as per the uirw Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.12 |
xylnatmVcCrossConnectL2HLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.13.1.1.13 |
xylnatmVcCrossConnectH2LLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.13.1.1.14 |
xylnatmVcCrossConnectL2HOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.15 |
xylnatmVcCrossConnectH2LOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.16 |
xylnatmVcCrossConnectVcTypeThe type of VC...Permanent/Switched/ Soft/controlro Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.17 |
xylnatmVcCrossConnectPvcIdentifierThis is required by NMS to identify PVC's across networksrw INTEGER .1.3.6.1.4.1.800.2.9.1.13.1.1.18 |
xylnatmVcCrossConnectRowStatusThis 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-pointrw Enumeration .1.3.6.1.4.1.800.2.9.1.13.1.1.19 |
xylnatmVpCrossConnectGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.14 |
xylnatmVpCrossConnectTableThe 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. SEQUENCE OF XylnatmVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.14.1 |
xylnatmVpCrossConnectEntryAn 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. XylnatmVpCrossConnectEntry .1.3.6.1.4.1.800.2.9.1.14.1.1 |
xylnatmVpCrossConnectLowSlotIndexThe low slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.1 |
xylnatmVpCrossConnectLowPortIndexThe low physical port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.2 |
xylnatmVpCrossConnectLowVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.3 |
xylnatmVpCrossConnectHighSlotIndexThe value of the high slot numberro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.4 |
xylnatmVpCrossConnectHighPortIndexThe high physical port numberro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.5 |
xylnatmVpCrossConnectHighVpiThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.6 |
xylnatmVpCrossConnectConnectionIdThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.7 |
xylnatmVpCrossConnectLowRxTrafficDescrIndexThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.8 |
xylnatmVpCrossConnectLowTxTrafficDescrIndexThe 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.9 |
xylnatmVpCrossConnectMCastEnableWhether Mcast should be enabled/disabled for this
connectionrw Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.10 |
xylnatmVpCrossConnectL2HLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.14.1.1.11 |
xylnatmVpCrossConnectH2LLastChangeThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.2.9.1.14.1.1.12 |
xylnatmVpCrossConnectL2HOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.13 |
xylnatmVpCrossConnectH2LOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.14 |
xylnatmVpCrossConnectVcTypeThe type of VC...Permanent/Switched/Soft/controlro Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.15 |
xylnatmVpCrossConnectPvcIdentifierThis is required by NMS to id PVC's across networksrw INTEGER .1.3.6.1.4.1.800.2.9.1.14.1.1.16 |
xylnatmVpCrossConnectRowStatusThis 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-pointrw Enumeration .1.3.6.1.4.1.800.2.9.1.14.1.1.17 |
xylnatmVclModGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.15 |
xylnatmVclModTableThis table contains xylan implementation specific
objects SEQUENCE OF XylnatmVclModEntry .1.3.6.1.4.1.800.2.9.1.15.1 |
xylnatmVclModEntryList of xylan specific objects XylnatmVclModEntry .1.3.6.1.4.1.800.2.9.1.15.1.1 |
xylnatmVclModSlotIndexSlot Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.1 |
xylnatmVclModPortIndexPort Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.2 |
xylnatmVclModVclVpiVpi instancero INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.3 |
xylnatmVclModVclVciVci instancero INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.4 |
xylnatmVclModDestSlotIndexSlot Instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.5 |
xylnatmVclModDestPortIndexPort Instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.6 |
xylnatmVclModDestVclVpiVpi instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.7 |
xylnatmVclModDestVclVciVci instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.15.1.1.8 |
xylnatmVclModDestStatusTo be in sync with the ui we allow modificationrw Enumeration .1.3.6.1.4.1.800.2.9.1.15.1.1.9 |
xylnatmVplModGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.16 |
xylnatmVplModTableThis table contains xylan implementation specific
objects SEQUENCE OF XylnatmVplModEntry .1.3.6.1.4.1.800.2.9.1.16.1 |
xylnatmVplModEntryList of xylan specific objects XylnatmVplModEntry .1.3.6.1.4.1.800.2.9.1.16.1.1 |
xylnatmVplModSlotIndexSlot Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.1 |
xylnatmVplModPortIndexPort Instancero INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.2 |
xylnatmVplModVplVpiVpi instancero INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.3 |
xylnatmVplModDestSlotIndexSlot Instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.4 |
xylnatmVplModDestPortIndexPort Instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.5 |
xylnatmVplModDestVplVpiVpi instancerw INTEGER .1.3.6.1.4.1.800.2.9.1.16.1.1.6 |
xylnatmVplModDestStatusTo be in sync with the ui we allow modificationrw Enumeration .1.3.6.1.4.1.800.2.9.1.16.1.1.7 |
xylnatmClockingxCtrlGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.17 |
xylnatmClockingxCtrlTableA table of Clocking configuration and control information. SEQUENCE OF XylnatmClockingxCtrlEntry .1.3.6.1.4.1.800.2.9.1.17.1 |
xylnatmClockingxCtrlEntryAn entry in the Clocking Configuration/control table,
containing information about Cell Switching Module
(CSM) clocking. XylnatmClockingxCtrlEntry .1.3.6.1.4.1.800.2.9.1.17.1.1 |
xylnatmClockingxCtrlBusLineThe Bus Signal function used for clocking CSM modules.
This is used as a unique
ID to identify a clocking line on the bus.ro Enumeration .1.3.6.1.4.1.800.2.9.1.17.1.1.1 |
xylnatmClockingxCtrlSrcLevelThis 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.17.1.1.2 |
xylnatmClockingxSrcOperStateThis 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.ro Enumeration .1.3.6.1.4.1.800.2.9.1.17.1.1.3 |
xylnatmClockingxSrcTypeThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.17.1.1.4 |
xylnatmClockingxCtrlSlotThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.17.1.1.5 |
xylnatmClockingxCtrlPortThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.17.1.1.6 |
xylnatmClockingxGlobalCSTThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.17.2 |
xylnatmTrafficShaperConfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.18 |
xylnatmTrafficShaperConfTableA table of Traffic Shapers' configuration information.
Currently, traffic shaping function is available
on module types CSM-AB-OC3 and CSM-AB-DS3/E3 only. SEQUENCE OF XylnatmTrafficShaperConfEntry .1.3.6.1.4.1.800.2.9.1.18.1 |
xylnatmTrafficShaperConfEntryAn entry in the Traffic Shaper Configuration table
containing parameters of the traffic shapers of
cell switching module. XylnatmTrafficShaperConfEntry .1.3.6.1.4.1.800.2.9.1.18.1.1 |
xylnatmTrafficShaperConfSlotIndexThe slot on which the traffic shaping module
resides.ro INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.1 |
xylnatmTrafficShaperConfPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.2 |
xylnatmTrafficShaperConfTsNumIndexThis 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).ro INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.3 |
xylnatmTrafficShaperConfCDVThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.4 |
xylnatmTrafficShaperConfPCRThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.5 |
xylnatmTrafficShaperConfSCRThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.6 |
xylnatmTrafficShaperConfMBSThis 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.rw INTEGER .1.3.6.1.4.1.800.2.9.1.18.1.1.7 |
xylnatmTrafficShaperMemGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.2.9.1.19 |
xylnatmTrafficShaperMemTableA 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. SEQUENCE OF XylnatmTrafficShaperMemEntry .1.3.6.1.4.1.800.2.9.1.19.1 |
xylnatmTrafficShaperMemEntryAn entry in the Traffic Shaper Membership table
containing a VPI/VCI number mapping to a traffic shaper
number. XylnatmTrafficShaperMemEntry .1.3.6.1.4.1.800.2.9.1.19.1.1 |
xylnatmTrafficShaperMemSlotIndexThe slot on which the traffic shaping module
resides.ro INTEGER .1.3.6.1.4.1.800.2.9.1.19.1.1.1 |
xylnatmTrafficShaperMemPortIndexThe 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.19.1.1.2 |
xylnatmTrafficShaperMemTsNumIndexThis 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.ro INTEGER .1.3.6.1.4.1.800.2.9.1.19.1.1.3 |
xylnatmTrafficShaperMemVpiNumIndexThis 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].rw INTEGER .1.3.6.1.4.1.800.2.9.1.19.1.1.4 |
xylnatmTrafficShaperMemVciNumIndexThis 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].rw INTEGER .1.3.6.1.4.1.800.2.9.1.19.1.1.5 |
xylnatmTrafficShaperMemVpiOperThis 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.rw Enumeration .1.3.6.1.4.1.800.2.9.1.19.1.1.6 |