22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

network receive these labeled packets, they can make a forwarding decision based only on<br />

the label of the packet without regard to source, destination, or type of traffic contained<br />

within the packet.<br />

The core of MPLS is decoupled <strong>and</strong> consists of two primary areas:<br />

• Control plane: Leverages protocols to construct the Forwarding Table, whereas the<br />

forwarding plane forwards packets to the appropriate destination.<br />

• Forwarding table: Lists label values, which are each associated with determining the<br />

outgoing interface for every network prefix. Cisco NX-OS Software supports two<br />

signaling mechanisms to distribute labels: Label Distribution Protocol (LDP) <strong>and</strong><br />

Resource Reservation Protocol/Traffic Engineering (RSVP / TE).<br />

MPLS is comp<strong>os</strong>ed of the following major components:<br />

• MPLS Virtual Private Networks (Layer 3 VPN): Provides secure segmentation of<br />

different traffic types <strong>and</strong> classes, shared services, <strong>and</strong> route import/export between<br />

VPNs<br />

• MPLS Traffic Engineering (TE): Enables on-dem<strong>and</strong> b<strong>and</strong>width for applications,<br />

optimized link sharing <strong>and</strong> protection, fast convergence, <strong>and</strong> capacity planning<br />

• MPLS quality of service (QoS): Supports classification <strong>and</strong> prioritization of traffic<br />

flows, ability to preserve or remark traffic flows, <strong>and</strong> ability to police <strong>and</strong> to conform<br />

to service-level agreements (SLAs)<br />

Integration of MPLS application components, including Layer 3 VPNs, Traffic Engineering,<br />

QoS, <strong>and</strong> mVPN, enables the development of highly efficient, scalable, <strong>and</strong> secure networks<br />

that guarantee SLAs.<br />

MPLS Terminology<br />

Before underst<strong>and</strong>ing <strong>and</strong> learning MPLS configurations <strong>and</strong> operations, the MPLS<br />

terminology needs to be defined <strong>and</strong> understood:<br />

• Label: An MPLS label is a 4-byte header placed on a data packet, which contains<br />

basic information about how to forward the packet. The label contains a value, which<br />

identifies the packet, traffic class for QoS purp<strong>os</strong>es, <strong>and</strong> Time-To-Live (TTL). A<br />

packet can be marked with multiple labels, for example, an outer label, which contains<br />

forwarding information about the packet, <strong>and</strong> an inner label, which identifies a<br />

specific customer VPN that the packet is destined for. The label also contains a bit,<br />

which signifies whether it is the last or if subsequent labels are contained within the<br />

packet. Labels can also be aggregated so that many different packets may be assigned<br />

the same label; for example, packets going to the same destination network or<br />

belonging to the same VPN. These packets are part of the same forwarding<br />

equivalency class (FEC) <strong>and</strong> are treated the same throughout the MPLS network.<br />

• Label Distribution Protocol (LDP): Each device determines the unique label that it<br />

uses for a particular FEC. For end-to-end label switching to occur, the Label<br />

Switching Router (LSR) must disseminate its local label bindings to adjacent devices.<br />

LDP is the st<strong>and</strong>ard protocol used to propagate this information.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!