atmVpCrossConnectEntry

An entry in the ATM VP Cross Connect table.
This entry is used to model a bi-directional
ATM VP cross-connect which cross-connects
two VPLs.
            
Step-wise Procedures to set up a VP Cross-connect
            
Once the entries in the atmVplTable are created,
the following procedures are used
to cross-connect the VPLs together.
            
(1) The manager obtains a unique
   atmVpCrossConnectIndex by reading the
   atmVpCrossConnectIndexNext 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 atmVpCrossConnectIndex.
            
Negotiated VP Cross-Connect Establishment
            
(2a) The manager creates a row in this table by
   setting atmVpCrossConnectRowStatus to
   createAndWait(5).  The agent checks the
   requested topology and the mutual sanity of
   the ATM traffic parameters and
   service categories, i.e., the row creation
   fails if:
   - the requested topology is incompatible with
     associated values of atmVplCastType,
   - the requested topology is not supported
     by the agent,
   - the traffic/service category 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 atmVpCrossConnectIndex values in the
   corresponding atmVplTable rows are filled
   in by the agent at this point.
            
(2b) The manager promotes the row in the
   atmVpCrossConnectTable by setting
   atmVpCrossConnectRowStatus to active(1).  If
   this set is successful, the agent has reserved
   the resources specified by the ATM traffic
   parameter and Service category values
   for each direction of the VP cross-connect
   in an ATM switch or network.
            
(3) The manager sets the
   atmVpCrossConnectAdminStatus 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 atmVpCrossConnectRowStatus
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 atmVpCrossConnectIndex is released by:
            
(1) Setting atmVpCrossConnectRowStatus of all
            
   rows identified by this value of
   atmVpCrossConnectIndex to destroy(6).
   The agent may release all
   associated resources, and the
   atmVpCrossConnectIndex values in the
   corresponding atmVplTable 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
   atmVpCrossConnectEntries, the manager may
   set atmVplRowStatus to destroy(6) the
   associated VPLs.  The agent releases
   the resources and removes the associated
   rows in the atmVplTable.
            
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/service category parameter
values requires release of the VP cross-connect
before those parameter values may by changed
for individual VPLs.

MIB

ATM-MIB

OID

.1.3.6.1.2.1.37.1.9.1

Type

row

Status

current

Parent

atmVpCrossConnectTable

Table

atmVpCrossConnectTable

Children

11