Home > Articles > Cisco Network Technology > IP Communications/VoIP > Voice, IP, and ATM MPLS Features

Voice, IP, and ATM MPLS Features

  • Sample Chapter is provided courtesy of Cisco Press.
  • Date: May 17, 2002.

Commands for Creating and Displaying PVCs on the RPM

This section describes the commands you use to create, configure, and display PVCs and connections on the RPM:

  • atm pvc—Creates an ATM PVC on an interface

  • show atm vc—Displays the status of one or all ATM VCs on the RPM

  • map-group—Assigns a map group to an interface

  • map list—Creates or accesses the configuration of a map list

  • ip—Assigns IP addresses to PVCs in a map list

  • show atm map—Lists ATM mapping information

  • addcon—Creates a connection between an RPM PVC and the PXM card

  • show switch connections—Lists summary or detailed information for the connections on the RPM

ATM PVC Command

The atm pvc interface-specific configuration command adds a new PVC to a subinterface on the RPM. Remember that point-to-point subinterfaces support only one PVC; multipoint subinterfaces support multiple PVCs. You must create a PVC on the subinterface before you can add the ATM connection.

Here is the atm pvc command syntax:

atm pvc <VCD> <VPI> <VCI> <AAL-encapsulation> [inarp]

The keyword and parameter options are as follows:

  • VCD—The virtual circuit descriptor is a unique number that identifies the PVC. Do not use VCD 1 or 2 because these are hard-coded for RPM management.

  • VPI—The VPI value on the ATM cells created from the IP packets on this PVC. A VPI of 0 indicates that this PVC is a virtual channel connection (VCC). A nonzero value indicates that this is a virtual path connection (VPC). VPCs are used for MPLS edge routing. Remember to restrict VPI values to the range defined by the resource partitions.

  • VCI—The VCI value on the ATM cells created from the IP packets on this PVC. Remember to restrict VCI values to the range defined by the resource partitions. Use VCI 0 for VPCs.

  • AAL-encapsulation—The encapsulation method used by the RPM. The encapsulation options are aal5snap, used for ATM or translated ATM-Frame Relay services; aal5nlpid, used for transparent ATM-Frame Relay services; and aal5ciscoppp, used for PPP applications—usually frame forwarding connections from the FRSM.

  • inarp—Enables inverse Address Resolution Protocol (ARP) updates on aal5snap PVCs.


Additional options apply to the atm pvc command. For details, refer to the Cisco IOS documentation.

Show ATM Virtual Circuit Command

The show atm vc command lists summary or detailed information about the virtual circuits (VCs) on the RPM. Use this command to learn which VCs are configured on the RPM and their status.

Here is the show atm vc command syntax:

show atm vc [VCD]

If you type show atm vc, a summary of all VCs is output. If you specify a VCD, detailed information on the specified VC is output. Example 22-21 shows the show atm vc output.

Example 22-21 show atm vc Output

rpm01#sho atm vc

      VCD /                Peak Avg/Min Burst
Interface  Name VPI  VCI Type  Encaps   SC  Kbps  Kbps  Cells Sts
1.1        11    0    11  PVC  SNAP     UBR 155000            UP
1.2        12    0    12  PVC  SNAP     UBR 149760            UP
1.66       66    0    66  PVC  SNAP     UBR 149760            UP
1.100      99    0    99  PVC  SNAP     UBR 149760            UP
1          1     0 65526  PVC  IPC      UBR 149760            UP
1          2     0 65528  PVC  IPC      UBR 149760            UP
1.101      101   6   400  PVC  SNAP     ABR   1200   500      UP
1.101      102   6   401  PVC  SNAP     ABR   1200   500      UP
1.101      400  10     0  PVC  CISCOPPP UBR 149760            UP

The show atm vc output provides the following information:

  • The interface or subinterface the VC is on
  • The VCD, VPI, and VCI assigned to the VC
  • The type of VC—PVC or tag
  • The encapsulation method
  • The service class
  • The configured Peak Cell Rate (PCR)
  • The average and minimum traffic rate
  • The burst size in cells
  • The VC status (UP or DOWN)

Example 22-22 shows the show atm vc output when a VCD is specified.

Example 22-22 show atm vc Output

rpm01#sho atm vc 102

Switch1.101: VCD: 102, VPI: 6, VCI: 401
ABR, PeakRate: 1200, Minimum Rate: 500, Initial Rate: 1200, Current Rate: 0
RIF: 16, RDF: 16
FRM cells received: 0, BRM cells received: 0
RM cells sent: 0
AAL5-LLC/SNAP, etype:0x0, Flags: 0x10820, VCmode: 0x0
OAM frequency: 0 second(s)
InARP frequency: 15 minute(s)
Transmit priority 3
InPkts: 0, OutPkts: 6, InBytes: 0, OutBytes: 168
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0,
CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
OAM cells sent: 0
Status: UP

Map Group Command

The map-group interface-specific configuration command identifies a map group for a subinterface. Each multipoint subinterface must refer to a map group name. The associated map list identifies the destination IP addresses for each PVC that terminates on the subinterface. Use the map-list global configuration command to define the map list. Remember that PVCs on a subinterface terminate on interfaces that share the same IP network or subnetwork address.

Here is the map-group command syntax:

map-group <group-name>

group-name is a character string naming the map group. For example, type map-group FRport5 to associate the subinterface with a map group named FRport5.

Map List Command

The map-list global configuration command is used to create a map list and to start map-list-specific configuration mode. When you use the map-list command, the CLI prompt changes from hostname(config)# to hostname(config-map-list)#.

Here is the map-list command syntax:

map-list <list-name>

list-name is the same as the group name specified for the subinterface using the map-group command. For example, type map-list FRport5 to create or access the map list named FRport5.

IP Command

The ip map-list-specific configuration command associates an IP address with a VCD.

Here is the ip command syntax:

ip <IP-address> atm-vc <VCD> [broadcast]

The parameter options are as follows:

  • IP-address—The IP address assigned to the VC. Remember when choosing an IP address that subinterfaces with PVCs between them must be on the same IP network. The IP address is entered in dotted-decimal format, such as

  • VCD—The VCD of the PVC.

Show ATM Map Command

The show atm map command lists the ATM mapping on the RPM. If you have map lists configured or are using ARP, you will have VCD-to-IP address mapping. Example 22-23 shows the show atm map output.

Example 22-23 show atm map Output

rpm01#show atm map

Map list port101 : PERMANENT
ip maps to VC 101
    , broadcast
ip maps to VC 102
    , broadcast

Add Connection Command

The addcon command adds an ATM connection on the RPM. This connection is similar to a connection on any other service module, such as the FRSM or AUSM. A number of optional parameters are supported for the addcon command. These optional parameters control ATM network routing and are not supported on PXM1 platforms.

Here is the addcon command syntax:

addcon vcc switch <slot-number>/<interface-number>.[subinterface-number]
  <VCI> [rname remote-name] rslot <remote-slot> <remote-interface>
  <remote-VPI> <remote-VCI> [master local]
addcon vpc switch <slot-number>/<interface-number>.[subinterface-number]
  <VPI> [rname remote-name] rslot <remote-slot> <remote-interface>
  <remote-VPI> [master local]

The keyword and parameter options are as follows:

  • VCI—The VCI value defined for the ATM PVC. This parameter applies only to VCCs and should match the VCI of the ATM PVC that is already added to the RPM.

  • VPI—The VPI value defined for the ATM PVC. This parameter applies only to VPCs and should match the VPI of the ATM PVC that is already added to the RPM.

  • remote-name—The node name of the destination MGX switch. For PXM1 MGX switches, all connections terminate on the local switch, so this parameter is not used.

  • remote-slot—The destination card slot number. 0 for the PXM1.

  • remote-interface—The remote interface (port) number.

  • remote-VPI—The remote VPI value on the destination card slot. If the destination service type is ATM, the VPI value can be any number that falls within the configured resource partitions on the destination card. If the destination card is an FRSM, the value is 0.

  • remote-VCI—The remote VCI value on the destination card slot. This parameter applies only to VCCs. If the destination card is an FRSM, this parameter is the DLCI at the remote end.

  • master local—These optional keywords identify the connection as a master connection. If you do not type master, the connection is a slave. Remember that all feeder connections to the PXM1 must be master connections. If this is a local connection, one end must be the master and the other end the slave. The slave end of the connection (whether on the RPM or a service module) must be added first. Only the master local keyword combination is used. Do not use the master remote keyword combination.

Show Switch Connections Command

The show switch connections command lists summary or detailed information about the connections on the ATM switch interface. Use this command to learn which connections are on the RPM and to learn how they are configured.

Here is the show switch connections command syntax:

show switch connections {vpc | vcc} [VPI] [VCI]

The keyword and parameter options are as follows:

  • vpc—Use this keyword to show a specific VPC.

  • vcc—Use this keyword to show a specific VCC.

  • VPI—The VPI of the VPC you want to show. Use this optional parameter with the vpc keyword.

  • VCI—The VCI of the VCC you want to show. Use this optional parameter with the vcc keyword.

Example 22-24 shows the show switch connections output.

Example 22-24 show switch connections Output

rpm01#show switch connections
lVpi  lVci remoteNodeName  remoteSlot remoteIf rVpi  rVci   Status
  0    11           0             1      10     243        inSynch
 10     0           0             1     200       0        inSynch

Example 22-25 shows the show switch connections output for a specified VCC.

Example 22-25 show switch connections Output

rpm01#show switch connections vcc 11

Local Sub-Interface   : 1
Local VPI             : 0
Local VCI             : 11
Remote Node Name      :
Remote Slot           : 0
Remote Interface      : 1
Remote VPI            : 10
Remote VCI            : 243
Routing Priority      : 0
Max Cost              : 255
Restricted Trunk Type : none
Percent Util          : 100
Remote PCR            : 353208
Remote MCR            : 353208
Remote Percent Util   : 100
Connection Master     : Local
Synch Status          : inSynch
Auto Synch            : OFF

28. Creating Connections on the RPM | Next Section Previous Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020