Beta Draft Confidential
Configuring Management Paths
Using MSPVCs
ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 1/19/0511-11
Using MSPVCs in a PNNI Environment
When using a backbone of PNNI links, it is not possible to manage Lucent switches
using the traditional methods of inband management over Lucent direct or OPTimum
trunks. For this reason, you must use an alternate means of communicating between
the Lucent switches and the NMS and other types of management stations. Due to the
fact that MSPVCs are signaled connections that can be established over any PNNI link
(including those PNNI links to other vendor equipment), MSPVCs are ideal for
meeting the connectivity needs between the NMS and the Lucent switches.
When you use MSPVCs, the connection between the management logical port on the
SP/NP and the UNI/NNI logical port where the management station is located is a
standard SPVC. This means the VC can traverse any combination of Lucent CBX and
GX switches and other vendor equipment that is capable of supporting PNNI SPVCs.
Configuring MSPVCs
The following section describes how to define an SVC port address and configure the
MSPVC connection.
Before you configure an MSPVC:
1. Select the switch for which you want to configure the ATM UNI or NNI logical
port endpoint and define the physical port attributes. See the Switch Module
Configuration Guide
for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more
information.
2. Define an ATM UNI or NNI logical port. See “Working With ATM Logical Ports”
on page 3-2 for more information.
Defining SVC Port Addresses
If the device attached to a given physical port does not support ILMI address
registration, or to fully specify an address:
1. Define SVC port addresses for all logical ports on a given physical port (see
“Configuring SVC Port Addresses” on page 17-55).
2. Configure the PVP Termination, Connection ID, and VPI/VCI parameters (see
“Configuring PVP and PVC Termination” on page 17-65).
To Next Page
Loading...
