53-1003031-02 09 December, 2013 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide Supporting Multi-Service IronWare R05.6.
Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron, TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Supported software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto-bandwidth for RSVP LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Configuring auto-bandwidth feature at the global level . . . . . .39 Configuring per-LSP adjustment interval . . . . . . . . . . . . . . . . . .39 Configurable table-based absolute adjustment-threshold . . .40 Configuring per-LSP range of bandwidth values . . . . . . . . . . . .43 Underflow-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FRR bypass LSPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Link protection for FRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Command Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Configuring an adaptive LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Static transit LSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Show Commands . . . . . . . . . .
Displaying the Traffic Engineering database. . . . . . . . . . . . . . . . . Displaying a traffic engineering path to a destination . . . . . Displaying signaled LSP status information. . . . . . . . . . . . . . Displaying path information . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the MPLS routing table . . . . . . . . . . . . . . . . . . . . . Displaying the MPLS forwarding information. . . . . . . . . . . . . Displaying the P2MP hardware forwarding information . . . .
Setting the LDP Hello Interval and Hold Timeout values . . . . . . . Setting the LDP Hello interval values . . . . . . . . . . . . . . . . . . . Setting the LDP hold time sent to adjacent LSRs . . . . . . . . . Determining the LDP Hold Time on an MPLS interface . . . . LDP message authentication . . . . . . . . . . . . . . . . . . . . . . . . . 345 346 347 348 349 Resetting LDP neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 MPLS LDP-IGP synchronization . . . . . . . . . . .
Displaying LDP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the LDP version . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying information about LDP-created LSPs . . . . . . . . . . Displaying LDP tunnel LSP information . . . . . . . . . . . . . . . . . Displaying the contents of the LDP database . . . . . . . . . . . . Displaying LDP session information . . . . . . . . . . . . . . . . . . . . Displaying LDP neighbor connection information . . . . . . . .
VPLS LSP load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitations and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . Existing feature affected by this feature . . . . . . . . . . . . . . . . Assumptions and dependencies. . . . . . . . . . . . . . . . . . . . . . . 470 470 470 470 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying the endpoint of a VPLS instance . . . . . . . . . . . . .
VPLS LDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the VPLS peer FSM state with LDP support. . . . . VC type mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTU mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No remote VC label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LDP session down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying MPLS VLL information . . . . . . . . . . . . . . . . . . . . . . . . . Displaying information about MPLS VLLs . . . . . . . . . . . . . . . Displaying detailed information about MPLS VLLs . . . . . . . . Displaying LDP information . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying VLL endpoint statistics . . . . . . . . . . . . . . . . . . . . . 547 547 548 552 554 Clearing Local VLL traffic statistics . . . . . . . . . . . . . . . . . . . . . . . .
BGP MPLS metric follow IGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BGP next-hop IGP cost. . . . . . . . . . . . . . . . . . . . . Displaying show command . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 596 596 596 597 IS-IS shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring BGP VPNs on a PE. . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a VRF routing instance . . . . . . . . . . . . . . . . . . . . . . . Assigning a Route Distinguisher to a VRF . . . . . . . . . . . . . . . Defining IPv4 or IPv6 address families of a VRF . . . . . . . . . . Defining automatic route filtering . . . . . . . . . . . . . . . . . . . . . . Assigning a VRF routing instance to an interface . . . . . . . . . Assigning a VRF routing instance to a LAG interface . . . . . .
Displaying BGP or MPLS VPNv4 information. . . . . . . . . . . . . . . . . Displaying VPNv4 route information. . . . . . . . . . . . . . . . . . . . Displaying VPNv4 route information for a specified IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying VPNv4 attribute entries information. . . . . . . . . . . Displaying VPNv4 dampened paths information . . . . . . . . . . Displaying VPNv4 filtered routes information . . . . . . . . . . . .
Displaying BGP or MPLS VRF information . . . . . . . . . . . . . . . . . . . Displaying VRF route information . . . . . . . . . . . . . . . . . . . . . . Displaying VRF route information for a specified IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying attribute entries information for a specified VRF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying dampened paths information for a specified VRF. . . . . . . . . . . . . . . . . . . . . . .
BGP or MPLS VPN sample configurations . . . . . . . . . . . . . . . . . . . Basic configuration example for IBGP on the PEs . . . . . . . . . EBGP for route exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static routes for route exchange. . . . . . . . . . . . . . . . . . . . . . . RIP for route exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSPF for route exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cooperative route filtering. . . . . . . . . . .
Displaying VPLS auto-discovery information . . . . . . . . . . . . . . . . . Displaying information about BGP L2VPN VPLS routes . . . . Displaying information about VPLS auto-discovery and load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying information about LDP . . . . . . . . . . . . . . . . . . . . . 775 775 789 791 VPLS LSP Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792 Glossary . . . . . . . . . . . . . . . . . . . . .
xvi Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
About This Document In this chapter • Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii • Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii • Related publications . .
In this chapter Supported hardware and software The following hardware platforms are supported by this release of this guide: TABLE 1 Supported devices Brocade NetIron XMR Series Brocade MLX Series NetIron CES 2000 and NetIron CER 2000 Series Brocade NetIron XMR 4000 Brocade MLX-4 Brocade NetIron CES 2024C Brocade NetIron XMR 8000 Brocade MLX-8 Brocade NetIron CES 2024F Brocade NetIron XMR 16000 Brocade MLX-16 Brocade NetIron CES 2048C Brocade NetIron XMR 32000 Brocade MLX-32 Brocade NetIr
In this chapter Document conventions This section describes text formatting conventions and important notice formats used in this document.
In this chapter Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations. These references are made for informational purposes only.
In this chapter Getting technical help or reporting errors To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the latest e-mail and telephone contact information.
In this chapter xx Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Chapter 1 Configuring MPLS Traffic Engineering Overview Table 2 displays the individual Brocade devices and the MPLS Traffic Engineering features they support.
1 Overview TABLE 2 2 Supported Brocade MPLS traffic engineering features Features supported Brocade NetIron XMR Series Brocade MLX Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package MPLS Yes Point-to-Multipoint Traffic Engineering Yes No Yes No No Yes Auto-bandwidth for RSVP LSPs Yes Yes N
1 Overview TABLE 2 Supported Brocade MPLS traffic engineering features Features supported Brocade NetIron XMR Series Brocade MLX Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package LSP accounting statistics for single-hop LSP routes Yes Yes No No No No No MPLS BFD Yes Yes No No No No No
1 IETF RFC and Internet draft support NOTE MPLS cannot be configured on the system globally when a NI-MLX-10Gx8-D card is installed. This chapter explains how to configure Multiprotocol Label Switching (MPLS) on the Brocade device for traffic engineering purposes. MPLS can be used to direct packets through a network over a pre-determined path of routers. Forwarding decisions in MPLS are based on the contents of a label applied to the packet.
How MPLS works 1 The following sections describe these basic MPLS concepts: • How packets are forwarded through an MPLS domain • The kinds of Label Switched Paths (LSPs) that can be configured on a device • The components of an MPLS label header How packets are forwarded through an MPLS domain An MPLS domain consists of a group of MPLS-enabled routers, called LSRs (Label Switching Routers).
1 How MPLS works 1. The Ingress LER receives a packet and pushes a label onto it. When a packet arrives on an MPLS-enabled interface, the device determines to which LSP (if any) the packet are assigned. Specifically, the device determines to which Forwarding Equivalence Class (FEC) the packet belongs. An FEC is simply a group of packets that are all forwarded in the same way. For example, a FEC could be defined as all packets from a given Virtual Leased Line. FECs are mapped to LSPs.
How MPLS works 1 In this example, a packet comes into interface 2/1 with label 123. The transit LSR then looks up this interface-label pair in its MPLS forwarding table. The inbound interface-label pair maps to an outbound-interface-label pair – in this example, interface 3/1 with label 456. The LSR swaps label 123 with label 456 and forwards the packet out interface 3/1. 3. The egress LER receives labelled packet, pops label, and forwards IP packet.
1 How MPLS works When an LSR receives an MPLS packet, it looks up the label in its MPLS forwarding table. Normally, this table maps the label and inbound interface to a new label and outbound interface. However, when this is the penultimate LSR in an LSP, the label and inbound interface map only to an outbound interface. The penultimate LSR pops the label and forwards the packet – now a regular IP packet – out the outbound interface.
Using MPLS in traffic engineering 1 The EXP field is designated for experimental usage. By default, a device uses the EXP field to define a Class of Service (CoS) value for prioritizing packets travelling through an LSP. Please refer to Chapter 1, “Configuring MPLS Traffic Engineering”, for more information. Note that software forwarded VPLS packets do not use the EXP encode table. S (Bottom of Stack) field (1 bit) An MPLS packet can be assigned multiple labels.
1 Using MPLS in traffic engineering FIGURE 5 How traffic-engineered LSPs are configured, established, and activated Traffic-engineered, signaled LSPs are configured, established, and activated by the following processes (but with some differences between OSPF and IS-IS): CSPF calculates a traffic-engineered path When the user configures a signaled Label Switched Path, the user specifies the address of the egress LER, as well as optional attributes, such as the LSPs priority and bandwidth requirements.
OSPF-TE Link State Advertisements for MPLS interfaces 1 CSPF is enabled by default for signaled LSPs, but can be disabled. When signaled LSPs are configured without CSPF, the shortest path from the ingress LER to the egress LER is calculated using standard hop-by-hop routing methods. When the LSP also is configured to use a user-specified path, the device calculates the shortest path between each LSR in the path.
1 IS-IS Link State Protocol data units with TE extensions for MPLS interfaces The following events trigger the device to send out OSPF-TE LSAs: • Change in the interface’s administrative group membership • Change in the interface’s maximum available bandwidth or maximum reservable bandwidth • Significant change in unreserved bandwidth per priority level: • If for any priority level, the difference between the previously advertised unreserved bandwidth and the current unreserved bandwidth exceeds five per
Traffic engineering database 1 • Change in the interface’s maximum available bandwidth or maximum reservable bandwidth. • Significant change in unreserved bandwidth per priority level, which can be either of the following: • For any priority level, the difference between the previously advertised, unreserved bandwidth and the current, unreserved bandwidth exceeds five percent of the maximum reservable bandwidth.
1 Traffic engineering database How CSPF calculates a traffic-engineered path Using information in the TED in addition to the attributes and requirements of the LSP, CSPF calculates a traffic-engineered path for the LSP by performing the tasks listed below. 1. When more than one LSP needs to be enabled, CSPF selects the LSP for path calculation based on the LSPs setup priority and bandwidth requirement.
Traffic engineering database 1 How RSVP establishes a signaled LSP The traffic-engineered path calculated by CSPF consists of a sequential list of physical interface addresses, corresponding to a path from the ingress LER to the egress LER. Using this traffic-engineered path, RSVP establishes the forwarding state and resource reservations on each LSR in the path. As with OSPF, special extensions for traffic engineering are defined for RSVP.
1 Traffic engineering database When the LSP passes admission control, the ingress LER sends a Path message to the address at the top of the ERO list. This is the address of a physical interface on the next LSR in the path. As the ingress LER did, this LSR performs admission control to make sure the outbound interface has enough reservable bandwidth to accommodate the LSP.
Traffic engineering database 1 This process repeats at each LSR until the Resv message reaches the ingress LER. NOTE To enable penultimate hop popping for the LSP, the LABEL object sent by the egress LER to the penultimate LSR contains a value of 3 (Implicit Null Label). This is an IETF-reserved label value that indicates to the penultimate LSR that it must pop the label of MPLS-encoded packets that belong to this LSP. 5.
1 Traffic engineering database When setting up an LSP, the device actually performs admission control twice: when the Path message is received and when the Resv message is received. when the LSP passes admission control after the Resv message is received, bandwidth allocation and LSP preemption take place. The sections that follow include examples of how admission control, bandwidth allocation, and preemption work.
Traffic engineering database Priority Unreserved Bandwidth 0 10,000 1 10,000 2 10,000 3 9,000 4 9,000 5 9,000 6 9,000 7 9,000 1 Active: LSP with setup 6, hold 3, mean-rate 1,000 Given the bandwidth allocation above, when an LSP is established with a setup priority of three and a mean-rate of 9,500 Kbps, it would not pass admission control because only 9,000 Kbps is available at priority 3.
1 Traffic engineering database 1. Admission control: On the interface, there is 10,000 Kbps available to priority two. The mean-rate for the new LSP is 10,000, so the LSP passes admission control; bandwidth can be allocated to it. 2. Bandwidth allocation: The hold priority for the new LSP is one. On the interface, 10,000 Kbps is available to priority one. This entire amount is allocated to the LSP. 3.
Traffic engineering database 1 After preemption, the reservable bandwidth array for the interface looks like this: Priority Unreserved Bandwidth 0 2,500 1 2,500 2 2,500 3 0 4 0 5 0 6 0 7 0 Active: LSP with setup 1, hold 0, mean-rate 7,500 LSP with setup 4, hold 3, mean-rate 2,500 Preempted: LSP with setup 3, hold 2, mean-rate 5,000 Calculating a path based on an interface address Under normal conditions, router IDs are used to configure hops within an MPLS path.
1 Traffic engineering database The global cspf-interface-constraint command directs the router to include the interface address as a constraint when it determines the shortest path. When invoked, this command ensures that a specified interface must be included in an LSP. This constraint can be turned on and off dynamically and does not affect established primary or secondary LSPs. CSPF interface constraint is significant for the ingress node only, where CSPF calculation takes place for an LSP.
MPLS Point-to-Multipoint Traffic Engineering 1 The cspf-interface-constraint command is described in “Configuring CSPF interface constraint”. MPLS Point-to-Multipoint Traffic Engineering The MPLS Point-to-Multipoint (P2MP) feature enables forwarding of information from a single source to multiple destinations along an optimized MPLS path. P2MP feature is ideal for transporting multicast data traffic, leveraging MPLS, and using optimal bandwidth utilization of the network’s links.
1 MPLS Point-to-Multipoint Traffic Engineering Figure 10 displays a P2MP LSP originating at PE1 and ending at the three destinations PE2, PE3, and PE4. As depicted in the topology diagram, the bandwidth utilization across the network is 1 Gbps. The P2MP network consists of the following key elements in the topology. • • • • PE1: The source or the root or the ingress label switch router (LSR). P1 and P2: The transit routers. PE2, PE3, and PE4: The destination or the leaves or the egress LSRs.
MPLS Point-to-Multipoint Traffic Engineering 1 Prerequisites and limitations • P2MP feature supports transit and branch functionality only. • FPGA-based second generation line cards support P2MP LSP feature. This feature is not supported by FPGA-based first generation line cards and 24x10g module line cards.
1 MPLS Point-to-Multipoint Traffic Engineering • Maximum number of branches per P2MP LSP — There is no limit on number of branches per P2MP LSP. However, considering the linear behavior as detailed in RFC 4461 about number of egress points and branch LSRs, the standard recommendation is 64 branches per P2MP. • Maximum number of LSPs and XCs — On the Brocade NetIron CER device, the maximum number of LSPs are 512 with 4000 S2Ls.
MPLS Point-to-Multipoint Traffic Engineering 1 Source-to-leaf sub-LSP The P2MP LSP topology as observed in Figure 10 consists of multiple point-to-point LSPs that originate from the source device and terminate at a destination device or a leaf. These LSPs are known as source-to-leaf (S2L) sub-LSPs. These S2L sub-LSPs can either be signaled in individual Path and Resv messages, or can be combined into a small number of messages.
1 MPLS Point-to-Multipoint Traffic Engineering Though S2L sub-LSPs are signaled in separate Path and Resv messages, they are always part of the same P2MP LSP. LSRs such as P2 in Figure 12, handle multiple incoming S2L sub-LSPs on the same interface, allocates a single label and advertises it to LSR P1. It avoids unnecessary duplication of traffic in the data plane. S2L sub-LSP groups S2L sub-LSPs can further be grouped into sub-groups using a node that is part of the P2MP LSP.
RSVP soft preemption 1 Pruning The process of removing egress LSRs from an existing P2MP LSP is known as pruning. It allows removal of egress nodes from a P2MP LSP at different points in time. Pruning can be achieved using any one of the following signaling methods: • Implicit S2L Sub-LSP Teardown — Sending a modified Path message that includes all S2L sub-LSPs except the one that is being pruned. • Explicit S2L Sub-LSP Teardown — Sending a Path Tear message for the corresponding Path message.
1 RSVP soft preemption Only adaptive and non-FRR LSPs could be enabled for soft preemption. LSPs which are adaptive and without FRR configuration have the facility to enable or disable the soft preemption feature without disabling the LSP. When the soft preemption configuration is changed, RSVP is notified for this change and a new Path message is triggered with the soft preemption desired flag bit (0x40) set in session attribute for signaling.
RSVP soft preemption 1 Configuring RSVP soft preemption Soft preemption capability on unprotected adaptive LSPs (which is disabled by default) can be configured irrespective of its state (enable or disable). Non-adaptive and/or FRR enabled LSPs cannot be configured with soft preemption capability. In this scenario, the LSP must be disabled first to configure soft preemption based on the policies, other changes also may be required, such as removing FRR.
1 RSVP soft preemption Syntax: [no] soft-preemption The [no] function disables soft preemption for the path on which the command is executed. Secondary path example Brocade(config-mpls-lsp-test-secpath-sec)# soft-preemption Soft-preemption cleanup-timer Use the soft-preemption cleanup-timer command is used to set the amount of time that the point of preemption must wait to receive the Path tear notification from the ingress LSR, before sending a hard preemption path error.
RSVP soft preemption 1 soft-preemption secondary p2 traffic-eng mean-rate 5555 adaptive soft-preemption enable Show mpls lsp extensive Use the show mpls lsp extensive command to view the policy and detailed history. Syntax: Show mpls lsp lsp name [detail | extensive] Brocade(config-mpls)# show mpls lsp name low ext LSP low, to 10.80.80.80 From: 10.40.40.
1 RSVP soft preemption 23 Nov 21 08:58:54 : LSP simple retry[2 times] . . . . . . . . . . . . Show mpls rsvp session extensive Use the show mpls rsvp session extensive command to view the policy and detailed history.
RSVP soft preemption 1 3 Dec 19 09:12:41 Route query response for PSB 0x2664b58c dest=16843008 return_code: 1 . . . . . . . . . . . . Show mpls rsvp session ppend Use the show mpls rsvp session ppend command to view an appended version of the session. NOTE Use the show mpls rsvp session extensive command to view the time left to hard preempt.
1 RSVP soft preemption Brocade(config-if-e1000-1/8)# show mpls int e1/7 Admin: Up Oper: Up MTU: 1500 bytes Maximum BW: 10000000 kbps, maximum reservable BW: 10000000 kbps Admin group: 0x00000000 Reservable BW [priority] kbps: [0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000 [4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000 Last sent reservable BW [priority] kbps: [0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000 [4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000 Soft Preemption under provisioned B
Auto-bandwidth for RSVP LSPs 1 Syslog messages The following notification Syslog messages are logged under the conditions indicated. No additional traps are generated. 1. When first path error requesting soft preemption is received for an LSP, following message is printed to Syslog. Dec 9 23:58:49 Brocade MPLS: LSP test soft preemption triggered. Preemption point 10.1.1.20 2. When MBB is successful for make before break setup of soft preemption requested LSP, following message is printed to Syslog.
1 Auto-bandwidth for RSVP LSPs TABLE 4 Basic auto-bandwidth functionality Configuration considerations • This feature must not be used when a strict bandwidth guarantee is to be provided. • This feature is only valid for adaptive LSPs. • When auto-bandwidth is enabled on an LSP and it is not in monitor-only mode and a failover to secondary LSP occurs, the secondary LSP is set up with the configured mean-rate, and the auto-bandwidth process restarts for the secondary LSP when it is adaptive.
Auto-bandwidth for RSVP LSPs 1 Configuring auto-bandwidth feature at the global level Auto-bandwidth is disabled by default. It is important that enabling auto-bandwidth globally is necessary to have the auto-bandwidth session running on the LSP. The auto-bandwidth parameters can be pre-configured on an LSP at the LSP level. To globally enable automatic bandwidth , use the following commands.
1 Auto-bandwidth for RSVP LSPs Configurable table-based absolute adjustment-threshold The current percentage-based threshold configuration method has certain shortcoming when there are LSPs with a very wide range of traffic-rates. Consider all the links from the ingress to be 1 Gbps links and the adjustment threshold to be 10%. Now, assume there are two LSPs A and B with bandwidth 10 Mbps and 10 kbps respectively.
Auto-bandwidth for RSVP LSPs 1 TABLE 5 Global -level auto-bandwidth commands Command Description Enabling auto-bandwidth globally The auto-bandwidth parameters can be pre-configured on an LSP at the LSP level. To globally enable automatic bandwidth, use the following commands.
1 Auto-bandwidth for RSVP LSPs TABLE 5 Clearing auto-bandwidth sample history The auto-bandwidth history is deleted only in the cases when LSP is itself deleted or when user clears or deletes the samples manually. Clearing of auto bandwidth samples by user is recorded in the LSP history. Manual auto-bandwidth adjustment To specify the bandwidth reallocation interval in seconds for a specific LSP, enter the following commands.
Auto-bandwidth for RSVP LSPs 1 Brocade(config-mpls)# autobw-template abw1 Brocade(config-mpls-autobw-template-abwl)# adjustment-interval 600 Brocade(config-mpls-autobw-template-abwl)# overflow-limit 5 Brocade(config-mpls-autobw-template-abwl)# mode monitor-and-signal To apply the template on a path, go into the auto-bandwidth mode and use the following command: Brocade(config-mpls-lsp-tl-autobw)# template abwl Overriding using direct configuration Template-based configuration is useful when a large numb
1 Auto-bandwidth for RSVP LSPs Brocade(config-mpls-lsp-xyz)# auto-bandwidth Brocade(config-mpls-lsp-xyz-auto-bandwidth)# min-bandwidth 600 Syntax: [no] min-bandwidth value The value parameter specifies that the LSP bandwidth can never be lower than this value. The range is from 0 through 2147483647 kbps. The default value is 0 kbps. The [no] option sets the corresponding parameter value to the default.
Auto-bandwidth for RSVP LSPs 1 Syntax: [no] overflow limit value The value parameter specifies the least number of times the sampled bandwidth must consecutively overflow the adjustment threshold to trigger premature adjustment. The range is from zero through 65535 (where zero means it never adjusts for limit overflow). The default value is zero. The [no] option sets the corresponding parameter value to the default.
1 Commands Clearing auto-bandwidth counters To clear statistics for auto-bandwidth-enabled LSPs, enter the following command. Brocade(config-mpls-lsp-xyz-auto-bandwidth)# clear mpls auto-bandwidth-statistics lsp xyz Syntax: clear mpls auto-bandwidth-statistics lsp lsp_name The lsp lsp_name parameter clears the statistics for the named LSP. Sample-history With the current implementation of the feature, only the previous sampled rate is display as part of the show mpls lsp detail command.
Commands • • • • • 1 show mpls autobw-threshold-table show mpls lsp [autobw-samples|name lsp_name autobw-sample] show mpls lsp detail/extensive sample-recording underflow-limit Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 47
1 show mpls lsp [autobw-samples|name lsp_name autobw-sample] show mpls lsp [autobw-samples|name lsp_name autobw-sample] The show mpls lsp name lsp_name autobw-sample command shows the sample history for all the auto-bandwidth LSPs. If a specific LSP name is given as parameter, only that LSPs sample history is displayed.
show mpls lsp detail/extensive 1 show mpls lsp detail/extensive The show mpls lsp detail command displays detailed information about a specific LSP. The underflow-limit parameter and the number of consecutive underflows are displayed. The adjustment-threshold is used from the global table is indicated with the value for current rate.The show mpls lsp extensive command shows the adjustment event with the previous rate and the maximum sampled rate.
1 show mpls lsp detail/extensive Field output mean rate The average rate of packets that can go through the LSP (in kbps), set with the traffic-eng mean-rate command. max burst The maximum size (in bytes) of the largest burst the LSP can send at the maximum rate, set with the traffic-eng max-burst command. mode Mode will tell is the LSP is in monitor-only or monitor-and-signal mode. adjustment threshold Displays the configured adjustment-threshold value.
show mpls lsp detail/extensive Field output 1 Description minimum bw The configured minimum bandwidth. maximum bw The configured maximum bandwidth. overflow limit Displays the configured overflow-limit value. underflow limit The number of sample which have to be below the threshold to trigger a premature adjustment. sample-record Whether the template is set to record the sample history. Constraint-based routing enabled Whether CSPF is in effect for the LSP.
1 show mpls lsp detail/extensive Times primary LSP goes up since enabled: 1 Metric: 0, Adaptive Maximum retries: NONE, no. of retries: 0 Pri. path: NONE, up: yes, active: yes Setup priority: 7, hold priority: 0 Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes Auto-bandwidth.
autobw-threshold table 1 autobw-threshold table This command changes the parser mode to config-autobw-threshold-table under which the user can change the absolute adjustment threshold values. The [no] function of the command clears all the entries in the adjustment-threshold table. Syntax Parameters Modes [no] autobw-threshold-table None. This command operates in MPLS configuration mode. History Release Command history Multi-Service NetIron Release 05.6.00 This command was introduced.
1 bandwidth-ceiling bandwidth-ceiling This command adds a new threshold change point to the autobw-threshold table. If the change point is already there, the value of the threshold is updated. The [no] function of the command remove the bandwidth ceiling entry from the table. Syntax Parameters [no] bandwidth-ceiling [bw in kbps|max] threshold threshold in kbps bw in kbps The bandwidth in kilobytes per second. 0 – 0x7FFFFFFF. Range of bandwidth in kbps.
bandwidth-ceiling max threshold 1 bandwidth-ceiling max threshold This command sets the threshold for any traffic-rate above the maximum bandwidth-ceiling configured in the table. The [no] function of the command removes the entry. Syntax Parameters [no] bandwidth-ceiling max threshold threshold in kbps max Any rate above the maximum ceiling configured. By default, the last ceiling is used. threshold in kbps Threshold in kilobytes per second. 0 – 0x7FFFFFFF. Range of bandwidth in kbps.
1 bandwidth-ceiling max threshold percentage bandwidth-ceiling max threshold percentage This command sets the threshold for any traffic-rate above the maximum bandwidth-ceiling configured in the table as a percentage. The [no] function of this command removes the entry. Syntax Parameters bandwidth-ceiling max threshold percentage threshold percentage max Any rate above the maximum ceiling configured. By default, the last ceiling is used. threshold percentage Threshold percentage per second. 0 - 100%.
adjustment-threshold 1 adjustment-threshold To specify the sensitivity of the automatic bandwidth adjustment of an LSP to changes in bandwidth utilization, use the adjustment-threshold command. This command is used to set the threshold for when to trigger automatic bandwidth adjustments. When automatic bandwidth adjustment is configured, bandwidth demand for the current interval is determined and compared to the LSPs current bandwidth allocation.
1 underflow-limit underflow-limit This command sets the underflow-limit to the input value. The [no] function of the command sets the underflow-limit back to the default value. Syntax Parameters [no] underflow-limit value underflow-limit The number of consecutive samples which have to be below the threshold to trigger a premature adjustment. value Default is 0, meaning there is no premature adjustment because of underflow.
sample-recording 1 sample-recording This command configures the template to record the sample history. The [no] function of the command disables the option. Syntax Command default Parameters [no] sample-recording [enable|disable] sample-recording disable enable Sets the sample recording for this LSP or autobw-template. disable Removes the setting for the sample recording for this LSP or autobw-template.
1 clear mpls auto-bandwidth-samples clear mpls auto-bandwidth-samples This command deletes the sample-history from the auto-bandwidth LSPs. Syntax Command default Parameters clear mpls auto-bandwidth-samples [lsp lsp_name] None. lsp The lsp option clears the auto-bandwidth sample history for the LSP specified through the lsp_name. Command modes This command operate in EXEC mode. History Release Command history Multi-Service NetIron Release 05.6.00 This command was introduced.
show mpls autobw-threshold-table 1 show mpls autobw-threshold-table This command displays the global-threshold table with the range of current-bandwidth and the corresponding absolute adjustment-threshold. Syntax Parameters Command modes Example show mpls autobw-threshold-table None. This command operates in all modes.
1 MPLS fast reroute using one-to-one backup As shown In Figure 13, MPLS Fast Reroute operates according to the steps in the following list in a situation where the path from the ingress router to router N becomes inoperable. 1. The router first tries to find a detour path from the ingress router to the N + 1 node that excludes the failed link that the protected path traverses out of the ingress route and Node N. 2.
MPLS Fast Reroute using facility backup over a bypass LSP 1 MPLS Fast Reroute using facility backup over a bypass LSP A bypass LSP is an MPLS LSP that serves as a tunnel to support facility backup of multiple, Fast Reroute LSPs, as specified in RFC 4090. Although the underlying mechanism of this feature is facility backup, the execution of facility backup is implemented through a user-defined bypass LSP, so this section focuses on bypass LSP.
1 MPLS Fast Reroute using facility backup over a bypass LSP Configuring a protected LSP To acquire the protection of one or more bypass LSPs along its route, an LSP that is requesting facility backup checks the interfaces that it traverses for the availability of a bypass LSPs that meet its requirements. (A Fast Reroute LSP that needs facility backup must request it. Refer to “Protecting MPLS LSPs through a bypass LSP” for the configuration steps.
MPLS Fast Reroute using facility backup over a bypass LSP 1 • The protected LSP The specification of a bypass LSP includes manual entry of a list of interfaces at the PLR that cannot make up the bypass LSPs own route. These excluded interfaces are the interfaces that the protected LSPs traverse. Therefore, from the standpoint of the bypass LSP, the protected interfaces on the PLR are called excluded interfaces.
1 MPLS Fast Reroute using facility backup over a bypass LSP FIGURE 15 Excluded interfaces on a PLR Bypass LSP, like one-to-one backup, fits within the scope of MPLS Traffic Engineering, so the configuration of bypass LSP includes elements of traffic engineering. For example, setting up a bypass LSP relies on RSVP and CSPF. In fact, CSPF is automatically enabled on a bypass LSP and, therefore, does not appear as a configurable option at the bypass LSP configuration level.
MPLS Fast Reroute using facility backup over a bypass LSP 1 Example Brocade(config-mpls)# bypass-lsp 123 Brocade(config-mpls-bypasslsp-123)# exclude-interface ethernet 1/1 ethernet 1/3 Brocade(config-mpls-bypasslsp-123)# exclude-interface ethernet 1/1 ethernet 1/3 to 1/4 Syntax: [no] exclude-interface ethernet|pos|ve slot/port [ethernet|pos|ve slot/port | to slot/port] Facility backup over an adaptive bypass LSP Adding the adaptive capability to a bypass LSP enables the following capabilities: • An ena
1 MPLS Fast Reroute using facility backup over a bypass LSP A new instance of the bypass LSP becomes active as soon as it is signaled. After the new instance becomes active, the old instance is released. To minimize the effect on user traffic, signaling of a new instance for the bypass LSP not does occur when the current instance is carrying traffic. In this regard, adaptive bypass LSPs behave differently from adaptive regular LSPs.
Adaptive Fast Reroute (FRR) and Global Revertiveness 1 Adaptive Fast Reroute (FRR) and Global Revertiveness Adaptive capabilities support to Fast Reroute (FRR) and enabling global revertiveness enables the following capabilities: • Once FRR is triggered, a make-before-break operation is performed to reestablish the primary path.
1 Adaptive Fast Reroute (FRR) and Global Revertiveness Configuring FRR on an LSP to be adaptive When an FRR is enabled, the user can change the following parameters without disabling the LSP: • bandwidth • exclude-any • facility-backup 70 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Adaptive Fast Reroute (FRR) and Global Revertiveness • • • • 1 hop-limit include-all include-any priority For instructions on how to configure an adaptive FRR LSP, refer to“Configuring MPLS Fast Reroute using one-to-one backup”. Global Revertiveness NOTE Local revertiveness is not supported in this release. When failover happens, traffic continues to flow in backup. When global revertiveness for FRR is configured, a new LSP is created from the ingress after the ingress learns about the failover.
1 Adaptive Fast Reroute (FRR) and Global Revertiveness Setting the revertive hold time Use the revertive hold-time command to specify the time the LSP holds before attempting a new path on the FRR LSP.
MPLS CSPF fate-sharing group 1 Brocade(config-mpls-policy)# retry-limit 20 Brocade(config-mpls-policy)# exit Brocade(config-mpls)# lsp t1 Brocade(config-mpls-lsp-t1)# adaptive Brocade(config-mpls-lsp-t1)# frr Brocade(config-mpls-lsp-t1-frr)# revertive mode global Brocade(config-mpls-lsp-t1-frr)# revertive holdtime 20 Brocade(config-mpls-lsp-t1-frr)# exit Brocade(config-mpls-lsp-t1)# commit Brocade(config-mpls-lsp-t1)# Displaying global revertiveness information Use the show mpls lsp name command to displ
1 MPLS CSPF fate-sharing group traversed. The path computation for a CSPF-enabled LSP uses the information from the TE database to compute the best path for an LSP satisfying all constraints (bandwidth reservations, network topology information, available resources), yet has the shortest distance to its destination. The CSPF computation for an LSP only uses the information from the TE database at the time of computation. Any future updates to the TE database do not cause the CSPF-enabled LSP to recompute.
MPLS CSPF fate-sharing group 1 primary LSP. For example, Q1, Q2, and Q3 is a collection of CSPF groups used by the primary LSP. TE link 1 is a member of CSPF groups Q1 and Q2. Q1 has a penalty of 10, and Q2 has a penalty 30. The total penalty of CSPF groups Q1 and Q2 is equal to 40. The total adjusted distance for TE link 1 is equal to the native IGP cost plus 40. The penalty is only applied once to each shared CSPF group that the TE link is associated with.
1 MPLS CSPF fate-sharing group 3. Set the penalty value for the CSPF fate-sharing group. Enter the following command. Brocade(config-mpls-cspf-group-group3)# penalty 100 Syntax: [no] penalty penalty-value The penalty penalty-value command specifies the penalty value that is assigned to objects of the same fate-sharing group. The range is from 1 through 65535. The default value is one (1). Objects of the same fate-sharing group share the same penalty value.
MPLS CSPF fate-sharing group 1 Deleting CSPF groups This feature is an enhancement to all Brocade devices running MPLS, enabling users to delete all the CSPF fate-share groups using a single command. Users are required to confirm execution with a warning message. Previous implementations required users to delete each group individually. The enhancement is backward compatible so the earlier command continues to be supported on all Brocade devices running MPLS.
1 MPLS CSPF fate-sharing group Brocade# show mpls config cspf-group test8 cspf-group test8 penalty 65535 node 10.7.7.3 node 10.7.7.8 Syntax: show mpls config cspf-group cspf-group name The cspf-group name variable specifies the name of the CSPF group for which the user wants to display information. Fate-sharing group membership for any given TE link or node consists of its own membership to the group, and the TE node to which it belongs.
MPLS CSPF fate-sharing group 1 Brocade# show mpls ted database detail This Router is 10.100.100.100 Global Link Gen 21 Area 0 NodeID: 10.20.20.20, Type: Router info from applied local policies: cspf-group member information (name/penalty): group1/100 Type: P2P, To: 10.1.1.1, Local: 10.1.1.2, Remote: 10.1.1.
1 MPLS CSPF fate-sharing group Brocade# show mpls lsp test2 LSP test2, to 10.100.100.100 From: 10.20.20.20, admin: UP, status: UP, tunnel interface(primary path): tnl3 Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Adaptive Maximum retries: NONE, no. of retries: 0 Pri.
MPLS CSPF fate-sharing group 1 Syntax: show mpls lsp name lsp_name The show mpls bypass-lsp name lsp_name command displays detailed information about a specific bypass LSP name. The output from the show mpls bypass-lsp name lsp_name command is enhanced to display CSPF fate-sharing group configuration for a bypass LSP path. In the following example, the add-penalty parameter is enabled under the CSPF group computation mode for the bypass LSP path as highlighted below.
1 MPLS CSPF fate-sharing group Brocade# show mpls bypass-lsp name test LSP test, to 10.100.100.100 From: 10.7.7.1, admin: UP, status: UP, tunnel interface(primary path): tnl3 Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Maximum retries: NONE, no. of retries: 0 Pri.
MPLS traffic engineering flooding reduction 1 MPLS traffic engineering flooding reduction Traffic engineering advertisements are triggered when a threshold value is reached or crossed. For all other bandwidth changes, a periodic flooding timer or Connection Admission Check (CAC) failure triggers the TE advertisements. When no thresholds are crossed, changes are flooded periodically unless periodic flooding was disabled.
1 MPLS traffic engineering flooding reduction Interface specific configuration The rsvp-flooding-threshold command can be executed multiple times for the same interface. The threshold values are added to the existing set of values for the interface. Previously configured values are not overwritten. The interface specific configuration overrides the global configuration. Using the no form of this command removes the sub-set of the configured threshold values.
MPLS over virtual Ethernet interfaces 1 Use the rsvp-periodic-flooding-timer command to set the interval for periodic flooding. The interval is set in seconds. To set the interval as 240 which triggers periodic flooding every four minutes, enter commands such as the following.
1 MPLS over virtual Ethernet interfaces NOTE Multi-port static ARP configuration in not supported for MPLS uplinks. Configuration considerations before enabling MPLS on a VE interface Before enabling MPLS on a VE interface, consider the configuration notes in this section. • The user must create a VE vid virtual interface id. The virtual interface id is a decimal number that represents an already configured VE interface.
MPLS over virtual Ethernet interfaces 1 • When MPLS is enabled on an interface, the last IP address of a VE cannot be removed. The command is rejected. The following error message is displayed. Brocade(config-vif-54)# no ip address 10.40.40.5/24 IP/Port: Error(31) Can not remove IP address as MPLS is configured on the port VPLS CPU protection NOTE VPLS CPU protection is not applicable to Brocade NetIron CES or Brocade NetIron CER devices.
1 MPLS over virtual Ethernet interfaces Reverse path forwarding When enabling MPLS on a VE interface with reverse path forwarding, consider the following. • The user cannot configure MPLS on a VE interface that has at least one member port enabled with RPF strict mode. The command is rejected, and the following error message is displayed.
MPLS over virtual Ethernet interfaces 1 Protocol-based VLANs When enabling MPLS on a VE interface associated with a protocol-based VLAN, consider the following. NOTE MPLS is supported only on VE interfaces that are configured on port-based VLANs. • The user cannot configure MPLS on a VE interface associated with a protocol based VLAN. The command is rejected, and the following error message is displayed.
1 Configuring MPLS Configuring MPLS This section explains how to set up MPLS on devices. It contains the following topics: • • • • • • • • “Enabling MPLS” “RSVP message authentication” “Configuring MPLS on a VE interface” “Setting up signaled LSPs” “Configuring signaled LSP parameters” “Configuring an adaptive LSP” “Configuring MPLS Fast Reroute using one-to-one backup” “Protecting MPLS LSPs through a bypass LSP” Enabling MPLS MPLS is disabled by default.
Configuring MPLS 1 Brocade(config-mpls)# mpls-interface e 3/1 Syntax: [no] mpls-interface all-ethernet | ethernet slot/port | pos slot/port |ve vid The all-ethernet option specifies all Layer-3 Ethernet interfaces. The ethernet option specifies the individual Ethernet interface described by the slot/port variable. The pos option specifies the individual POS interface described by the slot/port variable. The ve option specifies the individual virtual ethernet (VE) interface described by the vid variable.
1 Configuring MPLS Brocade(config-mpls)# policy Brocade(config-mpls-policy)# retry-time 45 Syntax: [no] retry-time seconds Setting the retry limit When the ingress LER fails to connect to the egress LER in a signaled LSP, the ingress LER tries indefinitely to make the connection unless the user sets a limit for these connection attempts. After this limit is exceeded, the ingress LER stops trying to connect to the egress LER over the primary path.
Configuring MPLS 1 The number has a range of 0 – 31. After the user associates an administrative group name with a number, the user can see it by name when assigning interfaces to the group or including or excluding the group from LSP calculations. Refer to “Adding interfaces to administrative groups” and “Including or excluding administrative groups from LSP calculations”.
1 Configuring MPLS Brocade(config)# router mpls Brocade(config-mpls)# policy Brocade(config-mpls-policy)# traffic-engineering isis level-1 Syntax: [no] traffic-engineering isis level-1 | level-2 The level-1 option enables LSPs with TE extensions for the IS-IS level-1 domain. The level-2 option enables LSPs with TE extensions for the IS-IS level-2 domain. By default, the device does not send out IS-IS LSPs with TE extensions for its MPLS-enabled interfaces.
Configuring MPLS 1 • filter-inter-as-routes • filter-intra-as-ibgp routes Inter-AS routes originate from other BGP autonomous systems. Intra-AS routes originate from within a BGP AS. Configuration considerations NOTE Brocade recommends that the user makes route filtering configuration decisions when booting the router for the first time. A system reload is not required when the user changes the filtering configuration.
1 Configuring MPLS Displaying MPLS policy parameters Use the show mpls policy command to display the current parameter settings configured under the MPLS policy mode. The following example shows the route filtering configuration in output from the show mpls policy command.
Configuring MPLS 1 • The Maximum Bandwidth TLV indicates the maximum outbound bandwidth that can be used on the interface. Maximum Bandwidth is the operating speed of the port. When calculated for a LAG, the Maximum Bandwidth is the operating speed of the primary port multiplied by the number of active ports in the LAG. Hence, this reflects the actual physical bandwidth of the interface. This TLV is not configurable by the user.
1 Configuring MPLS To configure the maximum reservable bandwidth as a percentage of the total interface bandwidth for MPLS LSPs on the interface, enter the following commands as displayed in the following example. Brocade(config-mpls)# mpls-interface ethernet 1/1 Brocade(config-mpls-if-e1000-1/1)# reservable-bandwidth percentage 80 Syntax: [no] reservable bandwidth [decimal | percentage decimal] The decimal variable specifies a value from 0 through 2,000,000,000 in kbits per second.
Configuring MPLS 1 outputs. For more information on the maximum reservable bandwidth configuration as displayed in the output of the show mpls config command, refer to “Displaying MPLS configuration information”. For more information on the maximum reservable bandwidth configuration as displayed in the output of the show mpls interface [ethernet slot/port] command, refer to “Displaying information about MPLS-enabled interfaces”.
1 Configuring MPLS At the MPLS router that pops the label (either the penultimate LSR or the egress LER), the incoming packet’s MPLS TTL value is copied to the packet’s IP TTL field, the IP TTL field is decremented by 1, and the checksum is recalculated. The result is that each LSR in the MPLS domain is counted as one hop. This is the default behavior. Optionally, the user can configure TTL propagation so that the entire MPLS domain appears as a two hops.
Configuring MPLS 1 • Ingress-tunnel accounting with exclude-ethernet-overhead: • The exclude-ethernet-overhead option, lets the user exclude the Ethernet header (14 bytes) and Ethernet overhead (20 bytes) and CRC overhead (4 bytes) when collecting the byte statistics. In other words, it counts only the size of MPLS packet. The exclude-ethernet-overhead option does not work with untagged ports carrying q-in-q packets for IP over MPLS, nor does it count multiple tags in a packet.
1 exclude-ethernet-overhead exclude-ethernet-overhead The exclude-ethernet-overhead option, lets the operator exclude the Ethernet header (14 bytes) and Ethernet overhead (20 bytes) and CRC overhead (four bytes) when collecting the byte statistics. In other words, it counts only the size of MPLS packet. The exclude-ethernet-overhead option does not work with untagged ports carrying q-in-q packets for IP over MPLS, nor does it count multiple tags in a packet.
LSP accounting statistics for single-hop LSP routes 1 Brocade(config)# system-max lsp-out-acl-cam 1000 Syntax: [no] system-max lsp-out-acl-cam number The number variable is the number of CAM entries available for LSP accounting. The default value is 0. The valid range of this value is 0 - 16384. NOTE When the LSP is a trunk port, the LSP accounting feature programs multiple label ACL CAM entries, once for each trunk port on all PPCRs.
1 LSP accounting statistics for single-hop LSP routes • In the case of a switchover from a primary LSP (multi-hop LSP) to a secondary LSP (single-hop LSP), the LSP accounting statistics on the secondary LSP are maintained only when the secondary LSP is a hot-standby. When the secondary LSP in a hot-standby mode is already UP, the LSP does not go down in a switchover, and the LSP accounting statistics from the primary LSP are accounted for on the secondary LSP.
LSP accounting statistics for single-hop LSP routes 1 Figure 20 depicts an MPLS domain for a multi-hop bypass LSP tunnel where the merge point is the egress LER. As with the single-hop bypass LSP scenario, the statistics for the individual LSPs riding over the multi-hop bypass LSP tunnel are accounted for. Individual LSP accounting statistics are collected on all LSP routes riding over a single-hop or multi-hop bypass LSP tunnel even when the merge point is the egress LER or not.
1 LSP accounting statistics for single-hop LSP routes Global RSVP parameters RSVP is automatically enabled when MPLS is enabled on the device. The user can optionally configure the following RSVP parameters globally at the Config-MPLS level: • Refresh interval • Refresh multiple The user can also optionally configure interface-specific RSVP behaviors (RSVP authentication, RSVP reliable messaging, and RSVP refresh reduction) at the interface level.
RSVP message authentication 1 The user can control how often the Path and Resv messages are sent by setting the refresh interval. By default, the refresh interval is 30 seconds. The user can set the refresh interval from zero through 2147483 seconds. use the following commands to set the refresh interval to 20 seconds.
1 RSVP reliable messaging Brocade(config)# router mpls Brocade(config-mpls)# mpls-interface ethernet 1/1 Brocade(config-mpls-if-e100-1/1)# rsvp-authentication key administrator Syntax: [no] rsvp-authentication key string The string variable specifies a text string of up to 64 characters that is encrypted and used for RSVP message authentication. By default, the authentication key is encrypted. When the user wants the authentication key to be in clear text, insert a 0 between key and string.
RSVP refresh reduction 1 Brocade(config-mpls-if-e1000-3/13)# rsvp-reliable-messaging The previous commands enable RSVP reliable messaging on interface 3/13 with all parameters set to their defaults (or to settings previously configured on this interface, if any).
1 RSVP refresh reduction RSVP bundle messages are disabled by default for all interfaces. To enable bundle messages on an interface, use commands such as the following. Brocade(config)# router mpls Brocade(config-mpls)# mpls-interface eth 3/13 Brocade(config-mpls-if-e1000-3/13)# rsvp-refresh-reduction bundle-message bundle-send-delay 20 The previous commands enable RSVP bundle messages on interface 3/13 with a bundle-send-delay of 20 milliseconds.
RSVP IGP synchronization 1 Enabling both RSVP refresh reduction extensions in a single step Bundle messages and summary refresh are disabled by default for all interfaces. The user can enable both extensions with default parameters on an interface by using commands such as the following.
1 RSVP IGP synchronization Limitations The RSVP IGP synchronization feature allows RSVP to react to an IGP neighbor down event. It does not allow RSVP to detect that a neighbor node has gone down. For example, when a pair of RSVP/IGP routers are connected with parallel links, detecting one neighbor down does not actually mean that the entire neighbor node has gone down. Globally enabling RSVP IGP synchronization This command globally enables the handling of an IGP neighbor down event by MPLS.
RSVP IGP synchronization 1 6. When an IGP neighbor goes down because of an underlying interface down, MPLS does not react to an IGP neighbor down event as RSVP would also receive the interface down event and tears down associated LSPs/sessions. Handling an IGP neighbor down event is redundant in such situations. 7. When BFD is configured on IGP interfaces, an IGP neighbor down is detected quickly and may help RSVP converge faster. 8. Bypass LSPs are treated exactly the same way as regular LSPs.
1 RSVP IGP synchronization for Remote Links red, group number: 6 green, group number: 8 RSVP IGP synchronization for Remote Links The RSVP IGP Sync- Phase II feature enables an LSP ingress router to react to neighbor down events from any location in the network. Any non-FRR or Bypass LSP can be rerouted when the router receives an IGP link or neighbor down event. MPLS will build an IGP Sync database which is independent of the MPLS TE database.
RSVP IGP synchronization for Remote Links 1 RSVP-OSPF Sync: Disabled RSVP-ISIS Sync: Enabled Show mpls rsvp igp-sync link Brocade# show mpls rsvp igp-sync link Link Address Remote Router LSP Count 12.1.1.1 11.11.11.11 1 12.1.1.2 11.11.11.11 4 12.2.2.2 11.11.11.11 3 14.1.1.4 11.11.11.11 2 23.1.1.3 22.22.22.22 2 24.1.1.4 22.22.22.22 4 34.1.1.4 33.33.33.33 2 Show mpls rsvp igp-sync link detail Brocade# show mpls rsvp igp-sync link detail Link Address: 12.1.1.1 Neighbor router Id: 22.22.22.
1 RSVP IGP synchronization for Remote Links LSP paths using this IGP link: 3 LSP List: lsp04-29:sec_path_1_to_4_2, lsp04-28:path_1_to_4_strict, lsp04-28:sec_path_1_to_4_2 Show mpls rsvp igp-sync lsp Brocade# show mpls rsvp igp-sync lsp LSP Name Path Name CSPF dbyp-12.1.1.
RSVP IGP synchronization for Remote Links 1 RSVP IGP Sync Links: 11.11.11.11->12.1.1.2, 22.22.22.22->23.1.1.3 33.33.33.33->34.1.1.4 RRO hops: 4 hops 12.1.1.1, 12.1.1.2, 23.1.1.3, 34.1.1.4 CSPF hops: 3 hops 12.1.1.2, 23.1.1.3, 34.1.1.4, LSP: lsp04-11, Path: CSPF: enabled, Record Route: enabled, Frr: disabled CSPF hops: 1, Record route hops: 1 RSVP IGP Sync Links: 11.11.11.11->14.1.1.4, RRO hops: 1 hops 14.1.1.4, CSPF hops: 1 hops 14.1.1.
1 RSVP IGP synchronization for Remote Links CSPF hops: 2 hops 12.1.1.2, 24.1.1.4, LSP: lsp04-63, Path: path_1_to_4_6 CSPF: enabled, Record Route: enabled, Frr: disabled CSPF hops: 2, Record route hops: 2 RSVP IGP Sync Links: 11.11.11.11->12.2.2.2, 22.22.22.22->24.1.1.4 RRO hops: 2 hops 12.2.2.2, 24.1.1.4, CSPF hops: 2 hops 12.2.2.2, 24.1.1.4, LSP: lsp04-71, Path: path_1_to_4_strict CSPF: enabled, Record Route: disabled, Frr: disabled CSPF hops: 3, Record route hops: 0 RSVP IGP Sync Links: 11.11.11.11->12.
RSVP IGP synchronization for Remote Links 1 LDP tunneling enabled: no Soft preemption enabled: no Sec. path: path_1_to_4_5, active: no Hot-standby: yes, status: down, adaptive Setup priority: 7, hold priority: 0 Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes Constraint-based routing enabled: yes hop limit: 0 Soft preemption enabled: no Sec.
1 RSVP IGP synchronization for Remote Links 24 Jul 12 11:25:41 : Secondary path path_1_to_4_5. RRO received: -> 13.1.1.3 -> 34.1.1.4 25 Jul 12 11:25:41 : Secondary path path_1_to_4_5 setup successful . Instance id 1 26 Jul 12 11:27:03 : IGP link 34.1.1.4 to neighbor 33.33.33.33 along Primary path path_1_to_4_6 is down. 27 Jul 12 11:27:03 : IGP link 34.1.1.4 to neighbor 33.33.33.33 along Secondary path path_1_to_4_5 is down. 28 Jul 12 11:27:03 : Secondary path path_1_to_4_5 torn down. Instance id 1.
RSVP IGP synchronization for Remote Links • • • • • • • • 1 admin-group - “Adding an MPLS VE interface to an administrative group” ldp-enable - “Configuring LDP on an MPLS VE interface” ldp-params - “Setting the LDP hello interval on an MPLS VE interface (link Only)” hello-interval - “Setting the LDP hello interval on an MPLS VE interface (link Only)” hello-timeout - “Setting the LDP hello holdtime on an MPLS VE interface (link only)” reservable-bandwidth - “Bandwidth computation for an MPLS VE interface
1 RSVP IGP synchronization for Remote Links Setting the LDP hello interval on an MPLS VE interface (link Only) NOTE For more information on setting the LDP hello interval on physical interfaces, refer to “Setting the LDP hello interval on an MPLS VE interface (link Only)”. The user can set the LDP Hello Interval on an MPLS enabled VE interface. This option is only available for Link LDP sessions. The following example configures LDP hello-interval to 30 seconds for MPLS interface ve 100.
RSVP message authentication on an MPLS VE interface 1 two ports, and each port is one gig. To calculate the bandwidth of the trunk, the user takes the sum of all active ports on a physical port. In this example, the bandwidth of the trunk is equal to two gigs. To calculate the bandwidth of the VE interface, take the minimum of all active port members. In this example, the bandwidth of the VE interface is one gig.
1 Setting up signaled LSPs Configuring RSVP message authentication on an MPLS VE interface NOTE For more information on configuring RSVP message authentication on physical interfaces, refer to “Configuring RSVP message authentication”. RSVP Message Authentication is disabled by default. This authentication method uses MD5 for an MPLS VE interface. The following example configures RSVP message authentication for MPLS interface ve 100.
Setting up signaled LSPs 1 • Specifying which packets are to be forwarded along the LSP (optional) Setting up paths A path is a list of router hops that specifies a route across an MPLS domain. Once the user creates a path, the user can create signaled LSPs that see the path. Paths are configured separately from LSPs so that a path may be specified once and then used by several LSPs that see the path by name. An LSP may specify a primary and one or more redundant paths.
1 Setting up signaled LSPs Modifying a path Once the user has created a path, the user can insert or delete nodes from it. For example, to delete a node from the sf_to_sj path defined above. Brocade(config-mpls)# path sf_to_sj Brocade(config-mpls-path)# delete loose 10.1.1.1 Brocade(config-mpls-path)# exit Syntax: [no] delete strict | loose ip address To insert a node into a path. Brocade(config-mpls)# path sf_to_sj Brocade(config-mpls-path)# insert strict 10.150.1.1 before 10.150.1.
Setting up signaled LSPs • • • • • • • • • • • • • • 1 Setting aliases for the egress LER (optional) Setting a Class of Service (CoS) value for the LSP (optional) Allocating bandwidth to the LSP (optional) Configuring the setup and hold priority for the LSP (optional) Setting a metric for the LSP (optional) Including or excluding administrative groups from LSP calculations (optional) Limiting the number of hops the LSP can traverse (optional) Specifying a tie-breaker for selecting CSPF equal-cost paths (
1 Setting up signaled LSPs To allow changes to be automatically applied, the user can use the implicit-commit command under the MPLS policy command to enable certain types of events to trigger implicit commit. When there are any changes to the configuration of the LSP, the make-before-break operation is not triggered.
Setting up signaled LSPs 1 address -- to manually set the router ID, then the tunnel destination address must be included in the router address TLV in the type 10 LSA originated by the egress LER. This is accomplished by setting the egress LERs traffic engineering policy to OSPF with the traffic-engineering ospf command (see “Enabling OSPF-TE LSAs for MPLS interfaces”).
1 Setting up signaled LSPs Syntax: [no] primary-path path name Configuring redundant paths for an LSP NOTE This section describes the behavior of redundant paths. However, the user can exercise further control over the path selection process by specifying the path selection mode and preferred path using the select-path command. This process is described in detail in “Configuring path selection”. A signaled LSP has a primary path, which is either user-defined or computed by the ingress LER.
Setting up signaled LSPs 1 Syntax: [no] secondary-path path name Issuing the secondary-path command enters the secondary path configuration level. From this level, the user can specify that this path is to operate in hot standby mode. Example Brocade(config-mpls-lsp-sec-path)# standby Syntax: [no] standby Once the LSP is enabled, both the primary and hot-standby paths are activated, although packets are directed over only the primary path.
1 Setting up signaled LSPs • unconditional select mode – In this mode, traffic is switched to and stays on the selected path regardless of the path’s condition even when it is in a failure state. The main difference between manual and unconditional select mode is the test of the working condition of the user selected path.
Setting up signaled LSPs 1 NOTE When the user configures a primary path to be the selected path, a message is generated that states that it is already the default system behavior because the primary path is the default preferred path. In this instance, no configuration information is saved in the configuration file. Configuring a Path Selection Revert Timer The Path Selection Revert Timer feature provides an option to stabilize a path before traffic is switched to it.
1 Setting up signaled LSPs The timer-value value specifies an amount of time in seconds that the router waits after the primary or selected path comes back up before reverting to it. Setting a Class of Service value for the LSP The 3-bit EXP field in the MPLS header can be used to define a Class of Service (CoS) value for packets travelling through the LSP. The user can manually set a CoS value for the LSP.
Setting up signaled LSPs 1 Configuring a priority for a signaled LSP The user can specify a priority for each signaled LSP for which this is the ingress LER. The priority determines the relative importance of the LSP during setup or preemption. The priority for an LSP has two components the setup priority and the hold priority. When multiple LSPs are enabled at the same time, such as when the device is booted, LSPs that have a higher setup priority are enabled before LSPs that have a lower setup priority.
1 Setting up signaled LSPs Syntax: [no] include-any groups The value specified for groups can be one or more valid administrative group names or numbers. In this example, the device includes any of the interfaces that are members of groups “gold” or “silver” when calculating the path for this LSP. Only those interfaces in the “gold” or “silver” groups are considered for the LSP.
Setting up signaled LSPs 1 For example, the following commands cause CSPF to select the path with the highest available bandwidth when choosing among equal-cost paths calculated for LSP tunnel1. Brocade(config-mpls)# lsp tunnel1 Brocade(config-mpls-lsp)# tie-breaking least-fill Syntax: [no] tie-breaking least-fill | most-fill | random The least-fill parameter causes CSPF to choose the path with the highest available bandwidth (that is, the path with the least utilized links).
1 Setting up signaled LSPs Configuration considerations The user can change the tunnel metric configuration at any time. The new value applies only to tunnels that are brought up after the change. Metrics for existing tunnels do not change. Configuring an LDP tunnel metric To set all LDP tunnels to metric 2 (for example), enter the following command under the MPLS LDP configuration.
FRR bypass LSPs 1 Enabling a signaled LSP After the user sets the parameters for the signaled LSP, the user can enable it. Enabling the LSP causes the path to be set up and resources reserved on the LSRs in the LSPs primary path. Enabling the LSP is the final step in configuring it. To enable LSP tunnel1. Brocade(config-mpls)# lsp tunnel1 Brocade(config-mpls-lsp)# enable Syntax: [no] enable Disabling an LSP Disabling an LSP de-activates it, but does not remove the LSP from the device’s configuration.
1 FRR bypass LSPs Resetting LSPs The clear mpls lsp command allows the user to reset an RSVP LSP session. Changes in the routing table after an LSP path is established do not take effect unless the LSP is brought down and then brought up again. After the user resets the LSP, it realigns to the new routing topology. The clear mpls lsp command can be used on the ingress LSR of the LSP. Resetting normal LSPs The clear mpls lsp command allows the user to reset normal LSPs.
FRR bypass LSPs 1 • Resetting the primary path of an LSP causes the secondary LSP path to become active, when a hot-standby secondary path for the LSP is available. However, when the primary path comes up after the reset operation, the active path switches over from the secondary to the primary again. When the “revert-timer” is configured, the LSP path switchover may be dampened and obeys the usual revert-timer rule. There is no change in the revert-timer behavior due to the reset LSP feature.
1 Link protection for FRR Link protection for FRR A Label Switched Path (LSP) set up across an MPLS network is used to switch traffic across MPLS network. The path used by a LSP across the network is based upon network resources or any other traffic engineering constraints provided by the user. Based on TE-constraints, the ingress MPLS router computes the path to be taken by LSP and signals it using RSVP protocol. By nature, nodes and links in a MPLS networks are prone to failure.
Link protection for FRR 1 Node Protection: In this protection, backup is selected in such a way that it avoids the failed link along with router to which this link connects to. The node which was responsible for link failure, is avoided altogether in its entirety, which was used earlier by the LSP. Traffic merges back to main stream from backup on somewhere downstream from the node, which is being avoided. Refer to Figure 22 illustrating node protection provided at R1 to LSP ingressing from R1 to R4.
1 Command Section Configuring protection type preference for Adaptive LSPs Because adaptive LSPs TE-property can be changed without restarting LSP and changed values takes effect through the make-before-break process, you are allowed to change the protection type preference (Node protection to Link protection or vice versa) at any point of time during life cycle of an adaptive LSPs, irrespective of its administrative or operational state.
link-protection 1 link-protection This command requests for link protection for FRR enabled LSP. The default configuration is always node protection. The [no] function of the command sets protection type back to default behavior, which is node protection. Syntax Command default Parameters Command modes [no] link-protection The [no] function of the command sets protection type back to default behavior, which is node protection. None.
1 show mpls lsp [name lsp_name][detail|extensive] show mpls lsp [name lsp_name][detail|extensive] The show mpls lsp lsp_name command displays detailed information about a specific LSP name. The command output now contains additional information indication link protection or node protection. Syntax Parameters show mpls lsp [name lsp_name][detail|extensive] name The name option displays information specified by the lsp_name variable. detail The detail option displays detailed information.
show mpls lsp [name lsp_name][detail|extensive] Output field Displays if the primary path is currently UP. active: Displays if the primary path is currently active. hold priority: Fast Reroute: Backup LSP: Examples Description up: Setup priority: 1 The configured setup priority for the LSP. The configured hold priority for the LSP. The method of Fast Reroute configured for this LSP. Currently only one-to-one backup is available. Displays if the backup LSP is UP or DOWN.
1 show mpls config [lsp] /show running-config /show configuration show mpls config [lsp] /show running-config /show configuration The show mpls config command and show running-config command display specific MPLS interface configuration information. The output of this command now contains additional information indicating that the link protection is configured. Syntax show mpls config show running-config show configuration Parameters Command modes Usage guidelines Example None.
Configuring an adaptive LSP 1 Configuring an adaptive LSP The Multi-Service IronWare software supports Adaptive LSPs. Using this feature, the user can change the following parameters of an LSP while it is in the enabled state: • • • • • • • • • cspf exclude-any hop-limit include-all include-any primary-path priority tie-breaking traffic-eng When one of these parameters is changed on a Adaptive LSP, a new instance of the same LSP is signaled using the newly defined parameters.
1 Configuring an adaptive LSP OTHER INSTANCE PRIMARY: NEW_INSTANCE admin: DOWN, status: DOWN Maximum retries: 0, no. of retries: 0 Setup priority: 7, hold priority: 1 Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes Constraint-based routing enabled: yes Tie breaking: random, hop limit: 0 Active Path attributes: Tunnel interface: tnl1, outbound interface: e1/2 Tunnel index: 4, Tunnel instance: 1 outbound label: 3 Path calculated using constraint-based routing: yes Explicit path hop count: 1 10.2.1.
Static transit LSP 1 The all option directs the router to reoptimize the paths for all LSPs configured. The lsp option directs the router to reoptimize the path for the LSP specified by the . NOTE On reoptimization of an adaptive LSP, LSP accounting statistics might miss the accounting of some of the packets. Time-triggered reoptimizing The user can set a timer to optimize a specific LSP path on a periodic basis.
1 Static transit LSP 1. Perform label range splitting (optional). 2. Configure static transit LSP. Label range splitting (optional) NOTE This procedure requires a reload. Use the following configuration procedure to split the label-ranges. 1. Configure the static range with the start and end of the range using the label-range static min-value min max-value max command. The dynamic range will start from the next label-value after the end of the static range. 2. Save the configuration and reload.
Static transit LSP 1 Functional Considerations The following configuration behaviors must be considered before the configuration. Changes in label range configuration 1. Configuration of in-label values outside of the label range will not be allowed. 2. If the label range is increased and reloaded, you will get a wider label range to use. Refer to “Label range splitting (optional)”.
1 Static transit LSP In-label Use the in-label command to specify the label that will be received in the packets and used to identify the static transit LSP in the router. That in turn decides who the next hop will be (based on the “next-hop” configuration). No in-interface is configured as we use the global label-space. It would be an error to configure the same in-label for multiple LSPs, or specify a value outside the static range.
Static transit LSP 1 Enable The enable command is used to enable the LSP configuration to bring up the LSP to allow forwarding to use the labels. It checks whether the configuration is valid - the in-label and the next-hop are configured - and then tries to bring up the LSP. Bring-up of the LSP can fail due to many reasons such as the out-interface not UP or the next-hop not valid.
1 Static transit LSP Show Commands The following show commands are available to display static-LSP information. Show mpls static-lsp The show mpls static-lsp command displays the static-LSPs in the system in brief. Brocade# show mpls static-lsp Number of transit lsps: 2 Name c2 c3 TABLE 7 Admin UP UP Oper In-label Out-label Next-hop Out-Intf DOWN 21 1024 160.168.123.122 e2/1 UP 22 3 160.168.111.
Static transit LSP 1 Next-hop interface address to reach configured next-hop: -History 0 Jul 11 01:38:32 : LSP tunnel is Enabled Syntax: show mpls static-lsp detail| name name | [up | down] [extensive] [up | down] [detail | extensive] [name name] extensive [wide] TABLE 8 show mpls static-lsp extensive field definitions Field Definition Role The role of the LSP. Currently, only transit. Enabled Whether the LSP is enabled or not.
1 Static transit LSP TABLE 9 show mpls label-range field definitions Field Definition Dynamic Represents the dynamic label range for transit labels. Modified label range This header displays the values that have been configured, but not yet effective as label range changes require a reload. This section is visible only if a different set of values have been configured to take effect after reload.
Static transit LSP VLL peers Peers operational Local VLLs: VLLs configured VLLs operational CSPF-GROUP: Total configured Tunnels: Total supported Total allocated = = 0 0 = = 0 0 = 0 1 = 16000 = 2 Cross-connects: Total supported Total allocated = 64000 = 1 Auto-bandwidth templates: Total supported Total configured = = 100 0 Number of times MPLS has been enabled: 1 TABLE 10 Field definitions Field Definition Transit-LSPs configured Number of static LSP transits configured Transit-LSPs en
1 Static transit LSP router mpls policy traffic-engineering isis level-1 mpls-interface ethernet 2/14 lsp c2 to 14.14.14.14 traffic mean-rate 10 enable static-lsp transit t1 in-label 100 out-label 101 next-hop 10.1.1.2 enable Syntax: show mpls config Show run The show run command display includes the static-LSPs configuration in the MPLS section of the configuration. Brocade# show run router mpls policy traffic-engineering isis level-1 mpls-interface ethernet 2/14 lsp c2 to 14.14.14.
Configuring MPLS Fast Reroute using one-to-one backup 1 Configuring MPLS Fast Reroute using one-to-one backup To configure MPLS Fast Reroute by using the one-to-one backup method for a defined LSP named frr_tunnel, use the ffr command as in the following example. Brocade(config)# router mpls Brocade(config-mpls)# lsp frr_tunnel Brocade(config-mpls-lsp-frr_tunnel)# to 10.1.1.
1 Configuring MPLS Fast Reroute using one-to-one backup Brocade(config-mpls-lsp-frr_tunnel)# frr Brocade(config-mpls-lsp-frr_tunnel-frr)# hop-limit 20 Syntax: [no] hop-limit number The number of hops can be from 0 – 255. Configuring priority for a MPLS Fast Reroute The user can specify setup and hold priorities for the detour routes within a specified LSP. These priorities are available to any LSP and function exactly the same on standard LSPs as they do on detour LSPs.
Configuring MPLS Fast Reroute using one-to-one backup 1 Brocade(config-mpls-lsp-frr_tunnel)# frr Brocade(config-mpls-lsp-frr_tunnel-frr)# exclude-any gold silver Syntax: [no] exclude-any groups In this example, the device excludes any of the interfaces that are members of groups “gold” or “silver” when calculating detour routes for this LSP. Only interfaces that are not part of either group can be considered for the detour routes.
1 Configuring MPLS Fast Reroute using one-to-one backup A subsequent iteration of the show command in the bypass LSP context shows that this LSP is a candidate for protection by a bypass LSP. The display for protected LSP xmr3-199 shows that, under frr, the facility-backup line shows this protection is requested. Brocade(config-mpls-bypasslsp-123)# show mpls config lsp xmr3-199 lsp xmr3-199 to 10.33.33.
Configuring a bypass LSP to be adaptive 1 The name must be unique among all regular LSPs and bypass LSPs. Syntax: [no] exclude-interface linkid, linkid, linkid-begin-linkid-end Syntax: [no] exclude-any group Configuring a bypass LSP to be adaptive The user can configure a bypass LSP to be adaptive using the adaptive command.
1 Configuring a bypass LSP to be adaptive The lsp-name variable specifies the LSP to be optimized. This LSP can be a regular LSP or a bypass LSP. Time-triggered reoptimizing a bypass LSP As with regular LSPs, the user can set a timer to optimize a specific bypass LSP path on a periodic basis. By default, the timer is disabled. Upon expiration of this timer, the bypass LSP is optimized for a new path when the new path has a lower cost than the existing path.
Dynamic Bypass LSPs 1 To change the value of one of these parameters, enter the command by the same name in the bypass LSP context, and then enter the commit command. The following example changes the limit on the number of hops a bypass LSP can traverse.
1 Dynamic Bypass LSPs There are two ways to establish a bypass LSP: 1. Static: The user manually configures in a MPLS enabled network so the protected LSPs uses the bypass LSP for link or node protection. 2. Dynamic: Computes and establishes a bypass LSP at runtime when there is a requirement to provide a FRR link or node protection to a facility protected LSP at its PLR points. Dynamic bypass LSPs are these bypass LSPs.
Dynamic Bypass LSPs 1 When establishing a facility protected LSP with link or node protection, each LSR on the primary path verifies when there are any existing bypass LSPs that require protection constraints. When finding a bypass, it updates its bandwidth, depending on the requesting backup path bandwidth. The protected LSP backup path uses this bypass to reach its merge point. When there is no bypass available, the LSR computes and establishes a new bypass LSP, addressing the backup path constraints.
1 Dynamic Bypass LSPs A link which is protected by the bypass LSP is called a protected-link, protected interface, or an excluded interface. Multiple facility protected LSPs use a common downstream link which becomes a protected link for all of them. This signifies that there is at least one dynamic bypass LSP to the NHOP (node connected by the interface) and many NNHOP dynamic bypass LSPs based on the path taken by the facility protected LSP.
Dynamic Bypass LSPs 1 • Now the first dynamic bypass has nine megabits per second and the second dynamic bypass has one megabyte per second occupied and there are 10 backup paths. Look at this at a bandwidth use optimization point of view; all 10 backups are accommodated in only one dynamic bypass LSP. Having an algorithm which realigns the backups so there is only one dynamic bypass, instead of two bypasses is not supported in this release.
1 Dynamic Bypass LSPs Dynamic bypass LSP creation must meet the following criteria: • There are no existing static bypass or dynamic bypass LSPs to satisfy the facility protected LSP backup path request. • Dynamic bypass is allowed to be created under current configuration for the protected interface. • Dynamic bypass creation does not exceed the configured or default system limits under current state. • There is a path available to setup the dynamic bypass LSP to fulfill backup request constraints.
Dynamic Bypass LSPs 1 Configuration steps Any modifications to the dynamic bypass interface or the router mode configuration parameters are applied to the new creation of dynamic bypass LSPs. Dynamic bypass parameter changes made at the interface level only apply to the existing dynamic bypass LSPs protecting this interface, when triggered by events such as timer or user intervention.
1 Dynamic Bypass LSPs Globally enabling dynamic bypass Using the dynamic-bypass command in MPLS router configuration mode for the first time enables the dynamic bypass feature in the system. When using the dynamic-bypass command in the MPLS router configuration mode which is already configured, there is no change in the existing status (enabled or disabled) of global dynamic bypass. To enable the dynamic bypass on MPLS router mode, enter a commands such as the following.
Dynamic Bypass LSPs 1 Use the [no] form of the command inside global dynamic-bypass configuration mode to disable dynamic bypass on all existing MPLS interfaces. Setting the maximum number of dynamic bypass LSPs The maximum number of dynamic bypass LSP is configurable in global mode. This is the limit for the total number of dynamic bypass LSPs that can be created on a router. This number must be less than, or equal to, the global maximum number of bypass LSPs that can be configured on a router.
1 Dynamic Bypass LSPs Setting the reoptimizer-timer When the re-optimization value is set to a non-zero value and the timer sets the amount of seconds, the reoptimizer-timer command enables the dynamic bypass LSP re-optimization. The re-optimization timer value is configurable on all MPLS interface modes. The global set value is applicable to all dynamic bypass LSPs for which corresponding interface level re-optimization timer value is not set.
Dynamic Bypass LSPs 1 dynamic bypasses per MP that can be created per MP is as per the corresponding global configuration. When the max-bypasses-per-mp limit is changed to a value which is less than the current active number of dynamic bypasses per mp, then the limit changes to the new value and used for the next new creations. Existing dynamic bypasses exceeding this number are not deleted.
1 Dynamic Bypass LSPs Enabling the record route option An interface level record route parameter can be configured for a dynamic bypass LSP corresponding to a protected link. Use the record command to enable or disable the dynamic bypass LSP record route options. Based on the value of this parameter, dynamic bypass LSPs are created with their record route option enabled or disabled.
Dynamic Bypass LSPs 1 Setting the reoptimize timer Use the reoptimize-timer command to configure a reoptimization timer value for all the dynamic bypass LSPs that are being created corresponding to a protected interface. When configured, this value overrides the global mode configured value. Reoptimization can be disabled corresponding to an interface by setting it to value zero. When a dynamic bypass is non adaptive, the reoptimization timer is not be considered for the dynamic bypass LSP.
1 Dynamic Bypass LSPs Number of active riding ingress backup lsps: 0 Number of inactive riding ingress backup lsps: 1 Syntax: show mpls bypass-lsp static [brief |detail |extensive|interface ethernet lsp_name] • The show mpls bypass-lsp command is modified to include filtering based of static bypass types, dynamic bypass types and protected interface. • The show mpls summary (brief) command output is modified to have an entry for total number of bypass LSPs in the system.
Dynamic Bypass LSPs 1 Name prefix: dbyp, primary path: none Max bypass per merge point: 111, total bypasses: 0 Total number of merge points 0 Dynamic bypass interface: e3/3, Active status: Enabled Admin type: Local, admin status: UP Hop limit: 255, Tie-breaking: random, cos: 0 Setup priority: 7, hold priority: 0 Max rate: 1000 kbps, mean rate: 1000 kbps, max burst: 1000000 bytes From: 10.11.11.
1 Dynamic Bypass LSPs VLLs: VLLs configured VLL peers Peers operational = = = 2 2 2 VLLs configured VLLs operational = = 0 0 Local VLLs: Syntax: show mpls summary Displaying dynamic bypass information Use the show mpls config to display all dynamic bypass global and interface configurations. Global or interface dynamic bypass default configurations do not display in show config except for ‘enable’.
Dynamic Bypass LSPs 1 Sample configurations Global dynamic bypass configuration example Brocade(config-mpls)# dynamic-bypass Brocade(config-mpls-dynamic-bypass)# Brocade(config-mpls-dynamic-bypass)# Brocade(config-mpls-dynamic-bypass)# Brocade(config-mpls-dynamic-bypass)# Brocade(config-mpls-dynamic-bypass)# Brocade(config-mpls-dynamic-bypass)# enable enable-all-interfaces max-bypasses 150 max-bypasses-per-mp 8 reoptimize-timer 300 disable Dynamic bypass interface configuration example Brocade(config-mp
1 Dynamic Bypass LSPs Scenario B: Dynamic bypass creation to NHOP When the path computation to NNHOP node fails, a path is calculated by considering NHOP as the destination. When the path computation is successful, the dynamic bypass is signaled. This creates a link protection dynamic bypass LSP as shown in Figure 28 below.
Dynamic Bypass LSPs 1 Scenario C: Dynamic bypass creation to NNNHOP When a path computation to NHOP node fails, a path is calculated by considering NNNHOP as the destination. When a path computation is successful, the dynamic bypass is signaled.
1 Dynamic Bypass LSPs Scenario D: Dynamic bypass creation from all PLRs Dynamic bypass LSP creation on a fully connected network is as below. When there is path available, All PLRs, except penultimate node, creates dynamic bypass LSPs with node protection.
Dynamic Bypass LSPs 1 Scenario E: Dynamic bypass creation from all PLRs Dynamic bypass LSP creation on a fully connected network is as below. When there is a path available, all PLRs, except penultimate node, creates dynamic bypass LSPs with node protection. This is illustrated in Figure 31 below.
1 Dynamic Bypass LSPs Scenario F: Dynamic bypass creation with link protection at PLRs When there is no path for NNHOP node protection and there is path for NHOP, link protection dynamic bypass LSP is created as shown in Figure 32, Figure 33, and Figure 34 below. 188 FIGURE 32 Dynamic bypass creation with link protection PLRs.a FIGURE 33 Dynamic bypass creation with link protection PLRs.
Dynamic Bypass LSPs FIGURE 34 1 Dynamic bypass creation with link protection PLRs.
1 RSVP LSP with FRR RSVP LSP with FRR RSVP LSP with FRR (fast reroute) protection can use two different protection methods. This documentation will use the terms of detour backup and facility backup going forward for differentiation. Detour backup establishes backup path with detour sessions from PLR (point of local repair) to MP (merge point) while Facility backup uses bypass LSP as tunnel to establish backup path from PLR to MP.
Liberal bypass selection and liberal dynamic bypass 1 A: When the node protection desired flag is present, PLR goes through the merge point in the order of next-next-hop (if present, to achieve node protection), next-hop (link protection), hops after next-next-hop in sequence of traverse, if any are present. B: When Node protection desired flag is not set, it simply selects the downstream next hops in sequence of traverse (example: next-hop, next-next-hop and so on).
1 Liberal bypass selection and liberal dynamic bypass At present by default, Dynamic Bypass path computation excludes the nodes between MP and Egress. Now when Liberal Bypass is enabled, Dynamic Bypass creation path computation can compute Dynamic Bypass path including nodes between Merge Point and Egress of protected session.
Liberal bypass selection and liberal dynamic bypass FIGURE 36 1 Bypass LSP selection: traversing the downstream node Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 193
1 Liberal bypass selection and liberal dynamic bypass The following cases are NOT supported: FIGURE 37 194 Cannot traverse any link between PLR and MP Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Liberal bypass selection and liberal dynamic bypass FIGURE 38 1 Cannot traverse any node between PLR and MP Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 195
1 Liberal bypass selection and liberal dynamic bypass The following diagram illustrates the difference between node protection and link protection with merge point other than next hop: FIGURE 39 True node protection Protected LSP Head PLR Node A Node B Link 1 X MP Protected LSP Tail Node C Node D Node G Node E Facility Protected LSP Protected LSP used Links protected interface.
Liberal bypass selection and liberal dynamic bypass FIGURE 40 1 Potential link protection with traversing link or node between PLR and MP Backward compatibility This is a software only feature and does not require special support from hardware. There are no backward compatibility issues as this feature is local to RSVP module regarding if the bypass LSP can serve as backup protection. With the new mode turned on, there can be additional bypass LSPs qualifying for the backup path.
1 Commands Upgrade and downgrade considerations The CLI changes are longer seen on a downgrade and the feature can lead to backup sessions not established due to more restricted qualification criteria in older releases. Commands The following commands support this feature.
use-bypass-liberal 1 use-bypass-liberal The use-bypass-liberal command enables and disables backup query algorithm using minimum restrictions to qualify bypass LSP. The use-bypass-liberal command can be executed without restart and bypass LSP selection process uses the restricted or liberal mode, depending upon the current configuration. Changing the computation mode on the fly does not impact the already selected bypass LSPs. The [no] form of the command returns to the default status.
1 show mpls config show mpls config The configuration which enables liberal mode displays as part of the command. By default, this option is disabled and not shown. This is different from the command of cspf-computation-mode use-bypass-metric, which shows disabled when not enabled. Syntax Parameters show mpls config [use-bypass-liberal] use-bypass-liberal Use liberal mode for CSPF facility backup computation.
show mpls policy 1 show mpls policy The configuration which enables liberal mode displays as part of the following command. Note that by default, this option is disabled and not shown. This is different from the command of cspf-computation-mode use-bypass-metric, which shows disabled when not enabled. Syntax show mpls policy Parameter None. Command modes The command operates under the MPLS policy sub-configuration mode (config-mpls-policy).
1 show mpls policy History Release Command history Multi-Service NetIron Release 05.6.00 The show mpls policy command output was enhanced to include use bypass liberal under the CSPF computation-mode command output line. Related commands 202 None.
show mpls lsp 1 show mpls lsp The show mpls lsp command, detailed or extensive variant outputs, now has a modified Fast Reroute section. Syntax Parameters Command modes Usage guidelines Command output show mpls lsp [wide frr_lsp] frr_lsp This command operates in all modes. Use to show FRR detailed or extensive display output. The show mpls lsp command displays the following information. Output field Description To: The egress LER for the LSP.
1 IP Traceroute over MPLS Output field Description cspf-computation-mode TE metric of TE link for CSPF computation. use-bypass-metric: cspf-computation-mode Liberal mode for CSPF facility backup computation. use-bypass-liberal: FRR Forwarding State: Example Specifies the Fast Reroute state on the primary and secondary path. Brocade# show mpls lsp name lsp04-3 LSP lsp04-3, to 10.44.44.44 From: 10.11.11.
IP Traceroute over MPLS 1 Standard traceroute Traceroute is a diagnostic utility that allows the user to troubleshoot a network path by iteratively sending Internet Control Message Protocol (ICMP) packets through an IP network from a source to a destination. Packets have a defined TTL and sent to a port that is known to be invalid on the destination device (usually above 3300).
1 IP Traceroute over MPLS Traceroute in an MPLS-enabled network The standard traceroute implementation is insufficient for diagnosing Layer 3 routing problems in an MPLS environment, such as a provider network configured to tunnel a customer’s Virtual Private Network (VPN) traffic through a public backbone. Standard traceroute relies on IP forwarding based on routing table lookup.
IP Traceroute over MPLS 1 Tracing a route through an MPLS domain Figure 41 shows an MPLS-enabled provider network consisting of four LSRs. R1 is the Provider Edge (PE) ingress Label Edge Router (LER), R2 and R3 are transit LSRs, and R4 is the PE egress LER. CE1 is a Customer Edge (CE) device in San Jose, and CE2 is the destination CE on another customer site in Broomfield.
1 IP Traceroute over MPLS 4 5 MPLS Label=1026 Exp=7 TTL=1 S=0 MPLS Label=500000 Exp=7 TTL=1 S=1 <1 ms <1 ms <1 ms 10.34.22.8 <1 ms <1 ms <1 ms 10.1.3.8 NOTE The traceroute output reports information on a traceroute packet only when its TTL equals 1. Label stack information associated with subsequent routing of the ICMP message along the LSPs to the destination and back to the source is not displayed. In the Figure 41 scenario, the traceroute operation can be described as follows: 6.
IP Traceroute over MPLS 1 9. CE1 sends a forth traceroute probe with a TTL value of 4. The packet is label-switched until it arrives at PE2 with a TTL value of 1. PE2 drops the packet and generates an ICMP ttl-exceeded message without label stack extension. Traceroute reports only the IP address of PE2. There is no label stack to report.
1 IP Traceroute over MPLS The no option disables the ICMP MPLS response configuration. When the feature is disabled, standard traceroute is used to trace a traffic path through an MPLS domain. The output of the show ip traffic command displays counts for ICMP messages that have been generated by an MPLS-enabled LSR with label extensions and returned to the source of the traceroute probe. Refer to “Displaying IP traffic statistics” for a description of the show ip traffic command and associated output.
IP Traceroute over MPLS 1 • IP Traceroute over MPLS supports IPv4 traceroute only. Configuration examples The MPLS response feature supports four different configuration options for controlling the traceroute behavior in an MPLS domain. The command behavior varies depending on what types of routes are configured for a given MPLS domain. The following examples assume the same MPLS response configuration for each of the LSRs in the MPLS domain.
1 IP Traceroute over MPLS 1. Re-enable the MPLS response default configuration on each LSR (R1, R2, R3, and R4). Brocade# configure terminal Brocade(config)# ip icmp mpls-response 2. On CE 1 (IP address 10.3.3.3), issue the traceroute command with the destination address of CE2 (IP address 10.1.3.8). CE1# traceroute 10.1.3.8 Type Control-c to abort Tracing the route to IP node (10.1.3.8) from 1 to 30 hops 1 <1 ms <1 ms <1 ms 10.51.3.7 2 * * * ? 3 * * * ? 4 * * * ? 5 <1 ms <1 ms <1 ms 10.1.3.
IP Traceroute over MPLS 1 Scenario B - Layer 3 VPN over MPLS MPLS is enabled in the provider core. Customer traffic is routed through the provider network using a Layer 3 VPN. The egress PE is a Brocade NetIron CER or a Brocade NetIron CES. 1. Issue the ip icmp mpls-response command with the use-lsp option on each LSR (R1, R2, R3, and R4). Brocade# configure terminal Brocade(config)# ip icmp mpls-response use-lsp 2. On the CE 1 (IP address 10.3.3.
1 IP Traceroute over MPLS 1 2 3 4 5 <1 <1 <1 <1 <1 ms ms ms ms ms <1 <1 <1 <1 <1 ms ms ms ms ms <1 <1 <1 <1 <1 ms ms ms ms ms 10.51.3.7 10.56.1.2 10.52.10.4 10.34.22.8 10.1.3.8 In this scenario, IP traceroute over MPLS behaves just like the standard traceroute command. At each hop, ICMP messages are generated and returned to the destination (source CE1) as regular IP packets through standard IP routing protocols.
MPLS LDP-IGP synchronization 1 This example is included only to illustrate the CLI behavior. It is not useful for diagnosing LSP routing problems. Regardless of whether the user has IP over MPLS or a Layer 3 VPN configured, the provider transit router cannot propagate ICMP errors without label extensions when use-lsp is specified. For this reason, traceroute returns information only for the PE1 and CE2. 1.
1 MPLS LDP-IGP synchronization • LDP determines convergence (receipt of all labels) for a link by one of two methods. - Receive Label silence mechanism - End Of Lib mechanism (RFC 5919) • Provides a means to disable LDP-IGP Synchronization on interfaces that the user does not want enabled. • Enables the user to globally enable LDP-IGP synchronization on each interface associated with an IGP Open Shortest Path First (OSPF) or IS-IS process.
MPLS LDP-IGP synchronization 1 Configuring MPLS LDP-IGP synchronization This section contains the following tasks: • Configuring MPLS LDP-IGP synchronization with OSPF interfaces (required). • Selectively Disabling MPLS LDP-IGP synchronization from some OSPF interfaces (optional). • Verifying MPLS LDP-IGP synchronization with OSPF (optional). NOTE Brocade recommends configuring the hold-down timer to more than 60 seconds to avoid traffic loss.
1 MPLS LDP-IGP synchronization By default, ldp-sync hold-down is disabled. To enable the ldp-sync hold-down timer with IS-IS, enter the following commands: Brocade(conf)# router isis Brocade(config-isis-router)# address-family ipv4 unicast Brocade(config-isis-router-router-ipv4u)# metric-style wide Brocade(config-isis-router-router-ipv4u)# ldp-sync Brocade(config-isis-router-router-ipv4u)# ldp-sync hold-down 100 By default, ldp-sync hold-down is disabled.
MPLS LDP-IGP synchronization 1 The value parameter specifies the length of time of the receive label silence timer in milliseconds. Possible values are from 100 to 60000 milliseconds. The default value is 1000. Enabling the end-of-lib submode Configure the end-of-lib submode under LDP to contain all the attributes of the end of lib capability and notification.
1 MPLS LDP-IGP synchronization The value parameter specifies the length of the EOL transmit label silence timer in milliseconds. Possible values are from 100 to 60000 milliseconds. The default value is 1000.
MPLS LDP-IGP synchronization 1 LDP-SYNC: Globally enabled, Hold-down time 66 sec Interfaces with LDP-SYNC enabled: eth 1/3 eth 1/4 Syntax: show ip ospf configuration Displaying LDP IGP synchronization interface information Use the show isis inter | show ip ospf inter under the config-if-e10000-1/3 policy to show: • The enable or disable state for the LDP-IGP sync • The time remaining in the hold down, when the hold-down is specified. Otherwise, it displays “-1”.
1 MPLS LDP-IGP synchronization Displaying the show mpls ldp configuration Use the sh mpls ldp command to view the extended parameters. Label Distribution Protocol version 1 LSR ID: 10.1.7.
Displaying MPLS and RSVP information 1 Use the show mpls int command to view the current cached LDP-IGP sync state.
1 Displaying MPLS and RSVP information Brocade# show mpls interface ethernet 1/1 e1/1 Admin: Up Oper: Up Maximum BW: 10000000 kbps, maximum reservable BW: 8000000 kbps (80%) Admin group: 0x00000000 Reservable BW [priority] kbps: [0] 8000000 [1] 8000000 [2] 8000000 [3] 8000000 [4] 8000000 [5] 8000000 [6] 8000000 [7] 8000000 Last sent reservable BW [priority] kbps: [0] 8000000 [1] 8000000 [2] 8000000 [3] 8000000 [4] 8000000 [5] 8000000 [6] 8000000 [7] 8000000 Configured Protecting bypass lsps: 1 Syntax: sh
Displaying MPLS and RSVP information 1 Displaying MPLS statistics The following sections describe the commands used to gather MPLS statistics. Displaying MPLS label statistics To display all of the MPLS traffic statistics by their MPLS label, enter the following command.
1 Displaying MPLS and RSVP information . Brocade# show mpls statistics In-label In-Port(s) 1024 e3/1 - e3/20 1026 e3/1 - e3/20 1030 e3/1 - e3/20 1032 e3/1 - e3/20 1033 e3/1 - e3/20 1034 e3/1 - e3/20 1036 e3/1 - e3/20 label 3/1 In-Packet Count 30 21 100 0 0 12 0 To display all MPLS traffic statistics by their MPLS label for a specific port on a Brocade NetIron CES or Brocade NetIron CER device, enter a command such as the following.
Displaying MPLS and RSVP information Brocade# show mpls statistics Tunnel In-Port(s) 1 e1/1 - e1/20 e2/1 - e2/2 e3/1 - e3/2 e3/3 - e3/4 e4/1 - e4/20 1 tunnel 1 L3VPN/IPoMPLS Out-Pkt 0 0 0 0 0 Table 16 lists the output displayed for the show mpls statistics tunnel command. TABLE 16 show mpls statistics tunnel parameters This field... Displays... Tunnel The index number of the MPLS tunnel. In-Port(s) The port where the traffic is received.
1 Displaying MPLS and RSVP information Displaying MPLS VRF statistics To display out-packet statistics for VRFs, enter the following command.
Displaying MPLS and RSVP information TABLE 17 1 show mpls statistics VRF parameters (Continued) This field... Displays... Endpt Out-Pkt The number of packets forwarded to the specified VRF interface. Tnl Out-Pkt The number of VRF data packets sent to the remote peer over an MPLS tunnel. Syntax: show mpls statistics vrf vrf-name The vrf-name variable allows the user to limit the display of VRF statistics to a specific VRF.
1 Displaying MPLS and RSVP information Brocade# show mpls statistics lsp LSP test1 Tunnel interface tnl2 4241 pkt 1187480 Byte 10 pps LSP test2 Tunnel interface tnl3 0 pkt 0 Byte 0 Avg. pps 2800 Bps 0 Avg. Bps Syntax: show mpls statistics lsp [name] The name variable specifies the LSP for which LSP accounting statistics are displayed. When the user does not specify an LSP name, statistics are displayed for all RSVP-signaled LSPs.
To display LDP-signaled LSP accounting statistics, enter the following command. 1 To display LDP-signaled LSP accounting statistics, enter the following command.
1 show mpls statistics ldp tunnel [dec|vif-index] show mpls statistics ldp tunnel [dec|vif-index] This is an existing command (in NI R05.500). No change is made to its syntax. The output of this command now shows the total combined statistics of all ECMP paths of an LDP tunnel with LDP ECMP LER feature. Syntax Parameters show mpls statistics ldp tunnel [dec|vif-index] dec The dec keyword is the destination prefix.
Displaying the Traffic Engineering database 1 The name variable specifies LSP that the user wants to clear byte and packet counters for. When the user does not specify an LSP name, byte and packet counters is cleared for all RSVP-signaled LSPs. Byte and packet counters can be cleared for LDP-signaled LSPs using the following commands.
1 Displaying the Traffic Engineering database Brocade# show mpls ted database AreaId: 0 NodeID: 2.2.2.2, Type: Router Type: M/A, To: 10.1.1.3, Local: NodeID: 3.3.3.3, Type: Router Type: P2P, To: 10.6.6.6, Local: Type: M/A, To: 10.1.1.3, Local: Type: M/A, To: 10.1.1.2, Local: NodeID: 10.1.1.3, Type: Network Type: M/A, To: 10.1.1.1, Local: Type: M/A, To: 10.2.2.2, Local: Type: M/A, To: 10.3.3.3, Local: NodeID: 30.1.1.2, Type: Network Type: M/A, To: 10.1.1.1, Local: Type: M/A, To: 10.6.6.6, Local: 10.1.1.
Displaying the Traffic Engineering database TABLE 18 1 Output from the show mpls ted data command (Continued) This field... Displays... [link] Type The type of link. The link type can be either P2P or M/A P2P Indicates this is a point-to-point link. M/A Indicates the link is a broadcast, multi-access network. To The ID of the node at the end of this link. Local The address of the interface used to reach the remote node.
1 Displaying the Traffic Engineering database TABLE 19 Output from the show mpls ted database detail command This field... Displays... Color The administrative groups to which this interface belongs. Metric The traffic engineering metric for the interface (by default, this is equal to the OSPF link cost). Max BW The maximum outbound bandwidth that can be used on the interface. This is the actual physical bandwidth of the interface (155M for OC-3, 622M for OC-12, or 2488M for OC-48).
Displaying the Traffic Engineering database TABLE 20 1 Parameters from the show mpls ted path command (Continued) CLI parameter Description hop-limit max_hops The maximum hops for the path to reach to its destination. The valid range is between 0 - 255. When an invalid range is entered, then an error message displays. When a path to the destination is available, but the hop count for the path is greater than max_hops value, then MPLS indicates that path is not available.
1 Displaying the Traffic Engineering database When an out of range parameter value is entered, the following error message is displayed for the priority parameter. Priority Error - Setup priority value is out of range [0 - 7] The following table describes the output of the show mpls ted path command. TABLE 21 Output from the show mpls ted path command This field... Displays... Path to10.4.4.4 found The IPv4 address of the destination host is found.
Displaying the Traffic Engineering database TABLE 22 1 Output from the show mpls lsp command (Continued) This field... Displays... Oper State The operational state of the LSP. This field indicates whether the LSP has been established through signaling and is capable of having packets forwarded through it. There may be a short period of time after the user enables the LSP that the administrative state of the LSP is UP, but the operational state is DOWN.
1 Displaying the Traffic Engineering database Syntax: show mpls lsp [detail / lsp_name] The lsp_name variable specifies the name of the LSP the user wants to display. Table 23 describes the output from the show mpls lsp detail command. TABLE 23 240 Output from the show mpls lsp detail command This field... Displays... Name The name of the LSP. LSPs are displayed in alphabetical order. To The egress LER for the LSP. From The LSPs source address, configured with the from command.
Displaying the Traffic Engineering database TABLE 23 1 Output from the show mpls lsp detail command (Continued) This field... Displays... Max rate The maximum rate of packets that can go through the LSP (in kbps), set with the traffic-eng max-rate command. mean rate The average rate of packets that can go through the LSP (in kbps), set with the traffic-eng mean-rate command.
1 Displaying the Traffic Engineering database TABLE 23 Output from the show mpls lsp detail command (Continued) This field... Displays... rx-interval The rx-interval value in milliseconds that has been negotiated between this router and its peer for this LSP. multiplier The multiplier value in milliseconds that has been negotiated between this router and its peer for this LSP.
Displaying the Traffic Engineering database Brocade# show mpls path Path Name Address to110_120 10.110.110.2 10.120.120.3 to2_pri 10.10.10.2 to2_sec 10.110.110.2 to3 10.110.110.2 10.120.120.3 to3_pri 10.10.10.2 10.20.20.3 to3_sec 10.110.110.2 10.120.120.3 to4 10.110.110.2 10.120.120.3 10.130.130.4 to_23 10.110.110.2 10.20.20.
1 Displaying the Traffic Engineering database Brocade# show mpls path wide | include pathfromsanfranciscotonewyork Path Name Address Strict/loose Usage Pathfromsanfranciscotonewyork 10.10.10.2 Strict 1 Syntax: show mpls path [wide [| include path-name]] The path-name variable specifies the name of the path the user wants to display. Displaying the MPLS routing table The MPLS routing table is used to store routes to egress LERs.
1 Displaying the Traffic Engineering database TABLE 25 Output from the show mpls route command (Continued) This field... Displays... Label The MPLS label received from the downstream router. sig The signal protocol type associated with the label. Possible values are: • L – LDP • R – RSVP Usage The number of LSPs that are either currently using or configured to use the path.
1 Displaying the Traffic Engineering database TABLE 26 Output from the show mpls forwarding command (Continued) This field... Displays... in-intf The interface through which the label identified in the in-lbl column has been received for the LSP. A value of 0 indicates the absence of the segment. When applicable, the in-intf field also displays a VE interface specified by the variable. out-lbl The outgoing segment or downstream label for the LSP.
Displaying the Traffic Engineering database 1 Displaying the RSVP version To display the RSVP version number, as well as the refresh interval and refresh multiple. Brocade# show mpls rsvp Resource ReSerVation Protocol, version 1. rfc2205 RSVP protocol = Enabled R (refresh interval) = 30 seconds K (refresh multiple) = 3 Syntax: show mpls rsvp Displaying the status of RSVP interfaces Use the following command to display the status of RSVP on devices where it is enabled.
1 Displaying the Traffic Engineering database TABLE 27 Output from the show mpls rsvp interface command (Continued) Field Description MD5 Whether RSVP message authentication is enabled on the interface. RelMsg Whether RSVP reliable messaging is enabled on the interface. Bundle Whether RSVP bundle messages are enabled on the interface. SRefresh Whether RSVP summary refresh is enabled on the interface. Num of OutSegs Act/Inact/Resv Out segments are traffic connections on the link.
Displaying the Traffic Engineering database TABLE 28 1 Output from the show mpls rsvp interface detail command (Continued) Field Description Ack The number of Ack messages sent and received on the interface. Ack messages are reliable messaging acknowledgements of RSVP trigger messages. SumRefresh The number of summary refresh messages sent and received on the interface.
1 Displaying the Traffic Engineering database The detail option displays detailed RSVP session information. The extensive option displays extensive RSVP session information. The wide option displays display the full LSP name in a single line. NOTE The show mpls rsvp session brief command displays the same information as the show mpls rsvp session command. Table 29 describes the output of the show mpls rsvp session command. TABLE 29 Output from the show mpls rsvp session command This field...
Displaying the Traffic Engineering database 1 Brocade# show mpls rsvp session detail Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress Ingress RSVP: 1 session(s) To From St Style Lbl_In Lbl_Out Out_If LSPname 10.140.140.4 10.130.130.
1 Displaying the Traffic Engineering database The extensive option provides the contents of the history buffer for the last 20 RSVP events, as shown in the following example. Brocade# show mpls rsvp session extensive Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress Ingress RSVP: 7 session(s) To From St Style Lbl_In Lbl_Out Out_If LSPname 10.33.33.33 10.11.11.
Displaying the Traffic Engineering database 1 Brocade# show mpls rsvp session wide Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress Ingress RSVP: 4 session(s) 10.3.3.3 10.2.2.2 10.3.3.3 10.10.10.10(BI) 10.3.3.3 10.2.2.2(BYI) 10.3.3.3 10.2.2.2 10.3.3.3 10.10.10.10(BI) 10.3.3.3 10.2.2.
1 Displaying the Traffic Engineering database The backup option limits the display to backup RSVP sessions. The bypass option limits the display to bypass RSVP sessions. The detour option limits the display to detour RSVP sessions. The ingress option limits the display to ingress RSVP sessions. The egress option limits the display to egress RSVP sessions. The transit option limits the display to transit RSVP sessions. The name option limits the display to the RSVP session name.
Displaying the Traffic Engineering database 1 The ppend option displays sessions in the soft preemption pending state. The s2l option displays P2MP source to leaf sub-LSPs. The transit option limits the display to transit P2MP sessions. The up option limits the display to an active P2MP session. The wide option displays long LSP names. Displaying RSVP statistics The device constantly gathers RSVP statistics.
1 Displaying the Traffic Engineering database TABLE 31 Output from the show mpls rsvp statistics command (Continued) This field... Displays... PathTear The number of PathTear messages sent and received. PathTear messages cause path states to be deleted. ResvTear The number of ResvTear messages sent and received. ResvTear messages cause reservation states to be deleted. ResvConf The number of reservation confirmation messages sent and received.
Displaying the Traffic Engineering database 1 Brocade(config)# show mpls rsvp session dest 10.30.30.30 source 10.10.10.10 tun 1 Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress Total Number of such sessions are: 1 To From St Style Lbl_In Lbl_Out Out_If LSPname 10.30.30.30 10.10.10.
1 Displaying the Traffic Engineering database When the user runs the command with the entire session object (destination ip, source ip, tunnel id), the router locates a session based on these filter. The router ignores in-interface and out interface filters when applied in addition to these filters since the entire session is described by its session object. The filters and their description are provided in the following sections. Up displays all the RSVP active sessions.
Displaying the Traffic Engineering database 1 Displaying information about IS-IS LSPs with TE extensions To display information about IS-IS LSPs with TE extensions. Brocade# show isis database level2 detail IS-IS Level-2 Link State Database LSPID LSP Seq Num LSP Checksum LSP Holdtime XMR3.00-00 0x00000644 0x78e3 843 Area Address: 49.0002 NLPID: CC(IP) Hostname: XMR3 Auth: Len 17 MD5 Digest "c33db90a87b93c80111980dbd59a19ed" TE Router ID: 15.15.15.15 Metric: 10 IP-Extended 15.15.15.
1 Displaying the Traffic Engineering database Brocade# show mpls lsp frr_tunnel LSP frr_tunnel, to 10.4.4.4 From: 10.1.1.1, admin: UP, status: UP, tunnel interface: tnl4 Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Maximum retries: 0, no. of retries: 0 Pri.
Displaying the Traffic Engineering database 1 Brocade# show mpls bypass-lsp name t100 LSP t100, to 10.1.1.1 From: 10.2.2.2, admin: UP, status: UP Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Adaptive Maximum retries: NONE, no. of retries: 0 Pri.
1 Displaying the Traffic Engineering database Tspec: peak 0 kbps rate 0 kbps size 0 bytes m 20 M 65535 Fast Reroute: one-to-one backup desired Setup priority: 7, hold priority: 0 Bandwidth: 1024 kbps, hop limit: 255 Detour LSP: UP. Nexthop (node) protection available. Up/Down times: 1, num retries: 0 Explicit path hop count: 3 11.1.1.2 (S) -> 13.1.1.2 (S) -> 15.1.1.2 (S) Received RRO count: 3 Protection codes: P: Local N: Node B: Bandwidth I: InUse 11.1.1.2 (PNB) -> 13.1.1.2 (PNB) -> 15.1.1.
Displaying the Traffic Engineering database 1 Displaying MPLS configuration information The show mpls config command displays all of the user-configured MPLS parameters.
1 Displaying the Traffic Engineering database enable enable-all-interfaces max-bypasses 25 max-bypasses-per-mp 5 reoptimize-timer 20000 lsp-xc-traps enable end of MPLS configuration Syntax: show mpls config brief Displaying in the detail mode The user can display all of the MPLS global information and all of the MPLS configuration information using the show mpls config command.
Displaying the Traffic Engineering database 1 ipmtu 1028 traffic-eng max-rate 180 mean-rate 125 metric 5 shortcuts ospf frr bandwidth 80 hop-limit 55 enable lsp lsp13d to 10.3.3.2 primary mu1_to_mu3 cos 7 traffic-eng max-rate 250 mean-rate 120 no cspf enable lsp lsp12d to 10.1.1.2 cos 7 traffic-eng max-rate 100 mean-rate 50 enable vll c13 5500 vll-peer 10.33.33.1 vlan 200 tagged e 1/3 vll-local l15 vlan 32 untag e 1/4 cos 4 vpls vpmaster 22 vpls-peer 10.66.66.
1 Displaying the Traffic Engineering database Brocade# show mpls config interface ve 20 mpls-interface ve 20 ldp-enable Syntax: show mpls config interface [ethernet slot/port | pos slot/port | ve vid] The ve parameter allows the user to limit the display to VE interface ID specified by the vid variable.
Transit LSP statistics 1 When an option is used without a variable specified, the configuration parameters for the option are shown for all elements that match the option are displayed. For instance, in the following example the lsp option is used without a specified lsp-name variable. Consequently, the display contains the configuration information for all three LSPs configured on the router. Brocade# mpls config lsp lsp frr1 to 10.4.2.
1 Transit LSP statistics TABLE 36 Transit LSP module support Interface module Feature support Packet count Byte count Rate (kbps) NI-MLX-1GX20-GC X NI-XMR-1Gx20-GC X NI-XMR-10Gx4 X NI-MLX-10GX4 X BR-MLX-10GX4-X X BR-MLX-10Gx4-X-ML X NI-MLX-10GX8-M X X X NI-MLX-10GX8-D X X X BR-MLX-10GX8-X X X X BR-MLX-10Gx24-DM X X X BR-MLX-100GX-1 X X X BR-MLX-100GX-2 X X X NetIron CES and NetIron CER limitations LDP LSP statistic collection is not supported; only RSVP LSP transi
Transit LSP statistics BROCADE# show mpls statistics label 2228 In-label In-Port(s) In-Packet Count 2228 e3/1 - e3/8 0 e3/9 - e3/16 81688115422 e3/17 - e3/24 0 In-Byte Count 0 13886979621740 0 1 Rate(in kbps) 0 7345166 0 Syntax: show mpls statistics label [interface|in-label] The interface variable allows the user to limit label statistics displayed to a specified interface. The in-label variable allows the user specify the label value.
1 Transit LSP statistics The wide option displays display the full LSP name in a single line. Table 29 describes the output of the show mpls rsvp session command. TABLE 38 Output from the show mpls rsvp session command This field... Displays... To Destination (egress LER) of the session. From Source (ingress LER) of the session; the source address for the LSP that was configured with the from command. Packets Specifies the number of packets received.
Transit LSP statistics 1 Clearing MPLS RSVP sessions To clear only the RSVP statistics transit counters, enter the following command: Brocade# clear mpls statistics rsvp session 10.2.2.2 10.1.1.1 5 Syntax: clear mpls statistics rsvp session destination ip address / source ip address / tunnel id Where the destination ip address specifies the destination IP address of session object. Where the source ip address specifies the source ip address of session object.
1 Transit LSP statistics end of MPLS configuration To reset counter-mode to byte, enter the following command. Brocade(config-mpls)# no counter-mode packet To verify the configuration, enter the following command. Brocade(config-mpls)# show mpls conf router mpls mpls-interface e1/11 end of MPLS configuration MPLS sample configurations This section presents examples of typical MPLS configurations.
Transit LSP statistics 1 Path direct_conn is the primary path for LSP t3, and path via_r2 is the secondary path. When the LSP is enabled, RSVP signaling messages set up path direct_conn. Packets assigned to this LSP use this path to reach the destination. When path direct_conn fails, path via_r2 is set up, and packets assigned to LSP t3 then use path via_r2 to reach the destination. By default, the secondary path is not set up until the primary path fails.
1 Transit LSP statistics Brocade(config-mpls)# interface e 4/1 Brocade(config-e10000-4/1)# ip address 10.20.1.1 255.0.0.0 Brocade(config-e10000-4/1)# ip ospf area 1 Brocade(config-e10000-4/1)# exit Brocade(config)# router ospf Brocade(config-ospf-router)# area 1 Brocade(config-ospf-router)# exit Router R3 In the configuration in Figure 43, Router R3 is the egress LER for LSP t3.
Transit LSP statistics 1 The following is the MPLS Fast Reroute configuration for Ingress Router 4. Router4(config)# interface loopback 1 Router4(config-lbif-1)# ip address 10.4.4.4/24 Router4(config)# interface ethernet 2/1 Router4(config-if-e1000-2/1)# ip address 10.10.10.2/24 Router4(config)# interface ethernet 2/9 Router4(config-if-e1000-2/9)# ip address 10.13.13.
1 Transit LSP statistics The Transit Router 6 display The following display examples are from Transit Router 6. Displays are shown for the show mpls rsvp session and show mpls rsvp session detail commands. Both displays show two paths from Ingress Router 4 at Loopback IP address 10.4.4.4. to Egress Router 5 at Loopback IP address 10.5.5.5. The (DI) path is an Ingress Detour path, and the path without a code is a protected path.
Transit LSP statistics To From St Style Lbl_in Lbl_out 10.5.5.5 10.4.4.4 Up SE 1024 3 Time left in seconds (PATH refresh: 28, ttd: 150 RESV refresh: 24, ttd: 128) Tspec: peak 0 kbps rate 0 kbps size 0 bytes m 20 M 1500 Fast Reroute: one-to-one backup desired Setup priority: 7, hold priority: 0 Bandwidth: 0 kbps, hop limit: 255 Detour LSP: UP. Nexthop (node) protection available. Up/Down times: 1, num retries: 0 Explicit path hop count: 1 10.19.19.
1 Transit LSP statistics For the DM path, one PLR and Avoid Node ID pair is shown labeled [1]. In [1] the Point of Local Repair (PLR) is at IP Address 10.19.19.2 which is an interface on Transit Router 6 and the Avoid Node is IP address 0.0.0.0. For the primary path, the “Explicit path hop count” field indicates that the path has two hops from this router to the egress to the path at routers with the following IP addresses 10.18.18.2 (Transit Router 6) and 10.19.19.1 (Egress Router 5).
Transit LSP statistics 1 Detour Rcvd: Number of PLR and Avoid Node ID pair(s): 1 [1]: PLR: 10.19.19.2 Avoid Node: 0.0.0.0 PATH rcvfrom: 10.18.18.2 (e2/1 ) (MD5 OFF) RESV rcvfrom: 10.13.13.1 (e5/10 ) (MD5 OFF) Egress RSVP: 0 session(s) The Ingress Router 4 display The following display examples are from Ingress Router 4. Displays are shown for the show mpls rsvp session and show mpls rsvp session detail commands.
1 Transit LSP statistics Ingress RSVP: 1 session(s) To From St Style Lbl_in Lbl_out 10.5.5.5 10.4.4.4(DI) Up SE 1028 Time left in seconds (PATH refresh: 16, ttd: 4293608 RESV refresh: 27, ttd: 133) Tspec: peak 0 kbps rate 0 kbps size 0 bytes m 20 M 65535 Explicit path hop count: 3 10.10.10.1 (S) -> 10.11.11.2 (S) -> 10.15.15.2 (S) Received RRO count: 3 Protection codes: P: Local N: Node B: Bandwidth I: InUse 10.10.10.1 -> 10.11.11.2 -> 10.15.15.
Transit LSP statistics Router3# show mpls rsvp session Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour RP:Repaired Session Ingress RSVP: 0 session(s) Transit RSVP: 1 session(s) To From St Style Lbl_in Lbl_out 10.5.5.5 10.4.4.4(DT) Up SE 1028 1028 Egress RSVP: 0 session(s) 1 LSPname 1 The following example displays the output from Transit Router 3 using the show mpls rsvp session detail command.
1 Transit LSP statistics The following example displays the output from Transit Router 1 using the show mpls rsvp session detail command. This option provides additional details about the paths described in the output from the show mpls rsvp session command For the DT path, the “Explicit path hop count” field indicates that there is one hop from this router to the egress of the path at the router at IP address 10.15.15.2 (Egress Router 5).
Transit LSP statistics 1 There is no “Explicit path hop count” field for either route because Egress Router 5 is the destination of the path. Router5# show mpls rsvp session detail Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour RP:Repaired Session Ingress RSVP: 0 session(s) Transit RSVP: 0 session(s) Egress RSVP: 1 session(s) To From St Style Lbl_in Lbl_out 10.5.5.5 10.4.4.
1 Transit LSP statistics Brocade# show mpls interface ethernet 4/15 e4/15 Admin: Up Oper: Up Maximum BW: 1000000 kbps, maximum reservable BW: 1000000 kbps Admin group: 0x00000000 Reservable BW [priority] kbps: [0] 780000 [1] 780000 [2] 780000 [3] 760000 [4] 760000 [5] 760000 [6] 760000 [7] 760000 Last sent reservable BW [priority] kbps: [0] 780000 [1] 780000 [2] 780000 [3] 760000 [4] 760000 [5] 760000 [6] 760000 [7] 760000 Configured Protecting bypass lsps: xmr4-by(UP) Syntax: show mpls interface etherne
Transit LSP statistics 1 Brocade(config-if-e1000-2/15)# show mpls bypass-lsp Note: LSPs marked with * are taking a Secondary Path Admin Oper Tunnel Up/Dn Retry Active Name To State State Intf Times No. Path xmr1-2 10.11.11.11 UP UP tnl4 2 0 -xmr1-1 10.11.11.11 UP UP tnl3 2 0 -xmr4 10.44.44.44 UP UP tnl7 2 0 xmr4-1 xmr1 10.11.11.11 UP UP tnl2 2 0 -xmr1-5 10.11.11.11 UP UP tnl5 2 0 -xmr3 10.33.33.
1 Transit LSP statistics Brocade (config-mpls-bypasslsp-b1)# show mpls bypass-lsp detail LSP b1, to 10.6.6.6 From: 10.7.7.7, admin: UP, status: UP, tunnel interface(primary path): tnl0 Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Adaptive Maximum retries: NONE, no. of retries: 0 Pri.
Transit LSP statistics 1 The include option can be used with the show mpls bypass-lsp wide command to filter and display specific bypass LSP name. Brocade# show mpls bypass-lsp wide | include bypasstunnelfromsanfranciscotonewyork Admin Oper Tunnel Up/Dn Retry Active Name To State State Intf Times No. Path bypasstunnelfromsanfranciscotonewyork 10.3.3.
1 Transit LSP statistics Bypass LSP in an RSVP session Use the show RSVP session command to display bypass LSP xmr1-by. This example shows bypass LSP traversing a LAG, and the BYI field shows this is the bypass ingress. Brocade# show mpls rsvp sess name xmr1-by Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress To From St Style Lbl_in Lbl_out LSPname 10.11.11.11 10.55.55.
Transit LSP statistics 1 Brocade# show mpls lsp xmr3-120 LSP xmr3-120, to 10.33.33.33 From: 10.55.55.55, admin: UP, status: UP, tunnel interface(primary path): tnl35 revert timer: 10 seconds Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Maximum retries: 0, no. of retries: 0 Pri.
1 Transit LSP statistics Protected LSP shown in RSVP session Show the MPLS RSVP session for protected LSP xmr3-199. The line “Backup LSP UP. Nexthop (node) protection available” shows that protection is available for xmr-199. If this LSP were actually riding the bypass LSP, this status would change from “protection available” to “in use.”.
Transit LSP statistics 1 Brocade@XMR5# show mpls rsvp sess name xmr3-120 Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup RP:Repaired Session BYI: Bypass Ingress To From St Style Lbl_in Lbl_out LSPname 10.33.33.33 10.55.55.
1 Commands The following command shows an LSP that is using its bypass. Note the last lines of output. Brocade# show mpls lsp xmr3-120 LSP xmr3-120, to 10.33.33.33 From: 10.55.55.55, admin: UP, status: UP, tunnel interface(primary path): tnl35 revert timer: 10 seconds Times primary LSP goes up since enabled: 1 Metric: 0, number of installed aliases: 0 Maximum retries: 0, no. of retries: 0 Pri.
show mpls lsp_p2mp_xc 1 show mpls lsp_p2mp_xc Displays hardware forwarding information Syntax Parameters show mpls lsp_p2mp_xc in_label in_label Specifies the MPLS input label value. Command Modes Privileged EXEC mode Usage Guidelines The show mpls lsp_p2mp_xc command displays information about the forwarding information of hardware that is allocated for the point-to-multipoint (P2MP) cross-connect.
1 show mpls lsp_p2mp_xc flag: 0, pool_index:1, avail_data:270e0800 The following example displays hardware forwarding statistics on a Brocade NetIron CES device: Brocade# show mpls lsp_p2mp_xc P2MP XC TABLE: TOTAL USED = 1 IN-LABEL XC# IP-TTI @ PPCR{1, 2, 3} MPLS-TTI@{PPCR 1, 2, 3} IN-PORT NUM_OUT_SEGS START-DIT 1024 1 65274 65275 1/1 2 2049 Brocade# show mpls lsp_p2mp_xc 1024 TOTAL OUT_SEGS under the given in_label = 2 BRANCH-ID OUT-LABEL 0 2001 1 2002 Event History Tue Aug 14 12:53:17 Tue Aug 14 12:52:
Chapter 2 Configuring Label Distribution Protocol (LDP) LDP overview Table 40 displays the individual Brocade devices and the Label Distribution Protocol (LDP) features they support.
2 LDP overview TABLE 40 296 Supported Brocade Label Distribution Protocol (LDP) features (Continued) Features supported Brocade NetIron XMR Series Brocade MLX Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package Resetting LDP neighbor Yes Yes No Yes No No Yes LDP graceful restart Yes Yes N
2 LDP overview TABLE 40 Supported Brocade Label Distribution Protocol (LDP) features (Continued) Features supported Brocade NetIron XMR Series Brocade MLX Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package Displaying LDP Neighbor Connection Information Yes Yes No Yes No No Yes Displaying the
2 Configuring LDP on an interface The Multi-Service IronWare software the LDP label space ID has a default value of zero which improves interoperability with routers from other vendors. Also, to provide backward compatibility with Multi-Service IronWare software previous versions, a command lets the user change the LDP label space ID value to 1 as described in “Resetting LDP neighbors”. Configuring LDP on an interface To use LDP, a loopback address (with a 32-bit mask) must be configured on the LSR.
LDP Inbound-FEC filtering 2 LDP Inbound-FEC filtering MPLS LDP inbound-FEC filtering filters inbound label bindings on a MPLS router. The user can control the amount of memory and CPU processing involved in installing and advertising label bindings not used for forwarding. MPLS LDP inbound-FEC filtering also serves as a tool to avoid DOS attack. By creating a prefix-list, and specifying prefixes label mappings, the forwarding plane accepts and installs the label bindings.
2 LDP Inbound-FEC filtering The prefix list parameter specifies the prefixes. The in keyword specifies inbound-fec-filter configuration. Use the [no] form of this command to remove the LDP inbound FEC filter. Modifying prefix-list after setting it in the filter-inbound-FEC When the prefix-list referenced by the LDP inbound-FEC filter is configured or changes, all the existing in-bound FECs and received later are subject to the changed prefix-list.
LDP Inbound-FEC filtering 2 Label Distribution Protocol version 1 LSR ID: 10.122.122.
2 LDP Inbound-FEC filtering Table 41 shows the field and output display of the show mpls ldp command. TABLE 41 Output from the show mpls ldp command. This field... Displays... Label Distribution Protocol version The LDP version. LSR ID The identifier of the device and the loopback interface number the LDP uses. LDP advertises the address of this loopback interface in address messages. Hello interval How often the device sends out LDP link hello and targeted hello messages.
LDP Inbound-FEC filtering 2 show mpls ldp fec filtered The show mpls ldp fec filtered command displays filtered information as shown below. Brocade(config)# show mpls ldp fec prefix prefix-filter prefix-list Total number of prefix FECs: 11 Destination State Out-interface Next-hop Ingress Egress 10.44.44.44/32 current --No Yes 10.66.66.66/32 current e4/2 10.1.1.2 Yes No 10.14.14.14/32 current e3/16 10.55.55.14 Yes No 172.16.8.0/24 current e3/16 10.55.55.14 Yes No 172.16.16.0/24 current e3/16 10.55.55.
2 LDP Inbound-FEC filtering State: current, Ingr: Yes, Egr: No, UM Dist. done: No Prefix: 172.16.8.0/24 next_hop: 10.55.55.14, out_if: e3/16 Downstream mappings: Local LDP ID Peer LDP ID 10.44.44.44:0 10.14.14.14:0 Label 1024 State Retained (f) CB 0x2cd3b610(-1) Table 60 shows the field and output display of the show mpls ldp fec prefix prefix-filter command. TABLE 42 Output from the show mpls ldp fec prefix prefix-filter command This field... Displays...
LDP Inbound-FEC filtering Upstream label database: Label Prefix 3 10.44.44.44/32 1024 10.66.66.66/32 Session 10.44.44.44:0 - 10.66.66.66:0 Downstream label database: Label Prefix 3 10.66.66.66/32 Upstream label database: Label Prefix 3 10.44.44.44/32 1025 10.14.14.14/32 2 State Installed Refer to Table 60 for additional information.
2 LDP Inbound-FEC filtering 1. Use the following command to configure the prefix list to allow all /32 addresses: Brocade(config)# ip prefix filter172_24 permit 172.16.09.0/16 ge 24 le 24 2. Configure the prefix list to allow 172.16.0.0/16 ge 24 le 24: Brocade(config)# ip prefix filter172_24 permit 172.16.09.0/16 ge 24 le 24 3. Configure the prefix list to allow 172.16.0.0/16 ge 24 le 28: Brocade(config)# ip prefix-list filter172_28 permit 172.16.0.0/16 ge 24 le 28 4.
LDP outbound FEC filtering 3 10.66.66.66/32 Upstream label database: Label Prefix 3 10.44.44.44/32 1024 172.16.8.0/24 1025 172.16.16.0/24 1026 172.16.32.0/24 1027 172.16.64.0/24 1028 172.16.8.0/28 1029 172.16.8.16/28 1030 172.16.8.32/28 1031 172.16.8.64/28 1032 10.14.14.14/32 2 Installed LDP outbound FEC filtering LDP performs a hop-by-hop or dynamic path setup in an MPLS network by assigning and distributing labels to routes learned from the underlying IGP routing protocols.
2 LDP outbound FEC filtering Configuration steps Follow the listed steps to configure LDP outbound FEC filter. 1. Create a prefix-list to permit or deny required set of FECs. 2. Go to the ldp config mode available on the router mpls config mode. 3. Set the above created prefix-list in the global or per neighbor outbound fec filter configuration. Configuration example For Global outbound FEC filter configuration Example: To set LDP to prevent advertisement of FEC 10.44.44.
Commands 2 Commands The following commands support this feature: • • • • • • • • show configuration/running-config show mpls config show mpls ldp show mpls ldp session detail show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] show mpls ldp fec prefix A.B.C.
2 show configuration/running-config show configuration/running-config The show configuration and show running-config commands displays specific MPLS interface configuration information. The outbound-fec filter configuration parameter now records in the startup or running configuration.It also now displays the name of the prefix-list configured in the LDP for outbound FEC filtering. Syntax show configuration running-config Parameters Command modes Usage guidelines None.
show mpls config 2 show mpls config The show mpls config command displays all of the user-configured MPLS parameters. The show mpls config [brief] command and show running-config [brief] command are enhanced to display the outbound FEC filter configuration parameter. Syntax show mpls config [brief] show-running-config [brief] Parameters brief The brief option displays brief MPLS configuration information. Command modes Usage guidelines Command output Example This command operates in all modes.
2 show mpls ldp show mpls ldp The show mpls ldp command displays the inbound FEC-filter configuration. When applying the prefix-list on LDP filter-FEC before creating it, it displays as “unbound”. The output of show mpls ldp command is modified to accommodate the out-bound FEC filter configuration. The prefix-list is displayed as (does not exist) when the given prefix-list is not created in system.
show mpls ldp Example 2 Command output Description Tunnel metric Displays information to decide whether LDP or RSVP is the preferred method for BGP next-hop resolution. Graceful restart Provides the show GR setting and the status of the forwarding state hold timer with the remaining time when it is running. Label withdrawal delay How long the device waits before sending a label withdrawal message for a FEC to a neighbor.
2 show mpls ldp session detail show mpls ldp session detail Use the show mpls ldp session detail command to display the number of FECs from the peer which are filtered due to the inbound FEC filter configuration. The output of show mpls ldp session detail command is modified to accommodate the out-bound FEC filter configuration. The prefix-list displays as (does not exist) when the given prefix-list is not created in system.
show mpls ldp session detail Example 2 Output field Description MD5 Authentication Key The MD5 authentication key is displayed in an encrypted form when you do not have the correct privileges. When you have the correct permission, it displays as clear text. Neighboring interfaces The interfaces where an LDP neighbor or adjacency relationship has been established with the peer. When there are multiple connections between two LDP-enabled peers, there can be multiple neighboring interfaces.
2 show mpls ldp session detail History Related commands 316 Release Command history Multi-Service NetIron Release 05.600 The output of show mpls ldp session detail command is modified to accommodate the out-bound FEC filter configuration. The prefix-list displays as (does not exist) when the given prefix-list is not created in system. The filtered FEC counter now shows both, filtered because of inbound and outbound filtering action. None.
show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] 2 show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] The command show mpls ldp session a.b.c.d is extended to include the option filtered. When this option is supplied, the display includes a list of upstream and downstream mappings for the session which are filtered due to the outbound and inbound FEC filter configuration.
2 show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] Output field Description KeepAlive interval: The number of seconds between successive KeepAlive messages send for an LDP session.When ka-interval is configured, then ka-timeout value displays as product ka-interval * ka-int-count. Max hold time: The number of seconds that the “Hold time remain” counter is reset to once a KeepAlive message is received from the peer.
show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] 2 Number of Operational link LDP sessions: 1 Number of targeted LDP sessions: 0 Number of Operational targeted LDP sessions: 0 Peer LDP ID: 10.12.12.12:0, Local LDP ID: 10.14.14.
2 show mpls ldp session a.b.c.d/brief/detail [filtered [in|out]] Outbound FEC filtering prefix-list: list-out FECs received from peer and filtered inbound 3 192.168.1.6/32 3 192.168.1.7/32 3 192.168.1.8/32 3 192.168.1.9/32 3 192.168.1.10/32 Router # show mpls ldp session 10.12.12.12 filtered out Number of link LDP sessions: 1 Number of Operational link LDP sessions: 1 Number of targeted LDP sessions: 0 Number of Operational targeted LDP sessions: 0 Peer LDP ID: 0.12.12.12:0, Local LDP ID: 10.14.14.
show mpls ldp fec prefix A.B.C.D/y 2 show mpls ldp fec prefix A.B.C.D/y The prefix option is introduced to the show mpls ldp fec command. The show mpls ldp fec prefix command displays the total number of Layer 3 FECs.The output of show mpls ldp fec prefix command is modified to indicate the upstream mappings, which are filtered because of the action of peer or global outbound FEC filter, as (f) instead of the label.
2 show mpls ldp fec prefix A.B.C.D/y Example Command output Description Downstream Mappings Contents of the downstream mapping CB created as a result of the label mapping received from the downstream LDP peer. Local LDP ID Local LDP ID of the LDP session to which this downstream mapping CB belongs. Peer LDP ID Remote LDP ID of the LDP session to which this downstream mapping CB belongs. Label MPLS label received from the downstream LSR. State State of label. Either installed or retained.
show mpls ldp fec prefix 2 show mpls ldp fec prefix An additional column is added in the output of this command to indicate that the FEC is filtered because of Inbound (In) or Outbound (Out) FEC filter action or if it is not filtered ( - ). The filtered prefix FEC counter now includes counters for both inbound and outbound filtered FEC. Syntax Parameters show mpls ldp fec [prefix [A.B.C.
2 show mpls ldp fec prefix 192.168.1.2/32 192.168.1.3/32 192.168.1.4/32 192.168.1.5/32 current current current current e2/1 e2/1 e2/1 e2/1 10.23.23.12 10.23.23.12 10.23.23.12 10.23.23.12 Yes Yes Yes Yes No No No No In Out Out - History Release Command history Multi-Service NetIron Release 05.600 An additional column is added in the output of this command to indicate that the FEC is filtered because of Inbound (In) / Outbound (Out) FEC filter action or if it is not filtered ( - ).
show mpls ldp fec prefix [filtered [in|out]] 2 show mpls ldp fec prefix [filtered [in|out]] The filtered options on the show mpls ldp fec prefix command now includes lists of both, FECs filtered due to inbound and outbound FEC filtering configuration. It also has two sub options, “in” and “out”, to display the FECs filtered due to inbound and outbound FEC filters, respectively. When one of the upstream mapping for a FEC is filtered, it displays in this list as filtered.
2 Label withdrawal delay Total number of prefix FECs: 6 Total number of prefix FECs installed: 1 Total number of prefix FECs filtered (in/out): 2/2 Destination 192.168.1.1/32 192.168.1.2/32 192.168.1.3/32 192.168.1.4/32 State current current current current Brocade# show mpls ldp Total number of prefix Total number of prefix Total number of prefix Destination 192.168.1.1/32 192.168.1.2/32 Next-hop 10.23.23.12 10.23.23.12 10.23.23.12 10.23.23.
Label withdrawal delay 2 Upgrade to R05.5.00 If a system is upgraded to R05.5.00 from a release which does not support the label withdrawal delay feature, then the newly upgraded system will exhibit new behavior as label withdrawal delay is enabled by default in R05.5.00.
2 Label withdrawal delay Setting the secs variable to 0 disables the label withdrawal delay feature for subsequent events. Any FEC which has already started the label withdrawal delay timer continues to run the timer and to delay sending its label withdrawal messages upstream The [no] form of the command restores the default behavior.
LDP ECMP for transit LSR 2 When LDP-IGP synchronization is enabled, the IGP metric for the new link is temporarily advertised at a maximum value to force traffic to use an alternate route, if one is available. After all label mappings are received on the link, the IGP metric is adjusted on the link to the normal value and route updates may occur as the cost of the link has been reduced.
2 LDP ECMP for transit LSR the set of programmed paths. MPLS always sends the complete set of ECMP paths to the forwarding plane. When the user changes the load sharing configuration, updates are also sent to the forwarding plane. FEC updates are only generated when the new load sharing value is different from the set of ECMP paths programmed in the forwarding plane. NOTE LDP ECMP is not supported at the ingress router. The ingress LDP LSP can be different from the transit LSP for the same FEC.
LDP ECMP for transit LSR 2 Brocade# show mpls config router mpls policy no propagate-ttl ldp load-sharing 4 Syntax: show mpls config MPLS OAM support for LDP ECMP MPLS OAM support for traceroute at any transit router returns the list of labels used at that transit router. However, traceroute is not able to exercise all ECMP paths. The forwarding plane selects one ECMP path to forward OAM packets.
2 LDP ECMP for transit LSR Brocade# show mpls ldp fec prefix 10.11.11.11 FEC_CB: 0x362eee00, idx: 14, type: 2, pend_notif: None State: current, Ingr: Yes, Egr: No, UM Dist. done: Yes Prefix: 10.11.11.11/32 next_hop: 10.90.90.25, out_if: ve4 next_hop: 10.11.11.11, out_if: tunnelto12_3 next_hop: 10.11.11.11, out_if: tunnelto12 next_hop: 10.11.11.11, out_if: tunnelto12_2 Downstream mappings: Local LDP ID Peer LDP ID 10.128.128.28:0 10.11.11.11:0 10.128.128.28:0 10.125.125.
LDP ECMP LER 2 LDP ECMP LER Glossary TABLE 43 Glossary Term Meaning CAM Hardware Routing Table CAM2PRAM Indirection pointer to PRAM table, also has no ECMP paths ECMP Equal Cost Multi Path IPoMPLS IPv4 (shortcuts) over MPLS tunnels L3VPN Layer-3 VPN routes LER Label Edge Router PRAM Next-hop information table RTM RTM module on MP Overview The LDP ECMP LER feature provides the capability to create LDP tunnels with up to eight paths.
2 Commands 9. Ingress tunnel accounting is supported for LDP ECMP tunnels. Statistics for LDP ECMP tunnel aggregate traffic from all the individual paths. 10. LDP ECMP LER tunnels cannot use GRE or RSVP tunnel interfaces. Interactions with other features LDP ECMP tunnel accounting The show mpls statistics ldp tunnel command is used to retrieve statistics for particular LDP tunnel.
system-max ecmp-pram-block-size dec 2 system-max ecmp-pram-block-size dec A new option is introduced to the system-max command to control the max PRAM block allocation for ECMP routes. This setting affects the ECMP routes of type IPv4/IPv6/VPNv4/VPNv6. Using this command requires a system restart in order for the new setting to take effect. Syntax Command default Parameters system-max [ecmp-pram-block-size dec] None.
2 show mpls ldp tunnel show mpls ldp tunnel The output of the show mpls ldp tunnel command is updated to include all the paths in the LDP tunnel.The show mpls ldp tunnel command has a filter for the tunnel destination prefix, ‘brief’ and ‘detail’. The tunnel destination prefix can be either IPv4 host address or IPv4 prefix with subnet mask. Output of the command with the path destination prefix filter displays a single tunnel entry for a specified tunnel destination IP prefix.
show mpls ldp tunnel Output field status Outgoing interface Next-hop index Outgoing interface Next-hop index Example 2 Description The operational state of the LSP. This field indicates whether the LSP has been established through LDP signalling and is capable of having packets forwarded through it. The outbound interface for the LSP. The outbound interface displays the egress interface of the tunnel.
2 show mpls ldp tunnel Outgoing interface: e1/1, Next-hop index: 0 LDP tunnel tnl1, to 10.100.100.8/32 Tunnel index: 1, metric: 0, status: UP Outgoing interface: e1/1, Next-hop index: 0 Outgoing interface: e1/4, Next-hop index: 1 NOTE The next-hop index (exists currently in Multi-Service NetIron Release 05.500) refers to the NHT modules nexthop table index. It can be correlated through the show nht-table command output’s ‘Index’ column value.
show mpls forwarding [p2p] 2 show mpls forwarding [p2p] The show mpls forwarding [p2p] command option displays all P2P forwarding entries for the specified destination or a specified in-label value. Syntax Parameters show mpls forwarding [p2p {A.B.C.D|in-label}] p2p The p2p option displays all P2P forwarding entries for the specified destination or a specified in-label value. Modes Usage guidelines Command output Global configuration.
2 show mpls forwarding [p2p] 11 12 13 14 15 16 17 10.77.77.12/32 10.13.13.13/32 2055 2055 2055 2066 3 3 3 3 3 3 3 e2/1 e2/1 e2/2 e2/2 e3/8 e3/8 e1/1 L L L L L L R 10.22.22.12 10.22.22.12 10.92.92.12 10.92.92.12 10.34.34.12 10.34.34.12 10.24.24.13 History Related commands 340 Release Command history MultiService NetIron Release 05.600 The p2p option displays all P2P forwarding entries for the specified destination or a specified in-label value. None.
show mpls route 2 show mpls route The MPLS routing table is used to store routes to egress LERs. To display the contents of the MPLS routing table, enter the show mpls route command. Syntax Parameters show mpls route A.B.C.D A.B.C.D The A.B.C.D variable is the destination prefix. Modes Usage guidelines Command output Example Global configuration.
2 show mpls route 3 4 10.13.13.13/32 10.77.77.12/32 10.13.13.13 10.12.12.12 10.12.12.12 10.12.12.12 tnl4 tnl10 e1/1 e2/1 e2/2 e3/8 3 3 3 3 L L L L 0 0 0 0 0 0 0 0 History Release Command history MultiService NetIron Release 05.500c With LDP ECMP LER tunnels, the output for one tunnel could be greater than one line where each line shows one outgoing path. Related commands 342 None.
ping mpls ldp 2 ping mpls ldp The LDP LSP ping command, sends an MPLS echo request from the ingress to the egress LSR. A new option, nexthop ipv4-address has been added to the existing ping command. Syntax Command default Parameters ping mpls ldp ip-address | ip-address/mask-length[count 1-4294967294 [destination ip-addr] [detail][reply-mode no-reply|router-alert] [reply-tos 0-254][size bytes] [source ip addr] [timeout 50-300000 msec][nexthop ipv4 addr] None.
2 traceroute mpls ldp traceroute mpls ldp The LDP LSP traceroute command in the (enable) mode, sends and MPLS echo request from the ingress to the egress LSR.
Setting the LDP Hello Interval and Hold Timeout values 2 The source ip-address option specifies the IP address of any interface. This address is used as the destination address for the echo reply address. The default address is the LSR ID. timeout msec The timeout msec option specifies an interval in milliseconds for the echo request message. The default timeout is five seconds. The maximum timeout value is five minutes.
2 Setting the LDP Hello Interval and Hold Timeout values Setting the LDP Hello interval values The LDP hello interval controls how often the device sends out LDP Hello messages. Hello messages are used to maintain LDP sessions between the device and its LDP peers.
Setting the LDP Hello Interval and Hold Timeout values 2 Setting the LDP Hello Interval globally for targeted LDP sessions To modify the hello message interval for targeted LDP sessions to 20 seconds, enter the hello-interval target command. Brocade(config-mpls)# ldp Brocade(config-mpls-ldp)# hello-interval target 20 Syntax: [no] hello-interval target seconds The seconds variable specifies the value in seconds of the hello interval that the user is globally configuring for LDP Targeted messages.
2 Setting the LDP Hello Interval and Hold Timeout values The LDP Hold Time sent in Hello messages to adjacent LSRs can be configured globally for either Link or Targeted LDP sessions, as described in the following sections: • Setting the LDP Hello Hold Time Sent to Adjacent LSRs for Link LDP Sessions • Setting the LDP Hello Hold Time Sent to Adjacent LSRs for Targeted LDP Sessions Setting the LDP Hello hold time sent to adjacent LSRs for link LDP sessions To set the hold time included in LDP Link Hello
Setting the LDP Hello Interval and Hold Timeout values 2 • For targeted LDP sessions – The value received in Hello messages from its peers determines the time that the device waits for its LDP peers to send a Hello message. When the Timeout value received from a peer is zero, the Hold Time is set to the default period of 45 seconds. • For link LDP sessions – In this case, the wait time is determined by any one of the below criteria. 1. When the Hello Hold Time is set per-interface, that value is used.
2 Resetting LDP neighbors Brocade(config)# mpls Brocade(config-mpls)# ldp Brocade(config-mpls-ldp)# session 10.10.10.3 key early Syntax: [no] session remote-ip-addr key string The remote-ip-addr variable specifies the IP address of the LDP peer that authentication is being configured for. The string variable specifies a text string of up to 80 characters used for authentication between LDP peers. It must be configured on both peers. By default, key is encrypted.
Resetting LDP neighbors 2 When the all option is specified, all LDP sessions on the Brocade device is reset, including the targeted LDP sessions. An LDP session is uniquely referred to by peer-ip-addr: label-space. This command also allows the user to input peer-ip-addr only and ignore label-space. In this case, all LDP sessions with the matching peer address is reset.
2 MPLS LDP-IGP synchronization • Syslog logs the event of a LDP session going down and then coming back up, as a result of resetting the LDP session. Use the command show log to view the syslog events. Following is an example of how to use the show log command to view the syslog.
MPLS LDP-IGP synchronization 2 The MPLS LDP-IGP synchronization feature provides the following benefits: • • • • Provides a means to synchronize LDP and IGPs to minimize MPLS packet loss. MPLS LDP-IGP synchronization may be enabled per interface, or globally OSPF and IS-IS are supported for the IGP; each operates independently LDP determines convergence (receipt of all labels) for a link through one of two methods.
2 MPLS LDP-IGP synchronization • When enabled on IS-IS, the feature applies to both level-1 and level-2 metrics. • Affects IPv4 metrics only.
MPLS LDP-IGP synchronization 2 When hold down time is un-configured, the router stops the hold-down-timer on every interface that has hold-down-timer running at the time as if there is no hold down time configured. As a result, these interfaces have infinite hold down time. For those not-in-sync interfaces with hold-down time already expired, IGP continues to advertise Normal metric. By default, hold-down time is disabled.
2 MPLS LDP-IGP synchronization Setting the receive label silence timer When labels are not received from the peer for a short period of time, the session is declared ‘In Sync’. When a label is received from a peer, then the ‘receive label silence timer’ is reset. Use the rx-label-silence-time command under config-mpls-ldp policy to define the length of the receive label silence timer.
MPLS LDP-IGP synchronization 2 Brocade(conf-router-mpls-ldp-eol)# notification-timer Syntax: EOL notification timer value The value parameter specifies the length of the EOL notification timer in milliseconds. Possible values are from 100 to 120000 milliseconds. The default value is 60000. Setting the EOL transmit label silence timer Use the tx-label-silence-timer command under conf-router-mpls-ldp-eol policy to sets the length of the EOL transmit label silence timer. This command is LDP global.
2 MPLS LDP-IGP synchronization Use the show ip ospf command to displaying IS-IS LDP IGP synchronization information. Brocade# show ip ospf OSPF Version Version 2 Router Id 10.1.1.
MPLS LDP-IGP synchronization 2 Level-2 Metric: 10, Level-2 Priority: 64 Level-2 Hello Interval: 10 Level-2 Hello Multiplier: 3 Level-2 Designated IS: R2-03 Level-2 DIS Changes: 2 Next IS-IS LAN Level-1 Hello in 7 seconds Next IS-IS LAN Level-2 Hello in 3 seconds Number of active Level-1 adjacencies: 0 Number of active Level-2 adjacencies: 0 Circuit State Changes: 1 Circuit Adjacencies State Changes: 0 Rejected Adjacencies: 0 Circuit Authentication L1 failures: 0 Circuit Authentication L2 failures: 0 Bad L
2 MPLS LDP-IGP synchronization Graceful restart: enabled Peer reconnect time(msec): 120000, peer recovery time(msec): 0 State: not started IGP Sync: Unrecognized Notification Capability: Local: On, Remote: On Local State: In-sync, RemoteState: In-sync EOL notification time: 60000 ms, Timer not running EOL transmit label silence time: 1000 ms, Timer not running Syntax: show mpls ldp session value Use the show mpls ldp interface command to view whether or not LDP-IGP sync is enabled on the interface.
MPLS LDP-IGP synchronization 2 The router can also support LDP GR in helper-only mode. In this mode, a router does not preserve its forwarding entries on a LDP GR restart, however, it can help a neighboring router recover its forwarding entries when the neighbor is going through restart. A NetIron router implementing LDP GR can play one of the two roles: • A restarting LSR: An LSR that performs LDP restart.
2 MPLS LDP-IGP synchronization When the timer is not expired the LSR uses the labels and next-hop information received from the neighbor to lookup and clear the stale flag for the corresponding label-FEC entries. When the timer is expired, all the entries that are still marked as “stale” are deleted and the LDP GR procedure is completed.
MPLS LDP-IGP synchronization 2 Graceful restart scenarios Re-advertise label to its upstream neighbors When the restarting router, acting as a transit LSR, can recover a FEC based on the Label Mapping it receives from its GR helper, and the local forwarding state successfully, it re-advertises the same label to all of its upstream neighbors.
2 MPLS LDP-IGP synchronization Transit LSR specific processing For those LDP cross-connects that can be recovered as part of LDP GR, there is no traffic loss for those application using those tunnels if and only if the GR helper (example: downstream neighbor) re-advertises the same label and upstream neighbor also support LDP GR procedure as well.
MPLS LDP-IGP synchronization 2 The helper-only option specifies that the LSR acts as a helper-only. In helper mode, the configuration commands for reconnect-time and recovery-time is rejected with informational messages. The [no] form of the commands removes the LDP GR helper mode and revert back to full LDP GR mode. The reconnect-time seconds option is the amount of time a GR neighbor must wait for the LDP session to be reestablished.
2 MPLS LDP-IGP synchronization LDP Session keepalive timeout configurations After an LDP session is established, an LSR maintains the integrity of the session by sending Keepalive messages. The Keepalive timer for each peer session resets whenever it receives any LDP protocol message or a Keepalive message on that session. When the Keepalive timer expires, LDP concludes that the TCP connection is bad or the peer is dead and terminates the session.
MPLS LDP-IGP synchronization Brocade(config-mpls-ldp)# ka-interval 11 Warning : LDP Session keepalive time changed. take effect on existing sessions Brocade(config-mpls-ldp)# ka-timeout 40 Error : Please unconfigure ka-interval before Brocade(config-mpls-ldp)# Brocade(config-mpls-ldp)# no ka-interval 11 Warning : LDP Session keepalive time changed. take effect on existing sessions Brocade(config-mpls-ldp)# Brocade(config-mpls-ldp)# ka-timeout 40 Warning : LDP Session keepalive time changed.
2 Configurable LDP router ID overview Configurable LDP router ID overview LDP protocol uses LDP messages to communicate between LDP peers for correct functioning of LDP protocol. All LDP messages contains a LDP header which is composed of LDP version, length of message, LDP ID, followed by message. The LDP ID for LDP protocol is composed of LSR-ID and label space. A valid IP address is selected as an LSR-ID field. Through NetIron Release 05.
Configurable LDP router ID overview 2 The LDP protocol uses the new IP address specified by feature as LSR-ID only when this IP address is configured on one of the enabled loopback interfaces. When this IP address is not configured in enabled state on any of the loopback interface, LDP protocol will continues in the disabled state. LDP protocol will be enabled as soon as this IP address is configured on one of the enabled loopback interfaces.
2 LDP over RSVP (for transit LSR only) 9. a) Precondition: LDP protocol is disabled and the feature is configured. b) Action: The feature is disabled. c) Post condition: An attempt is made to restart the LDP protocol. Because the attempt is made after disabling the feature, LSR-ID is selected with the default behavior and the LDP protocol is enabled. Limitations • You can not configure value 0.0.0.0. If you try to configure the feature with this value, the feature rejects the configuration.
LDP over RSVP (for transit LSR only) 2 • The RSVP tunnel must be enabled for LDP tunneling. For more information on enabling LDP tunneling, refer to “Enabling LDP over RSVP”. NOTE When an RSVP tunnel is created on ingress LSR with IS-IS or OSPF shortcuts enabled, and LDP tunneling is also enabled, then the LDP tunnel to the egress router of the RSVP tunnel is not formed. An LDP tunnel is not created at the ingress LSR when RTM selects the RSVP tunnel as the next-hop to the destination.
2 LDP over RSVP (for transit LSR only) By default, LDP tunneling is disabled. The user must disable the LSP configuration to change the setting on the ldp-tunneling command. NOTE The ldp-tunneling command is not available under bypass LSP configuration. To disable IS-IS shortcuts or OSPF shortcuts, enter the [no] form of the command. The level1 or level2 keyword is required and indicates the level of IS-IS routing enabled on the device.
LDP over RSVP (for transit LSR only) 2 Brocade# show mpls config router mpls policy traffic-eng isis level-2 ingress-tunnel-accounting ldp label-withdrawal-delay 30 session 10.7.7.2 key 2 $LSFVPW9iIQ== session 10.7.7.
2 LDP over RSVP (for transit LSR only) Syntax: show mpls ldp targeted-peer TTL propagation for LDP over RSVP packets TTL propagation for LDP over RSVP packets is controlled by the propagate-ttl command, and the label-propagate-ttl command: • When the label operation involves the swap of the LDP label followed by the push of the RSVP label, the label-propagate-ttl command controls the propagation of the LDP label TTL to the RSVP label TTL. By default, the TTL is not propagated.
LDP over RSVP (for transit LSR only) 2 Enabling TTL propagation By default, MPLS traceroute does not display the LSRs the RSVP tunnel is transiting through, except when the egress router is acting as the egress for both the LDP and the RSVP tunnel. In other words, the RSVP tunnel is treated as a single hop. The label-propagate-ttl command and the propagate-ttl command must be enabled in order to display details of the RSVP core. By default, the propagate-ttl command is enabled.
2 RSVP-TE Hello Brocade(config-mpls)# policy Brocade(config-mpls-policy)# backup-retry-time 100 Syntax: [no] backup-retry-time interval The interval parameter valid range is: [10 - 600] seconds. Use the [no] form of this command to revert to the default of 30 seconds.
RSVP-TE Hello 2 Vital Fractions for RSVP-TE Hello The Hello extension is composed of three parts: • Hello Message • Hello REQUEST object • Hello ACK object Each neighbor can individually issue Hello REQUEST objects. Each request may be answered by an Hello ACK object. The Hello extension is designed so that one side can use the mechanism while the other side does not. All messages may be ignored by nodes which do not wish to participate in Hello message processing.
2 RSVP-TE Hello 14. On receipt of a message containing a HELLO ACK object, the receiver must verify that the neighbor has not reset. This is done by comparing the sender's ‘Src_Instance’ field value with the previously received value. If the Neighbor_Src_Instance value is zero, and the ‘Src_Instance’ field is non-zero, the Neighbor_Src_Instance is updated with the new value. If the value differs or the ‘Src_Instance’ field is zero, then the node must treat the neighbor as if communication has been lost.
RSVP-TE Hello 2 Removing Hello support from one end of the link Consider the case when both ends of the link supported RSVP-TE Hello messages and the exchange of messages was normal as both links were up. Remove the support for Hello from one side of the link. The other side keeps sending Hello Request messages, but the neighbor starts ignoring these requests as it no longer wishes to participate in Hello messages exchange.
2 Commands Commands The following commands support this feature: • • • • • • • • • 380 rsvp-hello rsvp-hello acknowledgements rsvp-hello disable show mpls config show mpls config rsvp show mpls rsvp interface detail show mpls rsvp neighbor clear mpls statistics rsvp neighbor show mpls rsvp statistics Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
rsvp-hello 2 rsvp-hello This configures RSVP-TE Hello with default values on all the mpls-interfaces provided the mpls-interface does not have any local interface level configuration for the same. Interface level configuration takes precedence over global configuration. RSVP hello configuration at the global MPLS RSVP level Interval and tolerance for RSVP-TE Hello protocol can be configured at global MPLS RSVP level.
2 rsvp-hello [no] rsvp-hello acknowledgements Parameters acknowledgements The acknowledgements option acknowledges RSVP Hellos on interfaces not having RSVP sessions. interval The interval option is the interval between two RSVP Hello requests. The default is nine seconds and the range is 1 - 60 seconds. tolerance The tolerance option is the number of unacknowledged RSVP Hello requests before time-out specified by the dec variable. The default is 3 and the range is 1 - 255.
rsvp-hello disable 2 rsvp-hello disable Disables RSVP Hello on an mpls-interface. The [no] function of this command enables RSVP-TE Hello on the mpls-interface where it is executed. Syntax Parameters [no] rsvp-hello disable disable Disables RSVP-TE Hello protocol on this interface. Command modes Usage guidelines This command operates at MPLS interface configuration mode.
2 rsvp-hello acknowledgements rsvp-hello acknowledgements The rsvp-hello acknowledgements command configures the RSVP-TE Hello to respond back with Hello ACKs to neighbors not carrying any RSVP sessions. The configuring for acknowledgements is at the global MPLS RSVP level. The [no] format of this command sets it back to the default behavior of not sending ACKs to neighbors not carrying any RSVP sessions. This erases the configuration line from the global configuration.
show mpls rsvp neighbor 2 show mpls rsvp neighbor The show mpls rsvp neighbor command displays RSVP neighbors that were discovered dynamically during the exchange of RSVP packets. The RR and MsgID flags in this command show the ability of the neighbor to support Refresh Reduction and Message IDs respectively. The ‘MsgID’ field is set to YES in the following cases: • This field is defaulted to YES initially. • It is set to YES if the neighbor sends a message containing a Message ID.
2 show mpls rsvp neighbor Field name Description Hello-interval Hello-tolerance Hello-interval - Frequency at which RSVP-TE Hello Request messages are sent on the interface in seconds Hello-tolerance - The number of hello periods which may pass without receiving a complete Hello message before the Hello session times out. (Detail mode only.) Hello Tx/Rx Count Number of Hello packets sent to or received from the neighbor.
show mpls rsvp neighbor Related commands 2 None.
2 clear mpls statistics rsvp neighbor clear mpls statistics rsvp neighbor The clear mpls statistics rsvp neighbor command clears the statistics for RSVP neighbors that were discovered dynamically during the exchange of RSVP packets. This clears the counters for RSVP Hello packets transmitted and received for this neighbor which are displayed in the show mpls rsvp neighbor command. This does not clear the counters from show mpls rsvp statistics command OR the show mpls rsvp interface detail command.
clear mpls statistics rsvp neighbor 10.152.152.15 10.92.98.9 10.92.95.9 10.92.99.9 e1/2 e1/12 e4/1 e3/2 UP UP DOWN UP 10:2:31:44 0:6:39:36 6:6:39:36 0:0:31:44 0/0 0/0 0/0 0/0 2 Y/Y N/Y N/Y N/N History Release Command history Multi-Service NetIron Release 05.6.00 This command was introduced. Related commands None.
2 show mpls config rsvp show mpls config rsvp The show mpls config rsvp command displays all RSVP global configurations. Syntax Parameters Modes Example show mpls con fig rsvp None. This command operates in all modes. Brocade# show mpls config rsvp rsvp refresh-interval 80 refresh-multiple 10 rsvp-hello interval 20 tolerance 3 History Release Command history Multi-Service NetIron Release 05.6.00 This command was introduced. Related commands 390 None.
show mpls rsvp statistics 2 show mpls rsvp statistics This command displays the RSVP control packet statistics combined over all the interfaces. Syntax Parameters Modes Usage guidelines show mpls rsvp statistics None. This command operates in all modes. clear mpls rsvp statistics clears the ‘Since last clear’ column for the Harlequins and Hillock added packet types. Command output Description Packet Type: Path The number of Path messages sent and received.
2 show mpls rsvp statistics Description Rev MD5 Auth Errors The number of MD5 authentication errors on received packets on the interface. PATH state timeout The PATH timeout. RESV state timeout The reservation confirmation timeout. Pkt. with MsgId drop Number of packets with dropped message ID’s. Pkt. with SRef drop Number of packets with dropped Rcv pkt processing error: Example Path The number of Path messages received with a packet processing error.
show mpls rsvp statistics RESV state timeout 1 Pkt with MsgId drop 0 Pkt with SRef drop 0 Rcv pkt processing error: Path 13700 Resv 4 PathErr 0 ResvErr 0 PathTear 0 ResvTear 0 ResvConf 0 Bundle 0 Ack 0 SumRefresh 0 Hello 33 2 1 0 0 13700 4 0 0 0 0 0 0 0 0 8 History Release Command history Multi-Service NetIron Release 05.6.00 This command displays the RSVP control packet statistics combined over all the interfaces. Added one packet type Hello.
2 show mpls rsvp interface detail show mpls rsvp interface detail Use the show mpls rsvp interface detail command to view a details about each configured interface. This command displays the RSVP control packet statistics on a per interface basis. One new packet types, Hello, is added in the Multi-Service NetIron Release 05.6.00. Syntax Parameters Command modes Usage guidelines Command output Example show mpls rsvp interface detail None. This command operates in all modes.
show mpls rsvp interface detail SumRefresh Hello Nack Object 16 821 0 0 221 0 11 743 0 2 0 111 0 Active BIs: 0 Inactive BIs: 0 Errors Total Rcv MD5 Auth Errors 0 Pkt with MsgId drop 0 Pkt with SRef drop 0 Duplicate preempt dropped 0 Since last clear 0 0 0 P2MP Capable : Yes When Hello is not operational.
2 show mpls rsvp interface detail History Release Command history Multi-Service NetIron Release 05.6.00 This command displays the RSVP control packet statistics on a per interface basis. Added one packet, Hello The clear mpls rsvp statistics command clears the ‘since last clear’ column for the above newly added packet type. Related commands 396 None.
show mpls config 2 show mpls config The show mpls config command displays the MPLS configuration on the router.
2 show mpls config The vpls option lets the user limit the display to configuration information for the VLL specified by vpls_name variable. bypass-lsp The bypass-lsp option lets the user limit the display to information for the bypass LSP specified by bypass_name variable. Modes Usage guidelines Command output This command operates in all modes. When an option is used without a variable specified, the configuration parameters for the option are shown for all elements that match the option are displayed.
show mpls config 2 end of MPLS configuration Output 3: Hello configuration with non-default configuration on interface ethernet 1/12 and with configuration of hello-acknowledgements and non-default configuration at rsvp global level. And RSVP Hello disabled on the interface ethernet 1/12.
2 Displaying LDP information Displaying LDP information The user can display the following information about LDP: • • • • • • • The LDP version number and the LSPs LDP identifier and loopback number Information about active LDP-created LSPs on the device Information about LDP-created tunnel LSPs for which this device is the ingress LER LDP database content Information about the LDP session between this LSR and its LDP peers Information about the connection between this LSR and its LDP peers Information
Displaying LDP information TABLE 47 2 Output from the show mpls ldp command (Continued) This field... Displays... Hold time multiple The number of Keepalive messages not received before a session is declared down. Graceful restart The show GR setting and the status of the forwarding state hold timer is provided with the remaining time when it is running.
2 Displaying LDP information TABLE 48 Output from the show mpls ldp path command This field... Displays... Upstr-session(label) The LDP identifier of the upstream peer, as well as the incoming label. Note that upstream session information does not apply to LSPs for which this is the ingress LER. Because the device uses a per-platform label space, the incoming interface for LDP-created LSP is not relevant.
Displaying LDP information Brocade# show mpls ldp tunnel Total number of LDP tunnels : 3 Oper Tunnel To State Intf 10.22.22.22/32 UP tnl2 10.33.33.33/32 UP tnl3 10.44.44.44/32 UP tnl4 Outbound Intf e2/3 e3/3 (Trunk11) e2/3 (Trunk11) ve55 Brocade# show mpls ldp tunnel brief Total number of LDP tunnels : 3 Oper Tunnel To State Intf 10.22.22.22/32 UP tnl2 10.33.33.33/32 UP tnl3 10.44.44.44/32 UP tnl4 Outbound Intf e2/3 (Trunk11) e2/3 (Trunk11) ve55 2 Brocade# show mpls ldp tunnel 10.22.22.
2 Displaying LDP information TABLE 49 Output from the show mpls ldp tunnel command (Continued) This field... Displays... Metric Metric value for the tunnel. Next-hop index Index of the next hop used for this tunnel. Displaying the contents of the LDP database The show mpls ldp database command has been enhanced to have a filter for peer address. The peer address is the IPv4 address of the LDP Peer of an LDP Session.
Displaying LDP information TABLE 50 2 Output from the show mpls ldp database command (Continued) This field... Displays... Prefix The destination route associated with the label. Since Prefix is not applicable to the VC-FECs, this field indicates that the label is associated with the VC FEC. State Whether the label is actively being used for data forwarding. This can be one of the following “Installed” indicates that the label is being used with an active LDP-created LSP to forward packets.
2 Displaying LDP information Brocade# show mpls ldp session 10.11.11.1 Peer LDP ID: 10.11.11.1:0, Local LDP ID: 10.22.22.2:0, State: Operational Adj: Link, Role: Active, Next keepalive: 0 sec, Hold time left: 30 sec Keepalive interval: 6 sec, Max hold time: 36 sec Up time: 56 sec Neighboring interfaces: (targeted), e1/1 TCP connection: 10.22.22.2:9001--10.11.11.1:646, State: ESTABLISHED Next-hop addresses received from the peer: 10.9.1.1 10.10.1.1 10.11.11.1 10.11.11.
Displaying LDP information 2 For a router in helper-only mode, Up time indicates the time since the session was brought up after the peer has restarted. The show mpls ldp session command output has been enhanced to display the total number of link and targeted sessions in operational state. The following table describes the output of the show mpls ldp session command. TABLE 51 Output from the show mpls ldp session command This field... Displays... Peer LDP ID The LDP identifier of the peer LSR.
2 Displaying LDP information NOTE The key displayed using the command, show mpls ldp session detail is the one configured for that session. This key may not be the one which is “in use” by that session as the session may have been established prior to the change in the configured key. When the session is already in the established state, any change in the authentication key takes effect during the next incarnation of the LDP session.
Displaying LDP information TABLE 52 2 Output from the show mpls ldp session detail command (Continued) This field... Displays... State The state of the TCP connection between the peers. Next-hop addresses received from the peer The next-hop addresses received from the peer in LDP address messages. The LSR uses this list of addresses to determine whether the peer is the correct next hop for a destination route.
2 Displaying LDP information TABLE 53 410 Output from the show mpls ldp neighbor command (Continued) This field... Displays... Time Left The amount of time, in seconds, before the LDP neighbor times out when no Hello message is received from the neighbor. Up Time The Up Time is the time since the LDP adjacency is established. It is displayed in days, hours, minutes, and seconds. When there is no Adjacency, then nothing is displayed.
Displaying LDP information 2 Displaying information about LDP-enabled interfaces To display information about the LDP-enabled interfaces on the LSR, enter the show mpls ldp interface command. Brocade# show mpls ldp interface Label-space Interface ID e4/1 0 (targeted) 0 Nbr Count 1 0 Hello Interval 5 15 Next Hello 0 sec -- Syntax: show mpls ldp interface TABLE 54 Output from the show mpls ldp interface command This field... Displays...
2 Displaying LDP information TABLE 55 Output from the show mpls ldp interface command for a specific interface This field... Displays... Interface The slot and port number of the LDP-connected interface. The interface type refers to any one of the following: • ethernet slot/port to limit the display to a single ethernet port • ve vid to limit the display to a VE interface ID specified by the vid variable. Label-space ID The label space ID.
Displaying LDP information TABLE 56 2 Output from the show mpls ldp peer command (Continued) This field... Displays... Num-VLL Number of VLL instances using this LDP peer. Num-VPLS-Peer Number of VPLS instances using this LDP peer. To display more detailed information about the LDP peers, enter the following command. Brocade# show mpls ldp peer detail Peer LDP ID: 10.2.2.2:0, Local LDP ID: 10.1.1.
2 Displaying LDP information To display detailed information about a specific LDP peer, enter the following command. Brocade# show mpls ldp peer 10.22.22.22 Peer LDP ID: 10.22.22.22:0, Local LDP ID: 10.24.24.24:0, State: Operational Session Status UP, Entity Idx: 1, Targeted: No, Target Adj Added: No Num VLL: 0, Num VPLS: 0 Rcvd VC-FECs: From 10.5.5.5: Label: 100000, VC Id: 10, Grp_Id: 0, VC Type: 32773, MTU: 5000 From 10.5.5.
Displaying LDP information 2 Displaying LDP FEC information To display host addresses and the total number of Layer 3 prefix FECs from the LDP FEC database, enter the following command. Brocade# show mpls ldp fec prefix Total number of prefix FECs: 2 Destination State Out-intf 10.125.125.1/32 current e2/2 10.128.128.0/24 current -- Next-hop 10.90.90.
2 Displaying LDP information TABLE 60 Output from the show mpls ldp fec prefix command This field... Displays... FEC_CB Memory address of the FEC CB. idx A monotonically increasing number assigned to each FEC in the LDP internal FEC tree. type FEC type – Prefix FEC is type 2 and Host Address is assigned type 3. pend_notif Any notification pending on this FEC. State State of the FEC which indicates the FEC advertised to any LDP session (state equal to “current”).
Displaying LDP information TABLE 61 2 Output from the show mpls ldp fec summary command This field... Displays... LDP FEC summary Summarized information for LDP FEC. Total number of prefix FECs The total number of prefix FECs in the LDP FEC database. Total number of VC-FEC type 128 The total number of VC FECs for type 128. The FEC type for VC FEC can be 128 or 129. Total number of VC-FEC TYPE 129 The total number of VC FECs for type 129. The FEC type for VC FEC can be 128 or 129.
2 Displaying LDP information TABLE 62 Output from the show mpls ldp fec vc command This field... Displays... Total number of VC FECs The total number of VC FECs. Peer LDP ID The remote LDP ID of the peer (or local LSR) where this VC FEC is originated from. State The state of the FEC which indicates the FEC advertised to any LDP session (state equal to “current”).
Displaying LDP information 2 Brocade# show mpls ldp fec vc 100 FEC_CB: 0x29391510, idx: 6, type: 128, pend_notif: None State: current, Ingr: Yes, Egr: Yes, UM Dist. done: Yes VC-Id: 100, vc-type: 4, grp-id: 0 Local-mtu: 1500, remote-mtu: 1500, MTU enforcement: enabled Downstream mappings: Local LDP ID Peer LDP ID 10.128.128.28:0 10.125.125.1:0 Label 800000 State CB Installed 0x29391328(-1) Upstream mappings: Local LDP ID 10.128.128.28:0 Label 800003 CB 0x2939141c(-1) Peer LDP ID 10.125.125.
2 Displaying LDP information TABLE 63 Output from the show mpls ldp fec command (Continued) This field... Displays... Local LDP ID Local LDP ID of the LDP session to which this upstream mapping CB belongs. Peer LDP ID Remote LDP ID of the LDP session to which this upstream mapping CB belongs. Label MPLS label advertised to the upstream LDP LSR. CB Memory address of the upstream mapping CB.
Displaying LDP information 2 The following example displays a VC type mismatch where two VC FEC_CBs are displayed for the same VC ID of 1000. In the example, the user can see that one VC type displays 5, and the other VC type displays 11. The two VC FEC_CBs are not associated with each other in any way. The VC type mismatch causes the VC label to display a Retained state instead of an Installed state.
2 Displaying LDP information Displaying the LDP packet statistics The user can display a packet statistics for packet types and packet errors, as shown in the following.
Sample LDP configurations TABLE 64 2 Output from the show mpls ldp statistics command (Continued) This field... Displays... Total The number of the errors of the Type described for the row, generated since the Brocade device came up. Since Last Clear The number of the errors of the Type described for the row, generated since the last time a clear command was issued. Clearing the LDP packet statistics The user can clear the LDP Packet Statistics, as shown in the following commands.
2 Sample LDP configurations R1(config)# router mpls R1(config-mpls)# mpls-interface e 2/10 R1(config-mpls)# ldp-enable R1(config-mpls)# mpls-interface e 2/20 R1(config-mpls)# ldp-enable R1(config-mpls)# exit R1(config)# ip route 10.2.2.2/32 10.1.1.2 R1(config)# ip route 10.3.3.3/32 10.1.1.2 R1(config)# route-only R1(config)# interface ethernet 2/10 R1(config-if-2/10)# enable R1(config-if-2/10)# ip address 10.1.1.
Sample LDP configuration with VLL 2 Sample LDP configuration with VLL Figure 49 illustrates a sample Virtual Leased Line (VLL) configuration that uses LDP tunnel LSPs. FIGURE 49 MPLS VLL configuration with LDP tunnel LSPs In this example, routers R1 and R3 are Provider Edge (PE) routers configured as VLL peers. R1 and R3 have established a targeted LDP session to exchange VLL label information.
2 Sample LDP configuration with VLL R1(config-mpls)# interface loopback 1 R1(config-lbif-1)# port-name Generic All-Purpose Loopback R1(config-lbif-1)# ip address 192.168.2.100/32 R1(config-lbif-1)# ip ospf area 0 R1(config-lbif-1)# exit R1(config)# router mpls R1(config-mpls)# mpls-interface e 2/1 R1(config-mpls)# ldp-enable R1(config-mpls)# exit R1(config-mpls)# vll VLL_to_R3 40000 R1(config-mpls-vll)# vll-peer 192.168.2.
MPLS over GRE tunnel 2 Router R3 The following commands configure Router R3 in Figure 49. R3(config-mpls)# interface loopback 1 R3(config-lbif-1)# port-name Generic All-Purpose Loopback R3(config-lbif-1)# ip address 192.168.2.102/32 R3(config-lbif-1)# ip ospf area 0 R3(config-lbif-1)# exit R3(config)# router mpls R3(config-mpls)# mpls-interface e 2/1 R3(config-mpls)# ldp-enable R3(config-mpls)# exit R3(config-mpls)# vll VLL_to_R1 40000 R3(config-mpls-vll)# vll-peer 192.168.2.
2 MPLS over GRE tunnel NOTE Do not forward packets from one type of tunnel to another type of tunnel in XPP. Packets may not be routed properly. NOTE MP switchover event may not be handled properly by MPLS or RSVP module. This may result in inconsistent state for RSVP LSPs sessions. This could be fixed by adding support for RSVP Hello feature. LDP LSP over GRE tunnel This feature works when a GRE tunnel connects two LDP LSP transit nodes and all LDP sessions establish with each peer.
MPLS over GRE tunnel 2 When multiple GRE tunnels exist between two nodes with LDP enabled on them, multiple LDP hello adjacencies establish between those nodes. Even though multiple hello adjacencies form, each LDP session is based an LSR-ID, so only one session is maintained between those two nodes. This scenario is treated the same as multiple links between two nodes with LDP enabled on them.
2 MPLS over GRE tunnel LDP over a GRE tunnel within an encrypted network Figure 52 shows an implementation of LDP/MPLS over GRE over an encrypted network. Traffic is forced through a non-MPLS network because of the mandatory encrypted network that traffic must cross. Customer equipment (CE) is connected to PE1 and PE2. PE1 and PE2 negotiate VPLS labels, and an LDP tunnel is created between PE1 and PE2. MPLS traffic is not supported between P1 and P2.
MPLS over GRE tunnel 2 Configuration example To configure MPLS over a GRE tunnel, first enable an interface as an MPLS interface, and then configure the MPLS tunnel and enable LDP.
2 MPLS over GRE tunnel router ospf area 0 interface loopback 1 enable ip ospf area 0 ip address 10.1.1.1/32 interface ethernet 1/1 enable ip ospf area 0 ip address 10.11.11.1/24 router mpls mpls-interface e1/1 ldp-enable Router B configuration Router B is the LDP LSP transit router and the GRE tunnel ingress router. The user needs to configure an OSPF routing instance. Next, the user configures the loopback address, the Ethernet interface, and then the GRE tunnel.
MPLS over GRE tunnel 2 interface loopback 1 enable ip ospf area 0 ip address 10.3.3.3/32 interface ethernet 1/1 enable ip ospf area 0 ip address 10.22.22.2/24 interface ethernet 1/2 enable ip ospf area 0 ip address 10.33.33.1/24 interface tunnel 200 tunnel mode gre ip tunnel source 10.3.3.3 tunnel destination 10.2.2.2 ip ospf are 10.80.80.2/24 router mpls mpls-interface e1/2 ldp-enable mpls-interface tunnel 200 ldp-enable Router D configuration Router D is the LDP LSP egress router.
2 MPLS over GRE tunnel gre-tnl200 Admin: Up Oper: Up Syntax: show mpls interface tunnel tunnel-id NOTE Traffic parameters do not apply to GRE. The user can view the LDP tunnel interface configuration information, such as the hello interval and timeout, by entering the mpls ldp interface tunnel command. The user can include a tunnel ID to retrieve specific information.
Commands 2 Brocade# show mpls ldp path Destination route Upstr-session(label) 10.2.2.2/32 10.1.1.1:0(3) 10.1.1.1/32 10.1.1.1:0(3, e1/1) 10.3.3.3/32 10.3.3.3:0(5050) 10.1.1.1:0(3, e1/2) 10.4.4.4:0(2057,gre-tnl200) Brocade# show mpls ldp path 10.22.22.22 Destination route Upstr-session(label) 10.22.22.22/32 10.44.44.44:0(1024) Downstr-session(label, intf) 10.22.22.22:0(3, e2/3 (Trunk11) Downstr-session(label, intf) Brocade# show mpls ldp path 10.33.33.33/32 Destination route Upstr-session(label) 10.33.
2 Commands • lsr-id A.B.C.
label-withdrawal-delay 2 label-withdrawal-delay Delays sending a label withdrawal message for a FEC to a neighbor. in order to allow the IGP and LDP to converge. The no form of this command restores the default behavior. Syntax label-withdrawal-delay secs no label-withdrawal-delay secs Command Default Parameters The label withdrawal delay timer is enabled. The delay period is 60 seconds. secs Specifies the delay period for the label withdrawal delay timer in seconds. The range is 0 - 300.
2 lsr-id A.B.C.D lsr-id A.B.C.D The lsr-id A.B.C.D command enables the feature and sets your configured IP address for the feature. The [no] form of the command reverts the LSR-ID selection process back to the default behavior, which is the current implementation. Syntax Command default Parameters lsr-id A.B.C.D [no] lsr-id A.B.C.D A.B.C.D This is the value set by you to be used as LSR-ID for LDP protocol.
ldp enable 2 ldp enable When the feature is disabled, the output of the command continues to be as it is in the 5.40 release implementation. In this case, the feature is configured and LDP is down because the LSR-ID configured is not available on any loopback interface. The output of the command informs you that the LDP is not initialized and LSR-ID is configured by you. The [no] option removes LDP on an MPLS interface, including LDP on an MPLS VE interface. Syntax [no] ldp-enable Command default None.
2 show mpls config show mpls config Displays mpls configuration information. Syntax Parameters Command Modes show mpls config None User EXEC mode Privileged EXEC mode Global configuration mode Examples The following example displays the mpls configuration: Brocade# show mpls config router mpls policy traffic-eng isis level-2 ingress-tunnel-accounting ldp label-withdrawal-delay 30 session 10.7.7.2 key 2 $LSFVPW9iIQ== session 10.7.7.
show mpls ldp 2 show mpls ldp Displays the inbound FEC-filter configuration. Syntax Parameters Command Modes show mpls ldp None User EXEC mode Privileged EXEC mode Global configuration mode Command Output The show mpls ldp command displays the following information: Output field Description Label Distribution Protocol version The LDP version. LSR ID The identifier of the device and the loopback interface number the LDP uses.
2 show mpls ldp Examples The following example displays the inbound FEC-filter configuration: Brocade# show mpls ldp Label Distribution Protocol version 1 LSR ID: 10.122.122.
show mpls ldp fec prefix 2 show mpls ldp fec prefix Displays prefix FEC information from the LDP FEC database. Syntax Parameters show mpls ldp fec prefix [{IPaddress|IPaddress/mask-length}] IPaddress (Optionalepilepsiespecifies the display of L3 FEC information for a specific FEC IP address. IPaddress/mask-length (Optional) Specifies the display of L3 FEC information for a specific IP address and subnet mask length.
2 show mpls ldp fec prefix Examples Output field Description Egr Whether the FEC is an egress FEC. UM Dist Specifies when Upstream Mapping Distribution is complete. Prefix The IP Prefix associated with the host address or the prefix FEC type. Label Withdrawal Delay Label withdrawal delay state. Time Remaining Time remaining on the label withdrawal delay timer in seconds. next_hop For an ingress FEC, this mentions the next- hop IP address.
show mpls ldp fec prefix Related Commands 2 None.
2 show run show run The show run command shows the configuration of the feature with the configured IP address when it is enabled. Syntax show run Command default None. Parameters None. Modes Command output Example User EXEC mode. Output field Description run Displays the current running configuration. Brocade# show run router mpls policy traffic-eng ospf ldp lsr-id 10.2.2.2 mpls-interface e1/1 enable interface e1/2 enable lsp 2 to 10.20.20.20 enable vpls vpls 1 vpls-peer 10.2.2.
show run Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 2 447
2 448 show run Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Chapter 3 Configuring MPLS Virtual Private LAN Services Overview This chapter explains how to configure Virtual Private LAN Services (VPLS). VPLS is a method for carrying Layer 2 frames between customer edge (CE) devices across an MPLS domain. The implementation supports VPLS as described in the IETF RFC 4762 (Virtual Private LAN Services over MPLS Using LDP Signaling). NOTE VPLS endpoints can be configured on a Foundry Discovery Protocol (FDP) enabled interface.
3 How VPLS works TABLE 65 Supported Virtual Private LAN Services (VPLS) features (Continued) Feature supported Brocade Brocade NetIron MLX XMR Series Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package VPLS Raw Pass Through Mode Yes Yes Yes Yes Yes Yes Yes VPLS CPU Protection Yes Yes No No
How VPLS works 3 VPLS can be used to transport Ethernet frames to and from multiple, geographically dispersed sites belonging to a customer Virtual Private Network (VPN). The Provider Edge (PE) devices connecting the customer sites provide functions similar to a Layer 2 switch.
3 How VPLS works A PE device in the VPLS configuration operates like a standard Layer 2 switch, in that it performs MAC address learning, flooding, and forwarding for the CE devices in each VPLS instance. For example, when PE device R1 receives a Layer 2 frame with a given MAC destination address from Customer A’s CE device, it looks up the MAC address in a Layer 2 forwarding table that records associations between MAC addresses and VC LSPs. This forwarding table is known as the VPLS MAC database.
Configuring VPLS instances 3 NOTE On Brocade NetIron CES and Brocade NetIron CER devices, the route-only command must not be configured on untagged MPLS uplinks when using it for VPLS or VLL. Otherwise, incoming VPLS or VLL traffic is dropped. NOTE The Brocade NetIron CES and NetIron CER devices can only support 127 endpoints + peers in a VPLS instance. Configuring VPLS instances This section explains how to set up VPLS instances.
3 Configuring VPLS instances Creating a VPLS instance The user creates a VPLS instance by entering VPLS configuration statements on two or more PE routers. The endpoints of a VPLS instance are associated by having the same VPLS Virtual Circuit Identifier (VCID) on each PE router. To create a VPLS instance, enter commands such as the following.
Configuring VPLS instances 3 Syntax: vpls name / vpls-vcid [cos cos-value] [max-mac max-mac-entries] The name variable is the name of the VPLS instance for which the user is configuring the maximum number of MAC entries. The vpls-vcid variable is the VPLS ID number of the VPLS instance for which the user is configuring the maximum number of MAC entries. The vpls-vcid variable can take a value in the range of one through 4294967294.
3 Configuring VPLS instances • ON CCEP ports, MAC withdrawal messages are sent only when both local and remote links of the CCEP goes down. • On a MCT standby switch, the LDP MAC withdrawal messages are sent to the active switch on MCT spoke PW and the MCT active switch relays the LDP messages to all the active PWs.
Configuring VPLS instances 3 The name name parameter clears all entries associated with the named VPLS instance. The id vpls-vcid parameter clears all entries associated with the specified VPLS VCID. The ethernet portnum parameter clears all local MAC entries on the specified port. The label label parameter clears all entries associated with a local VC label.
3 Configuring VPLS instances By default, each PE router attempts to initiate an LDP session through extended discovery with its VPLS peers, when a session is not already established. Each VPLS instance is allocated a range of 32 labels. The PE router assigns one label in the range to each of its peers to be used as the peer’s local VC label. When there are more than 32 peers in the VPLS instance, an additional label range is automatically allocated to the VPLS instance.
Configuring VPLS instances 3 Table 66 describes the expected Class of Service (CoS) behavior for VPLS packets when VPLS raw mode is in effect.
3 Configuring VPLS instances Single tag to single tag packet tag handling into or from the MPLS uplink with raw-pass-through mode with ports configured as untagged. Using the raw pass through option enables the user to configure the VC mode to interoperate between third party devices. The raw pass through option allows the user to: 1. Select the raw-pass-through mode which behaves like a tagged mode when all endpoints are configured as tagged endpoints. 2.
Configuring VPLS instances FIGURE 54 3 Sample configuration Interoperability with third party devices This section assumes that the user understands how QoS works. Third party device to Brocade device Table 66 describes the expected Class of Service (CoS) behavior for VPLS packets when VPLS raw pass through mode is in effect.
3 Configuring VPLS instances Legend for Table 66 W = Mapped CoS from internal priority (Z contributes to internal priority) using the CoS encode table. X = Original outer VLAN CoS. Y = Original inner VLAN CoS. Z = Incoming EXP bits as described by the Tunnel or VC label column = V or internal priority. The or option in the Tunnel/VC label column is to differentiate when qos exp encode policy is on (default) or off.
Configuring VPLS instances 3 Specifying the VPLS VC type The default VC type for all VPLS instances is set to 0x5 or “Ethernet”. For compatibility with previous versions, the VC type can be changed to 0xB or “Ethernet VPLS”. The VC type must match between peers for the VPLS session to be established. To change the VPLS VC type, use the following command at the MPLS configuration level.
3 Configuring VPLS instances Brocade(config-mpls-vpls-test)# no vc-mode raw-pass-through For VPLS instances with an ISID configuration, first remove the ISID configuration, then disable VPLS raw-pass-through mode. When the user attempts to disable VPLS raw pass through mode on a VPLS instance with ISID, the system displays the following error message.
Configuring VPLS instances 3 • When the original packet has an I-component Service Identifier (ISID) tag, the payload tag is the unmodified ISID tag For more information about CoS behavior for VPLS tagged mode, see Table 70. VPLS tagged mode must be enabled on both sides of the communicating edge routers. When the VPLS VC type does not match, the remote peer does not transition into operational state.
3 Configuring VPLS instances TABLE 70 Expected class of service behavior for VPLS tagged mode VPLS endpoints Incoming packet Outer VLAN MPLS cloud Outgoing packet Inner VLAN Tunnel/VC label (Z) Payload tag Outer VLAN Inner VLAN Dual-tagged X to dual-tagged Y V or internal priority Y W or Y Y Single-tagged X to dual-tagged N/A X W or X X Untagged N/A to dual-tagged N/A 0 W or 0 0 Y Y W or Y N/A Dual-tagged to single-tagged X Legend for Table 70 V = Mapped EXP bits from inter
Configuring VPLS instances 3 • Use the COS value assigned to the VPLS. The VPLS COS is a configurable option. Show commands will display the COS if it is configured. If the COS value it is not configured, the show commands will not display any COS value. When a COS value is set for the VPLS, the device selects a tunnel LSP that also has this COS value, when one is available.
3 LSP load balancing for VPLS traffic Specifying an LSP to reach a peer within a VPLS The user can specify the LSPs that can be used to reach a peer within a VPLS. The user can specify up to four Resource ReSerVation Protocol (RSVP) LSPs per VPLS peer. VPLS subsequently selects one of the LSPs configured to reach the specified peer. Any of the configured LSPs can be used, and the order of configuration is not relevant to the selection of the LSP.
LSP load balancing for VPLS traffic 3 • IPv4 TCP packets: Source MAC address and destination MAC address, source IP address and destination IP address, and TCP source port and TCP destination port. • IPv4 UDP packets: Source MAC address and destination MAC address, source IP address and destination IP address, and UDP source port and UDP destination port. • IPv6 non-TCP/UDP packets: Source MAC address and destination MAC address, source IP address and destination IP address.
3 VPLS LSP load balancing NOTE To disable the LSP load balancing, the user must delete the VPLS peer with the no vpls-peer command, then re-enter the vpls-peer command without the load-balance option. In the prior example, when the load-balance option is specified, VPLS traffic originating from the device and sent to peer 192.168.0.0 is load balanced across eligible tunnel LSPs whose destination is the peer.
Commands 3 Commands The following command support the features described in this chapter: • show mpls vpls detail Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 471
3 show mpls vpls detail show mpls vpls detail VPLS Manual LSP assignment for a peer can now accept maximum of eight LSPs instead of four LSPs. The show mpls vpls detail command output shows all the tunnels (maximum eight) used. Syntax Parameters Modes Command output Examples 472 show mpls vpls detail None Global configuration mode. The show mpls vpls detail command displays the following information. Output field Description VPLS The configured name of the VPLS instance.
show mpls vpls detail 3 VC-Mode: Raw Total VPLS peers: 1 (1 Operational) Peer address: 19.19.19.
3 show mpls vpls detail Specifying the endpoint of a VPLS instance When the user configures the VPLS endpoint, the user specifies what happens to packets exiting the VPLS instance, which VLAN the packet belongs to, as well as whether it is transmitted from the PE device to the CE device over a dual-tagged, single-tagged, or untagged port. The user can also specify a server Link Aggregation Group (LAG) group as the endpoint of a VPLS instance.
show mpls vpls detail 3 NOTE The system-max size for the Internal Forwarding Lookup CAM is zero. Use the command system-max ifl-cam to specify a size. The informational message only warns that the configuration must be changed. It does not cause the system to reject the VPLS configuration.
3 show mpls vpls detail Brocade(config-mpls-vpls-test)# cpu-protection Error - Cannot configure CPU protection for VPLS 10 as multiple end-points share the same physical port. The restrictions exist because packets are hardware-forwarded when CPU protection is enabled. In this case, source port suppression cannot be properly performed when there are multiple endpoints on the same physical interface.
show mpls vpls detail 3 Brocade(config-mpls)# vpls v1 40000 Brocade(config-mpls-vpls-v1)# vlan 200 inner-vlan 300 Brocade(config-mpls-vpls-v1-vlan-200)# tagged ethernet 3/11 Syntax: [no] vlan VLAN-ID inner-vlan VLAN-ID Syntax: [no] tagged ethernet slot/port The vlan VLAN-ID variable, which is the outer VLAN ID, can be in the range from 1 through 4094 and excludes the default VLAN. The inner-vlan VLAN-ID variable, can be in the range from 1 through 4095 and includes the default VLAN.
3 show mpls vpls detail Brocade(config-mpls-vpls-test_10)# vlan 100 Brocade(config-mpls-vpls-test_10-vlan-100)# tagged ethernet 2/1 Brocade(config-mpls-vpls-test_10-vlan-100)# exit Brocade(config-mpls-vpls-test_10)# exit Brocade(config-mpls)# vpls test_20 20 Brocade(config-mpls-vpls-test_20)# vlan 100 inner-vlan 300 Brocade(config-mpls-vpls-test_20-vlan-100-inner-vlan-300)# tagged ethernet 2/1 Brocade(config-mpls-vpls-test_20-vlan-100-inner-vlan-300)# exit Example of a less-specific and more-specific VLA
show mpls vpls detail 3 • Traffic received from any port in the LAG is forwarded to the VPLS instance. All traffic is matched to its VLAN.
3 show mpls vpls detail Configuring VPLS tagged mode This section describes how to enable, disable, and view the configuration details of VPLS tagged mode. For details about how VPLS tagged mode works, see “VPLS tagged mode”. Enabling VPLS tagged mode To enable VPLS tagged mode, first create the VPLS instance when it does not already exist, and then enter commands such as the following at the MPLS VPLS configuration level of the CLI.
show mpls vpls detail 3 Displaying the VPLS raw pass through mode configuration Use the show mpls vpls detail command to view the VPLS raw pass through mode configuration. Brocade# show mpls vpls detail VPLS name_raw, Id 3, Max mac entries: 8192 Total vlans: 1, Tagged ports: 3 (3 Up), Untagged ports 0 (0 Up) IFL-ID: 4097 Vlan 300 inner-vlan 500 Tagged: ethe 3/1 ethe 3/11 ethe 3/13 VC-Mode: Raw Total VPLS peers: 1 (1 Operational) Peer address: 10.200.200.
3 show mpls vpls detail Table 73 lists the output displayed by the show mpls vpls detail command. TABLE 73 482 Output from the show mpls vpls detail command Field Description VPLS The configured name of the VPLS instance. Id The ID of this VPLS instance. Max mac entries The maximum number of MAC address entries that can be learned for this VPLS instance. This is a soft limit only and can be exceeded when there is space available in the VPLS MAC database.
show mpls vpls detail TABLE 73 3 Output from the show mpls vpls detail command (Continued) Field Description Uptime The time in minutes that the entry has been operational. Tnnl in use The tunnel LSP used to reach the VPLS peer. When VPLS traffic to the peer is load balanced across multiple tunnel LSPs, the tunnel LSPs used to reach the peer are displayed. LDP session The state of the LDP session between this device and the VPLS peer.
3 show mpls vpls detail • CPU protection cannot be enabled for a VPLS instance that has a port configured under two different VPLS VLANs. Similarly, when CPU protection is enabled for a VPLS instance, the system does not support a configuration with two different VPLS VLANs as part of the same VPLS instance. • When VPLS FID usage reaches 100%, CPU protection is temporarily disabled until adequate FID resources are available.
Layer 2 control traffic behavior on VPLS endpoints 3 The number variable refers to the packet limits for broadcast, multicast, and unknown unicast packets. NOTE When configuring global multicast-limit all multicast packets, even those that would have been hardware forwarded, will not be sent to the CPU to be rate-limited. CPU packet limiting The CPU limiting feature affects the packets being flooded into VPLS endpoints as well as remote peers.
3 Layer 2 control traffic behavior on VPLS endpoints 802.1x Protocol packets on a VPLS endpoint 802.1x does not support VPLS endpoints. Cisco Discovery Protocol packets Cisco Discovery Protocol (CDP) cannot be configured on a VPLS endpoint port and a VPLS endpoint cannot be configured on a physical port that has CDP enabled. This restriction is enforced by the CLI. When a VPLS endpoint receives any CDP traffic, this traffic is transparently flooded within the VPLS.
Flooding Layer 2 BPDUs with a VPLS instance 3 3 When both FDP/CDP is enabled globally. Brocade(config-mpls-vpls-vpls1-vlan-100)#tag eth 4/3 eth 4/5 eth 4/7 info- FDP/CDP is disabled on port 4/3 info- FDP/CDP is disabled on port 4/5 info- FDP/CDP is disabled on port 4/7 For example, when VPLS endpoint is deleted the info messages are displayed as below. 1 When only FDP is enabled globally.
3 Flooding Layer 2 BPDUs with a VPLS instance Specifying a VPLS MTU The vpls-mtu command allows the user to specify an MTU value per VPLS instance. The newly configured VPLS MTU takes effect immediately to refresh or re-establish the VPLS sessions with peers in the following manner: • When the VPLS session is Operational and the VPLSs MTU is changed by configuration, bring down the peer, send a label withdraw message to the peer, followed by the current VC binding message.
Flooding Layer 2 BPDUs with a VPLS instance 3 Configuring VPLS MTU enforcement The user can set the device to enforce the VPLS MTU value when establishing control sessions with peers. This is done globally on the Brocade device using the vpls-mtu-enforcement command. Brocade(config)# router mpls Brocade(config-mpls)# vpls-mtu-enforcement Syntax: [no] vpls-mtu-enforcement NOTE The vpls-mtu-enforcement command is global to all VPLS instances. It requires a reload to take effect.
3 Enabling MPLS VPLS traps Enabling MPLS VPLS traps The user can enable traps that are generated for MPLS VPLS by entering the following command. Brocade(config)# snmp-server enable trap mpls vpls Syntax: [no] snmp-server enable trap mpls vpls Refer to the Unified IP MIB Reference for MPLS VPLS trap notifications. Disabling Syslog messages for MPLS VPLS The generation of Syslog messages for MPLS VPLS and MPLS VLL Local is enabled by default.
Displaying VPLS extended counters 3 The on option enables extended counters for a particular VPLS instance. The off option disables extended counters for a particular VPLS instance. Displaying VPLS extended counters When extended counters are enabled for a particular VPLS instance either by default or explicit configuration, the user can display the number of bytes and packets received and sent on a particular endpoint or all the endpoints of that particular VPLS instance.
3 Clearing VPLS extended counters Table 74 describes the output parameters of the show mpls statistics vpls extended-counters command. TABLE 74 Output of the show mpls statistics vpls extended-counters command Field Description VPLS Name The configured name for a VPLS instance. VPLS Id The ID of the VPLS instance. VPLS Vlan The ID of the configured VLAN. Interface The port ID of the interface for which the user wants to display the counters.
Local VPLS 3 The vlan vlan-id parameter specifies the ID of the configured VLAN for which the user wants to clear the counters. The ethernet port-id parameter specifies the port ID of the interface for which the user wants to clear the counters. The priority pri parameter specifies a priority queue for a particular VPLS endpoint for which the user wants to clear the counters. Local VPLS Local VPLS is used to create a VPLS circuit with endpoints in the same device.
3 Local VPLS The endpoints connected to the Local VPLS can be untagged, dual tagged, or single-tagged as members of the same or different VLANs. Using this function of Local VPLS, a router can receive packets with particular tags or no tag on one endpoint and forward them to the Local VPLSs other endpoint, which may be untagged, dual-tagged, or single-tagged with a different VLAN tag.
Local VPLS TABLE 75 Local VPLS endpoints 3 Expected class of service behavior for Local VPLS Incoming packet Outgoing packet Outer VLAN Inner VLAN Outer VLAN Inner VLAN Dual-tagged to dual-tagged X Y X’ or X Y Single-tagged to dual-tagged X N/A X’ or X X Untagged to dual-tagged N/A N/A X’ or 0 0 Dual-tagged to single-tagged X Y X’ or Y N/A Legend for Table 75 X = Original outer VLAN CoS. Y = Original inner VLAN CoS.
3 Displaying VPLS information Brocade(config)# router mpls Brocade(config-mpls)# vpls test1 Brocade(config-mpls-vpls-test1)# vlan 200 Brocade(config-mpls-vpls-test1-vlan-200)# tagged ethernet 1/2 Syntax: vlan VLAN-ID The range for VLAN ID from 1 through 4094. (This parameter range excludes the default VLAN ID.) Syntax: [no] tagged ethernet slot/port The slot/port variable specifies the port that is a tagged ethernet port.
Displaying VPLS information • • • • • • • • 3 Information about individual VPLS instances configured on the device Detailed information about VPLS instances Information about a specified VPLS ID or VPLS name Information about VPLS instances that are not fully operational The contents of the VPLS MAC database for a VPLS instance The VPLS MAC database entries on the Management Processor (MP) VPLS traffic statistics VPLS CPU protection configuration status Display considerations for VPLS information The VP
3 Displaying VPLS information Displaying information about VPLS instances The show mpls vpls brief command has changed. The Num VC-label field is no longer displayed in the output of the show mpls vpls brief command. To display information about VPLS instances configured on the device, enter the following command.
Displaying VPLS information 3 Brocade# show mpls vpls detail VPLS 3, Id 3, Max mac entries: 8192 Total vlans: 2, Tagged ports: 2 (1 Up), Untagged ports 0 (0 Up) IFL-ID: n/a Vlan 500 Tagged: ethe 1/3 Vlan 600 Tagged: ethe 1/4 VC-Mode: Raw Total VPLS peers: 1 (1 Operational) Peer address: 21.21.21.
3 Displaying VPLS information TABLE 77 Output from the show mpls vpls detail command (Continued) Field Description Total VPLS peers The number of VPLS peers this device has for this VPLS instance, as well as the number of these VPLS peers with which this device has an LDP session. Peer address The IP address of the VPLS peer. State The current state of the connection with the VPLS peer. This can be one of the following states: • Operational – The VPLS instance is operational.
Displaying VPLS information 3 The Wait for LDP session to Peer state is no longer displayed in the output of the show mpls vpls detail command. The Wait for Pseudo Wire (PW) Up (Wait for LDP session to Peer) state is now displayed, and replaces the existing state. The total VC labels allocated field is also removed from the output. In the following example, the LDP session to the remote peer is down. The Local VC lbl field displays N/A (not applicable).
3 Displaying VPLS information WARNING: VPLS id 3 Peer IP Address: 10.21.21.21 is placed in VC Bind Failure state due to low system memory. WARNING: VPLS id 3 Peer IP Address: 10.11.11.11 state due to low system memory. is placed in VC Withdraw Failure Displaying information about a specified VPLS ID or VPLS name The show mpls vpls id vpls-id command displays detailed information about a specified VPLS ID. The show mpls vpls name vpls-name command displays detailed information about a VPLS name.
Displaying VPLS information 3 Brocade# show mpls vpls id 200 VPLS vc_mismatched, Id 200, Max macentries: 8192 Total vlans: 1, Tagged ports: 1 (1 Up), Untagged ports 0 (0 Up) IFL-ID: 4098 Vlan200 inner-vlan145 Tagged: ethe2/1 VC-Mode: Tagged Total VPLS peers: 1 (0 Operational) Peer address: 10.33.33.
3 Displaying VPLS information Brocade# show mpls vpls id 400 VPLS waiting_for_remote_label, Id 400, Max macentries: Total vlans: 1, Tagged ports: 1 (1 Up), Untagged ports IFL-ID: 4100 Vlan900 inner-vlan245 Tagged: ethe7/1 VC-Mode: Tagged Total VPLS peers: 1 (0 Operational) Peer address: 10.55.55.
Displaying VPLS information 3 The vpls-id variable is the ID of a VPLS instance. The vpls-name variable is the name of a VPLS instance. Displaying VPLS CPU protection configuration status The show mpls vpls id command has changed. The total VC labels allocated field is no longer displayed in the output of the show mpls vpls id command. To see the VPLS CPU protection configuration status for a specified VPLS, use the show mpls vpls id command.
3 Displaying VPLS information Displaying the contents of the VPLS MAC database The VPLS MAC database stores entries associating remote MAC addresses with VC LSPs and local MAC addresses with CE devices. When a PE device receives a Layer 2 frame from an attached CE device with a given destination MAC address, the PE device looks up the MAC address in the VPLS MAC database and assigns the frame to the associated VC LSP. Each VPLS instance configured on the PE device has a separate VPLS MAC database.
Displaying VPLS information 3 Brocade# show mac vpls Total VPLS mac entries in the table: 2274 (Local: 8, Remote: 2266) VPLS ==== 3 504 504 504 504 504 504 504 504 MAC Address ============== 0000.009b.d419 0000.0000.0067 0000.0033.b24c 0000.0073.6185 0000.0000.40cf 0000.0019.d7f4 0000.0044.d58b 0000.005c.5a3b 0000.0044.d696 L/R === L R R R R R R R R Port ==== 4/2 Mult. Mult. 1/1 Mult. Mult. Mult. Mult. Mult. Vlan:Inner-Vlan /Peer ============ 3 10.99.42.253 10.99.42.253 10.99.42.253 10.99.42.253 10.
3 Displaying VPLS information TABLE 78 Output from the show mac vpls command Field Description Total VPLS mac entries in the table The number of MAC addresses that have been learned in the database. Local The number of locally learned entries in the database. Remote The number of remotely learned entries in the database. VPLS The VC ID of the VPLS instance. MAC Address The MAC address of the entry.
Displaying VPLS information 3 To display all VPLS traffic statistics on a Brocade device, enter the following command.
3 Clearing VPLS traffic statistics To display VPLS traffic statistics for a VPLS instance specified by its VPLS ID, enter the following command.
VPLS LDP 3 VPLS LDP Displaying the VPLS peer FSM state with LDP support The user can display the various VPLS peer FSM states with the LDP integration on the device using the show mpls vpls commands. Table 80 provides a description of all the peer FSM states with the LDP support. TABLE 80 PEER FSM state description Peer FSM state name State description Wait for functional local ports No functional local endpoints. Wait for LSP tunnel to Peer No LSP tunnels available to reach the remote peer.
3 VPLS LDP Brocade# show mpls vpls id 200 VPLS vc_mismatched, Id 200, Max mac entries: 8192 Total vlans: 1, Tagged ports: 1 (1 Up), Untagged ports 0 (0 Up) IFL-ID: 4098 Vlan 200 inner-vlan 145 Tagged: ethe 2/1 VC-Mode: Tagged Total VPLS peers: 1 (0 Operational) Peer address: 10.33.33.
VPLS LDP 3 Brocade# show mpls vpls id 400 VPLS waiting_for_remote_label, Id 400, Max mac entries: 8192 Total vlans: 1, Tagged ports: 1 (1 Up), Untagged ports 0 (0 Up) IFL-ID: 4100 Vlan 900 inner-vlan 245 Tagged: ethe 7/1 VC-Mode: Tagged Total VPLS peers: 1 (0 Operational) Peer address: 10.55.55.
3 MPLS LDP show commands Brocade# show mpls vpls detail VPLS waiting_for_remote_label, Id 400, Max mac entries: 8192 Total vlans: 1, Tagged ports: 1 (1 Up), Untagged ports 0 (0 Up) IFL-ID: 4100 Vlan 900 inner-vlan 245 Tagged: ethe 7/1 VC-Mode: Tagged Total VPLS peers: 1 (0 Operational) Peer address: 10.55.55.
VPLS MAC age timer configuration overview 3 There is an existing CLI to configure a global timer that controls MAC aging in the system (software cache). However, this configuration is not being applied to the age timers used for MAC entries associated with VPLS instances. Consequently, the age timer for VPLS MAC entries becomes hard-coded. The VPLS application has separate age timers for different types of entries, local and remote. Prior to NetIron R05.5.
3 VPLS MAC age timer configuration overview • When aging is re-enabled after software aging is disabled, the software aging resumes from the age value where it was stopped. The MAC age timer aging operation • The aging process only applies to MAC entries that are learned dynamically. • A SA lookup is always performed on incoming VPLS traffic, a miss on the lookup in hardware triggers SA learning. • A SA entry is installed in both software and hardware on the LP where it is learned.
Commands 3 Commands The following commands upport the features describe in this chapter: • mac-age-time vpls • show mpls vpls summary Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 517
3 mac-age-time vpls mac-age-time vpls The mac-age-time vpls command time value of zero can also be configured, which disables the software aging process. This is hidden. However, it provides the flexibility to you. The MAC age time sets the aging period for ports on the device, defining how many seconds a port address remains active in the address table. Syntax Parameters mac-age-time vpls vpls Sets aging period for VPLS MAC entries.
mac-age-time vpls 3 DECIMAL seconds to age software MAC table 60..65535 Brocade(config)#mac-age-time vpls remote 240 History Related commands Release Command history NetIron R05.5.00 This command was introduced. Relate command Description mac-age-time DECIMAL Seconds to age software MAC table 60 - 65535 seconds.
3 show mpls vpls summary show mpls vpls summary You can display a summary of VPLS information, including the number of VPLS instances, number of VPLS peers, maximum size of the VPLS MAC database, VPLS raw mode, and the values of the VPLS global MTU, the value of the remote VC MTU, the MAC-address withdrawal limit, MAC age for local, and MAC age for remote, with the show mpls vpls summary command. Syntax Parameters Modes Command output show mpls vpls summary None. Global configuration mode. This Field...
show mpls vpls summary 3 MAC age time for local: 150 MAC age time for remote: 200 Show command on LP (MLX and XMR only) Brocade(config)# shOW mpls vpls VPLS Summary ============ CPU Protection: OFF MAC age time for local: 150 MAC age time for remote: 200 History Related commands Release Command History NetIron R05.5.00 New MAC age time for local and remote parameter added. None.
3 522 show mpls vpls summary Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Chapter 4 Configuring MPLS Virtual Leased Line Overview Table 81 displays the individual Brocade devices and the MPLS Virtual Leased Line (VLL) features they support.
4 Overview TABLE 81 Supported Brocade MPLS Virtual Leased Line (VLL) features (Continued) Features supported Brocade NetIron XMR Series Brocade MLX Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package Dual-tags for VLL-local Yes Yes No No No No No MPLS Signalling: RSVP-TE support Yes Yes No
How MPLS VLL works 4 How MPLS VLL works The following diagram illustrates how packets are forwarded over an MPLS VLL. FIGURE 57 Forwarding packets over an MPLS VLL Packets are forwarded over an MPLS VLL as described below. 1. A Customer Edge (CE) device forwards a packet to a Label Edge Router (LER) serving as a Provider Edge (PE) router at the edge of the MPLS domain. 2.
4 How MPLS VLL works 4. The VLL peer at the egress of the tunnel LSP examines the VC label. This VC label is mapped to an endpoint for the VLL. The endpoint of a VLL specifies what happens to packets exiting the VLL. The endpoint can specify an untagged, dual-tagged, or single-tagged port. • For untagged ports, the endpoint consists of an interface • For single-tagged ports, the endpoint consists of an interface and a VLAN ID.
How MPLS VLL works 4 • On Brocade NetIron CES and Brocade NetIron CER devices, only one of the trunk ports is used for a given VLL instance, depending on the VC label used by the instance. QoS for VLL traffic By default, packets travelling through an MPLS domain are treated equally from a QoS standpoint, in a best effort manner. However, when a Layer 2 packet has an internal priority in its 802.
4 How MPLS VLL works Tunnel LSP configured COS or VLL configured COS or 802.
How MPLS VLL works EXP Bits in VC label Priority queue 6, 7 qosp3 (highest priority) 4, 5 qosp2 2, 3 qosp1 0, 1 qosp0 (best effort) 4 CoS behavior for VLL tagged mode and VLL raw mode This section describes the difference in CoS behavior for VLL traffic when tagged mode or raw mode is in effect. CoS behavior for VLL tagged mode NOTE This section assumes that the user understands how QoS works.
4 How MPLS VLL works W = mapped COS from internal priority (Z contributes to internal priority) using the COS encode table X = original outer VLAN COS Y = original inner VLAN COS Z = incoming EXP bits as described by Tunnel / VC label column = V or internal priority or in the Tunnel/VC label column differentiates the behavior between when qos exp encode policy is ON (default) or OFF.
4 How MPLS VLL works or in the Tunnel/VC label column differentiates the behavior when qos exp encode policy is ON (default) or OFF. or in the Outgoing packet Outer VLAN column differentiates the behavior when qos pcp encode policy is ON (default) or OFF. Example 1: CoS behavior for dual-tagged to dual-tagged VLL endpoints Table 84 shows a detailed example of the CoS behavior in a dual-tagged to dual-tagged VLL endpoint configuration.
4 How MPLS VLL works TABLE 84 Example CoS behavior in a dual-tagged to dual-tagged VLL endpoint configuration Port priority 5 (with priority force), LSP CoS 3. VLL CoS 4 QoS exp encode policy all-zero (ingress router) VLAN 100, CoS 7 VLAN 200, CoS 7 VLAN 300, CoS 0 VLAN 400, CoS 7 VLAN 300 CoS 0 VLAN 400 CoS 0 Port priority 5 (with priority force), LSP CoS 3.
4 Configuring MPLS VLLs TABLE 85 Example CoS behavior in a dual-tagged to single-tagged VLL endpoint configuration Port priority 7 (with priority force), LSP CoS 0. VLL CoS 4 VLAN 100, CoS 6 VLAN 200 CoS 5 VLAN 300, CoS 0 NA VLAN 300 CoS 0 NA .1p is 6 for outer VLAN, 5 for inner VLAN Port 3 No LSP CoS VLL CoS 4 (ingress above) Egress below Port is 7 VLL CoS 2 VLAN 100 CoS 6 VLAN 200 CoS 5 VLAN 300 CoS 7 NA VLAN 300 CoS 7 NA Port priority 7 (with priority force), LSP no value.
4 Configuring MPLS VLLs Brocade(config-mpls)# vll foundry-sj-to-sf 40000 Brocade(config-mpls-vll)# On the VLL peer (when it is a device), the user would enter commands such as the following. Brocade(config-mpls)# vll foundry-sf-to-sj 40000 Brocade(config-mpls-vll)# Syntax: vll vll-name | vll-vc-id [cos cos value] [raw-mode] The vll-vc-id corresponds to the user-configurable ID defined in draft-ietf-pwe3-control-protocol-14.txt.
Configuring MPLS VLLs 4 Specifying a VLL peer The VLL peer is the PE router at the other end of the VLL. As part of VLL configuration, the user specifies the IP address of the VLL peer. Each PE router must have tunnel LSP reachability to its VLL peer. Tunnel LSP reachability is defined as having at least one operational LSP tunnel with the destination (the LSPs “to” address) matching the VLL peer’s IP address.
4 Configuring MPLS VLLs • In the case of an untagged port, an endpoint is identified by the physical port alone, and the packets are sent in untagged Ethernet format. • In the case of a dual-tagged port, the packets contain both an outer VLAN tag and an inner VLAN tag.
Configuring MPLS VLLs 4 NOTE By removing FDP from the configuration, no fdp enable stays in the configuration of the VLPS endpoints, which cannot be removed. Special considerations for VLL dual-tagged endpoints Before configuring a dual-tagged endpoint, consider the following: • An Internal Forwarding Lookup Identifier (IFL-ID) is be allocated to each MPLS VLL instance that has a dual-tagged endpoint. The ID is displayed in the show mpls vll detail command output.
4 Configuring MPLS VLLs Specifying an untagged endpoint Untagged ports are not associated with any VLAN. A port must be a member of the default VLAN before it can be used in a VLL configuration as an untagged port. Upon configuration as the endpoint of a VLL, the port is taken out of the default VLAN. This means no local broadcast traffic includes this port. A VLL untagged port does not belong to any VLAN.
Configuring MPLS VLLs 4 Specifying a dual-tagged endpoint Dual-tagged packets contain both an outer VLAN tag and an inner VLAN tag. Dual-tagged VLL endpoints enable MPLS VLL to recognize packets with two tags and make forwarding decisions based on them. A dual-tagged endpoint can receive packets with two tags and forward them to the other endpoint either untagged, single-tagged, or dual-tagged.
4 Configuring MPLS VLLs Specifying a LAG group as the endpoint of a VLL The endpoint of a VLL can be a LAG group. When the endpoint of a VLL is a LAG group, the VLL traffic load is distributed to the customer edge (CE) device across all of the LAG group’s ports, using a hashing mechanism. Figure 59 illustrates a sample configuration where a LAG group of two ports serves as the endpoint of a VLL.
Configuring MPLS VLLs 4 By default, MTU checking is off. The user can use the [no] form of the command to disable VLL MTU checking when it is on. NOTE The user must save the configuration and reload the software for this command to take effect. Specifying a VLL MTU Previously, every VLL configured on a Brocade device used the system default max-frame-size as the VLL MTU while establishing the LDP session with its peer.
4 Transparent forwarding of L2 and L3 protocols on a VLL for CES and CER Transparent forwarding of L2 and L3 protocols on a VLL for CES and CER Use the forward-all-control command to add per port Layer 2 and Layer 3 (L2/L3) protocols ACL filters for the VLL end-point port. The command no forward-all-control removes the L2/L3 protocols ACL filters for the VLL end point port. NOTE The forward-all-control command is only applicable to the Brocade NetIron CER and Brocade NetIron CES.
VLL extended counters 4 The following output example shows the show interfaces ethernet slot/port command with the forward-all-control command enabled. Brocade(config-if-e1000-1/1)# forward-all-protocol Brocade(config-if-e1000-1/1)# show interfaces ethernet 1/1 GigabitEthernet1/1 is up, line protocol is up STP Root Guard is disabled, STP BPDU Guard is disabled Hardware is GigabitEthernet, address is 001b.eda3.f841 (bia 001b.eda3.
4 Displaying VLL extended counters When the extended counters are disabled globally, the user can enable the extended counters for a particular VLL instance by entering the following command. Brocade(config-mpls-vll-test10)# extended-counters on Syntax: [no] extended-counters [on | off] The on option enables extended counters for a particular VLL instance. The off option disables extended counters for a particular VLL instance.
Clearing VLL extended counters 4 The ethernet port-id parameter specifies the port ID of the interface for which the user wants to display the counters. Table 86 describes the output parameters of the show mpls statistics vll extended-counters command. TABLE 86 Output of the show mpls statistics vll extended-counters command Field Description VLL The configured name for a VLL instance. VLL-ID The ID of the VLL instance. VLAN The ID of the configured VLAN.
4 MPLS VLL behavior with other features The vlan vlan-id parameter specifies the ID of the configured VLAN for which the user wants to clear the counters. The ethernet port-id parameter specifies the port ID of the interface for which the user wants to clear the counters. The priority pri parameter specifies a priority queue for a particular VLL endpoint for which the user wants to clear the counters.
Displaying MPLS VLL information 4 Layer 2 ACLs When the port and VLAN combination of a Layer 2 ACL matches with any VLL endpoint, the ACL is applied. For dual-tagged VLL endpoints, the Layer 2 ACL is applied based on the port and outer VLAN combination, when it is configured.
4 Displaying MPLS VLL information TABLE 88 Output from the show mpls vll command (Continued) This field... Displays... End-point How packets are forwarded once they reach the egress LER. This can be one of the following • “untagged portnum” – Forward the packet out the specified port as untagged. • “tag VLAN vlan-id / portnum” – Tag the packet with the specified VLAN ID and forward the packet out the specified port.
Displaying MPLS VLL information 4 Brocade# show mpls vll detail VLL VLL1 VC-ID 1001 State: DOWN -PW is Down (Reason: MTU mismatch Local-MTU 1500, Remote-MTU 1400) End-point: tagged vlan 1001 e 2/20 IFL-ID: -Vll-peer: 10.21.21.
4 Displaying MPLS VLL information Brocade# show mpls vll detail VLL VLL1 VC-ID 1001 State: DOWN -Waiting for PW Up End-point: tagged vlan 1001 e 2/20 IFL-ID: -Vll-peer: 10.21.21.21 Local VC type: tag Remote Local label: -Remote Local group-id: 0 Remote Local VC MTU: 1500 Remote COS: -Tunnel Extended Counters: Enabled VC type: label: group-id: VC MTU: LSP: ----LSP_XMR21 (tnl0) Syntax: show mpls vll detail | vll-name For each configured VLL, the command displays the following information in Table 263.
Displaying MPLS VLL information TABLE 89 4 Output from the show mpls vll detail command (Continued) This field... Displays... IFL-ID The Internal Forwarding Lookup Indentifier (IFL-ID) that is allocated to each Local VLL instance that has at least one dual-tagged endpoint. For instances that do not have dual-tagged endpoints, the IFL-ID is displayed as “--”. Vll-peer The remote PE router. This must be the same as the LSP destination for the LSPs that the VLL is transported over.
4 Displaying MPLS VLL information Brocade# show mpls vll detail VLL VLL1 VC-ID 1001 State: DOWN -VC withdrawal Failed End-point: tagged vlan 1001 e 2/20 IFL-ID: -Vll-peer: 10.21.21.21 Local VC type: tag Remote Local label: -Remote Local group-id: 0 Remote Local VC MTU: 1500 Remote COS: -Tunnel Extended Counters: Enabled VC type: label: group-id: VC MTU: LSP: ----LSP_XMR21 (tnl0) VLL generates the following warning messages.
Displaying MPLS VLL information 4 Brocade# show mpls ldp session Peer LDP Ident: 192.168.2.100:1, Local LDP Ident: 10.1.1.1:1 Active: no, State: Operational TCP connection: 10.1.1.1:646--10.2.2.2:9001, State: ESTABLISHED Addresses bound to peer LDP Ident: 10.1.1.2 1.1.1.2 20.1.1.2 22.2.2.2 Syntax: show mpls ldp session [label-space-id | detail | brief ] For each established LDP session, the command displays the following information. TABLE 91 Output from the show mpls ldp session command This field...
4 Displaying MPLS VLL information TABLE 92 Output from the show mpls ldp session command (Continued) This field... Displays... KeepAlive interval The frequency within which LDP “Hello” messages are sent out. Max hold time The length of time the device waits for a “Hello” message from its peer before terminating the session. Neighboring interfaces The physical interfaces on which the adjacency to the neighbor is formed. TCP connection, state The TCP local or remote IP address, port and state.
Clearing Local VLL traffic statistics 4 The vll-name variable is the configured name for a VLL instance. The vll-id variable is the ID of a VLL instance. For following information is displayed in the show mpls statistics vll command. TABLE 93 Output from the show mpls vll command This field... Displays... VLL-Name The configured name of the VLL instance. VLL-Ports The port where the traffic is monitored. VLL-Ingress-Pkts Packets arriving from the Customer Endpoint.
4 Sample MPLS VLL configuration In this example, routers R1 and R3 are Provider Edge (PE) routers configured as VLL peers. R1 and R3 have established an LDP session to exchange VLL label information. When the LDP session is established, each router advertises its locally assigned VC label and VC ID to its VLL peer. RSVP-signalled (tunnel) LSPs have been established in each direction between the two routers.
Sample MPLS VLL configuration 4 Brocade(config)# interface e 2/1 Brocade(config-if-e1000-2/1)# port-name Connection_to_R2 Brocade(config-if-e1000-2/1)# enable Brocade(config-if-e1000-2/1)# ip address 192.168.37.1/30 Brocade(config-if-e1000-2/1)# ip ospf area 0 Brocade(config-if-e1000-2/1)# exit Router R2 The following commands configure Router R2 in Figure 60. Brocade(config)# ip router-id 192.168.2.
4 Local VLL Brocade(config-mpls)# vll VLL_to_R1 40000 Brocade(config-mpls-vll)# vll-peer 192.168.2.100 Brocade(config-mpls-vll)# vlan 200 Brocade(config-mpls-vll-vlan)# tagged e 3/11 Brocade(config-mpls-vll-vlan)# exit Brocade(config-mpls-vll)# exit Brocade(config)# interface loopback 1 Brocade(config-lbif-1)# port-name Generic All-Purpose Loopback Brocade(config-lbif-1)# ip address 192.168.2.
Local VLL 4 NOTE Packets that arrive on an interface with the same destination MAC address as the interface are forwarded in hardware just like packets with other destination addresses. The endpoints connected to the Local VLL can be untagged or tagged as members of the same or different VLANs.
4 Local VLL Under this configuration, a router can receive packets with a two tags on one endpoint and forward them to the Local VLLs other endpoint either untagged, tagged with a single tag or tagged with an inner and outer VLAN tag. Where dual-tagging is used within a Local VLL, the system allocates an Internal Lookup Indentifier (IFL-ID) for the Local VLL instance. In Figure 63 the Local VLL named “Test2” contains Ethernet ports 1/1 and 2/1.
Local VLL 4 FIGURE 63 Local VLL “Test2” with one single-tagged VLAN and one dual-tagged VLAN Brocade(config)# system-max ifl-cam 16384 Brocade(config)# router mpls Brocade(config-mpls)# vll-local test2 Brocade(config-mpls-vll-lo-test1)# vlan 100 inner-vlan 300 Brocade(config-mpls-vll-lo-test1-vlan)# tagged ethernet 1/1 Brocade(config-mpls-vll-lo-test1-vlan)# vlan 200 Brocade(config-mpls-vll-lo-test1-vlan)# tagged ethernet 2/1 A shown in the following example, the user can use the show mpls vll-local det
4 Local VLL Brocade(config)# router mpls Brocade(config-mpls)# vll-local test3 Brocade(config-mpls)# untagged ethernet 2/1 Brocade(config-mpls-vll-lo-test1)# vlan 100 Brocade(config-mpls-vll-lo-test1-vlan)# tagged ethernet 1/1 Local VLL QoS The user can optionally specify Class of Service (COS) on a per-endpoint (EP) basis. This COS value applies to inbound traffic on the endpoint. When a COS value is not specified, the port’s configured priority and the packet’s 802.
Local VLL 4 1. The internal priority is determined. 2. When Vll-local COS is configured, this value overrides internal priority. 3. The outgoing outer VLAN COS is mapped from internal priority through use of the egress encoding map by default. The internal priority does not affect the outgoing inner VLAN COS 4. The outgoing outer VLAN COS is preserved when qos pcp encode-policy off is configured on the outgoing interface. 5. The outgoing inner VLAN COS is the COS in the incoming packet.
4 Local VLL TABLE 94 Local VLL endpoints Expected class of service behavior for Local VLL Incoming packet Outgoing packet Outer VLAN Inner VLAN Outer VLAN Inner VLAN Untagged to dual-tagged N/A N/A X’ or 0 0 Dual-tagged to single-tagged X Y X’ or Y N/A Legend for Table 94 X = original outer VLAN CoS Y = original inner VLAN CoS X’ = mapped CoS from internal priority (X contributes to internal priority) using CoS encode table Configuring Local VLL Configuring Local VLL uses the following p
Local VLL 4 Configuring a single-tagged endpoint Tagged ports are configured under a VLAN ID. This ID is only meaningful for the tagged port. For tagged ports, a vlan-id, port pair constitutes a VLL endpoint. When a port is currently a member of a non-default VLAN as an untagged port, it must be returned to the default VLAN before it can be assigned to a VLL as a tagged port. To configure tagged port 1/2 with VLAN 200 into Local VLL instance “test1” use the following commands.
4 Local VLL Brocade(config-mpls)# vll-local test1 Brocade(config-mpls-vll-lo-test1)# vlan 100 Brocade(config-mpls-vll-lo-test1-vlan)# tag e 2/1 Brocade(config-mpls-vll-lo-test1-if-e-2/1)# vlan 100 inner-vlan 200 Brocade(config-mpls-vll-lo-test1-vlan)# tag e 2/1 Brocade(config-mpls-vll-lo-test1-vlan)# The result of this example is that single-tagged packets received on port 2/1 with VLAN ID value of “100” and double-tagged packets with an outer-VLAN value of “100” and inner-VLAN of any value other than “2
Local VLL extended counters 4 To set a COS value for an untagged port use the following command. Brocade(config)# router mpls Brocade(config-mpls)# vll-local test1 Brocade(config-mpls-vll-test1)# untagged ethernet 1/1 Brocade(config-mpls-if-e1000-1/1)# cos 3 To set a COS value for an tagged port use the following command.
4 Displaying Local VLL extended counters Displaying Local VLL extended counters When extended counters are enabled for a particular Local VLL instance either by default or explicit configuration, the user can display the number of bytes and packets received and sent on a particular endpoint or all the endpoints of that Local VLL instance. The counters are displayed whether or not the per-VLAN, port, and priority-based accounting mode is enabled at the global configuration level.
Clearing Local VLL extended counters TABLE 95 4 Output of the show mpls statistics vll-local extended-counters command Field Description VLL The configured name for a Local VLL instance. VLL-ID The ID of the Local VLL instance. VLAN The ID of the configured VLAN. Port The port ID of the interface for which the user wants to display the counters. RxPkts The number of packets received at the specified port. TxPkts The number of packets transmitted from the specified port.
4 Displaying Local VLL information The ethernet port-id parameter specifies the port ID of the interface for which the user wants to clear the counters. The priority pri parameter specifies a priority queue for a particular Local VLL endpoint for which the user wants to clear the counters.
Displaying Local VLL information 4 To display detailed information about a specific Local VLL configured on the device.
4 Displaying Local VLL information TABLE 97 Output from the show mpls vll-local detail command (Continued) This field... Displays... End-point How packets are forwarded out of the egress port of the Local VLL. This can be one of the following: • “untagged portnum” – Forward the packet out the specified port as untagged. • “tag VLAN vlan_id / portnum” – Tag the packet with the specified VLAN ID and forward the packet out the specified port.
Enabling MPLS Local VLL traps Brocade# show mpls stat vll-local 4 VLL-Name End-point 1/2 VLL Port(s) -----------------------------------test3 End-point1 e2/1 End-point2 e2/2 4 VLL-Ingress-Pkts -----------------0 0 Syntax: show mpls statistics vll-local [vll-name | vll-id] The vll-name variable is the configured name for a Local VLL instance. The vll-id variable is the ID of a VLL instance.
4 Disabling Syslog messages for MPLS VLL-local and VLL Disabling Syslog messages for MPLS VLL-local and VLL Transitions of VLL local instances from an up state to a down state and vice versa are logged by default. The user can disable the logging of these events by entering the following command. Brocade(config)# no logging enable mpls Syntax: [no] logging enable mpls Similarly, the generation of Syslog message for MPLS VLL events are enabled by default.
VLL raw-pass-through overview 4 Packet handling behavior Depending on the type of endpoints configured on the VLL instance, VLL instance has the packet processing behavior listed in Table 90. TABLE 99 Packet tag insertion and stripping decision Local endpoint type Packet received from local endpoint destined towards remote peer (MPLS uplink). Packet received from local remote peer (MPLS uplink) destined towards local endpoint. Untagged endpoint No additional tag is inserted in the packet.
4 VLL raw-pass-through overview Figure 58 describes the tagged packet handling with “tagged-mode” prior to NetIron R05.5.00. FIGURE 65 Tagged packet handling into and from MPLS link uplink with ‘tagged-mode’ Figure 59 describes the tagged packet handling in the “raw-mode” prior to NetIron R05.5.00.
Customer requirements 4 Figure 60 describes the behavior with “raw-pass-through-mode” with NetIron R05.5.00. FIGURE 67 Tagged packet handling into and from MPLS uplink with ‘raw-pass-through’ Backward compatibility This feature is backward compatible where the existing VC modes continue to be supported and operable with older releases. Upgrade and downgrade considerations When deploying this feature, follow the standard upgrade procedure for the XMR/MLX platform.
4 Commands Commands The following commands support the features described in this chapter: • raw-pass-through-mode • show mpls vll detail 578 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
raw-pass-through-mode 4 raw-pass-through-mode A new CLI option is added as part of the VLL configuration to support a raw-pass-through mode to inter-operate between the vendors. Prior to NetIron R05.5.00, there was only one option to configure VC mode as “raw-mode” and the default configuration is “tagged-mode”. A new option is added to allow you to select the “raw-pass-through mode”.
4 show mpls vll detail show mpls vll detail To display detailed information about the configurations of the VLLs on the device, use the show mpls vll detail command. Syntax Command default None. Parameters None. Command modes Usage guidelines Command output 580 show mpls vll detail Interface sub-configuration mode. Using the show mpls vll detail command displays information about the operation state of the VPLS instance in regard to the local endpoints.
show mpls vll detail Example 4 For tagged endpoint: Brocade(config)# show mpls vll detail VLL test, VC-ID 1, VLL-INDEX 0 End-point : End-Point state : MCT state : Local VC type : Local VC MTU : Extended Counters: Counter : tagged vlan 100 Up None raw-pass-through 1500 disabled disabled Vll-Peer State Remote VC type Local label Local group-id Tunnel LSP 20.0.0.
4 582 show mpls vll detail Related command Description show mpls vll ASCII string VLL name show mpls vll brief Brief information show mpls vll redundancy MCT VLLs and VLLs having redundant peers Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Chapter 5 IP over MPLS One of the benefits that MPLS offers service providers is the ability to take advantage of MPLS traffic engineering capabilities to efficiently utilize the service provider network bandwidth, to control traffic placement, and to achieve fast network resilience. This is accomplished through IP-over-MPLS features. Table 101 displays the individual Brocade devices and the IP over MPLS features they support.
5 BGP shortcuts NOTE MPLS cannot be configured on the system globally when a NI-MLX-10Gx8-D card is installed. The following sections describe some of the procedures and considerations required when configuring a device to carry IP traffic over an MPLS network: • “BGP shortcuts” – This feature directs BGP to resolve a route nexthop to a MPLS LSP when one is available. • “LDP route injection” – This feature allows the user to make selected customer routes available though LDP created LSP tunnels.
BGP shortcuts 5 Native IP forwarding When next-hop MPLS is disabled, BGP uses the default BGP decision process and native IP forwarding to build BGP EMCP routes. Next-hop MPLS For each unique BGP next hop, when next-hop MPLS is enabled, BGP first determines when an LSP can be used to resolve the route. When BGP can resolve the route, it does not check the native IP routing table.
5 BGP shortcuts • Enabling next-hop MPLS (LSP metric becomes fixed at 1) • Enabling compare-LSP-metric (so IGP metric is compared with user-configurable LSP metric) • Disabling next-hop MPLS Enable next-hop MPLS using the next-hop-mpls command, as the following example illustrates. The follow-up show command of the running configuration indicates the global enabling of this feature.
BGP shortcuts 5 • Enable next-hop MPLS and observe the effect on the route to 10.8.8.1/32. • Enable LSP-metric comparison and note that, because of the metric for LSP to22, it has no effect on the routing table. • Change the metric for an LSP (to2 in this example). • Disable LSP-metric compare and check the consequences. • Disable global next-hop MPLS Specifying metrics This step specifies metrics for three LSPs.
5 BGP shortcuts Brocade(config-mpls)# router bgp Brocade(config-bgp)# maximum 5 Brocade(config-bgp)# show ip route Total number of IP routes: 5 Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric ISIS Codes - L1:Level-1 L2:Level-2 OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link Destination Gateway Port Cost Type Uptime 1 10.1.1.1/32 DIRECT loopback 1 0/0 D 9m46s 2 10.2.3.3/32 DIRECT loopback 2 0/0 D 9m46s 3 10.5.5.5/32 10.1.1.
BGP shortcuts 5 Brocade(config-bgp)# next-hop-mpls compare-lsp-metric Brocade(config-bgp)# show ip route Total number of IP routes: 5 Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric ISIS Codes - L1:Level-1 L2:Level-2 OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link Destination Gateway Port Cost Type Uptime 1 10.1.1.1/32 DIRECT loopback 1 0/0 D 11m30s 2 10.2.3.3/32 DIRECT loopback 2 0/0 D 11m30s 3 10.5.5.5/32 10.1.1.10 eth 1/1 1/1 S 11m19s 4 10.8.8.
5 LDP route injection Because global next-hop MPLS remains enabled and the LSP metrics are no longer a factor, all the LSPs are displayed in the routing table because BGP considers them to have equal cost.
LDP route injection 5 The LDP route injection feature allows the user to make routes available from the customer network through LSPs that have been created by LDP. The user can filter routes that the user wants to allow through the MPLS network using an ACL, and then apply that ACL to the advertise-labels for command. The routes injected are then accessible over the MPLS network.
5 LDP route injection Brocade# show mpls ldp database Session 10.3.3.3:0 - 10.5.5.2:0 Downstream label database: Label Prefix 1024 10.3.3.3/32 Upstream label database: Label Prefix 3 10.3.3.3/32 3 10.5.5.5/32 State Retained 3. The show ip route command displays routes available to ports on Router 1. Brocade# show ip route Total number of IP routes: 9 Type Codes - B:BGP D:Connected S:Static Destination Gateway 1 10.2.2.2/32 10.0.0.2 2 10.3.3.3/32 DIRECT 3 10.5.5.0/24 10.0.0.2 4 10.5.5.1/32 10.0.0.2 5 10.
Using traffic-engineered LSPs within an AS 5 Brocade(config)# show mpls ldp database Session 10.3.3.3:0 - 10.5.5.2:0 Downstream label database: Label Prefix State Upstream label database: Label Prefix 3 10.2.2.2/32 3 10.5.5.2/32 Displaying routes through LSP tunnels Once a network has been enabled to allow routes through LSP tunnels, the routes appear in the IP routing table. In the following example, the show ip route command displays a table that contains routes through LSP tunnels.
5 Using traffic-engineered LSPs within an AS The cost of the LSP is the user-configured metric for the LSP. When there is no user-configured metric, the underlying IP cost of the LSP is used. For example, when the IP cost of the best underlying path between two routers is 2, and there is an LSP configured between these two routers, the cost of the LSP is 2.
BGP MPLS metric follow IGP 5 This feature points OSPF routes to routes from the configured egress router of the LSP tunnel. By way of the LSP interface, the ingress router points to routes on the egress router (including downstream external or summary routes). To view these routes, enter the show ip route command as shown in the following example.
5 BGP MPLS metric follow IGP The RFE 3053 is mainly for BGP to set MED value as IGP cost and advertise out. This feature has the foundation for this for BGP routes resolving next hop to MPLS LSP tunnel. Then, a route-map is required to set BGP MED value to IGP metric by set metric-type internal. Feature information • The two options compare-lsp-metric and follow-igp are mutually exclusive. Because one option uses MPLS metric value, the other uses IGP metric.
IS-IS shortcuts 5 Displaying show command These commands display the configuration. Brocade(config)# show running config Brocade(config)# show ip bgp config To check BGP next hop resolution and the IGP cost for the next hop, use this show command. Brocade(config)# show ip bgp next-hop This command checks the RTM entry cost value to determine whether BGP next hop resolution takes the IGP cost value, compare to MPLS LSP metric value.
5 IS-IS shortcuts The announce metric and relative metric are described in detail in the following sections. Use the show isis shortcuts command to display the metric used to determine the cost. The announce metric When IS-IS shortcuts are enabled on an LSP tunnel, the MPLS router does not announce (advertise) the IS-IS shortcuts unless specifically configured to do so.
IS-IS shortcuts 5 • The IS-IS native route has a better metric than the LSP tunnel. • Another shortcut has a better metric than the LSP tunnel. Configuration notes Consider the following configuration notes: • IS-IS shortcuts require MPLS and IS-IS Traffic Engineering (TE) to be enabled. • IS-IS does not use an LSP tunnel as a shortcut when the To address of the tunnel is not the router ID of the destination router.
5 IS-IS shortcuts Configuration tasks It is recommended that the user performs the configuration tasks in the order listed in Table 102. TABLE 102 Configuration tasks for IS-IS shortcuts Configuration task Default behavior See...
IS-IS shortcuts 5 To enable announce, enter the following command on an LSP that is not yet enabled. Brocade(config-mpls-lsp-tomu3)# shortcuts isis level2 announce When the tunnel is enabled, disable it before enabling announce, then re-enable the tunnel. For example.
5 IS-IS shortcuts This command sets the relative metric value to -5. The LSP cost is determined by subtracting 5 from the native IGP cost to reach the tunnel destination. Using this example, when the native IGP cost is 10, the relative metric value -5 sets the LSP cost to 5. NOTE The shortcut cost is never a value less than 1. For example, when the native IGP cost is 10 and the relative metric is -15, the shortcut cost is 1, not -5.
IS-IS shortcuts 5 mu1(config-mpls)# show ip route isis Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric ISIS Codes - L1:Level-1 L2:Level-2 OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link Destination Gateway Port Cost Type Uptime 1 2 3 4 5 6 7 0.0.0.0/0 10.2.1.0/24 10.3.1.0/24 10.4.1.1/32 10.2.2.2/32 10.1.0.0/16 10.2.1.1/32 10.1.1.1 10.1.1.1 10.1.1.1 10.1.1.1 10.1.1.1 DIRECT 10.1.1.
5 IS-IS shortcuts Brocade(config-mpls)# show isis database mu1.00-00 detail IS-IS Level-2 Link State Database LSPID Seq Num Checksum Holdtime mu1.00-00* 0x00000010 0xd938 35 Area Address: 47 NLPID: IPv6 IP Hostname: mu1 TE Router ID: 10.1.1.1 Metric: 10 IP-Extended 10.1.1.0/24 Up: 0 Subtlv: 0 Metric: 10 IP-Extended 10.2.1.0/24 Up: 0 Subtlv: 0 Metric: 1 IP-Extended 10.1.2.0/24 Up: 0 Subtlv: 0 Metric: 1 IP-Extended 10.1.3.0/24 Up: 0 Subtlv: 0 Metric: 1 IP-Extended 10.1.4.
IS-IS shortcuts 5 • clear isis shortcut lsp lsp-name – This command clears IS-IS shortcuts for the specified LSP. Syntax: clear isis shortcut [lsp lsp-name] Ignore LSP metric The Ignore LSP Metric feature, when enabled, forces IGP protocols not to use configured LSP metric values for IS-IS and OSPF shortcuts when performing SFP calculations. Enabling this feature causes the shortcut’s effective metric to be derived by summing up all the path’s cost spanned over by the shortcut.
5 IS-IS shortcuts The following example shows a sample configuration of the Ignores LSP metric feature: R2(config-mpls)# lsp lsp100 R2(config-mpls-lsp-lsp100)# disable Disconnecting signaled LSP lsp100 R2(config-mpls-lsp-lsp100)# shortcut isis level2 ignore-lsp-metric R2(config-mpls-lsp-lsp100)# enable Connecting signaled LSP lsp100 R2(config-mpls)# show isis shortcut detail Configured:1 Up: 1, Announced: 0 L2 lsp lsp100 To 10.1.1.
5 IS-IS shortcuts Brocade# show isis shortcuts Configured: 3, Up: 2, Announced: 1 Name To lsp tomu2 lsp tomu3 lsp toolong toreachmu3 Metric (SPF/Announce) 10/-/10/10 10.4.1.1 10.3.1.1 10.20.1.1 Announce No Yes Yes Tunnel Intf tnl1 tnl2 tnl3 Syntax: show isis shortcuts [lsp lsp-name] The optional lsp parameter displays information about IS-IS shortcuts for a specific LSP. Table 103 describes the fields shown in this output. TABLE 103 Output for the show is-is shortcuts command This field...
5 IS-IS shortcuts • How long the LSP has been an IS-IS shortcut The following shows output from this command. Brocade# show isis shortcuts lsp tomu2 detail lsp tomu2 To 10.1.1.1, Used by SPF (10), Not Announced LSP metric: 10, Relative Metric: -, Announce Metric: ISIS System Id for 10.4.1.1 is mu2.00-00 Not announced due to configuration Last notification from MPLS received 0h0m35s ago. NOTE The LSP name in this output is not wrapped.
IS-IS shortcuts TABLE 104 5 Output for the show isis shortcuts detail command This field... Displays Not announced due to configuration Indicates that announce is not configured. Last notification from MPLS received The last time (in hours, minutes, seconds) a status notification was received from MPLS.
5 QoS mapping between IP packets and MPLS QoS mapping between IP packets and MPLS The 3-bit EXP field in the MPLS header can be used to define a Class of Service (CoS) value for packets the traverse an LSP. The CoS value specifies a priority for MPLS packets. There are two ways that a CoS value can be applied to packets that traverse an MPLS network through an LSP: • A CoS value is manually configured for the LSP. This is the default operation.
IP over MPLS statistics 5 Syntax: show mpls ldp traffic Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02 611
5 612 IP over MPLS statistics Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
Chapter 6 Configuring BGP or MPLS VPNs Overview Table 106 displays the individual Brocade devices and the BGP or MPLS VPN features they support. NOTE On Brocade NetIron CES devices, both ME_PREM and L3_PREM licenses are required to support L3 VPN.
6 Overview TABLE 106 614 Supported BGP or MPLS VPN features (Continued) Features supported Brocade Brocade NetIron XMR MLX Series Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package ECMP forwarding for IP VPN Yes Yes No aYes aYes No Yes Autonomous System Number Override Yes Yes No aYes a
6 What is a BGP or MPLS VPN TABLE 106 Supported BGP or MPLS VPN features (Continued) Features supported Brocade Brocade NetIron XMR MLX Series Series Brocade NetIron CES 2000 Series BASE package Brocade NetIron CES 2000 Series ME_PREM package Brocade NetIron CES 2000 Series L3_PREM package Brocade NetIron CER 2000 Series Base package Brocade NetIron CER 2000 Series Advanced Services package Displaying BGP or MPLS VPNv4 Information Yes Yes No aYes aYes No Yes IPv4 VPN CAM Optimization Yes
6 What is a BGP or MPLS VPN common MPLS-domain, multiple Virtual Private Networks (VPNs) can be configured across a service-provider MPLS core network. Each VPN provides a secure data path that allows IP packetized traffic to share the infrastructure while being effectively segregated from other VPNs that are using the same MPLS domain. In Figure 62, four separate customers (1-4) each have remote sites.
BGP or MPLS VPN components and what they do 6 BGP RFC 1771 – A Border Gateway Protocol 4 (BGP-4) RFC 1997 – BGP Communities Attribute RFC 2283 – Multiprotocol Extensions for BGP-4 RFC 2842 – Capabilities Advertisement with BGP-4 RFC 2858 – Multiprotocol Extensions for BGP-4 RFC 3107 – Carrying Label Information in BGP-4 Draft standards draft-ietf-idr-route-filter-11 draft-ietf-idr-bgp-ext-communities-07 MIB support RFC 4382 – MPLS or BGP Layer 3 Virtual Private Network (VPN) Management Information Base
6 BGP or MPLS VPN operation Provider MPLS domain – The Provider MPLS domain is composed of Provider (P) devices. An MPLS domain can traverse more than one service provider’s MPLS network. The P devices do not store any VPN information; they just switch traffic from the ingress PE device along the LSP to the egress PE device.
BGP or MPLS VPN operation 6 The PE device is connected to the MPLS domain through one or more interfaces. The PE must advertise the routes that it has available in it’s VRF tables across the MPLS domain to its PE peers. Available routes in the VRF are prepended with a Route Distinguisher (RD) and advertised across the MPLS domain using IBGP. The PEs can either be configured for IBGP as either full mesh or with a route reflector to allow greater scalability.
6 Configuring BGP VPNs on a PE Configuring BGP VPNs on a PE To configure a BGP VPN on a Provider Edge device (PE) the user must perform the configuration steps listed below. 1. “Defining a VRF routing instance” 2. “Assigning a Route Distinguisher to a VRF” 3. “Defining IPv4 or IPv6 address families of a VRF” 4. “Defining automatic route filtering” 5. “Assigning a VRF routing instance to an interface” 6. “Assigning a VRF routing instance to a LAG interface” 7. “Setting up cooperative route filtering” 8.
Configuring BGP VPNs on a PE 6 13. “Configuring a PE to allow routes with its AS number” 14. “Setting up LSPs per VRF” 15. “Configuring OSPF sham links” 16. “Configuring OSPF on a PE device to redistribute BGP-VPNv4 routes” 17. “Generating traps for VRFs” Defining a VRF routing instance A single PE can contain one or more VRFs. Each of these VRFs must be defined separately on a PE. A PE distributes routes and route packets to other members of the same VRF but not to other VRFs.
6 Configuring BGP VPNs on a PE The route_distinguisher variable specifies a route distinguisher for a VRF that gives a route associated with the VRF a unique identity. The RD is prepended on the address being advertised. The RD allows the same IP address to be used in different VPNs without creating any conflicts. It can also be used with the route-target command to constrain distribution of routes to or from a VPN.
Configuring BGP VPNs on a PE 6 The import parameter specifies that routes with route-target extended community attributes matching the specified route-target variable can be imported into the VRF where this command is configured. The export parameter specifies the route-target extended community attributes that are attached to routes export from the specified VRF.
6 Configuring BGP VPNs on a PE Brocade(config)# lag red dynamic Brocade(config-lag-red)# ports ethernet 1/1 to 1/2 Brocade(config-lag-red)# primary port 1/1 Brocade(config-lag-red)# ports ethernet 1/2 Brocade(config-lag-red)# deploy Brocade(config-lag-red)# exit Brocade(config)# interface ethernet 1/1 Brocade(config-if-e10000-1/1)# vrf forwarding VPN1 When the dynamic LAG named “red” is undeployed as shown in the following, port 1/1 remains in the VRF routing instance named “VPN1” but port 1/2 is returne
Configuring BGP VPNs on a PE 6 Route maps applied to a VRF can coexist with route maps that are applied to a BGP neighbor. The user can filter routes from being imported into a VRF using the import and export route commands. This allows the user to accept or deny the routes for one VRF without affecting the routes that are imported or exported from other VRFs. To do this, the user must define a route-map import or export command.
6 Configuring BGP VPNs on a PE The rt route ID variable specifies the route target that is applied to filtering. The route ID has the format of either ASN:nn or IP-address:nn. When four-byte ASNs have been enabled or when four-byte IP addresses are used, the user-purposed nn value can be a maximum of two bytes instead of our bytes. The soo route ID variable specifies the site of origin. The route ID has the format of either ASN:nn or IP-address:nn.
Configuring BGP VPNs on a PE 6 The group-num variable refers to an extended community list number from 1 to 99 that specifies the routes that the user wants to filter. Configuring BGP VRF load sharing The default for each VRF is to maintain only the lowest-cost route in its routing table for each VPN that it is connected to. When a lower-cost route is discovered, it replaces the route that is currently in the table. When another route of equal cost is discovered, it is rejected.
6 Configuring BGP VPNs on a PE When configuring ECMP hardware forwarding, all outgoing paths must configured in the same VRF. A hash value is computed for a packet when it is received by XPP. XPP uses the hash value to select a PRAM that is used to forward the packet to its destination. An ECMP PRAM block consists of 8 PRAMs.
Configuring BGP VPNs on a PE 6 Brocade(config-bgp-ipv4u-vrf)# neighbor 10.33.36.2 allowas-in 3 Syntax: [no] neighbor IPaddress allowas-in asn_limit The IPaddress is the IP address of the neighbor CE device from which the PE device can accept routes that have the same AS number. The asn_limit value prevents loops by limiting the number of occurrences that the PEs AS number can be accepted in routes that are received from the specified device.
6 Configuring BGP VPNs on a PE Configuring OSPF sham links OSPF can be used to propagate links between a Customer Edge device (CE) and a Provider Edge device (PE). Normal operation of this type of network assumes that the only connections between CEs pass through the provider network. However, when other links or routes between the CEs exist within the same area, problems can arise due to the OSPF preference for Intra-area links over Inter-area links.
Configuring BGP VPNs on a PE 6 The following illustrates the configuration that takes place first on PE1 and then on PE2: Sham link configuration on PE1 router ospf vrf CustomerA area 1 area 1 sham-link 172.31.255.1 172.31.255.2 cost 1 redistribution bgp interface loopback 2 vrf forwarding CustomerA ip address 172.31.255.1/32 ! Brocade# show ip route vrf CustomerA 172.31.255.
6 Configuring BGP VPNs on a PE Syntax: [no] router ospf vrf vrf_name The vrf_name value specifies the name of the VRF that the user is creating an instance of OSPF in. Creating an OSPF area in an OSPF VRF instance NOTE This features is not supported on Brocade NetIron CES or Brocade NetIron CER devices. To create OSPF area 1 in OSPF VRF instance VPN1, enter the following command in the OSPF VRF Instance Config level.
Configuring BGP VPNs on a PE 6 When not specified, the domain-tag value is calculated from the autonomous system number of the MPLS domain. Adding a static ARP entry for a VRF NOTE This features is not supported on Brocade NetIron CES or Brocade NetIron CER devices. To configure a static ARP entry to a VRF enter the following command at the global configuration level. Brocade(config)# arp vrf green 192.168.201.2 2001:DB8.52cf.
6 Configuring BGP VPNs on a PE Configuring IP TTL to MPLS TTL propagation in an IPVPN The vrf-propagate-ttl and label-propagate-ttl commands configure the device to propagate TTL values in an IPVPN between the IP TTL value and the MPLS TTL value, as described in Table 107 and Table 108. TABLE 107 MPLS TTL propagation behavior with IPVPNs on Brocade NetIron XMR and Brocade MLX series.
Configuring BGP VPNs on a PE 6 TABLE 108 MPLS TTL propagation behavior with IPVPNs on the Brocade NetIron CES and Brocade NetIron CER devices NOTE: The no label-propagate-ttl and vrf-propagate-ttl commands are not supported on the NetIron CES and NetIron CER devices. The propagation of TTL from IP VPN to MPLS and from MPLS to IP VPN is controlled by propagate-ttl command.
6 Configuring BGP VPNs on a PE Configuring a static route within the VRF context NOTE This features is not supported on Brocade NetIron CES or Brocade NetIron CER devices. To configure a static route entry in a VRF, enter the following command. Brocade(config)# vrf blue Brocade(config-vrf-blue)# ip route 10.0.0.0 255.0.0.0 10.1.1.1 Syntax: [no] ip route dest-ip-addr/mask-bits | next-hop-ip-addr [metric] The dest-ip-addr is the route’s destination.
Configuring BGP VPNs on a PE 6 6. Activate the virtual interface DANGER The user must configure a VRF on an interface before configuring a Virtual Router (VRRP-E) on it. When the user enables the Virtual Router before the user enables the VRF, the Virtual Router configuration is deleted. Configuration example The following example configures a backup virtual device using VRRPE for VRF “blue” on an Ethernet interface.
6 Configuring BGP VPNs on a PE Syntax: traceroute vrf vrf-name | ip-address The vrf-name is the name of the VRF that the user wants to conduct a traceroute to. The ip-address is the IP address containing the VRF to which the user wants to conduct a traceroute. Generating traps for VRFs The user can enable and disable SNMP traps for VRFs. VRF traps are enabled by default. To enable VRF traps after they have been disabled, enter the following command.
Displaying BGP or MPLS VPNv4 information 6 Displaying BGP or MPLS VPNv4 information The user can display the following information about a BGP or MPLS VPN configuration on the device: • • • • • • • • • • • • • • • • • “Displaying VPNv4 route information” “Displaying VPNv4 route information for a specified IP address” “Displaying VPNv4 attribute entries information” “Displaying VPNv4 dampened paths information” “Displaying VPNv4 filtered routes information” “Displaying VPNv4 Flap statistics information”
6 Displaying BGP or MPLS VPNv4 information Displaying VPNv4 route information The user can display route information about VPNv4 routes by entering the following command at any level of the CLI. Brocade# show ip bgp vpnv4 Total number of BGP VPNv4 Routes: 285 Status codes: s suppressed, d damped, h history, * valid, > best, i internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 1:1 *i 10.80.1.1/32 10.2.2.2 100 0 206 311 i *i 10.80.1.
Displaying BGP or MPLS VPNv4 information 6 TABLE 109 BGP4 summary information This field... Displays... Total number of BGP VPNv4 Routes: The number of BGP VPNv4 routes. Status or Status Codes The route’s status, which can be one or more of the following: • A – AGGREGATE. The route is an aggregate route for multiple networks. • B – BEST. BGP4 has determined that this is the optimal route to the destination.
6 Displaying BGP or MPLS VPNv4 information TABLE 109 BGP4 summary information (Continued) This field... Displays... Weight The value that this route associates with routes from a specific neighbor. For example, when the device receives routes to the same destination from two BGP4 neighbors, the device prefers the route from the neighbor with the larger weight. Path The routes AS path. To clear the VPNv4 routing table, the user must enter the following commands.
Displaying BGP or MPLS VPNv4 information 6 Displaying VPNv4 attribute entries information The route-attribute entries table lists the sets of BGP VPNv4 attributes stored in the device memory. Each set of attributes is unique and can be associated with one or more routes. In fact, the device typically has fewer route attribute entries than routes. To display the route-attribute entries table at any level of the CLI.
6 Displaying BGP or MPLS VPNv4 information TABLE 111 BGP VPNv4 attribute entries (Continued) This field... Displays... Cluster List The route-reflector clusters through which this set of attributes has passed. Aggregator Aggregator information: • AS Number shows the AS in which the network information in the attribute set was aggregated. This value applies only to aggregated routes and is otherwise 0.
Displaying BGP or MPLS VPNv4 information 6 The address / mask parameter specifies a particular route. When the user also uses the optional longer-prefixes parameter, then all statistics for routes that match the specified route or have a longer prefix than the specified route are displayed. For example, when the user specifies 10.157.0.0 longer, then all routes with the prefix 10.157 or that have a longer prefix (such as 10.157.22) are displayed.
6 Displaying BGP or MPLS VPNv4 information TABLE 113 BGP VPNv4 route distinguisher entries This field... Displays... Total number of BGP Routes The number of routes contained in the BGP4 route table that contain the specified RD. Prefix The network address and prefix. Age The last time an update occurred. Learned from Peer The IP address of the neighbor that sent this route. Out-Label MPLS label associated with this device. MED The route’s metric.
Displaying BGP or MPLS VPNv4 information 6 The TCP statistics at the end of the display show status for the TCP session with the neighbor. Most of the fields show information stored in the Transmission Control Block (TCB) for the TCP session between the device and a neighbor. These fields are described in detail in section 3.2 of RFC 793, “Transmission Control Protocol Functional Specification”.
6 Displaying BGP or MPLS VPNv4 information • Number of routes received from the neighbor • Number of routes accepted by this device from the neighbor • Number of routes this device filtered out of the UPDATES received from the neighbor and did not accept • Number of routes advertised to the neighbor • Number of attribute entries associated with routes received from or advertised to the neighbor This display shows the following information. TABLE 114 BGP4 neighbor information This field... Displays...
Displaying BGP or MPLS VPNv4 information 6 TABLE 114 BGP4 neighbor information (Continued) This field... Displays... Time The amount of time this session has been in its current state. KeepAliveTime The KeepAliveTime, which specifies how often this device sends keep alive messages to the neighbor. HoldTime The hold time, which specifies how many seconds the device waits for a KEEPALIVE or UPDATE message from a BGP4 neighbor before deciding that the neighbor is dead.
6 650 Displaying BGP or MPLS VPNv4 information TABLE 114 BGP4 neighbor information (Continued) This field... Displays... Last Connection Reset Reason The reason the previous session with this neighbor ended.
Displaying BGP or MPLS VPNv4 information 6 TABLE 114 BGP4 neighbor information (Continued) This field... Displays... Notification Sent When the device receives a NOTIFICATION message from the neighbor, the message contains an error code corresponding to one of the following errors. Some errors have subcodes that clarify the reason for the error. Where applicable, the subcode messages are listed underneath the error code messages.
6 652 Displaying BGP or MPLS VPNv4 information TABLE 114 BGP4 neighbor information (Continued) This field... Displays... TCP Connection state The state of the connection with the neighbor. The connection can have one of the following states: • LISTEN – Waiting for a connection request. • SYN-SENT – Waiting for a matching connection request after having sent a connection request.
Displaying BGP or MPLS VPNv4 information TABLE 114 BGP4 neighbor information (Continued) This field... Displays... TotalRcv The number of sequence numbers received from the neighbor. DupliRcv The number of duplicate sequence numbers received from the neighbor. RcvWnd The size of the receive window. SendQue The number of sequence numbers in the send queue. RcvQue The number of sequence numbers in the receive queue. CngstWnd The number of times the window has changed.
6 Displaying BGP or MPLS VPNv4 information Brocade# show ip bgp vpnv4 neighbors 10.2.2.2 attribute-entries Total number of BGP Attribute Entries: 35 1 Next Hop :0.0.0.0 Metric :0 Origin:IGP Originator:0.0.0.0 Cluster List:None Aggregator:AS Number :0 Router-ID:0.0.0.0 Atomic:None Local Pref:100 Communities:Internet Extended Community: RT 600:1 AS Path :310 Address: 0x247194b0 Hash:45 (0x0100036e) Reference Counts: 0:0:30 2 Next Hop :0.0.0.0 Metric :0 Origin:IGP Originator:0.0.0.
Displaying BGP or MPLS VPNv4 information TABLE 115 6 BGP4 route-attribute entries information (Continued) This field... Displays... Atomic Whether the network information in this set of attributes has been aggregated and this aggregation has resulted in information loss: • TRUE – Indicates information loss has occurred • FALSE – Indicates no information loss has occurred NOTE: Information loss under these circumstances is a normal part of BGP4 and does not indicate an error.
6 Displaying BGP or MPLS VPNv4 information Displaying received ORFs information for a specified VPNv4 neighbor To view BGP4 configuration information and statistics for a specified VPNv4 neighbor, enter the following command. Brocade# show ip bgp vpn neighbors 10.2.2.2 received extended-community Extended-community ORF capability was not negotiated No Prefix filter ORF received from neighbor 10.2.2.
Displaying BGP or MPLS VPNv4 information 6 Displaying the best routes that were nonetheless not installed in the IP route table To display the BGP4 routes received from a specific neighbor that are the “best” routes to their destinations but are not installed in the device’s IP route table, enter a command such as the following at any level of the CLI. Brocade# show ip bgp vpnv4 neighbor 192.168.4.
6 Displaying BGP or MPLS VPNv4 information Brocade# show ip bgp vpnv4 neighbor 10.10.2.3 rib-out-routes There are 154 RIB_out routes for neighbor 10.10.2.3 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST E:EBGP I:IBGP L:LOCAL Prefix Next Hop Metric LocPrf Weight 1 10.100.101.30/32 10.10.3.3 100 0 AS_PATH: 311 2 10.100.101.29/32 10.10.3.3 100 0 AS_PATH: 311 3 10.100.101.28/32 10.10.3.3 100 0 AS_PATH: 311 4 10.100.101.27/32 10.10.3.3 100 0 AS_PATH: 311 5 10.100.101.26/32 10.10.3.3 100 0 AS_PATH: 311 6 10.
Displaying BGP or MPLS VPNv4 information TABLE 117 6 BGP4 route summary information for a VPNv4 neighbor This field... Displays... Routes Accepted or Installed How many routes the has received from the neighbor during the current BGP4 session: • Filtered – Indicates how many of the received routes the device filtered and did not accept. • Filtered or kept – Indicates how many of the received routes the device did not accept or install because they were denied by filters.
6 Displaying BGP or MPLS VPNv4 information TABLE 117 BGP4 route summary information for a VPNv4 neighbor (Continued) This field... Displays... NLRIs Sent in Update Message The number of NLRIs for new routes the has sent to this neighbor in UPDATE messages: • Withdraws – The number of routes the device has sent to the neighbor to withdraw. • Replacements – The number of routes the device has sent to the neighbor to replace routes the neighbor already has.
6 Displaying BGP or MPLS VPNv4 information TABLE 118 BGP VPNv4 summary route information (Continued) This field... Displays... Routes originated by this device The number of VPNv4 routes in the BGP route table that this device originated. Routes selected as BEST routes The number of VPNv4 routes in the BGP route table that this device has selected as the best routes to the destinations.
6 Displaying BGP or MPLS VPNv4 information The age secs parameter displays only the routes that have been received or updated more recently than the number of seconds the user specifies. The as-path-access-list num parameter filters the display using the specified AS-path ACL. The best parameter displays the routes received from the neighbor that the device selected as the best routes to their destinations.
Displaying BGP or MPLS VPNv4 information 6 Brocade(config-bgp-router)# show ip bgp vpnv4 routes best Total number of BGP Routes: 28 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED F:FILTERED Prefix Next Hop Metric LocPrf Weight Status Route Distinguisher: 4:1 1 3.0.0.0/8 192.168.4.106 100 0 BE AS_PATH: 65001 4355 701 80 2 4.0.0.0/8 192.168.4.106 100 0 BE AS_PATH: 65001 4355 1 3 4.60.212.0/22 192.168.4.
6 Displaying BGP or MPLS VPNv4 information Displaying VPNv4 routes with unreachable destinations To display BGP VPNv4 routes whose destinations are unreachable using any of the paths in the BGP route table, enter a command such as the following at any level of the CLI. Brocade(config-bgp-router)# show ip bgp vpnv4 routes unreachable Searching for matching routes, use ^C to quit...
Displaying BGP or MPLS VPNv4 information 6 Brocade# show ip bgp vpnv4 routes detail Total number of BGP Routes: 288 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED Route Distinguisher: 4:1 1 Prefix: 10.6.1.0/24, Status: I, Age: 15h36m10s NEXT_HOP: 10.2.2.2, Learned from Peer: 10.2.2.2 (1) Out-Label: 500000 LOCAL_PREF: 100, MED: 3, ORIGIN: incomplete, Weight: 0 AS_PATH: Extended Community: RT 300:1 OSPF DOMAIN ID:0.0.0.
6 Displaying BGP or MPLS VRF information Displaying BGP VPNv4 MPLS tag information To display the MPLS in-label and out-label tags in the VPNv4 routes, enter a command such as the following at any level of the CLI. Brocade# show ip bgp vpnv4 tags Network Next Hop Route Distinguisher: 1:1 10.80.1.1/32 10.2.2.2 10.80.1.2/32 10.2.2.2 10.80.1.3/32 10.2.2.2 10.80.1.4/32 10.2.2.2 10.80.1.5/32 10.2.2.2 10.80.1.6/32 10.2.2.2 10.80.1.7/32 10.2.2.2 10.80.1.8/32 10.2.2.
Displaying BGP or MPLS VRF information 6 • “Displaying summary route information for a specified VRF” • “Displaying a VRFs BGP4 route table” Displaying VRF route information The user can display information about BGP routes that are contained within a specified VRF route table by entering a command such as the following at any level of the CLI.
6 Displaying BGP or MPLS VRF information TABLE 121 BGP4 summary information (Continued) This field... Displays... Origin code A character the display uses to indicate the route’s origin. The origin code appears to the right of the AS path (Path field). The origin codes are described in the command’s output. RD The Route Distinguisher. A unique ID that is prepended on any address being routed or advertised from a VRF.
Displaying BGP or MPLS VRF information 6 Brocade# show ip bgp vrf green 10.2.2.0/24 Route Distinguisher: 2:1 Number of BGP Routes matching display condition : 1 Status codes: s suppressed, d damped, h history, * valid, > best, i internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *i 10.2.2.0/24 10.4.4.4 1 100 0 ? Route is advertised to 2 peers: 10.4.4.4(1) 10.2.2.
6 Displaying BGP or MPLS VRF information Brocade# show ip bgp vrf green attribute-entries Total number of BGP Attribute Entries: 26 1 Next Hop :192.168.201.2 Metric :1 Origin:INCOMP Originator:0.0.0.0 Cluster List:None Aggregator:AS Number :0 Router-ID:0.0.0.0 Atomic:None Local Pref:100 Communities:Internet AS Path : Address: 0x247017ec Hash:279 (0x03000000) Reference Counts: 1:0:0 2 Next Hop :192.168.201.2 Metric :2 Origin:INCOMP Originator:0.0.0.0 Cluster List:None Aggregator:AS Number :0 Router-ID:0.0.
Displaying BGP or MPLS VRF information TABLE 123 BGP VPNv4 attribute entries (Continued) This field... Displays... Atomic Whether the network information in this set of attributes has been aggregated and this aggregation has resulted in information loss: • TRUE – Indicates information loss has occurred • FALSE – Indicates no information loss has occurred 6 NOTE: Information loss under these circumstances is a normal part of BGP4 and does not indicate an error.
6 Displaying BGP or MPLS VRF information The neighbor ip-addr parameter displays route flap dampening statistics only for routes learned from the specified neighbor. The user also can display route flap statistics for routes learned from a neighbor by entering the following command: show ip bgp neighbor ip-addr flap-statistics. The regular-expression regular-expression parameter is a regular expression. The regular expressions are the same ones supported for BGP4 AS-path filters.
Displaying BGP or MPLS VRF information 6 The TCP statistics at the end of the display show status for the TCP session with the neighbor. Most of the fields show information stored in the device’s Transmission Control Block (TCB) for the TCP session between the Brocade device and its neighbor. These fields are described in detail in section 3.2 of RFC 793, “Transmission Control Protocol Functional Specification”.
6 Displaying BGP or MPLS VRF information The routes-summary option displays a summary of the following information: • Number of routes received from the neighbor • Number of routes accepted by this Brocade device from the neighbor • Number of routes this Brocade device filtered out of the UPDATES received from the neighbor and did not accept • Number of routes advertised to the neighbor • Number of attribute entries associated with routes received from or advertised to the neighbor.
Displaying BGP or MPLS VRF information TABLE 125 6 BGP4 neighbor information (Continued) This field... Displays... State The state of the Brocade device’s session with the neighbor. The states are from this Brocade device’s perspective of the session, not the neighbor’s perspective. The state values are based on the BGP4 state machine values described in RFC 1771 and can be one of the following for each router: • IDLE – The BGP4 process is waiting to be started.
6 Displaying BGP or MPLS VRF information TABLE 125 BGP4 neighbor information (Continued) This field... Displays... Distribute-list Lists the distribute list parameters, when configured. Filter-list Lists the filter list parameters, when configured. Prefix-list Lists the prefix list parameters, when configured. Route-map Lists the route map parameters, when configured. Messages Sent The number of messages this Brocade device has sent to the neighbor.
Displaying BGP or MPLS VRF information TABLE 125 6 BGP4 neighbor information (Continued) This field... Displays... Last Connection Reset Reason (cont.) • Notification Sent When the Brocade device receives a NOTIFICATION message from the neighbor, the message contains an error code corresponding to one of the following errors. Some errors have subcodes that clarify the reason for the error. Where applicable, the subcode messages are listed underneath the error code messages.
6 Displaying BGP or MPLS VRF information TABLE 125 678 BGP4 neighbor information (Continued) This field... Displays... TCP Connection state The state of the connection with the neighbor. The connection can have one of the following states: • LISTEN – Waiting for a connection request. • SYN-SENT – Waiting for a matching connection request after having sent a connection request.
Displaying BGP or MPLS VRF information TABLE 125 6 BGP4 neighbor information (Continued) This field... Displays... RcvWnd The size of the receive window. SendQue The number of sequence numbers in the send queue. RcvQue The number of sequence numbers in the receive queue. CngstWnd The number of times the window has changed.
6 Displaying BGP or MPLS VRF information Brocade# show ip bgp vrf black neighbor 10.10.2.3 attribute-entries Total number of BGP Attribute Entries: 2 1 Next Hop :10.10.2.3 Metric :0 Origin:IGP Originator:0.0.0.0 Cluster List:None Aggregator:AS Number :0 Router-ID:0.0.0.0 Atomic:None Local Pref:100 Communities:Internet AS Path :310 Address: 0x2470139c Hash:223 (0x0100036e) Reference Counts: 30:0:60 2 Next Hop :10.2.2.2 Metric :2 Origin:INCOMP Originator:0.0.0.
Displaying BGP or MPLS VRF information TABLE 126 6 BGP4 route-attribute entries information (Continued) This field... Displays... Atomic Whether the network information in this set of attributes has been aggregated and this aggregation has resulted in information loss: • TRUE – Indicates information loss has occurred • FALSE – Indicates no information loss has occurred NOTE: Information loss under these circumstances is a normal part of BGP4 and does not indicate an error.
6 Displaying BGP or MPLS VRF information Brocade # show ip bgp vrf black neighbor 10.10.2.3 received extended-community Extended-community ORF capability was not negotiated Brocade# show ip bgp vrf black neighbor 10.10.2.3 received prefix-filter No Prefix filter ORF received from neighbor 10.10.2.3! Displaying received routes for a specified VRF neighbor To view the BGP4 VPNv4 configuration and statistics for specified VRFs neighbor, enter the following command.
Displaying BGP or MPLS VRF information 6 Syntax: show ip bgp vrf vrf-name neighbor ip-addr routes best For information about the fields in this display, refer to Table 121 on page 667. Displaying the best routes that were nonetheless not installed in the IP route table To display the BGP4 routes received from a specific neighbor that are the “best” routes to their destinations but are not installed in the Brocade device’s IP route table, enter a command such as the following at any level of the CLI.
6 Displaying BGP or MPLS VRF information Brocade# show ip bgp vrf black neighbor 10.10.2.3 rib-out-routes There are 154 RIB_out routes for neighbor 10.10.2.3 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST E:EBGP I:IBGP L:LOCAL Prefix Next Hop Metric LocPrf Weight 1 10.100.101.30/32 10.10.3.3 100 0 AS_PATH: 311 2 10.100.101.29/32 10.10.3.3 100 0 AS_PATH: 311 3 10.100.101.28/32 10.10.3.3 100 0 AS_PATH: 311 4 10.100.101.27/32 10.10.3.3 100 0 AS_PATH: 311 5 10.100.101.26/32 10.10.3.3 100 0 AS_PATH: 311 6 10.
Displaying BGP or MPLS VRF information 6 This display shows the following information. TABLE 128 BGP4 route summary information for a VRF neighbor This field... Displays... Routes Received How many routes the Brocade device has received from the neighbor during the current BGP4 session. • Accepted or Installed – Indicates how many of the received routes the Brocade device accepted and installed in the BGP4 route table.
6 Displaying BGP or MPLS VRF information TABLE 128 BGP4 route summary information for a VRF neighbor (Continued) This field... Displays... NLRIs Sent in Update Message The number of NLRIs for new routes the Brocade device has sent to this neighbor in UPDATE messages: • Withdraws – The number of routes the Brocade device has sent to the neighbor to withdraw. • Replacements – The number of routes the Brocade device has sent to the neighbor to replace routes the neighbor already has.
Displaying BGP or MPLS VRF information TABLE 129 6 BGP VPNv4 summary route information (Continued) This field... Displays... Routes originated by this Brocade device The number of VPNv4 routes in the BGP route table that this Brocade device originated. Routes selected as BEST routes The number of VPNv4 routes in the BGP route table that this Brocade device has selected as the best routes to the destinations.
6 Displaying BGP or MPLS VRF information ip-addr] | [no-best] | [not-installed-best] | [prefix-list string] | [regular-expression regular-expression] | [route-map map-name] | [summary] | [unreachable] The vrf-name parameter specifies the VRF whose neighbor the user wants to display information about. The ip-addr option displays routes for a specific network. The num option specifies the table entry with which the user wants the display to start.
Displaying BGP or MPLS VRF information 6 The unreachable option displays the routes that are unreachable because the Brocade device does not have a valid RIP, OSPF, or static route to the next hop. For information about the fields in this display, refer to Table 109 on page 641. The fields in this display also appear in the show ip bgp vpnv4 display.
6 Displaying BGP or MPLS VRF information Brocade# show ip bgp vrf black routes not-installed-best Searching for matching routes, use ^C to quit... Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED F:FILTERED Route Distinguisher: 4:1 Prefix Next Hop Metric LocPrf Weight Status 1 10.0.0.0/8 192.168.4.
Displaying BGP or MPLS VRF information 6 Brocade# show ip bgp vrf black routes 10.8.1.0/24 Route Distinguisher: 4:1 Number of BGP Routes matching display condition : 1 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED F:FILTERED Prefix Next Hop Metric LocPrf Weight Status 1 10.8.1.0/24 10.2.2.
6 Displaying additional BGP or MPLS VPN information TABLE 130 BGP VPNv4 route information (Continued) This field... Displays... Origin The source of the route information. The origin can be one of the following: • EGP – The routes with this set of attributes came to BGP through EGP. • IGP – The routes with this set of attributes came to BGP through IGP. • INCOMPLETE – The routes came from an origin other than one of the above. For example, they may have been redistributed from OSPF or RIP.
Displaying additional BGP or MPLS VPN information • • • • • • • • • 6 “Displaying OSPF sham links” “Displaying OSPF trap status for a VRF” “Displaying OSPF virtual links for a VRF” “Displaying OSPF virtual neighbor information for a VRF” “Displaying IP extcommunity list information” “Displaying the IP static route table for a VRF” “Displaying the static ARP table for a VRF” “Displaying TCP connections for a VRF” “Displaying MPLS statistics for a VRF” Displaying VRF information To display IP Information
6 Displaying additional BGP or MPLS VPN information TABLE 131 Output from the show VRF command This field... Displays... VRF Name The name of the VRF. Default RD The default route distinguisher for the VRF. Table ID The table ID for the VRF. Routes The total number of IPv4 and IPv6 Unicast routes configured on this VRF. Label Display the unique VRF label that has been assigned to the specified VRF. Label Switched Mode Displays when Label Switched Mode is ON or OFF.
Displaying additional BGP or MPLS VPN information 6 Displaying the IP route table for a specified VRF To display the IP routes for a specified VRF, enter the following command at any CLI level. Brocade# show ip route vrf green Total number of IP routes: 99 Type Codes - B:BGP D:Connected S:Static Destination Gateway 1 10.5.1.0/24 192.168.201.2 2 10.6.1.0/24 10.4.4.4 3 10.8.1.0/24 10.2.2.2 4 10.30.1.1/32 192.168.201.2 5 10.30.1.2/32 192.168.201.2 6 10.30.1.3/32 192.168.201.2 7 10.30.1.4/32 192.168.201.
6 Displaying additional BGP or MPLS VPN information Displaying ARP VRF information To display the ARP information for a specified VRF, enter the following command. Brocade# show arp vrf green Total number of ARP entries: 9 Entries in VRF green: IP Address MAC Address 1 192.168.201.2 2001:DB8.52cf.
Displaying additional BGP or MPLS VPN information 6 Displaying OSPF area information for a VRF To display OSPF Area Information for a specified VRF, enter the following command at any level of the CLI.
6 Displaying additional BGP or MPLS VPN information Displaying general OSPF configuration information for a VRF To display OSPF ABR and ABSR Information for a specified VRF, enter the following command at any level of the CLI.
Displaying additional BGP or MPLS VPN information 6 Displaying OSPF external link state information for a VRF To display OSPF External Link State Information for a specified VRF, enter the following command at any level of the CLI. Brocade# show ip ospf vrf green database external-link-state Index Aging LS ID Router Netmask Metric 1 491 10.30.1.6 10.5.1.3 ffffffff 00000001 2 1005 10.40.1.30 192.168.201.1 ffffffff 8000000a 3 765 10.60.1.10 192.168.201.1 ffffffff 8000000a 4 1005 10.40.1.9 192.168.201.
6 Displaying additional BGP or MPLS VPN information Displaying OSPF link state information for a VRF To display OSPF Link State Information for a specified VRF, enter the following command at any level of the CLI. Brocade# show ip ospf vrf green database link-state Index Area ID Type LS ID Adv Rtr 1 0 Summ 10.2.10.2 192.168.201.1 2 0 Summ 192.168.201.0 192.168.201.1 3 0 Summ 10.8.1.0 192.168.201.1 4 0 Summ 10.5.1.0 192.168.201.1 5 0 ASBR 10.2.10.2 192.168.201.1 6 0 ASBR 10.5.1.3 192.168.201.1 7 1 Rtr 192.
Displaying additional BGP or MPLS VPN information 6 Displaying OSPF interface information To display OSPF interface information for a specified VRF, enter the following command at any CLI level. Brocade# show ip ospf vrf green interface ethernet 6/3,OSPF enabled IP Address 192.168.201.1, Area 1 OSPF state DR, Pri 1, Cost 1, Options 2, Type broadcast Events 3 Timers(sec): Transit 1, Retrans 5, Hello 10, Dead 40 DR: Router ID 192.168.201.1 Interface Address 192.168.201.1 BDR: Router ID 1.2.10.
6 Displaying additional BGP or MPLS VPN information Brocade# show ip ospf vrf green redistribute route 10.6.1.0 10.255.255.0 bgp 10.8.1.0 10.255.255.0 bgp 10.40.1.1 10.255.255.255 bgp 10.40.1.2 10.255.255.255 bgp In this example, four routes have been redistributed from BGP routes. Syntax: show ip ospf vrf vrf-name redistribute route The vrf-name parameter specifies the VRF that the user wants to display routes redistributed into OSPF for.
Displaying additional BGP or MPLS VPN information 6 The vrf-name variable identifies the VRF for which the user wants to display OSPF sham links information. Displaying OSPF trap status for a VRF To display the state (enabled or disabled) of the OSPF traps for a specified VRF, enter the following command at any CLI level.
6 Displaying additional BGP or MPLS VPN information Displaying OSPF virtual neighbor information for a VRF To display the OSPF virtual neighbor information for a specified VRF, enter the following command at any level of the CLI. Brocade# show ip ospf vrf green virtual neighbor Syntax: show ip ospf vrf vrf-name virtual neighbor [num] The vrf-name parameter specifies the VRF that the user wants to display OSPF virtual neighbor information for.
Displaying additional BGP or MPLS VPN information 6 Displaying IP extcommunity list information To display the IP Extcommunity information, enter the following command at any level of the CLI. Brocade# show ip extcommunity-list ip extcommunity access list 20: permit RT 100:1 Syntax: show ip extcommunity-list For information about the fields, refer to the following. TABLE 134 Output of show IP extcommunity list This field... Displays...
6 Displaying additional BGP or MPLS VPN information To clear the static ARP table in a VRF, enter the following command. Brocade# clear arp vrf blue Syntax: clear arp vrf vrf-name Displaying TCP connections for a VRF The show ip tcp vrf connections command displays information about each TCP connection on the VRF, including the local IP address, local port number, remote IP address, remote port number and the state of the connection. For example.
Displaying additional BGP or MPLS VPN information TABLE 135 6 Output from the show MPLS statistics VRF command This field... Displays... VRF Name The name of the VRF MPLS statistics are being collected for. In-Ports The port where the traffic is received. Endpt Out-Pkt The number of packets transmitted out of local endpoints. Tnl Out-Pkt The number of packets transmitted out of lsp tunnels. To clear the MPLS statistics counters.
6 Displaying additional BGP or MPLS VPN information Brocade# show ip rip vrf black RIP Summary Default port 520 Administrative distance is 120 Updates every 30 seconds, expire after 180 Holddown lasts 180 seconds, garbage collect after 120 Last broadcast 27, Next Update 29 Need trigger update 0, Next trigger broadcast 3 Minimum update interval 25, Max update Interval 5 Split horizon is on; poison reverse is off Import metric 1 Prefix List, Inbound : Not set Prefix List, Outbound : Not set Route-map, Inbou
BGP or MPLS VPN sample configurations 6 BGP or MPLS VPN sample configurations This section presents examples of typical MPLS configurations.
6 BGP or MPLS VPN sample configurations 3. “Configuring an IBGP neighbor on a PE” Assigning an AS number to a PE In the IBGP configuration used in a BGP or MPLS VPN, all PEs are configured with the same AS number. To assign the local AS number 1 to the PE 1 router as shown in Figure 73, enter the following commands. Brocade(config)# router bgp Brocade(config-bgp)# local-as 1 Assigning a loopback interface A loopback interface is used as the termination for address for BGP sessions.
BGP or MPLS VPN sample configurations FIGURE 74 6 EBGP to CE network example To configure EBGP to exchange routes between PE routers and CE routers, the user must perform the configuration steps listed below. 1. “Configuring EBGP on a CE router”. 2. “Configuring EBGP on a PE router”. Configuring EBGP on a CE router To allow route exchange between a CE router and its associated PE router, BGP must be enabled on the CE router and the associated PE router must be configured as a BGP neighbor.
6 BGP or MPLS VPN sample configurations EBGP to CE network example In the example shown in Figure 74, the network is configured to use EBGP to forward routes between the networks attached to the CE routers and the PE routers. IBGP is used to forward routes between the PE routers and an LSP tunnel is configured across the MPLS domain. Figure 74 contains all of the network addresses and AS numbers required to perform this configuration.
BGP or MPLS VPN sample configurations 6 PE 1 configuration This configuration example describes what is required to operate the PE 1 router in Figure 74. In this example, the VRF VPN1 is created with a unique route descriptor consisting of the BGP AS number (1) and a random other number (2), and route targets are set for import and export. The VRF (VPN1) is defined on the interface that connects to CE 1. EBGP is configured between VPN1 and CE 1.
6 BGP or MPLS VPN sample configurations PE 4 configuration This configuration example describes what is required to operate the PE 2 router in Figure 74. In this example, the VRF VPN1 is created with a unique route descriptor consisting of the BGP AS number (1) and a random other number (2), and route targets are set for import and export. The VRF (VPN1) is defined on the interface that connects to CE 5. EBGP is configured between VPN1 and CE 5.
BGP or MPLS VPN sample configurations 6 Static routes for route exchange Static routes can be used to exchange routes between CE routers and PE routers. In this situation, a default static route must be configured on a CE router to its associated PE router. A static route must be configured between the PE router and the network (or networks) that the PE wants to advertise as available through a VRF.
6 BGP or MPLS VPN sample configurations Configuring a static default route on a PE router To allow route exchange between a PE router and its associated CE router, a static route must be created to the route that the user wants to provide access to with a next hop consisting of the IP address of the interface that is connected to the VRF. In Figure 75, the IP address of the connected port on the CE router is 10.33.33.2, and the address on the CE that is provided access from the PE’s VRF is 10.1.2.0/24.
BGP or MPLS VPN sample configurations 6 Brocade(config)# interface loopback 1 Brocade(config-lbif-1)# ip address 10.2.2.1/24 Brocade(config-lbif-1)# ip ospf area 0 Brocade(config-lbif-1)# exit Brocade(config)# vrf VPN1 Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# rd 1:1 route-target export 100:1 route-target import 100:2 exit-vrf Brocade(config)# ip route vrf VPN1 10.1.2.0/24 10.33.33.
6 BGP or MPLS VPN sample configurations Brocade(config)# interface loopback 1 Brocade(config-lbif-1)# ip address 10.2.2.2/32 Brocade(config-lbif-1)# ip ospf area 0 Brocade(config-lbif-1)# exit Brocade(config)# vrf VPN1 Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# rd 1:2 route-target export 100:2 route-target import 100:1 exit-vrf Brocade(config)# ip route vrf VPN1 10.1.2.0/24 10.33.36.
BGP or MPLS VPN sample configurations FIGURE 76 6 RIP to CE network example To configure RIP to exchange routes between PE routers and CE routers, the user must perform the configuration steps listed below. 1. “Configuring RIP on the CE router” 2. “Enabling RIP on the CE router’s interface” 3. “Configuring the VRF on the PE router to redistribute RIP routes” 4. “Configuring RIP on the PE router to redistribute BGP-VPNv4 routes” 5.
6 BGP or MPLS VPN sample configurations Configuring the VRF on the PE router to redistribute RIP routes To allow RIP route exchange between a specified VRF on a PE router and its associated CE router, the VRF must be enabled redistribute RIP routes. To enable the VRF VPN1 on PE 1 router in Figure 76 to redistribute RIP routes, enter the following commands.
BGP or MPLS VPN sample configurations 6 Brocade(config)# router rip Brocade(config-lbif-1)# redistribute static Brocade(config-lbif-1)# exit Brocade(config)# interface ethernet 1/1 Brocade(config-if-e10000-1/1)# ip rip v2-only Brocade(config-if-e10000-1/1)# ip address 10.33.33.2 Brocade(config-if-e10000-1/1)# exit CE 5 configuration This configuration example describes what is required to operate the CE 5 router in Figure 76. In this example, a static route is configured between the external network (10.
6 BGP or MPLS VPN sample configurations Brocade(config-bgp-vpnv4u)# neighbor 10.2.2.
BGP or MPLS VPN sample configurations 6 Brocade(config-bgp)# neighbor 10.2.2.1 update-source loopback 1 Brocade(config-bgp)# address-family vpnv4 unicast Brocade(config-bgp-vpnv4u)# neighbor 10.2.2.
6 BGP or MPLS VPN sample configurations FIGURE 77 OSPF to CE network example To configure OSPF to exchange routes between PE routers and CE routers, the user must perform the configuration steps listed below. 1. “Configuring OSPF on the CE router”. 2. “Enabling OSPF on the CE router interface”. 3. “Configuring the VRF on the PE router to redistribute OSPF routes”. 4. “Configuring OSPF on the PE router to redistribute BGP-VPNv4 routes”. 5. “Enabling OSPF on the PE router interface”.
BGP or MPLS VPN sample configurations 6 Configuring the VRF on the PE router to redistribute OSPF routes To allow OSPF route exchange between a specified VRF on a PE router and its associated CE router, the VRF must be enabled to redistribute OSPF routes. To enable the VRF VPN1 on PE 1 router in Figure 77 to redistribute OSPF routes, enter the following commands.
6 BGP or MPLS VPN sample configurations Brocade(config)# interface loopback 1 Brocade(config-lbif-1)# ip address 10.33.33.1/32 Brocade(config-lbif-1)# exit Brocade(config)# ip route 10.1.2.0/24 10.33.33.1 Brocade(config)# router ospf Brocade(config-ospf-router)# area 1 Brocade(config-ospf-router)# redistribute static Brocade(config-ospf-router)# exit Brocade(config)# interface ethernet 1/1 Brocade(config-if-e10000-1/1)# ip address 10.33.33.
BGP or MPLS VPN sample configurations 6 Brocade(config-vrf-vpn1)# route-target import 100:2 Brocade(config-vrf-vpn1)# exit-vrf Brocade(config)# router bgp Brocade(config-bgp)# local-as 1 Brocade(config-bgp)# neighbor 10.2.2.2 remote-as 1 Brocade(config-bgp)# neighbor 10.2.2.2 update-source loopback 1 Brocade(config-bgp)# address-family vpnv4 unicast Brocade(config-bgp-vpnv4u)# neighbor 10.2.2.
6 BGP or MPLS VPN sample configurations Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# rd 2:1 route-target export 100:2 route-target import 100:1 exit-vrf Brocade(config)# router bgp Brocade(config-bgp)# local-as 1 Brocade(config-bgp)# neighbor 10.2.2.1 remote-as 1 Brocade(config-bgp)# neighbor 10.2.2.1 update-source loopback 1 Brocade(config-bgp)# address-family vpnv4 unicast Brocade(config-bgp-vpnv4u)# neighbor 10.2.2.
BGP or MPLS VPN sample configurations 6 derived from. For example, in Figure 78 the routes that are admitted into VPN1 and VPN2 have route targets of 1:1 and 2:2. The user can use the cooperative route filtering feature to send an ORF that is derived from the route-target import commands on PE 1 to PE 2 to only accept these routes.
6 BGP or MPLS VPN sample configurations Using an IP extcommunity variable with route map In Figure 79, the VRF named “VPN1” on PE 1 is set to import routes with RT 100:14, 100:20 and 100:80. The VRF named “VPN1” on PE 4 is configured to export routes with RT 100:20 and 100:14. The VRF named “VPN2” on PE 4 is configured to export routes with RT 100:6 and 100:20. A route-map is configured from a BGP neighbor command on PE 1 to not install all routes from PE 4 with RT 100:6.
BGP or MPLS VPN sample configurations Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# Brocade(config-vrf-vpn1)# 6 route-target import 100:20 route-target import 100:80 route-target import 100:14 exit-vrf Autonomous system number override In the example shown in Figure 80 the service providers network is in AS1 and the customer wants both of his CE routers at different sites to use AS 2.
6 BGP or MPLS VPN sample configurations Setting an LSP for each VRF on a PE Figure 81 provides an example of assigning a different LSP for each VRF on a PE. In this example, PE 1 contains two VRFs: VPN1 and VPN2. It also contains two loopback interfaces with the following IP addresses: Loopback 0 = 10.2.2.1 and Loopback 2 = 10.2.2.2. Nexthop addresses for VPN1 and VPN2 can be created separately to Loopback 0 and Loopback 1. Then, different LSPs are assigned to each of the Loopback addresses.
BGP or MPLS VPN sample configurations 6 OSPF sham links In the example shown in Figure 82, CE 2 and CE 3 are both in OSPF Area 1 and connect to the same service provider network through different PEs. An additional backdoor connection is configured between them over another network. OSPF recognizes the backdoor connection as an Intra-area connection and the connection through the service provider network as an Inter-network connection.
6 BGP or MPLS VPN sample configurations This configuration example describes the additional configuration required to create a sham link between PE 1 and PE 2 in the example shown in Figure 83. In this example, the VRF VPN1 is added to the loopback interface configuration, and a sham link with a cost of 10 is created between the loopback interfaces on PE 1 and PE 2.
IPv4 L3 VPN CAM optimization overview 6 IPv4 L3 VPN CAM optimization overview This document reviews the functional specification for optimization of CAM programming for L3VPN CAM for IPv4. This scheme is similar to the existing CAM programming of L3VPN CAM for IPv6. After this optimization, L3VPN CAM look up for IPv4 packets is based on (VPN-ID, IP) instead of the current implementation (port, VLAN, IP).
6 Commands FIGURE 85 IP VPN CAM Optimization: ingress packet processing CE (port,VLAN) Packet (VPNID, IP) Service CAM or IFL CAM IPVPN CAM CAM Hit PRAM CAM Hit PRAM VPN ID MPLS Network Next Hop Local Routing CE IPv4 L3 VPN CAM optimization requirements The IPv4 L3 VPN CAM optimization feature is designed to optimize CAM usage for IPVPN routes where each route of a VRF only consumes one CAM entry on a PPCR.
show cam ifl slot/port 6 show cam ifl slot/port The output of show cam ifl slot/port is modified to add IFL-ID in the display. Syntax Parameters show cam ifl slot/port slot/port The slot/port parameter specifies the port for which you want to display the CAM entries. Modes Command output Example Privileged EXEC mode. Output field Description Slot Slot-number Index (Hex) Shows the row number of this entry in the IP route table.
6 show cam ifl slot/port History Related Commands 738 Release Modification NetIron R05.5.00 Enhanced to show IFL-ID None.
6 show cam ipvpn slot/port show cam ipvpn slot/port The output of show cam ipvpn slot/port is modified to add VPNID in the display. Syntax Parameters Show cam ipvpn slot/port slot/port The slot/port parameter specifies the port for which you want to display the CAM entries. Command Modes Privileged EXEC mode. Usage Guidelines Use to display IPv4 VPN CAM entries, including local (port+VLAN+IP) and remote (VC+IP) entries.
6 show cam ipvpn slot/port To add VRF to VE. Brocade(config)# vlan 22 Brocade(config-vlan-22)# tagged ethe 1/7 Brocade(config-vlan-22)# router-interface ve 22 Brocade(config-vlan-22)# exit Brocade(config)# interface ve 22 Brocade(config-vif-22)# vrf forwarding blue Brocade(config-vif-22)# ip address 10.0.0.22/24 Brocade(config-vif-22)# exit Brocade# show cam ipvpn slot/port History Related Commands Release Command History NetIron R05.5.00 This command was modified to add VPNID in the display. None.
Chapter 7 Routing over VPLS Table 137 displays the individual devices and Routing over VPLS features they support.
7 Overview FIGURE 86 Routing over VPLS VRRP and VRRP-E support on the VE over VPLS provides L3 redundancy for downstream devices. The VRRP control protocol communication across the VPLS link allows VRRP master and backup to exist in different data centers, providing L3 redundancy across data centers. FIGURE 87 Support for multiple VRRP backups for a single master allows L3 redundancy across multiple data centers.
Overview 7 Routing over VPLS components VE interface VE interfaces can switch or route packets. This is decided by the destination L2 (Ethernet) MAC of the packet received at the VPLS end-point. When the Ethernet MAC is the Port MAC or Router MAC, the packet is routed. Routing This is the IP interface of the VE, which supports most of the existing functionalities of a legacy IP interface or the VE over VLAN interface.
7 Overview Packet Coming from the Local End-point of a VPLS-VE: - to a VPLS uplink of same or another VPLS-VE instance to a local VPLS endpoint of same or another VPLS-VE instance to a VE over VLAN interface to a normal IP interface over a physical interface to an IP-over-MPLS interface to GRE tunnel Packet coming from the Uplink (Remote End-point) of a VPLS-VE: - to a VPLS uplink of another VPLS-VE instance to a local VPLS endpoint of same or another VPLS-VE instance to a VE over VLAN interface to a
Overview 7 NOTE The NetIron CES and NetIron CER require at least one active endpoint for software forwarding. VE over VPLS configuration and ICMP redirects VE over VPLS adjacent devices can be on the same IP subnet while being part of the same VPLS segment. To prevent generation of ICMP redirects and sending of data packets to the CPU, it is recommended to turn-off "ICMP redirects". Note that ICMP redirect is ON by default.
7 Overview TABLE 139 746 Routing over VPLS supported features Protocol Support ICMP Supported ICMP Redirect Message Supported ICMP Unreachable Message Not supported OSPF Supported IS-IS Supported RIP Supported BGP Supported Trunk Ports (LAG) Supported L2 Multicast Supported IGMP Snooping Supported L2 ACL Supported L3 ACL Supported Rate Limiting Supported PBR Not supported Multi-netting Supported VRRP/VRRP-E Supported (Brocade MLX Series and NetIron XMR only) IP Helper
7 Overview Modules supported Use the table below to determine when routing over VPLS is supported on specific interface module.
7 Overview Configuration Considerations Consider the following before configuring routing over VPLS.
Overview 7 Configuring VE over VPLS For information on configuring VPLS, refer to “Configuring MPLS Virtual Private LAN Services” on page 449 Use the router-interface ve command to configure the VE per VPLS instance. The user must specify a router-interface for each VPLS instance. Use commands such as the following.
7 VRRP/VRRP-E support 3. Configuration check that disallows a VE over VPLS with a PBB configuration. In this example, an error message is displayed when the user tries to enable both VE over VPLS and PBB in the same VPLS instance. Brocade(config)# router mpls Brocade(config-mpls)# vpls vinst 2000 Brocade(config-mpls-vpls-vinst)# router-interface ve 3 Brocade(config-mpls-vpls-vinst)# pbb Error - VE over VPLS and PBB cannot be enabled on the same VPLS instance.
VRRP/VRRP-E support 7 VRRP-E backup When short-path-forwarding is not enabled on the VRRP-E backup, then forwarding of the VRRP-E backup is the same as VRRP backup. When short-path-forwarding is enabled, the VRRP/VRRP-E backup itself can route packet instead of sending to the master. VRRP/VRRP-E master backup state change When the VRRP/VRRP-E master becomes the backup, it flushes all the CAM entries.
7 VRRP/VRRP-E support Single homing topology FIGURE 89 Single homing topology example Configuration considerations Consider the following when using VRRP/VRRP-E with routing over VPLS in a single homing topology. • In the single homing topology, a cost is connected to a single VPLS peer.
VRRP/VRRP-E support 7 Dual homing topology FIGURE 90 Dual homing topology example The configuration is the same for VRRP or VRRP-E over VPLS VE. In Figure 90, the VRRP/VRRP-e is configured similar to a VRRP/VRRP-E configuration over a regular Layer 2 based VE. Configuration considerations Consider the following when using VRRP and VRRP-E with routing over VPLS in a duel homing topology. • A single host can be used to connect to two VPLS nodes within the same VPLS instance for dual homing support.
7 ACL Support for VE over VPLS • On each node, include the VPLS endpoint VLAN in the topology group VLAN as a member VLAN, so the link from one of the nodes to the access box is blocked for Layer 2 loop avoidance. Configure the master VLAN to have a Layer 2 protocol configuration, such as MRP/RSTP. Refer to the topology group VLAN configuration for setting VPLS VLAN in the topology group VLAN. • The recommended configuration is VRRP-E with server virtualization.
ACL Support for VE over VPLS 7 • ACLs applied on the VPLS-VE interface is effective to inbound and outbound traffic received from or sent to local end-points. The MPLS uplink (VPLS Peer) inbound and outbound traffic is not filtered by the ACL. • The ACLs having VLAN ID in their rule can not be applied to VE over VPLS interfaces. • VPLS-VE and ACL definition modifications require explicit rebinding to take effect. Configuration steps VE over VPLS uses the same ACL commands as VE for VLANs.
7 ACL Support for VE over VPLS Step 3: interface ve 2 ip access-group v4_acl in ethernet 4/2 Error messages The following messages are seen when an invalid configuration is attempted. • • • • IN ACL – “Inbound ACL is applied to all local endpoints of VE over VPLS interface” OUT ACL – “Outbound ACL is applied to all local endpoints of VE over VPLS interface” This feature is not supported for 24x10G modules. This feature is not supported for POS modules.
ACL Support for VE over VPLS 7 The num parameter lets the user display the table beginning with a specific entry number. The entry numbers in the ARP cache are not related to the entry numbers for static ARP table entries. Show ip static-arp Use the show ip static-arp command to display port, VPLS-ID, VLAN, and VPLS peer information. Brocade(config)# show ip static-arp Total no. of entries: 2 Index IP Address MAC Address Port/VLAN 1 10.10.10.10 0000.0033.4444 100 2 10.11.11.11 0000.0066.
7 ACL Support for VE over VPLS Flags : U-Unnumbered, S-Secondary, US-Unnumbered Secondary, V-VE over VPLS, VS-VE over VPLS Secondary Interface IP-Address OK? Method Status Protocol VRF FLAG mgmt 1 10.25.106.36 YES NVRAM up up default-vrf ve 40 10.40.40.1 YES NVRAM down down default-vrf ve 150 10.15.15.1 YES NVRAM up up default-vrf V ve 150 10.20.20.1 YES NVRAM up up default-vrf V ve 150 10.15.15.2 YES NVRAM up up default-vrf VS loopback 1 10.1.1.
Chapter 8 Configuring BGP-Based Auto-Discovery for VPLS Overview Table 143 displays the individual Brocade devices and the BGP-Based Auto-Discovery for VPLS features they support.
8 How BGP-based auto-discovery for VPLS works Terms introduced in this chapter BGP-based auto-discovery for VPLS – Also called VPLS auto-discovery, this feature enables automatic discovery of VPLS Provider Edge (PE) devices that are part of the same VPLS domain, and the ability to detect and converge when other PE routers are added to or removed from the VPLS domain.
About the L2VPN VPLS address family 8 When VPLS auto-discovery is disabled for a VPLS instance, the system removes all auto-discovered peers for the VPLS instance from the configuration. It then removes the route (local VPLS endpoint address) from the BGP L2VPN route table and sends a “withdrawn” message to VPLS peers, prompting them to remove the route and to disable VPLS auto-discovery. Finally, the system updates the route target tree and sends a route refresh message for the L2VPN VPLS address family.
8 Configuring BGP-based auto-discovery for VPLS Configuring BGP-based auto-discovery for VPLS It is recommended that the user performs the configuration tasks in the order listed in Table 144. Performing the tasks in the recommended sequence minimizes CPU consumption and route flapping. Except where noted as “optional”, the configuration tasks in the table are required for VPLS auto-discovery. TABLE 144 Configuration tasks for VPLS auto-discovery Configuration task See...
Configuring BGP-based auto-discovery for VPLS 8 About loopback interfaces and the router ID In most configurations, a Brocade device has multiple IP addresses, usually configured on different interfaces. As a result, a Brocade device’s identity to other devices varies depending on the interface to which the other device is attached. BGP4 identifies a Brocade device by just one of the IP addresses configured on the device, regardless of the interfaces that connect the devices.
8 Configuring BGP-based auto-discovery for VPLS Viewing the loopback Interface Use the show mpls ldp command to view the loopback interface and router ID in use on the Brocade device. Refer to “Displaying information about LDP” on page 791. Configuring BGP4 to support VPLS auto-discovery BGP4 must be enabled on the device and a local Autonomous System (AS) number must be assigned before VPLS auto-discovery can be enabled.
Configuring BGP-based auto-discovery for VPLS 8 Changing or clearing the local AS number when VPLS auto-discovery is enabled When VPLS auto-discovery is enabled on the device and the user wants to clear or change the BGP local AS number, the user must first disable VPLS auto-discovery, then clear the local AS number.
8 Configuring BGP-based auto-discovery for VPLS NOTE When BGP is disabled, the system also removes the BGP local AS number from the configuration. Configuring VPLS to support auto-discovery This section describes how to configure VPLS to support BGP-based auto-discovery.
Configuring BGP-based auto-discovery for VPLS 8 Defining the route target for a VPLS instance (optional) NOTE When the user decides to manually define a route target, it is recommended that the user do so before enabling VPLS auto-discovery. The route target extended community for VPLS auto-discovery defines the import and export policies that a VPLS instance uses. The export route target sets an extended community attribute number that is appended to all routes that are exported from the VPLS instance.
8 Configuring BGP-based auto-discovery for VPLS Viewing the route target for a VPLS instance Use the show mpls vpls name command to view the route targets for a VPLS instance. Refer to “Displaying information about VPLS auto-discovery and load balancing” on page 789. Enabling and disabling load balancing for a VPLS instance (optional) This section describes how to enable and disable load balancing for a VPLS instance on which VPLS auto-discovery is enabled.
Configuring BGP-based auto-discovery for VPLS 8 The above commands disable VPLS auto-discovery for VPLS instance “c1”, then re-enable VPLS auto-discovery with the load-balance option. Syntax: [no] auto-discovery Syntax: [no] auto-discovery load-balance Disabling load balancing To disable load balancing when VPLS auto-discovery is enabled on the device, first disable VPLS auto-discovery, then re-enable it without the load-balancing option.
8 Clearing the BGP L2VPN route table Brocade(config-mpls-vpls-c2)# auto-discovery Error: Please configure a loopback address for LDP first! To add a loopback interface, follow the configuration instructions in “Configuring a loopback interface” on page 762. • When the user attempts to enable VPLS auto-discovery without first configuring the BGP AS number, the following error message displays on the console.
Clearing the BGP L2VPN route table 8 Clearing the BGP L2VPN route table and resetting BGP NOTE This section describes how to clear routes from the BGP L2VPN route table and reset the BGP session. When the user does not want to reset the BGP session while clearing routes, refer to “Clearing the BGP L2VPN route table without resetting the BGP session” on page 771.
8 Example configuration The soft parameter performs a soft reset of the neighbor session, which does not affect the session with the neighbor. The in parameter updates inbound routes. The out parameter updates outbound routes. NOTE When the user does not specify “in”, the command applies to both inbound and outbound updates. Example configuration The following shows a typical VPLS auto-discovery configuration. Brocade1 configuration The following commands are entered on Brocade1.
Example configuration 8 Brocade(config)# router mpls Brocade(config-mpls)# mpls-interface ethernet 1/1 Brocade(config-mpls)# vpls C1 10 Brocade(config-mpls-vpls-C1)# auto-discovery Brocade(config-mpls)# exit Brocade(config-mpls)# vpls C2 20 Brocade(config-mpls-vpls-C2)# auto-discovery Brocade(config-mpls-vpls-C2)# exit Brocade(config-mpls)# exit Brocade(config)# router bgp Brocade(config-bgp)# address-family l2vpn vpls Brocade(config-bgp-l2vpn-vpls)# neighbor 10.1.1.
8 Example configuration Brocade1# show ip bgp nei 10.1.1.2 1 IP Address: 10.1.1.2, AS: 10 (IBGP), RouterID: 10.2.2.
Displaying VPLS auto-discovery information 8 Brocade1# show mpls vpls name c1 VPLS c1, Id 10, Max mac entries: 8192 Total vlans: 0, Tagged ports: 0 (0 Up), Untagged ports 0 (0 Up) Total VPLS peers: 1 (0 Operational) auto-discovery enabled, RD 10:10 export RT 10:10 import RT 10:10 Peer address: 10.2.2.
8 Displaying VPLS auto-discovery information Viewing all BGP L2VPN VPLS routes The show ip bgp l2vpn vpls command displays all of the BGP L2VPN VPLS routes. The following shows example output. Brocade1# show ip bgp l2vpn vpls Total number of BGP L2VPN VPLS Routes: 4 Status codes: s suppressed, d damped, h history, * valid, > best, i stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 10:10 *> 10.1.1.1/32 0.0.0.0 0 100 65535 i *i 10.2.2.
Displaying VPLS auto-discovery information TABLE 146 8 Output for the show ip bgp l2vpn vpls command (Continued) This field... Displays Origin codes A list of the characters the display uses to indicate the route’s origin. The origin code appears to the right of the AS path (Path field). The origin code can be one of the following: • i - IGP – The routes with this set of attributes came to BGP4+ through IGP • e - EGP – The routes with this set of attributes came to BGP4+ through EGP.
8 Displaying VPLS auto-discovery information Syntax: show ip bgp l2vpn vpls IP route address Field definitions for the show ip bgp l2vpn vpls IP route address command are the same as for show ip bgp l2vpn vpls. Refer to Table 146. Viewing BGP L2VPN VPLS route attribute entries Use the show ip bgp l2vpn vpls attribute-entries command to view attribute entries for BGP L2VPN VPLS routes. Brocade1# show ip bgp l2vpn vpls attribute-entries Total number of BGP Attribute Entries: 4 (2) 1 Next Hop :10.0.0.
Displaying VPLS auto-discovery information TABLE 147 Output for the show ip bgp l2vpn vpls attribute-entries command This field... Displays Total number of BGP Attribute Entries The number of routes contained in this device’s BGP L2VPN VPLS route table. Next Hop The IP address of the next hop router for routes that have this set of attributes. Metric The cost of the routes that have this set of attributes. Origin 8 The source of the route information.
8 Displaying VPLS auto-discovery information Viewing neighbor connections Use the show ip bgp l2vpn vpls neighbors command to view the details of TCP and BGP neighbor connections. Brocade1# show ip bgp l2vpn vpls neighbors Total number of BGP Neighbors: 1 1 IP Address: 10.1.1.2, AS: 10 (IBGP), RouterID: 10.2.2.
Displaying VPLS auto-discovery information TABLE 148 8 Output for the show ip bgp l2vpn vpls neighbors command (Continued) This field... Displays... VRF • State The state of the Brocade device’s session with the neighbor. The states are from this device’s perspective of the session, not the neighbor’s perspective. The state values are based on the BGP4 state machine values described in RFC 1771 and can be one of the following for each router: • IDLE – The BGP4 process is waiting to be started.
8 Displaying VPLS auto-discovery information TABLE 148 782 Output for the show ip bgp l2vpn vpls neighbors command (Continued) This field... Displays... Messages Sent The number of messages this device has sent to the neighbor. The display shows statistics for the following message types: • Open • Update • KeepAlive • Notification • Refresh-Req Messages Received The number of messages this device has received from the neighbor. The message types are the same as for the Message Sent field.
Displaying VPLS auto-discovery information TABLE 148 8 Output for the show ip bgp l2vpn vpls neighbors command (Continued) This field... Displays... Last Connection Reset Reason (cont’d) • Notification Sent When the device sends a NOTIFICATION message to the neighbor, the message contains an error code corresponding to one of the following errors. Some errors have subcodes that clarify the reason for the error. Where applicable, the subcode messages are listed underneath the error code messages.
8 Displaying VPLS auto-discovery information TABLE 148 784 Output for the show ip bgp l2vpn vpls neighbors command (Continued) This field... Displays... Neighbor NLRI Negotiation The state of the NLRI negotiation with the neighbor.
Displaying VPLS auto-discovery information TABLE 148 8 Output for the show ip bgp l2vpn vpls neighbors command (Continued) This field... Displays... TotSent The number of sequence numbers sent to the neighbor. ReTrans The number of sequence numbers that the Brocade device retransmitted because they were not acknowledged. UnAckSeq The current acknowledged sequence number. IRcvSeq The initial receive sequence number for the session. RcvNext The next sequence number expected from the neighbor.
8 Displaying VPLS auto-discovery information TABLE 149 Output for the show ip bgp l2vpn vpls rd command (Continued) This field... Displays LocPrf The degree of preference for this route relative to other routes in the local AS. When the BGP4+ algorithm compares routes on the basis of local preferences, the route with the higher local preference is chosen. The preference can have a value from 0 – 4294967295. Weight The value that this route associates with routes from a specific neighbor.
Displaying VPLS auto-discovery information TABLE 150 8 Output for the show ip bgp l2vpn vpls routes command This field... Displays Total number of BGP Routes The number of BGP4 routes the Brocade device has installed in the BGP4 route table. Status A list of the characters the display uses to indicate the route’s status. The status code appears in the last column of the display, to the right of each route.
8 Displaying VPLS auto-discovery information TABLE 150 Output for the show ip bgp l2vpn vpls routes command (Continued) This field... Displays Weight The value that this route associates with routes from a specific neighbor. For example, when the Brocade device receives routes to the same destination from two BGP4 neighbors, the device prefers the route from the neighbor with the larger weight. Status The route’s status. Refer to “Status” on page 787.
Displaying VPLS auto-discovery information TABLE 151 8 Output for the show ip bgp l2vpn vpls summary command (Continued) This field... Displays AS# The AS number. State Refer to “State” on page 781.mmd. Time The time that has passed since the state last changed. Rt: Accepted The number of routes received from the neighbor that this device installed in the BGP4 route table. Usually, this number is lower than the RoutesRcvd number.
8 Displaying VPLS auto-discovery information TABLE 152 790 Output for the show mpls vpls name command (Continued) This field... Displays Max mac entries The maximum number of MAC address entries that can be learned for this VPLS instance. This is a soft limit only and can be exceeded when there is space available in the VPLS MAC database. Total VLANs The number of VLANs that are translated for this VPLS instance.
Displaying VPLS auto-discovery information TABLE 152 8 Output for the show mpls vpls name command (Continued) This field... Displays Local VC lbl The VC label value locally allocated for this peer for this VPLS instance. Packets forwarded from the VPLS peer to this device are expected to contain this label. This is the label that is advertised to the VPLS peer through LDP. Remote VC lbl The VC label allocated by the VPLS peer and advertised to this device through LDP.
8 VPLS LSP Load Balancing VPLS LSP Load Balancing Glossary TABLE 153 Glossary of terms Term Meaning MAC Media Access Control LSP Label Switched Path VPLS Virtual Private LAN Service Feature overview This functional specification documents the VPLS LSP load balancing which is to be incremented from four LSPs to eight LSPs in the NetIron R05.600 for the XMR/MLX product lines. Prior to NetIron R05.600, VPLS LSP load balancing is done with a maximum of four LSPs.
Feature overview 8 BUT the following unique mac addresses /unique VLANs are working: IXIA P1: SMAC = 00-00-00-03-01-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8 VLAN = 10yy where yy = 10, 11, 12, 13, 14, 15, 16, 17 IXIA P2: SMAC = 00-00-00-03-02-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8 VLAN = 10yy where yy = 10, 11, 12, 13, 14, 15, 16, 17 or IXIA P1: SMAC = 00-00-00-03-12-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8 VLAN = 10yy where yy = 10, 11, 12, 13, 14, 15, 16, 17 IXIA P2: SMAC = 00-00-00-03-13-xx where xx = 1, 2, 3, 4,
8 Feature overview Brocade(config-mpls)# path ve100 Brocade(config-mpls-path-ve100)# strict 10.19.3.2 Brocade(config-mpls)# mpls-interface ve 100 Brocade(config-mpls)# mpls-interface ve 10 Brocade(config-mpls)# lsp lsp1 Brocade(config-mpls-lsp-lsp1)# to 10.19.19.19 Brocade(config-mpls-lsp-lsp1)# primary ve100 Brocade(config-mpls-lsp-lsp1)# enable Brocade(config-mpls)# lsp lsp2 Brocade(config-mpls-lsp-lsp2)# 10.19.19.
Feature overview 8 Load balance with manual LSP Assignment Configuration on the Ingress router Brocade(config)# router mpls Brocade(config-mpls)# policy Brocade(config-mpls-policy)# cspf-interface-constraint Brocade(config-mpls)# path ve5 Brocade(config-mpls-path-ve5)# strict 10.19.2.3 Brocade(config-mpls)# path ve10 Brocade(config-mpls-path-ve10)# strict 10.19.3.
8 Commands Brocade(config-mpls)# v1 v100 Brocade(config-mpls-v1-v100)# vpls-peer 10.18.18.
show mpls vpls detail 8 show mpls vpls detail VPLS Manual LSP assignment for a peer can now accept maximum of eight LSPs instead of four LSPs. The show mpls vpls detail command output shows all the tunnels (max eight) used. Syntax Parameters Modes Command output Examples show mpls vpls detail None Global configuration mode. The show mpls vpls detail command displays the following information. Output field Description VPLS The configured name of the VPLS instance.
8 show mpls vpls detail VC-Mode: Raw Total VPLS peers: 1 (1 Operational) Peer address: 19.19.19.
Chapter 9 IPv6 Provider Edge Router over MPLS Table 155 displays the individual devices and whether or not the IPv6 over MPLS feature is supported.
9 6PE over MPLS FIGURE 92 6PE over MPLS 6PE over MPLS operation The 6PE router forwards IPv6 traffic between remote sites of a customer's network using the existing IPv4-signaled Label Switched Path (LSP). Creating routes in an MPLS domain Figure 93 describes how the IPv6 routes are created in an MPLS domain. A CE router maintains the connection to the customer's network and is configured within the network to send or receive IPv6 packets.
6PE over MPLS FIGURE 93 9 MPLS route discovery Routing an IPv6 packet through an MPLS domain The following steps describe how an IPv6 packet is routed through an existing MPLS domain. 1. The 6PE router receives the IPv6 packets from the CE router. 2. The 6PE router assigns labels to all the received IPv6 packets. 3. The 6PE router exchanges the IPv6 packets along with the labels with the other 6PE routers. 4. The 6PE router transports the IPv6 packets from the CE router using the existing IPv4 LSPs.
9 Configuring 6PE FIGURE 94 Routing an IPv6 packet through the MPLS domain 6PE limitations 6PE has the following limitations: • 6PE supports only IPv6 unicast forwarding • 6PE is supported only in the default VRF • 6PE does not support GREv6 over v4 tunnel NOTE Do not forward packets from one type of tunnel to another type of tunnel in XPP. Packets may not be routed properly. Configuring 6PE The user must first configure BGP and MPLS to enable 6PE route propagation.
Configuring 6PE 9 Brocade(config-bgp-ipv6u)# neighbor 10.30.30.1 activate Brocade(config-bgp-ipv6u)# neighbor 10.30.30.1 send-label Syntax: [no] neighbor IPv4 address activate The IPv4 address parameter specifies the IP address of the remote neighbor. The activate keyword enables IPv6 unicast capability for the IPv4 peers. The [no] option is used to turn off the IPv6 unicast capability that has been enabled previously for the IPv4 peers.
9 Configuring 6PE FIGURE 95 Deploying 6PE CE1 configuration This configuration example describes the operational requirements for the CE1 router. EBGP is configured between the CE1 and 6PE1 routers, and the connected route is redistributed through this connection.
Configuring 6PE 9 6PE1(config-if-e10000-1/2)# exit 6PE1(config)# router bgp 6PE1(config-bgp)# local-as 1 6PE1(config-bgp)# neighbor 10.40.40.1 remote-as 1 6PE1(config-bgp)# address-family ipv6 unicast 6PE1(config-bgp-ipv6u)# neighbor 2001:db8:1111::1 remote-as 2 6PE1(config-bgp-ipv6u)# neighbor 10.40.40.1 activate 6PE1(config-bgp-ipv6u)# neighbor 10.40.40.
9 Displaying 6PE information CE2(config-lbif-1)# exit CE2(config)# interface ethernet 1/1 CE2(config-if-e10000-1/1)# ipv6 address 2001:db8:2222::1/64 CE2(config-if-e10000-1/1)# exit CE2(config)# router bgp CE2(config)# local-as 3 CE2(config-bgp)# address-family ipv6 unicast CE2(config-bgp-ipv6u)# neighbor 2001:db8:2222::2 remote-as 1 CE2(config-bgp-ipv6u)# redistribute connected CE2(config-bgp-ipv6u)# exit Displaying 6PE information The user can display the following information about the 6PE configurati
Displaying 6PE information 9 BFD:Disabled TCP Connection state: ESTABLISHED, flags:00000044 (0,0) Maximum segment size: 1460 TTL check: 0, value: 0, rcvd: 62 Byte Sent: 981, Received: 962 Local host: 10.40.40.1, Local Port: 179 Remote host: 10.30.30.
9 Displaying 6PE information TABLE 156 Output parameters of the show ip bgp 6pe neighbors command (Continued) Field Description State Shows the state of the router session with the neighbor. The states are from the router’s perspective of the session, not the neighbor’s perspective. The state can be one of the following values: • IDLE – The BGP4 process is waiting to be started. Usually, enabling BGP4 or establishing a neighbor session starts the BGP4 process.
Displaying 6PE information TABLE 156 9 Output parameters of the show ip bgp 6pe neighbors command (Continued) Field Description Last Connection Reset Reason Shows the reason for ending the previous session with this neighbor.
9 Displaying 6PE information TABLE 156 810 Output parameters of the show ip bgp 6pe neighbors command (Continued) Field Description Notification Sent Shows an error code corresponding to one of the following errors when the router sends a Notification message from the neighbor. Some errors have subcodes that clarify the reason for the error. The subcode messages are listed underneath the error code messages, wherever applicable.
Displaying 6PE information TABLE 156 9 Output parameters of the show ip bgp 6pe neighbors command (Continued) Field Description Outbound Policy Group Shows the ID and the count used in the outbound policy group. BFD Shows whether or not Bidirectional Forwarding Detection (BFD) is enabled on the device. TCP Connection state Shows the state of the connection with the neighbor. The connection can have one of the following states: • LISTEN – Waiting for a connection request.
9 Displaying 6PE information TABLE 156 Output parameters of the show ip bgp 6pe neighbors command (Continued) Field Description TotalRcv Shows the count of the sequence numbers received from the neighbor. DupliRcv Shows the count of the duplicate sequence numbers received from the neighbor. RcvWnd Shows the size of the receive window. SendQue Shows the count of the sequence numbers in the send queue. RcvQue Shows the count of the sequence numbers in the receive queue.
Displaying 6PE information 9 Invalid Confed aspath:0, maxas-limit aspath:0 Duplicated Originator_ID:0, Cluster_ID:0 Routes Advertised:2, To be Sent:0, To be Withdrawn:0 NLRIs Sent in Update Message:2, Withdraws:0, Replacements:0 Peer Out of Memory Count for: Receiving Update Messages:0, Accepting Routes(NLRI):0 Attributes:0, Outbound Routes(RIB-out):0 Outbound Routes Holder:0 Syntax: show ip bgp 6pe neighbors routes-summary Table 158 describes the output parameters of the show ip bgp 6pe neighbors routes
9 Displaying 6PE information TABLE 158 Output parameters of the show ip bgp 6pe neighbors routes-summary command (Continued) Field Description NLRIs Discarded due to Shows the number of times the router discarded NLRI for the neighbor due to the following reasons: • Maximum Prefix Limit – The configured maximum prefix amount that had been reached. • AS Loop – An AS loop occurred. An AS loop occurs when the BGP4 AS-path attribute contains the local AS number.
Displaying 6PE information 9 BGP4 Summary Router ID: 10.40.40.1 Local AS Number: 1 Confederation Identifier: not configured Confederation Peers: Maximum Number of IP ECMP Paths Supported for Load Sharing: 1 Number of Neighbors Configured: 1, UP: 1 Number of Routes Installed: 4, Uses 344 bytes Number of Routes Advertising to All Neighbors: 2 (2 entries), Uses 96 bytes Number of Attribute Entries Installed: 4, Uses 360 bytes Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend 10.30.30.
9 Displaying 6PE information TABLE 159 Output parameters of the show ip bgp 6pe summary command (Continued) Field Description State Shows the state of the router sessions with each neighbor. The states can be one of the following for each router: • IDLE - The BGP4 process is waiting to be started. Usually, enabling BGP4 or establishing a neighbor session starts the BGP4 process. • ADMND - The neighbor has been administratively shut down.
Clearing 6PE information 9 Displaying the 6PE packet count Issue the show mpls statistics 6pe command to display the count of 6PE packets per packet processor. For example, to display the count of 6PE packets per packet processor for the configuration in Figure 95, enter the following command.
9 6PE behavioral differences on the Brocade devices 6PE behavioral differences on the Brocade devices The 6PE support provided on the Brocade MLXe series and Brocade NetIron XMR devices differs from that provided on the Brocade NetIron CES and Brocade NetIron CER devices.
6VPE Routing 9 TABLE 162 Differences in the 6PE CoS behavior on the Brocade devices Behavior of Brocade MLXe series and Brocade NetIron XMR devices Behavior of Brocade NetIron CES and Brocade NetIron CER devices At the ingress router, the tunnel and 6PE label EXP bits are set to internal priority. When the tunnel has a configured CoS value, the configured value overrides the internal priority. At the ingress router, the tunnel and 6PE label EXP bits are set to internal priority.
9 Configuring 6VPE • • • • Customer A sites: Advertise IPv6 routes. Customer B sites: Advertise IPv6 routes. PE1: The source or the ingress label switch router (LSR). PE2 and PE3: The destination or the egress LSRs. The topology shows different customer sites that are connected through IPv4 MPLS network and operating with IPv6 address families. The PE routers run dual stack IPv4 and IPv6.
Configuring 6VPE 9 Create a route distinguisher for the VRF: Brocade(config-vrf-A)# rd 1:1 Configure the address family: Brocade(config-vrf-A)# address-family ipv6 2. Interface configuration Assign an interface to the VRF: Brocade(config)# interface ethernet 1/1 Brocade(config-if-e10000-1/1)# vrf forwarding A Brocade(config-if-e10000-1/1)# Configure the IPv6 address: Brocade(config)# interface ethernet 1/1 Brocade(config-if-e10000-1/1)# ipv6address 3ffe:db8::2/64 3.
9 Configuring 6VPE Use case scenario: 6VPE when PEs are directly connected Figure 98 shows 6VPE packet flow when PE routers are directly connected to each other in an MPLS network. FIGURE 98 6VPE when PEs are directly connected Configuration example to deploy 6VPE Refer to Figure 99 for the network topology to understand the 6VPE configuration example.
Configuring 6VPE 9 CE-A1 Configuration 1. OSPFv3 Configuration CE-A1(config)# ip router-id 110.110.110.1 CE-A1(config)# ipv6 router ospf CE-A1(config-ospf6-router)# area 1 CE-A1(config-ospf6-router)# exit 2. Interface Configuration CE-A1(config)#interface ethernet 1/1 CE-A1(config-if-e10000-1/1)# enable CE-A1(config-if-e10000-1/1)# ipv6 address 3000:1::1/64 CE-A1(config-if-e10000-1/1)# ipv6 ospf area 1 CE-A1(config-if-e10000-1/1)# exit PE-1 Configuration 1.
9 Configuring 6VPE PE-1(config-if-e10000-1/2)# ip ospf area 0 PE-1(config-if-e10000-1/2)# exit 5. MP-BGP Configuration PE-1(config)# router bgp PE-1(config-bgp)# address-family vpnv6 unicast PE-1(config-bgp-vpnv6u)# neighbor 20.0.0.1 remote-as 100 PE-1(config-bgp-vpnv6u)# neighbor 20.0.0.1 capability orf prefixlist send PE-1(config-bgp-vpnv6u)# exit 6.
Configuring 6VPE 9 PE-2 Configuration 1. VRF Configuration PE-2(config)# vrf red PE-2(config-vrf-red)# rd 1:1 PE-2(config-vrf-red)# ip router-id 130.130.130.
9 Displaying 6VPE information CE-A2 Configuration 1. OSPFV3 Configuration CE-A2(config)# ip router-id 140.140.140.4 CE-A2(config)# ipv6 router ospf CE-A2(config-ospf6-router)# area 1 CE-A2(config-ospf6-router)# exit 2.
Displaying 6VPE information TABLE 164 9 Output from the show mpls statistics 6pe vrf command Field Description In-Port(s) Shows the port for which the 6VPE traffic is received or sent. Endpt Out-Pkt Shows the number of 6VPE packets received from the MPLS network and sent as IPv6 packets to the IPv6 cloud. Tnl Out-Pkt Shows the number of IPv6 packets received from the IPv6 cloud and sent as 6VPE packets to the MPLS network.
9 828 Displaying 6VPE information Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 53-1003031-02
