Beta Draft Confidential
Configuring ATM PVCs
Configuring PMP Circuits
ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 1/19/0510-77
Table 10-15. Add Point-to-Multipoint PVC Root: Administrative Tab
Fields
Field Action/Description
Root Name Enter an alphanumeric name for the circuit root.
Circuit Type Specify whether the circuit is a virtual path connection (VPC) or
virtual channel connection (VCC, the default). If you select VPC,
the VCI field is set to zero (0) and cannot be changed.
VPI (0-15) Enter a value from 0-15 to represent the VPI for the PVC. The
maximum value you can enter is based on the valid bits in VPI
that are configured for the logical port. See page 10-9 for
information about setting this value.
VCI (1-1023)
(For VCCs only)
Depending on the circuit configuration, enter a value from
1-1023 to represent the VCI for an ATM PVC. Although you can
configure VCIs in the 1 – 31 range (with the exception of
VCI=4), the ATM Forum reserves VCIs in this range for various
purposes. You should only use a VCI in the 1 – 31 range if you
are certain that compatibility issues will not arise with any
attached non-Lucent equipment. See page 10-9 for information
about setting this value.
CDV Tolerance
(1-65535)
(microsec)
Enter a value between 1 - 65535 µsec to define the CDVT. The
UPC uses this value to police the requested TD. The default is
600 µsec.
Note: If you are using the CBX 500 3-Port Channelized DS3/1
IMA IOM or the CBX 3500 3-Port Channelized DS3/1 Enhanced
IMA module, the recommended minimum CDV Tolerance value is
1000 µsec.
The recommended minimum for the 1-Port Channelized
STM-1/E1 IMA IOM or the CBX 3500 1-Port Channelized
STM-1/E1 Enhanced IMA module is 1200 µsecs.
Resource
Partitioning/
Network Overflow
Determines whether this PVC is restricted to trunks of its own
Layer2 VPN or can use public (shared) trunks during overflow
conditions. To configure this circuit for a specific Layer2 VPN
and customer, see page 13-9. For more information about Layer2
VPNs, see page 13-2.
Select one of the following options:
Public – (default) PVCs are routed over dedicated Layer2 VPN
trunks. However, in the event of failure, the customer’s traffic is
allowed to run over common trunks (shared by a variety of
different customers).
Restricted – PVCs can only use dedicated Layer2 VPN trunks. A
customer using this mode must purchase redundancy trunks to be
used in the event of outages or other trunk failures.