HP FlexFabric 11900 Switch Series Layer 3 - IP Routing Configuration Guide Part number: 5998-5259 Software version: Release 2111 and later Document version: 6W100-20140110
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents Configuring basic IP routing········································································································································ 1 Routing table ······································································································································································ 1 Dynamic routing protocols ·······························································································································
Configuring RIP route redistribution····················································································································· 30 Tuning and optimizing RIP networks ···························································································································· 30 Configuration prerequisites ·································································································································· 30 Configuring RIP timers········
Configuring the P2MP network type for an interface ························································································ 73 Configuring the P2P network type for an interface ··························································································· 73 Configuring OSPF route control ··································································································································· 73 Configuration prerequisites ······························
OSPF NSSA area configuration example ········································································································ 106 OSPF DR election configuration example ········································································································· 108 OSPF virtual link configuration example ··········································································································· 112 OSPF GR configuration example ···································
Configuring routing domain authentication······································································································ 147 Configuring IS-IS GR ···················································································································································· 148 Configuring BFD for IS-IS············································································································································· 149 Configuring IS-IS F
Configuring the interval for sending updates for the same route ··································································· 225 Enabling BGP to establish an EBGP session over multiple hops ···································································· 225 Enabling immediate reestablishment of direct EBGP connections upon link failure····································· 226 Enabling 4-byte AS number suppression ···················································································
Configuring IPv6 static routing ······························································································································· 294 Configuring an IPv6 static route ································································································································· 294 Configuring BFD for IPv6 static routes ······················································································································· 295 Bidirectional cont
Configuring OSPFv3 received route filtering···································································································· 325 Configuring Inter-Area-Prefix LSA filtering ········································································································ 325 Configuring an OSPFv3 cost for an interface ·································································································· 325 Configuring the maximum number of OSPFv3 ECMP routes ···········
IPv6 PBR configuration examples ······························································································································· 363 Packet type-based IPv6 local PBR configuration example··············································································· 363 Packet type-based IPv6 interface PBR configuration example ········································································ 364 Configuring routing policies ············································
Configuring basic IP routing The term "interface" in this chapter collectively refers to Layer 3 interfaces, including VLAN interfaces and Layer 3 Ethernet interfaces. You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command (see Layer 2—LAN Switching Configuration Guide). IP routing directs IP packet forwarding on routers based on a routing table. This chapter focuses on unicast routing protocols.
A route entry includes the following key items: • Destination—IP address of the destination host or network. • Mask—Mask length of the IP address. • Pre—Preference of the route. Among routes to the same destination, the route with the highest preference is optimal. • Cost—If multiple routes to a destination have the same preference, the one with the smallest cost is the optimal route. • NextHop—Next hop. • Interface—Output interface.
Table 3 Route types and default route preferences Route type Preference Direct route 0 Multicast static route 1 OSPF 10 IS-IS 15 Unicast static route 60 RIP 100 OSPF ASE 150 OSPF NSSA 150 IBGP 255 EBGP 255 Unknown (route from an untrusted source) 256 Load sharing A routing protocol might find multiple optimal equal-cost routes to the same destination. You can use these routes to implement equal-cost multi-path (ECMP) load sharing.
Route redistribution Route redistribution enables routing protocols to learn routing information from each other. A dynamic routing protocol can redistribute routes from other routing protocols, including direct and static routing. For more information, see the respective chapters on those routing protocols in this configuration guide. The RIB records redistribution relationships of routing protocols.
Configuring the maximum lifetime for routes in the FIB When GR or NSR is disabled, FIB entries must be retained for some time after a protocol process switchover or RIB process switchover. When GR or NSR is enabled, FIB entries must be removed immediately after a protocol or RIB process switchover to avoid routing issues. Perform this task to meet such requirements. To configure the maximum lifetime for routes in the FIB (IPv4): Step Command Remarks 1. Enter system view. system-view N/A 2.
Displaying and maintaining a routing table Execute display commands in any view and reset commands in user view. Task Command Display routing table information. display ip routing-table [ vpn-instance vpn-instance-name ] [ verbose ] Display information about routes permitted by an IPv4 basic ACL. display ip routing-table [ vpn-instance vpn-instance-name ] acl acl-number [ verbose ] Display information about routes to a specific destination address.
Task Command Display IPv6 RIB GR state information. display ipv6 rib graceful-restart Display next hop information in the IPv6 RIB. display ipv6 rib nib [ self-originated ] [ nib-id ] [ verbose ] display ipv6 rib nib protocol protocol-name [ verbose ] Display next hop information for IPv6 direct routes. display ipv6 route-direct nib [ nib-id ] [ verbose ] Clear IPv6 route statistics.
Configuring static routing Static routes are manually configured. If a network's topology is simple, you only need to configure static routes for the network to work correctly. Static routes cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. Configuring a static route Before you configure a static route, complete the following tasks: • Configure the physical parameters for related interfaces.
Step 4. (Optional.) Delete all static routes, including the default route. Command Remarks delete [ vpn-instance vpn-instance-name ] static-routes all To delete one static route, use the undo ip route-static command. Configuring BFD for static routes IMPORTANT: Enabling BFD for a flapping route could worsen the situation. BFD provides a general-purpose, standard, medium-, and protocol-independent fast failure detection mechanism.
Step Command Remarks • Method 1: 2. Configure BFD control mode for a static route.
Configuring static route FRR A link or router failure on a path can cause packet loss and even routing loop. Static route fast reroute (FRR) uses BFD to detect failures and enables fast rerouting to minimize the impact of link or node failures. Figure 1 Network diagram As shown in Figure 1, upon a link failure, FRR specifies a backup next hop by using a routing policy for routes matching the specified criteria. Packets are directed to the backup next hop to avoid traffic interruption.
Step Command Remarks • Method 1: 3. Configure static route FRR.
Figure 2 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure static routes: # Configure a default route on Switch A. system-view [SwitchA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2 # Configure two static routes on Switch B. system-view [SwitchB] ip route-static 1.1.2.0 255.255.255.0 1.1.4.1 [SwitchB] ip route-static 1.1.3.0 255.255.255.0 1.1.5.6 # Configure a default route on Switch C.
Summary Count : 2 Static Routing table Status : Summary Count : 2 Destination/Mask Proto 1.1.2.0/24 Static 60 Pre Cost NextHop Interface 0 1.1.4.1 Vlan500 Static Routing table Status : Summary Count : 0 # Use the ping command on Host B to test the reachability of Host A (Windows XP runs on the two hosts). C:\Documents and Settings\Administrator>ping 1.1.2.2 Pinging 1.1.2.2 with 32 bytes of data: Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.
Figure 3 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int10 12.1.1.1/24 Switch B Vlan-int10 12.1.1.2/24 Vlan-int11 10.1.1.102/24 Vlan-int13 13.1.1.1/24 Vlan-int11 10.1.1.100/24 Vlan-int13 13.1.1.2/24 Switch C Configuration procedure 1. Configure IP addresses for the interfaces. (Details not shown.) 2.
Verifying the configuration # Display BFD sessions on Switch A. display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 4/7 12.1.1.1 12.1.1.2 Up 2000ms Vlan10 The output shows that the BFD session has been created. # Display the static routes on Switch A.
BFD for static routes configuration example (indirect next hop) Network requirements In Figure 4, Switch A has a route to interface Loopback 1 (2.2.2.9/32) on Switch B, with the output interface VLAN-interface 10. Switch B has a route to interface Loopback 1 (1.1.1.9/32) on Switch A, with the output interface VLAN-interface 12. Switch D has a route to 1.1.1.9/32, with the output interface VLAN-interface 10, and a route to 2.2.2.9/32, with the output interface VLAN-interface 12.
[SwitchB] bfd multi-hop min-transmit-interval 500 [SwitchB] bfd multi-hop min-receive-interval 500 [SwitchB] bfd multi-hop detect-multiplier 9 [SwitchB] ip route-static 121.1.1.0 24 1.1.1.9 bfd control-packet bfd-source 2.2.2.9 [SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 preference 65 [SwitchB] quit # Configure static routes on Switch C. system-view [SwitchC] ip route-static 120.1.1.0 24 13.1.1.1 [SwitchC] ip route-static 121.1.1.0 24 10.1.1.
Summary Count : 1 Destination/Mask Proto 120.1.1.0/24 Static 65 Pre Cost NextHop Interface 0 10.1.1.100 Vlan11 Static Routing table Status : Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 11.
[SwitchS] display ip routing-table 4.4.4.4 verbose Summary Count : 1 Destination: 4.4.4.4/32 Protocol: Static SubProtID: 0x0 Cost: 0 Tag: 0 OrigTblID: 0x0 TableID: 0x2 NBRID: 0x26000002 AttrID: 0xffffffff Process ID: 0 Age: 04h20m37s Preference: 60 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.
Configuring a default route A default route is used to forward packets that do not match any specific route entry in the routing table. Without a default route, packets that do not match any route entries are discarded. A default route can be configured in either of the following ways: • The network administrator can configure a default route with both destination and mask being 0.0.0.0. For more information, see "Configuring a static route.
Configuring RIP Routing Information Protocol (RIP) is a distance-vector IGP suited to small-sized networks. It employs UDP to exchange route information through port 520. Overview RIP uses a hop count to measure the distance to a destination. The hop count from a router to a directly connected network is 0. The hop count from a router to a directly connected router is 1. To limit convergence time, RIP restricts the metric range from 0 to 15.
2. RIP uses the received responses to update the local routing table and sends triggered update messages to its neighbors. All RIP routers on the network do this to learn latest routing information. 3. RIP periodically sends the local routing table to its neighbors. After a RIP neighbor receives the message, it updates its routing table, selects optimal routes, and sends an update to other neighbors. RIP ages routes to keep only valid routes. RIP versions There are two RIP versions, RIPv1 and RIPv2.
RIP configuration task list Tasks at a glance Configuring basic RIP: • (Required.) Enabling RIP • (Optional.) Controlling RIP reception and advertisement on interfaces • (Optional.) Configuring a RIP version (Optional.
If you configure RIP settings in interface view before enabling RIP, the settings do not take effect until RIP is enabled. If a physical interface is attached to multiple networks, you cannot advertise these networks in different RIP processes. You cannot enable multiple RIP processes on a physical interface. Enabling RIP on a network You can enable RIP on a network and specify a wildcard mask for the network. After that, only the interface attached to the network runs RIP.
Step Command Remarks 5. Enter interface view. interface interface-type interface-number N/A 6. Enable an interface to receive RIP messages. rip input By default, a RIP-enabled interface can receive RIP messages. 7. Enable an interface to send RIP messages. rip output By default, a RIP-enabled interface can send RIP messages. Configuring a RIP version You can configure a global RIP version in RIP view or an interface-specific RIP version in interface view.
Configuring an additional routing metric An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIP route. An outbound additional metric is added to the metric of a sent route, and it does not change the route's metric in the routing table. An inbound additional metric is added to the metric of a received route before the route is added into the routing table, and the route's metric is changed.
For example, suppose contiguous subnets routes 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24 exist in the routing table. You can create a summary route 10.1.0.0/16 on Ethernet 1/1 to advertise the summary route instead of the more specific routes. To configure a summary route: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIP view. rip [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Disable RIPv2 automatic route summarization.
Step Command Remarks 3. Enable RIP to advertise a default route. default-route { only | originate } [ cost cost ] By default, RIP does not advertise a default route. 4. Return to system view. quit N/A 5. Enter interface view. interface interface-type interface-number N/A 6. Configure the RIP interface to advertise a default route.
To configure a preference for RIP: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIP view. rip [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Configure a preference for RIP. preference [ route-policy route-policy-name ] value The default setting is 100. Configuring RIP route redistribution Perform this task to configure RIP to redistribute routes from other routing protocols, including OSPF, IS-IS, BGP, static, and direct.
• Suppress timer—Specifies how long a RIP route stays in suppressed state. When the metric of a route is 16, the route enters the suppressed state. A suppressed route can be replaced by an updated route that is received from the same neighbor before the suppress timer expires and has a metric less than 16. • Garbage-collect timer—Specifies the interval from when the metric of a route becomes 16 to when it is deleted from the routing table. RIP advertises the route with a metric of 16.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable poison reverse. rip poison-reverse By default, poison reverse is disabled. Configuring the maximum number of ECMP routes Perform this task to implement load sharing over ECMP routes. To configure the maximum number of ECMP routes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIP view.
Enabling source IP address check on incoming RIP updates Perform this task to enable source IP address check on incoming RIP updates. Upon receiving a message on an Ethernet interface, RIP compares the source IP address of the message with the IP address of the interface. If they are not in the same network segment, RIP discards the message. Upon receiving a message on a serial interface, RIP checks whether the source address of the message is the IP address of the peer interface.
If the specified neighbor is not directly connected, disable source address check on incoming updates. • To specify a RIP neighbor: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIP view. rip [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Specify a RIP neighbor. peer ip-address By default, RIP does not unicast updates to any peer. 4.
Setting the maximum length of RIP packets NOTE: The supported maximum length of RIP packets varies by vendor. Use this feature with caution to avoid compatibility issues. The packet length of RIP packets determines how many routes can be carried in a RIP packet. Set the maximum length of RIP packets to make good use of link bandwidth.
Step Command Remarks 2. Enter RIP view. rip [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Enable GR for RIP. graceful-restart By default, RIP GR is disabled. Configuring BFD for RIP RIP detects route failures by periodically sending requests. If it receives no response for a route within a certain time, RIP considers the route unreachable. This detection mechanism is not fast enough. To speed up convergence, perform this task to enable BFD for RIP.
Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the source IP address of BFD echo packets. bfd echo-source-ip ip-address By default, no source IP address is configured for BFD echo packets. 3. Enter interface view. interface interface-type interface-number N/A 4. Enable BFD for RIP. rip bfd enable destination ip-address By default, BFD for RIP is disabled. Configuring bidirectional control detection Step Command Remarks 1. Enter system view.
In Figure 6, configure FRR on Router B by using a routing policy to specify a backup next hop. When the primary link fails, RIP directs packets to the backup next hop. At the same time, RIP calculates the shortest path based on the new network topology, and forwards packets over that path after network convergence. Configuration restrictions and guidelines • RIP FRR takes effect only for RIP routes learned from directly connected neighbors. • Do not use RIP FRR and BFD for RIP at the same time.
RIP configuration examples Configuring basic RIP Network requirements As shown in Figure 7, enable RIPv2 on all interfaces on Switch A and Switch B. Configure Switch B to not advertise route 10.2.1.0/24 to Switch A, and to accept only route 2.1.1.0/24 from Switch A. Figure 7 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure basic RIP by using either of the following methods: (Method 1) # Enable RIP on the specified networks on Switch A.
Destination/Mask Nexthop Cost Tag Flags Sec 10.0.0.0/8 192.168.1.2 1 0 RAOF 11 The output shows that RIPv1 uses a natural mask. 3. Configure a RIP version: # Configure RIPv2 on Switch A. [SwitchA] rip [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] quit # Configure RIPv2 on Switch B. [SwitchB] rip [SwitchB-rip-1] version 2 [SwitchB-rip-1] undo summary [SwitchB-rip-1] quit # Display the RIP routing table on Switch A.
[SwitchB-rip-1] quit # Display the RIP routing table on Switch A. [SwitchA] display rip 100 route Route Flags: R - RIP A - Aging, S - Suppressed, G - Garbage-collect O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------Peer 192.168.1.2 on Vlan-interface100 Destination/Mask Nexthop Cost Tag Flags Sec 10.1.1.0/24 192.168.1.2 1 0 RAOF 19 # Display the RIP routing table on Switch B.
[SwitchA-rip-100] undo summary [SwitchA-rip-100] quit # Enable RIP 100 and RIP 200, and configure RIPv2 on Switch B. system-view [SwitchB] rip 100 [SwitchB-rip-100] network 11.0.0.0 [SwitchB-rip-100] version 2 [SwitchB-rip-100] undo summary [SwitchB-rip-100] quit [SwitchB] rip 200 [SwitchB-rip-200] network 12.0.0.0 [SwitchB-rip-200] version 2 [SwitchB-rip-200] undo summary [SwitchB-rip-200] quit # Enable RIP 200, and configure RIPv2 on Switch C.
# Display the IP routing table on Switch C. [SwitchC] display ip routing-table Destinations : 15 Routes : 15 Destination/Mask Proto 0.0.0.0/32 10.2.1.0/24 Pre Cost NextHop Interface Direct 0 0 127.0.0.1 InLoop0 RIP 100 1 12.3.1.1 Vlan200 11.1.1.0/24 RIP 100 1 12.3.1.1 Vlan200 12.3.1.0/24 Direct 0 0 12.3.1.2 Vlan200 12.3.1.0/32 Direct 0 0 12.3.1.2 Vlan200 12.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0 12.3.1.255/32 Direct 0 0 12.3.1.2 Vlan200 16.4.1.
[SwitchA] rip 1 [SwitchA-rip-1] network 1.0.0.0 [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] quit # Configure Switch B. system-view [SwitchB] rip 1 [SwitchB-rip-1] network 1.0.0.0 [SwitchB-rip-1] version 2 [SwitchB-rip-1] undo summary # Configure Switch C. system-view [SwitchB] rip 1 [SwitchC-rip-1] network 1.0.0.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary # Configure Switch D. system-view [SwitchD] rip 1 [SwitchD-rip-1] network 1.0.0.
1.0.0.0/8, auto-summary 1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface 1.1.2.0/24, cost 0, nexthop 1.1.2.1, RIP-interface 1.1.3.0/24, cost 1, nexthop 1.1.1.2 1.1.4.0/24, cost 2, nexthop 1.1.1.2 1.1.5.0/24, cost 2, nexthop 1.1.1.2 The output shows that only one RIP route reaches network 1.1.5.0/24, with the next hop as Switch B (1.1.1.2) and a cost of 2.
[SwitchB-ospf-1-area-0.0.0.0] quit # Configure Switch C. system-view [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit 3. Configure basic RIP: # Configure Switch C. [SwitchC] rip 1 [SwitchC-rip-1] network 11.3.1.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary # Configure Switch D.
4. Configure route summarization: # Configure route summarization on Switch C and advertise only the summary route 10.0.0.0/8. [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] rip summary-address 10.0.0.0 8 # Display the IP routing table on Switch D. [SwitchD] display ip routing-table Destinations : 12 Routes : 12 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 Pre 0 127.0.0.1 InLoop0 10.0.0.0/8 RIP 1 11.3.1.1 Vlan300 11.3.1.0/24 Direct 0 0 11.3.1.
Figure 11 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure basic RIP: # Configure Switch A. system-view [SwitchA] rip 1 [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] network 192.168.1.
[SwitchC-rip-1] network 192.168.3.0 [SwitchC-rip-1] import-route static [SwitchC-rip-1] quit Configure BFD parameters on VLAN-interface 100 of Switch A. 3. [SwitchA] bfd session init-mode active [SwitchA] bfd echo-source-ip 11.11.11.
display ip routing-table 120.1.1.0 24 verbose Summary Count : 1 Destination: 120.1.1.0/24 Protocol: RIP SubProtID: 0x1 Cost: 1 Tag: 0 OrigTblID: 0x0 TableID: 0x2 NBRID: 0x26000002 AttrID: 0xffffffff Process ID: 2 Age: 04h20m37s Preference: 100 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 192.168.2.2 Flags: 0x1008c OrigNextHop: 192.168.2.2 Label: NULL RealNextHop: 192.168.2.
Figure 12 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure basic RIP and enable BFD on the interfaces: # Configure Switch A. system-view [SwitchA] rip 1 [SwitchA-rip-1] network 192.168.2.0 [SwitchA-rip-1] import-route static [SwitchA-rip-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] rip bfd enable destination 192.168.2.2 [SwitchA-Vlan-interface100] quit # Configure Switch B.
# Configure a static route on Switch C. [SwitchA] ip route-static 100.1.1.0 24 null 0 Verifying the configuration # Display BFD session information on Switch A. display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 session working under Echo mode: LD SourceAddr DestAddr State Holdtime Interface 3 192.168.2.1 192.168.2.2 Up 2000ms vlan100 # Display routes destined for 100.1.1.0/24 on Switch B. display ip routing-table 100.1.1.
Label: NULL RealNextHop: 192.168.3.2 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid BkTunnel ID: Invalid Interface: vlan-interface 200 BkInterface: N/A Configuring BFD for RIP (bidirectional detection in BFD control packet mode) Network requirements As shown in Figure 13, VLAN-interface 100 of Switch A and VLAN-interface 200 of Switch C run RIP process 1. VLAN-interface 300 of Switch A runs RIP process 2.
# Configure Switch A. system-view [SwitchA] rip 1 [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] network 192.168.1.0 [SwitchA-rip-1] network 101.1.1.0 [SwitchA-rip-1] peer 192.168.2.
[SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit # Configure Switch C. [SwitchC] bfd session init-mode active [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] bfd min-transmit-interval 500 [SwitchC-Vlan-interface200] bfd min-receive-interval 500 [SwitchC-Vlan-interface200] bfd detect-multiplier 7 [SwitchC-Vlan-interface200] quit 4. Configure static routes: # Configure a static route to Switch C on Switch A. [SwitchA] ip route-static 192.168.2.
display ip routing-table 100.1.1.0 24 verbose Summary Count : 1 Destination: 100.1.1.0/24 Protocol: RIP Process ID: 2 SubProtID: 0x1 Cost: 2 Tag: 0 OrigTblID: 0x0 TableID: 0x2 NBRID: 0x12000003 AttrID: 0xffffffff Age: 00h18m40s Preference: 100 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 192.168.3.2 Flags: 0x1008c OrigNextHop: 192.168.3.2 Label: NULL RealNextHop: 192.168.3.
[SwitchS-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 100 backup-nexthop 12.12.12.2 [SwitchS-route-policy-frr-10] quit [SwitchS] rip 1 [SwitchS-rip-1] fast-reroute route-policy frr [SwitchS-rip-1] quit # Configure Switch D. system-view [SwitchD] bfd echo-source-ip 3.3.3.3 [SwitchD] ip prefix-list abc index 10 permit 1.1.1.
Tag: 0 OrigTblID: 0x0 TableID: 0x2 NBRID: 0x26000002 AttrID: 0xffffffff State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 13.13.13.1 Flags: 0x1008c OrigNextHop: 13.13.13.1 Label: NULL RealNextHop: 13.13.13.1 BkLabel: NULL BkNextHop: 24.24.24.
Configuring OSPF Open Shortest Path First (OSPF) is a link-state IGP developed by the OSPF working group of the IETF. OSPF version 2 is used for IPv4. OSPF refers to OSPFv2 throughout this chapter. Overview OSPF has the following features: • Wide scope—Supports various network sizes and up to several hundred routers in an OSPF routing domain. • Fast convergence—Advertises routing updates instantly upon network topology changes. • Loop free—Computes routes with the SPF algorithm to avoid routing loops.
LSA types OSPF advertises routing information in Link State Advertisements (LSAs). The following LSAs are commonly used: • Router LSA—Type-1 LSA, originated by all routers and flooded throughout a single area only. This LSA describes the collected states of the router's interfaces to an area. • Network LSA—Type-2 LSA, originated for broadcast and NBMA networks by the designated router, and flooded throughout a single area only. This LSA contains the list of routers connected to the network.
Figure 15 Area-based OSPF network partition Area 4 Area 1 Area 0 Area 2 Area 3 Backbone area and virtual links Each AS has a backbone area that distributes routing information between non-backbone areas. Routing information between non-backbone areas must be forwarded by the backbone area. OSPF has the following requirements: • All non-backbone areas must maintain connectivity to the backbone area. • The backbone area must maintain connectivity within itself.
Figure 17 Virtual link application 2 Area 1 Virtual link R2 R1 Area 0 The virtual link between the two ABRs acts as a point-to-point connection. You can configure interface parameters, such as hello interval, on the virtual link as they are configured on a physical interface. The two ABRs on the virtual link unicast OSPF packets to each other, and the OSPF routers in between convey these OSPF packets as normal IP packets.
• Internal router—All interfaces on an internal router belong to one OSPF area. • ABR—Belongs to more than two areas, one of which must be the backbone area. ABR connects the backbone area to a non-backbone area. An ABR and the backbone area can be connected through a physical or logical link. • Backbone router—At least one interface of a backbone router must reside in the backbone area. All ABRs and internal routers in Area 0 are backbone routers.
destination of the Type-2 external route. If two Type-2 routes to the same destination have the same cost, OSPF takes the cost from the router to the ASBR into consideration to determine the best route. Route calculation OSPF computes routes in an area as follows: • Each router generates LSAs based on the network topology around itself, and sends them to other routers in update packets. • Each OSPF router collects LSAs from other routers to compose an LSDB.
• BDR—Elected along with the DR to establish adjacencies with all other routers. If the DR fails, the BDR immediately becomes the new DR, and other routers elect a new BDR. Routers other than the DR and BDR are called "DROthers." They do not establish adjacencies with one another, so the number of adjacencies is reduced. The role of a router is subnet (or interface) specific. It might be a DR on one interface and a BDR or DROther on another interface.
• RFC 3137, OSPF Stub Router Advertisement • RFC 4811, OSPF Out-of-Band LSDB Resynchronization • RFC 4812, OSPF Restart Signaling • RFC 4813, OSPF Link-Local Signaling OSPF configuration task list To run OSPF, you must first enable OSPF on the router. Make a proper configuration plan to avoid incorrect settings that can result in route blocking and routing loops. To configure OSPF, perform the following tasks: Tasks at a glance (Required.) Enabling OSPF (Optional.
Tasks at a glance (Optional.
• If you specify a router ID when you create an OSPF process, any two routers in an AS must have different router IDs. A common practice is to specify the IP address of an interface as the router ID. • If you specify no router ID when you create the OSPF process, the global router ID is used. HP recommends specifying a router ID when you create the OSPF process. OSPF supports multiple processes and VPNs: • To run multiple OSPF processes, you must specify an ID for each process.
Step Enter interface view. 2. Command Remarks interface interface-type interface-number N/A By default, OSPF is disabled on an interface. Enable an OSPF process on the interface. 3. ospf process-id area area-id [ exclude-subip ] If the specified OSPF process and area do not exist, the command creates the OSPF process and area. Disabling an OSPF process on an interface does not delete the OSPF process or the area.
Configuring an NSSA area A stub area cannot import external routes, but an NSSA area can import external routes into the OSPF routing domain while retaining other stub area characteristics. Do not configure the backbone area as an NSSA area or totally NSSA area. To configure an NSSA area, configure the nssa command on all the routers attached to the area. To configure a totally NSSA area, configure the nssa command on all the routers attached to the area and configure the nssa no-summary command on the ABR.
Step Command Remarks By default, no virtual link is configured. 4. vlink-peer router-id [ dead seconds | hello seconds | { { hmac-md5 | md5 } key-id { cipher cipher-string | plain plain-string } | simple { cipher cipher-string | plain plain-string } } | retransmit seconds | trans-delay seconds ] * Configure a virtual link. Configure this command on both ends of a virtual link, and the hello and dead intervals must be identical on both ends of the virtual link.
Step 3. 4. Command Remarks Configure the OSPF network type for the interface as broadcast. ospf network-type broadcast By default, the network type of an interface depends on the link layer protocol. (Optional.) Configure a router priority for the interface. ospf dr-priority priority The default router priority is 1.
Configuring the P2MP network type for an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A By default, the network type of an interface depends on the link layer protocol. After you configure the OSPF network type for an interface as P2MP unicast, all packets are unicast over the interface. The interface cannot broadcast hello packets to discover neighbors, so you must manually specify the neighbors.
• Enable OSPF. • Configure filters if routing information filtering is needed. Configuring OSPF route summarization Configure route summarization on an ABR or ASBR to summarize contiguous networks into a single network and distribute it to other areas. Route summarization reduces the routing information exchanged between areas and the size of routing tables, and improves routing performance. For example, three internal networks 19.1.1.0/24, 19.1.2.0/24, and 19.1.3.0/24 are available within an area.
Configuring received OSPF route filtering Perform this task to filter routes calculated using received LSAs. The following filtering methods are available: • Use an ACL or IP prefix list to filter routing information by destination address. • Use the gateway keyword to filter routing information by next hop. • Use an ACL or IP prefix list to filter routing information by destination address and at the same time use the gateway keyword to filter routing information by next hop.
used. If the calculated cost is less than 1, the value of 1 is used. If no cost or bandwidth reference value is configured for an interface, OSPF computes the interface cost based on the interface bandwidth and default bandwidth reference value. To configure an OSPF cost for an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure an OSPF cost for the interface.
Configuring OSPF preference A router can run multiple routing protocols, and each protocol is assigned a preference. If multiple routes are available to the same destination, the one with the highest protocol preference is selected as the best route. To configure OSPF preference: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a preference for OSPF.
Configuring OSPF to redistribute a default route The import-route command cannot redistribute a default external route. Perform this task to redistribute a default route. To redistribute a default route: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Redistribute a default route. By default, no default route is redistributed.
Tuning and optimizing OSPF networks You can use one of the following methods to optimize an OSPF network: • Change OSPF packet timers to adjust the convergence speed and network load. On low-speed links, consider the delay time for sending LSAs. • Change the SPF calculation interval to reduce resource consumption caused by frequent network changes. • Configure OSPF authentication to improve security.
Step Command Remarks By default: • The dead interval on P2P and broadcast interfaces is 40 seconds. 5. Specify the dead interval. • The dead interval on P2MP and NBMA interfaces is 120 seconds. ospf timer dead seconds The dead interval must be at least four times the hello interval on an interface. The default dead interval is restored when the network type for an interface is changed. The default setting is 5 seconds. 6. Specify the retransmission interval.
Step Command Remarks By default: 3. Specify the SPF calculation interval. spf-schedule-interval maximum-interval [ minimum-interval [ incremental-interval ] ] • The maximum interval is 5 seconds. • The minimum interval is 50 milliseconds. • The incremental interval is 200 milliseconds.
Step Command Remarks By default: • The maximum interval is 5 3. Configure the LSA generation interval. lsa-generation-interval maximum-interval [ minimum-interval [ incremental-interval ] ] seconds. • The minimum interval is 50 milliseconds. • The incremental interval is 200 milliseconds. Disabling interfaces from receiving and sending OSPF packets To enhance OSPF adaptability and reduce resource consumption, you can set an OSPF interface to "silent.
Step 2. 3. Command Remarks Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A Configure the router as a stub router. stub-router [ external-lsa [ max-metric-value ] | include-stub | on-startup { seconds | wait-for-bgp [ seconds ] } | summary-lsa [ max-metric-value ] ] * By default, the router is not configured as a stub router. A stub router has no associations with a stub area.
Step Command Remarks • Configure simple authentication: 3. Configure interface authentication mode. ospf authentication-mode simple { cipher cipher-string | plain plain-string } • Configure MD5 authentication: ospf authentication-mode { hmac-md5 | md5 } key-id { cipher cipher-string | plain plain-string } Use either method. By default, no authentication is configured.
Step Specify the maximum number of external LSAs in the LSDB. 3. Command Remarks lsdb-overflow-limit number By default, the maximum number of external LSAs in the LSDB is not limited. Configuring OSPF exit overflow interval When the number of LSAs in the LSDB exceeds the upper limit, the LSDB is in an overflow state. To save resources, OSPF does not receive any external LSAs and deletes the external LSAs generated by itself when in this state.
Step Command Remarks 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable compatibility with RFC 1583. rfc1583 compatible By default, this feature is enabled. Logging neighbor state changes Perform this task to enable output of neighbor state change logs to the information center. The information center processes the logs according to user-defined output rules (whether to output logs and where to output).
Step Command Remarks By default, SNMP notifications for OSPF is enabled. 3. Enable SNMP notifications for OSPF.
Step Enable OSPF ISPF. 3. Command Remarks ispf enable By default, OSPF ISPF is enabled. Configuring prefix suppression An OSPF interface by default advertises all its prefixes in LSAs. You can suppress interfaces from advertising all its prefixes to speed up OSPF convergence. This function also helps improve the network security by preventing IP routing toward the suppressed networks. When prefix suppression is enabled: • On P2P and P2MP networks, OSPF does not advertise Type-3 links in Router LSAs.
Step Command Remarks 2. Enter interface view. interface interface-type interface-number N/A 3. Enable prefix suppression on the interface. ospf prefix-suppression [ disable ] By default, prefix suppression is disabled on an interface. Configuring prefix prioritization This feature enables the device to install prefixes in descending priority order: critical, high, medium, and low. The prefix priorities are assigned through routing policies.
• GR restarter—Graceful restarting router. It must have GR capability. • GR helper—A neighbor of the GR restarter. It helps the GR restarter to complete the GR process. OSPF GR has the following types: • IETF GR—Uses Opaque LSAs to implement GR. • Non-IETF GR—Uses link local signaling (LLS) to advertise GR capability and uses out of band synchronization to synchronize the LSDB. A device can act as a GR restarter and GR helper at the same time.
Configuring OSPF GR helper You can configure the IETF or non IETF OSPF GR helper. Configuring the IETF OSPF GR helper Step Command Remarks 1. Enter system view. system-view N/A 2. Enable OSPF and enter its view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable opaque LSA reception and advertisement capability. opaque-capability enable By default, opaque LSA reception and advertisement capability is enabled. 4. (Optional.
Configuring BFD for OSPF BFD provides a single mechanism to quickly detect and monitor the connectivity of links between OSPF neighbors, which improves the network convergence speed. For more information about BFD, see High Availability Configuration Guide. OSPF supports the following BFD detection modes: • Bidirectional control detection—Requires BFD configuration to be made on both OSPF routers on the link.
Figure 21 Network diagram for OSPF FRR In Figure 21, configure FRR on Router B by using a routing policy to specify a backup next hop. When the primary link fails, OSPF directs packets to the backup next hop. At the same time, OSPF calculates the shortest path based on the new network topology, and forwards packets over the path after network convergence.
Step Command Remarks N/A 6. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * 7. Enable OSPF FRR to calculate a backup next hop by using the LFA algorithm. fast-reroute lfa [ abr-only ] By default, OSPF FRR is not configured. If abr-only is specified, the route to the ABR is selected as the backup path.
Task Command Display OSPF LSDB information (in IRF mode). display ospf [ process-id ] lsdb [ area area-id | brief | [ { asbr | ase | network | nssa | opaque-area | opaque-as | opaque-link | router | summary } [ link-state-id ] ] [ originate-router advertising-router-id | self-originate ] ] [ standby chassis chassis-number slot slot-number ] Display OSPF next hop information. display ospf [ process-id ] nexthop Display OSPF neighbor information (in standalone mode).
Task Command Reset an OSPF process. reset ospf [ process-id ] process [ graceful-restart ] Re-enable OSPF route redistribution. reset ospf [ process-id ] redistribution OSPF configuration examples These configuration examples only cover commands for OSPF configuration. Basic OSPF configuration example Network requirements • Enable OSPF on all switches, and split the AS into three areas. • Configure Switch A and Switch B as ABRs.
[SwitchB] ospf [SwitchB-ospf-1] area 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] quit [SwitchB-ospf-1] area 2 [SwitchB-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.2] quit [SwitchB-ospf-1] quit # Configure Switch C. system-view [SwitchC] router id 10.4.1.1 [SwitchC] ospf [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 10.4.1.0 0.0.0.
State: Full DR: 10.2.1.1 Mode: Nbr is Master BDR: 10.2.1.2 Priority: 1 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 32 sec Neighbor is up for 06:03:12 Authentication Sequence: [ 0 ] Neighbor state change count: 5 # Display OSPF routing information on Switch A. [SwitchA] display ospf routing OSPF Process 1 with Router ID 10.2.1.1 Routing Tables Routing for Network Destination Cost 10.2.1.0/24 1 Type NextHop 10.3.1.0/24 2 10.4.1.0/24 2 Stub 10.2.1.2 10.4.1.1 0.0.0.1 10.5.1.
--- Ping statistics for 10.4.1.1 --5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.779/1.408/1.702/0.323 ms OSPF route redistribution configuration example Network requirements • Enable OSPF on all the switches. • Split the AS into three areas. • Configure Switch A and Switch B as ABRs. • Configure Switch C as an ASBR to redistribute external routes (static routes). Figure 23 Network diagram Configuration procedure 1.
# Display the OSPF routing table on Switch D. display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 22 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.3.1.0/24 10 Transit 10.3.1.2 10.3.1.1 0.0.0.2 10.4.1.0/24 25 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.5.1.0/24 10 Stub 10.5.1.1 10.5.1.1 0.0.0.2 10.1.1.0/24 12 Inter 10.3.1.1 10.3.1.1 0.0.0.
Figure 24 Network diagram Vlan-int600 10.4.1.1/24 Vlan-int500 10.3.1.1/24 Vlan-int400 10.1.1.1/24 Vlan-int300 10.2.1.2/24 Switch E Switch D Vlan-int300 10.2.1.1/24 Vlan-int400 10.1.1.2/24 AS 100 Switch C Vlan-int200 11.1.1.2/24 EBGP Vlan-int200 11.1.1.1/24 Switch B Vlan-int100 11.2.1.1/24 Vlan-int100 11.2.1.2/24 AS 200 Switch A Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable OSPF: # Configure Switch A.
# Configure Switch D. system-view [SwitchD] router id 10.3.1.1 [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit # Configure Switch E. system-view [SwitchE] router id 10.4.1.1 [SwitchE] ospf [SwitchE-ospf-1] area 0 [SwitchE-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.
5. 0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0 10.1.1.0/24 OSPF 150 1 11.2.1.1 Vlan100 10.2.1.0/24 OSPF 150 1 11.2.1.1 Vlan100 10.3.1.0/24 OSPF 150 1 11.2.1.1 Vlan100 10.4.1.0/24 OSPF 150 1 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 0 11.2.1.2 Vlan100 11.2.1.0/32 Direct 0 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0 11.2.1.255/32 Direct 0 0 11.2.1.2 Vlan100 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 0 127.0.0.
• Configure Switch D as the ASBR to redistribute static routes. • Configure Area 1 as a stub area to reduce advertised LSAs without influencing reachability. Figure 25 Network diagram Switch A Area 0 Switch B Vlan-int100 10.1.1.1/24 Vlan-int100 10.1.1.2/24 Vlan-int200 10.2.1.1/24 Area 1 Stub Vlan-int200 10.2.1.2/24 Vlan-int200 10.3.1.1/24 Vlan-int200 10.3.1.2/24 Area 2 ASBR Switch C Vlan-int300 10.4.1.1/24 Vlan-int300 10.5.1.1/24 Switch D Configuration procedure 1.
10.1.1.0/24 5 Inter 10.2.1.1 10.2.1.1 0.0.0.1 Destination Cost Type Tag NextHop AdvRouter 3.1.2.0/24 1 Type2 1 10.2.1.1 10.5.1.1 Routing for ASEs Total Nets: 6 Intra Area: 2 Inter Area: 3 ASE: 1 NSSA: 0 Because Switch C resides in a normal OSPF area, its routing table contains an AS external route. 4. Configure Area 1 as a stub area: # Configure Switch A. system-view [SwitchA] ospf [SwitchA-ospf-1] area 1 [SwitchA-ospf-1-area-0.0.0.1] stub [SwitchA-ospf-1-area-0.0.0.
[SwitchA-ospf-1-area-0.0.0.1] quit # Display OSPF routing information on Switch C. [SwitchC] display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 4 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 3 Transit 10.2.1.2 10.4.1.1 0.0.0.1 10.4.1.0/24 3 Stub 10.4.1.1 0.0.0.1 10.4.1.
[SwitchA-ospf-1-area-0.0.0.1] nssa default-route-advertise no-summary [SwitchA-ospf-1-area-0.0.0.1] quit [SwitchA-ospf-1] quit # Configure Switch C. system-view [SwitchC] ospf [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.0.1] nssa [SwitchC-ospf-1-area-0.0.0.
10.3.1.0/24 10 Transit 10.3.1.2 10.3.1.1 0.0.0.2 10.4.1.0/24 25 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.5.1.0/24 10 Stub 10.5.1.1 10.5.1.1 0.0.0.2 10.1.1.0/24 12 Inter 10.3.1.1 10.3.1.1 0.0.0.2 Destination Cost Type Tag NextHop AdvRouter 3.1.3.0/24 1 Type2 1 10.3.1.1 10.2.1.1 Routing for ASEs Total Nets: 6 Intra Area: 2 Inter Area: 3 ASE: 1 NSSA: 0 The output shows an external route imported from the NSSA area exists on Switch D.
[SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. system-view [SwitchC] router id 3.3.3.3 [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. system-view [SwitchD] router id 4.4.4.4 [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.
Neighbor is up for 00:01:28 Authentication Sequence: [ 0 ] The output shows that Switch D is the DR and Switch C is the BDR. 3. Configure router priorities on interfaces: # Configure Switch A. [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] ospf dr-priority 100 [SwitchA-Vlan-interface1] quit # Configure Switch B. [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] ospf dr-priority 0 [SwitchB-Vlan-interface1] quit # Configure Switch C.
The output shows that the DR and BDR are not changed, because the priority settings do not take effect immediately. 4. Restart OSPF process: # Restart the OSPF process of Switch D. reset ospf 1 process Warning : Reset OSPF process? [Y/N]:y # Display neighbor information of Switch D. display ospf peer verbose OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 State: Full Address: 192.168.1.
192.168.1.1 Broadcast DR 1 100 192.168.1.1 192.168.1.3 [SwitchB] display ospf interface OSPF Process 1 with Router ID 2.2.2.2 Interfaces Area: 0.0.0.0 IP Address Type 192.168.1.2 Broadcast DROther State Cost Pri DR BDR 1 0 192.168.1.1 192.168.1.3 The interface state DROther means the interface is not the DR or BDR. OSPF virtual link configuration example Network requirements Configure a virtual link between Switch B and Switch C to connect Area 2 to the backbone area.
[SwitchB-ospf-1] quit # Configure Switch C. system-view [SwitchC] ospf 1 router-id 3.3.3.3 [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] quit [SwitchC-ospf-1] area 2 [SwitchC–ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchC–ospf-1-area-0.0.0.2] quit [SwitchC-ospf-1] quit # Configure Switch D. system-view [SwitchD] ospf 1 router-id 4.4.4.4 [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.
Routing for Network Destination Cost Type AdvRouter Area 10.2.1.0/24 2 Transit 10.2.1.1 NextHop 3.3.3.3 0.0.0.1 10.3.1.0/24 5 Inter 10.2.1.2 3.3.3.3 0.0.0.0 10.1.1.0/24 2 Transit 10.1.1.2 2.2.2.2 0.0.0.0 Total Nets: 3 Intra Area: 2 Inter Area: 1 ASE: 0 NSSA: 0 The output shows that Switch B has learned the route 10.3.1.0/24 to Area 2.
[SwitchB-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchB-ospf-100-area-0.0.0.0] quit # Configure Switch C. system-view [SwitchC] router id 3.3.3.3 [SwitchC] ospf 100 [SwitchC-ospf-100] area 0 [SwitchC-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchC-ospf-100-area-0.0.0.0] quit 3.
%Oct 21 15:29:29:902 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.2(Vlan-interface100) from Loading to Full. *Oct 21 15:29:29:902 2011 SwitchA OSPF/7/DEBUG: -MDC=1; OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.2. %Oct 21 15:29:30:897 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.3(Vlan-interface100) from Loading to Full. *Oct 21 15:29:30:897 2011 SwitchA OSPF/7/DEBUG: -MDC=1; OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.3.
Vlan-int13 13.1.1.2/24 Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable OSPF: # Configure Switch A. system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255 [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 121.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.
[SwitchA] quit # Enable BFD on Switch B and configure BFD parameters. [SwitchB] bfd session init-mode active [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ospf bfd enable [SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Switch A.
SubProtID: 0x1 Age: 04h20m37s Cost: 4 Preference: 10 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NBRID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 10.1.1.100 Label: NULL RealNextHop: 10.1.1.100 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid BkTunnel ID: Invalid Interface: Vlan-interface11 BkInterface: N/A The output shows that Switch A communicates with Switch B through VLAN-interface 11.
system-view [SwitchD] bfd echo-source-ip 3.3.3.3 [SwitchD] ospf 1 [SwitchD-ospf-1] fast-reroute lfa [SwitchD-ospf-1] quit { (Method 2.) Enable OSPF FRR to designate a backup next hop by using a routing policy. # Configure Switch S. system-view [SwitchS] bfd echo-source-ip 1.1.1.1 [SwitchS] ip prefix-list abc index 10 permit 4.4.4.
BkLabel: NULL BkNextHop: 12.12.12.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface100 # Display route 1.1.1.1/32 on Switch D to view the backup next hop information. [SwitchD] display ip routing-table 1.1.1.1 verbose Summary Count : 1 Destination: 1.1.1.
Incorrect routing information Symptom OSPF cannot find routes to other areas. Analysis The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, at least one area must be connected to the backbone. The backbone cannot be configured as a stub area. In a stub area, all routers cannot receive external routes, and all interfaces connected to the stub area must belong to the stub area. Solution 1.
Configuring IS-IS This chapter describes how to configure IS-IS for IPv4 networks. Overview Intermediate System-to-Intermediate System (IS-IS) is a dynamic routing protocol designed by the ISO to operate on the connectionless network protocol (CLNP). IS-IS was modified and extended in RFC 1195 by the IETF for application in both TCP/IP and OSI reference models, called "Integrated IS-IS" or "Dual IS-IS." IS-IS is an IGP used within an AS. It uses the SPF algorithm for route calculation.
• System ID—Identifies the host. • SEL—Identifies the type of service. The IDP and DSP are variable in length. The length of an NSAP address ranges from 8 bytes to 20 bytes. Figure 32 NSAP address format Area address The area address comprises the IDP and the HO-DSP of the DSP, which identify the area and the routing domain. Different routing domains cannot have the same area address. Typically, a router only needs one area address, and all nodes in the same area must have the same area address.
• Area ID—Has a length of 1 to 13 bytes. • System ID—A system ID uniquely identifies a host or router in the area and has a fixed length of 6 bytes. • SEL—Has a value of 0 and a fixed length of 1 byte. For example, for a NET ab.cdef.1234.5678.9abc.00, the area ID is ab.cdef, the system ID is 1234.5678.9abc, and the SEL is 00. Typically, a router only needs one NET, but it can have a maximum of three NETs for smooth area merging and partitioning.
Figure 33 IS-IS topology 1 Area 3 Area 2 L1/L2 L1/L2 L2 L2 L1 Area 1 L2 L2 Area 5 L1/L2 Area 4 L1 L1/L2 L1 L1 L1 L1 Figure 34 shows another IS-IS topology. The Level-1-2 routers connect to the Level-1 and Level-2 routers, and form the IS-IS backbone together with the Level-2 routers. No area is defined as the backbone in this topology. The backbone comprises all contiguous Level-2 and Level-1-2 routers in different areas. The IS-IS backbone does not need to be a specific area.
passing through the Level-1-2 router might not be the best. To solve this problem, IS-IS provides the route leaking feature. Route leaking enables a Level-1-2 router to advertise the routes of other Level-1 areas and the Level-2 area to the connected Level-1 area so that the Level-1 routers can select the optimal routes for packets. IS-IS network types Network types IS-IS supports the broadcast network (for example, Ethernet and Token Ring) and the point-to-point network (for example, PPP and HDLC).
NOTE: On an IS-IS broadcast network, all routers establish adjacency relationships, but they synchronize their LSDBs through the DIS. IS-IS PDUs PDU IS-IS PDUs are encapsulated into link layer frames. An IS-IS PDU has two parts, the headers and the variable length fields. The headers comprise the PDU common header and the PDU specific header. All PDUs have the same PDU common header. The specific headers vary by PDU type.
A CSNP describes the summary of all LSPs for LSDB synchronization between neighboring routers. On broadcast networks, CSNPs are sent by the DIS periodically (every 10 seconds by default). On point-to-point networks, CSNPs are sent only during the first adjacency establishment. A PSNP only contains the sequence numbers of one or multiple latest received LSPs. It can acknowledge multiple LSPs at one time. When LSDBs are not synchronized, a PSNP is used to request missing LSPs from a neighbor.
• RFC 2966, Domain-wide Prefix Distribution with Two-Level IS-IS • RFC 2973, IS-IS Mesh Groups • RFC 3277, IS-IS Transient Blackhole Avoidance • RFC 3358, Optional Checksums in ISIS • RFC 3373, Three-Way Handshake for IS-IS Point-to-Point Adjacencies • RFC 3567, Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication • RFC 3719, Recommendations for Interoperable Networks using IS-IS • RFC 3786, Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit • RFC 37
Tasks at a glance (Optional.) Enhancing IS-IS network security: • Configuring neighbor relationship authentication • Configuring area authentication • Configuring routing domain authentication (Optional.) Configuring IS-IS GR (Optional.) Configuring BFD for IS-IS (Optional.) Configuring IS-IS FRR Configuring basic IS-IS Configuration prerequisites Before the configuration, complete the following tasks: • Configure the link layer protocol.
To configure the IS level and circuit level: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Specify the IS level. is-level { level-1 | level-1-2 | level-2 } By default, the IS level is Level-1-2. 4. Return to system view. quit N/A 5. Enter interface view. interface interface-type interface-number N/A 6. Specify the circuit level.
Configuring IS-IS link cost The IS-IS cost of an interface is determined in the following order: 1. IS-IS cost specified in interface view. 2. IS-IS cost specified in system view. The cost is applied to the interfaces associated with the IS-IS process. 3. Automatically calculated cost. If the cost style is wide or wide-compatible, IS-IS automatically calculates the cost using the formula: Interface cost = (Bandwidth reference value / Expected interface bandwidth) × 10, in the range of 1 to 16777214.
Step Command Remarks 3. (Optional.) Specify an IS-IS cost style. cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] } By default, the IS-IS cost style is narrow. 4. Specify a global IS-IS cost. circuit-cost value [ level-1 | level-2 ] By default, no global cost is specified. Enabling automatic IS-IS cost calculation Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view.
Step 2. 3. Enter IS-IS view. Specify the maximum number of ECMP routes. Command Remarks isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A maximum load-balancing number By default, the maximum number of ECMP routes is the same as that configured in the max-ecmp-num command. For more information about the max-ecmp-num command, see Layer 3—IP Routing Command Reference.
Configuring IS-IS route redistribution Perform this task to redistribute routes from other routing protocols into IS-IS. You can specify a cost for redistributed routes and specify the maximum number of redistributed routes. To configure IS-IS route redistribution from other routing protocols: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A By default, no route is redistributed. 3. 4.
Filtering redistributed routes IS-IS can redistribute routes from other routing protocols or other IS-IS processes, add them to the IS-IS routing table, and advertise them in LSPs. Perform this task to filter redistributed routes. Only routes that are not filtered can be added to the IS-IS routing table and advertised to neighbors. To filter redistributed routes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view.
Specifying the interval for sending IS-IS hello packets If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval. To specify the interval for sending hello packets: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A The default setting is 10 seconds.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Specify the interval for sending CSNP packets on the DIS of a broadcast network. isis timer csnp seconds [ level-1 | level-2 ] The default setting is 10 seconds. Configuring a DIS priority for an interface On a broadcast network, IS-IS must elect a router as the DIS at a routing level. You can specify a DIS priority at a level for an interface.
To enable an interface to send small hello packets: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the interface to send small hello packets without CLVs. isis small-hello By default, the interface can send standard hello packets. Configuring LSP parameters Configuring LSP timers 1. Specify the maximum age of LSPs. Each LSP has an age that decreases in the LSDB.
Step Command Remarks By default: Specify the LSP generation interval. 4. timer lsp-generation maximum-interval [ minimum-interval [ incremental-interval ] ] [ level-1 | level-2 ] • The maximum interval is 5 seconds. • The minimum interval is 20 milliseconds. • The incremental interval is 200 milliseconds. 3. Specify LSP sending intervals. If a change occurs in the LSDB, IS-IS advertises the changed LSP to neighbors.
Step 4. Specify the maximum length of received LSPs. Command Remarks lsp-length receive size By default, the maximum length of received LSPs is 1497 bytes. Enabling LSP flash flooding Changed LSPs can trigger SPF recalculation. To advertise the changed LSPs before the router recalculates routes for faster network convergence, enable LSP flash flooding. To enable LSP flash flooding: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A By default: • The maximum interval is 5 3. Configure the SPF calculation interval. timer spf maximum-interval [ minimum-interval [ incremental-interval ] ] seconds. • The minimum interval is 50 milliseconds. • The incremental interval is 200 milliseconds.
Step Set the overload bit. 3. Command Remarks set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 ] [ allow { external | interlevel } * ] By default, the overload bit is not set. Configuring system ID to host name mappings A 6-byte system ID in hexadecimal notation uniquely identifies a router or host in an IS-IS network.
Step Command Remarks Specify a host name for the IS and enable dynamic system ID to host name mapping. is-name sys-name By default, no host name is specified for the router. 4. Return to system view. quit N/A 5. Enter interface view. interface interface-type interface-number N/A 3. By default, no DIS name is configured. 6. Configure a DIS name. isis dis-name symbolic-name This command takes effect only on a router enabled with dynamic system ID to host name mapping.
Configuring IS-IS network management This task includes the following configurations: • Bind an IS-IS process to MIB so that you can use network management software to manage the specified IS-IS process. • Enable IS-IS notifications to report important events. Notifications are delivered to the SNMP module, which outputs the notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide.
Configuration prerequisites Before the configuration, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • Enable IS-IS. Configuring neighbor relationship authentication With neighbor relationship authentication configured, an interface adds the password in the specified mode into hello packets to the peer and checks the password in the received hello packets.
To configure routing domain authentication: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Specify the routing domain authentication mode and password. domain-authentication-mode { md5 | simple } { cipher cipher-string | plain plain-string } [ ip | osi ] By default, no routing domain authentication is configured.
Step Command Remarks By default, the SA bit is not suppressed. (Optional.) Suppress the SA bit during restart. graceful-restart suppress-sa 5. (Optional.) Configure the T1 timer. graceful-restart t1 seconds count count By default, the T1 timer is 3 seconds and can expire 10 times. 6. (Optional.) Configure the T2 timer. graceful-restart t2 seconds By default, the T2 timer is 60 seconds. 7. (Optional.) Configure the T3 timer. graceful-restart t3 seconds By default, the T2 timer is 300 seconds.
traffic recovery time. Meanwhile, IS-IS calculates the shortest path based on the new network topology, and forwards packets over the path after network convergence. You can either enable IS-IS FRR to calculate a backup next hop automatically, or designate a backup next hop with a routing policy for routes matching specific criteria.
Step 4. Enable IS-IS FRR using a routing policy. Command Remarks fast-reroute route-policy route-policy-name By default, this feature is not enabled. Displaying and maintaining IS-IS Execute display commands in any view and the reset command in user view. Task Command Display brief IS-IS backup configuration information (in standalone mode). display isis brief [ process-id ] [ standby slot slot-number ] Display brief IS-IS backup configuration information (in IRF mode).
Task Command Display OSI connection information (in IRF mode). display osi [ chassis chassis-number slot slot-number ] Display OSI connection statistics (in standalone mode). display osi statistics [ slot slot-number ] Display OSI connection statistics (in IRF mode). display osi statistics [ chassis chassis-number slot slot-number ] Clear IS-IS process data structure information. reset isis all [ process-id ] [ graceful-restart ] Clear IS-IS GR log information (in standalone mode).
Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure IS-IS: # Configure Switch A. system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B.
Verifying the configuration # Display the IS-IS LSDB on each switch to verify the LSPs. [SwitchA] display isis lsdb Database information for IS-IS(1) --------------------------------Level-1 Link State Database --------------------------LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------0000.0000.0001.00-00* 0x00000004 0xdf5e 1096 68 0/0/0 0000.0000.0002.00-00 0x00000004 0xee4d 1102 68 0/0/0 0000.0000.0002.
0000.0000.0002.01-00 0x00000005 0xd2b3 1052 55 0/0/0 0000.0000.0003.00-00* 0x00000014 0x194a 1051 111 1/0/0 0000.0000.0003.01-00* 0x00000002 0xabdb 854 55 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload Level-2 Link State Database --------------------------LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------0000.0000.0003.00-00* 0x00000012 0xc93c 842 100 0/0/0 0000.0000.0004.
[SwitchC] display isis route Route information for IS-IS(1) ------------------------------ Level-1 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------192.168.0.0/24 10 NULL Vlan300 Direct D/L/- 10.1.1.0/24 10 NULL Vlan100 Direct D/L/- 10.1.2.
DIS election configuration example Network requirements As shown in Figure 40, Switches A, B, C, and D reside in IS-IS area 10 on a broadcast network (Ethernet). Switch A and Switch B are Level-1-2 switches, Switch C is a Level-1 switch, and Switch D is a Level-2 switch. Change the DIS priority of Switch A to make it elected as the Level-1-2 DIS router. Figure 40 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable IS-IS: # Configure Switch A.
[SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit # Configure Switch D. system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 10.0000.0000.0004.00 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 100 [SwitchD-Vlan-interface100] isis enable 1 [SwitchD-Vlan-interface100] quit # Display information about IS-IS neighbors on Switch A.
Id IPv4.State IPv6.State MTU Type DIS 001 Up Down 1497 L1/L2 Yes/No # Display information about IS-IS interfaces on Switch D. [SwitchD] display isis interface Interface information for IS-IS(1) ---------------------------------Interface: Vlan-interface100 Id IPv4.State IPv6.State MTU Type DIS 001 Up Down 1497 L1/L2 No/Yes The output shows that when the default DIS priority is used, Switch C is the DIS for Level-1, and Switch D is the DIS for Level-2.
001 Up Down 1497 L1/L2 Yes/Yes The output shows that after the DIS priority configuration, Switch A becomes the DIS for Level-1-2, and the pseudonode is 0000.0000.0001.01. # Display information about IS-IS neighbors and interfaces on Switch C. [SwitchC] display isis peer Peer information for IS-IS(1) ---------------------------System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up Type: L1 HoldTime: 25s PRI: 64 System Id: 0000.0000.
IS-IS route redistribution configuration example Network requirements As shown in Figure 41, Switch A, Switch B, Switch C, and Switch D reside in the same AS. They use IS-IS to interconnect. Switch A and Switch B are Level-1 routers, Switch D is a Level-2 router, and Switch C is a Level-1-2 router. Redistribute RIP routes into IS-IS on Switch D. Figure 41 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure basic IS-IS: # Configure Switch A.
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D.
10.1.2.0/24 10 NULL VLAN200 Direct D/L/- 192.168.0.0/24 10 NULL VLAN300 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------10.1.1.0/24 10 NULL VLAN100 Direct D/L/- 10.1.2.0/24 10 NULL VLAN200 Direct D/L/- 192.168.0.
[SwitchC] display isis route Route information for IS-IS(1) ------------------------------ Level-1 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------10.1.1.0/24 10 NULL VLAN100 Direct D/L/- 10.1.2.0/24 10 NULL VLAN200 Direct D/L/- 192.168.0.
Figure 42 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure basic IS-IS: # Configure Switch A. system-view [SwitchA] isis 1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B. system-view [SwitchB] isis 1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.
[SwitchC-Vlan-interface300] quit # Configure Switch D. system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 20.0000.0000.0001.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit 3. Configure neighbor relationship authentication between neighbors: # Configure the authentication mode as MD5 and set the plaintext password to eRq on VLAN-interface 100 of Switch A and on VLAN-interface 100 of Switch C.
[SwitchC] isis 1 [SwitchC-isis-1] domain-authentication-mode md5 plain 1020Sec [SwitchC-isis-1] quit [SwitchD] isis 1 [SwitchD-isis-1] domain-authentication-mode md5 plain 1020Sec IS-IS GR configuration example Network requirements As shown in Figure 43, Switch A, Switch B, and Switch C belong to the same IS-IS routing domain. Figure 43 Network diagram Configuration procedure 1. Configure IP addresses and subnet masks for interfaces. (Details not shown.) 2.
Restart phase: Finish Restart t1: 3, count 10; Restart t2: 60; Restart t3: 300 SA Bit: supported Level-1 restart information --------------------------Total number of interfaces: 1 Number of waiting LSPs: 0 Level-2 restart information --------------------------Total number of interfaces: 1 Number of waiting LSPs: 0 BFD for IS-IS configuration example Network requirements • As shown in Figure 44, run IS-IS on Switch A, Switch B and Switch C so that can reach each other at the network layer.
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] isis enable [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] isis enable [SwitchA-Vlan-interface11] quit # Configure Switch B. system-view [SwitchB] isis [SwitchB-isis-1] network-entity 10.0000.0000.0002.
Verifying the configuration # Display the BFD session information on Switch A. display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 3/1 192.168.0.102 192.168.0.100 Up 1700ms Vlan10 # Display routes destined for 120.1.1.0/24 on Switch A. display ip routing-table 120.1.1.0 verbose Summary Count : 1 Destination: 120.1.1.
BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: Vlan-interface11 BkTunnel ID: Invalid BkInterface: N/A The output shows that Switch A and Switch B communicate through VLAN-interface 11. IS-IS FRR configuration example Network requirements As shown in Figure 45, Switch S, Switch A, and Switch D belong to the same IS-IS routing domain. Configure IS-IS FRR so that when the Link A fails, traffic can be switched to Link B immediately. Figure 45 Network diagram Switch A 00 nt1 /24 n-i 12.
[SwitchS] ip prefix-list abc index 10 permit 4.4.4.4 32 [SwitchS] route-policy frr permit node 10 [SwitchS-route-policy-frr-10] if-match ip address prefix-list abc [SwitchS-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 100 backup-nexthop 12.12.12.2 [SwitchS-route-policy-frr-10] quit [SwitchS] isis 1 [SwitchS-isis-1] fast-reroute route-policy frr [SwitchS-isis-1] quit # Configure Switch D. system-view [SwitchD] bfd echo-source-ip 4.4.4.
Protocol: ISIS SubProtID: 0x1 Cost: 10 Tag: 0 OrigTblID: 0x0 TableID: 0x2 NBRID: 0x26000002 AttrID: 0xffffffff Process ID: 1 Age: 04h20m37s Preference: 10 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.1 Label: NULL RealNextHop: 13.13.13.1 BkLabel: NULL BkNextHop: 24.24.24.
Configuring BGP Overview Border Gateway Protocol (BGP) is an exterior gateway protocol (EGP). It is called internal BGP (IBGP) when it runs within an AS and called external BGP (EBGP) when it runs between ASs. The current version in use is BGP-4 (RFC 4271). BGP has the following characteristics: • Focuses on route control and selection rather than route discovery and calculation. • Uses TCP to enhance reliability.
BGP path attributes BGP uses the following path attributes in update messages for route filtering and selection: • ORIGIN The ORIGIN attribute specifies the origin of BGP routes. This attribute has the following types: { IGP—Has the highest priority. Routes generated in the local AS have the IGP attribute. { EGP—Has the second highest priority. Routes obtained through EGP have the EGP attribute. { • INCOMPLETE—Has the lowest priority. The source of routes with this attribute is unknown.
{ • Filter routes—By using an AS path list, you can filter routes based on AS numbers contained in the AS_PATH attribute. For more information about AS path list, see "Configuring routing policies." NEXT_HOP The NEXT_HOP attribute might not be the IP address of a directly-connected router. Its value is determined as follows: { { { When a BGP speaker advertises a self-originated route to a BGP peer, it sets the address of the sending interface as the NEXT_HOP.
Figure 48 MED attribute MED = 0 Router B 2.1.1.1 D = 9.0.0.0 Next_hop = 2.1.1.1 MED = 0 EBGP IBGP 9.0.0.0 IBGP Router A D = 9.0.0.0 Next_hop = 3.1.1.1 MED = 100 AS 10 EBGP Router D IBGP 3.1.1.1 Router C MED = 100 AS 20 Generally BGP only compares MEDs of routes received from the same AS. You can also use the compare-different-as-med command to force BGP to compare MED values of routes received from different ASs.
Figure 49 LOCAL_PREF attribute • COMMUNITY The COMMUNITY attribute identifies the community of BGP routes. A BGP community is a group of routes with the same characteristics. It has no geographical boundaries. Routes of different ASs can belong to the same community. A route can carry one or more COMMUNITY attribute values (each of which is represented by a 4-byte integer).
BGP route selection BGP discards routes with unreachable NEXT_HOPs. If multiple routes to the same destination are available, BGP selects the best route in the following sequence: 1. The route with the highest Preferred_value. 2. The route with the highest LOCAL_PREF. 3. The route generated by the network command, the route redistributed by the import-route command, or the summary route in turn. 4. The route with the shortest AS_PATH. 5. The IGP, EGP, or INCOMPLETE route in turn. 6.
The system supports BGP load balancing based on route recursion. If multiple recursive routes to the same destination are load balanced (suppose three direct next hop addresses), BGP generates the same number of next hops to forward packets. BGP load balancing based on route recursion is always enabled by the system rather than configured by using commands. • BGP load balancing through route selection.
Route summarization can reduce the BGP routing table size by advertising summary routes rather than more specific routes. The system supports both manual and automatic route summarization. Manual route summarization allows you to determine the attribute of a summary route and whether to advertise more specific routes. • Route dampening Route frapping (a route comes up and disappears in the routing table frequently) causes BGP to send many routing updates.
IBGP peers must be fully meshed to maintain connectivity. If n routers exist in an AS, the number of IBGP connections is n(n-1)/2. If a large number of IBGP peers exist, large amounts of network and CPU resources are consumed to maintain sessions. Using route reflectors can solve this issue. In an AS, a router acts as a route reflector, and other routers act as clients connecting to the route reflector. The route reflector forwards routing information received from a client to other clients.
• Confederation Confederation is another method to manage growing IBGP connections in an AS. It splits an AS into multiple sub-ASs. In each sub-AS, IBGP peers are fully meshed. As shown in Figure 54, intra-confederation EBGP connections are established between sub-ASs in AS 200. Figure 54 Confederation network diagram A non-confederation BGP speaker does not need to know sub-ASs in the confederation. It considers the confederation as one AS, and the confederation ID as the AS number.
MP-BGP uses these two attributes to advertise feasible and unfeasible routes for different network layer protocols. BGP speakers not supporting MP-BGP ignore updates containing these attributes and do not forward them to its peers. The current MP-BGP implementation supports multiple protocol extensions, including VPN, IPv6, and multicast. For more information about VPN, see MPLS Configuration Guide.
View names BGP VPNv6 address family view Ways to enter the views Remarks system-view Configurations in this view apply to VPNv6 routes and peers. [Sysname] bgp 100 [Sysname-bgp] address-family vpnv6 [Sysname-bgp-vpnv6] system-view BGP L2VPN address family view [Sysname] bgp 100 [Sysname-bgp] address-family l2vpn [Sysname-bgp-l2vpn] For more information about BGP VPNv6 address family view, see MPLS Configuration Guide.
• RFC 2796, BGP Route Reflection • RFC 3065, Autonomous System Confederations for BGP • RFC 4271, A Border Gateway Protocol 4 (BGP-4) • RFC 4724, Graceful Restart Mechanism for BGP • RFC 4360, BGP Extended Communities Attribute • RFC 4760, Multiprotocol Extensions for BGP-4 BGP configuration task list In a basic BGP network, you only need to perform the following configurations: • Enable BGP. • Configure BGP peers or peer groups.
Tasks at a glance Remarks (Optional.
Tasks at a glance Remarks (Optional.) Controlling BGP path selection: • • • • • • Specifying a preferred value for routes received Configuring preferences for BGP routes Configuring the default local preference N/A Configuring the MED attribute Configuring the NEXT_HOP attribute Configuring the AS_PATH attribute (Optional.
To enable BGP: Step 1. 2. Enter system view. Configure a global router ID. Command Remarks system-view N/A router id router-id By default, no global router ID is configured, and BGP uses the highest loopback interface IP address—if any—as the router ID. If no loopback interface IP address is available, BGP uses the highest physical interface IP address as the route ID regardless of the interface status. • Enable BGP and enter BGP 3. Enable BGP and enter BGP view or BGP-VPN instance view.
Step 5. 6. Command Remarks Create and enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] By default, the BGP IPv4 unicast address family view and BGP-VPN IPv4 unicast address family view are not created. Enable the router to exchange IPv4 unicast routing information with the specified peer. peer ip-address enable By default, the router cannot exchange IPv4 unicast routing information with the peer.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Create an IBGP peer group. group group-name [ internal ] By default, no IBGP peer group is created. By default, no peer exists in the peer group. 4. Add a peer into the IBGP peer group. peer ip-address group group-name [ as-number as-number ] 5. (Optional.
Step 6. 7. Command Remarks Create and enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] By default, the BGP IPv6 unicast address family view and BGP-VPN IPv6 unicast address family view are not created. Enable the router to exchange IPv6 unicast routing information with peers in the specified peer group. peer group-name enable By default, the router cannot exchange IPv6 unicast routing information with the peers.
Step Command Remarks peer group-name description description-text By default, no description is configured for the peer group. 6. (Optional.) Configure a description for a peer group. 7. Create and enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] By default, the BGP IPv4 unicast address family view and BGP-VPN IPv4 unicast address family view are not created.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Create an EBGP peer group. group group-name external By default, no EBGP peer group is created. 4. Create an IPv4 BGP peer and specify its AS number. peer ip-address as-number as-number By default, no IPv4 BGP peer is created.
Step Command Remarks By default, no peer exists in the peer group. 5. Add the peer into the EBGP peer group. peer ipv6-address group group-name [ as-number as-number ] 6. (Optional.) Configure a description for the peer group. peer group-name description description-text By default, no description is configured for the peer group. 7. Create and enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view.
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Create an EBGP peer group. group group-name external By default, no EBGP peer group is created. 4. Add a peer into the EBGP peer group. peer ipv6-address group group-name as-number as-number By default, no peer exists in the peer group. 5. (Optional.) Configure a description for the peer group.
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Specify the source interface for establishing TCP connections to a peer or peer group. 3.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Inject a local network to the BGP routing table.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A 4. Enable route redistribution from the specified IGP into BGP.
The output interface of a BGP summary route is Null 0 on the originating router. Therefore, a summary route must not be an optimal route on the originating router. Otherwise, BGP will fail to forward packets matching the route. If a summarized specific route has the same mask as the summary route, but has a lower priority, the summary route becomes the optimal route. In this case, you must change the priority of the summary or the specific route to make the specific route as the optimal route.
Step 4. Create a summary route in the BGP routing table. Command Remarks aggregate ip-address { mask | mask-length } [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] * By default, no summary route is configured. To configure BGP manual route summarization (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3.
Step Enter system view. 1. Command Remarks system-view N/A • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Advertise a default route to a peer or peer group.
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Specify the maximum number of routes that a router can receive from a peer or peer group.
If you configure multiple filtering policies, apply them in the following sequence: 1. filter-policy export 2. peer filter-policy export 3. peer as-path-acl export 4. peer prefix-list export 5. peer route-policy export Only routes passing all the configured policies can be advertised. To configure BGP route distribution filtering policies (IPv4): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view.
Step Command Remarks • Reference an ACL or IP prefix list to filter advertised BGP routes: filter-policy { acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ip-address } route-policy route-policy-name export 4. Configure BGP route distribution filtering policies.
Step Command Remarks • Reference an ACL or IPv6 prefix list to filter advertised BGP routes: filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ direct | isisv6 process-id | ospfv3 process-id | ripng process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv6-address } route-policy route-policy-name export 4. Configure BGP route distribution filtering policies.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view.
Step 3. Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. Command Remarks address-family ipv6 [ unicast ] N/A • Reference ACL or IPv6 prefix list to filter BGP routes received from all peers: filter-policy { acl6-number | prefix-list ipv6-prefix-name } import • Reference a routing policy to filter BGP routes received from a peer or peer group: peer { group-name | ipv6-address } route-policy route-policy-name import 4.
Step 4. Configure BGP route dampening. Command Remarks dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] * By default, BGP route dampening is not configured. To configure BGP route dampening (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4.
Step 3. 4. Command Remarks Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Specify a preferred value for routes received from a peer or peer group. peer { group-name | ip-address } preferred-value value The default preferred value is 0. To specify a preferred value for routes from a peer or peer group (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A 4. Configure preferences for EBGP, IBGP, and local BGP routes.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Configure the default local preference. default local-preference value The default local preference is 100.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Configure the default MED value. default med med-value The default MED value is 0. To configure the default MED value (IPv6): Step 1. Enter system view.
Step Enable MED comparison for routes from different ASs. 4. Command Remarks compare-different-as-med By default, this feature is disabled. To enable MED comparison for routes from different ASs (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A 4. Enable MED comparison for routes from different ASs.
* i 3.3.3.3 50 0 200e However, Router C and Router A reside in the same AS, and Router C has a greater MED, so network 10.0.0.0 learned from Router C should not be optimal. You can configure the bestroute compare-med command to enable MED comparison for routes from the same AS on Router D. After that, Router D puts the routes received from each AS into a group, selects the route with the lowest MED from each group, and compares routes from different groups.
not belong to the confederation, BGP does not compare it with other routes. As a result, the first route becomes the optimal route. To enable MED comparison for routes from confederation peers (IPv4): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4.
Figure 56 NEXT_HOP attribute configuration If a BGP router has two peers on a broadcast network, it does not set itself as the next hop for routes sent to an EBGP peer by default. As shown in Figure 57, Router A and Router B establish an EBGP neighbor relationship, and Router B and Router C establish an IBGP neighbor relationship. They are on the same broadcast network 1.1.1.0/24. When Router B sends EBGP routes to Router A, it does not set itself as the next hop by default.
To configure the NEXT_HOP attribute (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A peer { group-name | ipv6-address } next-hop-local By default, the router sets itself as the next hop for routes sent to an EBGP peer or peer group, but does not set itself as the next hop for routes sent to an IBGP peer or peer group. 4.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A Permit the local AS number to appear in routes from a peer or peer group and specify the appearance times.
Step 3. 4. Command Remarks Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A Disable BGP from considering AS_PATH during best route selection. bestroute as-path-neglect By default, BGP considers AS_PATH during best route selection.
Configuring AS number substitution IMPORTANT: Do not configure AS number substitution in normal circumstances. Otherwise, routing loops might occur. To use BGP between PE and CE in MPLS L3VPN, VPN sites in different geographical areas should have different AS numbers. Otherwise, BGP discards route updates containing the local AS number.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Configure AS number substitution for a peer or peer group. peer { group-name | ipv6-address } substitute-as By default, AS number substitution is not configured.
Step Command Configure BGP to remove private AS numbers from the AS_PATH attribute of updates sent to an EBGP peer or peer group. 4. peer { group-name | ipv6-address } public-as-only Remarks By default, this feature is not configured. This command is only applicable to EBGP peers or peer groups. Ignoring the first AS number of EBGP route updates By default, BGP checks whether the first AS number in the AS_PATH attribute of a route update received from a peer is the AS number of that peer.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Use either method. • Configure the global keepalive interval and hold time: timer keepalive keepalive hold holdtime 3. Configure the keepalive interval and hold time.
Configuring the interval for sending updates for the same route A BGP router sends an update message to its peers when a route is changed. If the route changes frequently, the BGP router keeps sending updates for the same route, resulting route flapping. To prevent this situation, perform this task to configure the interval for sending updates for the same route to a peer or peer group. To configure the interval for sending the same update to a peer or peer group (IPv4): Step 1. Enter system view.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Enable BGP to establish an EBGP session to an indirectly-connected peer or peer group and specify the maximum hop count. peer { group-name | ip-address } ebgp-max-hop [ hop-count ] By default, BGP cannot establish an EBGP session to an indirectly-connected peer or peer group.
Enabling 4-byte AS number suppression BGP supports 4-byte AS numbers. The 4-byte AS number occupies four bytes, in the range of 1 to 4294967295. By default, a device sends an Open message to the peer device for session establishment. The Open message indicates that the device supports 4-byte AS numbers. If the peer device supports 2-byte AS numbers instead of 4-byte AS numbers, the session cannot be established. To resolve this issue, enable the 4-byte AS number suppression function.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number Use either method. b. ip vpn-instance vpn-instance-name 3. Enable MD5 authentication for a BGP peer group or peer. peer { group-name | ip-address } password { cipher | simple } password By default, MD5 authentication is disabled. To enable MD5 authentication for BGP peers (IPv6): Step 1. Enter system view.
Step 4. Specify the maximum number of BGP ECMP routes for load balancing. Command Remarks balance number By default, load balancing is disabled. To specify the maximum number of BGP ECMP routes for load balancing (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4.
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Disable BGP to establish a session to a peer or peer group. 3. peer { group-name | ipv6-address } ignore By default, BGP can establish a session to a peer.
Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address } capability-advertise route-refresh 3. Enable BGP route refresh for a peer or peer group. • Enable BGP route refresh and multi-protocol extension capability for the specified peer or peer group: undo peer { group-name | ip-address } capability-advertise conventional Use either method. By default, BGP route refresh is enabled.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. Save all route updates from the peer or peer group. address-family ipv4 [ unicast ] peer { group-name | ip-address } keep-all-routes N/A By default, the routes are not saved.
Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address } capability-advertise route-refresh 3. 4. 5. Enable BGP route refresh for a peer or peer group. • Enable BGP route refresh and Return to user view. return N/A Perform manual soft-reset.
Step Command Remarks 5. refresh bgp { ipv6-address | all | external | group group-name | internal } { export | import } ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] N/A Perform manual soft-reset. Protecting an EBGP peer when memory usage reaches level 2 threshold Memory usage includes the following threshold levels: normal, level 1, level 2, and level 3.
Configuring a large-scale BGP network In a large network, the number of BGP connections is huge and BGP configuration and maintenance are complicated. To simply BGP configuration, you can use the peer group, community, route reflector, and confederation features as needed. For more information about configuring peer groups, see "Configuring a BGP peer group." Configuring BGP community By default, a router does not advertise the COMMUNITY or extended community attribute to its peers or peer groups.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A • Advertise the COMMUNITY 4. 5. Advertise the COMMUNITY or extended community attribute to a peer or peer group. (Optional.) Apply a routing policy to routes advertised to a peer or peer group.
Step Command Remarks 5. Enable route reflection between clients. reflect between-clients By default, route reflection between clients is enabled. 6. (Optional.) Configure the cluster ID of the route reflector. reflector cluster-id { cluster-id | ip-address } By default, a route reflector uses its own router ID as the cluster ID. To configure a BGP route reflector (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3.
Step Enter system view. 1. Command Remarks system-view N/A • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name By default, BGP does not ignore the ORIGINATOR_ID attribute. Ignore the ORIGINATOR_ID attribute. 3. peer { group-name | ipv6-address } ignore-originatorid Make sure this command does not result in a routing loop.
Configuring confederation compatibility If any routers in the confederation do not comply with RFC 3065, enable confederation compatibility to allow the router to work with those routers. To configure confederation compatibility: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enable confederation compatibility. confederation nonstandard By default, confederation compatibility is disabled.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enable GR capability for BGP. graceful-restart By default, GR capability is disabled for BGP. The default setting is 150 seconds. 4. Configure the GR timer. graceful-restart timer restart timer 5. Configure the maximum time to wait for the End-of-RIB marker. graceful-restart timer wait-for-rib timer The time that a peer waits to reestablish a session must be less than the hold time.
Step 3. Enable the logging of session state changes globally. Command Remarks log-peer-change By default, logging of session state changes is enabled globally. Configuring BFD for BGP IMPORTANT: If you have enabled GR, use BFD with caution because BFD might detect a failure before the system performs GR, which will result in GR failure. If you have enabled both BFD and GR for BGP, do not disable BFD during a GR process to avoid GR failure.
Displaying and maintaining BGP Execute display commands in any view and reset commands in user view (IPv4). Task Command Display BGP IPv4 unicast peer group information. display bgp group ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ group-name ] Display BGP IPv4 unicast peer or peer group information. display bgp peer ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ ip-address { log-info | verbose } | group-name log-info | verbose ] Display BGP IPv4 unicast routing information.
Task Command Reset IPv4 unicast BGP sessions. reset bgp { as-number | ip-address | all | external | group group-name | internal } ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] Clear dampened BGP IPv4 unicast routing information and release suppressed routes. reset bgp dampening ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ network-address [ mask | mask-length ] ] Clear BGP IPv4 unicast route flap information.
Task Command Display the incoming label of BGP IPv6 unicast routing information. display bgp routing-table ipv6 [ unicast ] inlabel Display the outgoing label of BGP IPv6 unicast routing information. display bgp routing-table ipv6 [ unicast ] outlabel Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp network ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] Display BGP path attribute information.
BGP connections. Enable OSPF in AS 65009 to make sure that Switch B can communicate with Switch C through loopback interfaces. The EBGP peers, Switch A and Switch B (typically belong to different carriers), are located in different ASs. Typically, their loopback interfaces are not reachable to each other, so directly connected interfaces are used for establishing BGP sessions. To enable Switch C to access the network 8.1.1.0/24 connected directly to Switch A, inject network 8.1.1.
Peer 2.2.2.2 AS MsgRcvd 65009 2 MsgSent OutQ PrefRcv Up/Down 2 0 State 0 00:00:13 Established The output shows that Switch C has established an IBGP peer relationship with Switch B. 3. Configure EBGP: # Configure Switch A. system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 3.1.1.1 as-number 65009 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 3.1.1.1 enable [SwitchA-bgp-ipv4] network 8.1.1.
* > 8.1.1.0/24 8.1.1.1 0 0 i # Display the BGP routing table on Switch B. [SwitchB] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 2.2.2.2 Status codes: * - valid, > - best, d - damped, h - history, s - suppressed, S - Stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network * >e 8.1.1.0/24 NextHop MED 3.1.1.2 0 LocPrf PrefVal Path/Ogn 0 65008i # Display the BGP routing table on Switch C.
Network NextHop MED LocPrf PrefVal Path/Ogn * >e 2.2.2.2/32 3.1.1.1 0 0 65009? e 3.1.1.0/24 3.1.1.1 0 0 65009? 8.1.1.0/24 8.1.1.1 0 0 i * >e 9.1.1.0/24 3.1.1.1 0 0 65009? * > Two routes, 2.2.2.2/32 and 9.1.1.0/24, have been added in Switch A's routing table. # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 4 BGP local router ID is 3.3.3.
Figure 60 Network diagram Configuration considerations Configure BGP to redistribute routes from OSPF on Switch B, so Switch A can obtain the route to 9.1.2.0/24. Configure OSPF to redistribute routes from BGP on Switch B, so Switch C can obtain the route to 8.1.1.0/24. Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure OSPF: Enable OSPF in AS 65009, so Switch B can obtain the route to 9.1.2.0/24. # Configure Switch B.
# Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 3.1.1.2 enable 4. Configure BGP and IGP route redistribution: # Configure route redistribution between BGP and OSPF on Switch B.
Verifying the configuration # Use ping for verification. [SwitchA] ping -a 8.1.1.1 9.1.2.1 Ping 9.1.2.1 (9.1.2.1) from 8.1.1.1: 56 data bytes, press CTRL_C to break 56 bytes from 9.1.2.1: icmp_seq=0 ttl=254 time=10.000 ms 56 bytes from 9.1.2.1: icmp_seq=1 ttl=254 time=12.000 ms 56 bytes from 9.1.2.1: icmp_seq=2 ttl=254 time=2.000 ms 56 bytes from 9.1.2.1: icmp_seq=3 ttl=254 time=7.000 ms 56 bytes from 9.1.2.1: icmp_seq=4 ttl=254 time=9.000 ms --- Ping statistics for 9.1.2.
Figure 61 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure static routing between Switch A and Switch B: # Configure a default route with the next hop 192.168.212.1 on Switch A. system-view [SwitchA] ip route-static 0.0.0.0 0 192.168.212.1 # Configure static routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 with the same next hop 192.168.212.161 on Switch B. system-view [SwitchB] ip route-static 192.
Summary Count : 5 OSPF Routing table Status : Summary Count : 3 Destination/Mask Proto Pre Cost NextHop Interface 192.168.64.0/24 OSPF 150 1 172.17.100.1 Vlan100 192.168.74.0/24 OSPF 150 1 172.17.100.1 Vlan100 192.168.99.0/24 OSPF 150 1 172.17.100.1 Vlan100 OSPF Routing table Status : Summary Count : 2 Destination/Mask Proto Pre Cost NextHop Interface 10.220.2.0/24 OSPF 10 1 10.220.2.16 Vlan200 172.17.100.0/24 OSPF 10 1 172.17.100.
192.168.99.0/24 BGP 255 1 10.220.2.16 Vlan200 BGP Routing table Status : Summary Count : 0 The output shows that Switch D has learned routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 through BGP. After the above configurations, ping hosts on networks 192.168.74.0/24, 192.168.99.0/24, and 192.168.64.0/18 from Switch D. The ping operations succeed. 5. Configure route summarization on Switch C to summarize 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.
Figure 62 Network diagram Configuration considerations On Switch A, establish EBGP connections with Switch B and Switch C. Configure BGP to advertise network 8.1.1.0/24 to Switch B and Switch C, so that Switch B and Switch C can access the internal network connected to Switch A. On Switch B, establish an EBGP connection to Switch A and an IBGP connection to Switch C. Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet through Switch B.
[SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] peer 3.3.3.3 as-number 65009 [SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 3.1.1.2 enable [SwitchB-bgp-ipv4] peer 3.3.3.3 enable [SwitchB-bgp-ipv4] network 9.1.1.0 24 [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit [SwitchB] ip route-static 3.3.3.3 32 9.1.1.2 # Configure Switch C.
Because Switch A has two routes to reach AS 65009, configuring load balancing over the two BGP routes on Switch A can improve link usage. # Configure Switch A. [SwitchA] bgp 65008 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] balance 2 [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit Verifying the configuration # Display the BGP routing table on Switch A. [SwitchA] display bgp routing-table ipv4 Total number of routes: 3 BGP local router ID is 1.1.1.
Figure 63 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure EBGP: # Configure Switch A. system-view [SwitchA] bgp 10 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 200.1.2.2 as-number 20 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 enable [SwitchA-bgp-ipv4] network 9.1.1.0 255.255.255.0 [SwitchA-bgp] quit # Configure Switch B. system-view [SwitchB] bgp 20 [SwitchB-bgp] router-id 2.2.
[SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1) Relay nexthop : 200.1.2.1 Original nexthop: 200.1.2.1 OutLabel : NULL AS-path : 10 Origin : igp Attribute value : pref-val 0 State : valid, external, best, # Display advertisement information of network 9.1.1.0 on Switch B. [SwitchB] display bgp routing-table ipv4 9.1.1.
[SwitchA-route-policy-comm_policy-0] quit # Apply the routing policy. [SwitchA] bgp 10 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 route-policy comm_policy export [SwitchA-bgp-ipv4] peer 200.1.2.2 advertise-community Verifying the configuration # Display the routing table on Switch B. [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 200.1.2.
• Between Switch A and Switch B is an EBGP connection, between Switch C and Switch B, and between Switch C and Switch D are IBGP connections. • Switch C is a route reflector with clients Switch B and D. • Switch D can learn route 20.0.0.0/8 from Switch C. Figure 64 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure BGP connections: # Configure Switch A. system-view [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.
[SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 193.1.1.2 as-number 200 [SwitchC-bgp] peer 194.1.1.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 193.1.1.2 enable [SwitchC-bgp-ipv4] peer 194.1.1.2 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Configure Switch D. system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] peer 194.1.1.1 as-number 200 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 194.1.1.
Network i 20.0.0.0 NextHop MED LocPrf PrefVal Path/Ogn 193.1.1.2 0 100 0 100i Switch D has learned route 20.0.0.0/8 from Switch C. BGP confederation configuration example Network requirements As shown in Figure 65, to reduce IBGP connections, AS 200 is split into three sub-ASs: AS65001, AS65002, and AS65003. Switches in AS65001 are fully meshed.
[SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 10.1.1.2 enable [SwitchA-bgp-ipv4] peer 10.1.2.2 enable [SwitchA-bgp-ipv4] peer 10.1.1.2 next-hop-local [SwitchA-bgp-ipv4] peer 10.1.2.2 next-hop-local [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch B. system-view [SwitchB] bgp 65002 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] confederation id 200 [SwitchB-bgp] confederation peer-as 65001 65003 [SwitchB-bgp] peer 10.1.1.
[SwitchD-bgp] peer 10.1.5.2 as-number 65001 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 10.1.3.1 enable [SwitchD-bgp-ipv4] peer 10.1.5.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit # Configure Switch E. system-view [SwitchE] bgp 65001 [SwitchE-bgp] router-id 5.5.5.5 [SwitchE-bgp] confederation id 200 [SwitchE-bgp] peer 10.1.4.1 as-number 65001 [SwitchE-bgp] peer 10.1.5.1 as-number 65001 [SwitchE-bgp] address-family ipv4 unicast [SwitchE-bgp-ipv4] peer 10.1.4.
Network * >i 9.1.1.0/24 NextHop MED LocPrf PrefVal Path/Ogn 10.1.1.1 0 100 0 (65001) 100i [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 65002 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 10.1.1.1 (1.1.1.1) Relay nexthop : 10.1.1.1 Original nexthop: 10.1.1.
State : valid, internal-confed, best, The output indicates the following: • Switch F can send route information to Switch B and Switch C through the confederation by establishing only an EBGP connection to Switch A. • Switch B and Switch D are in the same confederation, but belong to different sub-ASs. They obtain external route information from Switch A and generate identical BGP route entries although they have no direct connection in between.
# Configure Switch C. system-view [SwitchC] ospf [SwitchC-ospf] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. system-view [SwitchD] ospf [SwitchD-ospf] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] quit 3.
# Configure Switch D. [SwitchD] bgp 200 [SwitchD-bgp] peer 194.1.1.2 as-number 200 [SwitchD-bgp] peer 195.1.1.2 as-number 200 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 194.1.1.2 enable [SwitchD-bgp-ipv4] peer 195.1.1.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit 4. Configure attributes for route 1.0.0.0/8, making Switch D give priority to the route learned from Switch C: { (Method 1.) Configure a higher MED value for the route 1.0.0.0/8 advertised from Switch A to peer 192.
* >i 1.0.0.0 193.1.1.1 50 100 0 100i * 192.1.1.1 100 100 0 100i i Route 1.0.0.0/8 is the optimal. { (Method 2.) Configure different local preferences on Switch B and C for route 1.0.0.0/8, making Switch D give priority to the route from Switch C: # Define an ACL numbered 2000 on Switch C, permitting route 1.0.0.0/8. [SwitchC] acl number 2000 [SwitchC-acl-basic-2000] rule permit source 1.0.0.0 0.255.255.
Figure 67 Network diagram Configuration procedure 1. Configure Switch A: # Configure IP addresses for interfaces. (Details not shown.) # Configure the EBGP connection. system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 200.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchA-bgp] graceful-restart # Inject network 8.0.0.0/8 to the BGP routing table. [SwitchA-bgp] address-family ipv4 [SwitchA-bgp-ipv4] network 8.0.0.
system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 9.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchC-bgp] graceful-restart # Enable Switch C to exchange IPv4 unicast routing information with Switch B. [SwitchC-bgp-ipv4] peer 9.1.1.1 enable Verifying the configuration Ping Switch C on Switch A. Meanwhile, perform an active/standby switchover on Switch B. The ping operation is successful during the whole switchover process.
Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure OSPF to make sure that Switch A and Switch C are reachable to each other. (Details not shown.) 3. Configure BGP on Switch A: # Establish two IBGP connections to Switch C. system-view [SwitchA] bgp 200 [SwitchA-bgp] peer 3.0.2.2 as-number 200 [SwitchA-bgp] peer 2.0.2.2 as-number 200 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 3.0.2.2 enable [SwitchA-bgp-ipv4] peer 2.0.2.
[SwitchC-bgp-ipv4] peer 3.0.1.1 enable [SwitchC-bgp-ipv4] peer 2.0.1.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Enable BFD for peer 3.0.1.1. [SwitchC-bgp] peer 3.0.1.1 bfd [SwitchC-bgp] quit [SwitchC] quit Verifying the configuration # Display detailed BFD session information on Switch C. display bfd session verbose Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 513 Source IP: 3.0.2.
Protocol: BGP Process ID: 0 SubProtID: 0x1 Cost: 50 Tag: 0 OrigTblID: 0x1 TableID: 0x2 NBRID: 0x15000001 AttrID: 0x1 Age: 00h00m09s Preference: 255 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 3.0.1.1 Flags: 0x10060 OrigNextHop: 3.0.1.1 Label: NULL RealNextHop: 3.0.2.1 BkLabel: NULL Tunnel ID: Invalid BkTunnel ID: Invalid BkNextHop: N/A Interface: Vlan-interface101 BkInterface: N/A The output shows that Switch C communicates with network 1.1.1.
Figure 69 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure IBGP: # Configure Switch B. system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 9::2 as-number 65009 [SwitchB-bgp] address-family ipv6 [SwitchB-bgp-ipv6] peer 9::2 enable [SwitchB-bgp-ipv6] quit # Configure Switch C. system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.
# Configure Switch B. [SwitchB-bgp-ipv6] network 10:: 64 [SwitchB-bgp-ipv6] network 9:: 64 [SwitchB-bgp-ipv6] quit [SwitchB-bgp] quit # Configure Switch C. [SwitchC-bgp-ipv6] network 9:: 64 [SwitchC-bgp-ipv6] quit [SwitchC-bgp] quit Verifying the configuration # Display IPv6 BGP peer information on Switch B. [SwitchB] display bgp peer ipv6 BGP local router ID: 2.2.2.
PrefVal : 0 MED OutLabel : NULL : 0 Path/Ogn: 65009i * > Network : 50:: PrefixLen : 64 NextHop : :: LocPrf : PrefVal : 32768 OutLabel : NULL MED : 0 Path/Ogn: i The output shows that Switch A has learned routing information of AS 65009. # Display IPv6 BGP routing table information on Switch C. [SwitchC] display bgp routing-table ipv6 Total number of routes: 4 BGP local router ID is 3.3.3.
IPv6 BGP route reflector configuration example Network requirements In Figure 70, run EBGP between Switch A and Switch B, run IBGP between Switch C and Switch B, and between Switch C and Switch D. Switch C is a route reflector with clients Switch B and D. Figure 70 Network diagram Configuration procedure 1. Configure IPv6 addresses for interfaces and IPv4 addresses for loopback interfaces. (Details not shown.) 2.
[SwitchB-bgp] quit # Configure Switch C. system-view [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 101::2 as-number 200 [SwitchC-bgp] peer 102::2 as-number 200 [SwitchC-bgp] address-family ipv6 [SwitchC-bgp-ipv6] peer 101::2 enable [SwitchC-bgp-ipv6] peer 102::2 enable [SwitchC-bgp-ipv6] network 101:: 96 [SwitchC-bgp-ipv6] network 102:: 96 # Configure Switch D. system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.
* >i Network : 101:: PrefixLen : 96 NextHop : 102::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL MED : 0 Path/Ogn: i * > Network : 102:: PrefixLen : 96 NextHop : :: LocPrf : PrefVal : 32768 OutLabel : NULL MED : 0 Path/Ogn: i * i Network : 102:: PrefixLen : 96 NextHop : 102::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL MED : 0 Path/Ogn: i The output shows that Switch D has learned the network 1::/64 from Switch C through route reflection.
Switch A Switch B Vlan-int100 3000::1/64 Vlan-int200 2000::1/64 Vlan-int100 3000::2/64 Vlan-int101 3001::2/64 Switch C Switch D Vlan-int101 3001::3/64 Vlan-int201 2001::3/64 Vlan-int200 2000::2/64 Vlan-int201 2001::2/64 Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2. Configure OSPFv3 so that Switch A and Switch C can reach each other. (Details not shown.) 3. Configure IPv6 BGP on Switch A: # Establish two IBGP connections to Switch C.
[SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 3000::1 as-number 200 [SwitchC-bgp] peer 2000::1 as-number 200 [SwitchC-bgp] address-family ipv6 [SwitchC-bgp-ipv6] peer 3000::1 enable [SwitchC-bgp-ipv6] peer 2000::1 enable [SwitchC-bgp-ipv6] quit # Enable BFD for peer 3001::1. [SwitchC-bgp] peer 3000::1 bfd [SwitchC-bgp] quit [SwitchC] quit Verifying the configuration # Display detailed BFD session information on Switch C.
display ipv6 routing-table 1200::0 64 verbose Summary Count : 1 Destination: 1200::/64 Protocol: BGP4+ SubProtID: 0x1 Cost: 50 Tag: 0 OrigTblID: 0x1 TableID: 0xa NBRID: 0x25000001 AttrID: 0x1 Process ID: 0 Age: 00h01m07s Preference: 255 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 3000::1 Flags: 0x10060 OrigNextHop: 3000::1 Label: NULL RealNextHop: FE80::20C:29FF:FE4A:3873 BkLabel: NULL Tunnel ID: Invalid BkTunnel ID: Invalid BkNextHop: N/A Interface: Vlan-interfac
Troubleshooting BGP Symptom Display BGP peer information by using the display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command. The state of the connection to a peer cannot become established. Analysis To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange Open messages successfully. Solution 1. Use the display current-configuration command to verify the current configuration, and verify that the peer's AS number is correct. 2.
Configuring PBR Introduction to PBR Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop and other parameters for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: 1. The device uses PBR to forward matching packets. 2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets. 3.
Relationship between the match mode and clauses on the node Does a packet match all the if-match clauses on the node? Match mode Permit Deny • If the node is configured with an apply clause, PBR executes the apply clause on the node. Yes. • If the node is configured with no The packet is forwarded according to the routing table. PBR matches the packet against the next node. PBR matches the packet against the next node. apply clause, the packet is forwarded according to the routing table. No.
Configuring match criteria for a node Step Command Remarks 1. Enter system view. system-view N/A 2. Enter policy node view. policy-based-route policy-name [ deny | permit ] node node-number N/A 3. Configure an ACL match criterion. if-match acl acl-number{ acl-number | name acl-name } By default, no ACL match criterion is configured.
Step Command Remarks 1. Enter system view. system-view N/A 2. Apply a policy locally. ip local policy-based-route policy-name By default, no policy is locally applied. Configuring interface PBR Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of packets received on the interface. The specified policy must already exist. Otherwise, the interface PBR configuration fails. You can apply only one policy to an interface.
PBR configuration examples Packet type-based local PBR configuration example Network requirements As shown in Figure 72, configure PBR on Switch A to forward all TCP packets to the next hop 1.1.2.2. Switch A forwards other packets according to the routing table. Figure 72 Network diagram Switch B Switch A Vlan-int10 1.1.2.1/24 Vlan-int10 1.1.2.2/24 Vlan-int20 1.1.3.1/24 Vlan-int20 1.1.3.2/24 Switch C Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20.
[SwitchB] vlan 10 [SwitchB-vlan10] quit # Configure the IP address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ip address 1.1.2.2 24 3. Configure Switch C: # Create VLAN 20. system-view [SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IP address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ip address 1.1.3.2 24 Verifying the configuration # Telnet to Switch B on Switch A. The operation succeeds.
Figure 73 Network diagram Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20. system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20. [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ip address 1.1.2.1 24 [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.3.
[SwitchA-Vlan-interface11] ip address 10.110.0.10 24 [SwitchA-Vlan-interface11] ip policy-based-route aaa [SwitchA-Vlan-interface11] quit 2. Configure Switch B: # Create VLAN 10. system-view [SwitchB] vlan 10 [SwitchB-vlan10] quit # Configure the IP address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ip address 1.1.2.2 24 [SwitchB-Vlan-interface10] quit # Configure a static route to subnet 10.110.0.0/24. [SwitchB] ip route-static 10.110.0.0 24 1.1.2.
Configuring IPv6 static routing Static routes are manually configured and cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. IPv6 static routing works well in a simple IPv6 network. Configuring an IPv6 static route Before you configure an IPv6 static route, complete the following tasks: • Configure parameters for the related interfaces.
Configuring BFD for IPv6 static routes BFD provides a general purpose, standard, and medium- and protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols and MPLS. For more information about BFD, see High Availability Configuration Guide. IMPORTANT: Enabling BFD for a flapping route could worsen the situation.
Step Command Remarks • Method 1: 2. Configure BFD control mode for an IPv6 static route.
Step Command Remarks • Method 1: 3. Configure BFD echo mode for an IPv6 static route.
Figure 74 Network diagram Host B 2::2/64 Vlan-int400 2::1/64 Vlan-int200 4::2/64 Vlan-int300 5::2/64 Switch B Vlan-int200 4::1/64 Vlan-int300 5::1/64 Vlan-int100 1::1/64 Vlan-int500 3::1/64 Switch C Switch A Host A 1::2/64 Host C 3::2/64 Configuration procedure 1. Configure the IPv6 addresses for all VLAN interfaces. (Details not shown.) 2. Configure IPv6 static routes: # Configure a default IPv6 static route on Switch A.
Summary Count : 2 Static Routing table Status : Summary Count : 2 Destination: 1::/64 Protocol NextHop : 4::1 Preference: 60 : Static Interface : Vlan-interface200 Cost : 0 Destination: 3::/64 Protocol : Static NextHop : 5::1 Preference: 60 Interface : Vlan-interface300 Cost : 0 Static Routing table Status : Summary Count : 0 # Use the ping command to test the reachability.
Figure 75 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int10 12::1/64 Switch B Vlan-int10 12::2/64 Vlan-int11 10::102/64 Vlan-int13 13::1/64 Switch C Vlan-int11 10:: 100/64 Vlan-int13 13::2/64 Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2.
Verifying the configuration # Display the BFD sessions on Switch A.
The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for IPv6 static routes configuration example (indirect next hop) Network requirements In Figure 76, Switch A has a route to interface Loopback 1 (2::9/128) on Switch B, with the output interface being VLAN-interface 10. Switch B has a route to interface Loopback 1 (1::9/128) on Switch A, with the output interface being VLAN-interface 12.
[SwitchA] ipv6 route-static 120:: 64 2::9 bfd control-packet bfd-source 1::9 [SwitchA] ipv6 route-static 120:: 64 10::100 preference 65 [SwitchA] quit # Configure IPv6 static routes on Switch B and enable BFD control packet mode for the static route that traverses Switch D.
Interface : Vlan10 Cost : 0 Static Routing table Status : Summary Count : 0 The output shows that Switch A communicates Switch B through VLAN-interface 10. The link over VLAN-interface 10 fails. # Display IPv6 static routes on Switch A again.
Configuring an IPv6 default route A default IPv6 route is used to forward packets that match no entry in the routing table. A default IPv6 route can be configured in either of the following ways: • The network administrator can configure a default route with a destination prefix of ::/0. For more information, see "Configuring an IPv6 static route." • Some dynamic routing protocols, such as OSPFv3, IPv6 IS-IS, and RIPng, can generate a default IPv6 route.
Configuring RIPng RIP next generation (RIPng) is an extension of RIP-2 for support of IPv6. Most RIP concepts are applicable to RIPng. Overview RIPng is a distance vector routing protocol. It employs UDP to exchange route information through port 521. RIPng uses a hop count to measure the distance to a destination. The hop count is the metric or cost. The hop count from a router to a directly connected network is 0. The hop count between two directly connected routers is 1.
2. When a RIPng neighbor receives the request packet, it sends back a response packet that contains the local routing table. RIPng can also advertise route updates in response packets periodically or advertise a triggered update caused by a route change. 3. After RIPng receives the response, it checks the validity of the response before adding routes to its routing table, such as whether the source IPv6 address is the link-local address and whether the port number is correct.
Step Enter interface view. 4. Command Remarks interface interface-type interface-number N/A By default, RIPng is disabled. Enable RIPng on the interface. 5. ripng process-id enable If RIPng is not enabled on an interface, the interface does not send or receive any RIPng route. Configuring RIPng route control Before you configure RIPng, complete the following tasks: • Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes. • Configure basic RIPng.
To configure RIPng route summarization: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Advertise a summary IPv6 prefix. ripng summary-address ipv6-address prefix-length By default, the summary IPv6 prefix is not configured. Advertising a default route Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view.
Configuring a preference for RIPng Routing protocols each have a preference. When they find routes to the same destination, the route found by the routing protocol with the highest preference is selected as the optimal route. You can manually set a preference for RIPng. The smaller the value, the higher the preference. To configure a preference for RIPng: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ] N/A Configure RIPng timers. timers { garbage-collect garbage-collect-value | suppress suppress-value | timeout timeout-value | update update-value } * 3. By default: • • • • The update timer is 30 seconds. The timeout timer is 180 seconds. The suppress timer is 120 seconds. The garbage-collect timer is 120 seconds.
RIPng does not process the packets. If you are certain that all packets are trustworthy, disable the zero field check to save CPU resources. To configure RIPng zero field check: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Enable the zero field check on incoming RIPng packets. checkzero By default, this feature is enabled. Configuring the maximum number of ECMP routes Step Command Remarks 1.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enable RIPng and enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Enable the GR capability for RIPng. graceful-restart By default, RIPng GR is disabled. Displaying and maintaining RIPng Execute display commands in any view and reset commands in user view. Task Command Display configuration information of a RIPng process. display ripng [ process-id ] Display routes in the RIPng database.
[SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 400 [SwitchA-Vlan-interface400] ripng 1 enable [SwitchA-Vlan-interface400] quit # Configure Switch B.
Destination 5::/64, via FE80::20F:E2FF:FE00:100, cost 1, tag 0, AOF, 11 secs # Display the RIPng routing table on Switch A.
Peer FE80::2:100 on Vlan-interface100 Destination 4::/64, via FE80::1:100, cost 2, tag 0, AOF, 2 secs RIPng route redistribution configuration example Network requirements As shown in Figure 78, Switch B communicates with Switch A through RIPng 100 and with Switch C through RIPng 200. Configure route redistribution on Switch B, so the two RIPng processes can redistribute routes from each other. Figure 78 Network diagram Configuration procedure 1. Configure IPv6 addresses for interfaces.
system-view [SwitchC] ripng 200 [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ripng 200 enable [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ripng 200 enable [SwitchC-Vlan-interface400] quit # Display the routing table on Switch A. [SwitchA] display ipv6 routing-table Destinations : 7 Routes : 7 3.
# Display the routing table on Switch A.
Configuring OSPFv3 This chapter describes how to configure RFC 2740-compliant Open Shortest Path First version 3 (OSPFv3) for an IPv6 network. For more information about OSPFv2, see "Configuring OSPF.
• Inter-Area-Router LSA—Type-4 LSA, originated by ABRs and flooded throughout the LSA's associated area. Each Inter-Area-Router LSA describes a route to ASBR. • AS External LSA—Type-5 LSA, originated by ASBRs, and flooded throughout the AS, except stub and NSSA areas. Each AS External LSA describes a route to another AS. A default route can be described by an AS External LSA. • Link LSA—Type-8 LSA. A router originates a separate Link LSA for each attached link. Link LSAs have link-local flooding scope.
Tasks at a glance (Optional.) Tuning and optimizing OSPFv3 networks: • • • • • • • • • Configuring OSPFv3 timers Specifying LSA transmission delay Configuring a DR priority for an interface Specifying SPF calculation interval Specifying the LSA generation interval Ignoring MTU check for DD packets Disabling interfaces from receiving and sending OSPFv3 packets Enabling the logging of neighbor state changes Configuring the LSU transmit rate (Optional.
Configuring OSPFv3 area parameters OSPFv3 has the same stub area and virtual link features as OSPFv2. After you split an OSPFv3 AS into multiple areas, the LSA number is reduced and OSPFv3 applications are extended. To further reduce the size of routing tables and the number of LSAs, configure the non-backbone areas at an AS edge as stub areas.
To configure a virtual link: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Enter OSPFv3 area view. area area-id N/A Configure a virtual link. vlink-peer router-id [ dead seconds | hello seconds | instance instance-id | retransmit seconds | trans-delay seconds ] * By default, no virtual link is configured. 4.
Configuring an NBMA or P2MP neighbor For NBMA and P2MP interfaces (only when in unicast mode), you must specify the link-local IP addresses of their neighbors because these interfaces cannot find neighbors through broadcasting hello packets. For NBMA interfaces, you can also specify DR priorities for neighbors. To configure an NBMA or P2MP (unicast) neighbor and its DR priority: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view.
Configuring OSPFv3 received route filtering According to some rules, you can configure OSPFv3 to filter routes calculated using received LSAs. To configure OSPFv3 to filter routes calculated using received LSAs: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A Configure OSPFv3 to filter routes calculated using received LSAs.
Step Command Remarks 2. Enter interface view. interface interface-type interface-number N/A 3. Configure an OSPFv3 cost for the interface. ospfv3 cost value [ instance instance-id ] By default, the OSPFv3 cost is 1 for a VLAN interface, is 0 for a loopback interface, and is automatically computed according to the interface bandwidth for other interfaces. To configure a bandwidth reference value: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view.
Step Command Remarks 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a preference for OSPFv3. preference [ ase ] [ route-policy route-policy-name ] preference By default, the preference of OSPFv3 internal routes is 10, and the priority of OSPFv3 external routes is 150. Configuring OSPFv3 route redistribution Because OSPFv3 is a link state routing protocol, it cannot directly filter LSAs to be advertised. OSPFv3 filters only redistributed routes.
Configuration prerequisites Before you tune and optimize OSPFv3 networks, complete the following tasks: • Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes. • Enable OSPFv3. Configuring OSPFv3 timers Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the hello interval.
Specifying SPF calculation interval LSDB changes result in SPF calculations. When the topology changes frequently, a large amount of network and router resources are occupied by SPF calculation. You can adjust the SPF calculation interval to reduce the impact. When network changes are not frequent, the minimum-interval is adopted.
To configure a DR priority for an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure a router priority. ospfv3 dr-priority priority [ instance instance-id ] The default router priority is 1. Ignoring MTU check for DD packets When LSAs are few in DD packets, it is unnecessary to check the MTU in DD packets to improve efficiency. To ignore MTU check for DD packets: Step Command Remarks 1.
Enabling the logging of neighbor state changes With this feature enabled, the router delivers logs about neighbor state changes to its information center, which processes logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see Network Management and Monitoring Configuration Guide. To enable the logging of neighbor state changes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view.
After the active/standby switchover, the GR restarter sends a Grace LSA to tell its neighbors that it performs a GR. Upon receiving the Grace LSA, the neighbors with the GR helper capability enter the helper mode (and are called "GR helpers"). Then, the GR restarter retrieves its adjacencies and LSDB with the help of the GR helpers. Configuring GR restarter You can configure the GR restarter capability on a GR restarter. To configure GR restarter: Step Command Remarks 1. Enter system view.
To configure BFD for OSPFv3, you need to configure OSPFv3 first. To configure BFD for OSPFv3: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Specify a router ID. router-id router-id N/A 4. Quit the OSPFv3 view. quit N/A 5. Enter interface view. interface interface-type interface-number N/A 6. Enable an OSPFv3 process on the interface.
Purpose Command Display OSPFv3 statistics. display ospfv3 [ process-id ] statistics [ error ] Display OSPFv3 virtual link information. display ospfv3 [ process-id ] vlink OSPFv3 configuration examples OSPFv3 area configuration example Network requirements As shown in Figure 79: • Enable OSPFv3 on all switches. • Split the AS into three areas. • Configure Switch B and Switch C as ABRs to forward routing information between areas.
# Configure Switch B: enable OSPFv3 and specify the router ID as 2.2.2.2. system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 0 [SwitchB-Vlan-interface100] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 1 [SwitchB-Vlan-interface200] quit # Configure Switch C: enable OSPFv3 and specify the router ID as 3.3.3.3.
OSPFv3 Process 1 with Router ID 3.3.3.3 Area: 0.0.0.0 ------------------------------------------------------------------------Router ID Pri State Dead-Time Interface Inst ID 2.2.2.2 1 00:00:40 0 Full/DR Vlan100 Area: 0.0.0.2 ------------------------------------------------------------------------Router ID Pri State Dead-Time Interface Inst ID 4.4.4.4 1 00:00:40 0 Full/Backup Vlan400 # Display OSPFv3 routing table information on Switch D.
# Display OSPFv3 routing table information on Switch D. [SwitchD] display ospfv3 routing OSPFv3 Process 1 with Router ID 4.4.4.
Type : I Cost NextHop : directly-connected Interface: Vlan400 : 1 Total: 2 Intra area: 1 Inter area: 1 ASE: 0 The output shows that route entries are reduced. All indirect routes are removed, except the default route. OSPFv3 DR election configuration example Network requirements • Configure router priority 100 for Switch A, the highest priority on the network, so it will become the DR.
[SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 0 [SwitchB-Vlan-interface200] quit # Configure Switch C: enable OSPFv3 and specify the router ID as 3.3.3.3. system-view [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 0 [SwitchC-Vlan-interface100] quit # Configure Switch D: enable OSPFv3 and specify the router ID as 4.4.4.4.
[SwitchA-Vlan-interface100] quit # Configure the router priority of VLAN-interface 200 as 0 on Switch B. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 dr-priority 0 [SwitchB-Vlan-interface200] quit # Configure the router priority of VLAN-interface 100 of Switch C as 2. [SwitchC] interface Vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 dr-priority 2 [SwitchC-Vlan-interface100] quit # Display neighbor information on Switch A.
[SwitchD] display ospfv3 peer OSPFv3 Process 1 with Router ID 4.4.4.4 Area: 0.0.0.0 ------------------------------------------------------------------------Router ID Pri State Dead-Time Interface Inst ID 1.1.1.1 100 Full/DR 00:00:30 Vlan100 0 2.2.2.2 0 2-Way/DROther 00:00:37 Vlan200 0 3.3.3.3 2 Full/Backup 00:00:31 Vlan100 0 The output shows that Switch A becomes the DR.
[SwitchA-Vlan-interface200] ospfv3 1 area 2 [SwitchA-Vlan-interface200] quit # Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B. system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 2 [SwitchB-Vlan-interface100] quit [SwitchB] ospfv3 2 [SwitchB-ospfv3-2] router-id 3.3.3.
3. Destination: 4::1/128 Protocol NextHop : ::1 Preference: 0 : Direct Interface : InLoop0 Cost : 0 Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost : 0 Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Configure OSPFv3 route redistribution: # Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B.
Destination: 4::1/128 Protocol NextHop : ::1 Preference: 0 : Direct Interface : InLoop0 Cost : 0 Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost : 0 Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 OSPFv3 GR configuration example Network requirements • As shown in Figure 82, Switch A, Switch B, and Switch C that reside in the same AS and the same OSPFv3 routing domain are GR capable.
[SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 1 [SwitchB-Vlan-interface100] quit # On Switch C, enable OSPFv3 and set the router ID to 3.3.3.3. (By default, GR helper is enabled on Switch C.) system-view [SwitchC] ospfv3 1 [SwitchC-ospfv3-1] router-id 3.3.3.
Configuration procedure 1. Configure IPv6 addresses for the interfaces. (Details not shown.) 2. Configure basic OSPFv3: # On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1. system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.
[SwitchB] bfd session init-mode active [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ospfv3 bfd enable [SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Switch A.
Configuring IPv6 IS-IS IPv6 IS-IS supports all IPv4 IS-IS features except that it advertises IPv6 routing information. This chapter describes only IPv6 IS-IS specific configuration tasks. For information about IS-IS, see "Configuring IS-IS." Overview Intermediate System-to-Intermediate System (IS-IS) supports multiple network protocols, including IPv6. To support IPv6, the IETF added two type-length-values (TLVs) and a new network layer protocol identifier (NLPID).
Configuring IPv6 IS-IS route control Before you configure IPv6 IS-IS route control, complete basic IPv6 IS-IS configuration. To configure IPv6 IS-IS route control: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Specify a preference for IPv6 IS-IS routes. ipv6 preference { route-policy route-policy-name | preference } * By default, the default setting is 15. 4. Configure an IPv6 IS-IS summary route.
Step Command 12. Specify the maximum number of ECMP routes for load balancing. Remarks By default, the maximum number of ECMP routes is the same as that configured in the max-ecmp-num command. ipv6 maximum load-balancing number For more information about the max-ecmp-num command, see Layer 3—IP Routing Command Reference. Tuning and optimizing IPv6 IS-IS networks Configuration prerequisites Before you tune and optimize IPv6 IS-IS networks, complete basic IPv6 IS-IS tasks.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enable an IS-IS process and enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] N/A 3. Configure the NET for the IS-IS process. network-entity net By default, no NET is configured. 4. Enable IPv6 for the IS-IS process. ipv6 enable By default, IPv6 for the IS-IS process is disabled. 5. Return to system view. quit N/A 6. Enter interface view. interface interface-type interface-number N/A 7.
Figure 84 Network diagram Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2. Configure IPv6 IS-IS: # Configure Switch A. system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] ipv6 enable [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis ipv6 enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B.
[SwitchC-Vlan-interface200] isis ipv6 enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis ipv6 enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D. system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.
Route information for IS-IS(1) ------------------------------ Level-1 IPv6 Forwarding Table ----------------------------- Destination : :: PrefixLen: 0 Flag : R/-/- Cost Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200 : 10 Destination : 2001:1:: PrefixLen: 64 Flag : D/L/- Cost Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200 : 10 Destination : 2001:2:: PrefixLen: 64 Flag : R/-/- Cost Next Hop : Direct Interface: Vlan200 : 20 Destination : 2001:3:: PrefixLen: 64 Flag : R/-/
----------------------------- Destination : 2001:1:: PrefixLen: 64 Flag : D/L/- Cost Next Hop : Direct Interface: Vlan100 : 10 Destination : 2001:2:: PrefixLen: 64 Flag : D/L/- Cost Next Hop : Direct Interface: Vlan200 : 10 Destination : 2001:3:: PrefixLen: 64 Flag : D/L/- Cost Next Hop : Direct Interface: Vlan300 : 10 Destination : 2001:4::1 PrefixLen: 128 Flag : R/-/- Cost Next Hop : FE80::20F:E2FF:FE3E:FA3D Interface: Vlan300 : 10 Flags: D-Direct, R-Added to Rib, L-Ad
BFD for IPv6 IS-IS configuration example Network requirements • As shown in Figure 85, configure IPv6 IS-IS on Switch A and Switch B so that they can reach other. • Enable BFD on VLAN-interface 10 of Switch A and Switch B. After the link between Switch B and the Layer-2 switch fails, BFD can quickly detect the failure and notify IPv6 IS-IS of the failure. Then Switch A and Switch B communicate through Switch C.
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] ipv6 enable [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] isis ipv6 enable 1 [SwitchB-Vlan-interface10] quit [SwitchB] interface vlan-interface 13 [SwitchB-Vlan-interface13] isis ipv6 enable 1 [SwitchB-Vlan-interface13] quit # Configure Switch C. system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.
Source IP: FE80::20F:FF:FE00:1202 (link-local address of VLAN-interface 10 on Switch A) Destination IP: FE80::20F:FF:FE00:1200 (link-local address of VLAN-interface 10 on Switch B) Session State: Up Interface: Vlan10 Hold Time: 2319ms # Display routes destined for 2001:4::0/64 on Switch A.
Configuring IPv6 PBR Introduction to IPv6 PBR Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop and other parameters for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: 1. The device uses PBR to forward matching packets. 2.
Relationship between the match mode and clauses on the node Does a packet match all the if-match clauses on the node? Match mode In permit mode In deny mode • If the node is configured with an apply clause, IPv6 PBR executes the apply clause on the node. Yes • If the node is configured with no The packet is forwarded according to the routing table. IPv6 PBR matches the packet against the next node. IPv6 PBR matches the packet against the next node.
Step 2. Create an IPv6 policy or policy node, and enter IPv6 policy node view. Command Remarks ipv6 policy-based-route policy-name [ deny | permit ] node node-number By default, no IPv6 policy node is created. Configuring match criteria for an IPv6 node Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 policy node view. ipv6 policy-based-route policy-name [ deny | permit ] node node-number N/A 3. Configure an ACL match criterion.
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy. Do not configure IPv6 local PBR unless required. To configure IPv6 local PBR: Step Command Remarks 1. Enter system view. system-view N/A 2. Apply a policy locally. ipv6 local policy-based-route policy-name By default, no policy is locally applied. Configuring IPv6 interface PBR Configure IPv6 PBR by applying an IPv6 policy to an interface.
Task Command Clear IPv6 PBR statistics. reset ipv6 policy-based-route statistics [ policy policy-name ] IPv6 PBR configuration examples Packet type-based IPv6 local PBR configuration example Network requirements As shown in Figure 86, configure IPv6 PBR on Switch A to forward all TCP packets to the next hop 1::2. Switch A forwards other packets according to the routing table. Figure 86 Network diagram Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20.
[SwitchA] ipv6 local policy-based-route aaa 2. Configure Switch B: # Create VLAN 10. system-view [SwitchB] vlan 10 [SwitchB-vlan10] quit # Configure the IPv6 address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ipv6 address 1::2 64 3. Configure Switch C: # Create VLAN 20. system-view [SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IPv6 address of VLAN-interface 20.
Figure 87 Network diagram Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20. system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure RIPng.
[SwitchA-pbr6-aaa-5] apply next-hop 1::2 [SwitchA-pbr6-aaa-5] quit # Configure IPv6 interface PBR by applying policy aaa to VLAN-interface 11. [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] ipv6 address 10::2 64 [SwitchA-Vlan-interface11] undo ipv6 nd ra halt [SwitchA-Vlan-interface11] ripng 1 enable [SwitchA-Vlan-interface11] ipv6 policy-based-route aaa 2. Configure Switch B: # Create VLAN 10. system-view [SwitchB] vlan 10 [SwitchB-vlan10] quit # Configure RIPng.
367
Configuring routing policies Routing policies control routing paths by filtering and modifying routing information. This chapter describes both IPv4 and IPv6 routing policies. Overview Routing policies can filter advertised, received, and redistributed routes, and modify attributes for specific routes. To configure a routing policy: 1. Configure filters based on route attributes, such as destination address and the advertising router's address. 2.
For more information about extended community lists, see MPLS Configuration Guide. Routing policy A routing policy can comprise multiple nodes, which are in a logical OR relationship. A node with a smaller number is matched first. A route (except the route configured with the continue clauses) that matches one node matches the routing policy. Each node has a match mode of permit or deny. • permit—Specifies the permit match mode for a routing policy node.
Step Command Remarks 1. Enter system view. system-view N/A 2. Configure an IPv4 prefix list. ip prefix-list prefix-list-name [ index index-number ] { deny | permit } ip-address mask-length [ greater-equal min-mask-length ] [ less-equal max-mask-length ] By default, no IPv4 prefix list is configured. Configuring an IPv6 prefix list If all items are set to deny mode, no routes can pass the IPv6 prefix list.
Step Command Remarks • Configure a basic community list: 2. Configure a community list. ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit } [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] * Use either method. • Configure an advanced community list: ip community-list { adv-comm-list-num | advanced adv-comm-list-name } { deny | permit } regular-expression By default, no community list is configured.
Configuring if-match clauses You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit-mode node, all routing information can pass the node. If no if-match clause is specified for a deny-mode node, no routing information can pass the node. The if-match clauses of a routing policy node have a logical AND relationship. A route must meet all if-match clauses before it can be executed by the apply clauses of the node.
Step Command Remarks if-match local-preference preference By default, no local preference is configured for BGP routes. 10. Match routes having MPLS labels. if-match mpls-label By default, no MPLS label match criterion is configured. 11. Match routes having the specified route type.
Step Command Remarks • Set the next hop for IPv4 9. Set the next hop for routes. routes: apply ip-address next-hop ip-address [ public | vpn-instance vpn-instance-name ] • Set the next hop for IPv6 routes: apply ipv6 next-hop ipv6-address By default, no next hop is set for IPv4/IPv6 routes. The apply ip-address next-hop and apply ipv6 next-hop commands do not apply to redistributed IPv4 and IPv6 routes. 10. Redistribute routes to a specified ISIS level.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter routing policy node view. route-policy route-policy-name { deny | permit } node node-number N/A 3. Specify the next node to be matched. By default, no continue clause is configured. continue [ node-number ] The specified next node must have a larger number than the current node. Displaying and maintaining the routing policy Execute display commands in any view and reset commands in user view.
Figure 88 Network diagram IS-IS OSPF Vlan-int100 192.168.1.2/24 Switch B Vlan-int200 192.168.2.2/24 Vlan-int201 172.17.1.1/24 Vlan-int100 192.168.1.1/24 Vlan-int200 192.168.2.1/24 Vlan-int202 172.17.2.1/24 Switch C Switch A Vlan-int203 172.17.3.1/24 Configuration procedure 1. Specify IP addresses for interfaces. (Details not shown.) 2. Configure IS-IS: # Configure Switch C. system-view [SwitchC] isis [SwitchC-isis-1] is-level level-2 [SwitchC-isis-1] network-entity 10.0000.0000.0001.
[SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # On Switch B, configure OSPF and enable route redistribution from IS-IS. [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] import-route isis 1 [SwitchB-ospf-1] quit # Display the OSPF routing table on Switch A to view redistributed routes.
[SwitchB-route-policy-isis2ospf-30] quit 6. Apply the routing policy to route redistribution: # On Switch B, enable route redistribution from IS-IS and apply the routing policy. [SwitchB] ospf [SwitchB-ospf-1] import-route isis 1 route-policy isis2ospf [SwitchB-ospf-1] quit # Display the OSPF routing table on Switch A. [SwitchA] display ospf routing OSPF Process 1 with Router ID 192.168.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 192.168.1.
[SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 address 10::1 32 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ipv6 address 11::1 32 [SwitchA-Vlan-interface200] quit # Enable RIPng on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit # Configure three static routes with next hop 11::2, and make sure that the static routes are active.
via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 8 secs Destination 40::/32, via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 3 secs 380
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons 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. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index Numerics IP routing OSPF summary route advertisement, 100 4-byte IP routing RIP default route, 28 IP routing RIP on interface, 25 IPv4 BGP AS number suppression, 227 IP routing RIP summary route advertisement configuration, 45 IPv6 BGP AS number suppression, 227 A IP routing RIPv2 summary route, 27 ABR IPv4 BGP basic configuration, 244 IP routing OSPF route summarization on ABR, 74 IPv4 BGP BFD configuration, 272 IP routing OSPF router type, 62 IPv4 BGP COMMUNITY configuration, 235, 257 A
IPv4 BGP MED AS route comparison (diff ASs), 213, 213 IP routing OSPF network type configuration, 71 IP routing OSPF NSSA area, 62 IPv4 BGP MED AS route comparison (per-AS), 214, 214 IP routing OSPF NSSA area configuration, 70, 106 IPv4 BGP MED default value, 212 IP routing OSPF stub area, 62 IPv4 BGP path selection configuration, 267 IP routing OSPF stub area configuration, 69, 103 IPv4 BGP private AS number removal, 222 IP routing OSPF totally NSSA area, 62 IPv4 BGP route reflector configuration
IP routing IS-IS FRR automatic backup next hop calculation, 150 IPv4 BGP fake AS number advertisement, 220 IPv4 BGP local AS number appearance, 218, 218 IPv4 BGP MED AS route comparison (confederation peers), 215 IPv4 BGP route automatic summarization, 200 automatic IP routing IS-IS automatic cost calculation, 134 IPv4 BGP MED AS route comparison (diff ASs), 213 IPv4 BGP MED AS route comparison (per-AS), 214 IPv4 BGP MED default value, 212 IP routing RIPv2 automatic route summarization enable, 27 B back
static route BFD bidirectional control mode (direct next hop), 9 route dampening, 180 static route BFD bidirectional control mode (indirect next hop), 9 route filtering policies, 203 route distribution control, 199 route generation, 197 static route BFD configuration, 9 route reception control, 199 static route BFD single-hop echo mode, 10 route recursion, 179 BGP, 174, See also MP-BGP route reflection configuration, 236 AS_PATH attribute configuration, 218 route reflector, 180 basic configurat
BGP confederation compatibility, 239 OSPFv3 network type configuration (for interface), 323 IPv4 BGP confederation configuration, 263 IPv4 BGP MED AS route comparison (confederation peers), 215 C calculating IPv6 BGP MED AS route comparison (confederation peers), 215 IP routing IS-IS SPF calculation interval, 142 IP routing OSPF FRR backup next hop calculation (LFA algorithm), 93 configuring basic IP routing, 1 IP routing OSPF interface cost, 75 BGP, 174, 186 IP routing OSPF route calculation, 64
IP routing OSPF interface authentication, 83 IP routing IS-IS LSP timer, 140 IP routing IS-IS LSP-calculated route filtering, 136 IP routing OSPF interface cost, 75 IP routing IS-IS neighbor relationship authentication, 147 IP routing OSPF LSDB max number external LSAs, 84 IP routing IS-IS network management, 146 IP routing OSPF LSU transmit rate, 87 IP routing IS-IS redistributed route filtering, 137 IP routing OSPF max number ECMP routes, 76 IP routing IS-IS route control, 132 IP routing OSPF NB
IPv4 BGP holdtime, 223 IP routing policy if-match clause, 372 IP routing policy IP prefix list, 369 IPv4 BGP keepalive interval, 223 IP routing policy IPv4 prefix list, 369 IPv4 BGP load balancing, 228, 254 IP routing policy IPv6 prefix list, 370 IPv4 BGP manual soft reset, 232 IP routing RIB label max lifetime, 4 IPv4 BGP MED default value, 212 IP routing RIB route max lifetime, 4 IPv4 BGP NEXT_HOP attribute, 216 IP routing RIP, 22, 24, 39 IPv4 BGP path selection, 267 IP routing RIP additional
IPv6 IS-IS route control, 349 OSPFv3 stub area, 322 IPv6 PBR, 359, 360, 361, 363 OSPFv3 timer, 328 IPv6 PBR interface, 362 OSPFv3 virtual link, 322 IPv6 PBR interface (packet type-based), 364 PBR, 286, 287, 288, 290 IPv6 PBR local, 361 PBR interface, 289 IPv6 PBR local (packet type-based), 363 PBR interface (packet type-based), 291 IPv6 PBR node action, 361 PBR local, 288 IPv6 PBR node match criteria, 361 PBR local (packet type-based), 290 IPv6 PBR policy, 360 PBR node action, 288 IPv6 sta
BGP path selection, 209 IP routing OSPF redistributed route default parameters, 78 BGP route distribution, 199 BGP route reception, 199 IP routing RIP default route advertisement, 28 IP routing IS-IS route control, 132 IPv4 BGP default local preference, 211 IP routing IS-IS SPF calculation interval, 142 IPv4 BGP MED default value, 212 IP routing OSPF route control, 73 IPv6 BGP default local preference, 211 IPv6 BGP MED default value, 212 IP routing RIP additional routing metric configuration, 27
IP routing IS-IS routing domain authentication, 147 IPv4 BGP route summarization, 251 IPv4 BGP-IGP route redistribution, 248 DR IPv6 BGP basic configuration, 275 IP routing OSPF, 64 IPv6 BGP BFD configuration, 281 IP routing OSPF DR election, 108 IPv6 BGP configuration, 275 IP routing OSPF election, 65 IPv6 BGP route reflector configuration, 279 OSPFv3 DR election configuration, 338 OSPFv3 interface DR priority, 329 DIS IP routing IS-IS DIS election, 127 DSCP IP routing IS-IS DIS election confi
IP routing OSPF DR election, 108 IPv6 BGP MED AS route comparison (diff ASs), 213 OSPFv3 DR election configuration, 338 IPv6 BGP MED AS route comparison (per-AS), 214 IPv6 BGP multiple hop EBGP session establishment, 225 enabling BGP, 188 BGP session state change logging, 240 IPv6 BGP peer MD5 authentication, 227 BGP SNMP notification, 240 IPv6 BGP route refresh, 230 OSPFv3, 321 EBGP direct connections after link failure, 226 IP routing IS-IS, 131 IP routing IS-IS automatic cost calculation, 134 OS
IP routing policy apply clause configuration, 373 IP routing policy AS_PATH list, 368 IP routing policy AS_PATH list configuration, 370 RIPng received/redistributed route filtering, 309 flooding IP routing IS-IS LSP flash flooding, 142 format IP routing IS-IS address format, 123 IP routing policy community list, 368 IP routing policy community list configuration, 370 IP routing IS-IS NSAP address format, 123 forwarding IP routing OSPF GR configuration, 89 IP routing policy configuration, 368, 371, 375
garbage-collect timer (RIP), 30 IP routing IS-IS PDU type, 128 generating IP routing OSPF hello packet, 59 BGP route, 197 IP routing OSPF hello packet timer, 79 OSPFv3 LSA generation interval, 329 OSPFv3 packet type, 319 GR helper IP routing IS-IS GR configuration, 148 HO-DSP (IS-IS area address), 124 holdtime IP routing OSPF configuration, 91 IPv4 BGP, 223 IP routing OSPF GR configuration, 89 IPv6 BGP, 223 IP routing RIP GR helper configuration, 35 hop OSPFv3 GR configuration, 331 IP routi
IPv6 BGP ORIGINATOR_ID attribute, 237 IP routing OSPF LSA generation interval, 81 OSPFv3 DD packet MTU check, 330 IP routing OSPF LSU transmit rate, 87 IP routing OSPF SPF calculation interval, 80 IGP BGP ORIGIN path attribute, 175, 175 IPv4 BGP keepalive interval, 223 IP routing IS-IS basic configuration, 131, 152 IPv4 BGP route update interval, 225 IP routing IS-IS configuration, 123, 130, 152 IPv6 BGP keepalive interval, 223 IP routing IS-IS DIS election configuration, 157 IPv6 BGP route updat
BGP route recursion, 179 IS-IS interface hello packet send, 139 BGP route reflection configuration, 236 IS-IS interface packet send/receive, 139 BGP route selection, 179, 179 IS-IS ISPF enable, 145 BGP route summarization, 180, 199 IS-IS link cost configuration, 133 BGP session state change logging, 240 IS-IS LSDB overload bit, 143 BGP SNMP notification enable, 240 IS-IS LSP flash flooding, 142 BGP soft reset configuration, 230 IS-IS LSP fragment extension, 142 BGP TCP connection source addres
OSPF broadcast network type configuration for interface, 71 OSPF route redistribution from different routing protocol, 77 OSPF configuration, 59, 66, 96 OSPF route summarization configuration, 74 OSPF DD packet interface MTU, 84 OSPF route summarization on ABR, 74 OSPF default route redistribution, 78 OSPF SPF calculation interval, 80 OSPF DR election, 108 OSPF stub area configuration, 69, 103 OSPF ECMP route max number, 76 OSPF stub router configuration, 82 OSPF FRR backup next hop calculation
OSPFv3 virtual link configuration, 322 RIP host route reception disable, 28 PBR interface configuration, 289 interface RIP configuration, 43 PBR local configuration, 288 policy application to IPv4 route redistribution, 375 additional metric RIP interface advertisement control, 25 RIP interface reception control, 25 policy application to IPv6 route redistribution, 378 RIP max number ECMP routes, 32 policy apply clause configuration, 373 RIP neighbor specification, 33 policy AS_PATH list configura
static routing BFD configuration (indirect next hop), 17 RIPng packet, 306 RIPng packet zero configuration, 311 field check static routing configuration, 8, 12 RIPng poison configuration, 311 static routing configuration, 21 reverse RIPng preference, 310 default static routing FRR configuration, 19 RIPng received/redistributed route filtering, 309 RIPng route configuration, 308 IPv4 IP routing FIB route max lifetime, 5 IP routing IS-IS basic configuration, 131, 152 control IP routing IS-IS con
GR configuration, 270 IS-IS.
4-byte AS number suppression, 227 IPv6 IS-IS AS number substitution, 221 basic configuration, 348, 351 basic configuration, 275 BFD configuration, 350, 356 BFD configuration, 241, 281 configuration, 348, 351 COMMUNITY configuration, 235 displaying, 351 configuration, 275 network optimization, 350 default local preference, 211 network tuning, 350 default route advertisement to peer/peer group, 201 route control configuration, 349 displaying, 242 route convergence priority assignment, 350 IPv
authentication, 164 network optimization, 137 basic configuration, 131, 152 network security enhancement, 146 BFD configuration, 149, 168 network tuning, 137 broadcast network type, 127 NSAP address format, 123 circuit level configuration, 131 N-SEL, 124 configuration, 123, 130, 152 PDU CLVs, 129 CSNP packet send interval, 138 PDU hello type, 128 default route advertisement, 135 PDU LSP type, 128 DIS election, 127 PDU SNP type, 128 DIS election configuration, 157 PDU types, 128 displayin
IP routing IS-IS routes, 137 IPv4 BGP load balancing configuration, 254 IPv4 EBGP peer protection (level 2 threshold exemption), 234 OSPFv3 max number ECMP routes, 326 IPv6 BGP, 228 level IPv6 EBGP peer protection (level 2 threshold exemption), 234 RIPng max number ECMP routes, 312 load sharing IP routing IS-IS ECMP routes max number, 134 limiting IPv4 BGP routes received from peer/peer group, 202 IPv6 BGP routes received from peer/peer group, 202 IP routing load sharing, 3 IP routing RIP max numbe
OSPFv3 intra-area-prefix LSA, 319 manual IPv4 BGP route manual summarization, 200 OSPFv3 link LSA, 319 OSPFv3 LSA generation interval, 329 mapping OSPFv3 LSA transmission delay, 328 IP routing IS-IS system ID-host name mapping, 144 OSPFv3 network LSA, 319 IP routing IS-IS system ID-host name mapping (dynamic), 144 OSPFv3 NSSA LSA, 319 IP routing IS-IS system ID-host name mapping (static), 144 OSPFv3 router LSA, 319 LSAck IP routing OSPF LSAck packet, 59 matching IP routing policy if-match clause,
IP routing RIPv2 message authentication configuration, 33 MTU IP routing OSPF DD packet interface MTU, 84 metric OSPFv3 DD packet ignore MTU check, 330 IP routing RIP additional routing metric configuration, 27 multicast IP routing RIP interface additional metric configuration, 43 Multiprotocol Extensions for BGP-4.
BGP MED attribute, 212 IP routing IS-IS FRR configuration using routing policy, 150 BGP optimal route advertisement, 201 IP routing IS-IS global cost configuration, 133 BGP load balancing, 179 BGP optimization, 223 IP routing IS-IS GR configuration, 148 BGP path selection, 209 IP routing IS-IS hello multiplier, 138 BGP peer configuration, 189 BGP peer group, 180 IP routing IS-IS hello packet send interval, 138 BGP peer group configuration, 190 BGP route dampening, 180 IP routing IS-IS configurat
IP routing IS-IS authentication, 147 routing IP routing OSPF interface authentication configuration, 83 domain IP routing IS-IS security enhancement, 146 IP routing OSPF interface cost, 75 IP routing interval, 142 IP routing OSPF interface packet send/receive disable, 82 IS-IS SPF calculation IP routing IS-IS system ID-host name mapping, 144 IP routing OSPF ISPF enable, 87 IP routing OSPF LSA arrival interval, 81 IP routing IS-IS system ID-host name mapping (dynamic), 144 IP routing OSPF LSA g
IP routing OSPF configuration, 73 route IP routing RIP additional routing metric configuration, 27 control IP routing OSPF route redistribution, 77 IP routing RIP basic configuration, 24, 39 IP routing OSPF route redistribution from different routing protocol, 77 IP routing RIP BFD configuration, 36 IP routing RIP BFD configuration (bidirectional detection/control packet mode), 53 IP routing OSPF route summarization configuration, 74 IP routing RIP BFD configuration (single-hop echo detection/speci
IP routing RIP summary advertisement configuration, 45 route IPv4 BGP private AS number removal, 222 IPv4 BGP received route preferred value, 209 IP routing RIP timer configuration, 30 IPv4 BGP route dampening, 208 IP routing RIP update source IP address check, 33 IPv4 BGP route policies, 203 IP routing RIP version configuration, 26 IPv4 BGP policies, 206 IP routing RIPv1 message zero field check, 32 route reception filtering IPv4 BGP route reflector configuration, 236 IP routing RIPv2 message
OSPFv3 DD packet ignore MTU check, 330 IPv6 BGP route preference, 210 IPv6 BGP route policies, 206 reception IPv6 BGP configuration, 236 route OSPFv3 GR, 331 filtering OSPFv3 GR helper, 332 reflector OSPFv3 GR restarter, 332 OSPFv3 Inter-Area-Prefix LSA filtering, 325 IPv6 BGP route update interval, 225 OSPFv3 interface cost configuration, 325 IPv6 BGP route update save, 231 OSPFv3 interface DR priority, 329 IPv6 BGP route-refresh, 230 OSPFv3 interface disable, 330 IPv6 BGP routes received f
RIPng max number ECMP routes, 312 IP routing OSPF DR election, 108 RIPng network optimization, 310 IP routing OSPF FRR configuration, 119 IP routing OSPF GR configuration, 114 RIPng network tuning, 310 IP routing OSPF NSSA area configuration, 106 RIPng packet, 306 IP routing OSPF route redistribution, 99 RIPng packet zero field check, 311 IP routing OSPF stub area configuration, 103 RIPng poison reverse, 311 IP routing OSPF summary route advertisement, 100 IP routing OSPF virtual link configurati
OSPFv3 DR election configuration, 338 IPv6 PBR node action, 361 OSPFv3 GR configuration, 344 IPv6 PBR node creation, 360 OSPFv3 network optimization, 327 IPv6 PBR node match criteria configuration, 361 OSPFv3 network tuning, 327 IPv6 PBR policy, 359 OSPFv3 route redistribution, 341 IPv6 PBR/Track collaboration, 360 PBR configuration, 286, 287, 288, 290 PBR apply clause, 286 PBR interface configuration (packet type-based), 291 PBR creation, 287 PBR local configuration (packet type-based), 290
BGP route, 201 interface enable, 68 IP routing FIB table optimal routes, 1 interface packet send/receive disable, 82 IP routing IS-IS BFD configuration, 149 optimizing BGP network, 223 IP routing IS-IS DIS election, 127 IP routing IS-IS networks, 137 ISPF enable, 87 IP routing OSPF network, 79 LSA arrival interval, 81 IP routing RIP networks, 30 LSA generation interval, 81 IPv6 IS-IS networks, 350 LSA transmission delay, 80 OSPFv3 network, 327 LSA types, 60 RIPng network, 310 LSDB max numbe
route types, 63 P2MP neighbor configuration, 324 router types, 62 packet types, 319 SPF calculation interval, 80 preference configuration, 326 stub area, 62 protocols and standards, 320 stub area configuration, 69, 103 received route filtering, 325 stub router configuration, 82 route control configuration, 324 summary route advertisement, 100 route redistribution, 327, 341 timer configuration, 79 route summarization, 324 totally NSSA area, 62 SPF calculation interval, 329 totally stub area
IP routing OSPF basic configuration, 96 IPv6 PBR local configuration, 361 IP routing OSPF BFD configuration, 92 IPv6 PBR local configuration (packet type-based), 363 IP routing OSPF configuration, 59, 66, 96 IP routing OSPF DD, 59 IPv6 PBR policy, 359 IP routing OSPF DD packet interface MTU, 84 IPv6 PBR policy configuration, 360 IP routing OSPF exit overflow interval, 85 IP routing OSPF FRR configuration, 92 OSPFv3 area configuration, 334 IP routing OSPF GR configuration, 89 OSPFv3 BFD configurat
IP routing IS-IS types, 128 path BGP MED attribute configuration, 212 peer BGP path attributes, 175 BGP, 174 BGP path selection, 209 BGP configuration, 189 IP routing OSPF configuration, 59 IPv4 BGP COMMUNITY configuration, 257 BGP default route advertisement to peer/peer group, 201 IPv4 BGP MED AS route comparison (confederation peers), 215 BGP peer group, 180 BGP peer group configuration, 190 IPv4 BGP MED AS route comparison (diff ASs), 213 EBGP, 174 IPv4 BGP MED AS route comparison (per-AS),
IP routing policy AS_PATH list configuration, 370 IP routing OSPF default route redistribution, 78 IP routing policy community list configuration, 370 IP routing OSPF protocol preference configuration, 77 IP routing OSPF host route advertisement, 78 IP routing policy configuration, 368, 371, 375 IP routing OSPF redistributed route default parameters, 78 IP routing policy continue clause configuration, 374 IP routing policy creation, 371 IP routing OSPF route redistribution configuration, 77 IP rout
assigning IPv6 IS-IS route convergence priority, 350 configuring IP routing IS-IS LSP parameters, 140 configuring an IPv6 BGP peer, 190 configuring IP routing IS-IS LSP-calculated route filtering, 136 configuring IP routing IS-IS LSP timer, 140 configuring BGP, 186 configuring IP routing IS-IS neighbor relationship authentication, 147 configuring BGP AS_PATH attribute, 218 configuring BGP basics, 188 configuring IP routing IS-IS network management, 146 configuring BGP confederation, 238 configuring
configuring IP routing OSPF FRR, 92, 119 configuring IP routing OSPF redistributed route summarization on ASBR, 74 configuring IP routing OSPF FRR backup next hop calculation (LFA algorithm), 93 configuring IP routing OSPF route control, 73 configuring IP routing OSPF FRR backup next hop specification (routing policy), 94 configuring IP routing OSPF route redistribution, 77, 99 configuring IP routing OSPF GR, 89, 114 configuring IP routing OSPF route redistribution from different routing protocol, 77
configuring IPv4 BGP route dampening, 208 configuring IP routing RIP BFD single-hop echo detection, 47 configuring IPv4 BGP route distribution filtering policies, 203 configuring IP routing RIP FRR, 37, 56 configuring IPv4 BGP route manual summarization, 200 configuring IP routing RIP GR, 35 configuring IP routing RIP interface additional metric, 43 configuring IPv4 BGP route preference, 210 configuring IP routing RIP max number ECMP routes, 32 configuring IPv4 BGP route reception filtering policies
configuring IPv6 PBR local (packet type-based), 363 configuring OSPFv3 stub area, 322 configuring OSPFv3 timer, 328 configuring IPv6 PBR node action, 361 configuring OSPFv3 virtual link, 322 configuring IPv6 PBR node match criteria, 361 configuring PBR, 287, 288, 290 configuring IPv6 PBR policy, 360 configuring PBR interface, 289 configuring IPv6 static route, 294 configuring PBR interface (packet type-based), 291 configuring IPv6 static route BFD, 295 configuring PBR local, 288 configuring IPv6
controlling IP routing IS-IS SPF calculation interval, 142 enabling IP routing IS-IS neighbor state change logging, 145 controlling IP routing RIP interface advertisement, 25 enabling IP routing OSPF, 67 controlling IP routing RIP interface reception, 25 creating IP routing policy, 371 enabling IP routing OSPF neighbor state change logging, 86 creating IPv6 PBR node, 360 enabling IP routing OSPF on interface, 68 creating PBR node, 287 enabling IP routing OSPF on network, 68 disabling IP routing IS
enhancing IP routing IS-IS network security, 146 setting IP routing IS-IS LSDB overload bit, 143 generating BGP route, 197 setting IP routing RIP packet max length, 35 ignoring BGP first AS number of EBGP route updates, 223 specifying BGP TCP connection source address, 196 ignoring IPv4 BGP ORIGINATOR_ID attribute, 237 specifying IP routing IS-IS CSNP packet send interval, 138 ignoring IPv6 BGP ORIGINATOR_ID attribute, 237 specifying IP routing IS-IS hello multiplier, 138 ignoring OSPFv3 DD packet
IP routing OSPF, 65 basic configuration, 24, 39 IP routing OSPF preference, 77 BFD configuration, 36 IP routing OSPF RFC 1583 compatibility, 85 BFD configuration (bidirectional control detection), 37 IP routing RIP, 23 BFD configuration (bidirectional detection/control packet mode), 53 MP-BGP, 185 OSPFv3, 320 BFD configuration (single-hop echo detection/neighbor), 36 RIPng, 307 R BFD configuration (single-hop echo detection/specific destination), 36, 50 receiving IPv4 BGP routes received from pe
routing loop prevention, 22 RIP versions, 23 split horizon configuration, 31 route summarization configuration, 27 split horizon enable, 31 summary route advertisement, 27 summary route advertisement configuration, 45 version configuration, 26 timer configuration, 30 route update source IP address check, 33 BGP default route advertisement to peer/peer group, 201 version configuration, 26 BGP optimal route advertisement rules, 201 versions, 23 BGP route advertisement rules, 179 RIPng, 306, Se
IP routing OSPF route redistribution configuration, 77 IPv4 BGP route reflector configuration, 236, 260 IP routing OSPF route redistribution from different routing protocol, 77 IPv4 BGP route summarization, 251 IPv4 BGP route refresh, 230 IPv4 BGP route update interval, 225 IP routing OSPF route summarization configuration, 74 IPv4 BGP route update save, 231 IPv4 BGP routes received from peer/peer group, 202 IP routing OSPF route summarization on ABR, 74 IP routing OSPF stub area configuration, 103
IP routing policy community list configuration, 370 RIPng route control configuration, 308 RIPng route entry, 306 IP routing policy configuration, 368, 371, 375 RIPng route redistribution, 310, 316 IP routing policy continue clause configuration, 374 RIPng route summarization, 308 IP routing policy creation, 371 static route BFD configuration, 9 IP routing policy extended community list configuration, 371 static route configuration, 8 IP routing policy filter configuration, 369 static route FRR c
RIPng routing metric configuration, 308 SNP IS-IS PDU type, 128 RIPng split horizon configuration, 311 soft reset RIPng timer configuration, 310 BGP configuration, 230 tuning BGP network, 223 IPv4 BGP manual configuration, 232 Routing Information Protocol.
displaying, 12 switch FRR configuration, 19 IP routing RIP BFD configuration (bidirectional detection/control packet mode), 53 IPv6.
IP routing OSPF dead packet timer, 79 tuning IP routing OSPF hello packet timer, 79 BGP network, 223 IP routing OSPF LSA retransmission packet timer, 79 IP routing IS-IS network, 137 IP routing OSPF network, 79 IP routing OSPF packet timer, 79 IP routing RIP networks, 30 IP routing OSPF poll packet timer, 79 IPv6 IS-IS network, 350 IP routing RIP garbage-collect timer, 30 OSPFv3 network, 327 IP routing RIP suppress timer, 30 IP routing RIP timeout timer, 30 IP routing RIP update timer, 30 OSPFv3
zero field check RIPng packet, 311 zero field check (RIPv1), 32 433
