Cisco MGX 8950 Specifications Page 198

  • Download
  • Add to my manuals
  • Print
  • Page
    / 642
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 197
3-70
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
Chapter 3 Provisioning PXM1E Communication Links
General PXM1E Configuration Procedures
Provisioning and Managing SPVCs and SPVPs
The following sections describe the following tasks:
Configuring Point-to-Point Connections
Configuring Point-to-Multipoint Connections
Adding Parties to a P2MP Root Connection
Obtaining the NSAP for a Party
Displaying a List of Connections
Displaying the Status of a Single Connection
Modifying P2P and P2MP Connections
Bringing Down a Connection
Bringing Up a Connection
Bringing Down a Party
Bringing Up a Party
Rerouting Connections
Rerouting a P2MP Party
Deleting Connections
Deleting a P2MP Party
Configuring Point-to-Point Connections
Point-to-point SPVCs and SPVPs are created between two ATM CPE and must be configured at each
endpoint. The master endpoint is responsible for routing and rerouting. The slave endpoint is responsible
for responding to requests from the master during connection setup and rerouting. Both endpoints are
configured on the switch to which the ATM CPE connects. These endpoints can be on the same switch
or on different switches.
The master and slave relationships exist for each SPVC or SPVP and apply only to that SPVC or SPVP
connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and
then create another with the Master on Node B and the slave on Node A. It is good practice to distribute
the master side of SPVCs and SPVPs among the network nodes so that route processing is distributed.
Cisco MGX switches support two types of SPVCs/SPVPs:
Single-ended SPVCs
Double-ended SPVCs
Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave
endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After
configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature
to work correctly, the destination endpoint must support single-ended SPVCs.
Single-ended SPVCs are non-persistent.
Double-ended SPVCs and SPVPs require separate configuration of the master and slave endpoints. The
slave endpoint must be configured first because this step generates a slave address that must be entered
during master endpoint configuration.
The following sections describe how to configure slave and master SPVC and SPVP connections.
Page view 197
1 ... 197 198 199 ... 642

Comments to this Manuals

No comments