Chapter 8 Permanent Virtual Connections (PVCs and PVPs)
104 Avaya M770 ATM Switch User’s Guide
Traffic descriptor does not have to be specified. If they are not, UBR traffic will be
assumed and an existing UBR traffic descriptor will be used. If no such traffic
descriptor exists, one will be automatically set up for UBR traffic. If any other type
of traffic is required, you must first set up the traffic descriptors in the usual way
(using the command td setup) on all required modules.
If one of the specified VCLs already exists, this VCL's traffic descriptors will be used
in preference to any other VCLs specified by the user. If both VCLs already exist,
their traffic descriptors must be compatible for the command to succeed.
To create a PMP PVC connection, use the pvc setup pmp command:
Freeing a PVC connection
To free a PVC connection and associated VCLs, use the pvc free command:
Command: M15-155s8:/>pvc setup pmp <vci1index> <vci2index>...<vciNindex>
<trunkId> [<fwd td>]
Example1: Setting up a PMP PVC between 2 ports on the same module:
M15-155s8:/> pvc setup pmp 2.15.0.801 2.15.0.802 2.200 3
Example2: Adding a branch to the same PMP call (same trunk ID) on a
different module:
On module 2: M15-155s2:/> pvc setup pmp 2.15.0.803 9.2.0.803
9.2.0.804 2.200 3
On module 9: M15-155s9:/> pvc setup pmp 2.15.0.803 9.2.0.803
9.2.0.804 2.200 3
Parameters: <vci1index> The first VCL for the PVC connection in the format
<slot.portnumber.vpi.vci>.
<vci2index>.
..
<vcNindex>
The branch VCLs (until the Nth branch) for the PMP PVC
connection in the format <slot.port.vpi.vci>
<trunkId> The identifier of the PMP call, but be the same on both the
root module and the branch module. The format is
<slot>.<index>. Must be in the range of trunk IDs are
determined by the module that holds the root.
<fwd td> Index of traffic descriptor for the forwarding direction (rx for
the root VCL, and tx for the branch VCLs).
Command: M15-155s8:/>pvc free {<vcl_index>|<all>}
Use: Either
M15-155s8:/>pvc free <vclindex>