- VISM Overview
- MPLS Overview
- RPM Overview
- VISM Voice Features
- Voice Connections
- Voice Over AAL2 Network
- VoIP Network
- Voice Over ATM Services on the VISM
- Digital Signal Processors
- VISM Clocking
- Commands for Adding, Configuring, and Displaying Voice Connections
- Commands for Verifying Voice Connections
- Introduction to Multiprotocol Label Switching
- The Problem of Persistent Loops Due to Protocol Conflicts
- Cisco WAN Switches with MPLS Support
- Setting Up MPLS on the MGX Switch
- MPLS and Virtual Private Networks Using the Route Processor Module
- RPM Memory Locations
- RPM Port Numbering
- Cisco IOS Command-Line Interface
- Commands for Configuring the RPM
- Commands for Setting Up the RPM ATM Switch Interface
- How to Set Up the RPM
- Configuring Subinterfaces
- PVCs on the RPM
- Commands for Configuring Subinterfaces
- Commands for Creating and Displaying PVCs on the RPM
- Creating Connections on the RPM
- Summary
Creating Connections on the RPM
Follow these steps to create a connection on the RPM:
Step 1 |
Log into the RPM CLI. |
Step 2 |
Type show switch partitions to confirm that there is a PAR resource partition on the RPM. Note the VPI and VCI ranges. If the partition is not there, use the rpmrscprtn global configuration command to create one. This outputs a list of all resource partitions on the RPM. |
Step 3 |
Type enable. This prompts you for the enable password. |
Step 4 |
Type the password. You enter privileged EXEC mode. The command prompt changes from > to #. |
Step 5 |
Type configure terminal. This starts the configuration mode from the terminal. |
Step 6 |
Type interface switch <slot-number> /1.[subinterface-number] {point-to-point | multipoint}, where subinterface-number is either an existing interface or a new subinterface. This enters interface configuration mode and creates a new subinterface. |
Step 7 |
If you need to assign an IP address to the subinterface, type ip address <IP-address> <subnet-mask>. This assigns an IP address and subnet mask to the subinterface. |
Step 8 |
Type atm pvc <VCD> <VPI> <VCI> <AAL-encapsulation> [inarp], where the VPI and VCI values are within the specified range of the PAR partition. For a VCC, the VPI must be 0; for a VPC, the VCI must be 0. This creates an ATM PVC on the subinterface. |
Step 9 |
If you need to customize the PVC (for example, to set traffic shaping), refer to the IOS configuration guide for assistance. |
Step 10 |
If this is a point-to-point subinterface, type exit and go to Step 15. If this is a multipoint subinterface and a map group is not already defined, type map-group <group-name>. This associates a map group to the subinterface. |
Step 11 |
Type exit. You exit interface-specific configuration mode. |
Step 12 |
Type map-list <list-name>, where list-name is the same as the map group name from Step 10. This adds a slave (master remote) connection on the RPM subinterface. |
Step 13 |
Type ip <IP-address> atm-vc <VCD> [broadcast] for the VCD you created in Step 8. This associates an IP address to the ATM PVC. |
Step 14 |
Type exit. This ends map-list-specific configuration mode. |
Step 15 |
If you are adding a VCC, type addcon vcc switch <slot-number>/1.[subinterface-number] <VCI> [rslot <remote-slot> <remote-interface> <remote-VPI> <remote-VCI> [master local]. If you are adding a VPC, type addcon vpc switch <slot-number>/1.[subinterface-number] <VPI> rslot <remote-slot> <remote-interface> <remote-VPI> [master local]. This adds an ATM connection from the RPM PVC. |
Step 16 |
Press Ctrl-Z. If you want to save the changes, type copy running-config start-config. This exits configuration mode and saves the configuration to the startup configuration. |
Step 17 |
Type show switch connection {vcc | vpc} [VPI] [VCI]. This outputs the connection information. Verify the connection configuration. |
Step 18 |
If the remote end of the connection is an RPM, log into the remote RPM and follow Steps 1 through 17. If the remote end is an FRSM or AUSM, create a connection on the remote card module as required. This creates a logical port and a master connection on the AXSM. |
Step 19 |
If you are adding a local connection, you are finished. If you are adding a feeder connection, continue with Step 20. |
Step 20 |
If you have a BPX backbone network, log into the BPX switch attached to one of your MGX switches. Type addcon <local channel> <remote node> <remote channel> <connection class | connection type> [connection parameters] [route avoid] to add an ATM routing connection through the BPX network. Be sure to match the VPI and VCI values in the BPX network with the values you used when you added the MGX connection segments. Use the dspcons and dspcon commands to verify the connection status. |
Step 21 |
If you have an MGX 8850-PXM45 backbone network, log into the AXSM on the local switch and type addcon <interface number> <vpi> <vci> <service type> 2 [parameters], where 2 indicates the slave endpoint. Be sure to write down the endpoint ID (NSAP address, VPI, and VCI). Log into the AXSM on the remote switch and type addcon Step 21<interface number> <vpi> <vci> <service type> 1 <-slave slave endpoint ID> [parameters], where 1 indicates the master endpoint, and the slave endpoint ID is as previously noted. This adds a routing connection through the MGX 8850-PXM45 network. Use the dspcons and dspcon commands to verify the connection status. |
You have completed the steps necessary for creating a connection on the RPM.