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.

Cisco WAN Switches with MPLS Support

Figure 22-9 shows an example of an MPLS network.

Figure 22-9 MPLS Network Example

Based on the network routing protocol, a path (or route) is set up to all reachable IP networks. Simple label-switching tables identifying the labels and the destination interface are set up on all intermediate nodes. The nodes at the edge of the MPLS network attach the appropriate labels to the IP packets. The nodes in the network core simply switch the packets from one interface to the next based on the label. For example, if a packet with label 2A comes in on interface 01, it is switched to interface 06, and the label is changed to 15.

Label switching is similar to switching cells in an ATM network: Instead of a VPI and a VCI, there is a label. Because of this similarity, using an MPLS-enabled ATM network in the core is the ideal solution, especially in cases where ATM networks are already deployed.

An LSR is a core device that switches labeled packets according to predefined switching tables. An LSR can be a switch or a router. BPX 8650 switches (a BPX switch plus a 7200-series router) and MGX 8850-PXM45 switches (with RPM installed) are examples of LSRs.

An Edge LSR (ELSR) or Label Edge Router (LER) is an edge device that performs initial packet processing and classification and applies the first label. An ELSR can be either a router or a switch with built-in routing. The RPM installed in an MGX switch is an example of an ELSR.

A Label Switch Controller (LSC) is an MPLS router that controls the operation of an ATM switch in such a way that the two function together as a single ATM-LSR. An LSR comprises a switch and an LSC. A 7200 series router is an LSC for the BPX switch; an RPM is an LSC for the MGX 8850-PXM45 switch.

MPLS Features Supported on the MGX Switch

This section provides a high-level description of the MPLS features supported on the RPM installed in an MGX switch running Release 1.1.x firmware.

The RPM supports the following MPLS features:

  • The RPM as an ELSR or LER

  • Support for MPLS VPNs

  • Support for QoS

  • Support for MGX switches (with PXM1) interworking with MGX 8850-PXM45 switches via MPLS Virtual Switch Interface (VSI) virtual trunks

  • Support for MGX switches (with PXM1) interworking with BPX 8650 switches via MPLS VSI virtual trunks

The RPM as an Edge Label Switch Router

The RPM installed in an MGX switch is an ELSR or LER. As an ELSR, the RPM is responsible for initial packet processing and classification. It also applies the first label to the packets.

MPLS VPN Support on RPM

MPLS VPN support on RPM is described in greater detail in the upcoming section, "MPLS and Virtual Private Networks Using the Route Processor Module."

The VPN offers private connectivity over a public infrastructure. Each customer is assigned a VPN ID. You can think of the VPN ID as a prefix or extension of the IP address. For example, if a destination IP address is 10.10.15.2 and the VPN ID is 243, the packet destination is effectively 243.10.10.15.2, uniquely identifying the destination. Even if another customer is using the same IP address, the VPN ID is different, making the packet address different as well. In the MPLS network, the VPN identifier and the destination IP address are associated with a label.

The VPN is also isolated by the routing protocol (BGP) so that routing updates are exchanged only between members of the same VPN. The router at one customer's site does not even know about another customer's routers.

Figure 22-10 shows an example of VPNs in the MPLS network. Company A and Company B are connected to the same public network; however, they each have a VPN that behaves like a private network.

Figure 22-10 Example of VPNs in the MPLS Network

MPLS QoS Support on RPM

Customers have different types of traffic that they want to send to the service provider. MPLS allows the service provider to assign a different label to each traffic class. This label determines how traffic will be handled in the network.

The MPLS QoS solution does not map different traffic classes into different virtual circuits, as is done in ATM. MPLS simply applies a different label. These labels move the packet from end to end, maybe over a different path. Each switch along the way has a label that tells it the packet's CoS.

MGX PXM1 MPLS Interworking with MGX 8850-PXM45 and BPX Switches

This feature allows RPMs as ELSRs in PXM1-based platforms to interwork with the MGX 8850-PXM45 or BPX 8650 LSC function. The MPLS VSI virtual trunks feature enables the definition of one virtual path (VP) tunnel per ELSR on a PXM1-based platform to be mapped to one VSI virtual trunk under the control of the LSC on the attached backbone switch.

Figure 22-11 shows the MPLS interworking feature for MGX 8850-PXM45 switches.

Figure 22-11 The MPLS Interworking Feature

MPLS Networks Using the MGX Switch

This section describes how the MGX switch is placed in an MPLS network. It shows how the MGX switches with the BPX ATM MPLS core, the MGX 8850-PXM45 ATM MPLS core, and the IP MPLS core.

MGX Switches with the BPX ATM MPLS Core

This ATM MPLS architecture uses BPX 8650 ATM LSRs. The ELSR or LERs in this network are RPMs installed in MGX 8230/8250/8850-PXM1 switches.

The MGX switches are connected to the BPX switches by T3, E3, OC-3/STM1, or OC-12/STM4 ATM links.

Figure 22-12 shows an ATM MPLS core with MGX switches with RPMs as ELSRs.

Figure 22-12 ATM MPLS Core with MGX Switches

Cisco MGX 8230, 8250, and 8850-PXM1 switches do not yet support LSCs. This means that all MPLS traffic to RPMs must be carried inside a PVC or a PVP. PVCs are used with packet-based MPLS. If an MGX switch is used with ATM MPLS, the connections to the RPMs must be PVPs, which are used as MPLS VP tunnels.

Two options exist for the PVP connections, as shown in Figure 22-13. In the first option, at least two separate ATM lines are used between the MGX switch and the BPX switch. One line is the feeder trunk, which carries all but MPLS traffic, and the second line carries PVPs from the RPMs to the BPX switch. The second line is a UNI or NNI port on the MGX switch, with several VSI virtual trunk endpoints on the BPX switch.

Figure 22-13 PVP Connections

The second line is required because the BPX switch does not support virtual trunk endpoints on interfaces that are configured as feeder trunks. Another option involves using three or four lines with the PVPs distributed across them, increasing the available bandwidth. In this topology, additional lines are configured in the same fashion as the second UNI or NNI (nonfeeder trunk) link.

If two or three UNI or NNI lines are used to carry MPLS PVPs, these can be connected from one MGX switch to two or three different BPX nodes. Non-MPLS traffic from the MGX switch is still carried on the feeder trunk to a single BPX switch.

It is possible to carry all traffic (MPLS and non-MPLS) on the feeder trunk between the MGX and BPX switches. This option requires loopback cables on the BPX node and additional connections between the BPX feeder trunk and UNI or NNI ports.

MGX Switches with the MGX 8850-PXM45 ATM MPLS Core

Using an MGX 8850-PXM45 ATM MPLS core for MGX switches is similar to using a BPX core. The main difference is that the LSC for the MGX 8850-PXM45 switch is an RPM card module rather than an external router.

Figure 22-14 shows MGX 8850-PXM45 switches and MGX PXM1 switches in an ATM MPLS network.

Figure 22-14 Cisco Switches in an ATM MPLS Network

Like a BPX ATM MPLS core, you must set up a second line between the MGX PXM1 and the MGX 8850-PXM45 switches to carry the PVPs from the RPM ELSR.

MGX Switches with the IP MPLS Core

It is possible to set up the MGX switches without an ATM MPLS core. In this case, PVCs are required between RPMs in the network that need to pass traffic between them. The ATM backbone can be BPX, MGX 8850-PXM45, or other-vendor switches, but it is not an MPLS-enabled network. The ATM backbone network simply transports ATM cells from one RPM to another without any knowledge of MPLS.

Figure 22-15 shows an example of MGX switches and an IP MPLS core.

Figure 22-15 Cisco Switches in an IP MPLS Core

Refer to this Web site for more information on the benefits of MPLS: http://www.ciscopress.com/book.cfm?series=1&book=168.

16. Setting Up MPLS on the MGX Switch | 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.

Overview

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.

Surveys

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.

Newsletters

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.

Security

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

Children

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

Marketing

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.

Choice/Opt-out

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.

Links

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