Page 1: Configuration Guide
HP 6125XLG Blade Switch Layer 3—IP Routing Configuration Guide Part number: 5998-3719 Software version: Rlease 2306 Document version: 6W100-20130912...
Page 2 HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Page 3: Table Of Contents
Contents IP routing basics ··························································································································································· 1 Routing table ······································································································································································ 1 Dynamic routing protocols ··············································································································································· 2 Route preference ······························································································································································· 2 Load sharing ······································································································································································ 3 Route backup ····································································································································································· 3 Route recursion ·································································································································································· 3 Route redistribution ··························································································································································· 3 ...
Page 4 Configuring RIP timers ··········································································································································· 28 Configuring split horizon and poison reverse ···································································································· 29 Configuring the maximum number of ECMP routes ·························································································· 29 Enabling zero field check on incoming RIPv1 messages ·················································································· 30 Enabling source IP address check on incoming RIP updates ············································································ 30 ...
Page 5 Tuning and optimizing OSPF networks ························································································································ 67 Configuration prerequisites ·································································································································· 67 Configuring OSPF timers ······································································································································ 68 Specifying LSA transmission delay ······················································································································ 68 Specifying SPF calculation interval ······················································································································ 69 Specifying the LSA arrival interval ······················································································································· 69 ...
Page 6 IS-IS configuration task list ··········································································································································· 115 Configuring basic IS-IS ················································································································································ 116 Configuration prerequisites ································································································································ 116 Enabling IS-IS ······················································································································································· 116 Configuring the IS level and circuit level ·········································································································· 116 Configuring P2P network type for an interface ································································································ 117 ...
Page 7 BGP message types ············································································································································· 158 BGP path attributes ············································································································································· 159 BGP route selection ············································································································································· 163 BGP route advertisement rules ··························································································································· 163 BGP load balancing ············································································································································ 163 Settlements for problems in large-scale BGP networks ···················································································· 164 ...
Page 8 BGP and IGP route redistribution configuration example ··············································································· 230 BGP route summarization configuration example ··························································································· 233 BGP load balancing configuration example ···································································································· 236 BGP community configuration example ············································································································ 239 BGP route reflector configuration example······································································································· 242 BGP confederation configuration example ·······································································································...
Page 9 Configuring RIPng route summarization ··········································································································· 288 Advertising a default route ································································································································· 289 Configuring received/redistributed route filtering ··························································································· 289 Configuring a preference for RIPng ··················································································································· 289 Configuring RIPng route redistribution ·············································································································· 290 Tuning and optimizing the RIPng network ················································································································· 290 ...
Page 10 OSPFv3 configuration examples ································································································································ 313 Configuring OSPFv3 areas ································································································································ 313 Configuring OSPFv3 DR election ······················································································································· 317 Configuring OSPFv3 route redistribution ·········································································································· 320 Configuring OSPFv3 GR ···································································································································· 323 Configuring BFD for OSPFv3 ····························································································································· 325 Configuring IPv6 IS-IS ············································································································································· 328 ...
Page 11 Subscription service ············································································································································ 357 Related information ······················································································································································ 357 Documents ···························································································································································· 357 Websites ······························································································································································· 357 Conventions ·································································································································································· 358 Index ········································································································································································ 360 ...
Page 12: Ip Routing Basics
IP routing basics IP routing directs IP packet forwarding on routers based on a routing table. This chapter focuses on unicast routing protocols. For more information about multicast routing protocols, see IP Multicast Configuration Guide. Routing table A router maintains at least two routing tables: a global routing table and a FIB. The FIB table contains only the optimal routes, and the global routing table contains all routes.
Page 13: Dynamic Routing Protocols
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.
Page 14: Load Sharing
Route type Preference Multicast static route OSPF IS-IS Unicast static route OSPF ASE OSPF NSSA IBGP EBGP Unknown (route from an untrusted source) Load sharing A routing protocol may find multiple optimal equal-cost routes to the same destination. You can use these routes to implement equal-cost multi-path (ECMP) load sharing.
Page 15: Configuring The Maximum Number Of Ecmp Routes
Configuring the maximum number of ECMP routes This configuration takes effect at next reboot. Make sure the reboot does not impact your network. To configure the maximum number of ECMP routes: Step Command Remarks Enter system view. system-view Configure the maximum By default, the maximum max-ecmp-num number number of ECMP routes.
Page 16 Task Command Display information about routes display ipv6 routing-table [ vpn-instance vpn-instance-name ] installed by an IPv6 protocol. protocol protocol [ inactive | verbose ] display ipv6 routing-table [ vpn-instance vpn-instance-name ] Display IPv6 route statistics. statistics reset ipv6 routing-table statistics protocol [ vpn-instance Clear IPv6 route statistics.
Page 17: Configuring Static Routing
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 properly. 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.
Page 18: Configuring Bfd For Static Routes
Step Command Remarks (Optional.) Delete all To delete one static route, static routes, delete [ vpn-instance vpn-instance-name ] use the undo ip route-static including the default static-routes all command. route. 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.
Page 19: Single-Hop Echo Mode
Step Command Remarks • Method 1: ip route-static dest-address { mask | mask-length } { next-hop-address bfd control-packet bfd-source ip-address | vpn-instance d-vpn-instance-name next-hop-address bfd control-packet bfd-source ip-address } [ preference preference-value ] [ tag Use either method. tag-value ] [ description description-text ] Configure BFD By default, BFD control control mode for a...
Page 20: Configuring Static Route Frr
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) 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...
Page 21: Displaying And Maintaining Static Routes
Step Command Remarks • Method 1: ip route-static dest-address { mask | mask-length } interface-type interface-number [ next-hop-address [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] ] ] [ permanent ] Use either method. Configure static route • Method 2: By default, static route FRR is FRR.
Page 22: Verifying The Configuration
Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure static routes: # Configure a default route on Switch A. <SwitchA> 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. <SwitchB> 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.
Page 23: Bfd For Static Routes Configuration Example (Direct Next Hop)
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.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Ping statistics for 1.1.2.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms # Use the tracert command on Host B to test the reachability of Host A.
Page 24 Configuration procedure Configure IP addresses for the interfaces. (Details not shown.) Configure static routes and BFD: # Configure static routes on Switch A and enable BFD control mode for the static route that traverses the Layer 2 switch. <SwitchA> system-view [SwitchA] interface vlan-interface 10 [SwitchA-vlan-interface10] bfd min-transmit-interval 500 [SwitchA-vlan-interface10] bfd min-receive-interval 500...
Page 25: Bfd For Static Routes Configuration Example (Indirect Next Hop)
Summary Count : 1 Destination/Mask Proto Cost NextHop Interface 120.1.1.0/24 Static 60 12.1.1.2 Vlan10 Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 10. Then the link over VLAN-interface 10 fails.
Page 26 Figure 4 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure static routes and BFD: # Configure static routes on Switch A and enable BFD control mode for the static route that traverses Switch D. <SwitchA> system-view [SwitchA] bfd multi-hop min-transmit-interval 500 [SwitchA] bfd multi-hop min-receive-interval 500 [SwitchA] bfd multi-hop detect-multiplier 9...
Page 27 IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 1.1.1.9 2.2.2.9 2000ms Loop1 The output shows that the BFD session has been created. # Display the static routes on Switch A. <SwitchA> display ip routing-table protocol static Summary Count : 1 Static Routing table Status : <Active>...
Page 28: Static Route Frr Configuration Example
Static route FRR configuration example Network requirements As shown in Figure 5, configure static routes on Switch S, Switch A, and Switch D, and configure static route FRR so when Link A becomes unidirectional, traffic can be switched to Link B immediately. Figure 5 Network diagram Configuration procedure Configure IP addresses for interfaces.
Page 29 OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NBRID: 0x26000002 LastAs: 0 AttrID: 0xffffffff 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.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.1/32...
Page 30: Configuring A Default Route
Configuring a default route A default route is used to forward packets that do not match any specific routing entry in the routing table. Without a default route, packets that do not match any routing 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 •...
Page 31: Configuring Rip
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.
Page 32: Rip Versions
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. 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.
Page 33: Configuring Basic Rip
Tasks at a glance (Optional.) Configuring RIP route control: • Configuring an additional routing metric • Configuring RIPv2 route summarization • Disabling host route reception • Advertising a default route • Configuring received/redistributed route filtering • Configuring a preference for RIP •...
Page 34: Controlling Rip Reception And Advertisement On Interfaces
Step Command Remarks By default, RIP is disabled on an interface. Enable the RIP process on the The network 0.0.0.0 command interface attached to the network network-address can enable RIP on all interfaces in specified network. a single process, but does not apply to multiple RIP processes.
Page 35: Configuring Rip Route Control
Step Command Remarks By default, no global version is specified, and an interface sends RIPv1 broadcasts, and can receive Specify a global RIP version. version { 1 | 2 } RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts. Return to system view.
Page 36: Configuring Ripv2 Route Summarization
Configuring RIPv2 route summarization Perform this task to summarize contiguous subnets into a summary network and sends the network to neighbors. The smallest metric among all summarized routes is used as the metric of the summary route. Enabling RIPv2 automatic route summarization Automatic summarization enables RIPv2 to generate a natural network for contiguous subnets.
Page 37: Disabling Host Route Reception
Disabling host route reception Perform this task to disable RIPv2 from receiving host routes from the same network to save network resources. This feature does not apply to RIPv1. To disable RIP from receiving host routes: Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view.
Page 38: Configuring Received/Redistributed Route Filtering
Configuring received/redistributed route filtering Perform this task to filter received and redistributed routes by using an IP prefix list. You can also configure RIP to receive routes only from a specified neighbor. To configure route filtering: Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view.
Page 39: Tuning And Optimizing Rip Networks
Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, RIP route redistribution is disabled. import-route protocol [ process-id Redistribute routes from | all-processes | allow-ibgp ] [ cost This command can redistribute another routing protocol.
Page 40: Configuring Split Horizon And Poison Reverse
Step Command Remarks rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default: timers { garbage-collect • The garbage-collect timer is 120 garbage-collect-value | suppress seconds. Configure RIP timers. suppress-value | timeout • The suppress timer is 120 seconds. timeout-value | update •...
Page 41: Enabling Zero Field Check On Incoming Ripv1 Messages
Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, the maximum number of ECMP routes is the same as that configured in the max-ecmp-num Configure the maximum maximum load-balancing number command.
Page 42: Configuring Ripv2 Message Authentication
Step Command Remarks Enable source IP address check on incoming RIP validate-source-address By default, this function is enabled. messages. Configuring RIPv2 message authentication Perform this task to enable authentication on RIPv2 messages. This feature does not apply to RIPv1 because RIPv1 does not support authentication. Although you can specify an authentication mode for RIPv1 in interface view, the configuration does not take effect.
Page 43: Configuring Bfd For Rip
Two routers are required to complete a GR process. The following are router roles in a GR process. • 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. •...
Page 44: Displaying And Maintaining Rip
Figure 6 Network diagram for RIP FRR 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.
Page 45: Rip Configuration Examples
Task Command display rip process-id interface [ interface-type Display RIP interface information. interface-number ] Display routing information about a specified RIP display rip process-id route [ ip-address { mask | process. mask-length } | peer ip-address | statistics ] Reset a RIP process. reset rip process-id process Clear statistics for a RIP process.
Page 46 ---------------------------------------------------------------------------- Peer 192.168.1.2 on Vlan-interface100 Destination/Mask Nexthop Cost Flags 10.0.0.0/8 192.168.1.2 The output shows that RIPv1 uses a natural mask. 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.
Page 47: Configuring Rip Route Redistribution
[SwitchB-rip-1] filter-policy prefix-list bbb export [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 ---------------------------------------------------------------------------- Peer 192.168.1.2 on Vlan-interface100 Destination/Mask Nexthop Cost...
Page 48 [SwitchA-rip-100] quit # Enable RIP 100 and RIP 200, and configure RIPv2 on Switch B. <SwitchB> 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.
Page 49: Configuring An Additional Metric For A Rip Interface
[SwitchC] display ip routing-table Destinations : 15 Routes : 15 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.2.1.0/24 12.3.1.1 Vlan200 11.1.1.0/24 12.3.1.1 Vlan200 12.3.1.0/24 Direct 0 12.3.1.2 Vlan200 12.3.1.0/32 Direct 0 12.3.1.2 Vlan200 12.3.1.2/32 Direct 0 127.0.0.1 InLoop0 12.3.1.255/32 Direct 0...
Page 50 [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. <SwitchB> 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. <SwitchC> 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.
Page 51: Configuring Rip To Advertise A Summary Route
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. Configuring RIP to advertise a summary route Network requirements As shown in Figure...
Page 52 [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 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. <SwitchD>...
Page 53: Configuring Bfd For Rip (Single-Hop Echo Detection)
[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 127.0.0.1 InLoop0 10.0.0.0/8 11.3.1.1 Vlan300 11.3.1.0/24 Direct 0 11.3.1.2 Vlan300 11.3.1.0/32...
Page 54 Figure 11 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic RIP: # Configure Switch A. <SwitchA> 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] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] rip bfd enable [SwitchA-Vlan-interface100] quit [SwitchA] rip 2...
Page 55 [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. [SwitchA] bfd session init-mode active [SwitchA] bfd echo-source-ip 11.11.11.11 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit [SwitchA] quit Configure a static route on Switch C.
Page 56: Configuring Rip Frr
<SwitchA> display ip routing-table 120.1.1.0 24 verbose Summary Count : 1 Destination: 120.1.1.0/24 Protocol: RIP Process ID: 2 SubProtID: 0x1 Age: 04h20m37s Cost: 1 Preference: 100 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NBRID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 192.168.2.2...
Page 57 [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. <SwitchD> system-view [SwitchD] bfd echo-source-ip 4.4.4.4 [SwitchD] ip prefix-list abc index 10 permit 1.1.1.1 32 [SwitchD] route-policy frr permit node 10 [SwitchD-route-policy-frr-10] if-match ip address prefix-list abc [SwitchD-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 101 backup-nexthop 24.24.24.2...
Page 58 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NBRID: 0x26000002 LastAs: 0 AttrID: 0xffffffff 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.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface101...
Page 59: Configuring Ospf
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 offers the following features: Wide scope—Supports various network sizes and up to several hundred routers in an OSPF routing •...
Page 60: Lsa Types
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, •...
Page 61 Figure 13 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 includes the following requirements: •...
Page 62: Router Types
Figure 15 Virtual link application 2 Area 1 Virtual link 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.
Page 63: Route Types
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.
Page 64: Route Calculation
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 •...
Page 65: Protocols And Standards
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.
Page 66: Ospf Configuration Task List
RFC 3137, OSPF Stub Router Advertisement • • RFC 481 1, 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.
Page 67: Enabling Ospf
Tasks at a glance (Optional.) Tuning and optimizing OSPF networks: • Configuring OSPF timers • Specifying LSA transmission delay • Specifying SPF calculation interval • Specifying the LSA arrival interval • Specifying the LSA generation interval • Disabling interfaces from receiving and sending OSPF packets •...
Page 68: Configuration Procedure
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.
Page 69: Configuring A Stub Area
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • • Enable OSPF. Configuring a stub area You can configure a non-backbone area at an AS edge as a stub area. To do so, issue the stub command on all routers attached to the area.
Page 70: Configuring A Virtual Link
Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enter OSPF view. router-id | vpn-instance vpn-instance-name ] * Enter area view. area area-id nssa [ default-route-advertise | no-import-route | no-summary | Configure the area as an By default, no area is configured as translate-always | NSSA area.
Page 71: Configuration Prerequisites
Broadcast—When the link layer protocol is Ethernet or FDDI, OSPF classifies the network type as • broadcast by default. NBMA—When the link layer protocol is Frame Relay, ATM, or X.25, OSPF classifies the network • type as NBMA by default. P2P—When the link layer protocol is PPP, LAPB, or HDLC, OSPF classifies the network type as P2P •...
Page 72: Configuring The P2Mp Network Type For An Interface
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the OSPF By default, the network type of an network type for the ospf network-type nbma interface depends on the link layer interface as NBMA. protocol. The default setting is 1.
Page 73: Configuring The P2P Network Type For An Interface
Step Command Remarks ospf [ process-id | router-id Enter OSPF view. router-id | vpn-instance vpn-instance-name ] * By default, no neighbor is specified. (Optional.) Specify a peer ip-address [ cost value | This step must be performed if the neighbor and its router dr-priority dr-priority ] network type is P2MP unicast, and is priority.
Page 74: Configuring Inbound Ospf Route Filtering
To configure route summarization on an ABR: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id Enter OSPF view. | vpn-instance vpn-instance-name ] * Enter OSPF area view. area area-id By default, no route summarization abr-summary ip-address { mask | is configured.
Page 75: Configuring Type-3 Lsa Filtering
Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * filter-policy { acl-number [ gateway Configure OSPF to ip-prefix-name ] | gateway ip-prefix-name | By default, OSPF accepts all filter routes calculated ip-prefix ip-prefix-name [ gateway routes calculated using using received LSAs.
Page 76: Configuring The Maximum Number Of Ecmp Routes
Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Configure a bandwidth The default setting is 100 bandwidth-reference value reference value. Mbps. Configuring the maximum number of ECMP routes Perform this task to implement load sharing over ECMP routes.
Page 77: Configuring Ospf Route Redistribution
Configuring OSPF route redistribution On a router running OSPF and other routing protocols, you can configure OSPF to redistribute routes from other protocols, such as RIP, IS-IS, BGP, static, and direct, and advertise them in Type-5 LSAs or Type-7 LSAs. In addition, you can configure OSPF to filter redistributed routes so that OSPF advertises only permitted routes.
Page 78: Advertising A Host Route
Configuring default parameters for redistributed routes Perform this task to configure default parameters for redistributed routes, including cost, tag, and type. Tags indicate information about protocols. For example, when redistributing BGP routes, OSPF uses tags to identify AS IDs. To configure the default parameters for redistributed routes: Step Command Remarks...
Page 79: Configuring Ospf Timers
Configuring OSPF timers An OSPF interface includes the following timers: • Hello timer—Interval for sending hello packets. It must be identical on OSPF neighbors. • Poll timer—Interval for sending hello packets to a neighbor that is down on the NBMA network. •...
Page 80: Specifying Spf Calculation Interval
To specify the LSA transmission delay on an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Specify the LSA transmission ospf trans-delay seconds The default setting is 1 second. delay. Specifying SPF calculation interval LSDB changes result in SPF calculations.
Page 81: Specifying The Lsa Generation Interval
Step Command Remarks The default setting is 1000 milliseconds. Configure the LSA arrival lsa-arrival-interval interval Make sure this interval is smaller than interval. or equal to the interval set with the lsa-generation-interval command. Specifying the LSA generation interval Adjust the LSA generation interval to protect network resources and routers from being overwhelmed by LSAs at the time of frequent network changes.
Page 82: Configuring Stub Routers
Step Command Remarks By default, an OSPF interface can receive and send OSPF packets. The silent-interface command disables only the interfaces Disable interfaces from silent-interface { interface-type associated with the current process receiving and sending interface-number | all } rather than other processes. OSPF packets.
Page 83: Adding The Interface Mtu Into Dd Packets
Step Command Remarks Enter area view. area area-id By default, no Configure area authentication authentication-mode { md5 | simple } authentication is mode. configured. Return to OSPF view. quit Return to system view. quit Enter interface view. interface interface-type interface-number •...
Page 84: Configuring Ospf Exit Overflow Interval
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.
Page 85: Configuring Ospf Network Management
Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enable the logging of By default, this feature is log-peer-change neighbor state changes. enabled. Configuring OSPF network management OSPF network management allows you to save system resources by enabling trap generation to report important events and configuring the maximum number of output traps for a specific time period.
Page 86: Enabling Ospf Ispf
Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * By default, an OSPF interface Configure the LSU transmit-pacing interval interval count count sends up to three LSU packets transmit rate. every 20 milliseconds. Enabling OSPF ISPF When the topology changes, Incremental Shortest Path First (ISPF) computes only the affected part of the SPT, instead of the entire SPT.
Page 87: Configuring Ospf Gr Helper
Step Command Remarks ospf [ process-id | router-id Enable OSPF and enter its router-id | vpn-instance view. vpn-instance-name ] * By default, opaque LSA reception Enable opaque LSA reception opaque-capability enable and advertisement capability is and advertisement capability. enabled. graceful-restart ietf [ global | By default, the IETF GR capability is Enable the IETF GR.
Page 88: Triggering Ospf Gr
Step Command Remarks (Optional.) Enable strict LSA graceful-restart helper By default, strict LSA checking for checking for the GR Helper. strict-lsa-checking the GR Helper is disabled. Configuring the non-IETF OSPF GR Helper Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enable OSPF and enter its router-id | vpn-instance view.
Page 89: Configuring Single-Hop Echo Detection
Step Command Remarks interface interface-type Enter interface view. interface-number By default, BFD bidirectional control detection is disabled. Enable BFD bidirectional control ospf bfd enable Both ends of a BFD session must be detection. on the same network segment and in the same area. Configuring single-hop echo detection Step Command...
Page 90: Configuration Prerequisites
Configuration prerequisites Before you configure OSPF FRR, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. Enable OSPF. • Configuration guidelines Do not use FRR and BFD at the same time. Otherwise, FRR might fail to take effect. •...
Page 91: Displaying And Maintaining Ospf
Step Command Remarks Configure the source address By default, the source address of bfd echo-source-ip ip-address of echo packets. echo packets is not configured. ospf [ process-id | router-id Enter OSPF view. router-id | vpn-instance vpn-instance-name ] * Enable OSPF FRR to specify a fast-reroute route-policy By default, OSPF FRR is not backup next hop by using a...
Page 92: Ospf Configuration Examples
Task Command Re-enable OSPF route reset ospf [ process-id ] redistribution redistribution. OSPF configuration examples These configuration examples only cover commands for OSPF configuration. Configuring basic OSPF Network requirements Enable OSPF on all switches, and split the AS into three areas. •...
Page 93 [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. <SwitchC> 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.255 [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit # Configure Switch D.
Page 94 DR: 10.2.1.1 BDR: 10.2.1.2 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 32 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...
Page 95: Configuring Ospf Route Redistribution
--- 10.4.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms Configuring OSPF route redistribution Network requirements Enable OSPF on all the switches. • Split the AS into three areas. • Configure Switch A and Switch B as ABRs. •...
Page 96: Configuring Ospf To Advertise A Summary Route
Inter 10.4.1.1 0.0.0.2 10.3.1.1 ASBR # Display the OSPF routing table on Switch D. <SwitchD> 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 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.3.1.0/24 Transit 10.3.1.2...
Page 97 Figure 22 Network diagram Vlan-int600 Vlan-int500 10.4.1.1/24 10.3.1.1/24 Vlan-int400 Vlan-int300 10.1.1.1/24 10.2.1.2/24 Switch E Switch D Vlan-int300 Vlan-int400 10.2.1.1/24 10.1.1.2/24 Switch C AS 100 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 Configure IP addresses for interfaces.
Page 98 # Configure Switch D. <SwitchD> 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. <SwitchE> 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.0.0.0] quit...
Page 99: Configuring An Ospf Stub Area
0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.1.1.0/24 OSPF 11.2.1.1 Vlan100 10.2.1.0/24 OSPF 11.2.1.1 Vlan100 10.3.1.0/24 OSPF 11.2.1.1 Vlan100 10.4.1.0/24 OSPF 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 11.2.1.2 Vlan100 11.2.1.0/32 Direct 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 127.0.0.1 InLoop0 11.2.1.255/32 Direct 0 11.2.1.2 Vlan100 127.0.0.0/8 Direct 0...
Page 100 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 23 Network diagram Switch A Area 0 Switch B Vlan-int100 10.1.1.1/24 Vlan-int100 10.1.1.2/24 Vlan-int200 Vlan-int200 10.2.1.1/24...
Page 101 10.1.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 Routing for ASEs Destination Cost Type NextHop AdvRouter 3.1.2.0/24 Type2 10.2.1.1 10.5.1.1 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. Configure Area 1 as a stub area: # Configure Switch A.
Page 102: Configuring An Ospf Nssa Area
[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 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 Transit 10.2.1.2 10.4.1.1 0.0.0.1 10.4.1.0/24...
Page 103 [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. <SwitchC> 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.1] quit [SwitchC-ospf-1] quit NOTE: To allow Switch C in the NSSA area to reach other areas within the AS, you must provide the •...
Page 104: Configuring Ospf Dr Election
10.3.1.0/24 Transit 10.3.1.2 10.3.1.1 0.0.0.2 10.4.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.5.1.0/24 Stub 10.5.1.1 10.5.1.1 0.0.0.2 10.1.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 Routing for ASEs Destination Cost Type NextHop AdvRouter 3.1.3.0/24 Type2 10.3.1.1 10.2.1.1 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.
Page 105 [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. <SwitchC> 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. <SwitchD> system-view [SwitchD] router id 4.4.4.4 [SwitchD] ospf [SwitchD-ospf-1] area 0...
Page 106 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. 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.
Page 107 The output shows that the DR and BDR are not changed, because the priority settings do not take effect immediately. Restart OSPF process: # Restart the OSPF process of Switch D. <SwitchD> reset ospf 1 process Warning : Reset OSPF process? [Y/N]:y # Display neighbor information of Switch D.
Page 108: Configuring Ospf Virtual Links
192.168.1.1 Broadcast DR 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 State Cost 192.168.1.2 Broadcast DROther 192.168.1.1 192.168.1.3 The interface state DROther means the interface is not the DR or BDR. Configuring OSPF virtual links Network requirements Configure a virtual link between Switch B and Switch C to connect Area 2 to the backbone area.
Page 109 [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> 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. <SwitchD> 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.0.255 [SwitchD-ospf-1-area-0.0.0.2] quit...
Page 110: Configuring Ospf Gr
Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Transit 10.2.1.1 3.3.3.3 0.0.0.1 10.3.1.0/24 Inter 10.2.1.2 3.3.3.3 0.0.0.0 10.1.1.0/24 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. Configuring OSPF GR Network requirements As shown in...
Page 111 [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 <SwitchC> 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 Configure OSPF GR: # Configure Switch A as the non-IETF OSPF GR Restarter: enable the link-local signaling capability, the out-of-band re-synchronization capability, and non-IETF GR capability for OSPF process 100.
Page 112: Configuring Bfd For Ospf
%Oct 21 15:29:29:902 2011 SwitchA OSPF/5/OSPF_NBR_CHG: OSPF 100 Neighbor 192.1.1.2(Vlan-interface100) from Loading to Full. *Oct 21 15:29:29:902 2011 SwitchA OSPF/7/DEBUG: 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: OSPF 100 Neighbor 192.1.1.3(Vlan-interface100) from Loading to Full. *Oct 21 15:29:30:897 2011 SwitchA OSPF/7/DEBUG: OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.3.
Page 113 Vlan-int13 13.1.1.2/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Switch A. <SwitchA> 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.0] quit [SwitchA-ospf-1] quit [SwitchA] interface vlan 11 [SwitchA-Vlan-interface11] ospf cost 2 [SwitchA-Vlan-interface11] quit...
Page 114 [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.
Page 115: Configuring Ospf Frr
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 Interface: Vlan-interface11 BkTunnel ID: Invalid...
Page 116 <SwitchD> system-view [SwitchD] bfd echo-source-ip 4.4.4.4 [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. <SwitchS> system-view [SwitchS] bfd echo-source-ip 1.1.1.1 [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...
Page 117: Troubleshooting Ospf Configuration
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.1/32 Protocol: OSPF Process ID: 1 SubProtID: 0x1...
Page 118: Incorrect Routing Information
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.
Page 119: Configuring Is-Is
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 1 195 by the IETF for application in both TCP/IP and OSI reference models, called "Integrated IS-IS"...
Page 120: Net
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 30 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.
Page 121: Is-Is Area
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. •...
Page 122 Figure 31 IS-IS topology 1 Area 3 Area 2 L1/L2 L1/L2 Area 1 Area 5 L1/L2 L1/L2 Area 4 Figure 32 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.
Page 123: Is-Is Network Types
passing through the Level- 1 -2 router may 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.
Page 124: Is-Is Pdus
NOTE: On an IS-IS broadcast network, all routers establish adjacency relationships, but they synchronize their LSDBs through the DIS. IS-IS PDUs 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.
Page 125: Protocols And Standards
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.
Page 126: Is-Is Configuration Task List
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 •...
Page 127: Configuring Basic Is-Is
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: •...
Page 128: Configuring P2P Network Type For An Interface
To configure the IS level and circuit level: Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] is-level { level-1 | level-1-2 | Specify the IS level. By default, the IS level is Level-1-2. level-2 } Return to system view.
Page 129: Configuring Is-Is Link Cost
Configuring IS-IS link cost The IS-IS cost of an interface is determined in the following order: IS-IS cost specified in interface view. IS-IS cost specified in system view. The cost is applied to the interfaces associated with the IS-IS process. Automatically calculated cost.
Page 130: Specifying A Preference For Is-Is
Step Command Remarks Specify a global By default, no global cost is circuit-cost value [ level-1 | level-2 ] IS-IS cost. specified. Enabling automatic IS-IS cost calculation Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view.
Page 131: Configuring Is-Is Route Summarization
Step Command Remarks By default, the maximum number of ECMP routes is the same as that configured in the Specify the maximum number max-ecmp-num maximum load-balancing number of ECMP routes. command. For more information about the max-ecmp-num command, see IP Routing Command Reference.
Page 132: Configuring Is-Is Route Redistribution
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...
Page 133: Configuring Is-Is Route Leaking
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.
Page 134: Specifying Intervals For Sending Is-Is Hello And Csnp Packets
Specifying intervals for sending IS-IS hello and CSNP packets Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number The default setting is 10 seconds. The interval between hello packets Specify the interval for isis timer hello seconds [ level-1 | sent by the DIS is 1/3 the hello sending hello packets.
Page 135: Disabling An Interface From Sending/Receiving Is-Is Packets
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure a DIS priority for isis dis-priority value [ level-1 | The default setting is 64. the interface. level-2 ] Disabling an interface from sending/receiving IS-IS packets After being disabled from sending and receiving hello packets, an interface cannot form any neighbor relationship, but can advertise directly connected networks in LSPs through other interfaces.
Page 136 Each LSP has an age that decreases in the LSDB. IS-IS runs a process to delete any LSP with an age of 0 from the LSDB. You can adjust the age value based on the scale of a network. To specify the maximum age of LSPs: Step Command Remarks...
Page 137 Step Command Remarks interface interface-type Enter interface view. interface-number Specify the minimum By default, the minimum interval is interval for sending LSPs isis timer lsp time [ count 33 milliseconds, and the maximum and the maximum LSP count ] LSP number that can be sent at a number that can be sent at a time is 5.
Page 138: Controlling Spf Calculation Interval
Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] Enable LSP fragment lsp-fragments-extend [ level-1 | By default, this feature is disabled. extension. level-1-2 | level-2 ] By default, no virtual system ID is configured.
Page 139: Setting The Lsdb Overload Bit
Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] priority { critical | high | medium } Assign convergence priorities By default, IS-IS routes have the { prefix-list prefix-list-name | tag to specific IS-IS routes.
Page 140: Enabling The Logging Of Neighbor State Changes
Step Command Remarks Configure a system ID to host A system ID can correspond to only name mapping for a remote is-name map sys-id map-sys-name one host name. Configuring dynamic system ID to host name mapping Static system ID to host name mapping requires you to manually configure a mapping for each router in the network.
Page 141: Enabling Is-Is Ispf
Step Command Remarks Enable the logging of By default, the logging of log-peer-change neighbor state changes. neighbor state is enabled. Enabling IS-IS ISPF When the network topology changes, Incremental Shortest Path First (ISPF) computes only the affected part of the SPT, instead of the entire SPT. To enable IS-IS ISPF: Step Command...
Page 142: Configuring Area Authentication
Step Command Remarks isis authentication-mode { md5 | simple | gca key-id { hmac-sha-1 | hmac-sha-224 Specify the authentication | hmac-sha-256 | hmac-sha-384 | By default, no authentication mode and password. hmac-sha-512 } } { cipher cipher-string | is configured. plain plain-string } [ level-1 | level-2 ] [ ip | osi ] Configuring area authentication...
Page 143: Configuring Is-Is Gr
Step Command Remarks domain-authentication-mode { md5 | simple | gca key-id Specify the routing domain { hmac-sha-1 | hmac-sha-224 | By default, no routing domain authentication mode and hmac-sha-256 | hmac-sha-384 | authentication is configured. password. hmac-sha-512 } } { cipher cipher-string | plain plain-string } [ ip | osi ] Configuring IS-IS GR...
Page 144: Configuring Bfd For Is-Is
Step Command Remarks (Optional.) Configure graceful-restart t1 seconds count By default, the T1 timer is 3 seconds and can the T1 timer. count expire 10 times. (Optional.) Configure graceful-restart t2 seconds By default, the T2 timer is 60 seconds. the T2 timer. (Optional.) Configure graceful-restart t3 seconds By default, the T2 timer is 300 seconds.
Page 145: Configuration Prerequisites
Configuration prerequisites Before you configure IS-IS FRR, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. Enable IS-IS. • Configuration guidelines Do not use FRR and BFD at the same time. Otherwise, FRR may fail to take effect. Configuring IS-IS FRR to automatically calculate a backup next Step Command...
Page 146: Displaying And Maintaining Is-Is
Displaying and maintaining IS-IS Execute display commands in any view and the reset command in user view. Task Command Display brief IS-IS configuration display isis brief [ process-id ] information. Display the IS-IS GR status. display isis graceful-restart status [ level-1 | level-2 ] [ process-id ] Display information about IS-IS enabled display isis interface [ [ interface-type interface-number ] [ verbose ] interfaces.
Page 147 Figure 37 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure IS-IS: # Configure Switch A. <SwitchA> 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.
Page 148 [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 100 [SwitchD-Vlan-interface100] isis enable 1 [SwitchD-Vlan-interface100] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Verifying the configuration...
Page 149 0000.0000.0003.00-00 0x00000014 0x194a 1190 1/0/0 0000.0000.0003.01-00 0x00000002 0xabdb 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [SwitchC] 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 0x00000006 0xdb60 0/0/0 0000.0000.0002.00-00...
Page 150 [SwitchA] 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 NULL Vlan100 Direct D/L/- 10.1.2.0/24 NULL Vlan100 10.1.1.1 R/-/- 192.168.0.0/24 NULL Vlan100 10.1.1.1 R/-/- 0.0.0.0/0 NULL Vlan100 10.1.1.1 R/-/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set...
Page 151: Dis Election Configuration Example
Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 192.168.0.0/24 NULL Vlan300 Direct D/L/- 10.1.1.0/24 NULL Vlan300 192.168.0.1 R/-/- 10.1.2.0/24 NULL Vlan300 192.168.0.1 R/-/- 172.16.0.0/16 NULL Vlan100 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set The output shows that the routing table of Level- 1 switches contains a default route with the next hop as the Level- 1 -2 switch.
Page 152 [SwitchA-Vlan-interface100] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] isis enable 1 [SwitchB-Vlan-interface100] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] is-level level-1 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1...
Page 153 # Display information about IS-IS interfaces on Switch A. [SwitchA] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 No/No # Display information about IS-IS interfaces on Switch C. [SwitchC] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100...
Page 154 System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 28s Type: L2(L1L2) PRI: 64 System Id: 0000.0000.0004 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 30s Type: L2 PRI: 64 # Display information about IS-IS interfaces on Switch A. [SwitchA] display isis interface Interface information for IS-IS(1) ----------------------------------...
Page 155: Is-Is Route Redistribution Configuration Example
System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 28s Type: L2 PRI: 64 [SwitchD] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 No/No IS-IS route redistribution configuration example Network requirements As shown in Figure 39, Switch A, Switch B, Switch C, and Switch D reside in the same AS.
Page 156 # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [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...
Page 157 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set [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 NULL VLAN100 Direct D/L/- 10.1.2.0/24 NULL VLAN200 Direct D/L/-...
Page 158: Is-Is Authentication Configuration Example
[SwitchD-rip-1] undo summary # Configure RIPv2 on Switch E. [SwitchE] rip 1 [SwitchE-rip-1] network 10.0.0.0 [SwitchE-rip-1] version 2 [SwitchE-rip-1] undo summary # Configure IS-IS to redistribute RIP routes on Switch D. [SwitchD-rip-1] quit [SwitchD] isis 1 [SwitchD–isis-1] import-route rip level-2 # Display IS-IS routing information on Switch C.
Page 159 Configure neighbor relationship authentication between neighbors. Configure area authentication in Area 10 to prevent untrusted routes from entering into the area. Configure routing domain authentication on Switch C and Switch D to prevent untrusted routes from entering the routing domain. Figure 40 Network diagram Configuration procedure Configure IP addresses for interfaces.
Page 160 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D. <SwitchD> 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 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.
Page 161: Is-Is Gr Configuration Example
[SwitchC-isis-1] quit Configure routing domain authentication mode as MD5 and set the plaintext password to 1020Sec on Switch C and Switch D. [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...
Page 162: Bfd For Is-Is Configuration Example
<SwitchA> display isis graceful-restart status Restart information for IS-IS(1) -------------------------------- Restart status: COMPLETE 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...
Page 163 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis [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.
Page 164 [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] isis bfd enable [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 8 [SwitchB-Vlan-interface10] return Verifying the configuration # Display the BFD session information on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode:...
Page 165: Is-Is Frr Configuration Example
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 Interface: Vlan-interface11 BkTunnel ID: Invalid BkInterface: N/A The output shows that Switch A and Switch B communicate through VLAN-interface 1 1. IS-IS FRR configuration example Network requirements As shown in...
Page 166 [SwitchD-isis-1] quit (Method 2.) Enable IS-IS FRR to designate a backup next hop by using a referenced routing policy: # Configure Switch S. <SwitchS> system-view [SwitchS] bfd echo-source-ip 1.1.1.1 [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...
Page 167 # 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.1/32 Protocol: ISIS Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 10 Preference: 10 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf...
Page 169: Configuring Bgp
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.
Page 170: Bgp Path Attributes
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.
Page 171 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 may 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.
Page 172 Figure 46 MED attribute MED = 0 Router B 2.1.1.1 D = 9.0.0.0 Next_hop = 2.1.1.1 EBGP IBGP MED = 0 9.0.0.0 IBGP Router A Router D D = 9.0.0.0 EBGP IBGP Next_hop = 3.1.1.1 MED = 100 AS 10 3.1.1.1 Router C AS 20...
Page 173 Figure 47 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).
Page 174: Bgp Route Selection
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: The route with the highest Preferred_value The route with the highest LOCAL_PREF The route generated by the network command, the route redistributed by the import-route command, or the summary route in turn.
Page 175: Settlements For Problems In Large-Scale Bgp Networks
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.
Page 176 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.
Page 177 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.
Page 178: Mp-Bgp
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 intra-confederation EBGP connections are established between sub-ASs in AS 200. Figure 52 Confederation network diagram A non-confederation BGP speaker does not need to know sub-ASs in the confederation.
Page 179: Bgp Configuration Views
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.
Page 180: Protocols And Standards
View names Ways to enter the views Remarks <Sysname> system-view [Sysname] bgp 100 Configurations in this view are BGP-VPN IPv4 unicast [Sysname-bgp] ip vpn-instance effective for IPv4 unicast routes in the vpn1 instance view specified VPN instance. [Sysname-bgp-vpn1] ipv4-family unicast [Sysname-bgp-ipv4-vpn1] <Sysname>...
Page 181 Tasks at a glance Remarks Configuring basic BGP: HP recommends • (Required.) Enabling BGP configuring BGP peer • (Required.) Perform one of the following tasks: groups on large scale BGP networks for easy Configuring a BGP peer configuration and Configuring a BGP peer group maintenance.
Page 182 To configure BGP, perform the following tasks (IPv6): Tasks at a glance Remarks Configuring basic BGP: HP recommends • (Required.) Enabling BGP configuring BGP peer • (Required.) Perform one of the following tasks: groups on large scale BGP networks for easy Configuring a BGP peer configuration and Configuring a BGP peer group...
Page 183: Configuring Basic Bgp
Tasks at a glance Remarks (Optional.) Enabling logging of session state changes (Optional.) Configuring BFD for BGP Configuring basic BGP This section describes the basic settings required for a BGP network to run. Enabling BGP A router ID is the unique identifier of a BGP router in an AS. To ensure the uniqueness of a router ID and enhance availability, specify in BGP view the IP address •...
Page 184: Configuring A Bgp Peer
Configuring a BGP peer Configuring an IPv4 BGP peer Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Create an IPv4 BGP peer and peer ip-address as-number By default, no IPv4 BGP peer is specify its AS number.
Page 185: Configuring A Bgp Peer Group
Configuring a BGP peer group The peers in a peer group use the same route selection policy. In a large-scale network, many peers can use the same route selection policy. You can configure a peer group and add these peers into this group. When you change the policy for the group, the modification also applies to the peers in the group.
Page 186 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. bgp as-number ip vpn-instance vpn-instance-name By default, no IBGP peer group is Create an IBGP peer group. group group-name [ internal ] created.
Page 187 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name By default, no EBGP peer group is Create an EBGP peer group. group group-name external created.
Page 188 Step Command Remarks By default, no peer exists in the peer group. peer ipv6-address group Add a peer into the EBGP The as-number as-number option, group-name [ as-number peer group. if used, must specify the same AS as-number ] number as the peer group-name as-number as-number command.
Page 189 To configure an EBGP peer group by using Method 2 (IPv6): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name By default, no EBGP peer group is Create an EBGP peer group.
Page 190: Specifying The Source Interface For Tcp Connections
Step Command Remarks Create and enter BGP IPv4 By default, the BGP IPv4 unicast unicast instance view or instance view and BGP-VPN IPv4 ipv4-family [ unicast ] BGP-VPN IPv4 unicast unicast instance view are not instance view. created. Enable the router to exchange By default, the router cannot IPv4 unicast routing peer group-name enable...
Page 191: Generating Bgp Routes
On a BGP router that has multiple links to a peer, if the source interface fails, BGP has to reestablish • TCP connections. To avoid this problem, use a loopback interface as the source interface. To establish multiple BGP sessions between two routers, specify the source interface for establishing •...
Page 192: Injecting A Local Network
Injecting a local network Perform this task to inject a network in the local routing table to the BGP routing table, so BGP can advertise the network to BGP peers. The ORIGIN attribute of BGP routes advertised in this way is IGP. You can also use a routing policy to control route advertisement.
Page 193: Controlling Route Distribution And Reception
Only active routes can be redistributed. To view route state information, use the display ip routing-table protocol or display ipv6 routing-table protocol command. The ORIGIN attribute of BGP routes redistributed from IGPs is INCOMPLETE. To configure BGP to redistribute IGP routes (IPv4): Step Command Remarks...
Page 194: Configuring Bgp Route Summarization
Configuring BGP route summarization Route summarization can reduce the number of redistributed routes and the routing table size. IPv4 BGP supports automatic route summarization and manual route summarization. Manual summarization takes precedence over automatic summarization. IPv6 BGP supports only manual route summarization. The output interface of a BGP summary route is Null 0 on the originating router.
Page 195: Advertising Optimal Routes In The Ip Routing Table
Step Command Remarks aggregate ip-address { mask | mask-length } [ as-set | attribute-policy route-policy-name Create a summary route in the By default, no summary route is | detail-suppressed | origin-policy BGP routing table. configured. route-policy-name | suppress-policy route-policy-name ] * To configure BGP manual route summarization (IPv6): Step Command...
Page 196: Limiting Routes Received From A Peer Or Peer Group
Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view.
Page 197: Configuring Bgp Route Filtering Policies
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view. peer { group-name | ip-address } Specify the maximum number route-limit prefix-number...
Page 198 filter-policy export peer filter-policy export peer as-path-acl export peer prefix-list export peer route-policy export Only routes passing all the configured policies can be advertised. To configure BGP route distribution filtering policies (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number •...
Page 199 Step Command Remarks • Reference an ACL or IP prefix list to filter routes redistributed to all peers: filter-policy { acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] •...
Page 200 Step Command Remarks • Reference an ACL or IPv6 prefix list to filter routes redistributed to all peers: filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ direct | isisv6 process-id | ospfv3 process-id | ripng process-id | static ] •...
Page 201 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view.
Page 202: Configuring Bgp Route Dampening
Step Command Remarks Enter BGP IPv6 unicast instance view or BGP-VPN ipv6-family [ unicast ] IPv6 unicast instance view. • Reference ACL or IPv6 prefix list to filter routes from all peers: filter-policy { acl6-number | prefix-list ipv6-prefix-name } import •...
Page 203: Controlling Bgp Path Selection
Step Command Remarks dampening [ half-life-reachable Configure BGP route half-life-unreachable reuse suppress By default, BGP route dampening dampening. ceiling | route-policy is not configured. route-policy-name ] * To configure BGP route dampening (IPv6): Step Command Remarks Enter system view. system-view •...
Page 204: Configuring Preferences For Bgp Routes
Step Command Remarks Specify a preferred value for peer { group-name | ip-address } routes received from a peer or The default preferred value is 0. preferred-value value peer group. To specify a preferred value for routes from a peer or peer group (IPv6): Step Command Remarks...
Page 205: Configuring The Default Local Preference
Step Command Remarks Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view. preference { external-preference Configure preferences for The default preferences for EBGP, internal-preference EBGP, IBGP, and local BGP IBGP, and local BGP routes are local-preference | route-policy routes.
Page 206: Configuring The Med Attribute
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view. Configure the default local The default local preference is default local-preference value...
Page 207 Step Command Remarks Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view. Configure the default MED default med med-value The default MED value is 0. value. To configure the default MED value (IPv6): Step Command Remarks...
Page 208 Step Command Remarks Enter BGP IPv6 unicast ipv6-family [ unicast ] instance view. Enable MED comparison for compare-different-as-med By default, this feature is disabled. routes from different ASs. Enabling MED comparison for routes on a per-AS basis This task enables BGP to compare the MEDs of routes from an AS. Figure 53 Route selection based on MED (in an IPv4 network) AS 400 Router E...
Page 209 Network NextHop LocPrf PrefVal Path/Ogn *>i 10.0.0.0 2.2.2.2 300e 3.3.3.3 200e 1.1.1.1 200e To enable MED comparison for routes on a per-AS basis (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view.
Page 210: Configuring The Next_Hop Attribute
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view. Enable MED comparison for routes from confederation bestroute med-confederation...
Page 211 next hop by default. However, you can configure Router B to set it (1.1.1.2/24) as the next hop for routes sent to Router A by using the peer next-hop-local command as needed. Figure 55 NEXT_HOP attribute configuration IMPORTANT: If you have configured BGP load balancing, the router sets itself as the next hop for routes sent to an IBGP peer or peer group regardless of whether the peer next-hop-local command is configured.
Page 212: Configuring The As_Path Attribute
Step Command Remarks By default, the router sets itself as the next hop for routes sent to an Specify the router as the next peer { group-name | EBGP peer or peer group, but does hop for routes sent to a peer ipv6-address } next-hop-local not set itself as the next hop for or peer group.
Page 213 Step Command Remarks Enter BGP IPv6 unicast instance view or BGP-VPN ipv6-family [ unicast ] IPv6 unicast instance view. Permit the local AS number to peer { group-name | By default, the local AS number is appear in routes from a peer ipv6-address } allow-as-loop not allowed in routes from a peer or peer group and specify the...
Page 214 the router to advertise a fake AS number 2 to its EBGP peers so that the EBGP peers still think that Router A is in AS 2. To advertise a fake AS number to a peer or peer group (IPv4): Step Command Remarks...
Page 215 Figure 56 AS number substitution configuration (in an IPv4 network) For example, as shown in Figure 56, CE 1 and CE 2 use the same AS number 800. To implement bidirectional communication between the two sites, configure AS number substitution on PE 2 to replace AS 800 as AS 100 for the BGP route update originated from CE 1 before advertising it to CE 2, and perform the same configuration on PE 1.
Page 216 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view.
Page 217: Tuning And Optimizing Bgp Networks
Tuning and optimizing BGP networks This section describes how to tune and optimize BGP networks. Configuring the keepalive interval and hold time BGP sends keepalive messages at a specific interval to keep the BGP session between two routers. If a router receives no keepalive or update message from a peer within the hold time, it tears down the session.
Page 218: Configuring The Interval For Sending Updates For The Same Route
Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Use either method. By default, the keepalive interval is • Configure the global keepalive 60 seconds, and hold time is 180 interval and hold time:...
Page 219: Enabling Bgp To Establish An Ebgp Session Over Multiple Hops
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Configure the interval for peer { group-name | By default, the interval is 15 sending updates for the same ipv6-address } seconds for an IBGP peer and 30...
Page 220: Enabling Immediate Reestablishment Of Direct Ebgp Connections Upon Link Failure
Step Command Remarks Enable BGP to establish an By default, BGP cannot establish EBGP session to an peer { group-name | an EBGP session to an indirectly-connected peer or ipv6-address } ebgp-max-hop indirectly-connected peer or peer peer group and specify the [ hop-count ] group.
Page 221: Configuring Md5 Authentication For Bgp
Step Command Remarks peer { group-name | ip-address } Enable 4-byte AS number By default, 4-byte AS number capability-advertise suppression. suppression is not enabled. suppress-4-byte-as To enable 4-byte AS number suppression (IPv6): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number •...
Page 222: Configuring Bgp Load Balancing
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. bgp as-number ip vpn-instance vpn-instance-name Configure MD5 peer { group-name | By default, MD5 authentication is authentication for a peer or ipv6-address } password { cipher | not configured for any BGP peer.
Page 223: Disabling Bgp To Establish A Session To A Peer Or Peer Group
Step Command Remarks Configure the maximum By default, load balancing is number of ECMP routes for balance number disabled. load balancing. Disabling BGP to establish a session to a peer or peer group This task enables you to temporarily tear down the BGP session to a specific peer or peer group so that you can perform network upgrade and maintenance without needing to delete and reconfigure the peer or peer group.
Page 224 Enabling route-refresh—The BGP router advertises a route-refresh message to the specified peer, • and the peer resends its routing information to the router. After receiving the routing information, the router filters the routing information by using the new policy. This method requires that both the local router and the peer support route refresh. Saving updates—Use the peer keep-all-routes command to save all route updates from the •...
Page 225 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address } capability-advertise route-refresh...
Page 226 Step Command Remarks Enter BGP IPv6 unicast ipv6-family [ unicast ] instance view. By default, the routes are not saved. Save all route updates from peer { group-name | This command takes effect only for the peer or peer group. ipv6-address } keep-all-routes the routes received after this command is executed.
Page 227: Protecting An Ebgp Peer When Memory Usage Reaches Level 2 Threshold
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address } capability-advertise route-refresh...
Page 228: Configuring A Large-Scale Bgp Network
Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Configure BGP to protect By default, BGP tears down an EBGP peer or peer group peer { group-name | ip-address } EBGP session to release memory when the memory usage...
Page 229 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP view or BGP-VPN Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast instance view or BGP-VPN ipv4-family [ unicast ] IPv4 unicast instance view.
Page 230: Configuring A Bgp Route Reflector
Configuring a BGP route reflector If an AS has many BGP routers, configure them as a cluster. To reduce IBGP connections, configure one of them as a route reflector and others as clients. To improve availability, you can specify multiple route reflectors for a cluster. The route reflectors in the cluster must have the same cluster ID to avoid routing loops.
Page 231: Configuring Bgp Gr
A confederation contains sub-ASs. In each sub-AS, IBGP peers are fully meshed. Sub-ASs establish EBGP connections in between. Configuring a BGP confederation After you split an AS into multiple sub-ASs, configure a router in a sub-AS as follows: Enable BGP and specify the AS number of the router. For more information, see "Enabling BGP."...
Page 232: Enabling Trap
The BGP GR Restarter and Helper exchange Open messages for GR capability negotiation. If both parties have the GR capability, they establish a GR-capable session. The GR Restarter sends the GR timer set by the graceful-restart timer restart command to the GR Helper in an Open message. When an active/standby switchover occurs or BGP restarts, the GR Restarter does not remove existing BGP routes, and it still uses these routes for packet forwarding.
Page 233: Enabling Logging Of Session State Changes
Step Command Remarks Enter system view. system-view By default, trap for BGP is enabled. For more information about this Enable trap for BGP. snmp-agent trap enable bgp command, see Network Management and Monitoring Configuration Guide. Enabling logging of session state changes Perform this task to enable BGP to log BGP session establishment and disconnection events.
Page 234: Displaying And Maintaining Bgp
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN • Enter BGP-VPN instance view: instance view. bgp as-number ip vpn-instance vpn-instance-name Enable BFD to detect the link to the By default, BFD is peer ip-address bfd specified BGP peer.
Page 235 Task Command Display BGP IPv4 unicast routing display bgp routing-table ipv4 [ unicast ] [ vpn-instance information matching the specified AS vpn-instance-name ] as-path-acl as-path-acl-number path list. display bgp routing-table ipv4 [ unicast ] [ vpn-instance Display BGP IPv4 unicast routing vpn-instance-name ] community-list information matching the specified BGP { { basic-community-list-number | comm-list-name }...
Page 236 Task Command display bgp routing-table ipv6 [ unicast ] peer ipv6-address { advertised-routes | received-routes } [ network-address Display BGP IPv6 unicast routing prefix-length | statistics ] information sent to/received from the display bgp routing-table ipv6 [ unicast ] vpn-instance specified BGP peer.
Page 237: Ipv4 Bgp Configuration Examples
IPv4 BGP configuration examples Basic BGP configuration example Network requirements Figure 57, run EBGP between Switch A and Switch B, and run IBGP between Switch B and Switch C so that Switch C can access the network 8.1.1.0/24 connected to Switch A. Figure 57 Network diagram Configuration considerations To prevent route flapping caused by port state changes, this example uses loopback interfaces to...
Page 238 [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 2.2.2.2 as-number 65009 [SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0 [SwitchC-bgp] ipv4-family unicast [SwitchC-bgp-ipv4] peer 2.2.2.2 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit [SwitchC] ospf 1 [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit...
Page 239 BGP local router ID : 2.2.2.2 Local AS number : 65009 Total number of peers : 2 Peers in established state : 2 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 3.3.3.3 65009 0 00:02:49 Established 3.1.1.2 65008 0 00:00:05 Established The output shows that Switch B has established an IBGP peer relationship with Switch C and an EBGP peer relationship with Switch A.
Page 240 Network NextHop LocPrf PrefVal Path/Ogn i 8.1.1.0/24 3.1.1.2 65008i The outputs show that Switch A has learned no route to AS 65009, and Switch C has learned network 8.1.1.0, but the next hop 3.1.1.2 is unreachable. As a result, the route is invalid. Redistribute direct routes: Configure BGP to redistribute direct routes on Switch B, so that Switch A can obtain the route to 9.1.1.0/24, and Switch C can obtain the route to 3.1.1.0/24.
Page 241: Bgp And Igp Route Redistribution Configuration Example
The output shows that the route 8.1.1.0 becomes valid with the next hop as Switch A. Verifying the configuration # Ping 8.1.1.1 on Switch C. [SwitchC] ping 8.1.1.1 PING 8.1.1.1 (8.1.1.1): 56 data bytes 56 bytes from 8.1.1.1: icmp_seq=0 ttl=254 time=10.000 ms 56 bytes from 8.1.1.1: icmp_seq=1 ttl=254 time=4.000 ms 56 bytes from 8.1.1.1: icmp_seq=2 ttl=254 time=4.000 ms 56 bytes from 8.1.1.1: icmp_seq=3 ttl=254 time=3.000 ms...
Page 242 [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ospf 1 [SwitchC-ospf-1] import-route direct [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure the EBGP connection: Configure the EBGP connection and inject network 8.1.1.0/24 to the BGP routing table of Switch A, so that Switch B can obtain the route to 8.1.1.0/24.
Page 243 >e 3.3.3.3/32 3.1.1.1 65009? > 8.1.1.0/24 8.1.1.1 >e 9.1.2.0/24 3.1.1.1 65009? # Display the OSPF routing table on Switch C. [SwitchC] display ospf routing OSPF Process 1 with Router ID 3.3.3.3 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 9.1.1.0/24...
Page 244: Bgp Route Summarization Configuration Example
BGP route summarization configuration example Network requirements As shown in Figure 59, run EBGP between Switch C and Switch D, so the internal network and external network can communicate with each other. In AS 65106, configure static routing between Switch A and Switch B, configure OSPF between Switch B and Switch C, and configure OSPF to redistribute static routes, so the devices in the internal network can communicate with each other.
Page 245 [SwitchB-ospf-1] import-route static [SwitchB-ospf-1] quit # Configure OSPF to advertise the local networks on Switch C. [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 172.17.100.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 10.220.2.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Display the IP routing table on Switch C. [SwitchC] display ip routing-table protocol ospf Summary Count : 5 OSPF Routing table Status : <Active>...
Page 246 [SwitchD-bgp] quit # Display the IP routing table on Switch D. [SwitchD] display ip routing-table protocol bgp Summary Count : 3 BGP Routing table Status : <Active> Summary Count : 3 Destination/Mask Proto Cost NextHop Interface 192.168.64.0/24 10.220.2.16 Vlan200 192.168.74.0/24 10.220.2.16 Vlan200 192.168.99.0/24...
Page 247: Bgp Load Balancing Configuration Example
Summary Count : 0 The output shows that Switch D has only one route 192.168.64.0/18 to AS 65106. After the above configurations, ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24 and 192.168.99.0/24 from Switch D. The ping operations succeed. BGP load balancing configuration example Network requirements As shown in Figure...
Page 248 <SwitchA> 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] peer 3.1.2.1 as-number 65009 [SwitchA-bgp] ipv4-family unicast [SwitchA-bgp-ipv4] peer 3.1.1.1 enable [SwitchA-bgp-ipv4] peer 3.1.2.1 enable [SwitchA-bgp-ipv4] network 8.1.1.1 24 [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch B. <SwitchB>...
Page 249 Network NextHop LocPrf PrefVal Path/Ogn > 8.1.1.0/24 8.1.1.1 >e 9.1.1.0/24 3.1.1.1 65009i 3.1.2.1 65009i The output shows two valid routes to destination 9.1.1.0/24. The route with next hop 3.1.1.1 is marked with a greater-than sign (>), indicating it is the best route (because the ID of Switch B is smaller).
Page 250: Bgp Community Configuration Example
BGP community configuration example Network requirements As shown in Figure 61, Switch B establishes EBGP connections with Switch A and C. Configure NO_EXPORT community attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any other AS.
Page 251 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 200.1.3.1 as-number 20 [SwitchC-bgp] ipv4-family unicast [SwitchC-bgp-ipv4] peer 200.1.3.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Display the BGP 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:...
Page 252 >e 9.1.1.0/24 200.1.3.1 20 10i The output shows that Switch C has learned route 9.1.1.0/24 from Switch B. Configure BGP community: # Configure a routing policy. [SwitchA] route-policy comm_policy permit node 0 [SwitchA-route-policy-comm_policy-0] apply community no-export [SwitchA-route-policy-comm_policy-0] quit # Apply the routing policy. [SwitchA] bgp 10 [SwitchA-bgp] ipv4-family unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 route-policy comm_policy export...
Page 253: Bgp Route Reflector Configuration Example
You can see the NO_EXPORT community attribute in the output. In this case, Switch B does not advertise the route 9.1.1.0/24 through BGP. BGP route reflector configuration example Network requirements Figure 62, all switches run BGP. Between Switch A and Switch B is an EBGP connection, between Switch C and Switch B, and •...
Page 254 [SwitchB-bgp-ipv4] peer 192.1.1.1 enable [SwitchB-bgp-ipv4] peer 193.1.1.1 enable [SwitchB-bgp-ipv4] peer 193.1.1.1 next-hop-local [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 200 [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] ipv4-family unicast [SwitchC-bgp-ipv4] peer 193.1.1.2 enable [SwitchC-bgp-ipv4] peer 194.1.1.2 enable [SwitchC-bgp-ipv4] quit...
Page 255: Bgp Confederation Configuration Example
[SwitchD] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 4.4.4.4 Status codes: * - valid, > - best, d - damped, h - history, s - suppressed, S - Stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop...
Page 256 # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 65001 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] confederation id 200 [SwitchA-bgp] confederation peer-as 65002 65003 [SwitchA-bgp] peer 10.1.1.2 as-number 65002 [SwitchA-bgp] peer 10.1.2.2 as-number 65003 [SwitchA-bgp] ipv4-family 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...
Page 257 [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch D. <SwitchD> system-view [SwitchD] bgp 65001 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] confederation id 200 [SwitchD-bgp] peer 10.1.3.1 as-number 65001 [SwitchD-bgp] peer 10.1.5.2 as-number 65001 [SwitchD-bgp] ipv4-family 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.
Page 258 [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 NextHop...
Page 259: Bgp Path Selection Configuration Example
BGP routing table information of 9.1.1.0/24: From : 10.1.3.1 (1.1.1.1) Relay nexthop : 10.1.3.1 Original nexthop: 10.1.3.1 OutLabel : NULL AS-path : 100 Origin : igp Attribute value : MED 0, localpref 100, pref-val 0, pre 255 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 •...
Page 260 # Configure Switch B. <SwitchB> system-view [SwitchB] ospf [SwitchB-ospf] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> 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.
Page 261 [SwitchC] bgp 200 [SwitchC-bgp] peer 193.1.1.1 as-number 100 [SwitchC-bgp] peer 195.1.1.1 as-number 200 [SwitchC-bgp] ipv4-family unicast [SwitchC-bgp-ipv4] peer 193.1.1.1 enable [SwitchC-bgp-ipv4] peer 195.1.1.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # 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] ipv4-family unicast [SwitchD-bgp-ipv4] peer 194.1.1.2 enable...
Page 262 BGP local router ID is 195.1.1.1 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...
Page 263: Bgp Gr Configuration Example
BGP GR configuration example Network requirements Figure 65 are all BGP switches. EBGP runs between Switch A and Switch B. IBGP runs between Switch B and Switch C. Enable GR capability for BGP so that the communication between Switch A and Switch C is not affected when an active/standby switchover occurs on Switch B.
Page 264: Bfd For Bgp Configuration Example
[SwitchB-bgp-ipv4] network 9.1.1.0 24 # Enable Switch B to exchange IPv4 unicast routing information with Switch A and Switch C. [SwitchB-bgp-ipv4] peer 200.1.1.2 enable [SwitchB-bgp-ipv4] peer 9.1.1.2 enable Configure Switch C: # Configure IP addresses for interfaces. (Details not shown.) # Configure the IBGP connection.
Page 265 Figure 66 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 3.0.1.1/24 Switch C Vlan-int101 3.0.2.2/24 Vlan-int200 2.0.1.1/24 Vlan-int201 2.0.2.2/24 Switch B Vlan-int100 3.0.1.2/24 Switch D Vlan-int200 2.0.1.2/24 Vlan-int101 3.0.2.1/24 Vlan-int201 2.0.2.1/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure OSPF to make sure that Switch A and Switch C are reachable to each other.
Page 266 [SwitchA-route-policy-apply_med_50-10] quit [SwitchA] route-policy apply_med_100 permit node 10 [SwitchA-route-policy-apply_med_100-10] if-match ip address acl 2000 [SwitchA-route-policy-apply_med_100-10] apply cost 100 [SwitchA-route-policy-apply_med_100-10] quit # Apply routing policy apply_med_50 to routes outgoing to peer 3.0.2.2, and apply routing policy apply_med_100 to routes outgoing to peer 2.0.2.2. [SwitchA] bgp 200 [SwitchA-bgp] ipv4-family unicast [SwitchA-bgp-ipv4] peer 3.0.2.2 route-policy apply_med_50 export...
Page 267 Protocol: BGP Diag Info: No Diagnostic The output shows that a BFD session has been established between Switch A and Switch C. # Display BGP peer information on Switch C. <SwitchC> display bgp peer ipv4 BGP local router ID: 3.3.3.3 Local AS number: 200 Total number of peers: 2 Peers in established state: 2...
Page 268: Ipv6 Bgp Configuration Examples
BGP.: 3.0.1.1 Send NOTIFICATION Err/SubErr: 6/0 (Cease/ErrSubCode Unspecified) Error data NULL. *Mar 12 19:02:59:243 2012 SwitchC BGP/7/DEBUG: -VDC=1; BGP.: 3.0.1.1 State is changed from ESTABLISHED to IDLE. The output shows that Switch C can quickly detect the link failure and notify BGP to change the relevant IBGP session state.
Page 269 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure IBGP: # Configure Switch B. <SwitchB> system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 9::2 as-number 65009 [SwitchB-bgp] ipv6-family [SwitchB-bgp-ipv6] peer 9::2 enable [SwitchB-bgp-ipv6] quit # Configure Switch C. <SwitchC>...
Page 270 Verifying the configuration # Display IPv6 BGP peer information on Switch B. [SwitchB] display bgp peer ipv6 BGP local router ID: 2.2.2.2 Local AS number: 65009 Total number of peers: 2 Peers in established state: 2 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 9::2 65009...
Page 271: Ipv6 Bgp Route Reflector Configuration Example
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.3 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete >...
Page 272 Figure 68 Network diagram Configuration procedure Configure IPv6 addresses for interfaces and IPv4 addresses for loopback interfaces. (Details not shown.) Configure IBGP and EBGP connections and advertise network routes through IPv6 BGP: # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 100::2 as-number 200 [SwitchA-bgp] ipv6-family...
Page 273 [SwitchC-bgp] peer 102::2 as-number 200 [SwitchC-bgp] ipv6-family [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. <SwitchD> system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] peer 102::1 as-number 200 [SwitchD-bgp] ipv6-family [SwitchD-bgp-ipv6] peer 102::1 enable [SwitchD-bgp-ipv6] network 102:: 96...
Page 274: Bfd For Ipv6 Bgp Configuration Example
> Network : 102:: PrefixLen : 96 NextHop : :: LocPrf PrefVal : 32768 OutLabel : NULL Path/Ogn: i i Network : 102:: PrefixLen : 96 NextHop : 102::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL Path/Ogn: i The output shows that Switch D has learned the network 1::/64 from Switch C through route reflection.
Page 275 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure OSPFv3 so that Switch A and Switch C can reach each other. (Details not shown.) Configure IPv6 BGP on Switch A: # Establish two IBGP connections to Switch C. <SwitchA>...
Page 276 [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. <SwitchC> display bfd session verbose Total Session Num: 1 Up Session Num: 1 Init Mode: Active...
Page 277 Protocol: BGP4+ Process ID: 0 SubProtID: 0x1 Age: 00h01m07s Cost: 50 Preference: 255 Tag: 0 State: Active Adv OrigTblID: 0x1 OrigVrf: default-vrf TableID: 0xa OrigAs: 0 NBRID: 0x25000001 LastAs: 0 AttrID: 0x1 Neighbor: 3000::1 Flags: 0x10060 OrigNextHop: 3000::1 Label: NULL RealNextHop: FE80::20C:29FF:FE4A:3873 BkLabel: NULL BkNextHop: N/A...
Page 278: Troubleshooting Bgp
Flags: 0x10060 OrigNextHop: 2000::1 Label: NULL RealNextHop: FE80::20C:29FF:FE40:715 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: Vlan-interface201 BkTunnel ID: Invalid BkInterface: N/A The output shows that Switch C communicates with network 1200::0/64 through the path Switch C<—>Switch D<—>Switch A. Troubleshooting BGP Symptom Display BGP peer information by using the display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command.
Page 279: Configuring Pbr
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 uses PBR to forward matching packets and uses the routing table to forward other packets. If PBR is not configured, the device uses the routing table to forward packets.
Page 280: Pbr And Track
A node that has no if-match clauses matches any packet. PBR and Track PBR can work with the Track feature to dynamically adapt the availability status of a node configured with an apply clause to the link status of a tracked next hop. When the track entry associated with the node changes to negative because the next hop is detected as being unavailable, the node cannot be used for forwarding.
Page 281: Configuring Actions For A Node
NOTE: If an ACL match criterion is defined, packets are matched against the ACL rules, and the permit or deny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no packet is matched.
Page 282: Packet Type-Based Interface Pbr Configuration Example
Task Command Display PBR configuration. display ip policy-based-route setup Display interface PBR configuration and display ip policy-based-route interface interface-type statistics (centralized devices). interface-number Display interface PBR configuration and display ip policy-based-route interface interface-type statistics (distributed devices–centralized IRF interface-number [ slot slot-number ] devices–in standalone mode).
Page 283: Verifying The Configuration
<SwitchA> system-view [SwitchA] acl number 3101 [SwitchA-acl-adv-3101] rule permit tcp [SwitchA-acl-adv-3101] quit # Configure Node 5 for policy aaa to forward TCP packets to next hop 1.1.2.2. [SwitchA] policy-based-route aaa permit node 5 [SwitchA-pbr-aaa-5] if-match acl 3101 [SwitchA-pbr-aaa-5] apply next-hop 1.1.2.2 [SwitchA-pbr-aaa-5] quit # Configure interface PBR by applying the policy aaa to VLAN-interface 11.
Page 285: Configuring Ipv6 Static Routing
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.
Page 286: Configuring Bfd For Ipv6 Static Routes
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.
Page 287: Single-Hop Echo Mode
Step Command Remarks • Method 1: ipv6 route-static ipv6-address prefix-length { next-hop-address bfd control-packet bfd-source ipv6-address | vpn-instance d-vpn-instance-name Use either next-hop-address bfd control-packet bfd-source ip-address } method. [ preference preference-value ] [ tag tag-value ] [ description Configure BFD By default, BFD description-text ] control mode for an...
Page 288: Displaying And Maintaining Ipv6 Static Routes
Step Command Remarks • Method 1: ipv6 route-static ipv6-address prefix-length interface-type interface-number next-hop-address bfd echo-packet Use either method. [ preference preference-value ] [ tag tag-value ] [ description description-text ] By default, BFD echo mode for Configure BFD echo • an IPv6 static route is not Method 2: mode for an IPv6...
Page 289 Configuration procedure Configure the IPv6 addresses for all VLAN interfaces. (Details not shown.) Configure IPv6 static routes: # Configure a default IPv6 static route on Switch A. <SwitchA> system-view [SwitchA] ipv6 route-static :: 0 4::2 # Configure two IPv6 static routes on Switch B. <SwitchB>...
Page 290: Bfd For Ipv6 Static Routes Configuration Example (Direct Next Hop)
Static Routing table Status : <Inactive> Summary Count : 0 # Use the ping command to test the reachability. [SwitchA] ping ipv6 3::1 PING6(104=40+8+56 bytes) 4::1 --> 3::1 56 bytes from 3::1, icmp_seq=0 hlim=62 time=4.000 ms 56 bytes from 3::1, icmp_seq=1 hlim=62 time=3.000 ms 56 bytes from 3::1, icmp_seq=2 hlim=62 time=2.000 ms 56 bytes from 3::1, icmp_seq=3 hlim=62 time=2.000 ms 56 bytes from 3::1, icmp_seq=4 hlim=62 time=2.000 ms...
Page 291 [SwitchA] interface vlan-interface 10 [SwitchA-vlan-interface10] bfd min-transmit-interval 500 [SwitchA-vlan-interface10] bfd min-receive-interval 500 [SwitchA-vlan-interface10] bfd detect-multiplier 9 [SwitchA-vlan-interface10] quit [SwitchA] ipv6 route-static 120:: 64 vlan-interface 10 FE80::2E0:FCFF:FE58:123E bfd control-packet [SwitchA] ipv6 route-static 120:: 64 10::100 preference 65 [SwitchA] quit # Configure IPv6 static routes on Switch B and enable BFD control mode for the static route that traverses the Layer 2 switch.
Page 292: Bfd For Ipv6 Static Routes Configuration Example (Indirect Next Hop)
Summary Count : 1 Destination: 12::/64 Protocol : Static NextHop : 12::2 Preference: 60 Interface : Vlan10 Cost Direct Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 10. The link over VLAN-interface 10 fails.
Page 293 Figure 73 Network diagram Loop1 Loop1 121::/64 120::/64 1::9/128 2::9/128 Switch D Vlan-int10 Vlan-int12 Vlan-int10 Vlan-int12 Switch A Switch B Vlan-int11 Vlan-int13 Switch C Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int10 12::1/64 Switch B Vlan-int12 11::1/64 Vlan-int11 10::102/64 Vlan-int13...
Page 294 # Configure IPv6 static routes on Switch D. <SwitchD> system-view [SwitchD] ipv6 route-static 120:: 64 11::2 [SwitchD] ipv6 route-static 121:: 64 12::1 Verifying the configuration # Display the BFD sessions on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode:...
Page 295 Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 1 1.
Page 296: Configuring An Ipv6 Default Route
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 •...
Page 297: Configuring Ripng
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.
Page 298: Protocols And Standards
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. After RIPng receives a 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.
Page 299: Configuring Ripng Route Control
Step Command Remarks interface interface-type Enter interface view. interface-number By default, RIPng is disabled. If RIPng is not enabled on an Enable RIPng on the interface. ripng process-id enable 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.
Page 300: Advertising A Default Route
Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number By default, the Advertise a summary IPv6 ripng summary-address ipv6-address summary IPv6 prefix prefix. prefix-length is not configured. Advertising a default route Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.
Page 301: Configuring Ripng Route Redistribution
To configure a preference for RIPng: Step Command Remarks Enter system view. system-view ripng [ process-id ] [ vpn-instance Enter RIPng view. vpn-instance-name ] Configure a preference for preference [ route-policy The default setting is 100. RIPng. route-policy-name ] value Configuring RIPng route redistribution Step Command...
Page 302: Configuring Split Horizon And Poison Reverse
Step Command Remarks By default: timers { garbage-collect • The update timer is 30 seconds. garbage-collect-value | suppress Configure RIPng • suppress-value | timeout The timeout timer is 180 seconds. timers. timeout-value | update • The suppress timer is 120 seconds. update-value } * •...
Page 303: Configuring The Maximum Number Of Ecmp Routes
Step Command Remarks Enter system view. system-view ripng [ process-id ] [ vpn-instance Enter RIPng view. vpn-instance-name ] Enable the zero field check on checkzero By default, this feature is enabled. incoming RIPng packets. Configuring the maximum number of ECMP routes Step Command Remarks...
Page 304: Displaying And Maintaining Ripng
Step Command Remarks Enable the GR capability for graceful-restart By default, RIPng GR is disabled. RIPng. Displaying and maintaining RIPng Execute display commands in any view and reset commands in user view. Task Command Display configuration information of a RIPng display ripng [ process-id ] process.
Page 305 [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. <SwitchA> system-view [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 C.
Page 306 Route Flags: A - Aging, S - Suppressed, G - Garbage-collect ---------------------------------------------------------------- Peer FE80::200:2FF:FE64:8904 on Vlan-interface100 Dest 1::/64, via FE80::200:2FF:FE64:8904, cost 1, tag 0, A, 31 Sec Dest 3::/64, via FE80::200:2FF:FE64:8904, cost 1, tag 0, A, 31 Sec Dest 4::/64, via FE80::200:2FF:FE64:8904, cost 2, tag 0, A, 31 Sec Dest 5::/64,...
Page 307: Ripng Route Redistribution Configuration Example
RIPng route redistribution configuration example Network requirements As shown in Figure 75, 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.
Page 308 [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 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost...
Page 309 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : Direct NextHop : 1::1 Preference: 0 Interface : Vlan100 Cost Destination: 1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2::/64 Protocol...
Page 310: Configuring Ospfv3
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." OSPFv3 overview OSPFv3 and OSPFv2 have the following in common: 32-bit router ID and area ID •...
Page 311: Protocols And Standards
Inter-Area-Router-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—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.
Page 312: Enabling Ospfv3
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 •...
Page 313: Configuring Ospfv3 Area Parameters
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.
Page 314: Configuring Ospfv3 Network Types
To configure a virtual link: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enter OSPFv3 area view. area area-id vlink-peer router-id [ dead seconds | hello seconds | instance instance-id | By default, no virtual link is Configure a virtual link.
Page 315: Configuring An Nbma Or P2Mp Neighbor
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...
Page 316: Configuring Ospfv3 Received Route Filtering
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 Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view.
Page 317: Configuring The Maximum Number Of Ospfv3 Ecmp Routes
Step Command Remarks By default, the OSPFv3 cost is 1 for a VLAN Configure an OSPFv3 ospfv3 cost value [ instance interface, is 0 for a loopback interface, and is cost for the interface. instance-id ] automatically computed according to the interface bandwidth for other interfaces.
Page 318: Configuring Ospfv3 Route Redistribution
Step Command Remarks By default, the preference of OSPFv3 Configure a preference preference [ ase ] [ route-policy internal routes is 10, and the priority of for OSPFv3. route-policy-name ] preference 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.
Page 319: Configuring Ospfv3 Timers
Enable OSPFv3. • Configuring OSPFv3 timers Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ospfv3 timer hello seconds By default, the hello interval on P2P and Configure the hello interval. [ instance instance-id ] broadcast interfaces is 10 seconds. By default, the dead interval on P2P and broadcast interfaces is 40 seconds.
Page 320: Specifying The Lsa Generation Interval
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the SPF calculation interval is incremented by incremental-interval × 2 (n is the number of generation times) each time an SPF calculation occurs until the maximum-interval is reached. To configure SPF calculation interval: Step Command...
Page 321: Ignoring Mtu Check For Dd Packets
Step Command Remarks ospfv3 dr-priority priority [ instance The default router priority Configure a router priority. instance-id ] 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.
Page 322: Enabling The Logging Of Neighbor State Changes
Enabling the logging of neighbor state changes Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enable the logging of log-peer-change By default, this feature is enabled. neighbor state changes. Configuring OSPFv3 GR GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Page 323: Configuring Gr Helper
Configuring GR Helper You can configure the GR Helper capability on a GR Helper. To configure GR Helper Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enable the GR Helper By default, the GR Helper capability is graceful-restart helper enable capability.
Page 324: Displaying And Maintaining Ospfv3
Displaying and maintaining OSPFv3 Execute display commands in any view. Purpose Command Display information about the routes to display ospfv3 [ process-id ] abr-asbr OSPFv3 ABR and ASBR. Display brief OSPFv3 process display ospfv3 [ process-id ] brief information. Display GR status of the specified display ospfv3 [ process-id ] graceful-restart status OSPFv3 process.
Page 325 Figure 76 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # Configure Switch A: enable OSPFv3 and specify the router ID as 1.1.1.1. <SwitchA> system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 300 [SwitchA-Vlan-interface300] ospfv3 1 area 1 [SwitchA-Vlan-interface300] quit [SwitchA] interface vlan-interface 200...
Page 326 [SwitchC-Vlan-interface400] ospfv3 1 area 2 [SwitchC-Vlan-interface400] quit # Configure Switch D: enable OSPFv3 and specify the router ID as 4.4.4.4. <SwitchD> system-view [SwitchD] ospfv3 [SwitchD-ospfv3-1] router-id 4.4.4.4 [SwitchD-ospfv3-1] quit [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] ospfv3 1 area 2 [SwitchD-Vlan-interface400] quit # Display OSPFv3 neighbors on Switch B.
Page 327 NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:1::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:2::/64 Type Cost NextHop : directly-connected Interface: Vlan400 *Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 Total: 4 Intra area: 1 Inter area: 3 ASE: 0 Configure Area 2 as a stub area:...
Page 328: Configuring Ospfv3 Dr Election
NextHop : directly-connected Interface: Vlan400 *Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 Total: 5 Intra area: 1 Inter area: 4 ASE: 0 The output shows that a default route is added, and its cost is the cost of a direct route plus the configured cost.
Page 329 Figure 77 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # Configure Switch A: enable OSPFv3 and specify the router ID as 1.1.1.1. <SwitchA> system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 0 [SwitchA-Vlan-interface100] quit # Configure Switch B: enable OSPFv3 and specify the router ID as 2.2.2.2.
Page 330 [SwitchD-Vlan-interface200] ospfv3 1 area 0 [SwitchD-Vlan-interface200] quit # Display neighbor information on Switch A. The switches have the same default DR priority 1, so Switch D (the switch with the highest Router ID) is elected as the DR, and Switch C is the BDR. [SwitchA] display ospfv3 peer OSPFv3 Process 1 with Router ID 1.1.1.1 Area: 0.0.0.0...
Page 331: Configuring Ospfv3 Route Redistribution
2.2.2.2 2-Way/DROther 00:00:36 Vlan200 3.3.3.3 Full/Backup 00:00:35 Vlan200 4.4.4.4 Full/DR 00:00:33 Vlan200 # Display neighbor information on Switch D. Switch D is still the DR. [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...
Page 332 OSPFv3 process 1 and OSPFv3 process 2 run on Switch B. Switch B communicates with Switch A • and Switch C through OSPFv3 process 1 and OSPFv3 process 2. Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on •...
Page 333 [SwitchC] ospfv3 2 [SwitchC-ospfv3-2] router-id 4.4.4.4 [SwitchC-ospfv3-2] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ospfv3 2 area 2 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 2 area 2 [SwitchC-Vlan-interface400] quit # Display the routing table on Switch C. [SwitchC] display ipv6 routing-table Destinations : 7 Routes : 7 Destination: ::1/128 Protocol...
Page 334: Configuring Ospfv3 Gr
[SwitchB-ospfv3-2] quit # Display the routing table on Switch C. [SwitchC] display ipv6 routing-table Destinations : 9 Routes : 9 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : OSPFv3 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface...
Page 335 Switch A acts as the GR Restarter. Switch B and Switch C act as the GR Helpers, and synchronize • their LSDBs with Switch A through out-of-band (OOB) communication of GR. Figure 79 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # On Switch A, enable OSPFv3 process 1, enable GR, and set the router ID to 1.1.1.1.
Page 336: Configuring Bfd For Ospfv3
Verifying the configuration After all switches function properly, perform a master/backup switchover on Switch A to trigger an OSPFv3 GR operation. Configuring BFD for OSPFv3 Network requirements As shown in Figure Configure OSPFv3 on Switch A, Switch B and Switch C and configure BFD over the link Switch •...
Page 337 <SwitchB> system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ospfv3 1 area 0 [SwitchB-Vlan-interface10] quit [SwitchB] interface vlan-interface 13 [SwitchB-Vlan-interface13] ospfv3 1 area 0 [SwitchB-Vlan-interface13] quit # On Switch C, enable OSPFv3 and configure the router ID as 3.3.3.3. <SwitchC>...
Page 338 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. <SwitchA> display ipv6 routing-table 2001:4::0 64 Summary Count : 1 Destination: 2001:4::/64 Protocol...
Page 339: Configuring Ipv6 Is-Is
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).
Page 340: Configuring Ipv6 Is-Is Route Control
Step Command Remarks Enable IPv6 for an IS-IS isis ipv6 enable [ process-id ] The default setting is disabled. process on the interface. 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...
Page 341: Configuring Bfd For Ipv6 Is-Is
Step Command Remarks By default, the maximum number of ECMP routes is the same as that configured Specify the maximum in the max-ecmp-num number of ECMP routes for ipv6 maximum load-balancing number command. For more load balancing. information about the max-ecmp-num command, see IP Routing Command Reference.
Page 342: Ipv6 Is-Is Configuration Examples
IPv6 IS-IS configuration examples IPv6 IS-IS basic configuration example Network requirements As shown in Figure 81, Switch A, Switch B, Switch C, and Switch D, all enabled with IPv6, reside in the same AS. Configure IPv6 IS-IS on the switches so that they can reach each other. Switch A and Switch B are Level- 1 switches, Switch D is a Level-2 switch, and Switch C is a Level- 1 -2 switch.
Page 343 # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] ipv6 enable [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis ipv6 enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 200 [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.
Page 344 Flag : R/-/- Cost : 20 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100 Destination : 2001:3:: PrefixLen: 64 Flag : R/-/- Cost : 20 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set # Display the IPv6 IS-IS routing table on Switch B.
Page 345 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: Vlan200 Destination : 2001:3:: PrefixLen: 64 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: Vlan300 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv6 Forwarding Table ----------------------------- Destination : 2001:1::...
Page 346: Bfd For Ipv6 Is-Is Configuration Example
Next Hop : Direct Interface: Vlan300 Destination : 2001:4::1 PrefixLen: 128 Flag : D/L/- Cost Next Hop : Direct Interface: Loop1 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set BFD for IPv6 IS-IS configuration example Network requirements As shown in Figure 82, configure IPv6 IS-IS on Switch A and Switch B so that they can reach other.
Page 347 [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] isis ipv6 enable 1 [SwitchA-Vlan-interface11] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [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...
Page 348 <SwitchA> display bfd session Total Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 1441 Remote Discr: 1450 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...
Page 349: Configuring Ipv6 Pbr
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 uses PBR to forward matching packets and uses the routing table to forward non-matching packets.
Page 350: Pbr And Track
A node that has no if-match clauses matches any packet. PBR and Track PBR can work with the Track feature to dynamically adapt the availability status of a node configured with an apply clause to the link status of a tracked next hop. When the track entry associated with the node changes to negative because the next hop is detected as unavailable, the node cannot be used for forwarding.
Page 351: Configuring Actions For An Ipv6 Node
NOTE: If an ACL match criterion is defined, packets are matched against the ACL rules, and the permit or deny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no packet is matched.
Page 352: Packet Type-Based Ipv6 Interface Pbr Configuration Example
Task Command Display IPv6 interface PBR configuration and display ipv6 policy-based-route interface interface-type statistics. interface-number [ slot slot-number ] Clear IPv6 PBR statistics. reset ipv6 policy-based-route statistics [ policy policy-name ] Packet type-based IPv6 interface PBR configuration example Network requirements As shown in Figure 83, configure IPv6 PBR on Switch A to forward all TCP packets received on...
Page 353: Verifying The Configuration
[SwitchA-Vlan-interface10] ripng 1 enable [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 2::1 64 [SwitchA-Vlan-interface20] ripng 1 enable [SwitchA-Vlan-interface20] quit # Configure ACL 3001 to match TCP packets. [SwitchA] acl ipv6 number 3001 [SwitchA-acl6-adv-3001] rule permit tcp [SwitchA-acl6-adv-3001] quit # Configure Node 5 for policy aaa to forward TCP packets to next hop 1::2.
Page 354 Telnet uses TCP, and ping uses ICMP. The preceding results show that all TCP packets arriving on VLAN-interface 1 1 of Switch A are forwarded to next hop 1::2, and other packets are forwarded through VLAN-interface 20. The IPv6 interface PBR configuration is effective.
Page 355: Configuring Routing Policies
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: Configure filters based on route attributes, such as destination address and the advertising router's address.
Page 356: Routing Policy
For more information about extended community lists, see MCE 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.
Page 357: Configuring An As Path List
Step Command Remarks Enter system view. system-view ip prefix-list prefix-list-name [ index index-number ] Configure an IPv4 { deny | permit } ip-address mask-length By default, no IPv4 prefix prefix list. [ greater-equal min-mask-length ] [ less-equal list is configured. max-mask-length ] Configuring an IPv6 prefix list If all items are set to deny mode, no routes can pass the IPv6 prefix list.
Page 358: Configuring An Extended Community List
Step Command Remarks • Configure a basic community list: ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit } [ community-number&<1-32> | aa:nn&<1-32> ] Use either method. [ internet | no-advertise | no-export | Configure a community By default, no no-export-subconfed ] * list.
Page 359: Configuring If-Match Clauses
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.
Page 360: Configuring Apply Clauses
Step Command Remarks By default, no local Match BGP routes having the if-match local-preference preference preference is configured for specified local preference. BGP routes. if-match route-type { external-type1 | external-type1or2 | external-type2 | Match routes having the internal | is-is-level-1 | is-is-level-2 | By default, no route type specified route type.
Page 361: Configuring A Continue Clause
Step Command Remarks • Set the next hop for IPv4 routes: apply ip-address next-hop By default, no next hop is set for ip-address [ public | IPv4/IPv6 routes. vpn-instance The apply ip-address next-hop and Set the next hop for routes. vpn-instance-name ] apply ipv6 next-hop commands do •...
Page 362: Displaying And Maintaining The Routing Policy
Step Command Remarks route-policy route-policy-name Enter routing policy node view. { deny | permit } node node-number By default, no continue clause is configured. Specify the next node to be continue [ node-number ] The specified next node must matched. have a larger number than the current node.
Page 363 Figure 84 Network diagram IS-IS OSPF Vlan-int100 Vlan-int200 192.168.1.2/24 192.168.2.2/24 Switch B Vlan-int201 172.17.1.1/24 Vlan-int100 Vlan-int200 Vlan-int202 192.168.1.1/24 192.168.2.1/24 172.17.2.1/24 Switch A Switch C Vlan-int203 172.17.3.1/24 Configuration procedure Specify IP addresses for interfaces. (Details not shown.) Configure IS-IS: # Configure Switch C. <SwitchC>...
Page 364 [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.
Page 365: Applying A Routing Policy To Ipv6 Route Redistribution
[SwitchB-route-policy-isis2ospf-30] quit 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...
Page 366 [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. [SwitchA] ipv6 route-static 20:: 32 11::2 [SwitchA] ipv6 route-static 30:: 32 11::2 [SwitchA] ipv6 route-static 40:: 32 11::2...
Page 367 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...
Page 368: Support And Other Resources
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers • Technical support registration number (if applicable) • • Product serial numbers Error messages •...
Page 369: Conventions
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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 370 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.
Page 371: Index
Index Numerics IPv4 BGP GR configuration, IPv4 BGP load balancing configuration, 4-byte IPv4 BGP path selection configuration, IPv4 BGP AS number suppression, IPv4 BGP route reflector configuration, IPv6 BGP AS number suppression, IPv4 BGP route summarization, IPv4 BGP-IGP route redistribution, IPv6 BGP basic configuration, OSPF route summarization on ABR, IPv6 BGP BFD configuration,...
Page 372 OSPF stub area configuration, IPv6 BGP BFD configuration, OSPF totally NSSA area, IPv6 BGP configuration, OSPF totally stub area, IPv6 BGP fake AS number advertisement, OSPF virtual link configuration, IPv6 BGP MED AS route comparison (confederation peers), 198, OSPFv3 area configuration, IPv6 BGP MED AS route comparison (diff OSPFv3 area parameter configuration, ASs), 196,...
Page 373 IPv4 BGP MED AS route comparison IP routing route backup, (per-AS), bandwidth IPv4 BGP MED default value, OSPF reference value, IPv4 BGP NEXT_HOP, IPv4 BGP private AS number removal, OSPF, IPv6 BGP AS number substitution, OSPF election, IPv6 BGP AS_PATH best route selection, IPv6 BGP fake AS number advertisement, IPv4 BGP configuration, 222, IPv6 BGP MED AS route comparison...
Page 374 first AS number of EBGP route updates, IPv6 static route BFD control mode (direct next hop), GR configuration, IPv6 static route BFD control mode (indirect next GR Helper configuration, hop), GR Restarter configuration, IPv6 static route BFD echo mode (single hop), IPv4 EBGP peer protection (low memory OSPF BFD detection (bidirectional control), exemption),...
Page 375 IPv4 BGP MED AS route comparison IPv4 BGP keepalive interval, (confederation peers), IPv4 BGP load balancing, IPv4 BGP MED AS route comparison (diff IPv4 BGP MED default value, ASs), IPv4 BGP NEXT_HOP attribute, IPv4 BGP MED AS route comparison IPv4 BGP path selection, (per-AS), IPv4 BGP peer, IPv6 BGP MED AS route comparison...
Page 376 IPv6 IS-IS BFD, 330, IS-IS route convergence priority, IPv6 IS-IS route control, IS-IS route filtering, IPv6 node action, IS-IS route redistribution, 121, IPv6 node match criteria, IS-IS route summarization, IPv6 PBR, 338, 339, IS-IS routing domain authentication, IPv6 PBR configuration (interface/packet IS-IS system ID-host name mapping, type-based), IS-IS system ID-host name mapping (dynamic),...
Page 377 OSPF route redistribution, 66, RIP basics, 22, OSPF route redistribution from different routing RIP BFD, protocol, RIP FRR, 32, OSPF route summarization, RIP GR, OSPF route summarization on ABR, RIP interface additional metric, OSPF stub area, 58, RIP max number ECMP routes, OSPF stub router, RIP packet send rate, OSPF summary route advertisement,...
Page 378 static route BFD bidirectional control mode database (direct next hop), OSPF DD packet, static route BFD bidirectional control mode (indirect next hop), OSPFv3 DD packet ignore MTU check, static route BFD echo mode (single-hop), OSPFv3 packet type, static route FRR, dead packet timer (OSPF), static routing, 6, default...
Page 379 IPv6 IS-IS BFD configuration, RIP summary route advertisement configuration, IPv6 IS-IS configuration, RIPng basic configuration, IPv6 PBR configuration (interface/packet RIPng configuration, type-based), RIPng route redistribution, IPv6 static routing, routing policy application to IPv4 route IPv6 static routing basics, redistribution, IPv6 static routing BFD (direct next hop), routing policy application to IPv6 route redistribution, IPv6 static routing BFD (indirect next hop),...
Page 380 IP routing route redistribution, RIP max number ECMP routes, IPv4 BGP-IGP route redistribution, RIPng max number ECMP routes, OSPFv3 route redistribution, 307, electing RIPng received/redistributed route filtering, OSPF DR election, RIPng route redistribution, 290, OSPFv3 DR election configuration, domain enabling IS-IS routing domain, 1 10 BGP,...
Page 381 enhancing IPv6 BGP route reception filtering policies, IS-IS network security, IPv6 BGP route reflector configuration, establishing IS-IS LSP-calculated routes, IPv4 BGP multiple hop EBGP session IS-IS redistributed routes, establishment, IS-IS routes, IPv4 BGP session establishment disable, OSPF Type-3 LSA filtering, IPv6 BGP multiple hop EBGP session OSPFv3 Inter-Area-Prefix LSA filtering, establishment,...
Page 382 OSPFv3 BFD configuration, IS-IS configuration, PBR configuration, 268, 269, IS-IS GR configuration, PBR configuration (interface/packet IS-IS GR Helper configuration, length-based), IS-IS GR Restarter configuration, PBR policy configuration, OSPF configuration, 75, fragment OSPF GR Helper configuration, IS-IS LSP fragment extension, OSPF GR Restarter configuration, OSPF trigger, IS-IS configuration, OSPFv3 GR configuration,...
Page 383 OSPF stub area, IS-IS hello packet send interval, OSPF summary route advertisement, IS-IS SPF calculation interval, OSPF virtual link, OSPF exit overflow interval, IDP (IS-IS area address), OSPF LSA arrival interval, IETF OSPF LSA generation interval, OSPF GR configuration, OSPF LSU transmit rate, OSPF GR Helper, OSPF SPF calculation interval, OSPF GR Restarter,...
Page 384 BGP route recursion, OSPFv3 interface DR priority, BGP route selection, 163, OSPFv3 interface packet send/receive disable, BGP route summarization, 164, OSPFv3 LSA generation interval, BGP session state change logging, OSPFv3 LSA transmission delay, BGP soft reset configuration, OSPFv3 max number ECMP routes, BGP TCP connection source interface, OSPFv3 NBMA neighbor configuration, BGP trap enable,...
Page 385 RIPng packet zero field check configuration, IPv4 RIPng poison reverse configuration, IS-IS basic configuration, RIPng preference, IS-IS configuration, 108, RIPng received/redistributed route filtering, IS-IS DIS election configuration, RIPng route control configuration, OSPF basic configuration, RIPng route entry, OSPF BFD configuration, RIPng route redistribution, 290, OSPF configuration, 48, 55, RIPng route summarization,...
Page 386 MED AS route comparison (diff ASs), OSPFv3 LSA generation interval, MED AS route comparison (per-AS), OSPFv3 LSA transmission delay, MED default value, OSPFv3 max number ECMP routes, multiple hop EBGP session establishment, OSPFv3 NBMA neighbor configuration, NEXT_HOP attribute, OSPFv3 neighbor state change logging, 31 1 path selection configuration, OSPFv3 network optimization,...
Page 387 MED AS route comparison (confederation maintaining, peers), match mode/node clause relationship, MED AS route comparison (diff ASs), policy, MED AS route comparison (per-AS), Track collaboration, MED default value, IPv6 static routing multiple hop EBGP session establishment, basic configuration, NEXT_HOP attribute, BFD configuration (direct next hop), peer configuration, BFD configuration (indirect next hop),...
Page 388 interface packet send/receive disable, system ID, IPv6 IS-IS. See IPv6 IS-IS system ID-host name mapping configuration, IS level configuration, 1 16 system ID-host name mapping dynamic configuration, ISPF enable, system ID-host name mapping static Level- 1 router, 1 10 configuration, Level- 1 -2 router, 1 10 terminology,...
Page 389 routing policy AS_PATH list, OSPF NSSA LSA, routing policy AS_PATH list configuration, OSPF opaque LSA, routing policy community list, OSPF router LSA, routing policy community list configuration, OSPF Type-3 LSA filtering, routing policy extended community list, OSPFv3 AS external LSA, routing policy extended community list OSPFv3 grace LSA, configuration,...
Page 390 PBR, IPv4 EBGP peer protection (low memory exemption), RIP, IPv6 EBGP peer protection (low memory RIPng, exemption), routing policy, message managing BGP keepalive, BGP large scale network management, BGP notification, manual BGP open, IPv4 BGP route manual summarization, BGP route-refresh, IPv6 BGP route manual summarization, BGP update, mapping...
Page 391 IPv4 BGP-IGP route redistribution, BGP default route advertisement to peer/peer group, IPv6 BGP basic configuration, BGP GR configuration, IPv6 BGP BFD configuration, BGP GR Helper configuration, IPv6 BGP configuration, BGP GR Restarter configuration, IPv6 BGP route reflector configuration, BGP large-scale network configuration, overview, BGP load balancing, protocols and standards,...
Page 392 IPv4 BGP load balancing, 21 1 IPv6 BGP route update save, IPv4 BGP local AS number IPv6 BGP route-refresh, appearance, 201, IPv6 BGP routes received from peer/peer IPv4 BGP local network injection, group, IPv4 BGP multiple hop EBGP session IPv6 BGP session establishment disable, establishment, IPv6 IS-IS BFD configuration, IPv4 BGP NEXT_HOP attribute,...
Page 393 IS-IS LSP fragment extension, OSPF LSA generation interval, IS-IS LSP length specification, OSPF LSA transmission delay, IS-IS LSP parameters, OSPF LSDB max number external LSAs, IS-IS LSP timer, OSPF LSU transmit rate, IS-IS neighbor relationship authentication, OSPF NBMA network type configuration for interface, IS-IS neighbor state change logging, OSPF neighbor state change logging,...
Page 394 OSPFv3 interface DR priority, RIP route entries, OSPFv3 interface packet send/receive RIP route redistribution configuration, 27, disable, RIP routing loop prevention, OSPFv3 LSA generation interval, RIP split horizon configuration, OSPFv3 LSA transmission delay, RIP summary route advertisement configuration, OSPFv3 max number ECMP routes, RIP timer configuration, OSPFv3 NBMA neighbor configuration, RIP update source IP address check,...
Page 395 static route FRR configuration, OSPF GR configuration, tuning BGP, OSPF NSSA area configuration, network management OSPF route redistribution, BGP configuration, 158, OSPF stub area, BGP large scale networks, OSPF summary route advertisement, IP routing configuration, OSPF virtual link, IPv4 BGP basic configuration, OSPFv3 area configuration, IPv4 BGP BFD configuration, OSPFv3 BFD configuration,...
Page 396 NO_EXPORT_SUBCONFED IPv4 BGP fake AS number advertisement, BGP COMMUNITY path attribute, IPv4 BGP local AS number appearance, 201, node IPv4 BGP private AS number removal, IPv6 node action, IPv6 BGP 4-byte AS number suppression, IPv6 node creation, IPv6 BGP AS number substitution, IPv6 node match criteria configuration, IPv6 BGP fake AS number advertisement, IPv6 PBR policy,...
Page 397 exit overflow interval, route redistribution configuration, FRR backup next hop calculation, route redistribution from different routing protocol, FRR backup next hop specification (routing policy), route summarization configuration, FRR configuration, 78, route summarization on ABR, GR configuration, 75, route types, GR Helper configuration, router types, GR Restarter configuration, SPF calculation interval,...
Page 398 network optimization, IPv6 policy configuration, network tuning, IS-IS hello multiplier, network type configuration, IS-IS hello packet send interval, network type configuration (for interface), IS-IS interface hello packet send, P2MP neighbor configuration, IS-IS interface packet send/receive, packet types, IS-IS PDU CLVs, 1 14 preference configuration, IS-IS PDU hello type,...
Page 399 PBR configuration (interface/packet node match criteria, length-based), policy, PBR policy configuration, policy configuration, RIP packet send rate configuration, Track collaboration, RIPng, RIPng packet zero field check, IS-IS CLVs, 1 14 specifying IS-IS CSNP packet send interval, IS-IS hello type, 1 13 parameter IS-IS LSP type, 1 13...
Page 400 IPv4 BGP route distribution filtering policy, OSPF default route redistribution, IPv4 BGP route reception filtering policy, OSPF host route advertisement, IPv6 BGP route distribution filtering policy, OSPF protocol preference configuration, IPv6 BGP route reception filtering policy, OSPF redistributed route default parameters, IPv6 PBR, OSPF route redistribution configuration, IPv6 PBR configuration, 338, 339,...
Page 401 configuring BGP peer, configuring IPv6 BGP basics, configuring BGP peer group, configuring IPv6 BGP BFD, 222, configuring BGP route filtering policies, configuring IPv6 BGP COMMUNITY, configuring BGP route summarization, configuring IPv6 BGP default local preference, configuring BGP soft reset, configuring IPv6 BGP holdtime, configuring IP routing max number ECMP configuring IPv6 BGP keepalive interval, routes,...
Page 402 configuring IPv6 static routing BFD (indirect next configuring OSPF basics, hop), configuring OSPF BFD, 77, configuring IS-IS, configuring OSPF BFD detection (bidirectional configuring IS-IS area authentication, control), configuring IS-IS authentication, configuring OSPF BFD detection (single-hop echo), configuring IS-IS basics, configuring OSPF broadcast network type for configuring IS-IS BFD, 133, interface, configuring IS-IS circuit level,...
Page 403 configuring OSPF route summarization on configuring RIP basics, 22, ABR, configuring RIP BFD, configuring OSPF stub area, 58, configuring RIP FRR, 32, configuring OSPF stub router, configuring RIP GR, configuring OSPF summary route configuring RIP interface additional metric, advertisement, configuring RIP max number ECMP routes, configuring OSPF timer, configuring RIP packet send rate, configuring OSPF Type-3 LSA filtering,...
Page 404 configuring routing policy IPv6 prefix list, displaying IS-IS, configuring static route, displaying OSPF, configuring static route BFD, displaying OSPFv3, configuring static route BFD bidirectional control displaying PBR, mode (direct next hop), displaying RIP, configuring static route BFD bidirectional control displaying RIPng, mode (indirect next hop), displaying routing policy, configuring static route BFD echo mode...
Page 405 enabling OSPF neighbor state change protecting IPv6 EBGP peer (low memory logging, exemption), enabling OSPF RFC 1583 compatibility, redistributing IPv4 BGP IGP routes, enabling OSPFv3, redistributing IPv6 BGP IGP routes, enabling OSPFv3 neighbor state change removing IPv4 BGP private AS number from EBGP logging, 31 1 peer/peer group update,...
Page 406 OSPF RFC 1583 compatibility, FRR configuration, 32, OSPFv3, GR configuration, RIP, GR Helper configuration, RIPng, GR Restarter configuration, host route reception disable, interface additional metric configuration, receiving interface advertisement control, IPv4 BGP routes received from peer/peer interface reception control, group, IPv6.
Page 407 packet zero field check, IP routing ECMP route max number configuration, poison reverse configuration, 291, IP routing load sharing, preference configuration, IP routing route backup, protocols and standards, IP routing route preference, received/redistributed route filtering, IP routing route recursion, route control configuration, IP routing route redistribution, route entry, IPv4 BGP IGP route redistribution,...
Page 408 IPv6 static routing BFD (direct next hop), RIP route redistribution configuration, 27, IPv6 static routing BFD (indirect next hop), RIP split horizon configuration, IPv6 static routing configuration, 274, RIP update source IP address check, IS-IS default route advertisement, RIPng default route advertisement, IS-IS ECMP routes max number, 1 19 RIPng max number ECMP routes,...
Page 409 IPv4 BGP load balancing, 21 1 IS-IS route control configuration, 1 17 IPv6 BGP load balancing, 21 1 IS-IS route convergence priority, IPv6 default route. See under IPv6 static routing IS-IS route filtering, IPv6 IS-IS. See IPv6 IS-IS IS-IS route leaking, 1 1 1 IPv6 policy-based routing.
Page 410 OSPF P2P network type configuration for RIP configuration, 20, 21, interface, RIP default route advertisement, OSPF preference, RIP FRR configuration, 32, OSPF redistributed route default parameters, RIP GR configuration, OSPF redistributed route summarization on RIP host route reception disable, ASBR, RIP interface additional metric configuration, OSPF route control configuration, RIP interface advertisement control,...
Page 411 RIPv1 message zero field check, IPv4 BGP received route preferred value, RIPv2 message authentication configuration, IPv6 BGP received route preferred value, RIPv2 route summarization configuration, IS-IS CSNP packet send interval, static. See static routing IS-IS hello multiplier, tuning BGP network, IS-IS hello packet send interval, Routing Information Protocol.
Page 412 OSPF stub area, 51, IPv6 BGP configuration, OSPF stub area configuration, IPv6 BGP route reflector configuration, OSPF stub router configuration, IPv6 IS-IS basic configuration, OSPF totally stub area, IPv6 IS-IS BFD configuration, OSPFv3 stub area configuration, IPv6 IS-IS configuration, substituting IPv6 PBR configuration (interface/packet type-based), IPv4 BGP AS number substitution,...
Page 413 RIPng configuration, time RIPng route redistribution, IPv4 BGP holdtime, routing policy application to IPv4 route IPv6 BGP holdtime, redistribution, timeout timer, routing policy application to IPv6 route timer redistribution, IS-IS LSP timers, routing policy configuration, OSPF dead packet timer, static routing basic configuration, OSPF hello packet timer, static routing BFD configuration (direct next OSPF LSA retransmission packet timer,...
Page 414 IS-IS network, OSPF network, OSPFv3 network, RIPng network, tuning RIP networks, Type 1 external OSPF route type, Type 2 external OSPF route type, RIP configuration, 20, 21, RIPng basic configuration, 287, RIPng configuration, 286, 287, RIPng GR configuration, RIPng route redistribution, unicast IP routing configuration, IP routing dynamic routing protocols,...

HP 6125XLG Configuration Manual

IP Routing Basics

Configuring Static Routing

Configuring a Default Route

Configuring RIP

Configuring OSPF

Configuring IS-IS

Configuring BGP

Configuring PBR

Configuring Ipv6 Static Routing

Quick Links

Configuration Guide

Troubleshooting

Related Manuals for HP 6125XLG

Summary of Contents for HP 6125XLG