Page 1 HPE FlexNetwork 5510 HI Switch Series MPLS Configuration Guide Part number: 5200-0081b Software version: Release 11xx Document version: 6W102-20171020...
Page 2 © Copyright 2015, 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Configuring basic MPLS ···································································· 1 Overview ·································································································································· 1 Basic concepts ··················································································································· 1 MPLS network architecture ···································································································· 2 LSP establishment ··············································································································· 3 MPLS forwarding ················································································································· 4 PHP ································································································································· 4 Protocols and standards ······································································································· 5 MPLS configuration task list ········································································································· 5 Enabling MPLS ·························································································································...
Page 4 Configuring LDP-OSPF synchronization ················································································· 31 Configuring LDP-ISIS synchronization ··················································································· 32 Configuring LDP FRR ··············································································································· 33 Resetting LDP sessions ············································································································ 33 Enabling SNMP notifications for LDP ··························································································· 33 Displaying and maintaining LDP ·································································································· 34 LDP configuration examples ······································································································· 34 LDP LSP configuration example ··························································································· 34 Label acceptance control configuration example ······································································...
Page 5 No TE LSA generated ······································································································ 127 Configuring a static CRLSP ···························································· 128 Overview ······························································································································ 128 Configuration procedure ·········································································································· 128 Displaying static CRLSPs ········································································································ 129 Static CRLSP configuration example ·························································································· 129 Network requirements ······································································································ 129 Configuration procedure ··································································································· 130 Verifying the configuration ································································································· 132 Configuring RSVP ········································································...
Page 6 Configuration prerequisites ································································································ 175 Configuring VPN instances ································································································ 175 Configuring routing between a PE and a CE ·········································································· 177 Configuring routing between PEs ························································································ 181 Configuring BGP VPNv4 route control ·················································································· 182 Configuring inter-AS VPN ········································································································ 183 Configuring inter-AS option A ····························································································· 183 Configuring inter-AS option B ·····························································································...
Page 7 Configuring an OSPFv3 sham link ······················································································ 304 Configuring MPLS L2VPN ······························································ 310 Overview ······························································································································ 310 Basic concepts of MPLS L2VPN ························································································· 310 MPLS L2VPN network models ··························································································· 311 PW redundancy ·············································································································· 312 Multi-segment PW ··········································································································· 313 VCCV ··························································································································· 314 MPLS L2VPN configuration task list ··························································································· 315 Enabling L2VPN ····················································································································...
Page 8 Configuring MPLS OAM ································································ 397 Overview ······························································································································ 397 MPLS ping ····················································································································· 397 MPLS tracert ·················································································································· 397 BFD for MPLS ················································································································ 397 Periodic MPLS tracert ······································································································ 398 Protocols and standards ·········································································································· 398 Configuring MPLS OAM for LSP tunnels ····················································································· 398 Configuring MPLS ping for LSPs ························································································ 398 Configuring MPLS tracert for LSPs ······················································································...
Page 9 Remote support ·············································································································· 460 Documentation feedback ·································································································· 460 Index ························································································· 462...
Page 10: Configuring Basic Mpls
Configuring basic MPLS Multiprotocol Label Switching (MPLS) provides connection-oriented label switching over connectionless IP backbone networks. It integrates both the flexibility of IP routing and the simplicity of Layer 2 switching. In this chapter, the term "interface" refers to a Layer 3 interface. It can be a VLAN interface or a Layer 3 Ethernet interface.
Page 11: Mpls Network Architecture
A router that performs MPLS forwarding is a label switching router (LSR). A label switched path (LSP) is the path along which packets of an FEC travel through an MPLS network. An LSP is a unidirectional packet forwarding path. Two neighboring LSRs are called the upstream LSR and downstream LSR along the direction of an LSP.
Page 12: Lsp Establishment
• Transit LSR—Intermediate LSRs in the MPLS network. The transit LSRs on an LSP forward packets to the egress LSR according to labels. • Egress LSR—Egress LSR of packets. It removes labels from packets and forwards the packets to their destination networks. LSP establishment LSPs include static and dynamic LSPs.
Page 13: Mpls Forwarding
MPLS forwarding Figure 5 MPLS forwarding FIB table LFIB table Dest Out label Nexthop Out int In label Oper Out label Nexthop Out int Router C Vlan20 Router E Vlan40 10.1.0.0 LFIB table In label Oper Out label Nexthop Out int Swap Router D Vlan30...
Page 14: Protocols And Standards
• One LFIB lookup and one FIB lookup (if the packet has only one label). The penultimate hop popping (PHP) feature can pop the label at the penultimate node, so the egress node only performs one table lookup. A PHP-capable egress node sends the penultimate node an implicit null label of 3. This label never appears in the label stack of packets.
Page 15: Configuring Mpls Mtu
Step Command Remarks format. As a best practice, use the IP address of a loopback interface as an LSR ID. Enter the view of the interface interface interface-type that needs to perform MPLS interface-number forwarding. By default, MPLS is disabled on an Enable MPLS for the interface.
Page 16: Configuring Ttl Propagation
• Non-null label. The value range for a non-null label is 16 to 1048575. For LSPs established by a label distribution protocol, the label advertised by the egress determines how the penultimate hop processes a labeled packet. • If the egress advertises an implicit null label, the penultimate hop directly pops the top label of a matching packet.
Page 17 Figure 6 TTL propagation TTL 252 TTL 251 TTL 250 TTL 253 TTL 252 TTL 252 TTL 252 TTL 249 TTL 248 LSR A LSR B LSR C LSR D LSR E Egress Ingress TTL 249 TTL 249 IP TTL Label TTL Copy the label TTL value to the IP Copy the TTL value...
Page 18: Enabling Sending Of Mpls Ttl-Expired Messages
Enabling sending of MPLS TTL-expired messages This feature enables an LSR to generate an ICMP TTL-expired message upon receiving an MPLS packet with a TTL of 1. If the MPLS packet has only one label, the LSR sends the ICMP TTL-expired message back to the source through IP routing.
Page 19: Displaying And Maintaining Mpls
Displaying and maintaining MPLS Execute display commands in any view and reset commands in user view. Task Command Display MPLS interface information. display mpls interface [ interface-type interface-number ] Display usage information about MPLS display mpls label { label-value1 [ to label-value2 ] | all } labels.
Page 20: Configuring A Static Lsp
Configuring a static LSP Overview A static label switched path (LSP) is established by manually specifying the incoming label and outgoing label on each node (ingress, transit, or egress node) of the forwarding path. Static LSPs consume fewer resources, but they cannot automatically adapt to network topology changes.
Page 21: Displaying Static Lsps
Step Command Remarks static LSP. outgoing-interface interface-type node has an active route to the interface-number } out-label out-label specified next hop address. You do not need to configure this Configure static-lsp egress lsp-name in-label command if the outgoing label egress node of the in-label configured on the penultimate hop static LSP.
Page 22: Configuration Procedure
Configuration procedure Create VLANs and configure IP addresses for all interfaces, including the loopback interfaces, as shown in Figure 8. (Details not shown.) Configure a static route to the destination address of each LSP: # On Switch A, configure a static route to network 21.1.1.0/24. <SwitchA>...
Page 23: Verifying The Configuration
Verifying the configuration # Display static LSP information on switches. This example uses Switch A. [SwitchA] display mpls static-lsp Total: 2 Name In/Out Label Nexthop/Out Interface State AtoC 21.1.1.0/24 NULL/30 10.1.1.2 CtoA 70/NULL # Test the connectivity of the LSP from Switch A to Switch C. [SwitchA] ping mpls -a 11.1.1.1 ipv4 21.1.1.0 24 MPLS Ping FEC: 21.1.1.0/24 : 100 data bytes 100 bytes from 20.1.1.2: Sequence=1 time=4 ms...
Page 24: Configuring Ldp
Configuring LDP Overview The Label Distribution Protocol (LDP) dynamically distributes FEC-label mapping information between LSRs to establish LSPs. Terminology LDP session Two LSRs establish a TCP-based LDP session to exchange FEC-label mappings. LDP peer Two LSRs that use LDP to exchange FEC-label mappings are LSR peers. Label spaces and LDP identifiers Label spaces include the following types: •...
Page 25: Ldp Operation
• Notification messages—Provide advisory information and notify errors, such as Notification messages. LDP uses UDP to transport discovery messages for efficiency, and uses TCP to transport session, advertisement, and notification messages for reliability. LDP operation LDP operates in the following phases: Discovering and maintaining LDP peers LDP discovers peers in the following ways: •...
Page 26: Label Distribution And Control
Figure 9 Dynamically establishing an LSP Ingress Egress LSR A LSR C LSR B LSR D LSR E LSR F LSR G LSR H Label mapping Label distribution and control Label advertisement modes Figure 10 Label advertisement modes 1) Unsolicitedly distributes a label mapping for a FEC to the upstream.
Page 27 Label distribution control LDP controls label distribution in one of the following ways: • Independent label distribution—Distributes an FEC-label mapping to an upstream LSR at any time. An LSR might distribute a mapping for an FEC to its upstream LSR before it receives a label mapping for that FEC from its downstream LSR.
Page 28: Ldp Gr
LDP GR LDP GR overview LDP Graceful Restart (GR) enables an LSR to retain MPLS forwarding entries during an LDP restart, ensuring continuous MPLS forwarding. Figure 12 LDP GR GR helper LDP session GR restarter LDP session LDP session GR helper GR helper As shown in Figure...
Page 29: Ldp Nsr
b. Starts the Reconnect timer received from the GR restarter. After LDP completes restart, the GR restarter re-establishes an LDP session with the GR helper. If the LDP session is not set up before the Reconnect timer expires, the GR helper deletes ...
Page 30: Ldp-Igp Synchronization
LDP-IGP synchronization Basic operating mechanism LDP establishes LSPs based on the IGP optimal route. If LDP is not synchronized with IGP, MPLS traffic forwarding might be interrupted. LDP is not synchronized with IGP when one of the following occurs: • A link is up, and IGP advertises and uses this link.
Page 31: Protocols
You can use one of the following methods to enable IP FRR: • Configure an IGP to automatically calculate a backup next hop. • Configure an IGP to specify a backup next hop by using a routing policy. Figure 14 Network diagram for LDP FRR LSR C LSR A LSR B...
Page 32: Enabling Ldp
Tasks at a glance (Optional.) Configuring LDP session protection (Optional.) Configuring LDP GR (Optional.) Configuring LDP NSR (Optional.) Configuring LDP-IGP synchronization (Optional.) Configuring LDP FRR (Optional.) Resetting LDP sessions (Optional.) Enabling SNMP notifications for LDP Enabling LDP To enable LDP, you must first enable LDP globally. Then, enable LDP on relevant interfaces or configure IGP to automatically enable LDP on those interfaces.
Page 33: Configuring Hello Parameters
Configuring Hello parameters Perform this task to configure the following hello timers: • Link Hello hold time and Link Hello interval. • Targeted Hello hold time and Targeted Hello interval for a specific peer. Configuring Link Hello timers Step Command Remarks Enter system view.
Page 34: Configuring Ldp Backoff
Configuring LDP sessions parameters for Basic Discovery mechanism Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the Keepalive hold mpls ldp timer keepalive-hold By default, the Keepalive hold time. timeout time is 45 seconds. Configure Keepalive mpls...
Page 35: Configuring Ldp Md5 Authentication
start an attempt until the initial delay timer expires. If the session setup fails again, LDP waits for two times the initial delay before the next attempt, and so forth until the maximum delay time is reached. After that, the maximum delay time will always take effect. To configure LDP backoff: Step Command...
Page 36: Configuring The Ldp Label Distribution Control Mode
By default, LDP uses only host routes with a 32-bit mask to establish LSPs. The other two methods can result in more LSPs than the default policy. To change the policy, be sure that the system resources and bandwidth resources are sufficient. To configure an LSP generation policy: Step Command...
Page 37: Configuring A Label Acceptance Policy
Figure 15 Label advertisement control diagram Advertise label mappings permitted by IP prefix list B LSR B LSR A LSR C A label advertisement policy on an LSR and a label acceptance policy on its upstream LSR can achieve the same purpose. If downstream LSRs support label advertisement control, use label advertisement policies as a best practice to reduce network load.
Page 38: Configuring Ldp Loop Detection
Figure 16 Label acceptance control diagram Drop the label Label mappings not permitted mappings by the IP prefix list LSR B LSR A Label mappings permitted Accept the by the IP prefix list label mappings LSR C A label advertisement policy on an LSR and a label acceptance policy on its upstream LSR can achieve the same purpose.
Page 39: Configuring Ldp Session Protection
Step Command Remarks • Enter view: mpls ldp • Enter LDP-VPN instance view: Enter LDP view or enter LDP-VPN instance view. a. mpls ldp b. vpn-instance vpn-instance-name By default, loop detection is disabled. After loop detection Enable loop detection. loop-detect enabled, the device uses both the maximum hop count and the path vector methods to...
Page 40: Configuring Ldp Gr
Configuring LDP GR Before you configure LDP GR, enable LDP on the GR restarter and GR helpers. To configure LDP GR: Step Command Remarks Enter system view. system-view Enter LDP view. mpls ldp Enable LDP GR. graceful-restart By default, LDP GR is disabled. Configure the Reconnect graceful-restart timer reconnect By default, the Reconnect time is...
Page 41: Configuring Ldp-Isis Synchronization
Step Command Remarks interface interface-type Enter interface view. interface-number (Optional.) Disable LDP-IGP By default, LDP-IGP synchronization synchronization mpls ldp igp sync disable is not disabled on an interface. interface. Return to system view. quit Enter LDP view. mpls ldp (Optional.) Set the delay for By default, LDP immediately notifies LDP to notify IGP of the LDP igp sync delay time...
Page 42: Configuring Ldp Frr
Step Command Remarks Enter system view. system-view Enter IS-IS view. isis [ process-id ] Enable LDP-ISIS default, LDP-ISIS mpls ldp sync [ level-1 | level-2 ] synchronization. synchronization is disabled. Return to system view. quit interface interface-type Enter interface view. interface-number (Optional.) Disable LDP-IGP default,...
Page 43: Displaying And Maintaining Ldp
Step Command Remarks Enter system view. system-view Enable SNMP By default, SNMP notifications for snmp-agent trap enable ldp notifications for LDP. LDP are enabled. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide. Displaying and maintaining LDP Execute display commands in any view.
Page 44 Figure 17 Network diagram Loop0 Loop0 Loop0 2.2.2.9/32 3.3.3.9/32 1.1.1.9/32 Vlan-int2 Vlan-int3 10.1.1.1/24 20.1.1.2/24 Vlan-int4 Vlan-int5 Vlan-int2 Vlan-int3 11.1.1.1/24 21.1.1.1/24 10.1.1.2/24 20.1.1.1/24 Switch A Switch B Switch C 11.1.1.0/24 21.1.1.0/24 Requirements analysis • To ensure that the LSRs establish LSPs automatically, enable LDP on each LSR. •...
Page 45 [SwitchC-ospf-1] quit # Display routing tables on the switches, for example, on Switch A, to verify that the switches have learned the routes to each other. [SwitchA] display ip routing-table Destinations : 21 Routes : 21 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0...
Page 46 [SwitchB-Vlan-interface3] mpls ldp enable [SwitchB-Vlan-interface3] quit # Configure Switch C. [SwitchC] mpls lsr-id 3.3.3.9 [SwitchC] mpls ldp [SwitchC-ldp] quit [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable [SwitchC-Vlan-interface3] mpls ldp enable [SwitchC-Vlan-interface3] quit Configure LSP generation policies: # On Switch A, create IP prefix list switcha, and configure LDP to use only the routes permitted by the prefix list to establish LSPs.
Page 47: Label Acceptance Control Configuration Example
In/Out Label Nexthop OutInterface 1.1.1.9/32 -/1279(L) 2.2.2.9/32 10.1.1.2 Vlan-int2 1279/3 10.1.1.2 Vlan-int2 3.3.3.9/32 -/1278 10.1.1.2 Vlan-int2 1278/1278 10.1.1.2 Vlan-int2 11.1.1.0/24 1277/- -/1277(L) 21.1.1.0/24 -/1276 10.1.1.2 Vlan-int2 1276/1276 10.1.1.2 Vlan-int2 # Test the connectivity of the LDP LSP from Switch A to Switch C. [SwitchA] ping mpls -a 11.1.1.1 ipv4 21.1.1.0 24 MPLS Ping FEC: 21.1.1.0/24 : 100 data bytes 100 bytes from 20.1.1.2: Sequence=1 time=1 ms...
Page 48 Figure 18 Network diagram Loop0 2.2.2.9/32 Vlan-int2 Vlan-int3 10.1.1.2/24 20.1.1.1/24 Loop0 Loop0 1.1.1.9/32 Switch B 3.3.3.9/32 Vlan-int3 Vlan-int2 20.1.1.2/24 10.1.1.1/24 Vlan-int7 Vlan-int4 Vlan-int6 Vlan-int5 40.1.1.2/24 11.1.1.1/24 30.1.1.1/24 Loop0 21.1.1.1/24 4.4.4.9/32 Switch A Switch C Vlan-int6 Vlan-int7 30.1.1.2/24 40.1.1.1/24 Switch D 11.1.1.0/24 21.1.1.0/24 Requirements analysis...
Page 49 # Configure Switch B. <SwitchB> system-view [SwitchB] mpls lsr-id 2.2.2.9 [SwitchB] mpls ldp [SwitchB-ldp] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] mpls enable [SwitchB-Vlan-interface2] mpls ldp enable [SwitchB-Vlan-interface2] quit [SwitchB] interface vlan-interface 3 [SwitchB-Vlan-interface3] mpls enable [SwitchB-Vlan-interface3] mpls ldp enable [SwitchB-Vlan-interface3] quit # Configure Switch C.
Page 50 # On Switch B, create IP prefix list switchb, and configure LDP to use only the routes permitted by the prefix list to establish LSPs. [SwitchB] ip prefix-list switchb index 10 permit 11.1.1.0 24 [SwitchB] ip prefix-list switchb index 20 permit 21.1.1.0 24 [SwitchB] mpls ldp [SwitchB-ldp] lsp-trigger prefix-list switchb [SwitchB-ldp] quit...
Page 51: Label Advertisement Control Configuration Example
Status Flags: * - stale, L - liberal, B - backup Statistics: FECs: 2 Ingress LSPs: 1 Transit LSPs: 1 Egress LSPs: 1 In/Out Label Nexthop OutInterface 11.1.1.0/24 1277/- -/1148(L) 21.1.1.0/24 -/1149(L) -/1276 10.1.1.2 Vlan-int2 1276/1276 10.1.1.2 Vlan-int2 The output shows that the next hop of the LSP for FEC 21.1.1.0/24 is Switch B (10.1.1.2). The LSP has been established over the link Switch A—Switch B—Switch C, not over the link Switch A—Switch D—Switch C.
Page 52 Figure 19 Network diagram Loop0 2.2.2.9/32 Vlan-int2 Vlan-int3 10.1.1.2/24 20.1.1.1/24 Loop0 Loop0 1.1.1.9/32 Switch B 3.3.3.9/32 Vlan-int3 Vlan-int2 20.1.1.2/24 10.1.1.1/24 Vlan-int7 Vlan-int4 Vlan-int6 Vlan-int5 40.1.1.2/24 11.1.1.1/24 30.1.1.1/24 Loop0 21.1.1.1/24 4.4.4.9/32 Switch A Switch C Vlan-int6 Vlan-int7 30.1.1.2/24 40.1.1.1/24 Switch D 11.1.1.0/24 21.1.1.0/24 Requirements analysis...
Page 53 # Configure Switch B. <SwitchB> system-view [SwitchB] mpls lsr-id 2.2.2.9 [SwitchB] mpls ldp [SwitchB-ldp] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] mpls enable [SwitchB-Vlan-interface2] mpls ldp enable [SwitchB-Vlan-interface2] quit [SwitchB] interface vlan-interface 3 [SwitchB-Vlan-interface3] mpls enable [SwitchB-Vlan-interface3] mpls ldp enable [SwitchB-Vlan-interface3] quit # Configure Switch C.
Page 54 # On Switch B, create IP prefix list switchb, and configure LDP to use only the routes permitted by the prefix list to establish LSPs. [SwitchB] ip prefix-list switchb index 10 permit 11.1.1.0 24 [SwitchB] ip prefix-list switchb index 20 permit 21.1.1.0 24 [SwitchB] mpls ldp [SwitchB-ldp] lsp-trigger prefix-list switchb [SwitchB-ldp] quit...
Page 55 # On Switch D, create IP prefix list peer-a to permit 1.1.1.9/32. Switch D uses this list to filter peers. [SwitchD] ip prefix-list peer-a index 10 permit 1.1.1.9 32 # On Switch D, create IP prefix list prefix-to-c to deny subnet 11.1.1.0/24. Switch D uses this list to filter FEC-label mappings to be advertised to Switch C.
Page 56: Ldp Frr Configuration Example
21.1.1.0/24 1149/- -/1276(L) -/1150(L) [SwitchD] display mpls ldp lsp Status Flags: * - stale, L - liberal, B - backup Statistics: FECs: 2 Ingress LSPs: 0 Transit LSPs: 0 Egress LSPs: 2 In/Out Label Nexthop OutInterface 11.1.1.0/24 1151/- -/1277(L) 21.1.1.0/24 1150/- The output shows that Switch A and Switch C have received FEC-label mappings only from Switch B.
Page 57 When the primary LSP operates correctly, traffic between subnets 11.1.1.0/24 and 21.1.1.0/24 is forwarded through the LSP. When the primary LSP fails, traffic between the two subnets can be immediately switched to the backup LSP. Figure 20 Network diagram Loop0 2.2.2.2/32 Switch A Backup LSP...
Page 58 <SwitchS> system-view [SwitchS] bfd echo-source-ip 10.10.10.10 [SwitchS] ip prefix-list abc index 10 permit 21.1.1.0 24 [SwitchS] route-policy frr permit node 10 [SwitchS-route-policy] if-match ip address prefix-list abc [SwitchS-route-policy] apply fast-reroute backup-interface vlan-interface 12 backup-nexthop 12.12.12.2 [SwitchS-route-policy] quit [SwitchS] ospf 1 [SwitchS-ospf-1] fast-reroute route-policy frr [SwitchS-ospf-1] quit # Configure Switch D.
Page 59 # Configure Switch A. [SwitchA] mpls lsr-id 2.2.2.2 [SwitchA] mpls ldp [SwitchA-mpls-ldp] quit [SwitchA] interface vlan-interface 12 [SwitchA-Vlan-interface12] mpls enable [SwitchA-Vlan-interface12] mpls ldp enable [SwitchA-Vlan-interface12] quit [SwitchA] interface vlan-interface 24 [SwitchA-Vlan-interface24] mpls enable [SwitchA-Vlan-interface24] mpls ldp enable [SwitchA-Vlan-interface24] quit Configure LSP generation policies so LDP using all static routes and IGP routes to establish LSPs: # Configure Switch S.
Page 60: Configuring Mpls Te
Configuring MPLS TE Overview TE and MPLS TE Network congestion can degrade the network backbone performance. It might occur when network resources are inadequate or when load distribution is unbalanced. Traffic engineering (TE) is intended to avoid the latter situation where partial congestion might occur because of improper resource allocation.
Page 61 Dynamic CRLSPs adapt to network changes and support CRLSP backup and fast reroute, but they require complicated configurations. Advertising TE attributes MPLS TE uses extended link state IGPs, such as OSPF and IS-IS, to advertise TE attributes for links. TE attributes include the maximum bandwidth, maximum reservable bandwidth, non-reserved bandwidth for each priority, and the link attribute.
Page 62: Traffic Forwarding
Strict explicit path—Among the nodes that the path must traverse, a node and its previous  hop must be connected directly. Loose explicit path—Among the nodes that the path must traverse, a node and its  previous hop can be connected indirectly. Strict explicit path precisely specifies the path that an MPLS TE tunnel must traverse.
Page 63: Make-Before-Break
Figure 21 IGP shortcut and forwarding adjacency diagram Router B Router C Router A Router D Router E As shown in Figure 21, an MPLS TE tunnel is present from Router D to Router C. IGP shortcut enables only the ingress node Router D to use the MPLS TE tunnel in the IGP route calculation. Router A cannot use this tunnel to reach Router C.
Page 64: Route Pinning
Figure 22 Diagram for make-before-break Router A Router B Router C Router D Router E As shown in Figure 22, a CRLSP with 30 M reserved bandwidth has been set up from Router A to Router D through the path Router A—Router B—Router C—Router D. To increase the reserved bandwidth to 40 M, a new CRLSP must be set up through the path Router A——Router E—Router C—Router D.
Page 65: Crlsp Backup
You can use a command to limit the maximum and minimum bandwidth. If the tunnel bandwidth calculated by auto bandwidth adjustment is greater than the maximum bandwidth, MPLS TE uses the maximum bandwidth to set up the new CRLSP. If it is smaller than the minimum bandwidth, MPLS TE uses the minimum bandwidth to set up the new CRLSP.
Page 66: Diffserv-Aware Te
• Node protection—The PLR and the MP are connected through a device and the primary CRLSP traverses this device. When the device fails, traffic is switched to the bypass tunnel. As shown in Figure 24, the primary CRLSP is Router A—Router B—Router C—Router D—Router E, and the bypass tunnel is Router B—Router F—Router D.
Page 67 How DS-TE operates A device takes the following steps to establish an MPLS TE tunnel for a CT: Determines the CT. A device classifies traffic according to your configuration: When configuring a dynamic MPLS TE tunnel, you can use the mpls te bandwidth ...
Page 68: Bidirectional Mpls Te Tunnel
Figure 26 MAM bandwidth constraints model CT 0 BC 0 CT 1 BC 1 CT 2 BC 2 CT 0 CT 1 CT 2 Max reservable BW Checks whether the CT and the LSP setup/holding priority match an existing TE class. An MPLS TE tunnel can be established for the CT only when the following conditions are met: Every node along the tunnel has a TE class that matches the CT and the LSP setup priority.
Page 69: Mpls Te Configuration Task List
• ITU-T Recommendation Y.1720, Protection switching for MPLS networks MPLS TE configuration task list To configure an MPLS TE tunnel to use a static CRLSP, complete the following tasks: Enable MPLS TE on each node and interface that the MPLS TE tunnel traverses. Create a tunnel interface on the ingress node of the MPLS TE tunnel, and specify the tunnel destination address (the address of the egress node).
Page 70: Enabling Mpls Te
Tasks at a glance (Optional.) Configuring MPLS TE FRR Only MPLS TE tunnels established by RSVP-TE support this configuration. Enabling MPLS TE Enable MPLS TE on each node and interface that the MPLS TE tunnel traverses. Before you enable MPLS TE, complete the following tasks: •...
Page 71: Configuring An Mpls Te Tunnel To Use A Static Crlsp
To configure DS-TE: Step Command Remarks Enter system view. system-view Enter MPLS TE view. mpls te (Optional.) Configure the DS-TE By default, the DS-TE mode is ds-te mode ietf mode as IETF. prestandard. (Optional.) Configure the BC By default, the BC model of IETF ds-te bc-model mam model of IETF DS-TE as MAM.
Page 72: Configuring An Mpls Te Tunnel To Use A Dynamic Crlsp
Step Command Remarks Specify the MPLS TE tunnel default, MPLS uses establishment mode mpls te signaling static RSVP-TE to establish a tunnel. static. Apply the static CRLSP to By default, a tunnel does not mpls te static-cr-lsp lsp-name the tunnel interface. reference any static CRLSP.
Page 73: Advertising Link Te Attributes By Using Igp Te Extension
Step Command Remarks link bandwidth for MPLS bandwidth-value bandwidth MPLS TE traffic. traffic is 0. • Configure the maximum reservable bandwidth of the link (BC 0) and BC 1 in RDM model of the prestandard DS-TE: mpls te max-reservable-bandwidth bandwidth-value Use one command according bc1-bandwidth ] to the DS-TE mode and BC...
Page 74: Configuring Mpls Te Tunnel Constraints
Step Command Remarks Enable MPLS TE for the By default, an OSPF area does not mpls te enable OSPF area. support MPLS TE. Configuring IS-IS TE IS-IS TE uses a sub-TLV of the extended IS reachability TLV (type 22) to carry TE attributes. Because the extended IS reachability TLV carries wide metrics, specify a wide metric-compatible metric style for the IS-IS process before enabling IS-IS TE.
Page 75 Configuring the affinity attribute for an MPLS TE tunnel The associations between the link attribute and the affinity attribute might vary by vendor. To ensure the successful establishment of a tunnel between two devices from different vendors, correctly configure their respective link attribute and affinity attribute. To configure the affinity attribute for an MPLS TE tunnel: Step Command...
Page 76: Establishing An Mpls Te Tunnel By Using Rsvp-Te
Step Command Remarks CRLSP bypass the specified node. Return to system view. quit Enter MPLS tunnel interface tunnel tunnel-number interface view. [ mode mpls-te ] Configure the MPLS TE tunnel interface to use the mpls te path preference value By default, MPLS TE uses the explicit path, and specify a explicit-path path-name...
Page 77 Step Command Remarks Enter system view. system-view Enter MPLS TE view. mpls te By default, a tunnel uses the TE Specify the metric type to metric for path selection. use when no metric type is path-metric-type { igp | te } Execute this command on the explicitly configured for a ingress node of an MPLS TE...
Page 78: Controlling Mpls Te Tunnel Setup
Step Command Remarks Enter system view. system-view Enter MPLS tunnel interface tunnel tunnel-number interface view. [ mode mpls-te ] mpls reoptimization By default, tunnel reoptimization Enable tunnel reoptimization. [ frequency seconds ] is disabled. Return to user view. return (Optional.) Immediately reoptimize MPLS...
Page 79 Enabling route and label recording Perform this task to record the nodes that an MPLS TE tunnel traverses and the label assigned by each node. The recorded information helps you know about the path used by the MPLS TE tunnel and the label distribution information, and when the tunnel fails, it helps you locate the fault.
Page 80 Configuring automatic bandwidth adjustment Step Command Remarks Enter system view. system-view Enter MPLS TE view. mpls te default, global auto bandwidth adjustment is disabled. The sampling interval configured in Enable automatic MPLS TE view applies to all MPLS bandwidth adjustment auto-bandwidth enable TE tunnels.
Page 81: Configuring Traffic Forwarding
Configuring traffic forwarding Perform the tasks in this section on the ingress node of the MPLS TE tunnel. Configuring static routing to direct traffic to an MPLS TE tunnel Step Command Remarks Enter system view. system-view By default, no static route exists on the device.
Page 82: Configuring A Bidirectional Mpls Te Tunnel
Step Command Remarks OSPF and IS-IS will include the MPLS TE tunnel in route calculation. By default, the metric of an Assign a metric to the mpls te igp metric { absolute value | MPLS TE tunnel equals its IGP MPLS TE tunnel.
Page 83: Configuring Crlsp Backup
Step Command Remarks Enter system view. system-view Enter MPLS tunnel interface tunnel tunnel-number interface view. [ mode mpls-te ] By default, no bidirectional tunnel Configure co-routed mpls te bidirectional co-routed configured, tunnels bidirectional MPLS TE tunnel passive reverse-lsp lsr-id established tunnel and specify the local end as ingress-lsr-id tunnel-id tunnel-id...
Page 84: Enabling Frr
• Only MPLS TE tunnels established through RSVP-TE support FRR. Enabling FRR Perform this task on the ingress node of a primary CRLSP. To enable FRR: Step Command Remarks Enter system view. system-view Enter tunnel interface view of interface tunnel tunnel-number the primary CRLSP.
Page 85 Table 2 FRR protection principles Primary Bandwidt CRLSP h required requires Bypass tunnel providing Bypass tunnel providing no bandwidth bandwidth protection bandwidth protection primary protection CRLSP The primary CRLSP can be bound to the bypass tunnel if CT 0 or no CT is specified for the bypass tunnel.
Page 86 Primary Bandwidt CRLSP h required requires Bypass tunnel providing Bypass tunnel providing no bandwidth bandwidth protection bandwidth protection primary protection CRLSP carries the bandwidth protection protection. flag. This bypass tunnel is selected only when no bypass tunnel that does provide bandwidth protection can be bound to the primary CRLSP.
Page 87 Step Command Remarks Configure the bandwidth and mpls te backup bandwidth [ ct0 By default, the bandwidth and the the CT to be protected by the | ct1 | ct2 | ct3 ] { bandwidth | CT to be protected by the bypass bypass tunnel.
Page 88: Configuring Node Fault Detection
Configuring node fault detection Perform this task to configure the RSVP hello mechanism or BFD on the PLR and the protected node to detect the node faults caused by signaling protocol faults. FRR does not need to use the RSVP hello mechanism or BFD to detect the node faults caused by the link faults between the PLR and the protected node.
Page 89: Mpls Te Configuration Examples
Task Command Display sub-TLV information for IS-IS TE. display isis mpls te configured-sub-tlvs [ process-id ] display isis mpls te network [ [ level-1 | level-2 ] | Display network information in an IS-IS TEDB. local | lsp-id lsp-id ]* [ process-id ] display isis mpls te tunnel [ level-1 | level-2 ] Display IS-IS tunnel interface information.
Page 90 Figure 27 Network diagram Loop0 2.2.2.2/32 Vlan-int1 Vlan-int2 3.2.1.1/24 2.1.1.2/24 Switch B Vlan-int1 Vlan-int2 2.1.1.1/24 3.2.1.2/24 Switch A Switch C Loop0 Loop0 3.3.3.3/32 1.1.1.1/32 Configuration procedure Configure IP addresses and masks for interfaces. (Details not shown.) Configure IS-IS to advertise interface addresses, including the loopback interface address: # Configure Switch A.
Page 91 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] isis enable 1 [SwitchC-Vlan-interface2] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] isis enable 1 [SwitchC-LoopBack0] quit # Execute the display ip routing-table command on each switch to verify that the switches have learned the routes to one another, including the routes to the loopback interfaces. (Details not shown.) Configure an LSR ID, and enable MPLS and MPLS TE: # Configure Switch A.
Page 92 [SwitchB-Vlan-interface1] mpls te max-reservable-bandwidth 5000 [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] mpls te max-link-bandwidth 10000 [SwitchB-Vlan-interface2] mpls te max-reservable-bandwidth 5000 [SwitchB-Vlan-interface2] quit # Configure the maximum link bandwidth and maximum reservable bandwidth on Switch C. [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls te max-link-bandwidth 10000 [SwitchC-Vlan-interface2] mpls te max-reservable-bandwidth 5000 [SwitchC-Vlan-interface2] quit...
Page 93 Bandwidth: 64kbps Maximum Transmit Unit: 1496 Internet Address is 6.1.1.1/24 Primary Tunnel source unknown, destination 3.3.3.3 Tunnel TTL 255 Tunnel protocol/transport CR_LSP Output queue - Urgent queuing: Size/Length/Discards 0/100/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 Output queue - FIFO queuing: Size/Length/Discards 0/75/0 Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec...
Page 94: Establishing An Mpls Te Tunnel With Rsvp-Te
# Execute the display mpls lsp command or the display mpls static-cr-lsp command on each switch to display static CRLSP information. [SwitchA] display mpls lsp Proto In/Out Label Interface/Out NHLFE 1.1.1.1/0/1 StaticCR -/20 Vlan1 2.1.1.2 Local Vlan1 [SwitchB] display mpls lsp Proto In/Out Label Interface/Out NHLFE...
Page 95 Table 3 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Loop0 1.1.1.9/32 Switch D Loop0 4.4.4.9/32 Vlan-int1 10.1.1.1/24 Vlan-int3 30.1.1.2/24 Switch B Loop0 2.2.2.9/32 Switch C Loop0 3.3.3.9/32 Vlan-int1 10.1.1.2/24 Vlan-int3 30.1.1.1/24 Vlan-int2 20.1.1.1/24 Vlan-int2 20.1.1.2/24...
Page 96 [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] isis enable 1 [SwitchC-Vlan-interface3] isis circuit-level level-2 [SwitchC-Vlan-interface3] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] isis enable 1 [SwitchC-Vlan-interface2] isis circuit-level level-2 [SwitchC-Vlan-interface2] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] isis enable 1 [SwitchC-LoopBack0] isis circuit-level level-2 [SwitchC-LoopBack0] quit # Configure Switch D.
Page 97 [SwitchB-Vlan-interface1] mpls te enable [SwitchB-Vlan-interface1] rsvp enable [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] mpls enable [SwitchB-Vlan-interface2] mpls te enable [SwitchB-Vlan-interface2] rsvp enable [SwitchB-Vlan-interface2] quit # Configure Switch C. [SwitchC] mpls lsr-id 3.3.3.9 [SwitchC] mpls te [SwitchC-te] quit [SwitchC] rsvp [SwitchC-rsvp] quit [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable...
Page 98 [SwitchC-isis-1] cost-style wide [SwitchC-isis-1] mpls te enable level-2 [SwitchC-isis-1] quit # Configure Switch D. [SwitchD] isis 1 [SwitchD-isis-1] cost-style wide [SwitchD-isis-1] mpls te enable level-2 [SwitchD-isis-1] quit Configure MPLS TE attributes of links: # Configure the maximum link bandwidth and maximum reservable bandwidth on Switch A. [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] mpls te max-link-bandwidth 10000 [SwitchA-Vlan-interface1] mpls te max-reservable-bandwidth 5000...
Page 99 [SwitchA-Tunnel1] quit Configure a static route on Switch A to direct the traffic destined for subnet 30.1.1.0/24 to MPLS TE tunnel 1. [SwitchA] ip route-static 30.1.1.2 24 tunnel 1 preference 1 Verifying the configuration # Execute the display interface tunnel command on Switch A. The output shows that the tunnel interface is up.
Page 100: Establishing An Inter-As Mpls Te Tunnel With Rsvp-Te
Route Pinning : Disabled Retry Limit : 10 Retry Interval : 2 sec Reoptimization : Disabled Reoptimization Freq Backup Type : None Backup LSP ID Auto Bandwidth : Disabled Auto Bandwidth Freq Min Bandwidth Max Bandwidth Collected Bandwidth # Execute the display ip routing-table command on Switch A. The output shows a static route entry with interface Tunnel 1 as the output interface.
Page 101 Configure OSPF to advertise routes within the ASs, and redistribute the direct and BGP routes into OSPF on Switch B and Switch C: # Configure Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B.
Page 102 2.2.2.9/32 OSPF 10.1.1.2 Vlan1 10.1.1.0/24 Direct 0 10.1.1.1 Vlan1 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 Configure BGP on Switch B and Switch C to make sure the ASs can communicate with each other: # Configure Switch B.
Page 103 [SwitchA] rsvp [SwitchA-rsvp] quit [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] mpls enable [SwitchA-Vlan-interface1] mpls te enable [SwitchA-Vlan-interface1] rsvp enable [SwitchA-Vlan-interface1] quit # Configure Switch B. [SwitchB] mpls lsr-id 2.2.2.9 [SwitchB] mpls te [SwitchB-te] quit [SwitchB] rsvp [SwitchB-rsvp] quit [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] mpls enable [SwitchB-Vlan-interface1] mpls te enable [SwitchB-Vlan-interface1] rsvp enable...
Page 104 [SwitchD-Vlan-interface3] rsvp enable [SwitchD-Vlan-interface3] quit Configure OSPF TE: # Configure Switch A. [SwitchA] ospf [SwitchA-ospf-1] opaque-capability enable [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] mpls te enable [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B. [SwitchB] ospf [SwitchB-ospf-1] opaque-capability enable [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] mpls te enable [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit...
Page 105 [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] mpls te max-link-bandwidth 10000 [SwitchB-Vlan-interface2] mpls te max-reservable-bandwidth 5000 [SwitchB-Vlan-interface2] quit # Configure the maximum link bandwidth and maximum reservable bandwidth on Switch C. [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls te max-link-bandwidth 10000 [SwitchC-Vlan-interface2] mpls te max-reservable-bandwidth 5000 [SwitchC-Vlan-interface2] quit [SwitchC] interface vlan-interface 3...
Page 106 Tunnel protocol/transport CR_LSP Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 drops 3077 packets output, 197028 bytes, 0 drops # Execute the display mpls te tunnel-interface command on Switch A to display detailed information about the MPLS TE tunnel.
Page 107: Bidirectional Mpls Te Tunnel Configuration Example
1.1.1.9/32 Direct 0 127.0.0.1 InLoop0 2.2.2.9/32 OSPF 10.1.1.2 Vlan1 3.3.3.9/32 O_ASE 10.1.1.2 Vlan1 4.4.4.9/32 O_ASE 10.1.1.2 Vlan1 7.1.1.0/24 Direct 0 7.1.1.1 Tun1 7.1.1.1/32 Direct 0 127.0.0.1 InLoop0 10.1.1.0/24 Direct 0 10.1.1.1 Vlan1 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 20.1.1.0/24 O_ASE 10.1.1.2 Vlan1 30.1.1.0/24 Static 1...
Page 108 # Configure Switch A. <SwitchA> system-view [SwitchA] mpls lsr-id 1.1.1.9 [SwitchA] mpls label advertise non-null [SwitchA] mpls te [SwitchA-te] quit [SwitchA] rsvp [SwitchA-rsvp] quit [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] mpls enable [SwitchA-Vlan-interface1] mpls te enable [SwitchA-Vlan-interface1] rsvp enable [SwitchA-Vlan-interface1] quit # Configure Switch B.
Page 109 <SwitchD> system-view [SwitchD] mpls lsr-id 4.4.4.9 [SwitchD] mpls label advertise non-null [SwitchD] mpls te [SwitchD-te] quit [SwitchD] rsvp [SwitchD-rsvp] quit [SwitchD] interface vlan-interface 3 [SwitchD-Vlan-interface3] mpls enable [SwitchD-Vlan-interface3] mpls te enable [SwitchD-Vlan-interface3] rsvp enable [SwitchD-Vlan-interface3] quit Configure IS-IS TE: # Configure Switch A. [SwitchA] isis 1 [SwitchA-isis-1] cost-style wide [SwitchA-isis-1] mpls te enable level-2...
Page 110 [SwitchD-Tunnel4] mpls te bidirectional co-routed passive reverse-lsp lsr-id 1.1.1.9 tunnel-id 1 [SwitchD-Tunnel4] quit Verifying the configuration # Execute the display interface tunnel command on Switch A. The output shows that the tunnel interface is up. [SwitchA] display interface tunnel Tunnel1 current state: UP Line protocol current state: UP Description: Tunnel1 Interface The Maximum Transmit Unit is 64000...
Page 111 Retry Limit : 10 Retry Interval : 2 sec Reoptimization : Disabled Reoptimization Freq Backup Type : None Backup LSP ID Auto Bandwidth : Disabled Auto Bandwidth Freq Min Bandwidth Max Bandwidth Collected Bandwidth # Execute the display mpls lsp verbose command on Switch A to display detailed information about the bidirectional MPLS TE tunnel.
Page 112 Tunnel bandwidth 64 (kbps) Tunnel TTL 255 Tunnel protocol/transport CR_LSP Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 drops 0 packets output, 0 bytes, 0 drops # Execute the display mpls te tunnel-interface command on Switch D to display detailed information about the MPLS TE tunnel.
Page 113: Crlsp Backup Configuration Example
LSR Type : Egress Service In-Label State : Active Nexthop : 127.0.0.1 Out-Interface: - Destination : 4.4.4.9 : 1.1.1.9/1/30478 Protocol : RSVP LSR Type : Ingress Service NHLFE ID : 1025 State : Active Out-Label : 1150 Nexthop : 30.1.1.1 Out-Interface: Vlan1 Destination : 30.1.1.1...
Page 114 Figure 31 Network diagram Switch A Switch B Switch C Loop0 Loop0 Loop0 Vlan-int1 Vlan-int2 Vlan-int1 Vlan-int2 Vlan-int4 Vlan-int3 Switch D Vlan-int4 Vlan-int3 Loop0 Table 6 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Loop0 1.1.1.9/32 Switch D...
Page 115 [SwitchA-Vlan-interface4] rsvp enable [SwitchA-Vlan-interface4] quit # Configure Switch B, Switch C, and Switch D in the same way that Switch A is configured. (Details not shown.) Configure an MPLS TE tunnel on Switch A: # Configure the MPLS TE tunnel interface Tunnel 3. [SwitchA] interface tunnel 3 mode mpls-te [SwitchA-Tunnel3] ip address 9.1.1.1 24 # Specify the tunnel destination address as the LSR ID of Switch C.
Page 116 [SwitchA] display rsvp lsp verbose Tunnel name: SwitchA_t3 Destination: 3.3.3.9 Source: 1.1.1.9 Tunnel ID: 3 LSP ID: 30106 LSR type: Ingress Direction: Unidirectional Setup priority: 7 Holding priority: 7 In-Label: - Out-Label: 1137 In-Interface: - Out-Interface: Vlan1 Nexthop: 10.1.1.2 Exclude-any: 0 Include-Any: 0 Include-all: 0 Mean rate (CIR): 0 kbps...
Page 117: Manual Bypass Tunnel For Frr Configuration Example
# Shut down interface VLAN-interface 2 on Switch B, and then tracert the tunnel destination. The output shows that packets are forwarded on the CRLSP that traverses Switch D. [SwitchA] tracert –a 1.1.1.9 3.3.3.9 traceroute to 3.3.3.9 (3.3.3.9) from 9.1.1.1, 30 hops at most, 40 bytes each pac ket, press CTRL_C to break 30.1.1.2 (30.1.1.2) 3.000 ms...
Page 118 Device Interface IP address Device Interface IP address Vlan-int1 2.1.1.2/24 Switch C Loop0 3.3.3.3/32 Vlan-int2 3.1.1.1/24 Vlan-int3 4.1.1.1/24 Vlan-int4 3.2.1.1/24 Vlan-int2 3.1.1.2/24 Switch D Loop0 4.4.4.4/32 Vlan-int5 3.3.1.2/24 Vlan-int3 4.1.1.2/24 Configuration procedure Configure IP addresses and masks for interfaces. (Details not shown.) Configure IS-IS to advertise interface addresses, including the loopback interface address.
Page 119 [SwitchB-Vlan-interface4] rsvp enable [SwitchB-Vlan-interface4] quit # Configure Switch C in the same way that Switch B is configured. Configure Switch D and Switch E in the same way that Switch A is configured. (Details not shown.) Configure an MPLS TE tunnel on Switch A, the ingress node of the primary CRLSP: # Configure an explicit path for the primary CRLSP.
Page 120 LSP ID : 48960 Tunnel ID Admin State : Normal Ingress LSR ID : 1.1.1.1 Egress LSR ID : 3.3.3.3 Signaling : RSVP-TE Static CRLSP Name Resv Style : SE Tunnel mode Reverse-LSP name Reverse-LSP LSR ID Reverse-LSP Tunnel ID: - Class Type : CT0 Tunnel Bandwidth...
Page 121 [SwitchB-Vlan-interface2] mpls te fast-reroute bypass-tunnel tunnel 5 [SwitchB-Vlan-interface2] quit # Execute the display interface tunnel command on Switch B to verify that the tunnel interface Tunnel 5 is up. (Details not shown.) Configure a static route on Switch A to direct the traffic destined for subnet 4.1.1.0/24 to MPLS TE tunnel 4.
Page 122 Affinity Attr/Mask : 0/0 Explicit Path : pri-path Backup Explicit Path : - Metric Type : TE Record Route : Enabled Record Label : Enabled FRR Flag : Enabled Bandwidth Protection : Disabled Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth Bypass Tunnel : No...
Page 123: Auto Frr Configuration Example
Auto FRR configuration example Network requirements Use RSVP-TE to set up a primary CRLSP that explicitly uses path Switch A—Switch B—Switch C—Switch D. Configure auto FRR on Switch B to automatically set up bypass tunnels for the primary CRLSP. Configure BFD for RSVP-TE between Switch B and Switch C. When the link between Switch B and Switch C fails, BFD can detect the failure quickly and notify RSVP-TE of the failure, so RSVP-TE can switch traffic to the bypass tunnel.
Page 124 Configuration procedure Configure IP addresses and masks for interfaces. (Details not shown.) Configure IS-IS to advertise interface addresses, including the loopback interface address. (Details not shown.) Configure an LSR ID, and enable MPLS, MPLS TE, and RSVP-TE on each switch. Enable BFD for RSVP-TE on Switch B and Switch C: # Configure Switch A.
Page 125 Configure an MPLS TE tunnel on Switch A, the ingress node of the primary CRLSP: # Configure an explicit path named pri-path for the primary CRLSP. [SwitchA] explicit-path pri-path [SwitchA-explicit-path-pri-path] nexthop 2.1.1.2 [SwitchA-explicit-path-pri-path] nexthop 3.1.1.2 [SwitchA-explicit-path-pri-path] nexthop 4.1.1.2 [SwitchA-explicit-path-pri-path] nexthop 4.4.4.4 [SwitchA-explicit-path-pri-path] quit # Configure an MPLS TE tunnel.
Page 126 Tunnel mode Reverse-LSP name Reverse-LSP LSR ID Reverse-LSP Tunnel ID: - Class Type : CT0 Tunnel Bandwidth : 0 kbps Reserved Bandwidth : 0 kbps Setup Priority Holding Priority Affinity Attr/Mask : 0/0 Explicit Path : exp1 Backup Explicit Path : - Metric Type : TE Record Route...
Page 127 LSP ID : 16802 Tunnel ID : 50 Admin State : Normal Ingress LSR ID : 2.2.2.2 Egress LSR ID : 4.4.4.4 Signaling : RSVP-TE Static CRLSP Name Resv Style : SE Tunnel mode Reverse-LSP name Reverse-LSP LSR ID Reverse-LSP Tunnel ID: - Class Type : CT0 Tunnel Bandwidth...
Page 128 Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth Bypass Tunnel : Yes Auto Created : Yes Route Pinning : Disabled Retry Limit Retry Interval : 2 sec Reoptimization : Disabled Reoptimization Freq Backup Type : None Backup LSP ID Auto Bandwidth : Disabled Auto Bandwidth Freq...
Page 129: Ietf Ds-Te Configuration Example
Fast Reroute protection: Ready FRR inner label: 3 Bypass tunnel: Tunnel50 IETF DS-TE configuration example Network requirements Switch A, Switch B, Switch C, and Switch D run IS-IS and all of them are Level-2 switches. Use RSVP-TE to create a TE tunnel from Switch A to Switch D. Traffic of the tunnel belongs to CT 2, and the tunnel needs a bandwidth of 4000 kbps.
Page 130 [SwitchA] interface loopback 0 [SwitchA-LoopBack0] isis enable 1 [SwitchA-LoopBack0] isis circuit-level level-2 [SwitchA-LoopBack0] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] network-entity 00.0005.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] isis enable 1 [SwitchB-Vlan-interface1] isis circuit-level level-2 [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] isis enable 1...
Page 131 [SwitchD-LoopBack0] isis enable 1 [SwitchD-LoopBack0] isis circuit-level level-2 [SwitchD-LoopBack0] quit # Execute the display ip routing-table command on each switch to verify that the switches have learned the routes to one another, including the routes to the loopback interfaces. Take Switch A as an example: [SwitchA] display ip routing-table Destinations : 10...
Page 132 [SwitchB-Vlan-interface2] quit # Configure Switch C. [SwitchC] mpls lsr-id 3.3.3.9 [SwitchC] mpls te [SwitchC-te] ds-te mode ietf [SwitchC-te] quit [SwitchC] rsvp [SwitchC-rsvp] quit [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable [SwitchC-Vlan-interface3] mpls te enable [SwitchC-Vlan-interface3] rsvp enable [SwitchC-Vlan-interface3] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls enable [SwitchC-Vlan-interface2] mpls te enable [SwitchC-Vlan-interface2] rsvp enable...
Page 133 [SwitchD-isis-1] cost-style wide [SwitchD-isis-1] mpls te enable level-2 [SwitchD-isis-1] quit Configure MPLS TE attributes of links: # Configure the maximum bandwidth, maximum reservable bandwidth, and bandwidth constraints on Switch A. [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] mpls te max-link-bandwidth 10000 [SwitchA-Vlan-interface1] mpls te max-reservable-bandwidth rdm 10000 bc1 8000 bc2 5000 bc3 2000 [SwitchA-Vlan-interface1] quit # Configure the maximum bandwidth, maximum reservable bandwidth, and bandwidth...
Page 134 [SwitchA-Tunnel1] mpls te signaling rsvp-te # Assign 4000 kbps bandwidth to CT 2 for the tunnel. [SwitchA-Tunnel1] mpls te bandwidth ct2 4000 # Set the tunnel setup priority and holding priority both to 0. [SwitchA-Tunnel1] mpls te priority 0 [SwitchA-Tunnel1] quit Configure a static route on Switch A to direct the traffic destined for subnet 30.1.1.0/24 to MPLS TE tunnel 1.
Page 135 Record Route : Disabled Record Label : Disabled FRR Flag : Disabled Bandwidth Protection : Disabled Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth Bypass Tunnel : No Auto Created : No Route Pinning : Disabled Retry Limit : 10 Retry Interval : 2 sec...
Page 136: Troubleshooting Mpls Te
Troubleshooting MPLS TE No TE LSA generated Symptom OSPF TE is configured but no TE LSAs can be generated to describe MPLS TE attributes. Analysis For TE LSAs to be generated, at least one OSPF neighbor must reach FULL state. Solution To resolve the problem: a.
Page 137: Configuring A Static Crlsp
Configuring a static CRLSP Overview A static Constraint-based Routed Label Switched Path (CRLSP) is established by manually specifying CRLSP setup information on the ingress, transit, and egress nodes of the forwarding path. The CRLSP setup information includes the incoming label, outgoing label, and required bandwidth. If the device does not have enough bandwidth resources required by a CRLSP, the CRLSP cannot be established.
Page 138: Displaying Static Crlsps
Step Command Remarks Enter system view. system-view • Configure ingress node: Use one command according static-cr-lsp ingress lsp-name to the position of a device on nexthop next-hop-addr the network. outgoing-interface interface-type interface-number out-label By default, no static CRLSP out-label-value [ bandwidth [ ct0 | exists.
Page 139: Configuration Procedure
Figure 35 Network diagram Loop0 2.2.2.2/32 Vlan-int1 Vlan-int2 3.2.1.1/24 2.1.1.2/24 Switch B Vlan-int1 Vlan-int2 2.1.1.1/24 3.2.1.2/24 Switch A Switch C Loop0 Loop0 3.3.3.3/32 1.1.1.1/32 Configuration procedure Configure IP addresses and masks for interfaces. (Details not shown.) Configure IS-IS to advertise interface addresses, including the loopback interface address: # Configure Switch A.
Page 140 [SwitchC-isis-1] network-entity 00.0005.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] isis enable 1 [SwitchC-Vlan-interface2] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] isis enable 1 [SwitchC-LoopBack0] quit # Execute the display ip routing-table command on each switch to verify that the switches have learned the routes to one another, including the routes to the loopback interfaces.
Page 141: Verifying The Configuration
[SwitchA-Tunnel0] quit Create a static CRLSP: # Configure Switch A as the ingress node of the static CRLSP, specify the next hop address as 2.1.1.2 and outgoing label as 20. [SwitchA] static-cr-lsp ingress static-cr-lsp-1 nexthop 2.1.1.2 out-label 20 # On Switch A, configure tunnel 0 to reference the static CRLSP static-cr-lsp-1. [SwitchA] interface Tunnel0 [SwitchA-Tunnel0] mpls te static-cr-lsp static-cr-lsp-1 [SwitchA-Tunnel0] quit...
Page 142 Signaling : Static Static CRLSP Name : static-cr-lsp-1 Resv Style Tunnel mode Reverse-LSP name Reverse-LSP LSR ID Reverse-LSP Tunnel ID: - Class Type Tunnel Bandwidth Reserved Bandwidth Setup Priority Holding Priority Affinity Attr/Mask : -/- Explicit Path Backup Explicit Path : - Metric Type : TE Record Route...
Page 143 Destinations : 12 Routes : 12 Destination/Mask Proto Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 1.1.1.1/32 Direct 127.0.0.1 InLoop0 2.1.1.0/24 Direct 2.1.1.1 Vlan1 2.1.1.0/32 Direct 2.1.1.1 Vlan1 2.1.1.1/32 Direct 127.0.0.1 InLoop0 2.1.1.255/32 Direct 2.1.1.1 Vlan1 2.2.2.2/32 IS_L1 2.1.1.2 Vlan1 3.2.1.0/24 Static 0.0.0.0...
Page 144: Configuring Rsvp
Configuring RSVP Overview The Resource Reservation Protocol (RSVP) is a signaling protocol that reserves resources on a network. Extended RSVP supports MPLS label distribution and allows resource reservation information to be transmitted with label bindings. This extended RSVP is called RSVP-TE. RSVP-TE is a label distribution protocol for MPLS TE.
Page 145: Crlsp Setup Procedure
CRLSP setup procedure Figure 36 Setting up a CRLSP Ingress Egress Path Path Resv Resv Sender Receiver As shown in Figure 36, a CRLSP is set up using the following steps: The ingress LSR generates a Path message that carries LABEL_REQUEST, and then forwards the message along the path calculated by CSPF hop-by-hop towards the egress LSR.
Page 146: Rsvp Authentication
by sending back a message that includes the Message_ID_ACK object. If the sender does not receive a Message_ID_ACK within the retransmission interval (Rf), it performs the following tasks: • Retransmits the message when Rf expires. • Sets the next transmission interval to (1 + delta) × Rf. The sender repeats this process until it receives the Message_ID_ACK before the retransmission time expires or it has transmitted the message three times.
Page 147: Protocols And Standards
Protocols and standards • RFC 2205, Resource ReSerVation Protocol • RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels • RFC 2961, RSVP Refresh Overhead Reduction Extensions RSVP configuration task list Tasks at a glance (Required.) Enabling RSVP (Optional.) Perform the following tasks on each node of an MPLS TE tunnel according to your network requirements: •...
Page 148: Configuring Rsvp Srefresh And Reliable Rsvp Message Delivery
Configuring RSVP Srefresh and reliable RSVP message delivery After Srefresh is enabled, RSVP maintains the path and reservation states by sending Srefresh messages rather than standard refresh messages. To configure Srefresh and reliable RSVP message delivery: Step Command Remarks Enter system view. system-view interface interface-type...
Page 149: Configuring Rsvp Authentication
Step Command Remarks number of consecutive lost is 4. or erroneous hellos. Configure the interval for By default, hello requests are sent hello interval interval sending hello requests. every 5 seconds. Return to system view. quit interface interface-type Enter interface view. interface-number Enable RSVP...
Page 150: Specifying A Dscp Value For Outgoing Rsvp Packets
To configure RSVP authentication in interface view: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, RSVP authentication Enable RSVP authentication is disabled. interface rsvp authentication key { cipher enable both RSVP configure the authentication | plain } auth-key authentication and FRR on the key.
Page 151: Configuring Rsvp Gr
Step Command Remarks Enter system view. system-view Enter RSVP view. rsvp Specify a DSCP value for dscp dscp-value By default, the DSCP value is 48. outgoing RSVP packets. Configuring RSVP GR RSVP GR depends on the RSVP hello extension function. When configuring RSVP GR, you must enable RSVP hello extension.
Page 152: Rsvp Configuration Examples
Task Command interface-number ] ] Display information about security display rsvp authentication [ from ip-address ] [ to associations established with RSVP ip-address ] [ verbose ] neighbors. Display information about CRLSPs display rsvp lsp [ destination ip-address ] [ source established through RSVP.
Page 153 Table 10 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Loop0 1.1.1.9/32 Switch D Loop0 4.4.4.9/32 Vlan-int1 10.1.1.1/24 Vlan-int3 30.1.1.2/24 Switch B Loop0 2.2.2.9/32 Switch C Loop0 3.3.3.9/32 Vlan-int1 10.1.1.2/24 Vlan-int3 30.1.1.1/24 Vlan-int2 20.1.1.1/24 Vlan-int2 20.1.1.2/24...
Page 154 [SwitchC-Vlan-interface2] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] isis enable 1 [SwitchC-LoopBack0] quit # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 00.0005.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 3 [SwitchD-Vlan-interface3] isis enable 1 [SwitchD-Vlan-interface3] quit [SwitchD] interface loopback 0 [SwitchD-LoopBack0] isis enable 1 [SwitchD-LoopBack0] quit # Execute the display ip routing-table command on each switch to verify that the switches...
Page 155 [SwitchC] mpls te [SwitchC-te] quit [SwitchC] rsvp [SwitchC-rsvp] quit [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable [SwitchC-Vlan-interface3] mpls te enable [SwitchC-Vlan-interface3] rsvp enable [SwitchC-Vlan-interface3] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls enable [SwitchC-Vlan-interface2] mpls te enable [SwitchC-Vlan-interface2] rsvp enable [SwitchC-Vlan-interface2] quit # Configure Switch D.
Page 156: Rsvp Gr Configuration Example
Tunnel source unknown, destination 4.4.4.9 Tunnel TTL 255 Tunnel protocol/transport CR_LSP Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 6 bytes/sec, 48 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes, 0 drops Output: 177 packets, 11428 bytes, 0 drops # Execute the display mpls te tunnel-interface command on Switch A.
Page 157 Configure RSVP GR on the switches to ensure continuous forwarding when a switch reboots. Figure 38 Network diagram Loop0 Loop0 Loop0 2.2.2.9/32 3.3.3.9/32 1.1.1.9/32 Vlan-int1 Vlan-int2 10.1.1.1/24 20.1.1.2/24 Vlan-int1 Vlan-int2 10.1.1.2/24 20.1.1.1/24 Switch A Switch B Switch C Configuration procedure Configure IP addresses and masks for interfaces.
Page 158 <SwitchC> system-view [SwitchC] mpls lsr-id 3.3.3.9 [SwitchC] mpls te [SwitchC-te] quit [SwitchC] rsvp [SwitchC-rsvp] quit [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls enable [SwitchC-Vlan-interface2] mpls te enable [SwitchC-Vlan-interface2] rsvp enable [SwitchC-Vlan-interface2] rsvp hello enable [SwitchC-Vlan-interface2] quit Configure an MPLS TE tunnel. (Details not shown.) Configure RSVP GR: # Configure Switch A.
Page 159: Configuring Tunnel Policies
Configuring tunnel policies Overview Tunnel policies enable a PE to forward traffic for each MPLS VPN over a preferred tunnel or over multiple tunnels. The tunnels supported by MPLS VPN include MPLS LSPs and MPLS TE tunnels. For more information about MPLS TE, see "Configuring MPLS TE."...
Page 160: Configuration Procedure
Figure 39 MPLS VPN tunnel selection diagram Tunnel 1 PE 1 PE 2 Tunnel 2 Tunnel 3 As shown in Figure 39, PE 1 and PE 2 have multiple tunnels in between and they are connected to multiple MPLS VPNs. You can control the paths for VPN traffic by using one of the following methods: •...
Page 161: Displaying Tunnel Information
Displaying tunnel information Execute display commands in any view. Task Command display mpls tunnel statistics vpn-instance Display tunnel information. vpn-instance-name ] destination { tunnel-ipv4-dest | tunnel-ipv6-dest } } Tunnel policy configuration examples Preferred tunnel configuration example Network requirements PE 1 has multiple tunnels to reach PE 2: one MPLS TE tunnel on the interface Tunnel 1, and one LDP LSP tunnel.
Page 162: Tunnel Selection Order Configuration Example
[PE1] tunnel-policy preferredte1 [PE1-tunnel-policy-preferredte1] preferred-path tunnel 1 [PE1-tunnel-policy-preferredte1] quit Create MPLS VPN instance vpna, and apply tunnel policy preferredte1 to it. [PE1] ip vpn-instance vpna [PE1-vpn-instance-vpna] route-distinguisher 100:1 [PE1-vpn-instance-vpna] vpn-target 100:1 [PE1-vpn-instance-vpna] tnl-policy preferredte1 [PE1-vpn-instance-vpna] quit Tunnel selection order configuration example Network requirements PE 1 has multiple tunnels to reach PE 2: one MPLS TE tunnel on the interface Tunnel 1, and one LDP LSP tunnel.
Page 163 Configuration procedure Configure tunnel policies on PE 1: # Create tunnel policy preferredte1, and configure tunnel 1 as the preferred tunnel. <PE1> system-view [PE1] tunnel-policy preferredte1 [PE1-tunnel-policy-preferredte1] preferred-path tunnel 1 [PE1-tunnel-policy-preferredte1] quit # Create tunnel policy preferredte2, and configure tunnel 3 as the preferred tunnel. [PE1] tunnel-policy preferredte2 [PE1-tunnel-policy-preferredte2] preferred-path tunnel 3 [PE1-tunnel-policy-preferredte2] quit...
Page 164: Configuring Mpls L3Vpn
Configuring MPLS L3VPN This chapter describes MPLS L3VPN configuration. Overview MPLS L3VPN is a L3VPN technology used to interconnect geographically dispersed VPN sites. MPLS L3VPN uses BGP to advertise VPN routes and uses MPLS to forward VPN packets over a service provider backbone.
Page 165 • The classification of a site depends on the topology relationship of the devices, rather than the geographical positions. However, the devices at a site are, in most cases, adjacent to each other geographically. • The devices at a site can belong to multiple VPNs, which means that a site can belong to multiple VPNs.
Page 166: Mpls L3Vpn Route Advertisement
• When the Type field is 2, the Administrator subfield occupies four bytes, the Assigned number subfield occupies two bytes, and the RD format is 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536. For example, 65536:1. To guarantee global uniqueness for a VPN-IPv4 address, do not set the Administrator subfield to any private AS number or private IP address.
Page 167: Mpls L3Vpn Packet Forwarding
d. Advertises those routes to the connected CE over a static route, RIP route, OSPF route, IS-IS route, EBGP route, or IBGP route. MPLS L3VPN packet forwarding In a basic MPLS L3VPN (within a single AS), a PE adds the following information into VPN packets: •...
Page 168: Mpls L3Vpn Networking Schemes
MPLS L3VPN networking schemes In MPLS L3VPNs, route target attributes are used to control the advertisement and reception of VPN routes between sites. They work independently and can be configured with multiple values to support flexible VPN access control and implement multiple types of VPN networking schemes. Basic VPN networking scheme In the simplest case, all users in a VPN form a closed user group.
Page 169 • The import target attribute of a spoke PE is different from the export target attribute of any other spoke PE. Therefore, any two spoke PEs cannot directly advertise VPN-IPv4 routes to each other or directly access each other. Figure 44 Network diagram for hub and spoke network VPN 1 Site 1 VPN 1:...
Page 170: Inter-As Vpn
Figure 45 Network diagram for extranet networking scheme VPN 1 Site 1 VPN 1: Import:100:1 Export:100:1 PE 1 VPN 1 PE 3 Site 3 PE 2 VPN 1: Import:100:1,200:1 Export:100:1,200:1 VPN 2: Import:200:1 Site 2 Export:200:1 VPN 2 As shown in Figure 45, route targets configured on PEs produce the following results: •...
Page 171 Figure 46 Network diagram for inter-AS option A VPN 1 VPN 1 CE 1 CE 3 PE 1 PE 3 ASBR 2 ASBR 1 EBGP (PE) (PE) AS 200 AS 100 PE 2 PE 4 VPN LSP 1 VPN LSP 2 CE 4 CE 2 LSP 1...
Page 172 Figure 47 Network diagram for inter-AS option B VPN 1 VPN 1 CE 1 CE 3 PE 1 PE 3 ASBR 2 ASBR 1 MPLS backbone MPLS backbone MP-EBGP (PE) (PE) AS 100 AS 200 PE 2 PE 4 VPN LSP 1 VPN LSP 3 CE 4 CE 2...
Page 173 In this solution, PEs exchange VPN-IPv4 routes over a multihop MP-EBGP session. Each PE must have a route to the peer PE and a label for the route so that the inter-AS public tunnel between the PEs can be set up. Inter-AS option C sets up a public tunnel by using the following methods: •...
Page 174: Carrier's Carrier
After route advertisement and public tunnel setup, a packet is forwarded from CE 3 to CE 1 by using the following process: PE 3 performs the following routing table lookups for the packet: a. Finds a matching route with next hop PE 1 and inner label Lx, and encapsulates the packet with label Lx.
Page 175 Follow these guidelines to assign labels: • If the PE and the CE are in a same AS, you must configure IGP and LDP between them. If they are in different ASs, you must configure MP-EBGP to assign labels to IPv4 unicast routes exchanged between them.
Page 176: Nested Vpn
NOTE: If equal cost routes exist between the Level 1 carrier and the Level 2 carrier, establish equal cost LSPs between them as a best practice. Nested VPN The nested VPN technology exchanges VPNv4 routes between PEs and CEs of the ISP MPLS L3VPN and allows a customer to manage its own internal VPNs.
Page 177: Hovpn
The provider PE advertises VPN-IPv4 routes carrying the comprehensive VPN information to the other PEs of the service provider. After another provider PE receives the VPN-IPv4 routes, it matches the VPN-IPv4 routes to the import targets of its local VPNs. Each local VPN accepts routes of its own and advertises them to provider CEs.
Page 178: Ospf Vpn Extension
HoVPN supports HoPE recursion: • An HoPE can act as a UPE to form a new HoPE with an SPE. • An HoPE can act as an SPE to form a new HoPE with multiple UPEs. HoVPN supports multilevel recursion. In HoPE recursion, the concepts of SPE and UPE are relative. A PE might be the SPE of its underlayer PEs and a UPE of its SPE at the same time.
Page 179 but the OSPF routes actually might belong to the same OSPF domain. This problem can be resolved by configuring the same domain ID for sites in an OSPF domain. Figure 55 Network diagram for BGP/OSPF interaction VPN 1 VPN 1 OSPF Area 1 OSPF Area 0 Site 2...
Page 180: Bgp As Number Substitution
As shown in Figure 56, Site 1 is connected to two PEs. When a PE advertises VPN routes learned from MP-BGP to Site 1 through OSPF, the routes might be received by the other PE. This results in a routing loop. OSPF VPN extension uses the following tags to avoid routing loops: •...
Page 181: Mpls L3Vpn Frr
The BGP AS number substitution function allows physically dispersed CEs to use the same AS number. The function is a BGP outbound policy and affects routes to be advertised. With the BGP AS number substitution function, when a PE advertises a route to a CE, if an AS number identical to that of the CE exists in the AS_PATH of the route, the PE replaces it with its own AS number.
Page 182 VPNv4 route backup for a VPNv4 route Figure 59 Network diagram PE 2 PE 1 MPLS VPN 1 VPN 1 backbone CE 1 CE 2 Primary link Backup link PE 3 As show in Figure 59, configure FRR on the ingress node PE 1, and specify the backup next hop for VPN 1 as PE 3.
Page 183: Protocols And Standards
IPv4 route backup for a VPNv4 route Figure 61 Network diagram PE 2 PE 1 MPLS VPN 1 VPN 1 backbone CE 1 CE 2 Primary link Backup link PE 3 As shown in Figure 61, configure FRR on the egress node PE 2, and specify the backup next hop for VPN 1 as CE 2.
Page 184: Configuring Basic Mpls L3Vpn
Tasks at a glance (Optional.) Enabling logging for BGP route flapping Configuring basic MPLS L3VPN Tasks at a glance Configuring VPN instances: (Required.) Creating a VPN instance (Required.) Associating a VPN instance with an interface (Optional.) Configuring route related attributes for a VPN instance (Required.) Configuring routing between a PE and a CE (Required.)
Page 185 Associating a VPN instance with an interface After creating and configuring a VPN instance, associate the VPN instance with the interface connected to the CE. To associate a VPN instance with an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.
Page 186: Configuring Routing Between A Pe And A Ce
Step Command Remarks policies, see Layer 3—IP Routing Configuration Guide. By default, only one tunnel is selected (no load balancing) in this order: LSP tunnel, GRE tunnel, and CR-LSP tunnel. Apply a tunnel policy to tnl-policy tunnel-policy-name The specified tunnel policy must the VPN instance.
Page 187 To configure OSPF between a PE and a CE: Step Command Remarks Enter system view. system-view Create an OSPF process for ospf [ process-id | router-id Perform this configuration on the a VPN instance and enter the router-id vpn-instance PE. On the CE, create a common OSPF view.
Page 188 Step Command Remarks Enable the IS-IS process on By default, no IS-IS process is isis enable [ process-id ] the interface. enabled on the interface. Configuring EBGP between a PE and a CE Configure the PE: Step Command Remarks Enter system view. system-view Enable BGP and enter BGP bgp as-number...
Page 189 Step Command Remarks Enter BGP view. bgp as-number peer { group-name | ip-address Configure the PE as a BGP By default, no BGP peer is [ mask-length ] } as-number peer. created. as-number Create the BGP IPv4 unicast By default, the BGP IPv4 unicast address-family ipv4 [ unicast ] family and enter its view.
Page 190: Configuring Routing Between Pes
Step Command Remarks receiving side. (Optional.) Enable route Route reflection between clients is reflect between-clients reflection between clients. enabled by default. By default, the RR uses its own router ID as the cluster ID. (Optional.) Configure reflector cluster-id { cluster-id | If multiple RRs exist in a cluster, cluster ID for the RR.
Page 191: Configuring Bgp Vpnv4 Route Control
Configuring BGP VPNv4 route control BGP VPNv4 route control is configured similarly with BGP route control, except that it is configured in BGP VPNv4 address family view. For detailed information about BGP route control, see Layer 3—IP Routing Configuration Guide. To configure BGP VPNv4 route control: Step Command...
Page 192: Configuring Inter-As Vpn
Step Command Remarks 14. Specify a preferred value for peer { group-name | ip-address By default, the preferred value is routes received from a peer [ mask-length ] } preferred-value or peer group. value 15. Apply a prefix list to filter peer { group-name | ip-address routes received...
Page 193: Configuring Inter-As Option B
Configuring inter-AS option B To configure inter-AS option B, configure PEs and ASBRs. • PE configuration: Configure basic MPLS L3VPN, and specify the ASBR in the same AS as an MP-IBGP peer. The route targets for the VPN instances on the PEs in different ASs must match for the same VPN.
Page 194: Configuring Inter-As Option C
Step Command Remarks By default, the PE filters received VPNv4 routes by route targets. 13. Disable route target based undo policy vpn-target The routes surviving the filtering filtering of VPNv4 routes. are added to the routing table, and the others are discarded. Configuring inter-AS option C To configure inter-AS option C, configure PEs and ASBRs.
Page 195 Step Command Remarks Enable BGP to exchange default, does peer { group-name | ip-address IPv4 unicast routes with the exchange IPv4 unicast routes with [ mask-length ] } enable ASBR in the same AS. any peer. Enable BGP to exchange peer { group-name | ip-address By default, BGP cannot exchange labeled IPv4 routes with the...
Page 196 Step Command Remarks Enable MPLS LDP on the By default, MPLS LDP is disabled mpls ldp enable interface. on the interface. Return to system view. quit 10. Enter interface view of the interface interface-type interface connected to the interface-number remote ASBR. 11.
Page 197: Configuring Nested Vpn
Step Command Remarks node-number Match IPv4 routes carrying By default, no match criterion is if-match mpls-label labels. configured. By default, no apply clause is Set labels for IPv4 routes. apply mpls-label configured. Configuring nested VPN For a network with many VPNs, nested VPN is a good solution to implement layered management of VPNs and to conceal the deployment of internal VPNs.
Page 198: Configuring Hovpn
Step Command Remarks peer { group-name | peer-address Specify the peer CE or the [ mask-length ] } as-number By default, no peer is specified. peer group of the peer CE. as-number Create the BGP-VPN VPNv4 By default, the BGP-VPN VPNv4 address family and enter its address-family vpnv4 address family is not created.
Page 199: Configuring An Ospf Sham Link
Step Command Remarks • By default, no route is advertised Advertise a default VPN to the UPE. route UPE: peer group-name Do not configure both commands. ip-address [ mask-length ] } peer default-route-advertise default-route-advertise vpn-instance vpn-instance command vpn-instance-name advertises a default route using Advertise routes to the UPE.
Page 200: Redistributing The Loopback Interface Route
Redistributing the loopback interface route Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN instance ip vpn-instance vpn-instance-name view. Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view. Redistribute direct routes into BGP (including the By default, no direct routes are import-route direct loopback...
Page 201: Configuring Bgp As Number Substitution
• POP forwarding—Pops the label and forwards the packet through the FIB table. To specify the VPN label processing mode on an egress PE: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Specify label processing mode as POPGO vpn popgo The default is POP forwarding.
Page 202 Step Command Remarks Enter system view. system-view The mpls bfd enable command applies to VPNv4 route backup for a VPNv4 route and IPv4 route Enable MPLS BFD. mpls bfd enable backup for a VPNv4 route. For more information about this command, see MPLS Command Reference.
Page 203: Enabling Snmp Notifications For Mpls L3Vpn
Step Command Remarks next hop of the primary VPNv4 route backup for an IPv4 route. route. For more information about this command, Layer 3—IP Routing Command Reference. 10. Enter BGP-VPN instance vpn-instance view. vpn-instance-name 11. Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view.
Page 204: Displaying And Maintaining Mpls L3Vpn
Step Command Remarks Enter system view. system-view • Enter BGP VPNv4 address family view: a. bgp as-number b. address-family vpnv4 Enter BGP VPNv4 address • Enter BGP-VPN VPNv4 family view BGP-VPN address family view: VPNv4 address family view. a. bgp as-number b.
Page 205: Mpls L3Vpn Configuration Examples
Task Command display bgp peer vpnv4 [ vpn-instance vpn-instance-name ] Display VPNv4 peer [ ip-address mask-length | { ip-address | group-name group-name } information. log-info | [ [ ip-address ] verbose ] [ standby slot slot-number ] ] display routing-table vpnv4 route-distinguisher route-distinguisher ] [ network-address [ { mask | mask-length }...
Page 206 Figure 62 Network diagram AS 65410 AS 65430 VPN 1 VPN 1 CE 3 CE 1 Vlan-int11 Vlan-int11 Loop0 PE 2 Vlan-int11 Vlan-int11 PE 1 Vlan-int12 Vlan-int13 Loop0 Loop0 Vlan-int13 Vlan-int12 Vlan-int12 Vlan-int13 MPLS backbone Vlan-int12 Vlan-int13 CE 2 CE 4 VPN 2 VPN 2 AS 65420...
Page 207 # Configure the P device. <P> system-view [P] interface loopback 0 [P-LoopBack0] ip address 2.2.2.9 32 [P-LoopBack0] quit [P] interface vlan-interface 13 [P-Vlan-interface13] ip address 172.1.1.2 24 [P- Vlan-interface13] quit [P] interface vlan-interface 12 [P-Vlan-interface12] ip address 172.2.1.1 24 [P-Vlan-interface12] quit [P] ospf [P-ospf-1] area 0 [P-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255...
Page 208 [P-ldp] quit [P] interface vlan-interface 13 [P-Vlan-interface13] mpls enable [P-Vlan-interface13] mpls ldp enable [P-Vlan-interface13] quit [P] interface vlan-interface 12 [P-Vlan-interface12] mpls enable [P-Vlan-interface12] mpls ldp enable [P-Vlan-interface12] quit # Configure PE 2. [PE2] mpls lsr-id 3.3.3.9 [PE2] mpls ldp [PE2-ldp] quit [PE2] interface vlan-interface 12 [PE2-Vlan-interface12] mpls enable [PE2-Vlan-interface12] mpls ldp enable...
Page 209 [PE2-Vlan-interface11] ip binding vpn-instance vpn1 [PE2-Vlan-interface11] ip address 10.3.1.2 24 [PE2-Vlan-interface11] quit [PE2] interface vlan-interface 13 [PE2-Vlan-interface13] ip binding vpn-instance vpn2 [PE2-Vlan-interface13] ip address 10.4.1.2 24 [PE2-Vlan-interface13] quit # Configure IP addresses for the CEs according to Figure 62. (Details not shown.) # Execute the display ip vpn-instance command on the PEs to display the configuration of the VPN instance, for example, on PE 1.
Page 210 [PE1-bgp-vpn1] quit [PE1-bgp] ip vpn-instance vpn2 [PE1-bgp-vpn2] peer 10.2.1.1 as-number 65420 [PE1-bgp-vpn2] address-family ipv4 unicast [PE1-bgp-ipv4-vpn1] peer 10.2.1.1 enable [PE1-bgp-ipv4-vpn2] import-route direct [PE1-bgp-ipv4-vpn2] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # Configure PE 2 in the same way that PE 1 is configured. (Details not shown.) # Execute the display bgp peer ipv4 vpn-instance command on the PEs to verify that a BGP peer relationship in Established state has been established between a PE and a CE.
Page 211: Configuring A Hub-Spoke Network
127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 The output shows that PE 1 has a route to the remote CE. Output on PE 2 is similar. # Verify that CEs of the same VPN can ping each other, whereas those of different VPNs cannot. For example, CE 1 can ping CE 3 (10.3.1.1) but cannot ping CE 4 (10.4.1.1).
Page 212 Configuration procedure Configure an IGP on the MPLS backbone to ensure IP connectivity within the backbone: # Configure Spoke-PE 1. <Spoke-PE1> system-view [Spoke-PE1] interface loopback 0 [Spoke-PE1-LoopBack0] ip address 1.1.1.9 32 [Spoke-PE1-LoopBack0] quit [Spoke-PE1] interface vlan-interface 4 [Spoke-PE1-Vlan-interface4] ip address 172.1.1.1 24 [Spoke-PE1-Vlan-interface4] quit [Spoke-PE1] ospf [Spoke-PE1-ospf-1] area 0...
Page 213 # Execute the display ospf peer command on the devices to verify that OSPF adjacencies in Full state have been established between Spoke-PE 1, Spoke-PE 2, and Hub-PE. Execute the display ip routing-table command on the devices to verify that the PEs have learned the routes to the loopback interfaces of each other.
Page 214 [Spoke-PE2] ip vpn-instance vpn1 [Spoke-PE2-vpn-instance-vpn1] route-distinguisher 100:2 [Spoke-PE2-vpn-instance-vpn1] vpn-target 111:1 import-extcommunity [Spoke-PE2-vpn-instance-vpn1] vpn-target 222:2 export-extcommunity [Spoke-PE2-vpn-instance-vpn1] quit [Spoke-PE2] interface vlan-interface 3 [Spoke-PE2-Vlan-interface3] ip binding vpn-instance vpn1 [Spoke-PE2-Vlan-interface3] ip address 10.2.1.2 24 [Spoke-PE2-Vlan-interface3] quit # Configure Hub-PE. [Hub-PE] ip vpn-instance vpn1-in [Hub-PE-vpn-instance-vpn1-in] route-distinguisher 100:3 [Hub-PE-vpn-instance-vpn1-in] vpn-target 222:2 import-extcommunity [Hub-PE-vpn-instance-vpn1-in] quit...
Page 215 Establish EBGP peer relationships between the PEs and CEs, and redistribute VPN routes into BGP: # Configure Spoke-CE 1. <Spoke-CE1> system-view [Spoke-CE1] bgp 65410 [Spoke-CE1-bgp] peer 10.1.1.2 as-number 100 [Spoke-CE1-bgp] address-family ipv4 [Spoke-CE1-bgp-ipv4] peer 10.1.1.2 enable [Spoke-CE1-bgp-ipv4] import-route direct [Spoke-CE1-bgp-ipv4] quit [Spoke-CE1-bgp] quit # Configure Spoke-CE 2.
Page 216 [Spoke-PE2-bgp-ipv4-vpn1] quit [Spoke-PE2-bgp-vpn1] quit [Spoke-PE2-bgp] quit # Configure Hub-PE. [Hub-PE] bgp 100 [Hub-PE-bgp] ip vpn-instance vpn1-in [Hub-PE-bgp-vpn1-in] peer 10.3.1.1 as-number 65430 [Hub-PE-bgp-vpn1-in] address-family ipv4 [Hub-PE-bgp-ipv4-vpn1-in] peer 10.3.1.1 enable [Hub-PE-bgp-ipv4-vpn1-in] import-route direct [Hub-PE-bgp-ipv4-vpn1-in] quit [Hub-PE-bgp-vpn1-in] quit [Hub-PE-bgp] ip vpn-instance vpn1-out [Hub-PE-bgp-vpn1-out] peer 10.4.1.1 as-number 65430 [Hub-PE-bgp-vpn1-out] address-family ipv4 [Hub-PE-bgp-ipv4-vpn1-out] peer 10.4.1.1 enable [Hub-PE-bgp-ipv4-vpn1-out] peer 10.4.1.1 allow-as-loop 2...
Page 217 [Hub-PE-bgp-vpnv4] peer 1.1.1.9 enable [Hub-PE-bgp-vpnv4] peer 3.3.3.9 enable [Hub-PE-bgp-vpnv4] quit [Hub-PE-bgp] quit # Execute the display bgp peer vpnv4 command on the PEs to verify that a BGP peer relationship in Established state has been established between the PEs. (Details not shown.) Verifying the configuration # Execute the display ip routing-table vpn-instance command on the PEs to display the routes to the CEs.
Page 218: Configuring Mpls L3Vpn Inter-As Option A
Configuring MPLS L3VPN inter-AS option A Network requirements CE 1 and CE 2 belong to the same VPN. CE 1 accesses the network through PE 1 in AS 100, and CE 2 accesses the network through PE 2 in AS 200. Configure MPLS L3VPN inter-AS option A, and use the VRF-to-VRF method to manage VPN routes.
Page 219 # Configure basic MPLS on PE 1, and enable MPLS LDP on the interface connected to ASBR-PE 1. <PE1> system-view [PE1] mpls lsr-id 1.1.1.9 [PE1] mpls ldp [PE1-ldp] quit [PE1] interface vlan-interface 11 [PE1-Vlan-interface11] mpls enable [PE1-Vlan-interface11] mpls ldp enable [PE1-Vlan-interface11] quit # Configure basic MPLS on ASBR-PE 1, and enable MPLS LDP on the interface connected to PE 1.
Page 220 [CE1-Vlan-interface12] ip address 10.1.1.1 24 [CE1-Vlan-interface12] quit # Configure PE 1. [PE1] ip vpn-instance vpn1 [PE1-vpn-instance-vpn1] route-distinguisher 100:1 [PE1-vpn-instance-vpn1] vpn-target 100:1 both [PE1-vpn-instance-vpn1] quit [PE1] interface vlan-interface 12 [PE1-Vlan-interface12] ip binding vpn-instance vpn1 [PE1-Vlan-interface12] ip address 10.1.1.2 24 [PE1-Vlan-interface12] quit # Configure CE 2.
Page 221 Establish EBGP peer relationships between PEs and CEs, and redistribute VPN routes into BGP: # Configure CE 1. [CE1] bgp 65001 [CE1-bgp] peer 10.1.1.2 as-number 100 [CE1-bgp] address-family ipv4 unicast [CE1-bgp-ipv4] peer 10.1.1.2 enable [CE1-bgp-ipv4] import-route direct [CE1-bgp-ipv4] quit [CE1-bgp] quit # Configure PE 1.
Page 222: Configuring Mpls L3Vpn Inter-As Option B
[ASBR-PE1] bgp 100 [ASBR-PE1-bgp] ip vpn-instance vpn1 [ASBR-PE1-bgp-vpn1] peer 192.1.1.2 as-number 200 [ASBR-PE1-bgp-vpn1] address-family ipv4 unicast [ASBR-PE1-bgp-ipv4-vpn1] peer 192.1.1.2 enable [ASBR-PE1-bgp-ipv4-vpn1] quit [ASBR-PE1-bgp-vpn1] quit [ASBR-PE1-bgp] peer 1.1.1.9 as-number 100 [ASBR-PE1-bgp] peer 1.1.1.9 connect-interface loopback 0 [ASBR-PE1-bgp] address-family vpnv4 [ASBR-PE1-bgp-vpnv4] peer 1.1.1.9 enable [ASBR-PE1-bgp-vpnv4] peer 1.1.1.9 next-hop-local [ASBR-PE1-bgp-vpnv4] quit [ASBR-PE1-bgp] quit...
Page 223 PE 1 and ASBR-PE 1 exchange VPNv4 routes through MP-IBGP. PE 2 and ASBR-PE 2 exchange VPNv4 routes through MP-IBGP. ASBR-PE 1 and ASBR-PE 2 exchange VPNv4 routes through MP-EBGP. ASBRs do not perform route target filtering of received VPN-IPv4 routes. Figure 65 Network diagram MPLS backbone MPLS backbone...
Page 224 [PE1-Vlan-interface11] isis enable 1 [PE1-Vlan-interface11] mpls enable [PE1-Vlan-interface11] mpls ldp enable [PE1-Vlan-interface11] quit # Configure interface Loopback 0, and enable IS-IS on it. [PE1] interface loopback 0 [PE1-LoopBack0] ip address 2.2.2.9 32 [PE1-LoopBack0] isis enable 1 [PE1-LoopBack0] quit # Create VPN instance vpn1, and configure the RD and route target attributes. [PE1] ip vpn-instance vpn1 [PE1-vpn-instance-vpn1] route-distinguisher 11:11 [PE1-vpn-instance-vpn1] vpn-target 1:1 2:2 3:3 import-extcommunity...
Page 225 [ASBR-PE1-Vlan-interface11] ip address 1.1.1.1 255.0.0.0 [ASBR-PE1-Vlan-interface11] isis enable 1 [ASBR-PE1-Vlan-interface11] mpls enable [ASBR-PE1-Vlan-interface11] mpls ldp enable [ASBR-PE1-Vlan-interface11] quit # Configure interface VLAN-interface 12, and enable MPLS on it. [ASBR-PE1] interface vlan-interface 12 [ASBR-PE1-Vlan-interface12] ip address 11.0.0.2 255.0.0.0 [ASBR-PE1-Vlan-interface12] mpls enable [ASBR-PE1-Vlan-interface12] quit # Configure interface Loopback 0, and enable IS-IS on it.
Page 226 [ASBR-PE2-Vlan-interface12] ip address 11.0.0.1 255.0.0.0 [ASBR-PE2-Vlan-interface12] mpls enable [ASBR-PE2-Vlan-interface12] quit # Configure interface Loopback 0, and enable IS-IS on it. [ASBR-PE2] interface loopback 0 [ASBR-PE2-LoopBack0] ip address 4.4.4.9 32 [ASBR-PE2-LoopBack0] isis enable 1 [ASBR-PE2-LoopBack0] quit # Enable BGP on ASBR-PE 2. [ASBR-PE2] bgp 600 [ASBR-PE2-bgp] peer 11.0.0.2 as-number 100 [ASBR-PE2-bgp] peer 11.0.0.2 connect-interface vlan-interface 12...
Page 227: Configuring Mpls L3Vpn Inter-As Option C
[PE2-vpn-instance-vpn1] vpn-target 1:1 2:2 3:3 import-extcommunity [PE2-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity [PE2-vpn-instance-vpn1] quit # Bind the interface connected with CE 2 to the created VPN instance. [PE2] interface vlan-interface12 [PE2-Vlan-interface12] ip binding vpn-instance vpn1 [PE2-Vlan-interface12] ip address 20.0.0.1 8 [PE2-Vlan-interface12] quit # Enable BGP on PE 2.
Page 228 Figure 66 Network diagram Loop0 Loop0 MPLS backbone MPLS backbone AS 100 AS 600 Vlan-int12 Vlan-int12 Vlan-int11 Vlan-int11 ASBR-PE 1 ASBR-PE 2 Loop0 Loop0 Vlan-int11 Vlan-int11 Site 2 PE 2 Site 1 PE 1 Vlan-int12 Vlan-int12 MP-EBGP Vlan-int12 Vlan-int12 Site 1 Site 2 CE 1 CE 2...
Page 229 [PE1] isis 1 [PE1-isis-1] network-entity 10.111.111.111.111.00 [PE1-isis-1] quit # Configure the LSR ID, and enable MPLS and LDP. [PE1] mpls lsr-id 2.2.2.9 [PE1] mpls ldp [PE1-ldp] quit # Configure interface VLAN-interface 11, and enable IS-IS, MPLS, and LDP on the interface. [PE1] interface vlan-interface 11 [PE1-Vlan-interface11] ip address 1.1.1.2 255.0.0.0 [PE1-Vlan-interface11] isis enable 1...
Page 230 [PE1-bgp-vpnv4] quit # Configure 30.0.0.2 as an EBGP peer, and redistribute BGP routes to the routing table of vpn1. [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 30.0.0.2 as-number 65001 [PE1-bgp-vpn1] address-family ipv4 unicast [PE1-bgp-ipv4-vpn1] peer 30.0.0.2 enable [PE1-bgp-ipv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit Configure ASBR-PE 1: # Enable IS-IS on ASBR-PE 1.
Page 231 [ASBR-PE1-bgp] peer 2.2.2.9 as-number 100 [ASBR-PE1-bgp] peer 2.2.2.9 connect-interface loopback 0 [ASBR-PE1-bgp] address-family ipv4 unicast [ASBR-PE1-bgp-ipv4] peer 2.2.2.9 enable [ASBR-PE1-bgp-ipv4] peer 2.2.2.9 route-policy policy2 export # Enable the capability to advertise labeled routes to IBGP peer 2.2.2.9 and to receive labeled routes from the peer.
Page 232 # Create routing policies. [ASBR-PE2] route-policy policy1 permit node 1 [ASBR-PE2-route-policy-policy1-1] apply mpls-label [ASBR-PE2-route-policy-policy1-1] quit [ASBR-PE2] route-policy policy2 permit node 1 [ASBR-PE2-route-policy-policy2-1] if-match mpls-label [ASBR-PE2-route-policy-policy2-1] apply mpls-label [ASBR-PE2-route-policy-policy2-1] quit # Enable BGP on ASBR-PE 2, and enable the capability to advertise labeled routes to IBGP peer 5.5.5.9 and to receive labeled routes from the peer.
Page 233 # Configure interface Loopback 0, and enable IS-IS on it. [PE2] interface loopback 0 [PE2-LoopBack0] ip address 5.5.5.9 32 [PE2-LoopBack0] isis enable 1 [PE2-LoopBack0] quit # Create VPN instance vpn1, and configure the RD and route target attributes. [PE2] ip vpn-instance vpn1 [PE2-vpn-instance-vpn1] route-distinguisher 11:11 [PE2-vpn-instance-vpn1] vpn-target 1:1 2:2 3:3 import-extcommunity [PE2-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity...
Page 234: Configuring Mpls L3Vpn Carrier's Carrier
[CE2-Vlan-interface12] ip address 20.0.0.2 24 [CE2-Vlan-interface12] quit # Configure 20.0.0.1 as an EBGP peer, and redistribute direct routes. [CE2] bgp 65002 [CE2-bgp] peer 20.0.0.1 as-number 600 [CE2-bgp] address-family ipv4 unicast [CE2-bgp-ipv4] peer 20.0.0.1 enable [CE2-bgp-ipv4] import-route direct [CE2-bgp-ipv4] quit [CE2-bgp] quit Verifying the configuration # Execute the display ip routing table command on CE 1 and CE 2 to verify that CE 1 and CE 2 have a route to each other.
Page 235 Figure 67 Network diagram Loop0 Loop0 Provider carrier Vlan-int12 PE 1 PE 2 Vlan-int12 Vlan-int11 Vlan-int11 AS 100 AS 100 Loop0 Customer carrier Customer carrier Vlan-int11 Vlan-int11 Vlan-int12 Vlan-int12 CE 1 CE 2 Vlan-int12 Vlan-int12 PE 4 Vlan-int11 PE 3 Vlan-int11 Loop0 Loop0...
Page 236 [PE1-isis-1] quit [PE1] interface loopback 0 [PE1-LoopBack0] isis enable 1 [PE1-LoopBack0] quit [PE1] interface vlan-interface 12 [PE1-Vlan-interface12] ip address 30.1.1.1 24 [PE1-Vlan-interface12] isis enable 1 [PE1-Vlan-interface12] mpls enable [PE1-Vlan-interface12] mpls ldp enable [PE1-Vlan-interface12] mpls ldp transport-address interface [PE1-Vlan-interface12] quit [PE1] bgp 100 [PE1-bgp] peer 4.4.4.9 as-number 100 [PE1-bgp] peer 4.4.4.9 connect-interface loopback 0 [PE1-bgp] address-family vpnv4...
Page 237 [PE3-Vlan-interface12] quit # Configure CE 1. <CE1> system-view [CE1] interface loopback 0 [CE1-LoopBack0] ip address 2.2.2.9 32 [CE1-LoopBack0] quit [CE1] mpls lsr-id 2.2.2.9 [CE1] mpls ldp [CE1-ldp] quit [CE1] isis 2 [CE1-isis-2] network-entity 10.0000.0000.0000.0002.00 [CE1-isis-2] quit [CE1] interface loopback 0 [CE1-LoopBack0] isis enable 2 [CE1-LoopBack0] quit [CE1] interface vlan-interface 12...
Page 238 [PE1] bgp 100 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] address-family ipv4 unicast [PE1-bgp-ipv4-vpn1] import isis 2 [PE1-bgp-ipv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # Configure CE 1. [CE1] interface vlan-interface 11 [CE1-Vlan-interface11] ip address 11.1.1.1 24 [CE1-Vlan-interface11] isis enable 2 [CE1-Vlan-interface11] mpls enable [CE1-Vlan-interface11] mpls ldp enable [CE1-Vlan-interface11] mpls ldp transport-address interface [CE1-Vlan-interface11] quit...
Page 239 [PE3-bgp-vpn1] quit [PE3-bgp] quit # Configure PE 4 and CE 4 in the same way that PE 3 and CE 3 are configured. (Details not shown.) Configure MP-IBGP peer relationship between the PEs of the customer carrier to exchange the end customers' VPN routes: # Configure PE 3.
Page 240 2.2.2.9/32 ISIS 11.1.1.1 Vlan11 5.5.5.9/32 4.4.4.9 Vlan12 6.6.6.9/32 4.4.4.9 Vlan12 10.1.1.0/24 ISIS 11.1.1.1 Vlan11 11.1.1.0/24 Direct 0 11.1.1.2 Vlan11 11.1.1.0/32 Direct 0 11.1.1.2 Vlan11 11.1.1.2/32 Direct 0 127.0.0.1 InLoop0 11.1.1.255/32 Direct 0 11.1.1.2 Vlan11 20.1.1.0/24 4.4.4.9 Vlan12 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32...
Page 241 [PE3] display ip routing-table Destinations : 18 Routes : 18 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 1.1.1.9/32 Direct 0 127.0.0.1 InLoop0 2.2.2.9/32 ISIS 10.1.1.2 Vlan12 5.5.5.9/32 ISIS 10.1.1.2 Vlan12 6.6.6.9/32 ISIS 10.1.1.2 Vlan12 10.1.1.0/24 Direct 0 10.1.1.1 Vlan12 10.1.1.0/32...
Page 242: Configuring Nested Vpn
Configuring nested VPN Network requirements The service provider provides nested VPN services for users, as shown in Figure • PE 1 and PE 2 are PE devices on the service provider backbone. Both of them support the nested VPN function. •...
Page 243 Device Interface IP address Device Interface IP address PE 1 Loop0 3.3.3.9/32 PE 2 Loop0 4.4.4.9/32 Vlan-int1 11.1.1.2/24 Vlan-int1 21.1.1.1/24 Vlan-int2 30.1.1.1/24 Vlan-int2 30.1.1.2/24 PE 3 Loop0 1.1.1.9/32 PE 4 Loop0 6.6.6.9/32 Vlan-int1 100.1.1.2/24 Vlan-int1 120.1.1.2/24 Vlan-int2 10.1.1.1/24 Vlan-int2 20.1.1.2/24 Vlan-int3 110.1.1.2/24 Vlan-int3...
Page 244 Execute the display isis peer command to verify that the IS-IS neighbor relationship has  been established between PE 1 and PE 2. (Details not shown.) Configure the customer VPN. Enable IS-IS, and enable LDP between PE 3 and CE 1, and between PE 4 and CE 2: # Configure PE 3.
Page 245 # Configure PE 1. [PE1] ip vpn-instance vpn1 [PE1-vpn-instance-vpn1] route-distinguisher 200:1 [PE1-vpn-instance-vpn1] vpn-target 1:1 [PE1-vpn-instance-vpn1] quit [PE1] interface vlan-interface 1 [PE1-Vlan-interface1] ip binding vpn-instance vpn1 [PE1-Vlan-interface1] ip address 11.1.1.2 24 [PE1-Vlan-interface1] mpls enable [PE1-Vlan-interface1] quit [PE1] bgp 100 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 11.1.1.1 as-number 200 [PE1-bgp-vpn1] address-family ipv4 [PE1-bgp-ipv4-vpn1] peer 11.1.1.1 enable...
Page 246 [CE5-Vlan-interface3] quit [CE5] bgp 65411 [CE5-bgp] peer 110.1.1.2 as-number 200 [CE5-bgp] address-family ipv4 unicast [CE5-bgp-ipv4] peer 110.1.1.2 enable [CE5-bgp-ipv4] import-route direct [CE5-bgp-ipv4] quit [CE5-bgp] quit # Configure PE 3. [PE3] ip vpn-instance SUB_VPN1 [PE3-vpn-instance-SUB_VPN1] route-distinguisher 100:1 [PE3-vpn-instance-SUB_VPN1] vpn-target 2:1 [PE3-vpn-instance-SUB_VPN1] quit [PE3] interface vlan-interface 1 [PE3-Vlan-interface1] ip binding vpn-instance SUB_VPN1 [PE3-Vlan-interface1] ip address 100.1.1.2 24...
Page 247 [PE1-bgp-vpnv4] nesting-vpn [PE1-bgp-vpnv4] quit [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] address-family vpnv4 [PE1-bgp-vpnv4-vpn1] peer 11.1.1.1 enable [PE1-bgp-vpnv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # Enable CE 1 to exchange VPNv4 routes with PE 1. [CE1] bgp 200 [CE1-bgp] address-family vpnv4 [CE1-bgp-vpnv4] peer 11.1.1.2 enable # Allow the local AS number to appear in the AS-PATH attribute of the routes received.
Page 248 Destinations : 14 Routes : 14 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 3.3.3.9/32 Direct 0 127.0.0.1 InLoop0 4.4.4.9/32 ISIS 30.1.1.2 Vlan2 30.1.1.0/24 Direct 0 30.1.1.1 Vlan2 30.1.1.0/32 Direct 0 30.1.1.1 Vlan2 30.1.1.1/32 Direct 0 127.0.0.1 InLoop0 30.1.1.255/32 Direct 0 30.1.1.1...
Page 249 Total number of routes from all PEs: 4 Route Distinguisher: 100:1 Total number of routes: 1 Network NextHop LocPrf PrefVal Path/Ogn * > 100.1.1.0/24 1.1.1.9 200 65410? Route Distinguisher: 101:1 Total number of routes: 1 Network NextHop LocPrf PrefVal Path/Ogn * >...
Page 250 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 Display the routing table on the CEs of sub-VPNs in the customer VPN, for example, on CE 3 and CE 5: # Verify that the routing table contains the route to the remote sub-VPN on CE 3. [CE3] display ip routing-table Destinations : 13 Routes : 13...
Page 251: Configuring Hovpn
Configuring HoVPN Network requirements There are two levels of networks, the backbone and the MPLS VPN networks, as shown in Figure • SPEs act as PEs to allow MPLS VPNs to access the backbone. • UPEs act as PEs of the MPLS VPNs to allow end users to access the VPNs. •...
Page 252 [UPE1-LoopBack0] ip address 1.1.1.9 32 [UPE1-LoopBack0] quit [UPE1] mpls lsr-id 1.1.1.9 [UPE1] mpls ldp [UPE1-ldp] quit [UPE1] interface vlan-interface 11 [UPE1-Vlan-interface11] ip address 172.1.1.1 24 [UPE1-Vlan-interface11] mpls enable [UPE1-Vlan-interface11] mpls ldp enable [UPE1-Vlan-interface11] quit # Configure the IGP protocol (OSPF, in this example). [UPE1] ospf [UPE1-ospf-1] area 0 [UPE1-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255...
Page 253 [UPE1-bgp-vpn1] quit # Establish an EBGP peer relationship with CE 2, and redistribute VPN routes into BGP. [UPE1-bgp] ip vpn-instance vpn2 [UPE1-bgp-vpn2] peer 10.4.1.1 as-number 65420 [UPE1-bgp-vpn2] address-family ipv4 unicast [UPE1-bgp-ipv4-vpn2] peer 10.4.1.1 enable [UPE1-bgp-ipv4-vpn2] import-route direct [UPE1-bgp-ipv4-vpn2] quit [UPE1-bgp-vpn2] quit [UPE1-bgp] quit Configure CE 1.
Page 254 # Configure the IGP protocol (OSPF, in this example). [UPE2] ospf [UPE2-ospf-1] area 0 [UPE2-ospf-1-area-0.0.0.0] network 172.2.1.0 0.0.0.255 [UPE2-ospf-1-area-0.0.0.0] network 4.4.4.9 0.0.0.0 [UPE2-ospf-1-area-0.0.0.0] quit [UPE2-ospf-1] quit # Configure VPN instances vpn1 and vpn2, allowing CE 3 and CE 4 to access UPE 2. [UPE2] ip vpn-instance vpn1 [UPE2-vpn-instance-vpn1] route-distinguisher 300:1 [UPE2-vpn-instance-vpn1] vpn-target 100:1 both...
Page 255 Configure CE 3. <CE3> system-view [CE3] interface vlan-interface 12 [CE3-Vlan-interface12] ip address 10.1.1.1 255.255.255.0 [CE3-Vlan-interface12] quit [CE3] bgp 65430 [CE3-bgp] peer 10.1.1.2 as-number 100 [CE3-bgp] address-family ipv4 unicast [CE3-bgp-ipv4] peer 10.1.1.2 enable [CE3-bgp-ipv4] import-route direct [CE3-bgp-ipv4] quit [CE3-bgp] quit Configure CE 4. <CE4>...
Page 256 [SPE1-ospf-1-area-0.0.0.0] network 180.1.1.0 0.0.0.255 [SPE1-ospf-1-area-0.0.0.0] quit [SPE1-ospf-1] quit # Configure VPN instances vpn1 and vpn2. [SPE1] ip vpn-instance vpn1 [SPE1-vpn-instance-vpn1] route-distinguisher 500:1 [SPE1-vpn-instance-vpn1] vpn-target 100:1 both [SPE1-vpn-instance-vpn1] quit [SPE1] ip vpn-instance vpn2 [SPE1-vpn-instance-vpn2] route-distinguisher 700:1 [SPE1-vpn-instance-vpn2] vpn-target 100:2 both [SPE1-vpn-instance-vpn2] quit # Establish MP-IBGP peer relationships with SPE 2 and UPE 1, and specify UPE 1 as a UPE.
Page 257 [SPE2-ldp] quit [SPE2] interface vlan-interface 12 [SPE2-Vlan-interface12] ip address 180.1.1.2 24 [SPE2-Vlan-interface12] mpls enable [SPE2-Vlan-interface12] mpls ldp enable [SPE2-Vlan-interface12] quit [SPE2] interface vlan-interface 11 [SPE2-Vlan-interface11] ip address 172.2.1.2 24 [SPE2-Vlan-interface11] mpls enable [SPE2-Vlan-interface11] mpls ldp enable [SPE2-Vlan-interface11] quit # Configure the IGP protocol (OSPF, in this example). [SPE2] ospf [SPE2-ospf-1] area 0 [SPE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0...
Page 258: Configuring An Ospf Sham Link
# Advertise to UPE 2 the routes permitted by a routing policy (the routes of CE 1). [SPE2] ip prefix-list hope index 10 permit 10.2.1.1 24 [SPE2] route-policy hope permit node 0 [SPE2-route-policy-hope-0] if-match ip address prefix-list hope [SPE2-route-policy-hope-0] quit [SPE2] bgp 100 [SPE2-bgp] address-family vpnv4 [SPE2-bgp-vpnv4] peer 4.4.4.9 upe route-policy hope export...
Page 259 Configuration procedure Configure OSPF on the customer networks: Configure conventional OSPF on CE 1, Switch A, and CE 2 to advertise addresses of the interfaces as shown in Figure 70. Execute the display ip routing-table command to verify that CE 1 and CE 2 have learned the route to each other. (Details not shown.) Configure MPLS L3VPN on the backbone: # Configure basic MPLS and MPLS LDP on PE 1 to establish LDP LSPs.
Page 260 [PE2] bgp 100 [PE2-bgp] peer 1.1.1.9 as-number 100 [PE2-bgp] peer 1.1.1.9 connect-interface loopback 0 [PE2-bgp] address-family vpnv4 [PE2-bgp-vpnv4] peer 1.1.1.9 enable [PE2-bgp-vpnv4] quit [PE2-bgp] quit # Configure OSPF on PE 2. [PE2]ospf 1 [PE2-ospf-1]area 0 [PE2-ospf-1-area-0.0.0.0]network 2.2.2.9 0.0.0.0 [PE2-ospf-1-area-0.0.0.0]network 10.1.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0]quit [PE2-ospf-1]quit Configure PEs to allow CE access:...
Page 261 [PE2-ospf-100] domain-id 10 [PE2-ospf-100] area 1 [PE2-ospf-100-area-0.0.0.1] network 120.1.1.0 0.0.0.255 [PE2-ospf-100-area-0.0.0.1] quit [PE2-ospf-100] quit [PE2] bgp 100 [PE2-bgp] ip vpn-instance vpn1 [PE2-bgp-vpn1] address-family ipv4 unicast [PE2-bgp-ipv4-vpn1] import-route ospf 100 [PE2-bgp-ipv4-vpn1] import-route direct [PE2-bgp-ipv4-vpn1] quit [PE2-bgp-vpn1] quit [PE2-bgp] quit # Execute the display ip routing-table vpn-instance command on the PEs to verify that the path to the peer CE is along the OSPF route across the customer networks, instead of the BGP route across the backbone.
Page 262: Configuring Bgp As Number Substitution
OSPF Process 100 with Router ID 100.1.1.2 Sham link Area Neighbor ID Source IP Destination IP State Cost 0.0.0.1 120.1.1.2 3.3.3.3 5.5.5.5 P-2-P 10 # Verify that the peer state is Full on PE 1. [PE1] display ospf sham-link area 1 OSPF Process 100 with Router ID 100.1.1.2 Sham-Link: 3.3.3.3 -->...
Page 263 Device Interface IP address Device Interface IP address Vlan-int12 20.1.1.1/24 Vlan-int11 30.1.1.2/24 CE 2 Vlan-int12 10.2.1.1/24 Vlan-int12 10.2.1.2/24 Vlan-int13 200.1.1.1/24 Configuration procedure Configuring basic MPLS L3VPN: Configure OSPF on the MPLS backbone to allow the PEs and P device to learn the routes ...
Page 264 Destinations : 15 Routes : 15 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.1.1.0/24 1.1.1.9 Vlan11 10.2.1.0/24 Direct 0 10.2.1.2 Vlan12 10.2.1.0/32 Direct 0 10.2.1.2 Vlan12 10.2.1.2/32 Direct 0 127.0.0.1 InLoop0 10.2.1.255/32 Direct 0 10.2.1.2 Vlan12 100.1.1.0/24 1.1.1.9 Vlan11 127.0.0.0/8...
Page 265 [PE2] bgp 100 [PE2-bgp] ip vpn-instance vpn1 [PE2-bgp-vpn1] peer 10.2.1.1 substitute-as [PE2-bgp-vpn1] address-family ipv4 unicast [PE2-bgp-ipv4-vpn1] peer 10.2.1.1 enable [PE2-bgp-ipv4-vpn1] quit [PE2-bgp-vpn1] quit [PE2-bgp] quit Verifying the configuration # The output shows that among the routes advertised by PE 2 to CE 2, the AS_PATH of 100.1.1.0/24 has changed from 100 600 to 100 100.
Page 266: Configuring Mpls L3Vpn Frr Through Vpnv4 Route Backup For A Vpnv4 Route
200.1.1.0/24 Direct 0 200.1.1.1 Vlan13 200.1.1.0/32 Direct 0 200.1.1.1 Vlan13 200.1.1.1/32 Direct 0 127.0.0.1 InLoop0 200.1.1.255/32 Direct 0 200.1.1.1 Vlan13 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 # Verify that the VLAN interfaces of CE 1 and CE 2 can ping each other. (Details not shown.) Configuring MPLS L3VPN FRR through VPNv4 route backup for a VPNv4 route Network requirements...
Page 267 Device Interface IP address Device Interface IP address Vlan-int12 172.2.1.3/24 Vlan-int14 10.3.1.1/24 Vlan-int14 10.3.1.2/24 Configuration procedure Configure IP addresses and masks for interfaces as shown in Table 22, and configure BGP and MPLS L3VPN. (Details not shown.) For more information about configuring basic MPLS L3VPN, see "Configuring basic MPLS L3VPN."...
Page 268: Configuring Mpls L3Vpn Frr Through Vpnv4 Route Backup For An Ipv4 Route
Cost: 0 Preference: 255 IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x102 OrigAs: 300 NibID: 0x15000002 LastAs: 300 AttrID: 0x2 Neighbor: 2.2.2.2 Flags: 0x110060 OrigNextHop: 2.2.2.2 Label: 1146 RealNextHop: 172.1.1.2 BkLabel: 1275 BkNextHop: 172.2.1.3 Tunnel ID: Invalid Interface: Vlan-int11 BkTunnel ID: Invalid...
Page 269 Device Interface IP address Device Interface IP address PE 1 Loop0 1.1.1.1/32 Vlan-int13 10.1.1.2/24 Vlan-int10 10.2.1.2/24 Vlan-int15 172.3.1.2/24 Vlan-int11 172.1.1.1/24 PE 3 Loop0 3.3.3.3/32 Vlan-int12 172.2.1.1/24 Vlan-int12 172.2.1.3/24 CE 2 Loop0 4.4.4.4/32 Vlan-int14 10.3.1.2/24 Vlan-int13 10.1.1.1/24 Vlan-int15 172.3.1.3/24 Vlan-int14 10.3.1.1/24 Configuration procedure Configure IP addresses and masks for interfaces as shown in Table...
Page 270: Configuring Mpls L3Vpn Frr Through Ipv4 Route Backup For A Vpnv4 Route
SubProtID: 0x2 Age: 01h54m24s Cost: 0 Preference: 10 IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: vpn1 TableID: 0x102 OrigAs: 300 NibID: 0x15000002 LastAs: 300 AttrID: 0x0 Neighbor: 10.1.1.1 Flags: 0x10060 OrigNextHop: 10.1.1.1 Label: NULL RealNextHop: 10.1.1.1 BkLabel: 1275 BkNextHop: 172.3.1.3 Tunnel ID: Invalid...
Page 271 Device Interface IP address Device Interface IP address Vlan-int10 10.2.1.1/24 Vlan-int11 172.1.1.2/24 PE 1 Loop0 1.1.1.1/32 Vlan-int13 10.1.1.2/24 Vlan-int10 10.2.1.2/24 Vlan-int15 172.3.1.2/24 Vlan-int11 172.1.1.1/24 PE 3 Loop0 3.3.3.3/32 Vlan-int12 172.2.1.1/24 Vlan-int12 172.2.1.3/24 CE 2 Loop0 4.4.4.4/32 Vlan-int14 10.3.1.2/24 Vlan-int13 10.1.1.1/24 Vlan-int15 172.3.1.3/24 Vlan-int14...
Page 272 Verifying the configuration # Display detailed information about the route to 4.4.4.4/32 on PE 2. The output shows the backup next hop for the route. [PE2] display ip routing-table vpn-instance vpn1 4.4.4.4 32 verbose Summary Count : 1 Destination: 4.4.4.4/32 Protocol: BGP Process ID: 0 SubProtID: 0x1...
Page 273: Configuring Ipv6 Mpls L3Vpn
Configuring IPv6 MPLS L3VPN Overview IPv6 MPLS L3VPN uses BGP to advertise IPv6 VPN routes and uses MPLS to forward IPv6 VPN packets on the service provider backbone. Figure 75 shows a typical IPv6 MPLS L3VPN model. The service provider backbone in the IPv6 MPLS L3VPN model is an IPv4 network.
Page 274: Ipv6 Mpls L3Vpn Routing Information Advertisement
Based on the inbound interface and destination address of the packet, PE 1 finds a matching entry from the routing table of the VPN instance, labels the packet with both a private network label (inner label) and a public network label (outer label), and forwards the packet out. The MPLS backbone transmits the packet to PE 2 by outer label.
Page 275: Ipv6 Mpls L3Vpn Configuration Task List
IPv6 MPLS L3VPN configuration task list By configuring basic IPv6 MPLS L3VPN, you can construct a simple IPv6 VPN network over an MPLS backbone. To deploy special IPv6 MPLS L3VPN networks, such as inter-AS VPN, you must also perform specific configurations in addition to the basic IPv6 MPLS L3VPN configuration. For details, see the related sections.
Page 276 Step Command Remarks Enter system view. system-view Create a VPN instance and vpn-instance By default, no VPN instance is enter VPN instance view. vpn-instance-name created. Configure an RD for the VPN route-distinguisher By default, no RD is specified. instance. route-distinguisher By default, no description is configured for a VPN instance.
Page 277: Configuring Routing Between A Pe And A Ce
Step Command Remarks limited. Setting the maximum number of active routes for a VPN instance can prevent the PE from storing too many routes. By default, all routes matching the import target attribute accepted. Make sure the routing policy Apply import routing already exists.
Page 278 Step Command Remarks By default, no IPv6 static route is configured for a VPN instance. ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address Perform this prefix-length { interface-type interface-number configuration on the PE. Configure an IPv6 static next-hop-address nexthop-address On the CE, configure a route [ public ] | vpn-instance d-vpn-instance-name common...
Page 279 Step Command Remarks When you redistribute OSPFv3 routes into BGP, BGP adds the primary domain redistributed BGP VPNv6 routes as a BGP extended community attribute. You can configure the same domain ID for different OSPFv3 processes. All OSPF processes of the same VPN must be configured with the same OSPF domain ID to ensure correct route advertisement.
Page 280 Step Command Remarks version. Perform this configuration on the 10. Return to system view. quit interface interface-type 11. Enter interface view. interface-number By default, OSPFv3 is disabled on an interface. 12. Enable OSPFv3 ospfv3 process-id area area-id interface. [ instance instance-id ] Perform this configuration on the Configuring IPv6 IS-IS between a PE and a CE An IPv6 IS-IS process belongs to the public network or a single VPN instance.
Page 281 Step Command Remarks Configuration commands BGP-VPN IPv6 unicast address family view are the same as those in BGP IPv6 unicast address family view. For details, see Layer 3—IP Routing Configuration Guide. Enable IPv6 unicast route default, does peer { group-name | ipv6-address exchange with the specified exchange IPv6 unicast routes with [ prefix-length ] } enable...
Page 282 Step Command Remarks details, see Layer 3—IP Routing Configuration Guide. peer { group-name | ipv6-address Configure the CE as the VPN By default, no BGP peer is [ prefix-length ] } as-number IBGP peer. created. as-number Create the BGP-VPN IPv6 By default, the BGP-VPN IPv6 unicast family and enter its address-family ipv6 [ unicast ]...
Page 283: Configuring Routing Between Pes
Configuring routing between PEs Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number peer { group-name | ip-address Configure the remote PE as By default, no BGP peer is [ mask-length ] } as-number the peer. configured. as-number peer { group-name | ip-address default,...
Page 284: Configuring Inter-As Ipv6 Vpn
Step Command Remarks public AS numbers. numbers. 10. Apply a routing policy to peer { group-name | ip-address routes advertised [ mask-length ] } route-policy By default, no routing policy is received from the peer or route-policy-name export applied for a peer. peer group.
Page 285: Configuring Inter-As Ipv6 Vpn Option A
Configuring inter-AS IPv6 VPN option A Inter-AS IPv6 VPN option A applies to scenarios where the number of VPNs and that of VPN routes on the PEs are relatively small. To configure inter-AS IPv6 option A: • Configure basic IPv6 MPLS L3VPN on each AS. •...
Page 286: Configuring An Ospfv3 Sham Link
Step Command Remarks peer. Configuring the ASBR-PEs In the inter-AS IPv6 VPN option C solution, an inter-AS LSP is needed, and the routes advertised between the PEs and ASBRs must carry MPLS label information. The configuration is the same as that in the Inter-AS IPv4 VPN option C solution.
Page 287: Creating A Sham Link
Step Command Remarks Redistribute direct routes into BGP (including the By default, no direct routes are import-route direct loopback interface redistributed into BGP. address). Creating a sham link Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view.
Page 288 Execute the following commands in user view to soft reset or reset BGP connections: Task Command Soft reset BGP sessions for refresh bgp { ip-address [ mask-length ] | all | external | group VPNv6 address family. group-name | internal } { export | import } vpnv6 Reset BGP sessions for VPNv6 reset bgp { as-number | ip-address [ mask-length ] | all | external | internal | group group-name } vpnv6...
Page 289: Ipv6 Mpls L3Vpn Configuration Examples
IPv6 MPLS L3VPN configuration examples Configuring IPv6 MPLS L3VPNs Network requirements CE 1 and CE 3 belong to VPN 1. CE 2 and CE 4 belong to VPN 2. VPN 1 uses route target attributes 111:1. VPN 2 uses route target attributes 222:2. Users of different VPNs cannot access each other.
Page 290 # Configure PE 1. <PE1> system-view [PE1] interface loopback 0 [PE1-LoopBack0] ip address 1.1.1.9 32 [PE1-LoopBack0] quit [PE1] interface vlan-interface 13 [PE1-Vlan-interface13] ip address 172.1.1.1 24 [PE1- Vlan-interface13] quit [PE1] ospf [PE1-ospf-1] area 0 [PE1-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure the P switch.
Page 291 to verify that the PEs have learned the routes to the loopback interfaces of each other. (Details not shown.) Configure basic MPLS and enable MPLS LDP on the MPLS backbone to establish LDP LSPs: # Configure PE 1. [PE1] mpls lsr-id 1.1.1.9 [PE1] mpls ldp [PE1-ldp] quit [PE1] interface vlan-interface 13...
Page 292 [PE1] interface vlan-interface 12 [PE1-Vlan-interface12] ip binding vpn-instance vpn2 [PE1-Vlan-interface12] ipv6 address 2001:2::2 96 [PE1-Vlan-interface12] quit # Configure PE 2. [PE2] ip vpn-instance vpn1 [PE2-vpn-instance-vpn1] route-distinguisher 200:1 [PE2-vpn-instance-vpn1] vpn-target 111:1 [PE2-vpn-instance-vpn1] quit [PE2] ip vpn-instance vpn2 [PE2-vpn-instance-vpn2] route-distinguisher 200:2 [PE2-vpn-instance-vpn2] vpn-target 222:2 [PE2-vpn-instance-vpn2] quit [PE2] interface vlan-interface 11 [PE2-Vlan-interface11] ip binding vpn-instance vpn1...
Page 293 [CE1-bgp-ipv6] peer 2001:1::2 enable [CE1-bgp-ipv6] import-route direct [CE1-bgp-ipv6] quit [CE1-bgp] quit # Configure the other three CEs (CE 2 through CE 4) in the same way that CE 1 is configured. (Details not shown.) # Configure PE 1. [PE1] bgp 100 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 2001:1::1 as-number 65410 [PE1-bgp-vpn1] address-family ipv6 unicast...
Page 294 [PE1] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2001:1::/96 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan11 Cost Destination: 2001:1::2/128 Protocol : Direct...
Page 295: Configuring Ipv6 Mpls L3Vpn Inter-As Option A
NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost The output shows that PE 1 has routes to the remote CEs. Output on PE 2 is similar. # Verify that CEs of the same VPN can ping each other, and CEs of different VPNs cannot ping each other.
Page 296 Device Interface IP address Device Interface IP address Vlan-int11 172.1.1.1/24 Vlan-int11 162.1.1.1/24 Vlan-int12 2002:1::1/96 Vlan-int12 2002:1::2/96 Configuration procedure Configure an IGP on each MPLS backbone to ensure IP connectivity within the backbone: This example uses OSPF. (Details not shown.) # Execute the display ospf peer command to verify that each ASBR-PE has established an OSPF adjacency in Full state with the PE in the same AS, and that the PEs and ASBR-PEs in the same AS have learned the routes to the loopback interfaces of each other.
Page 297 [PE2] interface vlan-interface 11 [PE2-Vlan-interface11] mpls enable [PE2-Vlan-interface11] mpls ldp enable [PE2-Vlan-interface11] quit # Each PE and the ASBR-PE in the same AS can establish an LDP neighbor relationship. Execute the display mpls ldp peer command on the switches to verify that the session status is Operational.
Page 298 # On ASBR-PE 2, create a VPN instance and bind the VPN instance to the interface connected to ASBR-PE 1. ASBR-PE 2 considers ASBR-PE 1 to be its attached CE. [ASBR-PE2] ip vpn-instance vpn1 [ASBR-PE2-vpn-vpn-vpn1] route-distinguisher 200:1 [ASBR-PE2-vpn-vpn-vpn1] vpn-target 200:1 both [ASBR-PE2-vpn-vpn-vpn1] quit [ASBR-PE2] interface vlan-interface 12 [ASBR-PE2-Vlan-interface12] ip binding vpn-instance vpn1...
Page 299 Establish an IBGP peer relationship between each PE and the ASBR-PE in the same AS, and an EBGP peer relationship between the ASBR-PEs: # Configure PE 1. [PE1] bgp 100 [PE1-bgp] peer 2.2.2.9 as-number 100 [PE1-bgp] peer 2.2.2.9 connect-interface loopback 0 [PE1-bgp] address-family vpnv6 [PE1-bgp-vpnv6] peer 2.2.2.9 enable [PE1-bgp-vpnv6] quit...
Page 300: Configuring Ipv6 Mpls L3Vpn Inter-As Option C
Configuring IPv6 MPLS L3VPN inter-AS option C Network requirements Site 1 and Site 2 belong to the same VPN. Site 1 accesses the network through PE 1 in AS 100. Site 2 accesses the network through PE 2 in AS 600. PEs in the same AS run IS-IS. PE 1 and ASBR-PE 1 exchange labeled IPv4 routes by IBGP.
Page 301: Enable Bgp
# Configure 2001::1 as an EBGP peer, and redistribute direct routes. [CE1] bgp 65001 [CE1-bgp] peer 2001::1 as-number 100 [CE1-bgp] address-family ipv6 unicast [CE1-bgp-ipv6] peer 2001::1 enable [CE1-bgp-ipv6] import-route direct [CE1-bgp-ipv6] quit [CE1-bgp] quit Configure PE 1: # Run IS-IS on PE 1. <PE1>...
Page 302 [PE1-bgp] address-family ipv4 unicast [PE1-bgp-ipv4] peer 3.3.3.9 enable [PE1-bgp-ipv4] peer 3.3.3.9 label-route-capability [PE1-bgp-ipv4] quit # Configure the maximum hop count from PE 1 to EBGP peer 5.5.5.9 as 10. [PE1-bgp] peer 5.5.5.9 as-number 600 [PE1-bgp] peer 5.5.5.9 connect-interface loopback 0 [PE1-bgp] peer 5.5.5.9 ebgp-max-hop 10 # Configure peer 5.5.5.9 as a VPNv6 peer.
Page 303 # Create routing policies. [ASBR-PE1] route-policy policy1 permit node 1 [ASBR-PE1-route-policy-policy1-1] apply mpls-label [ASBR-PE1-route-policy-policy1-1] quit [ASBR-PE1] route-policy policy2 permit node 1 [ASBR-PE1-route-policy-policy2-1] if-match mpls-label [ASBR-PE1-route-policy-policy2-1] apply mpls-label [ASBR-PE1-route-policy-policy2-1] quit # Start BGP on ASBR-PE 1 and apply routing policy policy2 to routes advertised to IBGP peer 2.2.2.9 [ASBR-PE1] bgp 100 [ASBR-PE1-bgp] peer 2.2.2.9 as-number 100...
Page 304 [ASBR-PE2-Vlan-interface11] quit # Configure interface Loopback 0, and start IS-IS on it. [ASBR-PE2] interface loopback 0 [ASBR-PE2-LoopBack0] ip address 4.4.4.9 32 [ASBR-PE2-LoopBack0] isis enable 1 [ASBR-PE2-LoopBack0] quit # Configure interface VLAN-interface 12, and enable MPLS on it. [ASBR-PE2] interface vlan-interface 12 [ASBR-PE2-Vlan-interface12] ip address 11.0.0.1 255.0.0.0 [ASBR-PE2-Vlan-interface12] mpls enable [ASBR-PE2-Vlan-interface12] quit...
Page 305 # Configure an LSR ID, and enable MPLS and LDP. [PE2] mpls lsr-id 5.5.5.9 [PE2] mpls ldp [PE2-ldp] quit # Configure interface VLAN-interface 11, and enable IS-IS, MPLS, and LDP on the interface. [PE2] interface vlan-interface 11 [PE2-Vlan-interface11] ip address 9.1.1.2 255.0.0.0 [PE2-Vlan-interface11] isis enable 1 [PE2-Vlan-interface11] mpls enable [PE2-Vlan-interface11] mpls ldp enable...
Page 306: Configuring Ipv6 Mpls L3Vpn Carrier's Carrier
[PE2-bgp-vpn1] peer 2002::2 as-number 65002 [PE2-bgp-vpn1] address-family ipv6 unicast [PE2-bgp-ipv6-vpn1] peer 2002::2 enable [PE2-bgp-ipv6-vpn1] quit [PE2-bgp-vpn1] quit [PE2-bgp] quit Configure CE 2: # Configure an IPv6 address for VLAN-interface 12. <CE2> system-view [CE2] interface vlan-interface 12 [CE2-Vlan-interface12] ip address 2002::2 64 [CE2-Vlan-interface12] quit # Configure 2002::1 as an EBGP peer, and redistribute direct routes.
Page 307 Figure 80 Network diagram Loop0 Loop0 Provider carrier Vlan-int12 PE 1 PE 2 Vlan-int12 Vlan-int11 Vlan-int11 AS 100 AS 100 Loop0 Customer carrier Customer carrier Vlan-int11 Vlan-int11 Vlan-int12 Vlan-int12 CE 1 CE 2 Vlan-int12 Vlan-int12 PE 4 Vlan-int11 PE 3 Vlan-int11 Loop0 Loop0...
Page 308 [PE1-bgp] quit # Configure PE 2 in the same way that PE 1 is configured. (Details not shown.) # On PE 1 or PE 2, execute the following commands: Execute the display mpls ldp peer command to verify that an LDP session in Operational ...
Page 309 [CE1-Vlan-interface12] isis enable 2 [CE1-Vlan-interface12] mpls enable [CE1-Vlan-interface12] mpls ldp enable [CE1-Vlan-interface12] mpls ldp transport-address interface [CE1-Vlan-interface12] quit PE 3 and CE 1 can establish an LDP session and IS-IS neighbor relationship between them. # Configure PE 4 and CE 2 in the same way that PE 3 and CE 1 are configured. (Details not shown.) Connect the customer carrier to the provider carrier: # Configure PE 1.
Page 310 Connect end customers to the customer carrier: # Configure CE 3. <CE3> system-view [CE3] interface vlan-interface11 [CE3-Vlan-interface11] ipv6 address 2001:1::1 96 [CE3-Vlan-interface11] quit [CE3] bgp 65410 [CE3-bgp] peer 2001:1::2 as-number 100 [CE3-bgp] address-family ipv6 [CE3-bgp-ipv6] peer 2001:1::2 enable [CE3-bgp-ipv6] import-route direct [CE3-bgp-ipv6] quit [CE3-bgp] quit # Configure PE 3.
Page 311 # Verify that the public network routing table contains only routes of the provider carrier network. [PE1] display ip routing-table Destinations : 14 Routes : 14 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 3.3.3.9/32 Direct 0 127.0.0.1 InLoop0 4.4.4.9/32 ISIS...
Page 312 Destinations : 21 Routes : 21 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 1.1.1.9/32 ISIS 10.1.1.1 Vlan12 2.2.2.9/32 Direct 0 127.0.0.1 InLoop0 5.5.5.9/32 ISIS 11.1.1.2 Vlan11 6.6.6.9/32 ISIS 11.1.1.2 Vlan11 10.1.1.0/24 Direct 0 10.1.1.2 Vlan12 10.1.1.0/32 Direct 0 10.1.1.2 Vlan12 10.1.1.2/32...
Page 313: Configuring An Ospfv3 Sham Link
255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 # Verify that the VPN routing table has the remote VPN route. [PE3] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2001:1::/96...
Page 314 Figure 81 Network diagram Loop0 Loop0 Vlan-int12 PE 1 PE 2 Vlan-int12 Vlan-int11 Vlan-int11 Sham-link Loop1 Loop1 OSPFv3 Area 1 Vlan-int11 Vlan-int11 Vlan-int13 Vlan-int12 Vlan-int12 Vlan-int13 CE 1 Switch A CE 2 Backdoor link Table 28 Interface and IP address assignment Device Interface IP address...
Page 315 [PE1-Vlan-interface12] mpls ldp enable [PE1-Vlan-interface12] quit # Configure PE 1 to take PE 2 as an MP-IBGP peer. [PE1] bgp 100 [PE1-bgp] peer 2.2.2.9 as-number 100 [PE1-bgp] peer 2.2.2.9 connect-interface loopback 0 [PE1-bgp] address-family vpnv6 [PE1-bgp-vpnv6] peer 2.2.2.9 enable [PE1-bgp-vpnv6] quit [PE1-bgp] quit # Configure OSPF on PE 1.
Page 316 [PE1-vpn-instance-vpn1] route-distinguisher 100:1 [PE1-vpn-instance-vpn1] vpn-target 1:1 [PE1-vpn-instance-vpn1] quit [PE1] interface vlan-interface 11 [PE1-Vlan-interface11] ip binding vpn-instance vpn1 [PE1-Vlan-interface11] ipv6 address 100::2 64 [PE1-Vlan-interface11] ospfv3 100 area 1 [PE1-Vlan-interface11] quit [PE1] ospfv3 100 [PE1-ospfv3-100] router-id 100.1.1.1 [PE1-ospfv3-100] domain-id 10 [PE1-ospfv3-100] quit [PE1] bgp 100 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] address-family ipv6 unicast...
Page 317 [PE1-LoopBack1] ip binding vpn-instance vpn1 [PE1-LoopBack1] ipv6 address 3::3 128 [PE1-LoopBack1] quit [PE1] ospfv3 100 [PE1-ospfv3-100] area 1 [PE1-ospfv3-100-area-0.0.0.1] sham-link 3::3 5::5 [PE1-ospfv3-100-area-0.0.0.1] quit [PE1-ospfv3-100] quit # Configure PE 2. [PE2] interface loopback 1 [PE2-LoopBack1] ip binding vpn-instance vpn1 [PE2-LoopBack1] ipv6 address 5::5 128 [PE2-LoopBack1] quit [PE2] ospfv3 100 [PE2-ospfv3-100] area 1...
Page 318 Request list: 0 Retransmit list: 0...
Page 319: Configuring Mpls L2Vpn
Configuring MPLS L2VPN MPLS L2VPN provides point-to-point and point-to-multipoint connections. This chapter describes only the MPLS L2VPN technologies that provide point-to-point connections. For information about the MPLS L2VPN technologies that provide point-to-multipoint connections, see "Configuring VPLS." Overview MPLS L2VPN is an implementation of Pseudo Wire Emulation Edge-to-Edge (PWE3). It offers Layer 2 VPN services over an MPLS or IP backbone.
Page 320: Mpls L2Vpn Network Models
Assume that a VPN has 10 sites, and a PE assigns the first label block LB1/0/10 to the VPN. When another 15 sites are added, the PE keeps the first label block and assigns the second label block LB2/10/15 to extend the network. LB1 and LB2 are the initial label values that are randomly selected by the PE.
Page 321: Pw Redundancy
To establish BGP PWs, BGP advertises label block information in an extended BGP update to PEs in the same VPN. Each PE uses the received label block information to calculate outgoing labels and uses its own label block to calculate incoming labels. After two PEs complete label calculation, a BGP PW is established between them.
Page 322: Multi-Segment Pw
Multi-segment PW A multi-segment PW includes multiple concatenated static or LDP PWs. Creating two PWs for a cross-connect on a PE can concatenate the two PWs. Upon receiving a packet from one PW, the PE removes the tunnel ID and PW label of the packet, adds the PW label of the other PW, and forwards the packet over the public tunnel.
Page 323: Vccv
Figure 85 Intra-domain multi-segment PW MPLS or IP backbone PW 1 CE 1 PE 1 PE 2 Tunnel PW 2 PE 3 PE 4 CE 2 Inter-domain multi-segment PW An inter-domain multi-segment PW has concatenated PWs in different ASs, and is a method for inter-AS option B networking.
Page 324: Mpls L2Vpn Configuration Task List
MPLS L2VPN configuration task list To establish an MPLS L2VPN, you must complete the following tasks: • Configure an IGP to achieve IP connectivity within the backbone. • Configure basic MPLS, LDP, or MPLS TE to set up public tunnels across the backbone. •...
Page 325: Configuring An Ac
Configuring an AC An AC is an Ethernet service instance on a Layer 2 Ethernet interface or Layer 2 aggregate interface that connects to a CE. To configure an Ethernet service instance: Step Command Remarks Enter system view. system-view • Enter Layer Ethernet...
Page 326: Configuring A Pw
Configuring a PW Configuring a PW class You can configure PW attributes such as the PW data encapsulation type and enable control word in a PW class. PWs with the same attributes can use the same PW class. To configure a PW class: Step Command Remarks...
Page 327: Configuring A Bgp Pw
Step Command Remarks session to the peer PE. Then, the PE exchanges the PW ID FEC and PW label mapping with the peer. Configuring a BGP PW To configure a BGP PW, perform the following configurations on PEs: • Configure BGP to advertise MPLS L2VPN label block information. •...
Page 328 Step Command Remarks 12. (Optional.) Configure By default, the route reflector rr-filter filtering of reflected L2VPN does filter reflected extended-community-number information. L2VPN information. 13. (Optional.) Return to user view. return refresh ip-address 14. (Optional.) Soft-reset L2VPN [ mask-length ] | all | external | BGP sessions.
Page 329: Configuring A Remote Ccc Connection
Configuring a remote CCC connection To configure a remote CCC connection, perform the following configurations on the PE and P devices: • On the two PEs, use the ccc command to specify the incoming and outgoing labels. • On each P device between the two PEs, use the static-lsp transit command to configure a static LSP for each direction of the CCC connection.
Page 330: Configuring Pw Redundancy
Step Command Remarks Enter cross-connect view. connection connection-name interface interface-type Bind the Ethernet service interface-number By default, no Ethernet service instance on the interface to service-instance instance-id instance bound the cross-connect. [ access-mode { ethernet | cross-connect. vlan } ] To bind an Ethernet service instance to a BGP cross-connect: Step Command...
Page 331: Configuring Ldp Pw Redundancy
Step Command Remarks peer ip-address pw-id pw-id [ in-label label-value out-label Enter cross-connect label-value pw-class view. class-name tunnel-policy tunnel-policy-name ] * backup-peer ip-address pw-id Configure backup pw-id in-label label-value cross-connect PW and enter By default, no backup PW is out-label label-value [ pw-class backup cross-connect PW configured.
Page 332: Mpls L2Vpn Configuration Examples
Task Command information. group-name ] [ slot slot-number ] [ verbose ] display l2vpn pw [ xconnect-group group-name ] [ ldp | static ] Display L2VPN PW information. [ verbose ] Display PW class information. display l2vpn pw-class [ class-name ] Display Ethernet service...
Page 333 Table 29 Interface and IP address assignment Device Interface IP address Device Interface IP address PE 1 Loop0 192.2.2.2/32 Loop0 192.4.4.4/32 Vlan-int20 10.1.1.1/24 Vlan-int30 10.2.2.2/24 PE 2 Loop0 192.3.3.3/32 Vlan-int20 10.1.1.2/24 Vlan-int30 10.2.2.1/24 Configuration procedure Before you perform the following configurations, configure VLANs and add ports to VLANs. Configure CE 1.
Page 334 [PE1] interface gigabitethernet1/0/1 [PE1-GigabitEthernet1/0/1] service-instance 10 [PE1-GigabitEthernet1/0/1-srv10] encapsulation s-vid 10 [PE1-GigabitEthernet1/0/1-srv10] quit [PE1-GigabitEthernet1/0/1] quit # Create a cross-connect group named vpna, create a cross-connect named svc in the group, and bind Ethernet service instance 10 on GigabitEthernet 1/0/1 to the cross-connect. [PE1] xconnect-group vpna [PE1-xcg-vpna] connection svc [PE1-xcg-vpna-svc] ac interface GigabitEthernet 1/0/1 service-instance 10...
Page 335 [PE2] interface loopback 0 [PE2-LoopBack0] ip address 192.3.3.3 32 [PE2-LoopBack0] quit [PE2] mpls lsr-id 192.3.3.3 # Enable L2VPN. [PE2] l2vpn enable # Enable global LDP. [PE2] mpls ldp [PE2-ldp] quit # Configure VLAN-interface 30 connected to the P device and enable LDP on the interface. [PE2] interface vlan-interface 30 [PE2-Vlan-interface30] ip address 10.2.2.1 24 [PE2-Vlan-interface30] mpls enable...
Page 336: Configuring An Ldp Pw
[CE2-GigabitEthernet1/0/1] quit Verifying the configuration # Display L2VPN PW information on PE 1. The output shows that a static PW has been established. [PE1] display l2vpn pw Flags: M - main, B - backup, H - hub link, S - spoke link, N - no split horizon Total number of PWs: 1, 1 up, 0 blocked, 0 down, 0 defect Xconnect-group Name: vpna Peer...
Page 337 Configuration procedure Before you perform the following configurations, configure VLANs and add ports to VLANs. Configure CE 1. <CE1> system-view [CE1] interface gigabitethernet 1/0/1 [CE1-GigabitEthernet1/0/1] port link-type trunk [CE1-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE1-GigabitEthernet1/0/1] quit Configure PE 1: # Configure an LSR ID. <PE1>...
Page 338 [PE1-xcg-vpna] connection ldp [PE1-xcg-vpna-ldp] ac interface GigabitEthernet 1/0/1 service-instance 10 # Create an LDP PW for the cross-connect to bind the AC to the PW. [PE1-xcg-vpna-ldp] peer 192.3.3.3 pw-id 3 [PE1-xcg-vpna-ldp-192.3.3.3-3] quit [PE1-xcg-vpna-ldp] quit [PE1-xcg-vpna] quit Configure the P device: # Configure an LSR ID.
Page 339 [PE2] mpls ldp [PE2-ldp] quit # Configure VLAN-interface 30 connected to the P device and enable LDP on the interface. [PE2] interface vlan-interface 30 [PE2-Vlan-interface30] ip address 10.2.2.1 24 [PE2-Vlan-interface30] mpls enable [PE2-Vlan-interface30] mpls ldp enable [PE2-Vlan-interface30] quit # Configure OSPF for LDP to create LSPs. [PE2] ospf [PE2-ospf-1] area 0 [PE2-ospf-1-area-0.0.0.0] network 192.3.3.3 0.0.0.0...
Page 340: Configuring A Bgp Pw
Xconnect-group Name: vpna Peer PW ID In/Out Label Proto Flag Link ID State 192.3.3.3 65679/65679 # Display L2VPN PW information on PE 2. The output shows that an LDP PW has been established. [PE2] display l2vpn pw Flags: M - main, B - backup, H - hub link, S - spoke link, N - no split horizon Total number of PWs: 1, 1 up, 0 blocked, 0 down, 0 defect Xconnect-group Name: vpna Peer...
Page 341 [CE1-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE1-GigabitEthernet1/0/1] quit Configure PE 1: # Configure an LSR ID. <PE1> system-view [PE1] interface loopback 0 [PE1-LoopBack0] ip address 192.2.2.2 32 [PE1-LoopBack0] quit [PE1] mpls lsr-id 192.2.2.2 # Enable L2VPN. [PE1] l2vpn enable # Enable LDP globally. [PE1] mpls ldp [PE1-ldp] quit # Configure VLAN-interface 20 (the interface connected to P), and enable LDP on the interface.
Page 342 # Create a cross-connect group named vpnb, create a local site named site 1, create a BGP PW from site 1 to the remote site site 2, and bind Ethernet service instance 10 on GigabitEthernet 1/0/1 to the PW. [PE1] xconnect-group vpnb [PE1-xcg-vpnb] auto-discovery bgp [PE1-xcg-vpnb-auto] route-distinguisher 2:2 [PE1-xcg-vpnb-auto] vpn-target 2:2 export-extcommunity...
Page 343 [PE2-LoopBack0] ip address 192.3.3.3 32 [PE2-LoopBack0] quit [PE2] mpls lsr-id 192.3.3.3 # Enable L2VPN. [PE2] l2vpn enable # Enable LDP globally. [PE2] mpls ldp [PE2-ldp] quit # Configure VLAN-interface 30 (the interface connected to P), and enable LDP on the interface. [PE2] interface vlan-interface 30 [PE2-Vlan-interface30] ip address 10.2.2.1 24 [PE2-Vlan-interface30] mpls enable...
Page 344: Configuring A Remote Ccc Connection
[PE2-xcg-vpnb-auto] site 2 range 10 default-offset 0 [PE2-xcg-vpnb-auto-2] connection remote-site-id 1 [PE2-xcg-vpnb-auto-2-1] ac interface GigabitEthernet 1/0/1 service-instance 10 [PE2-xcg-vpnb-auto-2-1] return Configure CE 2. <CE2> system-view [CE2] interface gigabitethernet 1/0/1 [CE2-GigabitEthernet1/0/1] port link-type trunk [CE2-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE2-GigabitEthernet1/0/1] quit Verifying the configuration # Display L2VPN PW information on PE 1.
Page 345 Table 32 Interface and IP address assignment Device Interface IP address Device Interface IP address PE 1 Loop0 192.2.2.2/32 Loop0 192.4.4.4/32 Vlan-int20 10.1.1.1/24 Vlan-int20 10.1.1.2/24 PE 2 Loop0 192.3.3.3/32 Vlan-int30 10.2.2.2/24 Vlan-int30 10.2.2.1/24 Configuration procedure Before you perform the following configurations, configure VLANs and add ports to VLANs. Configure CE 1.
Page 346 [PE1-xcg-ccc-ccc] ccc in-label 101 out-label 201 nexthop 10.1.1.2 [PE1-xcg-ccc-ccc] ac interface GigabitEthernet 1/0/1 service-instance 10 [PE1-xcg-ccc-ccc] quit [PE1-xcg-ccc] quit Configure P: # Configure an LSR ID. <P> system-view [P] interface loopback 0 [P-LoopBack0] ip address 192.4.4.4 32 [P-LoopBack0] quit [P] mpls lsr-id 192.4.4.4 # Configure VLAN-interface 20 (the interface connected to PE 1), and enable MPLS on the interface.
Page 347: Configuring Ldp Pw Redundancy
[PE2] interface gigabitethernet1/0/1 [PE2-GigabitEthernet1/0/1] service-instance 10 [PE2-GigabitEthernet1/0/1-srv10] encapsulation s-vid 10 [PE2-GigabitEthernet1/0/1-srv10] quit [PE2-GigabitEthernet1/0/1] quit # Create a cross-connect group named ccc, create a remote CCC connection that has incoming label 202, outgoing label 102, and next hop 10.2.2.2, and bind Ethernet service instance 10 on GigabitEthernet 1/0/1 to the CCC connection.
Page 348 Figure 91 Network diagram Loop0 Loop0 GE1/0/1 Vlan-int10 Vlan-int12 GE1/0/1 Site 1 Site 2 GE1/0/1 Vlan-int12 GE1/0/1 Vlan-int13 Vlan-int10 CE 1 PE 1 PE 2 CE 2 GE1/0/2 Vlan-int10 Loop0 MPLS or IP backbone Vlan-int13 GE1/0/1 PE 3 Table 33 Interface and IP address assignment Device Interface IP address...
Page 349 [PE1-Vlan-interface12] ip address 12.1.1.1 24 [PE1-Vlan-interface12] mpls enable [PE1-Vlan-interface12] mpls ldp enable [PE1-Vlan-interface12] quit [PE1] interface vlan-interface 13 [PE1-Vlan-interface13] ip address 13.1.1.1 24 [PE1-Vlan-interface13] mpls enable [PE1-Vlan-interface13] mpls ldp enable [PE1-Vlan-interface13] quit # Configure OSPF for LDP to create LSPs. [PE1] ospf [PE1-ospf-1] area 0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0...
Page 350 [PE2] mpls lsr-id 2.2.2.2 # Enable global MPLS LDP. [PE2] mpls ldp [PE2-ldp] quit # Configure VLAN interface 12 (the interface connected to PE 1), and enable LDP on it. [PE2] interface vlan-interface 12 [PE2-Vlan-interface12] ip address 12.1.1.2 24 [PE2-Vlan-interface12] mpls enable [PE2-Vlan-interface12] mpls ldp enable [PE2-Vlan-interface12] quit # Configure OSPF for LDP to create LSPs.
Page 351 # Configure VLAN interface 13 (the interface connected to PE 1), and enable LDP on it. [PE3] interface vlan-interface 13 [PE3-Vlan-interface13] ip address 13.1.1.3 24 [PE3-Vlan-interface13] mpls enable [PE3-Vlan-interface13] mpls ldp enable [PE3-Vlan-interface13] quit # Configure OSPF for LDP to create LSPs. [PE3] ospf [PE3-ospf-1] area 0 [PE3-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255...
Page 352 2.2.2.2 65651/65779 3.3.3.3 65650/65779 Blocked # Display detailed information about the primary and backup PWs on PE 1. <PE1> display l2vpn pw verbose Xconnect-group Name: vpna Connection: ldp Peer: 2.2.2.2 PW ID: 20 Signaling Protocol : LDP Link ID PW State : Up In Label : 65651 Out Label: 65779...
Page 353: Configuring An Intra-Domain Multi-Segment Pw
<PE1> display l2vpn pw Flags: M - main, B - backup, H - hub link, S - spoke link, N - no split horizon Total number of PWs: 2, 1 up, 1 blocked, 0 down, 0 defect Xconnect-group Name: vpna Peer PW ID In/Out Label...
Page 354 [CE1-Vlan-interface10] ip address 100.1.1.1 24 [CE1-Vlan-interface10] quit [CE1] interface gigabitethernet 1/0/1 [CE1-GigabitEthernet1/0/1] port link-type trunk [CE1-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE1-GigabitEthernet1/0/1] quit Configure PE 1: # Configure an LSR ID. <PE1> system-view [PE1] interface loopback 0 [PE1-LoopBack0] ip address 192.2.2.2 32 [PE1-LoopBack0] quit [PE1] mpls lsr-id 192.2.2.2 # Enable L2VPN.
Page 355 # Configure MPLS TE to establish an MPLS TE tunnel between PE 1 and P, and between P and PE 2. For more information, see "Configuring MPLS TE." # Create a cross-connect group named vpn1, create a cross-connect named ldpsvc in the group, and create an LDP PW and a static PW for the cross-connect to form a multi-segment PW that includes the two PWs.
Page 356: Configuring An Inter-Domain Multi-Segment Pw
[CE2-vlan10] quit [CE2] interface vlan-interface 10 [CE2-Vlan-interface10] ip address 100.1.1.2 24 [CE2-Vlan-interface10] quit [CE2] interface gigabitethernet 1/0/1 [CE2-GigabitEthernet1/0/1] port link-type trunk [CE2-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE2-GigabitEthernet1/0/1] quit Verifying the configuration # Display L2VPN PW information on P. The output shows that two PWs have been created to form a multi-segment PW.
Page 357 • Configure an LDP PW between ASBR 1 and ASBR 2. Advertise labeled IPv4 routes between ASBR 1 and ASBR 2 through BGP, so as to set up the public tunnel to carry the LDP PW. • Concatenate the two public tunnels on ASBR 1. •...
Page 358 [PE1] mpls lsr-id 192.1.1.1 # Enable L2VPN. [PE1] l2vpn enable # Enable global LDP. [PE1] mpls ldp [PE1-ldp] quit # Configure VLAN-interface 23 connected to ASBR 1, and enable LDP on the interface. [PE1] interface vlan-interface 23 [PE1-Vlan-interface23] ip address 23.1.1.1 24 [PE1-Vlan-interface23] mpls enable [PE1-Vlan-interface23] mpls ldp enable [PE1-Vlan-interface23] quit...
Page 359 [ASBR1] l2vpn enable # Enable global LDP. [ASBR1] mpls ldp [ASBR1-ldp] quit # Configure VLAN-interface 23 connected to PE 1, and enable LDP on the interface. [ASBR1] interface vlan-interface 23 [ASBR1-Vlan-interface23] ip address 23.1.1.2 24 [ASBR1-Vlan-interface23] mpls enable [ASBR1-Vlan-interface23] mpls ldp enable [ASBR1-Vlan-interface23] quit # Configure VLAN-interface 26 connected to ASBR 2, and enable MPLS on the interface.
Page 360 [ASBR2] interface loopback 0 [ASBR2-LoopBack0] ip address 192.3.3.3 32 [ASBR2-LoopBack0] quit [ASBR2] mpls lsr-id 192.3.3.3 # Enable L2VPN. [ASBR2] l2vpn enable # Enable global LDP. [ASBR2] mpls ldp [ASBR2-ldp] quit # Configure VLAN-interface 22 connected to PE 2, and enable LDP on the interface. [ASBR2] interface vlan-interface 22 [ASBR2-Vlan-interface22] ip address 22.2.2.3 24 [ASBR2-Vlan-interface22] mpls enable...
Page 361 [ASBR2-xcg-vpn1-ldp] quit [ASBR2-xcg-vpn1] quit Configure PE 2: # Configure an LSR ID. <PE2> system-view [PE2] interface loopback 0 [PE2-LoopBack0] ip address 192.4.4.4 32 [PE2-LoopBack0] quit [PE2] mpls lsr-id 192.4.4.4 # Enable L2VPN. [PE2] l2vpn enable # Enable global LDP. [PE2] mpls ldp [PE2-ldp] quit # Configure VLAN-interface 22 connected to ASBR 1, and enable LDP on the interface.
Page 362 Configure CE 2. <CE2> system-view [CE2] vlan 10 [CE2-vlan10] quit [CE2] interface vlan-interface 10 [CE2-Vlan-interface10] ip address 100.1.1.2 24 [CE2-Vlan-interface10] quit [CE2] interface gigabitethernet 1/0/1 [CE2-GigabitEthernet1/0/1] port link-type trunk [CE2-GigabitEthernet1/0/1] port trunk permit vlan 10 [CE2-GigabitEthernet1/0/1] quit Verifying the configuration # Display L2VPN PW information on PE 1.
Page 363 # Verify that CE 1 and CE 2 can ping each other. (Details not shown.)
Page 364: Configuring Vpls
Configuring VPLS Overview Virtual Private LAN Service (VPLS) delivers a point-to-multipoint L2VPN service over an MPLS or IP backbone. The provider backbone emulates a switch to connect all geographically dispersed sites of each customer network. The backbone is transparent to the customer sites, which can communicate with each other as if they were on the same LAN.
Page 365: Vpls Implementation
to create a single Layer 2 VPN, which is referred to as a VPLS instance. Sites in different VPLS instances cannot communicate with each other at Layer 2. • VSI—A virtual switch instance provides Layer 2 switching services for a VPLS instance on a PE.
Page 366 Figure 95 Source MAC address learning on a PE PE 1 Port ARP broadcast VPN 1 Vlan 10, port 1 ARP response VPN 1 PW 1 MPLS or IP PE 1 PE 3 backbone PW 3 VLAN 10 VLAN 10 Port 1 Port 1 MAC A IP 1.1.1.2...
Page 367: H-Vpls
PW full mesh and split horizon A loop prevention protocol such as STP is required in a Layer 2 network to avoid loops. However, deploying a loop prevention protocol on PEs brings management and maintenance difficulties. Therefore, VPLS uses the following methods to prevent loops: •...
Page 368 Figure 97 H-VPLS using Ethernet access Backbone NPE 2 domain CE 1 N-PW N-PW Edge domain (Ethernet) CE 3 QinQ N-PW NPE 1 NPE 3 CE 2 As shown in Figure 97, in Ethernet access mode, the edge domain is an Ethernet network. The UPE and NPE 1 establish a point-to-point Ethernet QinQ connection in between (enable QinQ on the UPE interfaces connecting CEs and configure VLAN access mode on NPE 1).
Page 369: Vpls Configuration Task List
• The primary U-PW is deleted by the control plane. For example, the LDP session on the primary U-PW link is down, causing the primary U-PW to be deleted. • BFD detects a failure of the primary U-PW. • A primary and backup U-PW switchover is triggered by a command. As a best practice, execute the port bridge enable command on the NPE 1' interface connected to NPE 4 when the following conditions are met: •...
Page 370: Enabling L2Vpn
Enabling L2VPN Perform this task to enable L2VPN on the PE. Before you enable L2VPN, perform the following tasks: • Configure an LSR ID for the PE with the mpls lsr-id command. • Enable MPLS with the mpls enable command on the backbone interface of the PE. For more information about these commands, see MPLS Command Reference.
Page 371: Configuring A Vsi
Configuring a VSI Step Command Remarks Enter system view. system-view Create a VSI and enter VSI vsi vsi-name By default, no VSI is created. view. (Optional.) Configure By default, no description is description text description for the VSI. configured for a VSI. (Optional.) Configure By default, no default PW ID is...
Page 372: Configuring An Ldp Pw
Step Command Remarks tunnel-policy-name ] * no default PW ID is configured, you must provide a PW ID in the peer command. You must specify the no-split-horizon keyword to disable split horizon when you configure an NPE to establish a U-PW with a UPE.
Page 373 Step Command Remarks address family and enter address family is created. BGP L2VPN address family view. Enable BGP to exchange default, cannot peer { group-name | ip-address L2VPN information with the exchange L2VPN information [ mask-length ] } enable specified peer or peer group. with any peer or peer group.
Page 374: Configuring A Bgp Auto-Discovery Ldp Pw
Step Command Remarks Configure automatically discover By default, a VSI does not neighbors through BGP and auto-discovery bgp automatically discover neighbors enter auto-discovery through BGP. view. Configure an RD for the route-distinguisher By default, no RD is configured for auto-discovery VSI. route-distinguisher the auto-discovery VSI.
Page 375 Step Command Remarks the specified peer or peer [ non-standard ] BGP L2VPN peer or peer group. group by using RFC 6074 MP_REACH_NLRI. (Optional.) Permit the local AS number to appear in peer { group-name | ip-address default, local routes from the specified [ mask-length ] } allow-as-loop number is not allowed in routes peer or peer group and...
Page 376: Binding An Ac To A Vsi
Step Command Remarks the auto-discovery VSI. [ both | export-extcommunity | configured for the auto-discovery import-extcommunity ] VSI. (Optional.) Specify a PW By default, no PW class is class for the auto-discovery pw-class class-name specified. VSI. (Optional.) Specify a tunnel By default, no tunnel policy is policy for the auto-discovery tunnel-policy tunnel-policy-name...
Page 377: Configuring Static Pw Redundancy
• Specify whether to switch traffic from the backup PW to the primary PW when the primary PW recovers, and the wait time for the switchover. • Perform a manual PW switchover. Configuring static PW redundancy Step Command Remarks Enter system view. system-view Enter VSI view.
Page 378: Configuring Mac Address Learning
Step Command Remarks PW when the primary PW PW to the primary PW. recovers, and the wait time for the switchover. peer ip-address [ pw-id pw-id ] Configure an LDP PW and [ no-split-horizon | pw-class By default, no LDP PW is enter VSI LDP PW view.
Page 379: Vpls Configuration Examples
Task Command [ verbose ] Display VSI information. display l2vpn vsi [ name vsi-name ] [ verbose ] Display information about automatically display l2vpn auto-discovery [ peer ip-address ] [ vsi discovered VPLS PEs. vsi-name ] display l2vpn bgp [ peer ip-address | local ] [ vsi Display VPLS label block information.
Page 380 Figure 99 Network diagram Loop0 3.3.3.9/32 VPN 1 CE 3 GE1/0/1 Vlan-int30 Vlan-int40 PE 3 PE 1 PE 2 Vlan-int30 Vlan-int40 GE1/0/1 GE1/0/1 Vlan-int20 Vlan-int20 Loop0 Loop0 2.2.2.9/32 1.1.1.9/32 VPN 1 VPN 1 CE 1 CE 2 Configuration procedure This task includes the following configurations: •...
Page 381 [PE1-ospf-1] area 0 [PE1-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Create a VSI on PE 1, and configure the peer PEs. [PE1] vsi svc [PE1-vsi-svc] pwsignaling static [PE1-vsi-svc-static] peer 2.2.2.9 pw-id 3 in-label 100 out-label 100 [PE1-vsi-svc-static-2.2.2.9-3] quit [PE1-vsi-svc-static] peer 3.3.3.9 pw-id 3 in-label 200 out-label 200 [PE1-vsi-svc-static-3.3.3.9-3] quit...
Page 382 [PE2-ospf-1] area 0 [PE2-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Create a VSI on PE 2, and configure the peer PEs. [PE2] vsi svc [PE2-vsi-svc] pwsignaling static [PE2-vsi-svc-static] peer 1.1.1.9 pw-id 3 in-label 100 out-label 100 [PE2-vsi-svc-static-1.1.1.9-3] quit [PE2-vsi-svc-static] peer 3.3.3.9 pw-id 3 in-label 300 out-label 300 [PE2-vsi-svc-static-3.3.3.9-3] quit...
Page 383 [PE3-ospf-1] area 0 [PE3-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Create a VSI on PE 3 and configure the peer PEs. [PE3] vsi svc [PE3-vsi-svc] pwsignaling static [PE3-vsi-svc-static] peer 1.1.1.9 pw-id 3 in-label 200 out-label 200 [PE3-vsi-svc-static-1.1.1.9-3] quit [PE3-vsi-svc-static] peer 2.2.2.9 pw-id 3 in-label 300 out-label 300 [PE3-vsi-svc-static-2.2.2.9-3] quit...
Page 384: Ldp Pw Configuration Example
LDP PW configuration example Network requirements Configure VPLS on each PE, and establish LDP PWs between the PEs to interconnect the CEs. Figure 100 Network diagram Loop0 3.3.3.9/32 VPN 1 CE 3 GE1/0/1 Vlan-int30 Vlan-int40 PE 3 PE 1 PE 2 Vlan-int30 Vlan-int40 GE1/0/1...
Page 385 # Bind Ethernet service instance 10 to the VSI aaa. [PE1-GigabitEthernet1/0/1-srv10] xconnect vsi aaa Configure PE 2: # Configure basic MPLS. <PE2> system-view [PE2] interface loopback 0 [PE2-LoopBack0] ip address 2.2.2.9 32 [PE2-LoopBack0] quit [PE2] mpls lsr-id 2.2.2.9 [PE2] mpls ldp [PE2-ldp] quit # Enable L2VPN.
Page 386: Bgp Pw Configuration Example
[PE3-vsi-aaa-ldp] quit [PE3-vsi-aaa] quit # Create Ethernet service instance 10 on GigabitEthernet 1/0/1 to match all packets. [PE3] interface gigabitethernet1/0/1 [PE3-GigabitEthernet1/0/1] service-instance 10 [PE3-GigabitEthernet1/0/1-srv10] encapsulation default # Bind Ethernet service instance 10 to the VSI aaa. [PE3-GigabitEthernet1/0/1-srv10] xconnect vsi aaa Verifying the configuration # Execute the display l2vpn pw verbose command on PE 1.
Page 387 Figure 101 Network diagram Loop0 3.3.3.9/32 VPN 1 CE 3 GE1/0/1 Vlan-int30 Vlan-int40 PE 3 PE 1 PE 2 Vlan-int30 Vlan-int40 GE1/0/1 GE1/0/1 Vlan-int20 Vlan-int20 Loop0 Loop0 2.2.2.9/32 1.1.1.9/32 VPN 1 VPN 1 CE 1 CE 2 Configuration procedure Configure the IGP and public tunnels. (Details not shown.) Configure PE 1: # Configure basic MPLS.
Page 388 [PE1-vsi-aaa-auto-bgp] quit [PE1-vsi-aaa-auto] quit [PE1-vsi-aaa] quit # Create Ethernet service instance 10 on GigabitEthernet 1/0/1 to match all packets. [PE1] interface gigabitethernet1/0/1 [PE1-GigabitEthernet1/0/1] service-instance 10 [PE1-GigabitEthernet1/0/1-srv10] encapsulation default # Bind Ethernet service instance 10 to the VSI aaa. [PE1-GigabitEthernet1/0/1-srv10] xconnect vsi aaa Configure PE 2: # Configure basic MPLS.
Page 389 Configure PE 3: # Configure basic MPLS. <PE3> system-view [PE3] interface loopback 0 [PE3-LoopBack0] ip address 3.3.3.9 32 [PE3-LoopBack0] quit [PE3] mpls lsr-id 3.3.3.9 [PE3] mpls ldp [PE3-ldp] quit # Establish IBGP connections to PE 1 and PE 2 and use BGP to advertise VPLS label block information.
Page 390 : 1500 PW Attributes : Main VCCV CC VCCV BFD Tunnel Group ID : 0x1800000160000001 Tunnel NHLFE IDs : 137 Peer: 3.3.3.9 Remote Site: 3 Signaling Protocol : BGP Link ID : 10 PW State : Up In Label : 131196 Out Label: 131225 : 1500 PW Attributes...
Page 391: Bgp Auto-Discovery Ldp Pw Configuration Example
BGP auto-discovery LDP PW configuration example Network requirements Use BGP to discover remote PEs and use LDP to create PWs among PEs so CEs in different sites of VPN 1 can communicate with each other. Figure 102 Network diagram Loop0 3.3.3.9/32 VPN 1 CE 3...
Page 392 # Configure the VSI aaa to use BGP to discover remote PEs and use LDP to establish LDP PWs to PE 2 and PE 3. [PE1] vsi aaa [PE1-vsi-aaa] auto-discovery bgp [PE1-vsi-aaa-auto] route-distinguisher 1:1 [PE1-vsi-aaa-auto] vpn-target 1:1 [PE1-vsi-aaa-auto] signaling-protocol ldp [PE1-vsi-aaa-auto-ldp] vpls-id 100:100 [PE1-vsi-aaa-auto-ldp] quit [PE1-vsi-aaa-auto] quit...
Page 393 [PE2-vsi-aaa-auto-ldp] quit [PE2-vsi-aaa-auto] quit [PE2-vsi-aaa] quit # Create Ethernet service instance 10 on GigabitEthernet 1/0/1 to match all packets. [PE2] interface gigabitethernet1/0/1 [PE2-GigabitEthernet1/0/1] service-instance 10 [PE2-GigabitEthernet1/0/1-srv10] encapsulation default # Bind Ethernet service instance 10 to the VSI aaa. [PE2-GigabitEthernet1/0/1-srv10] xconnect vsi aaa Configure PE 3: # Configure basic MPLS.
Page 394 [PE3-GigabitEthernet1/0/1-srv10] xconnect vsi aaa Verifying the configuration # Execute the display l2vpn pw verbose command on PE 1. The output shows that two LDP PWs have been established. [PE1] display l2vpn pw verbose VSI Name: aaa Peer: 2.2.2.9 VPLS ID: 100:100 Signaling Protocol : LDP Link ID...
Page 395: H-Vpls Using Access Configuration Example
PW ID FEC (Local/Remote): Local AII : (1.1.1.9, 3.3.3.9) Remote AII : (3.3.3.9, 1.1.1.9) PW Type : VLAN/VLAN Group ID : 0/0 Label : 131154/131116 Control Word: Disabled/Disabled VCCV CV Type: -/- VCCV CC Type: -/- : 1500/1500 PW Status : PW forwarding/PW forwarding H-VPLS using access configuration example Network requirements...
Page 396 # Configure VSI aaa to use LDP to establish a U-PW to NPE 1. [UPE] vsi aaa [UPE-vsi-aaa] pwsignaling ldp [UPE-vsi-aaa-ldp] peer 2.2.2.9 pw-id 500 [UPE-vsi-aaa-ldp-2.2.2.9-500] quit [UPE-vsi-aaa-ldp] quit [UPE-vsi-aaa] quit # Create Ethernet service instance 10 on GigabitEthernet 1/0/1 to match all packets. [UPE] interface gigabitethernet1/0/1 [UPE-GigabitEthernet1/0/1] service-instance 10 [UPE-GigabitEthernet1/0/1-srv10] encapsulation default...
Page 397 # Configure VSI aaa that uses LDP as the PW signaling protocol, and establish an N-PW to NPE 1 and NPE 3, respectively. [NPE2] vsi aaa [NPE2-vsi-aaa] pwsignal ldp [NPE2-vsi-aaa-ldp] peer 2.2.2.9 pw-id 500 [NPE2-vsi-aaa-ldp-2.2.2.9-500] quit [NPE2-vsi-aaa-ldp] peer 4.4.4.9 pw-id 500 [NPE2-vsi-aaa-ldp-4.4.4.9-500] quit [NPE2-vsi-aaa-ldp] quit [NPE2-vsi-aaa] quit...
Page 398 Peer: 2.2.2.9 PW ID: 500 Signaling Protocol : LDP Link ID PW State : Up In Label : 131177 Out Label: 131177 : 1500 PW Attributes : Main VCCV CC VCCV BFD Tunnel Group ID : 0x1800000460000000 Tunnel NHLFE IDs : 130 [NPE1] display l2vpn pw verbose VSI Name: aaa...
Page 399: H-Vpls Upe Dual Homing Configuration Example
: 1500 PW Attributes : Main VCCV CC VCCV BFD Tunnel Group ID : 0x1800000660000000 Tunnel NHLFE IDs : 131 Peer: 4.4.4.9 PW ID: 500 Signaling Protocol : LDP Link ID PW State : Up In Label : 131177 Out Label: 131177 : 1500 PW Attributes : Main...
Page 400 Figure 104 Network diagram Loop0 2.2.2.2/32 Backbone NPE 1 domain Edge Vlan-int12 Vlan-int15 domain 12.1.1.2/24 15.1.1.1/24 CE 1 Vlan-int17 Loop0 17.1.1.1/24 Vlan-int12 4.4.4.4/32 GE1/0/1 12.1.1.1/24 Vlan-int15 VLAN 11 GE1/0/1 15.1.1.2/24 VLAN 10 Vlan-int16 GE1/0/2 16.1.1.2/24 VLAN 10 NPE 3 CE 3 Vlan-int13 Vlan-int17 13.1.1.1/24...
Page 401 [UPE] interface gigabitethernet 1/0/1 [UPE-GigabitEthernet1/0/1] service-instance 1000 [UPE-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 10 [UPE-GigabitEthernet1/0/1-srv1000] xconnect vsi aaa [UPE-GigabitEthernet1/0/1-srv1000] quit # Create VLAN 11 and assign GigabitEthernet 1/0/2 to the VLAN. [UPE] vlan 11 [UPE-vlan11] port gigabitethernet 1/0/2 [UPE-vlan11] quit # On interface GigabitEthernet 1/0/2 connected to CE 2, create an Ethernet service instance and bind the Ethernet service instance to VSI aaa.
Page 402 # Enable L2VPN. [NPE2] l2vpn enable # Configure VSI aaa that uses LDP as the PW signaling protocol, and establish a PW to UPE, NPE 2, and NPE 3, respectively. [NPE2] vsi aaa [NPE2-vsi-aaa] pwsignaling ldp [NPE2-vsi-aaa-ldp] peer 1.1.1.1 pw-id 500 no-split-horizon [NPE2-vsi-aaa-ldp-1.1.1.1-500] quit [NPE2-vsi-aaa-ldp] peer 2.2.2.2 pw-id 500 [NPE2-vsi-aaa-ldp-2.2.2.2-500] quit...
Page 403 Verifying the configuration # Execute the display l2vpn pw verbose command on each PE. The output shows that PWs in up state have been established. [UPE] display l2vpn pw verbose VSI Name: aaa Peer: 2.2.2.2 PW ID: 500 Signaling Protocol : LDP Link ID PW State : Up...
Page 404 Peer: 4.4.4.4 PW ID: 500 Signaling Protocol : LDP Link ID : 10 PW State : Up In Label : 131278 Out Label: 131279 : 1500 PW Attributes : Main VCCV CC VCCV BFD Tunnel Group ID : 0x1800000160000001 Tunnel NHLFE IDs : 138 [NPE2] display l2vpn pw verbose VSI Name: aaa...
Page 405 : 1500 PW Attributes : Main VCCV CC VCCV BFD Tunnel Group ID : 0x180000060000000 Tunnel NHLFE IDs : 136 Peer: 3.3.3.3 PW ID: 500 Signaling Protocol : LDP Link ID PW State : Up In Label : 131278 Out Label: 131278 : 1500 PW Attributes : Main...
Page 406: Configuring Mpls Oam
Configuring MPLS OAM Overview MPLS Operation, Administration, and Maintenance (OAM) provides fault management tools for the following purposes: • MPLS data plane connectivity verification. • Data plane and control plane consistency verification. • Fault locating. These fault management tools include the following types: •...
Page 407: Periodic Mpls Tracert
• Static mode—You manually specify the local and remote discriminators through command lines to establish the BFD session. • Dynamic mode—The system automatically runs MPLS ping to negotiate the discriminators to establish the BFD session. In static mode, the egress node returns a BFD control packet to the ingress node through the reverse tunnel.
Page 408: Configuring Mpls Tracert For Lsps
Task Command packet-size | -t time-out | -v ] * ipv4 dest-addr mask-length destination start-address end-address [ address-increment ] ] ] Configuring MPLS tracert for LSPs Perform the following task in any view: Task Command tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r Use MPLS tracert to trace the LSPs for reply-mode | -rtos tos-value | -t time-out | -v | fec-check ] * ipv4 an IPv4 prefix.
Page 409: Configuring Periodic Mpls Tracert For Lsps
Step Command Remarks By default, BFD for MPLS is Enable BFD for MPLS. mpls bfd enable disabled. mpls bfd dest-addr mask-length nexthop nexthop-address By default, BFD is not configured Configure BFD to verify LSP [ discriminator local local-id to verify LSP connectivity for an connectivity for an FEC.
Page 410: Configuring Mpls Oam For A Pw
• If both BFD and FRR are enabled for an MPLS TE tunnel, set the BFD detection interval for MPLS TE tunnel connectivity verification to be longer than that for FRR. Otherwise, the BFD session for MPLS TE tunnel connectivity verification will be down during an FRR switchover. To configure BFD for MPLS TE tunnels: Step Command...
Page 411 Enable BFD for MPLS. Create a PW class, and configure BFD for PW connectivity verification in PW class view. Create the PW, and reference the PW class created in the previous step for the PW. Whether BFD is used to verify PW connectivity, which encapsulation type is used for the BFD packets, and which CC type is used are determined by the configurations on both ends of the PW.
Page 412 Step Command Remarks session used to verify the Make sure the local discriminator connectivity of the backup remote discriminator configured on the local PE are the same as the remote discriminator and local discriminator configured on the remote PE, respectively. Configuring BFD for a VPLS static PW Step Command...
Page 413 Step Command Remarks on the remote PE, respectively. Configuring BFD for a VPLS LDP PW Step Command Remarks Enter system view. system-view By default, BFD for MPLS is Enable BFD for MPLS. mpls bfd enable disabled. By default, no PW class is created. To use BFD to verify connectivity of Create a PW class and pw-class class-name...
Page 414: Displaying Mpls Oam
Displaying MPLS OAM Execute display commands in any view. Task Command Display BFD information for LSP display mpls bfd [ ipv4 dest-addr mask-length | te tunnel tunnels or MPLS TE tunnels. tunnel-number ] display l2vpn pw bfd [ peer peer-ip pw-id pw-id ] Display BFD information for PWs.
Page 415 <SwitchC> system-view [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0 [SwitchC-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Enable MPLS and LDP: # Configure Switch A. [SwitchA] mpls lsr-id 1.1.1.9 [SwitchA] mpls ldp [SwitchA-ldp] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] mpls enable [SwitchA-Vlan-interface2] mpls ldp enable [SwitchA-Vlan-interface2] quit...
Page 416: Bfd For Pw Configuration Example
FEC Type: LSP FEC Info: Destination: 1.1.1.9 Mask Length: 32 NHLFE ID: - Local Discr: 514 Remote Discr: 514 Source IP: 1.1.1.9 Destination IP: 3.3.3.9 Session State: Up Session Role: Active Template Name: - FEC Type: LSP FEC Info: Destination: 3.3.3.9 Mask Length: 32 NHLFE ID: 1025 Local Discr: 513...
Page 417 Table 38 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Vlan-int10 100.1.1.1/24 PE 2 Loop0 2.2.2.2/32 PE 1 Loop0 1.1.1.1/32 Vlan-int12 12.1.1.2/24 Vlan-int12 12.1.1.1/24 PE 3 Loop0 3.3.3.3/32 Vlan-int13 13.1.1.1/24 Vlan-int13 13.1.1.3/24 CE 2 Vlan-int10 100.1.1.2/24 Configuration procedure...
Page 418 [PE1] l2vpn enable # Enable BFD for MPLS. [PE1] mpls bfd enable # Create interface VLAN-interface 10 connected to CE 1. This interface does not need an IP address. [PE1] interface vlan-interface 10 [PE1-Vlan-interface10] quit # Create PW class pwa. In the PW class, configure BFD to verify PW connectivity and configure the VCCV CC type as router-alert.
Page 419 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Enable L2VPN. [PE2] l2vpn enable # Enable BFD for MPLS. [PE2] mpls bfd enable # Create interface VLAN-interface 10 connected to CE 2. This interface does not need an IP address. [PE2] interface vlan-interface 10 [PE2-Vlan-interface10] quit # Create PW class pwa.
Page 420 [PE3-ospf-1] quit # Enable L2VPN. [PE3] l2vpn enable # Create interface VLAN-interface 10 connected to CE 2. This interface does not need an IP address. [PE3] interface vlan-interface 10 [PE3-Vlan-interface10] quit # Create cross-connect group vpna and create a cross-connect named ldp in the cross-connect group.
Page 421 1.1.1.1 65779/65650 # Execute the display l2vpn pw bfd command on PE 1 and PE 2. The output shows that a BFD session in up state has been established between PE 1 and PE 2 to verify the PW connectivity between 1.1.1.1/32 and 3.3.3.3/32.
Page 422: Configuring Mce
Configuring MCE This chapter describes MCE configuration. For information about the related routing protocols, see — Layer 3 IP Routing Configuration Guide. MPLS L3VPN overview MPLS L3VPN is a L3VPN technology used to interconnect geographically dispersed VPN sites. MPLS L3VPN uses BGP to advertise VPN routes and uses MPLS to forward VPN packets over a service provider backbone.
Page 423 • A site is a group of IP systems with IP connectivity that does not rely on any service provider network. • The classification of a site depends on the topology relationship of the devices, rather than the geographical positions. However, the devices at a site are, in most cases, adjacent to each other geographically.
Page 424: Mce Overview
• When the Type field is 1, the Administrator subfield occupies four bytes, the Assigned number subfield occupies two bytes, and the RD format is 32-bit IPv4 address:16-bit user-defined number. For example, 172.1.1.1:1. • When the Type field is 2, the Administrator subfield occupies four bytes, the Assigned number subfield occupies two bytes, and the RD format is 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536.
Page 425: Mce Configuration Task List
As shown in Figure 109, the MCE exchanges private routes with VPN sites and PE 1, and adds the private routes to the routing tables of corresponding VPN instances. • Route exchange between MCE and VPN site—Create VPN instances VPN 1 and VPN 2 on the MCE.
Page 426: Associating A Vpn Instance With An Interface
Step Command Remarks description configured for a VPN instance. instance. (Optional.) Configure a VPN default, vpn-id vpn-id ID for the VPN instance. configured for a VPN instance. Associating a VPN instance with an interface After creating and configuring a VPN instance, associate the VPN instance with the MCE's interface connected to the site and the interface connected to the PE.
Page 427: Configuring Routing On An Mce
Step Command Remarks The specified routing policy must have been created. For information about routing policies, see Layer 3—IP Routing Configuration Guide. By default, routes to be advertised are not filtered. The specified routing policy must Apply an export routing export route-policy route-policy have been created.
Page 428 Step Command Remarks ip route-static vpn-instance s-vpn-instance-name By default, no static dest-address { mask-length | mask } { interface-type route is configured. interface-number next-hop-address Configure static next-hop-address public track Perform this route vpn-instance track-entry-number configuration on the instance. d-vpn-instance-name next-hop-address track MCE.
Page 429 Step Command Remarks system view. Therefore, configure a router ID for the OSPF process. An OSPF process can belong to only one VPN instance, but one VPN instance can use multiple OSPF processes to advertise VPN routes. The default domain ID is 0. Perform this configuration on the MCE.
Page 430 Binding IS-IS processes to VPN instances can isolate routes of different VPNs. For more information about IS-IS, see Layer 3—IP Routing Configuration Guide. To configure IS-IS between an MCE and a VPN site: Step Command Remarks Enter system view. system-view Create an IS-IS process for a Perform this configuration on the isis [ process-id ] vpn-instance...
Page 431 Step Command Remarks Allow the local AS number to appear in the AS_PATH peer { group-name | ip-address default, discards attribute of routes received [ mask-length ] } allow-as-loop incoming route updates that from the peer, and set the [ number ] contain the local AS number.
Page 432: Configuring Routing Between An Mce And A Pe
Step Command Remarks address family view. Enable BGP to exchange default, does peer { group-name | ip-address IPv4 unicast routes with the exchange IPv4 unicast routes with [ mask-length ] } enable peer. any peer. By default, no RR or RR client is configured.
Page 433 • Performing route configurations. • Redistributing VPN routes into the routing protocol running between the MCE and the PE. Perform the following configurations on the MCE. Configure the PE in the same way that you configure a PE in a basic MPLS L3VPN. For more information about configuring the PE, see "Configuring MPLS L3VPN."...
Page 434 Step Command Remarks routes from the PE. (Optional.) Configure domain-id domain-id The default domain ID is 0. OSPF domain ID. [ secondary ] The defaults are as follows: (Optional.) Configure ext-community-type • 0x0005 for Domain ID. type codes OSPF domain-id type-code1 extended community...
Page 435 Step Command Remarks IS-IS view. Configure a network network-entity net By default, no NET is configured. entity title. default, IS-IS does import-route protocol [ process-id | redistribute routes from any other all-processes allow-ibgp routing protocol. Redistribute [ allow-direct | cost cost | cost-type If you do not specify the route level routes.
Page 436: Displaying And Maintaining Mce
Configuring IBGP between an MCE and a PE Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN ip vpn-instance vpn-instance-name instance view. Configure the PE as an peer group-name ip-address IBGP peer. [ mask-length ] } as-number as-number Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ]...
Page 437: Mce Configuration Examples
MCE configuration examples Configuring the MCE that uses OSPF to advertise VPN routes to the PE Network requirements As shown in Figure 110, VPN 2 runs OSPF. Configure the MCE device to separate routes from different VPNs and to advertise the VPN routes to PE 1 through OSPF. Figure 110 Network diagram VPN 2 Site 1...
Page 438 # Create VLAN 10, add port FortyGigE 1/0/1 to VLAN 10. [MCE] vlan 10 [MCE-vlan10] port fortygige 1/0/1 [MCE-vlan10] quit # Create VLAN-interface 10, and bind VLAN-interface 10 to VPN instance vpn1. [MCE] interface vlan-interface 10 [MCE-Vlan-interface10] ip binding vpn-instance vpn1 # Configure an IP address for VLAN-interface 10.
Page 439 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.214.10.0/24 Direct 0 10.214.10.3 Vlan10 10.214.10.0/32 Direct 0 10.214.10.3 Vlan10 10.214.10.3/32 Direct 0 127.0.0.1 InLoop0 10.214.10.255/32 Direct 0 10.214.10.3 Vlan10 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1...
Page 440 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.10.0/24 OSPF 10.214.20.2 Vlan20 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 The output shows that the MCE has learned the private routes of VPN 2. The MCE maintains the routes of VPN 1 and those of VPN2 in two different routing tables.
Page 441 [PE1] interface vlan-interface 40 [PE1-Vlan-interface40] ip binding vpn-instance vpn2 [PE1-Vlan-interface40] ip address 40.1.1.2 24 [PE1-Vlan-interface40] quit # Configure the IP address of the interface Loopback 0 as 101.101.10.1 for the MCE and as 100.100.10.1 for PE 1. Specify the loopback interface address as the router ID for the MCE and PE 1.
Page 442: Configuring The Mce That Uses Ebgp To Advertise Vpn Routes To The Pe
224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 # On PE 1, display the routing information for VPN 2. The output shows that the routes of OSPF process 2 in VPN 2 have been redistributed to the OSPF routing table of PE 1. [PE1] display ip routing-table vpn-instance vpn2 Destinations : 13 Routes : 13...
Page 443 Figure 111 Network diagram VPN 2 Site 1 CE 1 PE 2 PE 1 GE1/0/1 Vlan-int30: 30.1.1.2/24 Vlan-int40: 40.1.1.2/24 PE 3 CE 2 GE1/0/3 VPN 1 VPN 1 Vlan-int30: 30.1.1.1/24 Site 2 GE1/0/1 192.168.0.0/24 Vlan-int40: 40.1.1.1/24 Vlan-int10 GE1/0/2 VR 1 10.214.10.3/24 Vlan-int20 10.214.20.3/24...
Page 444 10.214.10.255/32 Direct 0 10.214.10.3 Vlan10 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.0.0/24 OSPF 10.214.10.2 Vlan10 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0...
Page 445 [PE1] bgp 200 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 30.1.1.1 as-number 100 [PE1-bgp-vpn1] address-family ipv4 [PE1-bgp-ipv4-vpn1] peer 30.1.1.1 enable [PE1-bgp-ipv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # Use similar procedures to configure VPN 2 settings on MCE and PE 1. (Details not shown.) Verifying the configuration # Display the routing information for VPN 1 on PE 1.
Page 446 The MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1.
Page 447: Configuring Ipv6 Mce
Configuring IPv6 MCE This chapter describes IPv6 MCE configuration. Overview In MPLS L3VPN networks, MCE uses static routes or dynamic routing protocols to advertise IPv4 routes between internal networks and PEs and forwards IPv4 packets. In IPv6 MPLS L3VPN networks, IPv6 MCE uses IPv6 static routes and dynamic routing protocols to advertise IPv6 routes between internal networks and PEs and forwards IPv6 packets.
Page 448: Associating A Vpn Instance With An Interface
Step Command Remarks relationship with a certain VPN. (Optional.) Configure an ID By default, no ID is configured for vpn-id vpn-id for the VPN instance. a VPN instance. Associating a VPN instance with an interface After creating and configuring a VPN instance, associate the VPN instance with the MCE's interface connected to the site and the interface connected to the PE.
Page 449: Configuring Routing On An Mce
Step Command Remarks By default, the number of active routes in a VPN instance is not limited. Set the maximum number of routing-table limit number Setting the maximum number of active routes. { warn-threshold | simply-alert } active routes for a VPN instance can prevent the PE from storing too many routes.
Page 450: Configuring Routing Between An Mce And A Vpn Site
Configuring routing between an MCE and a VPN site You can configure static routing, RIPng, OSPFv3, IPv6 IS-IS, or EBGP between an MCE and a VPN site. Configuring static routing between an MCE and a VPN site An MCE can reach a VPN site through an IPv6 static route. IPv6 static routing on a traditional CE is globally effective and does not support address overlapping among VPNs.
Page 451 Step Command Remarks Enable RIPng ripng process-id enable By default, RIPng is disabled. interface. Configuring OSPFv3 between an MCE and a VPN site An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an OSPFv3 process without binding it to an IPv6 VPN instance, the process belongs to the public network.
Page 452 To configure IPv6 IS-IS between an MCE and a VPN site: Step Command Remarks Enter system view. system-view Create an IPv6 IS-IS process Perform this configuration on the isis [ process-id ] vpn-instance for a VPN instance and enter MCE. On a VPN site, configure vpn-instance-name IS-IS view.
Page 453 Step Command Remarks of received routes. prefix-list ipv6-prefix-name received routes. import Configure a VPN site: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number peer { group-name | ipv6-address Configure the MCE as an By default, no BGP peer is [ prefix-length ] } as-number EBGP peer.
Page 454: Configuring Routing Between An Mce And A Pe
Step Command Remarks as a client of the RR (the MCE). import-route protocol Redistribute remote site [ process-id [ allow-direct | med default, routes routes advertised by the PE med-value route-policy redistributed into BGP. into BGP. route-policy-name ] * ] filter-policy acl6-number (Optional.) Configure filtering...
Page 455 Step Command Remarks ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number Configure IPv6 By default, no IPv6 [ next-hop-address ] | nexthop-address [ public ] | static route for an IPv6 static route vpn-instance d-vpn-instance-name VPN instance. configured. nexthop-address } [ permanent ] [ preference preference-value ] [ tag tag-value ] [ description description-text ] (Optional.)
Page 456 Step Command Remarks import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost default, routes Redistribute VPN routes. cost | nssa-only | route-policy redistributed into OSPFv3. route-policy-name | tag tag | type type ] * filter-policy acl6-number ipv6-prefix ipv6-prefix-name (Optional.) Configure filtering...
Page 457 Configuring EBGP between an MCE and a PE Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN instance vpn-instance view. vpn-instance-name peer { group-name | ipv6-address Configure the PE as an By default, no BGP peer is [ prefix-length ] } as-number EBGP peer.
Page 458: Displaying And Maintaining Ipv6 Mce
Displaying and maintaining IPv6 MCE Execute display commands in any view. Task Command Display information about specified VPN instance or all VPN display ip vpn-instance [ instance-name vpn-instance-name ] instances. Display peer group display group ipv6 unicast vpn-instance information for a VPN instance. vpn-instance-name [ group-name group-name ] display bgp peer ipv6 [ unicast ] vpn-instance vpn-instance-name Display BGP peer information for a...
Page 459 Figure 112 Network diagram VPN 2 Site 1 PE 2 PE 1 GE1/0/1 Vlan-int30: 30::2/64 Vlan-int40: 40::2/64 PE 3 Vlan-int10 VPN 1 GE1/0/3 VPN 1 2001:1::2/64 Site 2 Vlan-int30: 30::1/64 2012:1::/64 GE1/0/1 Vlan-int11 Vlan-int40: 40::1/64 Vlan-int10 GE1/0/2 2012:1::2/64 VR 1 2001:1::1/64 Vlan-int20 2002:1::1/64...
Page 460 # Bind VLAN-interface 10 to VPN instance vpn1, and configure an IPv6 address for the VLAN interface. [MCE] interface vlan-interface 10 [MCE-Vlan-interface10] ip binding vpn-instance vpn1 [MCE-Vlan-interface10] ipv6 address 2001:1::1 64 [MCE-Vlan-interface10] quit # Configure VLAN 20, add port Ten-GigabitEthernet 1/0/2 to VLAN 20. [MCE] vlan 20 [MCE-vlan20] port ten-gigabitethernet 1/0/2 [MCE-vlan20] quit...
Page 461 <VR2> system-view [VR2] ripng 20 [VR2-ripng-20] quit [VR2] interface vlan-interface 20 [VR2-Vlan-interface20] ripng 20 enable [VR2-Vlan-interface20] quit [VR2] interface vlan-interface 21 [VR2-Vlan-interface21] ripng 20 enable [VR2-Vlan-interface21] quit # On the MCE, display the routing table of VPN instance vpn1. [MCE] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol...
Page 462 Interface : Vlan20 Cost Destination: 2002:1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012::/64 Protocol : RIPng NextHop : FE80::20C:29FF:FE40:701 Preference: 100 Interface : Vlan20 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0...
Page 463 # On PE 1, create VLAN 30 and VLAN-interface 30, bind VLAN-interface 30 to VPN instance vpn1, and configure an IPv6 address for the VLAN-interface 30. [PE1] vlan 30 [PE1-vlan30] quit [PE1] interface vlan-interface 30 [PE1-Vlan-interface30] ip binding vpn-instance vpn1 [PE1-Vlan-interface30] ipv6 address 30::2 64 [PE1-Vlan-interface30] quit # On PE 1, create VLAN 40 and VLAN-interface 40, bind VLAN-interface 40 to VPN instance...
Page 464 Interface : InLoop0 Cost Destination: 30::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan30 Cost Destination: 30::2/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012:1::/64 Protocol : OSPFv3 NextHop : FE80::202:FF:FE02:2 Preference: 150 Interface : Vlan30...
Page 465 NextHop : :: Preference: 0 Interface : NULL0 Cost The routing information for the two VPNs has been added into the routing tables on PE 1.
Page 466: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 467: Network Topology Icons
Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 468: Support And Other Resources
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
Page 469: Websites
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
Page 470 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Page 471 Index MPLS TE tunnel traffic direction (automatic route advertisement), VPLS BGP label block information advertisement, VPLS VSI+AC binding, AC (attachment circuit) VPLS BGP PE information advertisement, MPLS L2VPN attachment circuit (AC), affinity MPLS L2VPN attachment circuit (AC) MPLS TE tunnel constraints, configuration, aging MPLS L2VPN cross-connect+attachment...
Page 472 attribute MPLS L3VPN FRR IPv4 route backup (VPNv4 route), IPv6 MCE VPN instance route related attributes, MPLS L3VPN FRR VPNv4 route backup (IPv4 route), MCE VPN instance route related attributes, MPLS L3VPN FRR VPNv4 route backup (VPNv4 route), MPLS L3VPN BGP export target attribute, 157, 415 MPLS TE CRLSP backup, MPLS L3VPN BGP import target attribute,...
Page 473 MPLS L2VPN remote CCC connection, MPLS TE CSPF path calculation, MPLS L3VPN, carrier's carrier MPLS L3VPN basics, IPv6 MPLS L3VPN, MPLS L3VPN BGP AS number substitution, MPLS L3VPN, 165, 225 171, 192, 253 MPLS L3VPN Level 1 carrier, MPLS L3VPN BGP VPNv4 route control, MPLS L3VPN Level 2 carrier, MPLS L3VPN BGP-OSPF interaction, MPLS L3VPN carrier's carrier,...
Page 474 MPLS FEC, IPv6 MPLS L3VPN PE-CE IPv6 IS-IS, MPLS L2VPN PW, IPv6 MPLS L3VPN PE-CE OSPFv3, VPLS PW class configuration, IPv6 MPLS L3VPN PE-CE RIPng, configuring IPv6 MPLS L3VPN PE-CE static routing, exclusive tunnel, IPv6 MPLS L3VPN PE-PE routing, H-VPLS (MPLS access), IPv6 MPLS L3VPN VPN instance, H-VPLS UPE dual homing, IPv6 MPLS L3VPN VPN instance route related...
Page 475 MCE-VPN site routing, MPLS L3VPN inter-AS VPN option C routing policy, MCE-VPN site static routing, MPLS L3VPN loopback interface, MPLS basics, 1, 5 MPLS L3VPN nested VPN, 188, 233 MPLS L2VPN, 310, 315, 323 MPLS L3VPN OSPF sham link, 190, 249 MPLS L2VPN attachment circuit (AC), MPLS L3VPN PE-CE EBGP, MPLS L2VPN BGP label block information...
Page 476 MPLS TE link attribute advertisement (OSPF VPLS LDP PW (BGP auto-discovery), 365, 382 TE), VPLS MAC address learning, MPLS TE RSVP-TE RSVP resource VPLS PW, reservation style, VPLS PW class, MPLS TE traffic forwarding, VPLS static PW, 362, 370 MPLS TE tunnel (dynamic CRLSP), VPLS UPE dual homing, MPLS TE tunnel (static CRLSP), VPLS UPE dual homing (redundant LDP PWs),...
Page 477 MPLS TE FRR, 56, 74 LDP loop detection, MPLS TE FRR bypass tunnel on PLR, MPLS TE FRR node fault detection, MPLS TE FRR link protection, 56, 56 MPLS TE loop detection, MPLS TE FRR manual bypass tunnel, device MPLS TE FRR node fault detection, customer edge device.
Page 478 provider edge device. See dynamic static CRLSP configuration, MPLS LSP establishment, VPLS BGP PW configuration, MPLS OAM BFD session mode, VPLS configuration, MPLS TE CRLSP establishment, VPLS LDP PW configuration, MPLS TE tunnel configuration (dynamic CRLSP), VPLS LDP PW configuration (BGP auto-discovery), VPLS static PW configuration, EBGP...
Page 479 exclusive tunnel (MPLS), MPLS TE DS-TE, EXPLICIT_ROUTE object (RSVP-TE), MPLS TE make-before-break, exporting MPLS TE tunnel automatic bandwidth adjustment, IPv6 MPLS L3VPN VPN instance route related attributes, MPLS TE tunnel automatic route advertisement traffic direction (forwarding adjacency), MCE VPN instance route related attributes, MPLS TE tunnel reoptimization, MPLS L3VPN BGP export target attribute, preferred tunnel configuration,...
Page 480 RSVP configuration, IBGP RSVP GR, IPv6 MCE-PE IBGP, RSVP GR configuration, IPv6 MCE-VPN site IBGP, RSVP GR helper, IPv6 MPLS L3VPN PE/CE IBGP, RSVP GR restarter, MCE-PE IBGP configuration, MCE-VPN site IBGP, exclusive tunnel configuration, MPLS L3VPN PE-CE IBGP, preferred tunnel configuration, ICMP preferred tunnel+selection order, MPLS TTL-expired message send,...
Page 481 MPLS TE inter-AS tunnel establishment LDP session parameters, (RSVP-TE), LDP session protection, inter-AS VPN LDP session reset, IPv6 MPLS L3VPN, LDP SNMP notification, IPv6 MPLS L3VPN option A, 276, 286 LDP-IGP synchronization, 21, 31 IPv6 MPLS L3VPN option C, 276, 291 LDP-IS-IS synchronization, MPLS L3VPN, LDP-OSPF synchronization,...
Page 482 VPN instance configuration, routing information advertisement, VPN instance creation, VPN instance, VPN instance route related attributes, VPN instance creation, VPN instance+interface association, VPN instance route related attributes, IPv6 MPLS L3VPN VPN instance+interface association, basics, IS-IS BGP VPNv6 route control, LDP-IS-IS synchronization, carrier's carrier, MCE-PE IS-IS, configuration,...
Page 483 RSVP-TE LABEL_REQUEST object, MPLS L2VPN multi-segment PW configuration (inter-domain)(on router), RSVP-TE tunnel establishment, MPLS L2VPN multi-segment PW configuration static CRLSP configuration, 128, 129 (intra-domain)(on router), static LSP configuration, 11, 12 MPLS OAM BFD for VPLS LDP PW, switched path. Use nonstop routing (NSR), switching router.
Page 484 MPLS TE link attribute advertisement (IS-IS MPLS TE FRR manual bypass tunnel, TE), MPLS TE IETF DS-TE configuration, MPLS TE link attribute advertisement (OSPF MPLS TE inter-AS tunnel establishment TE), (RSVP-TE), local MPLS TE tunnel establishment (RSVP-TE), MPLS L2VPN connection configuration, MPLS TE tunnel establishment (static CRLSP), logging BGP route flapping logging,...
Page 485 LDP configuration, 15, 22, 34 RSVP Srefresh mechanism, LDP FEC label mapping, RSVP-TE message types, LDP GR, mode LDP label acceptance control, H-VPLS Ethernet access, LDP label advertisement control, H-VPLS MPLS access, LDP LSP configuration, LDP label advertisement downstream on demand (DoD), LDP message types, LDP label advertisement downstream unsolicited...
Page 486 LDP GR configuration, BGP PW creation, LDP hello parameters, BGP PW remote CCC connection, LDP label acceptance policy, configuration, 310, 315, 323 LDP label advertisement policy, cross-connect configuration, LDP label distribution control mode, cross-connect+attachment circuit (AC) binding, LDP loop detection, display, LDP LSP generation policy, enable,...
Page 487 FRR configuration (IPv4 route/VPNv4 route nested VPN routing information propagation, backup), networking scheme, FRR configuration (VPNv4 route/IPv4 route networking scheme (basic), backup), networking scheme (extranet), FRR configuration (VPNv4 route/route networking scheme (hub-spoke), backup), OSPF area PE-CE configuration, FRR IPv4 route backup (VPNv4 route), OSPF sham link, 171, 190 FRR VPNv4 route backup (IPv4 route),...
Page 488 tracert for LSP (periodic), FRR optimal bypass tunnel selection interval, MPLS QoS IETF DS-TE configuration, IPv6 MCE configuration, inter-AS tunnel establishment (RSVP-TE), IPv6 MPLS L3VPN, 266, 280 IPv6 MCE configuration, IPv6 MPLS L3VPN carrier's carrier, IPv6 MPLS L3VPN, 266, 280 IPv6 MPLS L3VPN configuration, 264, 280 IPv6 MPLS L3VPN carrier's carrier,...
Page 489 traffic forwarding, IPv6 MCE VPN instance route related attributes, traffic forwarding automatic route advertisement, IPv6 MCE VPN instance+interface association, traffic forwarding configuration, IPv6 MCE-PE EBGP, traffic forwarding static routing, IPv6 MCE-PE IBGP, troubleshoot, IPv6 MCE-PE IPv6 IS-IS, troubleshoot no TE LSA generated, IPv6 MCE-PE IPv6 static routing, tunnel automatic bandwidth adjustment, IPv6 MCE-PE OSPFv3,...
Page 490 IPv6 MPLS L3VPN VPN instance creation, MCE-VPN site IBGP, MCE-VPN site IS-IS, IPv6 MPLS L3VPN VPN instance route MCE-VPN site OSPF, related attributes, MCE-VPN site RIP, IPv6 MPLS L3VPN VPN instance+interface MCE-VPN site routing, association, MCE-VPN site static routing, LDP backoff, MPLS control plane, LDP enable, MPLS egress label type advertisement,...
Page 491 MPLS L3VPN FRR configuration (IPv4 MPLS L3VPN VPN instance route related route/VPNv4 route backup), attributes, MPLS L3VPN FRR configuration (VPNv4 MPLS L3VPN VPN instance+interface route/IPv4 route backup), association, MPLS L3VPN FRR configuration (VPNv4 MPLS L3VPN VPN-IPv4 address, 156, 414 route/route backup), MPLS LFIB, MPLS L3VPN HoVPN, 189, 242...
Page 492 MPLS TE tunnel interface, static LSP configuration, 11, 12 MPLS TE tunnel reoptimization, tunnel policy configuration, 150, 152 MPLS TE tunnel setup, VPLS architecture, MPLS TE tunnel with RSVP-TE, VPLS configuration, 355, 360, 370 MPLS TTL propagation, node MPLS TTL-expired message send, MPLS TE FRR node fault detection, preferred tunnel configuration, RSVP configuration,...
Page 493 MPLS TE attribute advertisement, IPv6 MCE-PE IBGP, MPLS TE link attribute advertisement (OSPF IPv6 MCE-PE IPv6 IS-IS, TE), IPv6 MCE-PE IPv6 static routing, OSPFv3 IPv6 MCE-PE OSPFv3, IPv6 MCE-PE OSPFv3, IPv6 MCE-PE RIPng, IPv6 MCE-VPN site OSPFv3, IPv6 MCE-PE routing, IPv6 MPLS L3VPN OSPFv3 sham link, IPv6 MCE-VPN site EBGP, IPv6 MPLS L3VPN PE-CE OSPFv3,...
Page 494 MPLS L3VPN Layer 1 label packet priority forwarding, MPLS TE tunnel holding priority, MPLS L3VPN MP-BGP, MPLS TE tunnel setup priority, MPLS L3VPN nested VPN, 167, 188 procedure MPLS L3VPN OSPF area PE-CE advertising MPLS TE link attribute (IGP TE configuration, extension), MPLS L3VPN OSPF sham link,...
Page 495 configuring IPv6 MPLS L3VPN inter-AS IPv6 configuring LDP session parameter (Basic VPN option C routing policy, Discovery), configuring IPv6 MPLS L3VPN inter-AS option configuring LDP session parameter (Extended Discovery), configuring IPv6 MPLS L3VPN inter-AS option configuring LDP session protection, configuring LDP-IGP synchronization, configuring IPv6 MPLS L3VPN IPv6 configuring LDP-IS-IS synchronization, MCE-VPN site routing,...
Page 496 configuring MPLS L2VPN PW, configuring MPLS L3VPN PE-CE IS-IS, configuring MPLS L2VPN PW class, configuring MPLS L3VPN PE-CE OSPF, configuring MPLS L2VPN PW redundancy, configuring MPLS L3VPN PE-CE RIP, configuring MPLS L3VPN PE-CE routing, configuring MPLS L2VPN remote CCC configuring MPLS L3VPN PE-CE static routing, connection, configuring MPLS L2VPN static PW, 317, 323...
Page 497 configuring MPLS TE link attribute configuring static CRLSP, 128, 129 advertisement (IS-IS TE), configuring static LSP, configuring MPLS TE link attribute configuring tunnel policy, advertisement (OSPF TE), configuring tunnel selection order, configuring MPLS TE RSVP-TE RSVP configuring VPLS, resource reservation style, configuring VPLS AC, configuring MPLS TE traffic forwarding, configuring VPLS BGP label block information...
Page 498 enabling LDP globally, protocols and standards enabling LDP on interface, IPv6 MPLS L3VPN, enabling LDP SNMP notification, LDP, enabling MPLS, MPLS, enabling MPLS forwarding statistics, MPLS L3VPN, enabling MPLS L2VPN, MPLS OAM, enabling MPLS L3VPN SNMP notification, MPLS TE, RSVP, enabling MPLS SNMP notifications, provider enabling MPLS TE,...
Page 499 MPLS OAM BFD for VPLS static PW, remote MPLS OAM for PW, MPLS L2VPN BGP PW remote CCC connection, MPLS OAM ping for PW, MPLS L2VPN remote CCC connection, static configuration, MPLS L2VPN remote connection configuration, VPLS architecture, VPLS BGP PW configuration, reoptimizing VPLS BGP PW creation, MPLS TE tunnel reoptimization,...
Page 500 MPLS L2VPN multi-segment PW IPv6 MPLS L3VPN OSPFv3 sham link, configuration (inter-domain), IPv6 MPLS L3VPN packet forwarding, MPLS L2VPN multi-segment PW IPv6 MPLS L3VPN PE/CE EBGP, configuration (intra-domain), IPv6 MPLS L3VPN PE/CE IBGP, MPLS L2VPN remote CCC connection, IPv6 MPLS L3VPN PE/CE routing, MPLS L2VPN static PW configuration, IPv6 MPLS L3VPN PE-CE IPv6 IS-IS, VPLS BGP PW configuration,...
Page 501 MPLS L3VPN FRR configuration (VPNv4 RSVP-TE tunnel establishment, route/route backup), RSVP MPLS L3VPN HoVPN, authentication, MPLS L3VPN hub-spoke network, authentication configuration, MPLS L3VPN inter-AS option A, BFD enable, MPLS L3VPN inter-AS option B, configuration, 135, 138, 143 MPLS L3VPN inter-AS option C, CRLSP setup, MPLS L3VPN inter-AS VPN option C routing display,...
Page 502 Russian Dolls Model. See MPLS L3VPN HoVPN, specifying scheme MPLS egress label type advertisement, IPv6 MPLS L3VPN network, MPLS L3VPN egress PE VPN label processing MPLS L3VPN networking, mode, MPLS L3VPN networking (basic), Srefresh MPLS L3VPN networking (extranet), RSVP Srefresh configuration, MPLS L3VPN networking (hub-spoke), static security...
Page 503 MCE OSPF VPN route advertisement, VPLS multicast traffic flooding, MPLS L2VPN LDP PW redundancy, VPLS unicast traffic flooding, 357, 357 switching traffic forwarding MPLS basics configuration, 1, 5 MPLS TE, MPLS L2VPN configuration, 310, 323 MPLS TE automatic route advertisement (forwarding adjacency), MPLS L2VPN network models, MPLS TE automatic route advertisement (IGP...
Page 504 MPLS TE IETF DS-TE configuration, VPLS UPE dual homing configuration (redundant LDP PWs), MPLS TE inter-AS tunnel establishment (RSVP-TE), VPLS UPE dual homing configuration (redundant static PWs), MPLS TE make-before-break, user-facing network provider edge. Use MPLS TE traffic forwarding, 53, 72 MPLS TE tunnel automatic bandwidth adjustment, VCCV...
Page 505 MPLS L2VPN LDP PW redundancy, VPLS MAC address withdrawal, MPLS L2VPN multi-segment PW configuration (inter-domain)(on router), MPLS L2VPN multi-segment PW configuration (intra-domain)(on router), MPLS L2VPN static PW configuration, MPLS OAM BFD for VPLS LDP PW, MPLS OAM BFD for VPLS static PW, multicast traffic flooding, multicast traffic forwarding, PW class configuration,...

HPE FlexNetwork 5510 HI Series Mpls Configuration Manual

Configuring Basic MPLS

Configuring a Static LSP

Configuring LDP

Configuring MPLS te

Configuring a Static CRLSP

Configuring RSVP

Configuring Tunnel Policies

Configuring MPLS L3VPN

Configuring Ipv6 MPLS L3VPN

Configuring MPLS L2VPN

Configuring VPLS

Configuring MPLS OAM

Quick Links

Related Manuals for HPE FlexNetwork 5510 HI Series

Summary of Contents for HPE FlexNetwork 5510 HI Series