connPvcTable

The table containing information on current PVC/SVCs.
Currently, only PVCs are represented in this table.
The table is also used to establish and delete PVCs.
          
1. PVC establishment procedure
          
(1) Read connPvcIndexNext. This value is used as the
value of connPvcIndex for the new connection.
          
(2) Determine the value of connPvcHighIfIndex.  When
creating a new point-to-multipoint connection,
connPvcHighIfIndex must identify the first leaf.
When creating a new point-to-point connection,
connPvcHighIfIndex normally identifies the interface
with the higher value of ifIndex.
          
(3) Set connPvcRowStatus to 'createAndWait' using the
values of connPvcIndex and connPvcHighIfIndex as indexes.
This causes the switch to create the new row with some
objects being set to default values.  The parameters for
which there is no reasonable default are set to 0xffffffff.
          
    Object                Default
    connPvcTopology       bidirectionalVCC(2)
    connPvcTrafficType    trafficUBR(4)
    connPvcLowIfIndex     0xffffffff
    connPvcLowVPI         0xffffffff
    connPvcLowVCI         0xffffffff
    connPvcLowUpcParam    512
    connPvcLowUpc         pass(1)
    connPvcLowThroughput  0
    connPvcHighVPI        0xffffffff
    connPvcHighVCI        0xffffffff
    connPvcHighUpcParam   512
    connPvcHighUpc        pass(1)
    connPvcHighThroughput 0
          
The switch then sets the value of connPvcRowStatus to
'notReady'.  The default values can be read by the NMS.
          
(4) The values of the above objects which are set to
 0xffffffff must be modified, and the values of any other
 objects can be changed.  When establishing a VP connection,
 connPvcLowVCI and connPvcHighVCI should be set to 0.
When connPvcTrafficType is set to trafficUBR, the values
of connPvcLowThroughput and connPvcHighThroughput are
ignored. When all parameters have acceptable values, the
switch sets connPvcRowStatus to 'notInService'.
          
(5) When the NMS sets connPvcRowStatus to 'active', the
switch validates each parameter's value, and tries to 
establish the connection.  If this operation fails, the
the cause of the failure is indicated by the value of
connPvcCause.
          
At present, the switch allows connPvcRowStatus to have a
value of notReady or notInService for only one row at a
time.
          
2. Adding a new leaf to an existing pt-to-mpt connection
          
(1) Determine the value of connPvcIndex for the existing
point-to-multipoint connection to which a new leaf is
to be added.  
          
(2) Determine the value of connPvcHighIfIndex as the
ifIndex value of the interface to be used for the new leaf.
          
(3) Set connPvcRowStatus to 'createAndWait' using the
values of connPvcIndex and connPvcHighIfIndex as indexes.
This causes the switch to create the new leaf with some
objects being set to default values.  The parameters for
which there is no reasonable default are set to 0xffffffff.
          
     Object                Default
     connPvcHighVPI        0xffffffff
     connPvcHighVCI        0xffffffff
     connPvcHighUpcParam   512
     connPvcHighUpc        pass(1)
     connPvcHighThroughput 0
          
The switch then sets the value of connPvcRowStatus to
'notReady'.  The default values can be read by the NMS.
          
(4) The NMS must modify the values of connPvcHighVPI and
connPvcHighVCI, and can modify the values of connPvcHighUpc,
connPvcHighUpcParam and connPvcHighThroughput.  When
establishing a VP connection, connPvcHighVCI should
be set to 0.  The NMS should not change the values of
the following objects:
          
     connPvcTopology
     connPvcTrafficType
     connPvcLowIfIndex
     connPvcLowVPI
     connPvcLowVCI
     connPvcLowUpcParam
     connPvcLowUpc
     connPvcLowThroughput
          
 When all parameters have acceptable values, the switch
 sets connPvcRowStatus to 'notInService'.
          
 (5) When the NMS sets connPvcRowStatus to 'active', the
 switch validates each parameter's value, and tries to add
 the new leaf to the original connection.  If this operation
 fails, the cause of the failure is indicated by the value
 of connPvcCause.
          
3. PVC deletion  procedure
          
(1) Set the connPvcRowStatus to 'destroy'.
If the row exists but is impossible to delete, the cause
of the failure is indicated by the value of connPvcCause.
If the deletion is successful, the row is deleted 
(including the instance of connPvcCause for that row).
          
Notes:
 - a row representing a terminating VP will not have
instances of the following objects: connPvcLowUpc,
connPvcLowUpcParam, connPvcLowThroughput, connPvcHighUpc,
connPvcHighUpcParam, connPvcHighThroughput,
connPvcLowOutCells, connPvcHighInCells,
connPvcHighUpcViolatedCells, connPvcLowInCells,
connPvcHighOutCells, and connPvcLowUpcViolatedCells.
          
 - a row representing a connection between the
gateway-PAD (the switch's internal port) and a line
interface will not have instances of the following
objects: connPvcLowUpc, connPvcLowUpcParam,
connPvcLowThroughput, connPvcHighUpc, connPvcHighUpcParam,
connPvcHighThroughput, connPvcHighOutCells,
connPvcHighInCells, and connPvcHighUpcViolatedCells.

MIB

LS100-MIB

OID

.1.3.6.1.4.1.119.2.3.14.3.3.3

Type

table

Status

mandatory

Parent

conn

Siblings

2

Children

1