Download Print this page

HPE FlexFabric 5950 Series Configuration Manual

HPE FlexFabric 5950 Series Configuration Manual

Mpls

Hide thumbs Also See for FlexFabric 5950 Series:

Command reference manual (363 pages)

,

Configuration manual (94 pages)

,

Installation manual (53 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual

HPE FlexFabric 5950 Switch Series

MPLS Configuration Guide

Part number: 5200-0827

Software version: Release 6106 and later

Document version: 6W100-20160513

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the FlexFabric 5950 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for HPE FlexFabric 5950 Series

Page 1 HPE FlexFabric 5950 Switch Series MPLS Configuration Guide Part number: 5200-0827 Software version: Release 6106 and later Document version: 6W100-20160513...
Page 2 © Copyright 2016 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 ···························································································································································· 5 Protocols and standards ···························································································································· 5 ...
Page 4 Configuring LDP-IGP synchronization ············································································································· 33 Configuring LDP-OSPF synchronization ·································································································· 34 Configuring LDP IS-IS synchronization ···································································································· 35 Setting a DSCP value for outgoing LDP packets ····························································································· 35 Resetting LDP sessions ··································································································································· 36 Enabling SNMP notifications for LDP ·············································································································· 36 ...
Page 5 Displaying and maintaining MPLS TE ·············································································································· 97 MPLS TE configuration examples ···················································································································· 98 Establishing an MPLS TE tunnel over a static CRLSP ············································································ 98 Establishing an MPLS TE tunnel with RSVP-TE ···················································································· 102 Establishing an inter-AS MPLS TE tunnel with RSVP-TE ······································································ 108 ...
Page 6 Inter-AS VPN ·········································································································································· 185 Carrier's carrier ······································································································································ 189 Nested VPN ··········································································································································· 191 HoVPN ··················································································································································· 192 OSPF VPN extension ····························································································································· 194 BGP AS number substitution and SoO attribute ···················································································· 196 MPLS L3VPN FRR ································································································································· 197 ...
Page 7 Configuring inter-AS IPv6 VPN option A ································································································ 311 Configuring inter-AS IPv6 VPN option C ································································································ 312 Configuring an OSPFv3 sham link ················································································································· 313 Configuring a loopback interface ············································································································ 313 Redistributing the loopback interface address ······················································································· 313 ...
Page 8 IPv6 MCE configuration task list ···················································································································· 390 C onfiguring VPN instances ···························································································································· 3 91 2 9 5 H 6 3 4 H C reating a VPN instance ························································································································ 3 91 2 9 6 H 6 3 5 H ...
Page 9: Configuring Basic Mpls
C onfiguring 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. Overview 1 4 B MPLS has the following features: •...
Page 10: Mpls Network Architecture
L SP 3 2 0 B 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 11: Lsp Establishment
Figure 3 MPLS network architecture L SP establishment 1 3 8 B LSPs include static and dynamic LSPs. • Static LSP—To establish a static LSP, you must configure an LFIB entry on each LSR along the LSP. Establishing static LSPs consumes fewer resources than establishing dynamic LSPs, but static LSPs cannot automatically adapt to network topology changes.
Page 12: Mpls Forwarding
Figure 4 Dynamic LSP establishment M PLS forwarding 1 3 9 B As shown in F igure 5, a packet is forwarded over the MPLS network as follows: 6 5 8 H Device B (the ingress LSR) receives a packet with no label. Then, it performs the following operations: a.
Page 13: Php
Figure 5 MPLS forwarding P HP 1 4 0 B An egress node must perform two forwarding table lookups to forward a packet: • Two LFIB lookups (if the packet has more than one label). • 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.
Page 14: Enabling Mpls
Tasks at a glance (Optional.) Setting MPLS MTU 6 6 0 H (Optional.) Specifying the label type advertised by egress 6 6 1 H (Optional.) Configuring TTL propagation 6 6 2 H (Optional.) Enabling sending MPLS TTL-expired messages 6 6 3 H (Optional.) Enabling MPLS forwarding statistics 6 6 4 H...
Page 15: Specifying The Label Type Advertised By Egress
To set an MPLS MTU for an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set an MPLS MTU for the By default, no MPLS MTU is set mpls mtu size interface. on an interface. The following applies when an interface handles MPLS packets: •...
Page 16: Configuring Ttl Propagation
C onfiguration procedure 3 2 4 B To specify the type of label that the egress node will advertise to the penultimate hop: Step Command Remarks Enter system view. system-view Specify the label type mpls label advertise By default, an egress node advertised by the egress { explicit-null | implicit-null | advertises an implicit null label to...
Page 17: Enabling Sending Mpls Ttl-Expired Messages
• As a best practice, set the same TTL processing mode on all LSRs of an LSP. • To enable TTL propagation for a VPN, you must enable it on all PE devices in the VPN. Then, you can get the same traceroute result (hop count) from those PEs. To enable TTL propagation: Step Command...
Page 18: Enabling Split Horizon For Mpls Forwarding
Enabling split horizon for MPLS forwarding 2 2 B This feature prevents MPLS packets received from an interface from being forwarded back to that interface to provide loop-free forwarding. To enable split horizon for MPLS forwarding: Step Command Remarks Enter system view. system-view Enable split horizon for By default, split horizon is...
Page 19 Task Command Display NHLFE entries. display mpls forwarding nhlfe [ nid ] [ slot slot-number ] reset mpls statistics { all | [ vpn-instance vpn-instance-name ] { ipv4 ipv4-address mask-length | Clear MPLS forwarding statistics for the specified LSPs. ipv6 ipv6-address prefix-length } | static | te ingress-lsr-id tunnel-id }...
Page 20: Configuring A Static Lsp
C onfiguring a static LSP Overview 2 5 B 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: Configuration Procedure
• If you want to associate the static LSP with an LDP LSP, make sure the egress node of the static LSP has a route to the destination. Configuration procedure 2 8 B To configure a static LSP: Step Command Remarks Enter system view.
Page 22: Configuration Restrictions And Guidelines
Figure 8 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 C onfiguration restrictions and guidelines 1 4 3 B • For an LSP, the outgoing label specified on an LSR must be identical with the incoming label specified on the downstream LSR.
Page 23: Verifying The Configuration
# Configure Switch C. [SwitchC] mpls lsr-id 3.3.3.9 [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable [SwitchC-Vlan-interface3] quit Configure a static LSP from Switch A to Switch C: # Configure the LSP ingress node, Switch A. [SwitchA] static-lsp ingress AtoC destination 21.1.1.0 24 nexthop 10.1.1.2 out-label # Configure the LSP transit node, Switch B.
Page 24 100 bytes from 10.1.1.1: Sequence=3 time=1 ms 100 bytes from 10.1.1.1: Sequence=4 time=1 ms 100 bytes from 10.1.1.1: Sequence=5 time=1 ms --- FEC: 11.1.1.0/24 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max = 1/1/5 ms...
Page 25: Configuring Ldp
C onfiguring LDP Overview 3 1 B The Label Distribution Protocol (LDP) dynamically distributes FEC-label mapping information between LSRs to establish LSPs. T erminology 1 4 6 B L DP session 3 2 5 B Two LSRs establish a TCP-based LDP session to exchange FEC-label mappings. L DP peer 3 2 6 B Two LSRs that use LDP to exchange FEC-label mappings are LSR peers.
Page 26: 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. L DP operation 1 4 8 B LDP can operate on an IPv4 or IPv6 network, or a network where IPv4 coexists with IPv6.
Page 27: Label Distribution And Control
to create an LFIB entry for that FEC. When all LSRs (from the Ingress to the Egress) establish an LFIB entry for the FEC, an LSP is established exclusively for the FEC. Figure 9 Dynamically establishing an LSP L abel distribution and control 1 4 9 B L abel advertisement modes 3 3 2 B...
Page 28: Ldp Gr
L abel distribution control 3 3 3 B 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 29 As shown in F igure 12, GR defines the following roles: 6 7 2 H • GR restarter—An LSR that performs GR. It must be GR-capable. • GR helper—A neighbor LSR that helps the GR restarter to complete GR. The device can act as a GR restarter or a GR helper. Figure 12 LDP GR As shown in F igure...
Page 30: Ldp-Igp Synchronization
Figure 13 LDP GR operation GR restarter GR helper Set up an LDP session, and identify that they are LDP GR capable Protocol restarts Re-establish the LDP session Reconnect time MPLS forwarding state Send label mappings holding time LDP recovery time L DP-IGP synchronization 1 5 1 B B asic operating mechanism...
Page 31: Ldp Over Mpls Te
N otification delay for LDP restart or active/standby switchover 3 3 7 B When an LDP restart or an active/standby switchover occurs, LDP takes time to converge, and LDP notifies IGP of the LDP-IGP synchronization status as follows: • If a notification delay is not configured, LDP immediately notifies IGP of the current synchronization states during convergence, and then updates the states after LDP convergence.
Page 32: Enabling Ldp
Tasks at a glance (Optional.) Configuring Hello parameters 6 7 8 H (Optional.) Configuring LDP session parameters 6 7 9 H (Optional.) Configuring LDP backoff 6 8 0 H (Optional.) Configuring LDP MD5 authentication 6 8 1 H (Optional.) Configuring LDP to redistribute BGP unicast routes 6 8 2 H (Optional.) Configuring an LSP generation policy...
Page 33: Enabling Ldp On An Interface
E nabling LDP on an interface 1 5 5 B Step Command Remarks Enter system view. system-view If the interface is bound to a VPN instance, you must enable LDP interface interface-type Enter interface view. for the VPN instance by using interface-number the vpn-instance command in LDP view.
Page 34: Configuring Ldp Session Parameters
Configuring LDP session parameters 3 5 B This task configures the following LDP session parameters: • Keepalive hold time and Keepalive interval. • LDP transport address—IP address for establishing TCP connections. LDP uses Basic Discovery and Extended Discovery mechanisms to discovery LDP peers and establish LDP sessions with them.
Page 35: Configuring Ldp Backoff
Step Command Remarks device will send unsolicited send IPv4 Targeted Hellos to IPv4 Targeted Hellos to the any peers, or respond to IPv4 peer and can respond to IPv4 Targeted Hellos received from Targeted Hellos received from any peers. the targeted peer. mpls ldp timer keepalive-hold By default, the Keepalive hold Set the Keepalive hold time.
Page 36: Configuring Ldp Md5 Authentication
Step Command Remarks view: a. mpls ldp b. vpn-instance vpn-instance-name By default, the initial delay time is Set the initial delay time and backoff initial initial-time 15 seconds, and the maximum maximum delay time. maximum maximum-time delay time is 120 seconds. Configuring LDP MD5 authentication 3 7 B To improve security for LDP sessions, you can configure MD5 authentication for the underlying TCP...
Page 37: Configuring An Lsp Generation Policy
Step Command Remarks • Enter LDP-VPN instance view: a. mpls ldp b. vpn-instance vpn-instance-name By default, LDP does not Enable LDP to redistribute import bgp [ as-number ] redistribute BGP IPv4 unicast BGP IPv4 unicast routes. routes. By default, LDP does not Enable LDP to redistribute ipv6 import bgp [ as-number ] redistribute BGP IPv6 unicast...
Page 38: Configuring The Ldp Label Distribution Control Mode
Configuring the LDP label distribution control 4 0 B mode Step Command Remarks Enter system view. system-view • Enter LDP view: mpls ldp • Enter LDP view or enter Enter LDP-VPN instance view: LDP-VPN instance a. mpls ldp view. b. vpn-instance vpn-instance-name Configure the label label-distribution { independent |...
Page 39: Configuring A Label Acceptance Policy
Step Command Remarks • Enter LDP view: mpls ldp • Enter LDP view or enter Enter LDP-VPN instance view: LDP-VPN instance a. mpls ldp view. b. vpn-instance vpn-instance-name By default, LDP advertises all advertise-label prefix-list Configure an IPv4 label IPv4 FEC-label mappings prefix-list-name [ peer advertisement policy.
Page 40: Configuring Ldp Loop Detection
Step Command Remarks b. vpn-instance vpn-instance-name Configure an IPv4 label accept-label peer peer-lsr-id prefix-list By default, LDP accepts all IPv4 acceptance policy. prefix-list-name FEC-label mappings. Configure an IPv6 label ipv6 accept-label peer peer-lsr-id By default, LDP accepts all IPv6 acceptance policy. prefix-list prefix-list-name FEC-label mappings.
Page 41: Configuring Ldp Session Protection
Configuring LDP session protection 4 4 B If two LDP peers have both a direct link and an indirect link in between, you can configure this feature to protect their LDP session when the direct link fails. LDP establishes both a Link Hello adjacency over the direct link and a Targeted Hello adjacency over the indirect link with the peer.
Page 42: Configuring Ldp-Ospf Synchronization
You can execute the mpls ldp igp sync disable command to disable LDP-IGP synchronization on interfaces where LDP-IGP synchronization is not required. LDP-IGP synchronization protection is only applicable to an IPv4 network. C onfiguring LDP-OSPF synchronization 1 5 6 B LDP-IGP synchronization is not supported for an OSPF process and its OSPF areas if the OSPF process belongs to a VPN instance.
Page 43: Configuring Ldp Is-Is Synchronization
Step Command Remarks Return to system view. quit Enter LDP view. mpls ldp 10. (Optional.) Set the delay for By default, LDP immediately LDP to notify IGP of the LDP igp sync delay time notifies IGP of the LDP convergence. convergence completion.
Page 44: Resetting Ldp Sessions
Step Command Remarks Enter system view. system-view Enter LDP view. mpls ldp Set a DSCP value for outgoing By default, the DSCP value for dscp dscp-value LDP packets. outgoing LDP packets is 48. Resetting LDP sessions 4 8 B Changes to LDP session parameters take effect only on new LDP sessions. To apply the changes to an existing LDP session, you must reset all LDP sessions by executing the reset mpls ldp command.
Page 45: Ipv4 Ldp Configuration Examples
Task Command display mpls ldp interface [ vpn-instance vpn-instance-name ] Display LDP interface information. [ interface-type interface-number ] [ ipv6 ] display mpls ldp lsp [ vpn-instance vpn-instance-name ] Display LDP LSP information. [ ipv4-address mask-length | ipv6-address prefix-length | ipv6 ] Display LDP running parameters.
Page 46 [SwitchA-ospf-1] area 0 [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] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 11.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0 [SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C.
Page 47 224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24 Direct 0.0.0.0 NULL0 255.255.255.255/32 Direct 127.0.0.1 InLoop0 Enable MPLS and IPv4 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 # Configure Switch B.
Page 48 [SwitchB] ip prefix-list switchb index 40 permit 11.1.1.0 24 [SwitchB] ip prefix-list switchb index 50 permit 21.1.1.0 24 [SwitchB] mpls ldp [SwitchB-ldp] lsp-trigger prefix-list switchb [SwitchB-ldp] quit # On Switch C, create IP prefix list switchc, and configure LDP to use only the routes permitted by the prefix list to establish LSPs.
Page 49: Label Acceptance Control Configuration Example
100 bytes from 10.1.1.1: Sequence=1 time=1 ms 100 bytes from 10.1.1.1: Sequence=2 time=1 ms 100 bytes from 10.1.1.1: Sequence=3 time=1 ms 100 bytes from 10.1.1.1: Sequence=4 time=1 ms 100 bytes from 10.1.1.1: Sequence=5 time=1 ms --- FEC: 11.1.1.0/24 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max = 1/1/1 ms L abel acceptance control configuration example...
Page 50 C onfiguration procedure 3 4 9 B Before configuration, disable the spanning tree feature globally or map each VLAN to an MSTI. For more information, see Layer 2—LAN Switching Configuration Guide. Configure IP addresses and masks for interfaces, including the loopback interfaces, as shown F igure 18.
Page 51 [SwitchD] mpls lsr-id 4.4.4.9 [SwitchD] mpls ldp [SwitchD-ldp] quit [SwitchD] interface vlan-interface 6 [SwitchD-Vlan-interface6] mpls enable [SwitchD-Vlan-interface6] mpls ldp enable [SwitchD-Vlan-interface6] quit [SwitchD] interface vlan-interface 7 [SwitchD-Vlan-interface7] mpls enable [SwitchD-Vlan-interface7] mpls ldp enable [SwitchD-Vlan-interface7] quit Configure IPv4 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 52 [SwitchA] mpls ldp [SwitchA-ldp] accept-label peer 2.2.2.9 prefix-list prefix-from-b [SwitchA-ldp] accept-label peer 4.4.4.9 prefix-list prefix-from-d [SwitchA-ldp] quit # On Switch C, create IP prefix list prefix-from-b to permit subnet 11.1.1.0/24. Switch C uses this list to filter FEC-label mappings received from Switch B. [SwitchC] ip prefix-list prefix-from-b index 10 permit 11.1.1.0 24 # On Switch C, create IP prefix list prefix-from-d to deny subnet 11.1.1.0/24.
Page 53: Label Advertisement Control Configuration Example
100 bytes from 10.1.1.1: Sequence=3 time=1 ms 100 bytes from 10.1.1.1: Sequence=4 time=1 ms 100 bytes from 10.1.1.1: Sequence=5 time=1 ms --- FEC: 11.1.1.0/24 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max = 1/1/1 ms L abel advertisement control configuration example 1 6 0 B N etwork requirements...
Page 54 C onfiguration procedure 3 5 3 B Before configuration, disable the spanning tree feature globally or map each VLAN to an MSTI. For more information, see Layer 2—LAN Switching Configuration Guide. Configure IP addresses and masks for interfaces, including the loopback interfaces, as shown F igure 19.
Page 55 [SwitchD] mpls lsr-id 4.4.4.9 [SwitchD] mpls ldp [SwitchD-ldp] quit [SwitchD] interface vlan-interface 6 [SwitchD-Vlan-interface6] mpls enable [SwitchD-Vlan-interface6] mpls ldp enable [SwitchD-Vlan-interface6] quit [SwitchD] interface vlan-interface 7 [SwitchD-Vlan-interface7] mpls enable [SwitchD-Vlan-interface7] mpls ldp enable [SwitchD-Vlan-interface7] quit Configure IPv4 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 56 [SwitchA] mpls ldp [SwitchA-ldp] advertise-label prefix-list prefix-to-b peer peer-b [SwitchA-ldp] quit # On Switch C, create IP prefix list prefix-to-b to permit subnet 21.1.1.0/24. Switch C uses this list to filter FEC-label mappings advertised to Switch B. [SwitchC] ip prefix-list prefix-to-b index 10 permit 21.1.1.0 24 # On Switch C, create IP prefix list peer-b to permit 2.2.2.9/32.
Page 57 FECs: 2 Ingress: 2 Transit: 2 Egress: 0 In/Out Label Nexthop OutInterface 11.1.1.0/24 -/1277 10.1.1.1 Vlan-int2 1277/1277 10.1.1.1 Vlan-int2 21.1.1.0/24 -/1149 20.1.1.2 Vlan-int3 1276/1149 20.1.1.2 Vlan-int3 [SwitchC] display mpls ldp lsp Status Flags: * - stale, L - liberal, B - backup FECs: 2 Ingress: 1 Transit: 1...
Page 58: Ipv6 Ldp Configuration Examples
100 bytes from 10.1.1.1: Sequence=5 time=1 ms --- FEC: 11.1.1.0/24 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max = 1/1/1 ms IPv6 LDP configuration examples 5 2 B I Pv6 LDP LSP configuration example 1 6 1 B N etwork requirements 3 5 5 B...
Page 59 [SwitchA-LoopBack0] ospfv3 1 area 0.0.0.0 [SwitchA-LoopBack0] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ospfv3 1 area 0.0.0.0 [SwitchA-Vlan-interface2] quit [SwitchA] interface vlan-interface 4 [SwitchA-Vlan-interface4] ospfv3 1 area 0.0.0.0 [SwitchA-Vlan-interface4] quit # Configure Switch B. <SwitchB> system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.9 [SwitchB-ospfv3-1] area 0 [SwitchB-ospfv3-1-area-0.0.0.0] quit [SwitchB-ospfv3-1] quit...
Page 60 Destination: 10::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan2 Cost Destination: 10::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 11::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan4 Cost Destination: 11::1/128 Protocol...
Page 61 [SwitchA-ldp] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] mpls enable [SwitchA-Vlan-interface2] mpls ldp ipv6 enable [SwitchA-Vlan-interface2] mpls ldp transport-address 10::1 [SwitchA-Vlan-interface2] quit # Configure Switch B. [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 ipv6 enable [SwitchB-Vlan-interface2] mpls ldp transport-address 10::2 [SwitchB-Vlan-interface2] quit...
Page 62 [SwitchB-ldp] ipv6 lsp-trigger prefix-list switchb [SwitchB-ldp] quit # On Switch C, create IPv6 prefix list switchc, and configure LDP to use only the routes permitted by the prefix list to establish IPv6 LSPs. [SwitchC] ipv6 prefix-list switchc index 10 permit 100::1 128 [SwitchC] ipv6 prefix-list switchc index 20 permit 100::2 128 [SwitchC] ipv6 prefix-list switchc index 30 permit 100::3 128 [SwitchC] ipv6 prefix-list switchc index 40 permit 11::0 64...
Page 63: Ipv6 Label Acceptance Control Configuration Example
[SwitchA] ping ipv6 -a 11::1 21::1 Ping6(56 data bytes) 11::1 --> 21::1, press CTRL_C to break 56 bytes from 21::1, icmp_seq=0 hlim=63 time=2.000 ms 56 bytes from 21::1, icmp_seq=1 hlim=63 time=1.000 ms 56 bytes from 21::1, icmp_seq=2 hlim=63 time=3.000 ms 56 bytes from 21::1, icmp_seq=3 hlim=63 time=3.000 ms 56 bytes from 21::1, icmp_seq=4 hlim=63 time=2.000 ms --- Ping6 statistics for 21::1 ---...
Page 64 Figure 21 Network diagram Loop0 2.2.2.9/32 100::2/128 Vlan-int2 Vlan-int3 Loop0 Loop0 10::2/64 20::1/64 1.1.1.9/32 3.3.3.9/32 Switch B 100::1/128 100::3/128 Vlan-int3 Vlan-int2 20::2/64 10::1/64 Vlan-int7 Vlan-int4 Vlan-int6 Vlan-int5 Loop0 40::2/64 11::1/64 30::1/64 21::1/64 4.4.4.9/32 Switch A Switch C 100::4/128 Vlan-int6 Vlan-int7 30::2/64 40::1/64 Switch D...
Page 65 [SwitchA] interface vlan-interface 6 [SwitchA-Vlan-interface6] mpls enable [SwitchA-Vlan-interface6] mpls ldp ipv6 enable [SwitchA-Vlan-interface6] mpls ldp transport-address 30::1 [SwitchA-Vlan-interface6] quit # 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 ipv6 enable [SwitchB-Vlan-interface2] mpls ldp transport-address 10::2 [SwitchB-Vlan-interface2] quit...
Page 66 [SwitchD-Vlan-interface7] mpls ldp transport-address 40::1 [SwitchD-Vlan-interface7] quit Configure IPv6 LSP generation policies: # On Switch A, create IPv6 prefix list switcha, and configure LDP to use only the routes permitted by the prefix list to establish IPv6 LSPs. [SwitchA] ipv6 prefix-list switcha index 10 permit 11::0 64 [SwitchA] ipv6 prefix-list switcha index 20 permit 21::0 64 [SwitchA] mpls ldp [SwitchA-ldp] ipv6 lsp-trigger prefix-list switcha...
Page 67 [SwitchC] ipv6 prefix-list prefix-from-d index 10 deny 11::0 64 # On Switch C, configure IPv6 label acceptance policies to filter FEC-label mappings received from Switch B and Switch D. [SwitchC] mpls ldp [SwitchC-ldp] ipv6 accept-label peer 2.2.2.9 prefix-list prefix-from-b [SwitchC-ldp] ipv6 accept-label peer 4.4.4.9 prefix-list prefix-from-d [SwitchC-ldp] quit V erifying the configuration 3 6 2 B...
Page 68: Ipv6 Label Advertisement Control Configuration Example
round-trip min/avg/max/std-dev = 1.000/1.400/2.000/0.490 ms I Pv6 label advertisement control configuration example 1 6 3 B N etwork requirements 3 6 3 B Two links, Switch A—Switch B—Switch C and Switch A—Switch D—Switch C, exist between subnets 11::0/64 and 21::0/64. Configure LDP to establish LSPs only for routes to subnets 11::0/64 and 21::0/64.
Page 69 Enable MPLS and IPv6 LDP: # Configure Switch A. <SwitchA> system-view [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 ipv6 enable [SwitchA-Vlan-interface2] mpls ldp transport-address 10::1 [SwitchA-Vlan-interface2] quit [SwitchA] interface vlan-interface 6 [SwitchA-Vlan-interface6] mpls enable [SwitchA-Vlan-interface6] mpls ldp ipv6 enable [SwitchA-Vlan-interface6] mpls ldp transport-address 30::1...
Page 70 [SwitchD] mpls lsr-id 4.4.4.9 [SwitchD] mpls ldp [SwitchD-ldp] quit [SwitchD] interface vlan-interface 6 [SwitchD-Vlan-interface6] mpls enable [SwitchD-Vlan-interface6] mpls ldp ipv6 enable [SwitchD-Vlan-interface6] mpls ldp transport-address 30::2 [SwitchD-Vlan-interface6] quit [SwitchD] interface vlan-interface 7 [SwitchD-Vlan-interface7] mpls enable [SwitchD-Vlan-interface7] mpls ldp ipv6 enable [SwitchD-Vlan-interface7] mpls ldp transport-address 40::1 [SwitchD-Vlan-interface7] quit Configure IPv6 LSP generation policies:...
Page 71 # On Switch A, configure an IPv6 label advertisement policy to advertise only the label mapping for FEC 11::0/64 to Switch B. [SwitchA] mpls ldp [SwitchA-ldp] ipv6 advertise-label prefix-list prefix-to-b peer peer-b [SwitchA-ldp] quit # On Switch C, create IPv6 prefix list prefix-to-b to permit subnet 21::0/64. Switch C uses this list to filter FEC-label mappings advertised to Switch B.
Page 72 Nexthop FEC: 21::/64 In/Out Label: -/2416 OutInterface : Vlan2 Nexthop : FE80::20C:29FF:FE9D:EAC0 In/Out Label: 2415/2416 OutInterface : Vlan2 Nexthop : FE80::20C:29FF:FE9D:EAC0 [SwitchB] display mpls ldp lsp ipv6 Status Flags: * - stale, L - liberal, B - backup FECs: 2 Ingress: 2 Transit: 2 Egress: 0...
Page 73 In/Out Label: 1097/- OutInterface : - Nexthop The output shows that Switch A and Switch C have received FEC-label mappings only from Switch B. Switch B has received FEC-label mappings from both Switch A and Switch C. Switch D does not receive FEC-label mappings from Switch A or Switch C.
Page 74: Configuring Mpls Te
C onfiguring MPLS TE Overview 5 3 B T E and MPLS TE 1 6 4 B 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 75 A label distribution protocol (such as RSVP-TE) advertises labels to establish CRLSPs and reserves bandwidth resources on each node along the calculated path. Dynamic CRLSPs adapt to network changes and support CRLSP backup and fast reroute, but they require complicated configurations. A dvertising TE attributes 3 6 7 B MPLS TE uses extended link state IGPs, such as OSPF and IS-IS, to advertise TE attributes for...
Page 76: Crlsp Establishment Using Pce Path Calculation
Explicit path specifies the nodes to pass and the nodes to not pass for a tunnel. Explicit paths include the following types: Strict explicit path—Among the nodes that the path must traverse, a node and its previous hop must be directly connected. Strict explicit path precisely specifies the path that an MPLS TE tunnel must traverse.
Page 77: Traffic Forwarding
PCE 1 uses the local and received path information to select an end-to-end path for the PCC to reach the CRLSP destination, and sends the path to PCC as a reply. PCC uses the path calculated by PCEs to establish the CRLSP through RSVP-TE. Figure 23 BRPC path calculation T raffic forwarding 1 6 9 B...
Page 78: Make-Before-Break
Figure 24 IGP shortcut and forwarding adjacency diagram M ake-before-break 1 7 0 B Make-before-break is a mechanism to change an MPLS TE tunnel with minimum data loss and without using extra bandwidth. In case of tunnel reoptimization, traffic forwarding is interrupted if the existing CRLSP is removed before a new CRLSP is established.
Page 79: Route Pinning
Figure 25 Diagram for make-before-break R oute pinning 1 7 1 B Route pinning enables CRLSPs to always use the original optimal path even if a new optimal route has been learned. On a network where route changes frequently occur, you can use route pinning to avoid re-establishing CRLSPs upon route changes.
Page 80: Diffserv-Aware Te
• Bypass tunnel—An MPLS TE tunnel used to protect a link or node of the primary CRLSP. • Point of local repair—A PLR is the ingress node of the bypass tunnel. It must be located on the primary CRLSP but must not be the egress node of the primary CRLSP. •...
Page 81 • IETF mode—Complies with RFC 4124, RFC 4125, and RFC 4127. B asic concepts 3 7 6 B • CT—Class Type. DS-TE allocates link bandwidth, implements constraint-based routing, and performs admission control on a per-class type basis. A given traffic flow belongs to the same CT on all links.
Page 82: Bidirectional Mpls Te Tunnel
Figure 28 RDM bandwidth constraints model In MAM model, a BC constrains the bandwidth for only one CT. This ensures bandwidth isolation among CTs no matter whether preemption is used or not. Compared with RDM, MAM is easier to configure. MAM is suitable for networks where traffic of each CT is stable and no traffic bursts occur.
Page 83: Protocols And Standards
direction is established. The CRLSPs of a bidirectional MPLS TE tunnel established in co-routed mode use the same path. • Associated mode—In this mode, you establish a bidirectional MPLS TE tunnel by binding two unidirectional CRLSPs in opposite directions. The two CRLSPs can be established in different modes and use different paths.
Page 84 To configure an MPLS TE tunnel to use a CRLSP dynamically established by RSVP-TE, perform the following tasks: Enable MPLS TE and RSVP on each node and interface that the MPLS TE tunnel traverses. For information about enabling RSVP, see " C onfiguring RSVP."...
Page 85: Enabling Mpls Te
Tasks at a glance (Optional.) Configuring a bidirectional MPLS TE tunnel 7 2 5 H (Optional.) Configuring CRLSP backup 7 2 6 H Only MPLS TE tunnels established by RSVP-TE support this configuration. (Optional.) Configuring MPLS TE FRR 7 2 7 H Only MPLS TE tunnels established by RSVP-TE support this configuration.
Page 86: Configuring Ds-Te
Configuring DS-TE 5 7 B DS-TE is configurable on any node that an MPLS TE tunnel traverses. 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.
Page 87: Configuring An Mpls Te Tunnel To Use A Dynamic Crlsp
Step Command Remarks Enter MPLS TE tunnel interface tunnel tunnel-number Execute this command on the interface view. [ mode mpls-te ] ingress node. Specify the MPLS TE tunnel By default, MPLS TE uses establishment mode as mpls te signaling static RSVP-TE to establish a tunnel.
Page 88: Advertising Link Te Attributes By Using Igp Te Extension
Step Command Remarks Enter interface view. interface interface-type interface-number Set the maximum link By default, the maximum link mpls te max-link-bandwidth bandwidth for MPLS TE bandwidth for MPLS TE bandwidth-value 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...
Page 89: Configuring Mpls Te Tunnel Constraints
Step Command Remarks Command Reference. Enter area view. area area-id Enable MPLS TE for the By default, MPLS TE is disabled for mpls te enable OSPF area. an OSPF area. C onfiguring IS-IS TE 3 7 9 B 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 90 C onfiguring the affinity attribute for an MPLS TE tunnel 3 8 1 B 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.
Page 91: Establishing An Mpls Te Tunnel By Using Rsvp-Te
Step Command Remarks node. Return to system view. quit Enter MPLS TE 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 calculated path to establish a...
Page 92 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 93: Controlling Mpls Te Tunnel Setup
Step Command Remarks Enter MPLS TE tunnel interface tunnel tunnel-number interface view. [ mode mpls-te ] mpls te reoptimization [ frequency By default, tunnel Enable tunnel reoptimization. seconds ] reoptimization is disabled. Return to user view. return (Optional.) Immediately reoptimize all MPLS TE tunnels that are enabled with mpls te reoptimization the tunnel reoptimization...
Page 94 To enable route and label recording: Step Command Remarks Enter system view. system-view Enter MPLS TE tunnel interface tunnel tunnel-number [ mode interface view. mpls-te ] • To record routes: By default, both route mpls te record-route Record routes or record recording and label •...
Page 95: Configuring An Mpls Te Tunnel To Use A Crlsp Calculated By Pces
Step Command Remarks In current MPLS TE applications, tunnels are established usually by using the make-before-break mechanism. As a best practice, use the SE style. Configuring an MPLS TE tunnel to use a CRLSP 6 0 B calculated by PCEs C onfiguring a PCE 1 8 5 B Step...
Page 96: Establishing A Backup Crlsp By Using The Path Calculated By Pces
Step Command Remarks PCEP sessions to the specified PCEs. If you do not specify a PCE, the local device establishes PCEP sessions to all discovered PCEs. E stablishing a backup CRLSP by using the path calculated 1 8 8 B by PCEs Perform this task to enable the specified PCEs to calculate a backup CRLSP for the PCC.
Page 97: Configuring Traffic Forwarding
Configuring traffic forwarding 6 1 B Perform the tasks in this section on the ingress node of the MPLS TE tunnel. C onfiguring static routing to direct traffic to an MPLS TE 1 9 0 B tunnel Step Command Remarks Enter system view.
Page 98: Configuring A Bidirectional Mpls Te Tunnel
Step Command Remarks 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. relative value } metric. C onfiguring forwarding adjacency 3 9 5 B To use forwarding adjacency, you must establish two MPLS TE tunnels in opposite directions between two nodes, and configure forwarding adjacency on both the nodes.
Page 99: Configuring Crlsp Backup
Step Command Remarks passive reverse-lsp lsr-id bidirectional MPLS TE tunnel disabled on the tunnel interface, and specify the local end as ingress-lsr-id tunnel-id tunnel-id and tunnels established on the the passive end of the tunnel. tunnel interface are unidirectional MPLS TE tunnels. To configure an associated bidirectional MPLS TE tunnel: Step Command...
Page 100: Configuring A Bypass Tunnel On The Plr
To enable FRR: Step Command Remarks Enter system view. system-view Enter tunnel interface view of interface tunnel tunnel-number the primary CRLSP. [ mode mpls-te ] By default, FRR is disabled. mpls te fast-reroute If you specify the bandwidth Enable FRR. [ bandwidth ] keyword, the primary CRLSP must have bandwidth protection.
Page 101 Primary Bandwidt CRLSP h required requires Bypass tunnel providing Bypass tunnel providing no bandwidth bandwidth protection bandwidth protection primary protection or CRLSP does not carry the bandwidth protection flag. The bypass tunnel does not provide bandwidth protection for the primary CRLSP, and performs best-effort forwarding for traffic of the primary CRLSP.
Page 102 Primary Bandwidt CRLSP h required requires Bypass tunnel providing Bypass tunnel providing no bandwidth bandwidth protection bandwidth protection primary protection or CRLSP primary CRLSP. C onfiguration restrictions and guidelines 3 9 7 B When you configure a bypass tunnel on the PLR, follow these restrictions and guidelines: •...
Page 103 Step Command Remarks Enter interface view of the interface interface-type output interface of a primary interface-number CRLSP. mpls te fast-reroute Specify a bypass tunnel for By default, no bypass tunnel is bypass-tunnel tunnel the protected interface. specified for an interface. tunnel-number A utomatically setting up bypass tunnels 3 9 9 B...
Page 104: Configuring Node Fault Detection
C onfiguring node fault detection 1 9 4 B 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 105: Displaying And Maintaining Mpls Te
Step Command Remarks Enter system view. system-view Enable SNMP By default, SNMP notifications for snmp-agent trap enable te notifications for MPLS TE. MPLS TE are enabled. Displaying and maintaining MPLS TE 6 6 B Execute display commands in any view and reset commands in user view. Task Command Display information about explicit paths.
Page 106: Mpls Te Configuration Examples
MPLS TE configuration examples 6 7 B E stablishing an MPLS TE tunnel over a static CRLSP 1 9 6 B N etwork requirements 4 0 0 B Switch A, Switch B, and Switch C run IS-IS. Establish an MPLS TE tunnel over a static CRLSP from Switch A to Switch C to transmit data between the two IP networks.
Page 107 [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] isis enable 1 [SwitchB-Vlan-interface2] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] isis enable 1 [SwitchB-LoopBack0] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [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...
Page 108 [SwitchC-Vlan-interface2] mpls te enable [SwitchC-Vlan-interface2] quit Configure MPLS TE attributes of links: # Set 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 [SwitchA-Vlan-interface1] quit # Set the maximum link bandwidth and maximum reservable bandwidth on Switch B.
Page 109 Configure a static route on Switch A to direct traffic destined for subnet 100.1.2.0/24 to MPLS TE tunnel 0. [SwitchA] ip route-static 100.1.2.0 24 tunnel 0 preference 1 V erifying the configuration 4 0 2 B # Verify that the tunnel interface is up on Switch A. [SwitchA] display interface tunnel Tunnel0 Current state: UP...
Page 110: Establishing An Mpls Te Tunnel With Rsvp-Te
Bypass Tunnel Auto Created Route Pinning Retry Limit Retry Interval : 2 sec Reoptimization Reoptimization Freq Backup Type Backup LSP ID Auto Bandwidth Auto Bandwidth Freq Min Bandwidth Max Bandwidth Collected Bandwidth # Display static CRLSP information on each switch. [SwitchA] display mpls lsp Proto In/Out Label...
Page 111 Figure 31 Network diagram 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 Vlan-int10 100.1.1.1/24 Vlan-int10 100.1.2.1/24 Switch B Loop0 2.2.2.9/32 Switch C Loop0 3.3.3.9/32 Vlan-int1...
Page 112 [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 [SwitchB-Vlan-interface2] isis circuit-level level-2 [SwitchB-Vlan-interface2] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] isis enable 1 [SwitchB-LoopBack0] isis circuit-level level-2 [SwitchB-LoopBack0] quit # Configure Switch C.
Page 113 [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. [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...
Page 114 [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 [SwitchA-isis-1] quit # Configure Switch B. [SwitchB] isis 1 [SwitchB-isis-1] cost-style wide [SwitchB-isis-1] mpls te enable level-2 [SwitchB-isis-1] quit # Configure Switch C.
Page 115 [SwitchC-Vlan-interface2] mpls te max-reservable-bandwidth 5000 [SwitchC-Vlan-interface2] quit # Set the maximum link bandwidth and maximum reservable bandwidth on Switch D. [SwitchD] interface vlan-interface 3 [SwitchD-Vlan-interface3] mpls te max-link-bandwidth 10000 [SwitchD-Vlan-interface3] mpls te max-reservable-bandwidth 5000 [SwitchD-Vlan-interface3] quit Configure an MPLS TE tunnel on Switch A: # Configure MPLS TE tunnel interface Tunnel 1.
Page 116: Establishing An Inter-As Mpls Te Tunnel With Rsvp-Te
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 : 2000 kbps Reserved Bandwidth : 2000 kbps Setup Priority Holding Priority Affinity Attr/Mask : 0/0 Explicit Path Backup Explicit Path : -...
Page 117 Figure 32 Network diagram Table 4 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 Vlan-int10 100.1.1.1/24 Vlan-int10 100.1.2.1/24 Switch B Loop0 2.2.2.9/32 Switch C Loop0 3.3.3.9/32 Vlan-int1...
Page 118 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ospf [SwitchC-ospf-1] import-route direct [SwitchC-ospf-1] import-route bgp [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [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] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 4.4.4.9 0.0.0.0...
Page 119 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 20.1.1.1 enable [SwitchC-bgp-ipv4] import-route ospf [SwitchC-bgp-ipv4] import-route direct [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Verify that the switches have learned AS-external routes. [SwitchA] display ip routing-table Destinations : 10 Routes : 10 Destination/Mask Proto Pre Cost NextHop Interface 1.1.1.9/32...
Page 120 [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 2 [SwitchC-Vlan-interface2] mpls enable [SwitchC-Vlan-interface2] mpls te enable [SwitchC-Vlan-interface2] rsvp enable [SwitchC-Vlan-interface2] quit [SwitchC] interface vlan-interface 3 [SwitchC-Vlan-interface3] mpls enable...
Page 121 [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] mpls te enable [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. [SwitchD] ospf [SwitchD-ospf-1] opaque-capability enable [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] mpls te enable [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] quit Configure an explicit path on Switch A. Specify Switch B and Switch D as loose nodes, and Switch C as a strict node.
Page 122 # Configure MPLS TE tunnel interface Tunnel 1. [SwitchA] interface tunnel 1 mode mpls [SwitchA-Tunnel1] ip address 7.1.1.1 255.255.255.0 # Specify the tunnel destination address as the LSR ID of Switch D. [SwitchA-Tunnel1] destination 4.4.4.9 # Configure MPLS TE to use RSVP-TE to establish the tunnel. [SwitchA-Tunnel1] mpls te signaling rsvp-te # Assign 2000 kbps bandwidth to the tunnel.
Page 123: Establishing An Inter-Area Mpls Te Tunnel Over A Crlsp Calculated By Pces
Reserved Bandwidth : 2000 kbps Setup Priority Holding Priority Affinity Attr/Mask : 0/0 Explicit Path : atod Backup Explicit Path : - Metric Type : TE Record Route : Disabled Record Label : Disabled FRR Flag : Disabled Bandwidth Protection : Disabled Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth...
Page 124 Figure 33 Network diagram C onfiguration procedure 4 1 0 B Configure IP addresses and masks for interfaces. (Details not shown.) Configure OSPF to advertise interface addresses and configure OSPF TE: # 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.1 0.0.0.0 [SwitchA-ospf-1-area-0.0.0.0] mpls te enable...
Page 125 [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.1] network 3.3.3.3 0.0.0.0 [SwitchC-ospf-1-area-0.0.0.1] mpls te enable [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] ospf [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.2] network 4.4.4.4 0.0.0.0 [SwitchD-ospf-1-area-0.0.0.2] mpls te enable [SwitchD-ospf-1-area-0.0.0.2] quit [SwitchD-ospf-1] quit Configure an LSR ID, and enable MPLS, MPLS TE, and RSVP-TE:...
Page 126 # Configure Switch C. [SwitchC] mpls lsr-id 3.3.3.3 [SwitchC] mpls te [SwitchC-te] quit [SwitchC] rsvp [SwitchC-rsvp] quit [SwitchC] interface vlan-interface 11 [SwitchC-Vlan-interface11] mpls enable [SwitchC-Vlan-interface11] mpls te enable [SwitchC-Vlan-interface11] rsvp enable [SwitchC-Vlan-interface11] quit # Configure Switch D. [SwitchD] mpls lsr-id 4.4.4.4 [SwitchD] mpls te [SwitchD-te] quit [SwitchD] rsvp...
Page 127 Path scopes: Path scope Preference Compute intra-area paths Act as PCE for inter-area TE LSP computation Act as a default PCE for inter-area TE LSP computation Capabilities: Bidirectional path computation Support for request prioritization Support for multiple requests per message Domains: OSPF 1 area 0.0.0.0 OSPF 1 area 0.0.0.2...
Page 128: Bidirectional Mpls Te Tunnel Configuration Example
B idirectional MPLS TE tunnel configuration example 2 0 0 B N etwork requirements 4 1 2 B Switch A, Switch B, Switch C, and Switch D all run IS-IS and they are all level-2 switches. Use RSVP-TE to establish a bidirectional MPLS TE tunnel between Switch A and Switch D. Figure 34 Network diagram Table 5 Interface and IP address assignment Device...
Page 129 # Configure Switch B. <SwitchB> system-view [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 [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-interface1] quit...
Page 130 # Configure Switch A. [SwitchA] isis 1 [SwitchA-isis-1] cost-style wide [SwitchA-isis-1] mpls te enable level-2 [SwitchA-isis-1] quit # Configure Switch B. [SwitchB] isis 1 [SwitchB-isis-1] cost-style wide [SwitchB-isis-1] mpls te enable level-2 [SwitchB-isis-1] quit # Configure Switch C. [SwitchC] isis 1 [SwitchC-isis-1] cost-style wide [SwitchC-isis-1] mpls te enable level-2 [SwitchC-isis-1] quit...
Page 131 Internet address: 7.1.1.1/24 (primary) Tunnel source unknown, destination 4.4.4.9 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 Input: 0 packets, 0 bytes, 0 drops Output: 0 packets, 0 bytes, 0 drops # Display detailed information about the MPLS TE tunnel on Switch A.
Page 132 State : Active Out-Label : 1149 Nexthop : 10.1.1.2 Out-Interface: Vlan1 Destination : 4.4.4.9 : 1.1.1.9/1/30478 Protocol : RSVP LSR Type : Egress Service In-Label : 1151 State : Active Nexthop : 127.0.0.1 Out-Interface: - Destination : 10.1.1.2 : 10.1.1.2 Protocol : Local LSR Type...
Page 133 Ingress LSR ID Egress LSR ID Signaling : RSVP-TE Static CRLSP Name Resv Style : FF Tunnel mode : Co-routed, passive Reverse-LSP name Reverse-LSP LSR ID : 1.1.1.9 Reverse-LSP Tunnel ID: 1 Class Type Tunnel Bandwidth Reserved Bandwidth Setup Priority Holding Priority Affinity Attr/Mask : -/-...
Page 134: Crlsp Backup Configuration Example
Destination : 30.1.1.1 : 30.1.1.1 Protocol : Local LSR Type : Ingress Service NHLFE ID : 1024 State : Active Nexthop : 30.1.1.1 Out-Interface: Vlan1 C RLSP backup configuration example 2 0 1 B N etwork requirements 4 1 5 B Switch A, Switch B, Switch C, and Switch D run IS-IS and IS-IS TE.
Page 135 Device Interface IP address Device Interface IP address Vlan-int2 20.1.1.1/24 Vlan-int10 100.1.2.1/24 C onfiguration procedure 4 1 6 B Before configuration, disable the spanning tree feature globally or map each VLAN to an MSTI. For more information, see Layer 2—LAN Switching Configuration Guide. Configure IP addresses and masks for interfaces.
Page 136 Current state: UP Line protocol state: UP Description: Tunnel3 Interface Bandwidth: 64kbps Maximum transmission unit: 1496 Internet address: 9.1.1.1/24 (primary) Tunnel source unknown, destination 3.3.3.9 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...
Page 137 Tunnel name: Tunnel3 Destination: 3.3.3.9 Source: 1.1.1.9 Tunnel ID: 3 LSP ID: 30107 LSR type: Ingress Direction: Unidirectional Setup priority: 7 Holding priority: 7 In-Label: - Out-Label: 1150 In-Interface: - Out-Interface: Vlan4 Nexthop: 30.1.1.2 Exclude-any: 0 Include-Any: 0 Include-all: 0 Mean rate (CIR): 0 kbps Mean burst size (CBS): 1000.00 bytes Path MTU: 1500...
Page 138: Manual Bypass Tunnel For Frr Configuration Example
M anual bypass tunnel for FRR configuration example 2 0 2 B N etwork requirements 4 1 8 B On the primary CRLSP Switch A—Switch B—Switch C—Switch D, use FRR to protect the link Switch B—Switch C. Use RSVP-TE to establish the primary CRLSP and bypass tunnel based on the constraints of the explicit paths to transmit data between the two IP networks.
Page 139 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. <SwitchA> system-view [SwitchA] mpls lsr-id 1.1.1.1 [SwitchA] mpls te [SwitchA-te] quit [SwitchA] rsvp [SwitchA-rsvp] quit [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] mpls enable...
Page 140 [SwitchA] interface tunnel 4 mode mpls-te [SwitchA-Tunnel4] ip address 10.1.1.1 255.255.255.0 # Specify the tunnel destination address as the LSR ID of Switch D. [SwitchA-Tunnel4] destination 4.4.4.4 # Specify the tunnel signaling protocol as RSVP-TE. [SwitchA-Tunnel4] mpls te signaling rsvp-te # Specify the explicit path to be used as pri-path.
Page 141 Record Route : Enabled Record Label : Enabled FRR Flag : Enabled 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 142 [SwitchB] display mpls lsp Proto In/Out Label Interface/Out NHLFE 1.1.1.1/4/614000 RSVP 1245/3 Vlan2 Backup 1245/3 Tun5 2.2.2.2/5/30914 RSVP -/1150 Vlan2 3.2.1.2 Local Vlan4 3.1.1.2 Local Vlan2 [SwitchE] display mpls lsp Proto In/Out Label Interface/Out NHLFE 2.2.2.2/5/30914 RSVP 1150/3 Vlan5 3.3.1.2 Local Vlan5 # Shut down the protected interface VLAN-interface 2 on the PLR (Switch B).
Page 143: Auto Frr Configuration Example
Collected Bandwidth NOTE: If you execute the display mpls te tunnel-interface command immediately after an FRR, you can see two CRLSPs in up state. This is because FRR uses the make-before-break mechanism to set up a new LSP, and the old LSP is deleted after the new one has been established for a while. # Verify that the bypass tunnel is in use on Switch B.
Page 144 Figure 37 Network diagram Table 8 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Loop0 1.1.1.1/32 Switch E Loop0 5.5.5.5/32 Vlan-int1 2.1.1.1/24 Vlan-int4 3.2.1.2/24 Switch B Loop0 2.2.2.2/32 Vlan-int5 3.4.1.1/24 Vlan-int1 2.1.1.2/24 Switch C Loop0 3.3.3.3/32 Vlan-int2...
Page 145 [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. <SwitchB> system-view [SwitchB] mpls lsr-id 2.2.2.2 [SwitchB] mpls te [SwitchB-te] quit [SwitchB] rsvp [SwitchB-rsvp] quit [SwitchB] interface vlan-interface 1...
Page 146 [SwitchA] interface tunnel 1 mode mpls-te [SwitchA-Tunnel1] ip address 10.1.1.1 255.255.255.0 # Specify the tunnel destination address as the LSR ID of Switch D. [SwitchA-Tunnel1] destination 4.4.4.4 # Specify the tunnel signaling protocol as RSVP-TE. [SwitchA-Tunnel1] mpls te signaling rsvp-te # Specify the explicit path as pri-path.
Page 147 Record Route : Enabled Record Label : Enabled FRR Flag : Enabled Bandwidth Protection : Disabled Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth Bypass Tunnel : No Auto Created : No Route Pinning : Disabled Retry Limit Retry Interval : 2 sec Reoptimization...
Page 148 Explicit Path Backup Explicit Path : - Metric Type : TE Record Route : Enabled Record Label : Disabled FRR Flag : Disabled Bandwidth Protection : Disabled Backup Bandwidth Flag: Disabled Backup Bandwidth Type: - Backup Bandwidth Bypass Tunnel : Yes Auto Created : Yes Route Pinning...
Page 149: Ietf Ds-Te Configuration Example
Proto In/Out Label Interface/Out NHLFE 2.2.2.2/51/16802 RSVP Vlan4 2.2.2.2/1/16802 RSVP -/1151 Vlan2 Backup Tun50 2.2.2.2/50/16802 RSVP Vlan6 3.2.1.2 Local Vlan6 3.3.1.2 Local Vlan6 # Display detailed information about MPLS TE Tunnel1 (the tunnel for the primary CRLSP) on Switch A. The output shows that Tunnel1 is protected by the bypass tunnel Tunnel50, and the protected node is 3.1.1.1.
Page 150 Figure 38 Network diagram Table 9 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 Vlan-int10 100.1.1.1/24 Vlan-int10 100.1.2.1/24 Switch B Loop0 2.2.2.9/32 Switch C Loop0 3.3.3.9/32 Vlan-int1...
Page 151 [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 [SwitchB-Vlan-interface2] isis circuit-level level-2 [SwitchB-Vlan-interface2] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] isis enable 1 [SwitchB-LoopBack0] isis circuit-level level-2 [SwitchB-LoopBack0] quit # Configure Switch C.
Page 152 2.2.2.9/32 IS_L1 10.1.1.2 Vlan1 3.3.3.9/32 IS_L1 10.1.1.2 Vlan1 4.4.4.9/32 IS_L1 10.1.1.2 Vlan1 10.1.1.0/24 Direct 10.1.1.1 Vlan1 10.1.1.1/32 Direct 127.0.0.1 InLoop0 20.1.1.0/24 IS_L1 10.1.1.2 Vlan1 30.1.1.0/24 IS_L1 10.1.1.2 Vlan1 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0 Configure an LSR ID, enable MPLS, MPLS TE, and RSVP-TE, and configure the DS-TE mode as IETF : # Configure Switch A.
Page 153 [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. [SwitchD] mpls lsr-id 4.4.4.9 [SwitchD] mpls te [SwitchD-te] ds-te mode ietf [SwitchD-te] quit [SwitchD] rsvp [SwitchD-rsvp] quit...
Page 154 [SwitchA-Vlan-interface1] mpls te max-reservable-bandwidth rdm 10000 bc1 8000 bc2 5000 bc3 2000 [SwitchA-Vlan-interface1] quit # Set the maximum bandwidth, maximum reservable bandwidth, and bandwidth constraints on Switch B. [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] mpls te max-link-bandwidth 10000 [SwitchB-Vlan-interface1] mpls te max-reservable-bandwidth rdm 10000 bc1 8000 bc2 5000 bc3 2000 [SwitchB-Vlan-interface1] quit [SwitchB] interface vlan-interface 2...
Page 155 [SwitchA] ip route-static 100.1.2.0 24 tunnel 1 preference 1 V erifying the configuration 4 2 6 B # Verify that the tunnel interface is up on Switch A. [SwitchA] display interface tunnel Tunnel4 Current state: UP Line protocol current state: UP Description: Tunnel4 Interface Bandwidth: 64kbps Maximum transmission unit: 1496...
Page 156: Troubleshooting Mpls Te
Auto Bandwidth : Disabled Auto Bandwidth Freq Min Bandwidth Max Bandwidth Collected Bandwidth # Display bandwidth information on interface VLAN-interface 1 on Switch A. [SwitchA] display mpls te link-management bandwidth-allocation interface vlan-interface Interface: Vlan-interface1 Max Link Bandwidth : 10000 kbps Max Reservable Bandwidth of Prestandard RDM : 0 kbps Max Reservable Bandwidth of IETF RDM : 10000 kbps...
Page 157 c. Use the display ospf peer command to verify that OSPF neighbors are established correctly. If the problem persists, contact Hewlett Packard Enterprise Support.
Page 158: Configuring A Static Crlsp
C onfiguring a static CRLSP Overview 6 9 B 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 159: Displaying Static Crlsps
Step Command Remarks • Configure the ingress node: Use one command according static-cr-lsp ingress lsp-name to the position of a device on { nexthop ip-address | the network. outgoing-interface interface-type interface-number } out-label By default, no static CRLSPs out-label-value [ bandwidth [ ct0 | exist.
Page 160: Configuration Procedure
Figure 39 Network diagram Loop0 2.2.2.2/32 Vlan-int2 Vlan-int1 3.2.1.1/24 2.1.1.2/24 Switch B Vlan-int1 Vlan-int2 Vlan-int10 Vlan-int10 2.1.1.1/24 3.2.1.2/24 100.1.2.1/24 100.1.1.1/24 IP network IP network Switch A Switch C Loop0 Loop0 3.3.3.3/32 1.1.1.1/32 C onfiguration procedure 2 0 7 B 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 161 [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 162: Verifying The Configuration
[SwitchB-Vlan-interface1] mpls te max-link-bandwidth 10000 [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 # On Switch C, set the maximum bandwidth and the maximum reservable bandwidth. [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] mpls te max-link-bandwidth 10000 [SwitchC-Vlan-interface2] mpls te max-reservable-bandwidth 5000...
Page 163 Description: Tunnel0 Interface Bandwidth: 64kbps Maximum transmission unit: 1496 Internet address: 6.1.1.1/24 (primary) Tunnel source unknown, destination 3.3.3.3 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 Input: 0 packets, 0 bytes, 0 drops Output: 0 packets, 0 bytes, 0 drops...
Page 164 Proto In/Out Label Interface/Out NHLFE StaticCR 20/30 Vlan2 3.2.1.2 Local Vlan2 [SwitchC] display mpls lsp Proto In/Out Label Interface/Out NHLFE StaticCR 30/- [SwitchA] display mpls static-cr-lsp Name LSR Type In/Out Label Out Interface State static-cr-lsp-1 Ingress Null/20 Vlan1 [SwitchB] display mpls static-cr-lsp Name LSR Type In/Out Label...
Page 165: Configuring Rsvp
C onfiguring RSVP Overview 7 3 B 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 166: Crlsp Setup Procedure
C RLSP setup procedure 2 1 0 B As shown in F igure 40, a CRLSP is set up by using the following steps: 7 4 6 H 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 167: 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 168: Protocols And Standards
P rotocols and standards 2 1 4 B • 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 7 4 B Tasks at a glance (Required.) Enabling RSVP 7 4 7 H...
Page 169: Configuring Rsvp Srefresh And Reliable Rsvp Message Delivery
Configuring RSVP Srefresh and reliable RSVP 7 7 B 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.
Page 170: Configuring Rsvp Authentication
Step Command Remarks erroneous hellos. Set the interval for sending By default, hello requests are sent hello interval interval hello requests. every 5 seconds. Return to system view. quit interface interface-type Enter interface view. interface-number Enable RSVP hello By default, RSVP hello extension rsvp hello enable extension.
Page 171: Setting A Dscp Value For Outgoing Rsvp Packets
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. on the interface and rsvp authentication key { cipher Do not enable both RSVP configure the authentication | plain } string authentication and FRR on the key.
Page 172: Configuring Rsvp Gr
Step Command Remarks Set a DSCP value for outgoing dscp dscp-value By default, the DSCP value is 48. RSVP packets. Configuring RSVP GR 8 1 B RSVP GR depends on the RSVP hello extension feature. When configuring RSVP GR, you must enable RSVP hello extension.
Page 173: Rsvp Configuration Examples
Task Command neighbors. Display information about CRLSPs display rsvp lsp [ destination ip-address ] [ source established through RSVP. ip-address ] [ tunnel-id tunnel-id ] [ lsp-id lsp-id ] [ verbose ] display rsvp peer [ interface interface-type Display information about RSVP neighbors. interface-number ] [ ip ip-address ] [ verbose ] display rsvp request [ destination ip-address ] [ source Display information about RSVP resource...
Page 174 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 Vlan-int10 100.1.1.1/24 Vlan-int10 100.1.2.1/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...
Page 175 [SwitchC-isis-1] quit [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 176 [SwitchB-Vlan-interface1] mpls enable [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...
Page 177 [SwitchC] isis 1 [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: # Set 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 178 [SwitchA-Tunnel1] mpls te bandwidth 2000 [SwitchA-Tunnel1] quit Configure a static route on Switch A to direct the traffic destined for subnet 100.1.2.0/24 to the MPLS TE tunnel 1 for forwarding. [SwitchA] ip route-static 100.1.2.0 24 tunnel 1 preference 1 V erifying the configuration 4 3 5 B # Verify that the tunnel interface is up on Switch A.
Page 179: Rsvp Gr Configuration Example
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 to verify that a static route entry with interface Tunnel 1 as the output interface exists.
Page 180 [SwitchB-rsvp] quit [SwitchB-mpls] interface vlan-interface 1 [SwitchB-Vlan-interface1] mpls enable [SwitchB-Vlan-interface1] mpls te enable [SwitchB-Vlan-interface1] rsvp enable [SwitchB-Vlan-interface1] rsvp hello 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] rsvp hello enable [SwitchB-Vlan-interface2] quit # Configure Switch C.
Page 181 Peer GR restart time: 120000 ms Peer GR recovery time: 0 ms The output shows that the neighbor's GR state is Ready.
Page 182: Configuring Tunnel Policies
C onfiguring tunnel policies Overview 8 5 B 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 "...
Page 183: Configuration Procedure
application might take a great time to sequence the packets. As a best practice, do not use the second method. Figure 43 MPLS VPN tunnel selection diagram C onfiguration procedure 2 1 8 B To configure a tunnel policy: Step Command Remarks Enter system view.
Page 184: Tunnel Policy Configuration Examples
Tunnel policy configuration examples 8 8 B E xclusive tunnel configuration example 2 1 9 B N etwork requirements 4 3 9 B PE 1 has multiple tunnels to reach PE 2: two MPLS TE tunnels on interface Tunnel 1 and Tunnel 2, and one LDP LSP tunnel.
Page 185 VPN instance Tunnel policy vpnc, vpnd Use MPLS TE tunnel Tunnel 2 as the preferred tunnel. vpne Uses one tunnel selected in LDP LSP-MPLS TE order. C onfiguration procedure 4 4 2 B Configure tunnel policies on PE 1: # Create tunnel policy preferredte1, and configure tunnel 1 as the preferred tunnel. <PE1>...
Page 186 [PE1-vpn-instance-vpne] vpn-target 100:5 [PE1-vpn-instance-vpne] tnl-policy select-lsp...
Page 187: Configuring Mpls L3Vpn
C onfiguring MPLS L3VPN Overview 8 9 B 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. MPLS L3VPN provides flexible networking modes, excellent scalability, and convenient support for MPLS TE.
Page 188 • 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 189: 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 190: 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. M PLS L3VPN packet forwarding 2 2 4 B In a basic MPLS L3VPN (within a single AS), a PE adds the following information into VPN packets: •...
Page 191: Mpls L3Vpn Networking Schemes
M PLS L3VPN networking schemes 2 2 5 B 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. B asic VPN networking scheme 4 4 8 B In the simplest case, all users in a VPN form a closed user group.
Page 192 • The import target attribute of a spoke PE is different from the export target attribute of any other spoke PE. Any two spoke PEs do not directly advertise VPN-IPv4 routes to each other. Therefore, they cannot directly access each other. Figure 48 Network diagram for hub and spoke network A route in Site 1 is advertised to Site 2 by using the following process: Spoke-CE 1 advertises a route in Site 1 to Spoke-PE 1.
Page 193: Inter-As Vpn
Figure 49 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 F igure 49, route targets configured on PEs produce the following results: 7 6 4 H...
Page 194 Figure 50 Network diagram for inter-AS option A As shown in F igure 50, in VPN 1, routes are advertised from CE 1 to CE 3 by using the following 7 6 5 H process: PE 1 advertises the VPN routes learned from CE 1 to ASBR 1 through MP-IBGP. ASBR 1 performs the following operations: a.
Page 195 Figure 51 Network diagram for inter-AS option B VPN 1 VPN 1 CE 1 CE 3 ASBR 2 ASBR 1 PE 1 PE 3 (PE) (PE) MP-EBGP MPLS backbone MPLS backbone AS 100 AS 200 PE 2 PE 4 VPN LSP 1 VPN LSP 3 VPN LSP2 CE 4...
Page 196 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 197: Carrier's Carrier
Assume that the outgoing label for the public tunnel on PE 3 is Lv. 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.
Page 198 For packets between customer networks to travel through the Level 1 carrier, the PE of the Level 1 carrier and the CE of the Level 2 carrier must assign labels to the backbone networks of the Level 2 carrier. The CE of the Level 2 carrier is a PE within the Level 2 carrier network. Follow these guidelines to assign labels: •...
Page 199: Nested Vpn
Figure 55 Scenario where the Level 2 carrier is an MPLS L3VPN service provider NOTE: As a best practice, establish equal cost LSPs between the Level 1 carrier and the Level 2 carrier if equal cost routes exist between them. N ested VPN 2 2 8 B The nested VPN technology exchanges VPNv4 routes between PEs and CEs of the ISP MPLS...
Page 200: Hovpn
Figure 56 Network diagram for nested VPN VPN A Provider MPLS Provider PE Provider PE CE 8 CE 7 VPN backbone VPN A-2 VPN A-1 CE 2 CE 1 Customer MPLS Customer MPLS VPN network Customer PE Customer PE CE 3 CE 4 CE 5 CE 6...
Page 201 Figure 57 Basic architecture of HoVPN As shown in F igure 57, UPEs and SPEs play the following different roles: 7 7 4 H • A UPE is directly connected to CEs. It provides user access. It maintains the routes of directly connected VPN sites.
Page 202: Ospf Vpn Extension
Figure 58 Recursion of HoPEs F igure 58 shows a three-level HoPE. The PE in the middle is called the middle-level PE (MPE). 7 7 5 H MP-BGP runs between SPE and MPE, and between MPE and UPE. MP-BGP advertises the following routes: •...
Page 203 Figure 59 Network diagram for BGP/OSPF interaction As shown in F igure 59, CE 11, CE 21, and CE 22 belong to the same VPN and the same OSPF 7 7 6 H domain. Before domain ID configuration, VPN 1 routes are advertised from CE 11 to CE 21 and CE 22 by using the following process: PE 1 redistributes OSPF routes from CE 11 into BGP, and advertises the VPN routes to PE 2 through BGP.
Page 204: Bgp As Number Substitution And Soo Attribute
As shown in F igure 60, Site 1 is connected to two PEs. When a PE advertises VPN routes learned 7 7 7 H from MP-BGP to Site 1 through OSPF, the routes might be received by the other PE. This results in a routing loop.
Page 205: Mpls L3Vpn Frr
The BGP AS number substitution feature allows geographically different CEs to use the same AS number. If the AS_PATH of a route contains the AS number of a CE, the PE replaces the AS number with its own AS number before advertising the route to that CE. After you enable the BGP AS number substitution feature, the PE performs BGP AS number substitution for all routes and re-advertises them to connected CEs in the peer group.
Page 206 V PNv4 route backup for a VPNv4 route 4 6 0 B Figure 63 Network diagram As shown in F igure 63, configure FRR on the ingress node PE 1, and specify the backup next hop for 7 8 1 H VPN 1 as PE 3.
Page 207: Protocols And Standards
I Pv4 route backup for a VPNv4 route 4 6 2 B Figure 65 Network diagram As shown in F igure 65, configure FRR on the egress node PE 2, and specify the backup next hop for 7 8 4 H VPN 1 as CE 2.
Page 208: Configuring Basic Mpls L3Vpn
Tasks at a glance (Optional.) Enabling logging for BGP route flapping 7 9 4 H Configuring basic MPLS L3VPN 9 1 B Tasks at a glance Configuring VPN instances: 7 9 5 H (Required.) Creating a VPN instance 7 9 6 H (Required.) Associating a VPN instance with an interface 7 9 7 H...
Page 209 Step Command Remarks SNMP context for the VPN context-name configured. instance. A ssociating a VPN instance with an interface 4 6 4 B 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...
Page 210: Configuring Routing Between A Pe And A Ce
Step Command Remarks 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. policy. For information about routing policies, see Layer 3—IP Routing Configuration Guide. By default, only one tunnel is selected (no load balancing).
Page 211 C onfiguring OSPF between a PE and a CE 4 6 8 B An OSPF process that is bound to a VPN instance does not use the public network router ID configured in system view. Therefore, you must specify a router ID when creating a process or configure an IP address for a minimum of one interface in the VPN instance.
Page 212 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 VPN instance and enter PE. On the CE, configure vpn-instance-name IS-IS view. common IS-IS. Configure a network entity network-entity net By default, no NET is configured.
Page 213 Step Command Remarks a CE carries the AS number of the PE. Therefore, the route updates that the PE receives from the CE also include the AS number of the PE. This causes the PE to be unable to receive the route updates.
Page 214 Step Command Remarks Create the BGP-VPN IPv4 By default, the BGP-VPN IPv4 unicast family and enter its address-family ipv4 [ unicast ] unicast family is not created. view. Enable IPv4 unicast route By default, BGP does not peer { group-name | ip-address exchange with the exchange IPv4 unicast routes [ mask-length ] } enable...
Page 215: Configuring Routing Between Pes
C onfiguring routing between PEs 2 3 7 B Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] [ multi-session-thread ] peer { group-name | ip-address Configure the remote PE as [ mask-length ] } as-number By default, no BGP peers exist.
Page 216 Step Command Remarks Filter routes received from or peer { group-name | ipv4-address advertised to a peer or peer [ mask-length ] } as-path-acl By default, no AS filtering list is group based on an AS_PATH as-path-acl-number { export | applied to a peer or peer group.
Page 217: Configuring Inter-As Vpn
Step Command Remarks export route target attribute matches local import route target attribute are added to the routing table. By default, route reflection 21. Enable route reflection reflect between-clients between clients is enabled on the between clients. 22. Configure a cluster ID for the reflector cluster-id { cluster-id | By default, the RR uses its own ip-address }...
Page 218: Configuring Inter-As Option C
To configure inter-AS option B on an ASBR: Step Command Remarks Enter system view. system-view Enter interface view of the interface interface-type interface connected to an interface-number internal router of the AS. Enable MPLS on the By default, MPLS is disabled on mpls enable interface.
Page 219 Configure a routing protocol, and enable MPLS and LDP on the interface connected to an internal router of the AS. Specify the PE in the same AS as an IBGP peer, and the ASBR in a different AS as an EBGP peer.
Page 220 configure a routing policy to filter routes. Routes surviving the filtering are assigned labels, and all others are advertised as common IPv4 routes. To configure a routing policy, use the following commands: • if-match mpls-label—Matches routes carrying MPLS labels. • apply mpls-label—Sets MPLS labels for IPv4 routes advertised to a peer.
Page 221: Configuring Nested Vpn
Step Command Remarks [ mask-length ] } enable the same AS and the ASBR exchange IPv4 unicast routes with in another AS. any peer. 18. Enable exchange of labeled peer { group-name | ipv4-address By default, BGP cannot advertise IPv4 routes with the PE in the [ mask-length ] } labeled routes to any IPv4 peer or same AS and the ASBR in...
Page 222: Configuring Hovpn
Step Command Remarks Enter BGP VPNv4 address address-family vpnv4 family view. By default, nested VPN is Enable nested VPN. nesting-vpn disabled. Return to BGP instance view. quit Enter BGP-VPN instance ip vpn-instance view. vpn-instance-name peer { group-name | ipv4-address Specify the peer CE or the [ mask-length ] } as-number By default, no peer is specified.
Page 223: Configuring An Ospf Sham Link
Step Command Remarks peer group. peer. Specify the BGP peer or peer peer { group-name | ipv4-address By default, no peer is a UPE. group as a UPE. [ mask-length ] } upe • Advertise a default VPN By default, no route is advertised route to the UPE: to the UPE.
Page 224: Redistributing The Loopback Interface Address
R edistributing the loopback interface address 2 4 3 B Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] [ multi-session-thread ] ip vpn-instance Enter BGP-VPN instance view. vpn-instance-name Enter BGP-VPN IPv4 unicast address-family ipv4 [ unicast ] address family view.
Page 225: Configuring Bgp As Number Substitution And Soo Attribute
• POPGO forwarding—Pops the label and forwards the packet out of the output interface corresponding to the label. • 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...
Page 226 • Method 1—Execute the pic command in BGP-VPN IPv4 unicast address family view. The device calculates a backup next hop for each BGP route in the VPN instance if there are two or more unequal-cost routes to reach the destination. •...
Page 227: Enabling Snmp Notifications For Mpls L3Vpn
Step Command Remarks This step is required to enable MPLS L3VPN FRR in Method 2. For more information about this command, see Layer 3—IP Routing Command Reference. Return to system view. quit bgp as-number [ instance Enter BGP instance view. instance-name ] [ multi-session-thread ] By default, ARP is used to detect...
Page 228: Enabling Logging For Bgp Route Flapping
Enabling logging for BGP route flapping 1 0 0 B This feature enables BGP to generate logs for BGP route flappings that trigger log generation. The generated logs are sent to the information center. For the logs to be output correctly, you must also configure information center on the device.
Page 229: Mpls L3Vpn Configuration Examples
Task Command instance. [ statistics | verbose ] Display information about a specified display ip vpn-instance [ instance-name vpn-instance-name ] or all VPN instances. Display the FIB of a VPN instance. display fib vpn-instance vpn-instance-name Display FIB entries that match the display fib vpn-instance vpn-instance-name ip-address specified destination IP address in [ mask-length | mask ]...
Page 230 PEs use OSPF to communicate with each other and use MP-IBGP to exchange VPN routing information. Figure 66 Network diagram Table 12 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Vlan-int11 10.1.1.1/24 Loop0 2.2.2.9/32 PE 1 Loop0...
Page 231 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # 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...
Page 232 [P] mpls lsr-id 2.2.2.9 [P] mpls ldp [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...
Page 233 [PE2-vpn-instance-vpn2] quit [PE2] interface vlan-interface 11 [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 F igure 66.
Page 234 [PE1-bgp-default-ipv4-vpn1] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] ip vpn-instance vpn2 [PE1-bgp-default-vpn2] peer 10.2.1.1 as-number 65420 [PE1-bgp-default-vpn2] address-family ipv4 unicast [PE1-bgp-default-ipv4-vpn1] peer 10.2.1.1 enable [PE1-bgp-default-ipv4-vpn2] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] 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 235: 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 236 C onfiguration procedure 4 7 8 B 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...
Page 237 # 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 238 [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 239 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-default] peer 10.1.1.2 as-number 100 [Spoke-CE1-bgp-default] address-family ipv4 [Spoke-CE1-bgp-default-ipv4] peer 10.1.1.2 enable [Spoke-CE1-bgp-default-ipv4] import-route direct [Spoke-CE1-bgp-default-ipv4] quit [Spoke-CE1-bgp-default] quit # Configure Spoke-CE 2.
Page 240 [Spoke-PE2-bgp-default] quit # Configure Hub-PE. [Hub-PE] bgp 100 [Hub-PE-bgp-default] ip vpn-instance vpn1-in [Hub-PE-bgp-default-vpn1-in] peer 10.3.1.1 as-number 65430 [Hub-PE-bgp-default-vpn1-in] address-family ipv4 [Hub-PE-bgp-default-ipv4-vpn1-in] peer 10.3.1.1 enable [Hub-PE-bgp-default-ipv4-vpn1-in] quit [Hub-PE-bgp-default-vpn1-in] quit [Hub-PE-bgp-default] ip vpn-instance vpn1-out [Hub-PE-bgp-default-vpn1-out] peer 10.4.1.1 as-number 65430 [Hub-PE-bgp-default-vpn1-out] address-family ipv4 [Hub-PE-bgp-default-ipv4-vpn1-out] peer 10.4.1.1 enable [Hub-PE-bgp-default-ipv4-vpn1-out] peer 10.4.1.1 allow-as-loop 2 [Hub-PE-bgp-default-ipv4-vpn1-out] quit...
Page 241: Configuring Mpls L3Vpn Inter-As Option A
# 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.) V erifying the configuration 4 7 9 B # Execute the display ip routing-table vpn-instance command on the PEs to display the routes to the CEs.
Page 242 Figure 68 Network diagram MPLS backbone Loop0 Loop0 MPLS backbone AS 100 AS 200 Vlan-int12 Vlan-int12 Vlan-int11 Vlan-int11 ASBR-PE 1 ASBR-PE 2 Loop0 Loop0 Vlan-int11 Vlan-int11 PE 2 PE 1 Vlan-int12 Vlan-int12 Vlan-int12 Vlan-int12 CE 1 CE 2 AS 65001 AS 65002 Table 14 Interface and IP address assignment Device...
Page 243 # Configure basic MPLS on ASBR-PE 1, and enable MPLS LDP on the interface connected to PE 1. <ASBR-PE1> system-view [ASBR-PE1] mpls lsr-id 2.2.2.9 [ASBR-PE1] mpls ldp [ASBR-PE1-ldp] quit [ASBR-PE1] interface vlan-interface 11 [ASBR-PE1-Vlan-interface11] mpls enable [ASBR-PE1-Vlan-interface11] mpls ldp enable [ASBR-PE1-Vlan-interface11] quit # Configure basic MPLS on ASBR-PE 2, and enable MPLS LDP on the interface connected to PE 2.
Page 244 [PE1-Vlan-interface12] quit # Configure CE 2. <CE2> system-view [CE2] interface vlan-interface 12 [CE2-Vlan-interface12] ip address 10.2.1.1 24 [CE2-Vlan-interface12] quit # Configure PE 2. [PE2] ip vpn-instance vpn1 [PE2-vpn-instance] route-distinguisher 200:2 [PE2-vpn-instance] vpn-target 200:1 both [PE2-vpn-instance] quit [PE2] interface vlan-interface 12 [PE2-Vlan-interface12] ip binding vpn-instance vpn1 [PE2-Vlan-interface12] ip address 10.2.1.2 24 [PE2-Vlan-interface12] quit...
Page 245 # Configure PE 1. [PE1] bgp 100 [PE1-bgp-default] ip vpn-instance vpn1 [PE1-bgp-default-vpn1] peer 10.1.1.1 as-number 65001 [PE1-bgp-default-vpn1] address-family ipv4 unicast [PE1-bgp-default-ipv4-vpn1] peer 10.1.1.1 enable [PE1-bgp-default-ipv4-vpn1] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] quit # Configure CE 2. [CE2] bgp 65002 [CE2-bgp-default] peer 10.2.1.2 as-number 200 [CE2-bgp-default] address-family ipv4 unicast [CE2-bgp-default-ipv4] peer 10.2.1.2 enable [CE2-bgp-default-ipv4] import-route direct...
Page 246: Configuring Mpls L3Vpn Inter-As Option B
[ASBR-PE1-bgp-default-vpnv4] peer 1.1.1.9 enable [ASBR-PE1-bgp-default-vpnv4] peer 1.1.1.9 next-hop-local [ASBR-PE1-bgp-default-vpnv4] quit [ASBR-PE1-bgp-default] quit # Configure ASBR-PE 2. [ASBR-PE2] bgp 200 [ASBR-PE2-bgp-default] ip vpn-instance vpn1 [ASBR-PE2-bgp-default-vpn1] peer 192.1.1.1 as-number 100 [ASBR-PE2-bgp-default-vpn1] address-family ipv4 unicast [ASBR-PE2-bgp-default-ipv4-vpn1] peer 192.1.1.1 enable [ASBR-PE2-bgp-default-ipv4-vpn1] quit [ASBR-PE2-bgp-default-vpn1] quit [ASBR-PE2-bgp-default] peer 4.4.4.9 as-number 200 [ASBR-PE2-bgp-default] peer 4.4.4.9 connect-interface loopback 0 [ASBR-PE2-bgp-default] address-family vpnv4...
Page 247 Figure 69 Network diagram MPLS backbone Loop0 Loop0 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 PE 2 PE 1 Vlan-int12 Vlan-int12 Site 1 Site 2 CE 1 CE 2 AS 65001 AS 65002 Table 15 Interface and IP address assignment...
Page 248 # Configure 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 [PE1-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity...
Page 249 # Configure 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 Loopback 0, and enable IS-IS on it. [ASBR-PE1] interface loopback 0 [ASBR-PE1-LoopBack0] ip address 3.3.3.9 32 [ASBR-PE1-LoopBack0] isis enable 1 [ASBR-PE1-LoopBack0] quit # Enable BGP on ASBR-PE 1.
Page 250 [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-default] peer 11.0.0.2 as-number 100 [ASBR-PE2-bgp-default] peer 11.0.0.2 connect-interface vlan-interface 12 [ASBR-PE2-bgp-default] peer 5.5.5.9 as-number 600 [ASBR-PE2-bgp-default] peer 5.5.5.9 connect-interface loopback 0 # Disable route target based filtering of received VPNv4 routes.
Page 251: Configuring Mpls L3Vpn Inter-As Option C
[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. [PE2] bgp 600 # Configure IBGP peer 4.4.4.9 as a VPNv4 peer. [PE2-bgp-default] peer 4.4.4.9 as-number 600 [PE2-bgp-default] peer 4.4.4.9 connect-interface loopback 0 [PE2-bgp-default] address-family vpnv4 [PE2-bgp-default-vpnv4] peer 4.4.4.9 enable [PE2-bgp-default-vpnv4] quit...
Page 252 Figure 70 Network diagram Table 16 Interface and IP address assignment Device Interface IP address Device Interface IP address PE 1 Loop0 2.2.2.9/32 PE 2 Loop0 5.5.5.9/32 Vlan-int11 1.1.1.2/8 Vlan-int11 9.1.1.2/8 Vlan-int12 30.0.0.1/24 Vlan-int12 20.0.0.1/24 ASBR-PE 1 Loop0 3.3.3.9/32 ASBR-PE 2 Loop0 4.4.4.9/32 Vlan-int11...
Page 253 [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 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 254 [PE1-bgp-default-vpnv4] quit # Establish an EBGP peer relationship with CE 1, and add the learned BGP routes to the routing table of VPN instance vpn1. [PE1-bgp-default] ip vpn-instance vpn1 [PE1-bgp-default-vpn1] peer 30.0.0.2 as-number 65001 [PE1-bgp-default-vpn1] address-family ipv4 unicast [PE1-bgp-default-ipv4-vpn1] peer 30.0.0.2 enable [PE1-bgp-default-ipv4-vpn1] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] quit...
Page 255 [ASBR-PE1-bgp-default] peer 2.2.2.9 as-number 100 [ASBR-PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [ASBR-PE1-bgp-default] address-family ipv4 unicast [ASBR-PE1-bgp-default-ipv4] peer 2.2.2.9 enable [ASBR-PE1-bgp-default-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 256 # 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 257 # Configure 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 258: Configuring Mpls L3Vpn Carrier's Carrier In The Same As
[CE2-Vlan-interface12] ip address 20.0.0.2 24 [CE2-Vlan-interface12] quit # Establish an EBGP peer relationship with PE 2, and redistribute VPN routes. [CE2] bgp 65002 [CE2-bgp-default] peer 20.0.0.1 as-number 600 [CE2-bgp-default] address-family ipv4 unicast [CE2-bgp-default-ipv4] peer 20.0.0.1 enable [CE2-bgp-default-ipv4] import-route direct [CE2-bgp-default-ipv4] quit [CE2-bgp-default] quit V erifying the configuration 4 8 8 B...
Page 259 Figure 71 Network diagram Table 17 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 3 Vlan-int11 100.1.1.1/24 CE 4 Vlan-int11 120.1.1.1/24 PE 3 Loop0 1.1.1.9/32 PE 4 Loop0 6.6.6.9/32 Vlan-int11 100.1.1.2/24 Vlan-int11 120.1.1.2/24 Vlan-int12 10.1.1.1/24 Vlan-int12 20.1.1.2/24...
Page 260 [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-default] peer 4.4.4.9 as-number 100 [PE1-bgp-default] peer 4.4.4.9 connect-interface loopback 0 [PE1-bgp-default] address-family vpnv4...
Page 261 [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 262 [PE1-Vlan-interface11] mpls ldp transport-address interface [PE1-Vlan-interface11] quit [PE1] bgp 100 [PE1-bgp-default] ip vpn-instance vpn1 [PE1-bgp-default-vpn1] address-family ipv4 unicast [PE1-bgp-default-ipv4-vpn1] import isis 2 [PE1-bgp-default-ipv4-vpn1] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] 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...
Page 263 [PE3-bgp-default-vpn1] quit [PE3-bgp-default] 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 264 2.2.2.9/32 IS_L1 11.1.1.1 Vlan11 5.5.5.9/32 255 10 4.4.4.9 Vlan12 6.6.6.9/32 255 20 4.4.4.9 Vlan12 10.1.1.0/24 IS_L1 11.1.1.1 Vlan11 11.1.1.0/24 Direct 11.1.1.2 Vlan11 11.1.1.0/32 Direct 11.1.1.2 Vlan11 11.1.1.2/32 Direct 127.0.0.1 InLoop0 11.1.1.255/32 Direct 11.1.1.2 Vlan11 20.1.1.0/24 255 20 4.4.4.9 Vlan12 127.0.0.0/8 Direct 127.0.0.1 InLoop0...
Page 265 [PE3] display ip routing-table Destinations : 18 Routes : 18 Destination/Mask Proto Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 1.1.1.9/32 Direct 127.0.0.1 InLoop0 2.2.2.9/32 IS_L1 10.1.1.2 Vlan12 5.5.5.9/32 IS_L2 10.1.1.2 Vlan12 6.6.6.9/32 IS_L2 10.1.1.2 Vlan12 10.1.1.0/24 Direct 10.1.1.1 Vlan12 10.1.1.0/32 Direct 10.1.1.1...
Page 266: Configuring Mpls L3Vpn Carrier's Carrier In Different Ass
C onfiguring MPLS L3VPN carrier's carrier in different ASs 2 5 1 B N etwork requirements 4 9 2 B Configure carrier's carrier for the scenario shown in F igure 72. In this scenario: 8 1 0 H • PE 1 and PE 2 are the provider carrier's PE switches. They provide VPN services for the customer carrier.
Page 267 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-int11 11.1.1.2/24 Vlan-int12 30.1.1.2/24 Vlan-int12 30.1.1.1/24 Vlan-int11 21.1.1.1/24 C onfiguration procedure 4 9 3 B Configure MPLS L3VPN on the provider carrier backbone. Enable IS-IS as the IGP, enable LDP between PE 1 and PE 2, and establish an MP-IBGP peer relationship between the PEs: # Configure PE 1.
Page 268 <PE3> system-view [PE3] interface loopback 0 [PE3-LoopBack0] ip address 1.1.1.9 32 [PE3-LoopBack0] quit [PE3] mpls lsr-id 1.1.1.9 [PE3] mpls ldp [PE3-ldp] quit [PE3] isis 2 [PE3-isis-2] network-entity 10.0000.0000.0000.0001.00 [PE3-isis-2] quit [PE3] interface loopback 0 [PE3-LoopBack0] isis enable 2 [PE3-LoopBack0] quit [PE3] interface vlan-interface 12 [PE3-Vlan-interface12] ip address 10.1.1.1 24 [PE3-Vlan-interface12] isis enable 2...
Page 269 Allow CEs of the customer carrier to access PEs of the provider carrier: # 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 11 [PE1-Vlan-interface11] ip binding vpn-instance vpn1 [PE1-Vlan-interface11] ip address 11.1.1.2 24 [PE1-Vlan-interface11] mpls enable [PE1-Vlan-interface11] quit [PE1] bgp 200...
Page 270 [CE3] interface vlan-interface 11 [CE3-Vlan-interface11] ip address 100.1.1.1 24 [CE3-Vlan-interface11] quit [CE3] bgp 65410 [CE3-bgp-default] peer 100.1.1.2 as-number 100 [CE3-bgp-default] address-family ipv4 unicast [CE3-bgp-default-ipv4] peer 100.1.1.2 enable [CE3-bgp-default-ipv4] import-route direct [CE3-bgp-default-ipv4] quit [CE3-bgp-default] quit # Configure PE 3. [PE3] ip vpn-instance vpn1 [PE3-vpn-instance-vpn1] route-distinguisher 100:1 [PE3-vpn-instance-vpn1] vpn-target 1:1 [PE3-vpn-instance-vpn1] quit...
Page 271 Destinations : 14 Routes : 14 Destination/Mask Proto Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 3.3.3.9/32 Direct 127.0.0.1 InLoop0 4.4.4.9/32 IS_L1 30.1.1.2 Vlan12 30.1.1.0/24 Direct 30.1.1.1 Vlan12 30.1.1.0/32 Direct 30.1.1.1 Vlan12 30.1.1.1/32 Direct 127.0.0.1 InLoop0 30.1.1.255/32 Direct 30.1.1.1 Vlan12 127.0.0.0/8 Direct 127.0.0.1...
Page 272 2.2.2.9/32 Direct 127.0.0.1 InLoop0 6.6.6.9/32 255 0 11.1.1.2 Vlan11 10.1.1.0/24 Direct 10.1.1.2 Vlan12 10.1.1.0/32 Direct 10.1.1.2 Vlan12 10.1.1.2/32 Direct 127.0.0.1 InLoop0 10.1.1.255/32 Direct 10.1.1.2 Vlan12 11.1.1.0/24 Direct 11.1.1.1 Vlan11 11.1.1.0/32 Direct 11.1.1.1 Vlan11 11.1.1.1/32 Direct 127.0.0.1 InLoop0 11.1.1.255/32 Direct 11.1.1.1 Vlan11 127.0.0.0/8 Direct...
Page 273: Configuring Nested Vpn
100.1.1.0/24 Direct 100.1.1.2 Vlan11 100.1.1.0/32 Direct 100.1.1.2 Vlan11 100.1.1.2/32 Direct 127.0.0.1 InLoop0 100.1.1.255/32 Direct 100.1.1.2 Vlan11 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0 127.255.255.255/32 Direct 127.0.0.1 InLoop0 120.1.1.0/24 255 0 6.6.6.9 Vlan12 224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24 Direct...
Page 274 Figure 73 Network diagram Table 19 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Loop0 2.2.2.9/32 CE 2 Loop0 5.5.5.9/32 Vlan-int2 10.1.1.2/24 Vlan-int1 21.1.1.2/24 Vlan-int1 11.1.1.1/24 Vlan-int2 20.1.1.1/24 CE 3 Vlan-int1 100.1.1.1/24 CE 4 Vlan-int1 120.1.1.1/24 CE 5...
Page 275 [PE1] isis 1 [PE1-isis-1] network-entity 10.0000.0000.0000.0004.00 [PE1-isis-1] quit [PE1] interface loopback 0 [PE1-LoopBack0] isis enable 1 [PE1-LoopBack0] quit [PE1] interface vlan-interface 2 [PE1-Vlan-interface2] ip address 30.1.1.1 24 [PE1-Vlan-interface2] isis enable 1 [PE1-Vlan-interface2] mpls enable [PE1-Vlan-interface2] mpls ldp enable [PE1-Vlan-interface2] quit [PE1] bgp 100 [PE1-bgp-default] peer 4.4.4.9 as-number 100 [PE1-bgp-default] peer 4.4.4.9 connect-interface loopback 0...
Page 276 [PE3-Vlan-interface2] 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 2...
Page 277 [CE1] bgp 200 [CE1-bgp-default] peer 11.1.1.2 as-number 100 [CE1-bgp-default-vpn1] address-family ipv4 [CE1-bgp-default-ipv4-vpn1] peer 11.1.1.2 enable [CE1-bgp-default-ipv4-vpn1] quit [CE1-bgp-default] quit # Configure PE 2 and CE 2 in the same way that PE 1 and CE 1 are configured. (Details not shown.) Connect sub-VPN CEs to the customer VPN PEs: # Configure CE 3.
Page 278 [PE3-Vlan-interface3] ip address 110.1.1.2 24 [PE3-Vlan-interface3] quit [PE3] bgp 200 [PE3-bgp-default] ip vpn-instance SUB_VPN1 [PE3-bgp-default-SUB_VPN1] peer 100.1.1.1 as-number 65410 [PE3-bgp-default-SUB_VPN1] address-family ipv4 unicast [PE3-bgp-default-ipv4-SUB_VPN1] peer 100.1.1.1 enable [PE3-bgp-default-ipv4-SUB_VPN1] quit [PE3-bgp-default-SUB_VPN1] quit [PE3-bgp-default] ip vpn-instance SUB_VPN2 [PE3-bgp-default-SUB_VPN2] peer 100.1.1.1 as-number 65411 [PE3-bgp-default-SUB_VPN2] address-family ipv4 unicast [PE3-bgp-default-ipv4-SUB_VPN2] peer 110.1.1.1 enable [PE3-bgp-default-ipv4-SUB_VPN2] quit...
Page 279 [PE3-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [PE3-bgp-default] address-family vpnv4 [PE3-bgp-default-vpnv4] peer 2.2.2.9 enable # Allow the local AS number to appear in the AS-PATH attribute of the routes received. [PE3-bgp-default-vpnv4] peer 2.2.2.9 allow-as-loop 2 [PE3-bgp-default-vpnv4] quit [PE3-bgp-default] quit # Configure CE 1. [CE1] bgp 200 [CE1-bgp-default] peer 1.1.1.9 as-number 200 [CE1-bgp-default] peer 1.1.1.9 connect-interface loopback 0...
Page 280 11.1.1.0/24 Direct 11.1.1.2 Vlan1 11.1.1.0/32 Direct 11.1.1.2 Vlan1 11.1.1.2/32 Direct 127.0.0.1 InLoop0 11.1.1.255/32 Direct 11.1.1.2 Vlan1 100.1.1.0/24 255 0 11.1.1.1 Vlan1 110.1.1.0/24 255 0 11.1.1.1 Vlan1 120.1.1.0/24 255 0 4.4.4.9 Vlan2 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0...
Page 281 Route Distinguisher: 201:1 Total number of routes: 1 Network NextHop LocPrf PrefVal Path/Ogn * >e 130.1.1.0/24 11.1.1.2 100 200 65421? Display the VPN routing table on the customer PEs, for example, on PE 3: # Verify that the VPN routing table contains routes sent by the provider PE to the sub-VPN. [PE3] display ip routing-table vpn-instance SUB_VPN1 Destinations : 11 Routes : 11...
Page 282: Configuring Hovpn
Destinations : 13 Routes : 13 Destination/Mask Proto Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 110.1.1.0/24 Direct 110.1.1.1 Vlan1 110.1.1.0/32 Direct 110.1.1.1 Vlan1 110.1.1.1/32 Direct 127.0.0.1 InLoop0 110.1.1.255/32 Direct 110.1.1.1 Vlan1 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1...
Page 283 Table 20 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Vlan-int12 10.2.1.1/24 CE 3 Vlan-int12 10.1.1.1/24 CE 2 Vlan-int13 10.4.1.1/24 CE 4 Vlan-int13 10.3.1.1/24 UPE 1 Loop0 1.1.1.9/32 UPE 2 Loop0 4.4.4.9/32 Vlan-int11 172.1.1.1/24 Vlan-int11 172.2.1.1/24...
Page 284 [UPE1-Vlan-interface12] ip address 10.2.1.2 24 [UPE1-Vlan-interface12] quit [UPE1] interface vlan-interface 13 [UPE1-Vlan-interface13] ip binding vpn-instance vpn2 [UPE1-Vlan-interface13] ip address 10.4.1.2 24 [UPE1-Vlan-interface13] quit # Establish an MP-IBGP peer relationship with SPE 1. [UPE1] bgp 100 [UPE1-bgp-default] peer 2.2.2.9 as-number 100 [UPE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [UPE1-bgp-default] address-family vpnv4 [UPE1-bgp-default-vpnv4] peer 2.2.2.9 enable...
Page 285 [CE2-bgp-default-ipv4] peer 10.4.1.2 enable [CE2-bgp-default-ipv4] import-route direct [CE2-bgp-default-ipv4] quit [CE2-bgp-default] quit Configure UPE 2: # Configure basic MPLS and MPLS LDP to establish LDP LSPs. <UPE2> system-view [UPE2] interface loopback 0 [UPE2-Loopback0] ip address 4.4.4.9 32 [UPE2-Loopback0] quit [UPE2] mpls lsr-id 4.4.4.9 [UPE2] mpls ldp [UPE2-ldp] quit [UPE2] interface vlan-interface 11...
Page 286 [UPE2-bgp-default-vpnv4] quit # Establish an EBGP peer relationship with CE 3. [UPE2-bgp-default] ip vpn-instance vpn1 [UPE2-bgp-default-vpn1] peer 10.1.1.1 as-number 65430 [UPE2-bgp-default-vpn1] address-family ipv4 unicast [UPE2-bgp-default-ipv4-vpn1] peer 10.1.1.1 enable [UPE2-bgp-default-ipv4-vpn1] quit [UPE2-bgp-default-vpn1] quit # Establish an EBGP peer relationship with CE 4. [UPE2-bgp-default] ip vpn-instance vpn2 [UPE2-bgp-default-vpn2] peer 10.3.1.1 as-number 65440 [UPE2-bgp-default-vpn2] address-family ipv4 unicast...
Page 287 [SPE1-ldp] quit [SPE1] interface vlan-interface 11 [SPE1-Vlan-interface11] ip address 172.1.1.2 24 [SPE1-Vlan-interface11] mpls enable [SPE1-Vlan-interface11] mpls ldp enable [SPE1-Vlan-interface11] quit [SPE1] interface vlan-interface 12 [SPE1-Vlan-interface12] ip address 180.1.1.1 24 [SPE1-Vlan-interface12] mpls enable [SPE1-Vlan-interface12] mpls ldp enable [SPE1-Vlan-interface12] quit # Configure the IGP protocol (OSPF, in this example). [SPE1] ospf [SPE1-ospf-1] area 0 [SPE1-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0...
Page 288 # Advertise to UPE 1 the routes permitted by a routing policy (the routes of CE 3). [SPE1] ip prefix-list hope index 10 permit 10.1.1.1 24 [SPE1] route-policy hope permit node 0 [SPE1-route-policy-hope-0] if-match ip address prefix-list hope [SPE1-route-policy-hope-0] quit [SPE1] bgp 100 [SPE1-bgp-default] address-family vpnv4 [SPE1-bgp-default-vpnv4] peer 1.1.1.9 upe route-policy hope export...
Page 289: Configuring An Ospf Sham Link
[SPE2-bgp-default] peer 2.2.2.9 as-number 100 [SPE2-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [SPE2-bgp-default] address-family vpnv4 [SPE2-bgp-default-vpnv4] peer 2.2.2.9 enable [SPE2-bgp-default-vpnv4] peer 4.4.4.9 enable [SPE2-bgp-default-vpnv4] peer 4.4.4.9 upe [SPE2-bgp-default-vpnv4] peer 4.4.4.9 next-hop-local [SPE2-bgp-default-vpnv4] quit # Create BGP-VPN instances for VPN instances vpn1 and vpn2, so the VPNv4 routes learned according to the RT attributes can be added into the BGP routing tables of the corresponding VPN instances.
Page 290 Figure 75 Network diagram Loop0 Loop0 Vlan-int12 PE 1 PE 2 Vlan-int12 Vlan-int11 Vlan-int11 Sham-link Loop1 Loop1 OSPF Area 1 Vlan-int11 Vlan-int11 Vlan-int13 Vlan-int12 Vlan-int12 Vlan-int13 CE 1 Switch A CE 2 Backdoor link Table 21 Interface and IP address assignment Device Interface IP address...
Page 291 [PE1-Vlan-interface12] mpls enable [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-default] peer 2.2.2.9 as-number 100 [PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [PE1-bgp-default] address-family vpnv4 [PE1-bgp-default-vpnv4] peer 2.2.2.9 enable [PE1-bgp-default-vpnv4] quit [PE1-bgp-default] quit # Configure OSPF on PE 1.
Page 292 [PE1] ip vpn-instance vpn1 [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] ip address 100.1.1.2 24 [PE1-Vlan-interface11] quit [PE1] ospf 100 vpn-instance vpn1 [PE1-ospf-100] domain-id 10 [PE1-ospf-100] area 1 [PE1-ospf-100-area-0.0.0.1] network 100.1.1.0 0.0.0.255 [PE1-ospf-100-area-0.0.0.1] quit [PE1-ospf-100] quit [PE2] bgp 100...
Page 293 Configure a sham link: # Configure PE 1. [PE1] interface loopback 1 [PE1-LoopBack1] ip binding vpn-instance vpn1 [PE1-LoopBack1] ip address 3.3.3.3 32 [PE1-LoopBack1] quit [PE1] ospf 100 [PE1-ospf-100] area 1 [PE1-ospf-100-area-0.0.0.1] sham-link 3.3.3.3 5.5.5.5 [PE1-ospf-100-area-0.0.0.1] quit [PE1-ospf-100] quit # Configure PE 2. [PE2] interface loopback 1 [PE2-LoopBack1] ip binding vpn-instance vpn1 [PE2-LoopBack1] ip address 5.5.5.5 32...
Page 294: Configuring Bgp As Number Substitution
C onfiguring BGP AS number substitution 2 5 5 B N etwork requirements 5 0 4 B As shown in F igure 76, CE 1 and CE 2 belong to VPN 1, and are connected to PE 1 and PE 2, 8 1 5 H respectively.
Page 295 For more information about basic MPLS L3VPN configurations, see " C onfiguring basic MPLS 8 1 6 H L3VPN." # Execute the display ip routing-table command on CE 2. The output shows that CE 2 has learned the route to network 10.1.1.0/24, where the interface used by CE 1 to access PE 1 resides.
Page 296 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 # Enable BGP update packet debugging on PE 2. The output shows that PE 2 has advertised the route for 100.1.1.1/32, and the AS_PATH is 100 600. <PE2> terminal monitor <PE2>...
Page 297: Configuring Bgp As Number Substitution And Soo Attribute
# Display again the routing information that CE 2 has received, and the routing table. <CE2> display bgp routing-table ipv4 peer 10.2.1.2 received-routes Total number of routes: 3 BGP local router ID is 200.1.1.1 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network...
Page 298 Figure 77 Network diagram CE 1 Loop0 Vlan-int2 MPLS backbone Vlan-int2 AS 100 Loop0 Vlan-int3 Loop0 Loop0 Vlan-int3 PE 1 Vlan-int4 VPN 1 Vlan-int6 AS 600 Vlan-int6 Vlan-int7 PE 2 Vlan-int4 Vlan-int5 PE 3 CE 3 Loop0 Vlan-int5 Vlan-int7 Loop0 Vlan-int2 CE 2 VPN 1...
Page 299 Configure BGP AS number substitution: # Configure BGP AS number substitution on PE 1, PE 2, and PE 3. For more information about the configuration, see " C onfiguring BGP AS number substitution." 8 1 8 H # Display routing information on CE 2. The output shows that CE 2 has learned the route for 100.1.1.1/32 from CE 1.
Page 300: Configuring Mpls L3Vpn Frr Through Vpnv4 Route Backup For A Vpnv4 Route
10.2.1.1/32 Direct 0 127.0.0.1 Inloop0 10.2.1.255/32 Direct 0 10.2.1.1 Vlan2 10.3.1.0/24 10.2.1.2 Vlan2 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 200.1.1.1/32 10.2.1.2 Vlan2 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0...
Page 301 Device Interface IP address Device Interface IP address Vlan-int11 172.1.1.2/24 Vlan-int12 172.2.1.1/24 Vlan-int13 10.1.1.2/24 CE 2 Loop0 4.4.4.4/32 PE 3 Loop0 3.3.3.3/32 Vlan-int13 10.1.1.1/24 Vlan-int12 172.2.1.3/24 Vlan-int14 10.3.1.1/24 Vlan-int14 10.3.1.2/24 C onfiguration procedure 5 1 1 B Configure IP addresses and masks for interfaces as shown in T able 24, and configure BGP and 8 1 9 H...
Page 302: Configuring Mpls L3Vpn Frr Through Vpnv4 Route Backup For An Ipv4 Route
Destination: 4.4.4.4/32 Protocol: BGP Process ID: 0 SubProtID: 0x1 Age: 00h00m03s 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...
Page 303 Table 25 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Loop0 5.5.5.5/32 PE 2 Loop0 2.2.2.2/32 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...
Page 304: Configuring Mpls L3Vpn Frr Through Ipv4 Route Backup For A Vpnv4 Route
Summary Count : 1 Destination: 4.4.4.4/32 Protocol: BGP Process ID: 0 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...
Page 305 Table 26 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Loop0 5.5.5.5/32 PE 2 Loop0 2.2.2.2/32 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...
Page 306 [PE3] mpls bfd enable V erifying the configuration 5 1 8 B # 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...
Page 307: Configuring Ipv6 Mpls L3Vpn
C onfiguring IPv6 MPLS L3VPN Overview 1 0 3 B IPv6 MPLS L3VPN uses BGP to advertise IPv6 VPN routes and uses MPLS to forward IPv6 VPN packets on the service provider backbone. F igure 81 shows a typical IPv6 MPLS L3VPN model. The service provider backbone in the IPv6 8 2 5 H MPLS L3VPN model is an IPv4 network.
Page 308: 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 309: Ipv6 Mpls L3Vpn Configuration Task List
• RFC 6565, OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol IPv6 MPLS L3VPN configuration task list 1 0 4 B Tasks at a glance (Required.) Configuring basic IPv6 MPLS L3VPN 8 2 7 H (Optional.) Configuring inter-AS IPv6 VPN 8 2 8 H (Optional.) Configuring an OSPFv3 sham link...
Page 310 C reating a VPN instance 5 1 9 B A VPN instance is a collection of the VPN membership and routing rules of its associated site. A VPN instance might correspond to more than one VPN. To create and configure a VPN instance: Step Command Remarks...
Page 311: Configuring Routing Between A Pe And A Ce
Step Command Remarks vpn-instance-name over the configurations in VPN instance view. b. address-family ipv6 vpn-target vpn-target&<1-8> By default, no route targets are Configure route targets. [ both | export-extcommunity | configured. import-extcommunity ] By default, the number of active routes in a VPN instance is not limited.
Page 312 Step Command Remarks [ next-hop-address ] | nexthop-address Perform this [ public ] | vpn-instance d-vpn-instance-name configuration on the PE. nexthop-address } [ permanent ] [ preference On the CE, configure a preference ] [ tag tag-value ] [ description text ] common IPv6 static route.
Page 313 Step Command Remarks attribute. You can configure the same domain ID for different OSPFv3 processes. You must configure the same domain ID for all OSPFv3 processes of the same VPN to ensure correct route advertisement. By default, the type codes for domain ID, route type, and router (Optional.) Configure the ext-community-type...
Page 314 Step Command Remarks 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 on the ospfv3 process-id area area-id interface. [ instance instance-id ] Perform this configuration on the C onfiguring IPv6 IS-IS between a PE and a CE 5 2 5 B An IPv6 IS-IS process belongs to the public network or a single VPN instance.
Page 315 Step Command Remarks BGP-VPN IPv6 unicast address family view are the same as those in BGP IPv6 unicast address family view. For more information, see Layer 3—IP Routing Configuration Guide. Enable IPv6 unicast route By default, BGP does not exchange with the peer { group-name | ip-address exchange IPv6 unicast routes specified peer or peer...
Page 316 C onfiguring IBGP between a PE and a CE 5 2 7 B Use IBGP between PE and CE only in a basic IPv6 MPLS L3VPN network. In networks such as inter-AS VPN and carrier's carrier, you cannot configure IBGP between PE and CE. Configure the PE: Step Command...
Page 317: Configuring Routing Between Pes
Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] [ multi-session-thread ] peer { group-name | Configure the PE as an ipv6-address [ prefix-length ] } By default, no BGP peers exist. IBGP peer.
Page 318 Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] [ multi-session-thread ] Enter BGP VPNv6 address address-family vpnv6 family view. filter-policy { ipv6-acl-number | Configure filtering of By default, BGP does not filter prefix-list ipv6-prefix-name } advertised routes.
Page 319: Configuring Inter-As Ipv6 Vpn
Step Command Remarks the client. peer { group-name | ipv4-address [ mask-length ] } route-limit 16. Set the maximum number of By default, the number of routes prefix-number [ { alert-only | routes BGP can receive from that BGP can receive from a peer discard | reconnect a peer or peer group.
Page 320: Configuring Inter-As Ipv6 Vpn Option C
• Configure VPN instances on both PEs and ASBRs. The VPN instances on PEs allow CEs to access the network, and those on ASBRs are for access of the peer ASBRs. For more configuration information, see " C onfiguring basic IPv6 MPLS L3VPN."...
Page 321: Configuring An Ospfv3 Sham Link
C onfiguring the routing policy 5 3 0 B A routing policy on an ASBR performs the following operations: • Assigns MPLS labels to routes received from the PEs in the same AS before advertising them to the peer ASBR. •...
Page 322: Creating A Sham Link
C reating a sham link 2 7 3 B Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enter OSPFv3 area view. area area-id sham-link source-ipv6-address destination-ipv6-address [ cost cost-value | dead dead-interval | hello Configure an OSPFv3 hello-interval | instance instance-id | By default, no sham links exist.
Page 323: Enabling Logging For Bgp Route Flapping
Enabling logging for BGP route flapping 1 0 9 B This feature enables BGP to generate logs for BGP route flappings that trigger log generation. The generated logs are sent to the information center. For the logs to be output correctly, you must also configure information center on the device.
Page 324: Ipv6 Mpls L3Vpn Configuration Examples
Task Command display bgp [ instance instance-name ] peer vpnv6 Display BGP VPNv6 peer information. [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ] display bgp [ instance instance-name ] routing-table vpnv6 [ [ route-distinguisher route-distinguisher ] [ ipv6-address prefix-length [ advertise-info ] | as-path-acl as-path-acl-number | Display BGP VPNv6 routes.
Page 325 Figure 83 Network diagram Table 27 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Vlan-int11 2001:1::1/96 Loop0 2.2.2.9/32 PE 1 Loop0 1.1.1.9/32 Vlan-int12 172.2.1.1/24 Vlan-int11 2001:1::2/96 Vlan-int13 172.1.1.2/24 Vlan-int13 172.1.1.1/24 PE 2 Loop0 3.3.3.9/32 Vlan-int12 2001:2::2/96...
Page 326 [PE1-ospf-1] quit # Configure the P switch. <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...
Page 327 [P] mpls ldp [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...
Page 328 [PE2] interface vlan-interface 11 [PE2-Vlan-interface11] ip binding vpn-instance vpn1 [PE2-Vlan-interface11] ipv6 address 2001:3::2 96 [PE2-Vlan-interface11] quit [PE2] interface vlan-interface 13 [PE2-Vlan-interface13] ip binding vpn-instance vpn2 [PE2-Vlan-interface13] ipv6 address 2001:4::2 96 [PE2-Vlan-interface13] quit # Configure IP addresses for the CEs according to F igure 83.
Page 329 [PE1-bgp-default-vpn1] quit [PE1-bgp-default] ip vpn-instance vpn2 [PE1-bgp-default-vpn2] peer 2001:2::1 as-number 65420 [PE1-bgp-default-vpn2] address-family ipv6 unicast [PE1-bgp-default-ipv6-vpn2] peer 2001:2::1 enable [PE1-bgp-default-ipv6-vpn2] quit [PE1-bgp-default-vpn2] quit [PE1-bgp-default] quit # Configure PE 2 in the same way that PE 1 is configured. (Details not shown.) # Execute the display bgp peer ipv6 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 330: Configuring A Hub-Spoke Network
Destination: 2001:3::/96 Protocol : BGP4+ NextHop : ::FFFF:3.3.3.9 Preference: 255 Interface : Vlan13 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost [PE1] display ipv6 routing-table vpn-instance vpn2 Destinations : 6 Routes : 6...
Page 331 Configure EBGP between the Spoke-CEs and Spoke-PEs and between the Hub-CE and Hub-PE to exchange VPN routing information. Configure OSPF between the Spoke-PEs and Hub-PE to implement communication between the PEs. Configure MP-IBGP between the Spoke-PEs and Hub-PE to exchange VPN routing information.
Page 332 [Spoke-PE1-ospf-1] area 0 [Spoke-PE1-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255 [Spoke-PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0 [Spoke-PE1-ospf-1-area-0.0.0.0] quit [Spoke-PE1-ospf-1] quit # Configure Spoke-PE 2. <Spoke-PE2> system-view [Spoke-PE2] interface loopback 0 [Spoke-PE2-LoopBack0] ip address 3.3.3.9 32 [Spoke-PE2-LoopBack0] quit [Spoke-PE2] interface vlan-interface 5 [Spoke-PE2-Vlan-interface5] ip address 172.2.1.1 24 [Spoke-PE2-Vlan-interface5] quit [Spoke-PE2] ospf [Spoke-PE2-ospf-1] area 0...
Page 333 [Spoke-PE1-Vlan-interface4] mpls ldp enable [Spoke-PE1-Vlan-interface4] quit # Configure Spoke-PE 2. [Spoke-PE2] mpls lsr-id 3.3.3.9 [Spoke-PE2] mpls ldp [Spoke-PE2-ldp] quit [Spoke-PE2] interface vlan-interface 5 [Spoke-PE2-Vlan-interface5] mpls enable [Spoke-PE2-Vlan-interface5] mpls ldp enable [Spoke-PE2-Vlan-interface5] quit # Configure Hub-PE. [Hub-PE] mpls lsr-id 2.2.2.9 [Hub-PE] mpls ldp [Hub-PE-ldp] quit [Hub-PE] interface vlan-interface 4 [Hub-PE-Vlan-interface4] mpls enable...
Page 334 [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 [Hub-PE] ip vpn-instance vpn1-out [Hub-PE-vpn-instance-vpn1-out] route-distinguisher 100:4 [Hub-PE-vpn-instance-vpn1-out] vpn-target 111:1 export-extcommunity [Hub-PE-vpn-instance-vpn1-out] quit [Hub-PE] interface vlan-interface 6 [Hub-PE-Vlan-interface6] ip binding vpn-instance vpn1-in [Hub-PE-Vlan-interface6] ip address 13::2 24 [Hub-PE-Vlan-interface6] quit [Hub-PE] interface vlan-interface 7 [Hub-PE-Vlan-interface7] ip binding vpn-instance vpn1-out...
Page 335 # Configure Spoke-CE 2. <Spoke-CE2> system-view [Spoke-CE2] bgp 65420 [Spoke-CE2-bgp-default] peer 12::2 as-number 100 [Spoke-CE2-bgp-default] address-family ipv6 [Spoke-CE2-bgp-default-ipv6] peer 12::2 enable [Spoke-CE2-bgp-default-ipv6] import-route direct [Spoke-CE2-bgp-default-ipv6] quit [Spoke-CE2-bgp-default] quit # Configure Hub-CE. <Hub-CE> system-view [Hub-CE] bgp 65430 [Hub-CE-bgp-default] peer 13::2 as-number 100 [Hub-CE-bgp-default] peer 14::2 as-number 100 [Hub-CE-bgp-default] address-family ipv6 [Hub-CE-bgp-default-ipv6] peer 13::2 enable...
Page 336 [Hub-PE-bgp-default-vpn1-out] address-family ipv6 [Hub-PE-bgp-default-ipv6-vpn1-out] peer 14::1 enable [Hub-PE-bgp-default-ipv6-vpn1-out] peer 14::1 allow-as-loop 2 [Hub-PE-bgp-default-ipv6-vpn1-out] quit [Hub-PE-bgp-default-vpn1-out] quit [Hub-PE-bgp-default] quit # Execute the display bgp peer ipv6 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. (Details not shown.) Establish an MP-IBGP peer relationship between the Spoke-PEs and Hub-PE: # Configure Spoke-PE 1.
Page 337: Configuring Ipv6 Mpls L3Vpn Inter-As Option A
56 bytes from 12::1, icmp_seq=3 hlim=59 time=1.000 ms 56 bytes from 12::1, icmp_seq=4 hlim=59 time=0.000 ms --- Ping6 statistics for 12::1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.000/0.400/1.000/0.490 ms C onfiguring IPv6 MPLS L3VPN inter-AS option A 2 7 6 B N etwork requirements 5 3 7 B...
Page 338 C onfiguration procedure 5 3 8 B 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 PEs and ASBR-PEs in the same AS can learn the routes to the loopback interfaces of each other.
Page 339 # Execute the display mpls ldp peer command on the switches to verify that the session status is Operational, and that each PE and the ASBR-PE in the same AS have established an LDP neighbor relationship. (Details not shown.) Configure a VPN instance on the PEs: For the same VPN, the route targets for the VPN instance on the PE must match those for the VPN instance of the ASBR-PE in the same AS.
Page 340 [ASBR-PE2-vpn-vpn-vpn1] quit [ASBR-PE2] interface vlan-interface 12 [ASBR-PE2-Vlan-interface12] ip binding vpn-instance vpn1 [ASBR-PE2-Vlan-interface12] ipv6 address 2002:1::2 96 [ASBR-PE2-Vlan-interface12] quit # Execute the display ip vpn-instance command to display VPN instance configurations. Verify that each PE can ping its attached CE, and that ASBR-PE 1 and ASBR-PE 2 can ping each other.
Page 341 [PE1-bgp-default] peer 2.2.2.9 as-number 100 [PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [PE1-bgp-default] address-family vpnv6 [PE1-bgp-default-vpnv6] peer 2.2.2.9 enable [PE1-bgp-default-vpnv6] quit [PE1-bgp-default] quit # Configure ASBR-PE 1. [ASBR-PE1] bgp 100 [ASBR-PE1-bgp-default] ip vpn-instance vpn1 [ASBR-PE1-bgp-default-vpn1] peer 2002:1::2 as-number 200 [ASBR-PE1-bgp-default-vpn1] address-family ipv6 unicast [ASBR-PE1-bgp-default-ipv6-vpn1] peer 2002:1::2 enable [ASBR-PE1-bgp-default-ipv6-vpn1] quit [ASBR-PE1-bgp-default-vpn1] quit...
Page 342: Configuring Ipv6 Mpls L3Vpn Inter-As Option C
C onfiguring IPv6 MPLS L3VPN inter-AS option C 2 7 7 B N etwork requirements 5 4 0 B Site 1 and Site 2 belong to the same VPN. Site 1 accesses the network through PE 1 in AS 100, and Site 2 accesses the network through PE 2 in AS 600.
Page 343 # Establish an EBGP peer relationship with PE 1, and redistribute VPN routes. [CE1] bgp 65001 [CE1-bgp-default] peer 2001::1 as-number 100 [CE1-bgp-default] address-family ipv6 unicast [CE1-bgp-default-ipv6] peer 2001::1 enable [CE1-bgp-default-ipv6] import-route direct [CE1-bgp-default-ipv6] quit [CE1-bgp-default] quit Configure PE 1: # Run IS-IS on PE 1. <PE1>...
Page 344 [PE1-bgp-default] address-family ipv4 unicast [PE1-bgp-default-ipv4] peer 3.3.3.9 enable [PE1-bgp-default-ipv4] peer 3.3.3.9 label-route-capability [PE1-bgp-default-ipv4] quit # Configure the maximum hop count from PE 1 to EBGP peer 5.5.5.9 as 10. [PE1-bgp-default] peer 5.5.5.9 as-number 600 [PE1-bgp-default] peer 5.5.5.9 connect-interface loopback 0 [PE1-bgp-default] peer 5.5.5.9 ebgp-max-hop 10 # Configure peer 5.5.5.9 as a VPNv6 peer.
Page 345 # 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-default] peer 2.2.2.9 as-number 100...
Page 346 [ASBR-PE2-Vlan-interface11] quit # Configure 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 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 # Create routing policies.
Page 347 # Configure an LSR ID, and enable MPLS and LDP. [PE2] mpls lsr-id 5.5.5.9 [PE2] mpls ldp [PE2-ldp] quit # Configure 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 348: Configuring Ipv6 Mpls L3Vpn Carrier's Carrier In The Same As
[PE2-bgp-default] ip vpn-instance vpn1 [PE2-bgp-default-vpn1] peer 2002::2 as-number 65002 [PE2-bgp-default-vpn1] address-family ipv6 unicast [PE2-bgp-default-ipv6-vpn1] peer 2002::2 enable [PE2-bgp-default-ipv6-vpn1] quit [PE2-bgp-default-vpn1] quit [PE2-bgp-default] quit Configure CE 2: # Configure an IPv6 address for VLAN-interface 12. <CE2> system-view [CE2] interface vlan-interface 12 [CE2-Vlan-interface12] ipv6 address 2002::2 64 [CE2-Vlan-interface12] quit # Establish an EBGP peer relationship with PE 2, and redistribute VPN routes.
Page 349 Figure 87 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 350 [PE1-bgp-default] 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 state has been established between PE 1 and PE 2.
Page 351 [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 and the provider carrier: # Configure PE 1.
Page 352 # Configure PE 2 and CE 2 in the same way that PE 1 and CE 1 are configured. (Details not shown.) Connect end customers and 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-default] peer 2001:1::2 as-number 100...
Page 353 # 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 Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 3.3.3.9/32 Direct 127.0.0.1 InLoop0 4.4.4.9/32 IS_L1 30.1.1.2...
Page 354 Destinations : 21 Routes : 21 Destination/Mask Proto Pre Cost NextHop Interface 0.0.0.0/32 Direct 127.0.0.1 InLoop0 1.1.1.9/32 IS_L1 10.1.1.1 Vlan12 2.2.2.9/32 Direct 127.0.0.1 InLoop0 5.5.5.9/32 IS_L2 11.1.1.2 Vlan11 6.6.6.9/32 IS_L2 11.1.1.2 Vlan11 10.1.1.0/24 Direct 10.1.1.2 Vlan12 10.1.1.0/32 Direct 10.1.1.2 Vlan12 10.1.1.2/32 Direct 127.0.0.1...
Page 355: Configuring An Ospfv3 Sham Link
224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24 Direct 0.0.0.0 NULL0 255.255.255.255/32 Direct 127.0.0.1 InLoop0 # Verify that the VPN routing table contains 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...
Page 356 Figure 88 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 31 Interface and IP address assignment Device Interface IP address...
Page 357 [PE1-Vlan-interface12] mpls enable [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-default] peer 2.2.2.9 as-number 100 [PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0 [PE1-bgp-default] address-family vpnv6 [PE1-bgp-default-vpnv6] peer 2.2.2.9 enable [PE1-bgp-default-vpnv6] quit [PE1-bgp-default] quit # Configure OSPF on PE 1.
Page 358 [PE1] ip vpn-instance vpn1 [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-default] ip vpn-instance vpn1...
Page 359 [PE1] interface loopback 1 [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...
Page 360: Configuring Bgp As Number Substitution
Timers: Hello 10, Dead 40, Retransmit 5, Transmit delay 1 Request list: 0 Retransmit list: 0 C onfiguring BGP AS number substitution 2 8 0 B N etwork requirements 5 4 9 B As shown in F igure 89, CE 1 and CE 2 belong to VPN 1, and are connected to PE 1 and PE 2. The 8 5 0 H two CEs have the same AS number, 600.
Page 361 Configure BGP as the PE-CE routing protocol, and redistribute routes of the CEs into the PEs. For more information about basic IPv6 MPLS L3VPN configurations, see " C onfiguring IPv6 8 5 1 H MPLS L3VPNs." # Execute the display ipv6 routing-table command on CE 2 to verify that CE 2 has not learned the route to the VPN (100::/96) behind CE 1.
Page 362 Destination: 10:2::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 100::/96 Protocol : BGP4+ NextHop : ::FFFF:10.1.1.1 Preference: 255 Interface : Vlan-int11 Cost Destination: 200::/96 Protocol : BGP4+ NextHop : 10:2::2 Preference: 255 Interface : Vlan-int12 Cost Destination: FE80::/10 Protocol...
Page 363 [PE1-bgp-default-vpn1] quit [PE1-bgp-default] quit # Configure BGP AS number substitution on PE 2. <PE2> system-view [PE2] bgp 100 [PE2-bgp-default] ip vpn-instance vpn1 [PE2-bgp-default-vpn1] peer 10:2::2 substitute-as [PE2-bgp-default-vpn1] quit [PE2-bgp-default] quit V erifying the configuration 5 5 1 B # The output shows that among the routes advertised by PE 2 to CE 2, the AS_PATH of 100::/96 has changed from 100 600 to 100 100.
Page 364: Configuring Bgp As Number Substitution And Soo Attribute
NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 100::/96 Protocol : BGP4+ NextHop : 10:2::1 Preference: 255 Interface : Vlan-int12 Cost Destination: 200::/96 Protocol : Static NextHop : :: Preference: 60 Interface : NULL0 Cost Destination: FE80::/10 Protocol : Direct NextHop : ::...
Page 365 Table 33 Interface and IP address assignment Device Interface IP address Device Interface IP address CE 1 Loop0 100::1/96 CE 3 Loop0 200::1/96 Vlan-int2 10:1::1/96 Vlan-int7 10:3::1/96 CE 2 Vlan-int2 10:2::1/96 PE 2 Loop0 2.2.2.9/32 PE 1 Loop0 1.1.1.9/32 Vlan-int2 10:2::2/96 Vlan-int2 10:1::2/96...
Page 366 * >e Network : 200:: PrefixLen : 96 NextHop : 10:2::2 LocPrf PrefVal : 0 OutLabel : NULL Path/Ogn: 100 100? Configure BGP SoO attribute: # On PE 1, configure the SoO attribute as 1:100 for CE 1. <PE1> system-view [PE1] bgp 100 [PE1-bgp-default] ip vpn-instance vpn1 [PE1-bgp-default-vpn1] address-family ipv6...
Page 367: Configuring Mpls Oam
C onfiguring MPLS OAM Overview 1 1 2 B 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 368: 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 369: Configuring Bfd For Lsps
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 ipv4-address mask-length [ destination start-address an IPv4 prefix.
Page 370: Configuring Periodic Mpls Tracert For Lsps
Step Command Remarks option in BFD packets. This command takes effect only on BFD sessions that come up after this command is executed. 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 371: Configuring Bfd For Mpls Te Tunnels
C onfiguring BFD for MPLS TE tunnels 2 9 2 B To run BFD on an MPLS TE tunnel, configure both the local and remote devices as described T able 8 5 5 H Table 35 Configurations on the local and remote devices BFD session Execute the "mpls Execute the...
Page 372: Bfd For Lsp Configuration Example
BFD for LSP configuration example 1 1 7 B N etwork requirements 2 9 3 B Use LDP to establish an LSP from 1.1.1.9/32 to 3.3.3.9/32 and an LSP from 3.3.3.9/32 to 1.1.1.9/32. Use BFD to verify LSP connectivity. Figure 91 Network diagram C onfiguration procedure 2 9 4 B Configure IP addresses for interfaces.
Page 373: Verifying The Configuration
# 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 # Configure Switch B. [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...
Page 374 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 Remote Discr: 513 Source IP: 1.1.1.9 Destination IP: 127.0.0.1 Session State: Up Session Role: Passive Template Name: -...
Page 375: Configuring Mce
C onfiguring MCE 1 0 B This chapter describes MCE configuration. MPLS L3VPN overview 1 1 8 B 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 376 • 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 377: Mce Overview
• 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 378: Mce Configuration Task List
Figure 94 Network diagram for the MCE feature You can configure static routes, RIP, OSPF, IS-IS, EBGP, or IBGP between an MCE and a VPN site and between an MCE and a PE. NOTE: To implement dynamic IP assignment for DHCP clients in private networks, you can configure DHCP server or DHCP relay agent on the MCE.
Page 379: C Reating A Vpn Instance
C reating a VPN instance 2 9 8 B A VPN instance is a collection of the VPN membership and routing rules of its associated site. A VPN instance might correspond to more than one VPN. To create and configure a VPN instance: Step Command Remarks...
Page 380: Configuring Routing On An Mce
Step Command Remarks instance view. b. address-family ipv4 vpn-target vpn-target&<1-8> [ both | By default, no route targets are Configure route targets. export-extcommunity | configured. import-extcommunity ] By default, the number of active routes ain a VPN instance is not limited.
Page 381: C Onfiguring Routing Between An Mce And A Vpn Site
C onfiguring routing between an MCE and a VPN site 3 0 1 B You can configure static routing, RIP, OSPF, IS-IS, EBGP or IBGP between an MCE and a VPN site. C onfiguring static routing between an MCE and a VPN site 5 5 9 B An MCE can reach a VPN site through a static route.
Page 382 Step Command Remarks Enter system view. system-view Perform this configuration on the MCE. On a VPN site, create a common OSPF process. An OSPF process bound to a VPN instance does not use the public Create an OSPF process for ospf [ process-id | router-id network router ID configured in a VPN instance and enter...
Page 383 Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number Enable the IS-IS process on By default, no IS-IS process is isis enable [ process-id ] the interface. enabled on the interface. C onfiguring EBGP between an MCE and a VPN site 5 6 3 B To run EBGP between an MCE and a VPN site, you must configure a BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on the VPN site.
Page 384 Step Command Remarks EBGP peer. ipv4-address [ mask-length ] } peer groups exist. as-number as-number Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view. Enable BGP to exchange peer { group-name | By default, BGP does not IPv4 unicast routes with the ipv4-address [ mask-length ] } exchange IPv4 unicast routes...
Page 385: C Onfiguring Routing Between An Mce And A Pe
Configure a VPN site: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] By default, BGP is not enabled. [ multi-session-thread ] peer { group-name | Configure the MCE as an By default, no BGP peers or ipv4-address [ mask-length ] } IBGP peer.
Page 386 Step Command Remarks Create a RIP process for rip [ process-id ] vpn-instance a VPN instance and enter vpn-instance-name RIP view. Enable RIP on the By default, RIP is disabled on interface attached to the network network-address an interface. specified network. import-route protocol [ process-id | all-processes | allow-ibgp ] Redistribute the VPN...
Page 387 Step Command Remarks [ allow-direct | cost cost-value | routing protocol. cost-type { external | internal } | If you do not specify the route level [ level-1 | level-1-2 | level-2 ] | in the command, the command route-policy route-policy-name | tag redistributes routes to the level-2 tag ] * routing table by default.
Page 388: Displaying And Maintaining Mce
Step Command Remarks import-route protocol [ process-id | Redistribute the VPN routes all-processes ] [ allow-direct | med By default, no routes are of the VPN site. med-value | route-policy redistributed into BGP. route-policy-name ] * Displaying and maintaining MCE 1 2 3 B Execute display commands in any view.
Page 389 Figure 95 Network diagram C onfiguration procedure 5 7 2 B Assume that the system name of the MCE device is MCE, the system names of the edge devices of VPN 1 and VPN 2 are VR 1 and VR 2, respectively, and the system name of PE 1 is PE1. Configure the VPN instances on the MCE and PE 1: # On the MCE, configure VPN instances vpn1 and vpn2, and specify an RD and route targets for each VPN instance.
Page 390 [MCE-Vlan-interface20] ip binding vpn-instance vpn2 [MCE-Vlan-interface20] ip address 10.214.20.3 24 [MCE-Vlan-interface20] quit # On PE 1, configure VPN instances vpn1 and vpn2, and specify an RD and route targets for each VPN instance. <PE1> system-view [PE1] ip vpn-instance vpn1 [PE1-vpn-instance-vpn1] route-distinguisher 10:1 [PE1-vpn-instance-vpn1] vpn-target 10:1 [PE1-vpn-instance-vpn1] quit [PE1] ip vpn-instance vpn2...
Page 391 [MCE] ospf 2 vpn-instance vpn2 # Advertise subnet 10.214.20.0. [MCE-ospf-2] area 0 [MCE-ospf-2-area-0.0.0.0] network 10.214.20.0 0.0.0.255 [MCE-ospf-2-area-0.0.0.0] quit [MCE-ospf-2] quit # On VR 2, assign IP address 10.214.20.2/24 to the interface connected to MCE and 192.168.10.1/24 to the interface connected to VPN 2. (Details not shown.) # Configure OSPF process 2, and advertise subnets 192.168.10.0 and 10.214.20.0.
Page 392 [MCE-Vlan-interface40] ip binding vpn-instance vpn2 [MCE-Vlan-interface40] ip address 40.1.1.1 24 [MCE-Vlan-interface40] quit # On PE 1, bind VLAN-interface 30 to VPN instance vpn1, and configure an IP address for the VLAN interface. [PE1] interface vlan-interface 30 [PE1-Vlan-interface30] ip binding vpn-instance vpn1 [PE1-Vlan-interface30] ip address 30.1.1.2 24 [PE1-Vlan-interface30] quit # Bind VLAN-interface 40 to VPN instance vpn2, and configure an IP address for the VLAN...
Page 393: C Onfiguring The Mce That Uses Ebgp To Advertise Vpn Routes To The
30.1.1.0/24 Direct 30.1.1.2 Vlan30 30.1.1.0/32 Direct 30.1.1.2 Vlan30 30.1.1.2/32 Direct 127.0.0.1 InLoop0 30.1.1.255/32 Direct 30.1.1.2 Vlan30 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0 127.255.255.255/32 Direct 127.0.0.1 InLoop0 192.168.0.0/24 O_ASE2 150 1 30.1.1.1 Vlan30 224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24...
Page 394 Figure 96 Network diagram C onfiguration procedure 5 7 5 B Create VPN instances on the MCE and PE 1, and bind the VPN instances to VLAN interfaces. For the configuration procedure, see " C onfiguring the MCE that uses OSPF to advertise VPN 8 6 9 H routes to the PE."...
Page 395 10.214.10.3/32 Direct 127.0.0.1 InLoop0 10.214.10.255/32 Direct 10.214.10.3 Vlan10 127.0.0.0/8 Direct 127.0.0.1 InLoop0 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0 127.255.255.255/32 Direct 127.0.0.1 InLoop0 192.168.0.0/24 O_INTRA 10 10.214.10.2 Vlan10 224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24 Direct 0.0.0.0 NULL0 255.255.255.255/32 Direct 127.0.0.1 InLoop0 The output shows that the MCE has learned the private route of VPN 1 through OSPF process # On the MCE, bind OSPF process 20 to VPN instance vpn2 to learn the routes of VPN 2.
Page 396 # On PE 1, enable BGP in AS 200, and specify the MCE as its EBGP peer. [PE1] bgp 200 [PE1-bgp-default] ip vpn-instance vpn1 [PE1-bgp-default-vpn1] peer 30.1.1.1 as-number 100 [PE1-bgp-default-vpn1] address-family ipv4 [PE1-bgp-default-ipv4-vpn1] peer 30.1.1.1 enable [PE1-bgp-default-ipv4-vpn1] quit [PE1-bgp-default-vpn1] quit [PE1-bgp-default] quit # Use similar procedures to configure VPN 2 settings on MCE and PE 1.
Page 397 224.0.0.0/24 Direct 0.0.0.0 NULL0 255.255.255.255/32 Direct 127.0.0.1 InLoop0 The MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables...
Page 398: C Onfiguring Ipv6 Mce
C onfiguring IPv6 MCE 1 1 B This chapter describes IPv6 MCE configuration. IPv6 MPLS L3VPN overview 1 2 5 B IPv6 MPLS L3VPN uses BGP to advertise IPv6 VPN routes and uses MPLS to forward IPv6 VPN packets on the service provider backbone. F igure 97 shows a typical IPv6 MPLS L3VPN model.
Page 399: Configuring Vpn Instances
Tasks at a glance (Required.) Configuring routing between an MCE and a PE 8 7 9 H Configuring VPN instances 1 2 8 B By configuring VPN instances on a PE, you isolate not only VPN routes from public network routes, but also routes between VPNs.
Page 400: C Onfiguring Route Related Attributes For A Vpn Instance
Step Command Remarks interface after configuring this command. C onfiguring route related attributes for a VPN instance 3 0 7 B Step Command Remarks Enter system view. system-view • Enter VPN instance view: Configurations made in VPN ip vpn-instance instance view apply to both IPv4 vpn-instance-name VPN and IPv6 VPN.
Page 401: Configuring Routing On An Mce
Configuring routing on an MCE 1 2 9 B An MCE implements service isolation through route isolation. MCE routing configuration includes the following: • MCE-VPN site routing configuration. • MCE-PE routing configuration. On a PE in an MCE network environment, perform the following tasks: •...
Page 402 To configure RIPng between an MCE and a VPN site: Step Command Remarks Enter system view. system-view Create a RIPng process for a Perform this configuration on the ripng [ process-id ] vpn-instance VPN instance and enter MCE. On a VPN site, configure vpn-instance-name RIPng view.
Page 403 C onfiguring IPv6 IS-IS between an MCE and a VPN site 5 8 0 B An IPv6 IS-IS process belongs to the public network or a single IPv6 VPN instance. If you create an IPv6 IS-IS process without binding it to an IPv6 VPN instance, the process belongs to the public network.
Page 404 Step Command Remarks view. Enable BGP to exchange peer { group-name | By default, BGP does not IPv6 unicast routes with the ipv6-address [ prefix-length ] } exchange IPv6 unicast routes specified peer. enable with any peer. import-route protocol Redistribute remote site [ { process-id | all-processes } By default, no route routes advertised by the...
Page 405: C Onfiguring Routing Between An Mce And A Pe
Step Command Remarks IPv6 unicast routes with the ipv6-address [ prefix-length ] } exchange IPv6 unicast routes peer. enable with any peer. By default, no RR or RR client is configured. After you configure a VPN site as an IBGP peer, the MCE does (Optional.) Configure the not advertise the BGP routes peer { group-name |...
Page 406 C onfiguring IPv6 static routing between an MCE and a PE 5 8 3 B Step Command Remarks Enter system view. system-view ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length Configure an IPv6 { interface-type interface-number By default, no IPv6 static static route for an IPv6 [ next-hop-address ] | nexthop-address [ public ] routes are configured.
Page 407 Step Command Remarks tag tag | type type ] * Return to system view. quit interface interface-type Enter interface view. interface-number Enable the OSPFv3 process ospfv3 process-id area area-id By default, OSPFv3 is disabled on on the interface. [ instance instance-id ] an interface.
Page 408 Step Command Remarks import-route protocol [ { process-id | all-processes } By default, no routes are Redistribute VPN routes. [ allow-direct | med med-value | redistributed into BGP. route-policy route-policy-name ] C onfiguring IBGP between an MCE and a PE 5 8 8 B Step Command...
Page 409: C Onfiguration Procedure
Figure 98 Network diagram VPN 2 Site 1 PE 2 PE 1 Vlan-int30: 30::2/64 Vlan-int40: 40::2/64 PE 3 Vlan-int10 VPN 1 VPN 1 Vlan-int30: 30::1/64 2001:1::2/64 Site 2 2012:1::/64 Vlan-int40: 40::1/64 Vlan-int11 Vlan-int10 2012:1::2/64 2001:1::1/64 VR 1 Vlan-int20 2002:1::1/64 Vlan-int20 2002:1::2/64 VR 2 Vlan-int21...
Page 410 [MCE-Vlan-interface10] ipv6 address 2001:1::1 64 [MCE-Vlan-interface10] quit # Bind VLAN-interface 20 to VPN instance vpn2, and configure an IPv6 address for the VLAN interface. [MCE] interface vlan-interface 20 [MCE-Vlan-interface20] ip binding vpn-instance vpn2 [MCE-Vlan-interface20] ipv6 address 2002:1::1 64 [MCE-Vlan-interface20] quit # On PE 1, configure VPN instances vpn1 and vpn2, and specify an RD and route targets for each VPN instance.
Page 411 [VR2-Vlan-interface21] quit # On the MCE, display the routing tables of VPN instances vpn1 and vpn2. [MCE] 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::/64 Protocol...
Page 412 Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost The output shows that the MCE has learned the private route of VPN 2. The MCE maintains the routes of VPN 1 and VPN 2 in two different routing tables.
Page 413: Erifying The Configuration
# On PE 1, enable OSPFv3 process 10 and bind the process to VPN instance vpn1. [PE1] ospfv3 10 vpn-instance vpn1 [PE1-ospf-10] router-id 100.100.10.1 [PE1-ospf-10] quit # Enable OSPFv3 on VLAN-interface 30. [PE1] interface vlan-interface 30 [PE1-Vlan-interface30] ospfv3 10 area 0.0.0.0 [PE1-Vlan-interface30] quit # Configure OSPFv3 process 20 between the MCE and PE 1.
Page 414 NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 40::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan40 Cost Destination: 40::2/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012::/64 Protocol : O_ASE2 NextHop : FE80::200:FF:FE0F:5...
Page 415: D Ocument Conventions And Icons
D ocument conventions and icons 1 2 B Conventions 1 3 2 B This section describes the conventions used in the documentation. P ort numbering in examples 5 8 9 B The port numbers in this document are for illustration only and might be unavailable on your device. C ommand conventions 5 9 0 B Convention...
Page 416: Network Topology Icons
Network topology icons 1 3 3 B 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 417: S Upport And Other Resources
Accessing Hewlett Packard Enterprise Support 1 3 4 B • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: w ww.hpe.com/assistance 3 1 8 H • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: w ww.hpe.com/support/hpesc...
Page 418: W Ebsites
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 ( ocsfeedback@hpe.com). When submitting your feedback, include the document title, 3 3 8 H...
Page 419 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 420 Index IPv6 MPLS L3VPN BGP AS number substitution configuration, 3 52 accepting 9 1 3 H IPv6 MPLS L3VPN BGP AS number LDP label acceptance policy, substitution+SoO attribute configuration, 3 14, 3 56 8 8 3 H 9 1 4 H 9 1 5 H adjacency IPv6 MPLS L3VPN inter-AS IPv6 VPN...
Page 421 IPv6 MCE VPN instance route related MPLS TE CRLSP hot standby backup, 9 7 7 H attributes, 3 92 MPLS TE CRLSP ordinary backup, 9 4 7 H 9 7 8 H IPv6 MPLS L3VPN VPN instance route backoff mechanism (LDP), 9 7 9 H related attributes, 3 02...
Page 422 MPLS L3VPN carrier's carrier configuration MPLS L3VPN Level 1 carrier, 1 89 1 0 6 1 H (different ASs), 2 58 MPLS L3VPN Level 2 carrier, 1 89 1 0 2 5 H 1 0 6 2 H MPLS L3VPN carrier's carrier configuration (same AS), 2 50 IPv6 MPLS L3VPN BGP VPNv6 route...
Page 423 IPv6 LDP LSP, IPv6 MPLS L3VPN PE-CE RIPng, 3 04 1 1 0 2 H 1 1 4 9 H IPv6 MCE, 3 90, 3 90, 4 00 IPv6 MPLS L3VPN PE-CE routing, 3 03 1 1 0 3 H 1 1 0 4 H 1 1 0 5 H 1 1 5 0 H...
Page 424 MPLS L3VPN, 1 79, 1 99, 2 21 MPLS OAM tracert for LSP (periodic), 3 62 1 2 0 0 H 1 2 0 1 H 1 2 0 2 H 1 2 5 1 H MPLS L3VPN basics, 2 00, 2 21 MPLS OAM tracert for MPLS TE tunnel, 3 62...
Page 425 RSVP, 1 57, 1 60, 1 65 MPLS TE FRR node fault detection, 1 2 9 8 H 1 2 9 9 H 1 3 0 0 H 1 3 5 1 H RSVP authentication (interface view), 1 62 MPLS TE FRR node protection, 1 3 0 1 H 1 3 5 2 H RSVP authentication (RSVP neighbor...
Page 426 IPv6 LDP configuration, MPLS L3VPN BGP AS number substitution 1 3 9 6 H configuration, 2 86 IPv6 LDP label acceptance control, 1 4 4 0 H 1 3 9 7 H MPLS L3VPN BGP AS number substitution+SoO IPv6 LDP label advertisement control, 1 3 9 8 H attribute configuration, 2 89...
Page 427 RSVP-TE tunnel establishment, 1 65 EBGP 1 4 8 0 H static CRLSP configuration, 1 50, 1 51 IPv6 MCE-PE EBGP, 3 99 1 4 8 1 H 1 4 8 2 H 1 5 1 8 H static LSP configuration, IPv6 MCE-PE routing, 3 97 1 4 8 3 H...
Page 428 MPLS TE tunnel (static CRLSP), MPLS forwarding split horizon, 1 5 6 0 H 1 5 9 8 H MPLS TE tunnel with RSVP-TE, MPLS forwarding statistics, 1 5 6 1 H 1 5 9 9 H RSVP TE tunnel, 1 65 MPLS L3VPN packet forwarding, 1 82...
Page 429 LDP LSP generation policy, MPLS TE attribute advertisement, 1 6 3 8 H 1 6 7 7 H Graceful Restart (GR) MPLS TE CRLSP flooding, 1 6 7 8 H LDP GR, MPLS TE link attribute advertisement (IGP TE 1 6 3 9 H extension), LDP GR configuration, 1 6 7 9 H...
Page 430 MPLS L3VPN loopback address MPLS OAM BFD for LSP, 3 64 1 7 6 9 H redistribution, 2 16 MPLS OAM configuration, 3 59 1 7 1 9 H 1 7 7 0 H MPLS L3VPN loopback interface, 2 15 IPv6 1 7 2 0 H IP routing...
Page 431 inter-AS IPv6 VPN option C, 3 12 MPLS TE link attribute advertisement (IS-IS 1 8 2 0 H TE), inter-AS IPv6 VPN option C ASBR, 3 12 1 8 6 8 H 1 8 2 1 H inter-AS IPv6 VPN option C PE, 3 12 1 8 2 2 H MPLS L3VPN inter-AS VPN,...
Page 432 switched path. Use L SP LFIB 1 9 1 5 H switching router. Use L SR MPLS control plane, 1 9 1 6 H 1 9 6 3 H labeling MPLS forwarding plane, 1 9 6 4 H LDP label acceptance policy, MPLS forwarding process, 1 9 1 7 H 1 9 6 5 H...
Page 433 IPv6 LDP configuration, MPLS TTL propagation, 1 9 9 8 H 2 0 5 0 H IPv6 LDP label acceptance control, MPLS TTL-expired message send, 1 9 9 9 H 2 0 5 1 H IPv6 LDP label advertisement control, 2 0 0 0 H IPv6 LDP LSP configuration, 2 0 0 1 H...
Page 434 MCE-VPN site OSPF, 3 73 egress node label type advertisement, 2 0 9 5 H 2 1 3 7 H MCE-VPN site RIP, 3 73 enable, 2 0 9 6 H 2 1 3 8 H MCE-VPN site routing, 3 73 exclusive tunnel configuration, 1 76 2 0 9 7 H...
Page 435 preferred tunnel+selection order inter-AS option A configuration, 2 33 2 2 4 4 H configuration, 1 76 inter-AS option B configuration, 2 38 2 1 9 0 H 2 2 4 5 H protocols and standards, inter-AS option C configuration, 2 43 2 1 9 1 H 2 2 4 6 H...
Page 436 PE-CE EBGP, 2 04 CRLSP path selection control, 2 3 0 0 H 2 3 5 5 H PE-CE IBGP, 2 05 CRLSP RSVP-TE setup, 2 3 0 1 H 2 3 5 6 H PE-CE IS-IS, 2 03 CSPF path calculation, 2 3 0 2 H 2 3 5 7 H PE-CE OSPF,...
Page 437 MPLS L3VPN inter-AS option B tunnel setup, 2 4 5 3 H configuration, 2 38 tunnel traffic direction (automatic route 2 4 0 3 H MPLS L3VPN inter-AS option C advertisement), 2 4 5 4 H configuration, 2 43 tunnel traffic direction (static routing), 2 4 0 4 H 2 4 5 5 H MPLS L3VPN nested VPN,...
Page 438 IPv6 MPLS L3VPN carrier's carrier LDP label advertisement policy, 2 5 3 2 H configuration (same AS), 3 40 LDP label distribution control mode, 2 4 9 5 H 2 5 3 3 H IPv6 MPLS L3VPN configuration, 3 16 LDP loop detection, 2 4 9 6 H 2 5 3 4 H...
Page 439 MPLS L3VPN BGP AS number MPLS L3VPN networking scheme (extranet), 1 84 2 6 2 1 H substitution+SoO attribute configuration, 2 89 MPLS L3VPN networking scheme 2 5 8 2 H MPLS L3VPN BGP route flapping (hub-spoke), 1 83 2 6 2 2 H logging, 2 20 MPLS L3VPN OSPF area PE-CE...
Page 440 MPLS TE CSPF path calculation, MPLS L3VPN architecture, 1 79, 3 67 2 6 7 5 H 2 7 2 9 H 2 7 3 0 H MPLS TE DS-TE, 7 2, MPLS L3VPN configuration, 1 79, 1 99, 2 21 2 6 7 6 H 2 6 7 7 H 2 7 3 1 H...
Page 441 MPLS L3VPN hub-spoke network MPLS TE CRLSP establishment (PCE path configuration, 2 27 calculation), 2 7 8 1 H 2 8 1 8 H MPLS L3VPN OSPF area PE-CE MPLS TE CRLSP path selection, 2 8 1 9 H configuration, 1 94 MPLS TE CSPF calculation, 2 7 8 2 H...
Page 442 IPv6 MPLS L3VPN inter-AS IPv6 VPN option peer 3 12 LDP hello parameters, 2 8 5 7 H 2 9 0 1 H IPv6 MPLS L3VPN IPv6 MCE-VPN site LDP session parameters, 2 9 0 2 H routing, 3 93 LDP session protection, 2 8 5 8 H 2 9 0 3 H...
Page 443 configuring IPv6 LDP label advertisement configuring IPv6 MPLS L3VPN IPv6 MCE-VPN control, site routing, 3 93 2 9 3 6 H 2 9 7 3 H configuring IPv6 LDP LSP, configuring IPv6 MPLS L3VPN loopback 2 9 3 7 H interface, 3 13 configuring IPv6 MCE,...
Page 444 configuring MCE EBGP VPN route configuring MPLS L3VPN inter-AS VPN option advertisement, 3 85 2 09 3 0 0 9 H 3 0 4 9 H configuring MCE OSPF VPN route configuring MPLS L3VPN inter-AS VPN option advertisement, 3 80 2 09 3 0 1 0 H 3 0 5 0 H...
Page 445 configuring MPLS TE FRR, configuring RSVP authentication (interface 3 0 9 1 H view), 1 62 configuring MPLS TE FRR bypass tunnel on 3 1 2 2 H PLR, configuring RSVP authentication (RSVP neighbor 3 0 9 2 H view), 1 62 configuring MPLS TE FRR manual bypass 3 1 2 3 H...
Page 446 enabling MPLS TE route recording, MPLS, 3 1 7 0 H 3 2 0 5 H enabling MPLS TE SNMP notification, MPLS L3VPN, 1 99 3 1 7 1 H 3 2 0 6 H enabling MPLS TTL-expired message send, MPLS OAM, 3 60 3 1 7 2 H...
Page 447 RIPng IPv6 MPLS L3VPN BGP AS number substitution+SoO attribute configuration, 3 14, 3 56 IPv6 MCE-PE RIPng, 3 98 3 2 7 9 H 3 2 8 0 H 3 2 4 3 H IPv6 MPLS L3VPN carrier's carrier configuration IPv6 MCE-VPN site RIPng, 3 93 3 2 4 4 H...
Page 448 MCE-PE routing configuration, 3 77 MPLS L3VPN OSPF VPN extension, 1 94 3 3 2 1 H 3 3 5 8 H MCE-PE static routing, 3 77 MPLS L3VPN OSPF VPN on PE, 1 94 3 3 2 2 H 3 3 5 9 H MCE-VPN site EBGP, 3 75...
Page 449 Srefresh+reliable message delivery MPLS TTL-expired message send, 3 4 5 1 H configuration, 1 61 session 3 4 1 1 H tunnel establishment, 1 65 LDP message type, 3 4 1 2 H 3 4 5 2 H RSVP-TE LDP protection, 3 4 5 3 H LABEL object, 1 57...
Page 450 MPLS L3VPN egress PE VPN label MPLS TE bidirectional tunnel configuration, 1 20 3 5 2 3 H processing mode, 2 16 MPLS TE configuration, 6 6, 7 5, 3 4 8 7 H 3 5 2 4 H 3 5 2 5 H 3 5 2 6 H split horizon MPLS TE CRLSP backup configuration,...
Page 451 transit MPLS TE tunnel CRLSP configuration (PCE calculation), MPLS transit LSR, 3 6 1 0 H 3 5 6 4 H MPLS TE tunnel establishment (RSVP-TE), 1 02 transporting 3 6 1 1 H MPLS TE tunnel establishment (static LDP transport address, 3 5 6 5 H CRLSP), trapping...