HP FlexFabric 5930 Switch Series Layer 3 - IP Routing Configuration Guide Part number: 5998-4571 Software version: Release 2406 & Release 2407P01 Document version: 6W101-20140404
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents Configuring basic IP routing········································································································································ 1 Routing table ······································································································································································ 1 Dynamic routing protocols ·······························································································································
Configuring OSPF network types ································································································································· 31 Configuration prerequisites ·································································································································· 31 Configuring the broadcast network type for an interface ················································································· 31 Configuring the NBMA network type for an inte
OSPF DR election configuration example ··········································································································· 64 OSPF virtual link configuration example ············································································································· 68 Troubleshooting OSPF configuration ··························································································································· 70 No OSPF neighbor relationship established ·····
Configuring a BGP confederation ····················································································································· 135 Configuring BGP GR ··················································································································································· 136 Enabling SNMP notifications for BGP························································································································ 137 Enabling logging of session
Configuring an IPv6 default route ·························································································································· 201 Configuring OSPFv3 ··············································································································································· 202 OSPFv3 overview ························································································································································· 202 OSPFv3 pac
Configuring match criteria for an IPv6 node ···································································································· 234 Configuring actions for an IPv6 node ··············································································································· 235 Configuring IPv6 PBR ··················································································································································· 235 Configuring IPv6 local PBR···········
Configuring basic IP routing IP routing directs IP packet forwarding on routers based on a routing table. Routing table A RIB contains the global routing information and related information, including route recursion, route redistribution, and route extension information. The router selects optimal routes from the routing table and puts them into the FIB table, and it uses the FIB table to forward packets. For more information about the FIB table, see Layer 3—IP Services Configuration Guide.
• Cost—If multiple routes to a destination have the same preference, the one with the smallest cost is the optimal route. • NextHop—Next hop. • Interface—Output interface. Dynamic routing protocols Static routes work well in small, stable networks. They are easy to configure and require fewer system resources. However, in networks where topology changes occur frequently, a typical practice is to configure a dynamic routing protocol.
Route backup Route backup can improve network availability. Among multiple routes to the same destination, the route with the highest priority is the primary route and others are secondary routes. The router forwards matching packets through the primary route. When the primary route fails, the route with the highest preference among the secondary routes is selected to forward packets. When the primary route recovers, the router uses it to forward packets.
Step 4. Configure the maximum lifetime for IPv4 routes and labels in the RIB. Command Remarks protocol protocol lifetime seconds By default, the maximum lifetime for routes and labels in the RIB is 480 seconds. To configure the maximum route lifetime for routes and labels in the RIB (IPv6): Step Command Remarks 5. Enter system view. system-view N/A 6. Enter RIB view. rib N/A 7. Create a RIB IPv6 address family and enter RIB IPv6 address family view.
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 1. Enter system view. system-view N/A 2. Configure the maximum number of ECMP routes. max-ecmp-num number By default, the maximum number of ECMP routes is 8.
Displaying and maintaining a routing table Execute display commands in any view and reset commands in user view. Task Command Display the ECMP mode. display ecmp mode Display routing table information. display ip routing-table [ vpn-instance vpn-instance-name ] [ verbose ] Display information about routes permitted by an IPv4 basic ACL . display ip routing-table [ vpn-instance vpn-instance-name ] acl acl-number [ verbose ] Display information about routes to a specific destination address.
Task Command Display IPv6 route statistics. display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics Display route attribute information in the IPv6 RIB. display ipv6 rib attribute [ attribute-id ] Display IPv6 RIB GR state information. display ipv6 rib graceful-restart Display next hop information in the IPv6 RIB.
Configuring static routing Static routes are manually configured. If a network's topology is simple, you only need to configure static routes for the network to work correctly. Static routes cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. Configuring a static route Before you configure a static route, complete the following tasks: • Configure the physical parameters for related interfaces.
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. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols. For more information about BFD, see High Availability Configuration Guide.
Step Command Remarks • Method 1: 2. Configure BFD control mode for a static route.
Displaying and maintaining static routes Execute display commands in any view. Task Command Display static route information. display ip routing-table protocol static [ inactive | verbose ] Display static route next hop information. display route-static nib [ nib-id ] [ verbose ] Display static routing table information.
[SwitchC] ip route-static 0.0.0.0 0.0.0.0 1.1.5.5 3. Configure the default gateways of Host A, Host B, and Host C as 1.1.2.3, 1.1.6.1, and 1.1.3.1. (Details not shown.) Verifying the configuration # Display static routes on Switch A. [SwitchA] display ip routing-table protocol static Summary Count : 1 Static Routing table Status : Summary Count : 1 Destination/Mask Proto Pre 0.0.0.0/0 Static 60 Cost NextHop Interface 0 1.1.4.
Tracing route to 1.1.2.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 1.1.6.1 2 <1 ms <1 ms <1 ms 1.1.4.1 3 1 ms <1 ms <1 ms 1.1.2.2 Trace complete. BFD for static routes configuration example (direct next hop) Network requirements In Figure 2, configure a static route to subnet 120.1.1.0/24 on Switch A, and configure a static route to subnet 121.1.1.0/24 on Switch B. Enable BFD for both routes. Configure a static route to subnet 120.1.1.0/24 and a static route to subnet 121.1.1.
# Configure static routes on Switch B and enable BFD control mode for the static route that traverses the Layer 2 switch. system-view [SwitchB] interface vlan-interface 10 [SwitchB-vlan-interface10] bfd min-transmit-interval 500 [SwitchB-vlan-interface10] bfd min-receive-interval 500 [SwitchB-vlan-interface10] bfd detect-multiplier 9 [SwitchB-vlan-interface10] quit [SwitchB] ip route-static 121.1.1.0 24 vlan-interface 10 12.1.1.1 bfd control-packet [SwitchB] ip route-static 121.1.1.
Static Routing table Status : Summary Count : 1 Destination/Mask Proto Pre 120.1.1.0/24 Static 65 Cost NextHop Interface 0 10.1.1.100 Vlan11 Static Routing table Status : Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for static routes configuration example (indirect next hop) Network requirements In Figure 3, Switch A has a route to interface Loopback 1 (2.2.2.
[SwitchA] bfd multi-hop min-transmit-interval 500 [SwitchA] bfd multi-hop min-receive-interval 500 [SwitchA] bfd multi-hop detect-multiplier 9 [SwitchA] ip route-static 120.1.1.0 24 2.2.2.9 bfd control-packet bfd-source 1.1.1.9 [SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 preference 65 [SwitchA] quit # Configure static routes on Switch B and enable BFD control mode for the static route that traverses Switch D.
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. # Display static routes on Switch A. display ip routing-table protocol static Summary Count : 1 Static Routing table Status : Summary Count : 1 Destination/Mask Proto Pre 120.1.1.0/24 Static 65 Cost NextHop Interface 0 10.1.1.
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 0.0.0.0. For more information, see "Configuring a static route.
Configuring OSPF Open Shortest Path First (OSPF) is a link-state IGP developed by the OSPF working group of the IETF. OSPF version 2 is used for IPv4. OSPF refers to OSPFv2 throughout this chapter. Overview OSPF has the following features: • Wide scope—Supports various network sizes and up to several hundred routers in an OSPF routing domain. • Fast convergence—Advertises routing updates instantly upon network topology changes. • Loop free—Computes routes with the SPF algorithm to avoid routing loops.
• Router LSA—Type-1 LSA, originated by all routers and flooded throughout a single area only. This LSA describes the collected states of the router's interfaces to an area. • Network LSA—Type-2 LSA, originated for broadcast and NBMA networks by the designated router, and flooded throughout a single area only. This LSA contains the list of routers connected to the network. • Network Summary LSA—Type-3 LSA, originated by Area Border Routers (ABRs), and flooded throughout the LSA's associated area.
Figure 4 Area-based OSPF network partition Area 4 Area 1 Area 0 Area 2 Area 3 Backbone area and virtual links Each AS has a backbone area that distributes routing information between non-backbone areas. Routing information between non-backbone areas must be forwarded by the backbone area. OSPF has the following requirements: • All non-backbone areas must maintain connectivity to the backbone area. • The backbone area must maintain connectivity within itself.
Figure 6 Virtual link application 2 Area 1 Virtual link R2 R1 Area 0 The virtual link between the two ABRs acts as a point-to-point connection. You can configure interface parameters, such as hello interval, on the virtual link as they are configured on a physical interface. The two ABRs on the virtual link unicast OSPF packets to each other, and the OSPF routers in between convey these OSPF packets as normal IP packets.
• Internal router—All interfaces on an internal router belong to one OSPF area. • ABR—Belongs to more than two areas, one of which must be the backbone area. ABR connects the backbone area to a non-backbone area. An ABR and the backbone area can be connected through a physical or logical link. • Backbone router—At least one interface of a backbone router must reside in the backbone area. All ABRs and internal routers in Area 0 are backbone routers.
destination of the Type-2 external route. If two Type-2 routes to the same destination have the same cost, OSPF takes the cost from the router to the ASBR into consideration to determine the best route. Route calculation OSPF computes routes in an area as follows: • Each router generates LSAs based on the network topology around itself, and sends them to other routers in update packets. • Each OSPF router collects LSAs from other routers to compose an LSDB.
• BDR—Elected along with the DR to establish adjacencies with all other routers. If the DR fails, the BDR immediately becomes the new DR, and other routers elect a new BDR. Routers other than the DR and BDR are called "DROthers." They do not establish adjacencies with one another, so the number of adjacencies is reduced. The role of a router is subnet (or interface) specific. It might be a DR on one interface and a BDR or DROther on another interface.
• RFC 3137, OSPF Stub Router Advertisement • RFC 4811, OSPF Out-of-Band LSDB Resynchronization • RFC 4812, OSPF Restart Signaling • RFC 4813, OSPF Link-Local Signaling OSPF configuration task list To run OSPF, you must first enable OSPF on the router. Make a proper configuration plan to avoid incorrect settings that can result in route blocking and routing loops. To configure OSPF, perform the following tasks: Tasks at a glance (Required.) Enabling OSPF (Optional.
Tasks at a glance (Optional.
If you specify no router ID when you create the OSPF process, the global router ID is used. HP recommends specifying a router ID when you create the OSPF process. • OSPF supports multiple processes and VPNs: • To run multiple OSPF processes, you must specify an ID for each process. The process IDs take effect locally and has no influence on packet exchange between routers. Two routers with different process IDs can exchange packets.
Step Command Remarks By default, OSPF is disabled on an interface. Enable an OSPF process on the interface. 3. ospf process-id area area-id [ exclude-subip ] If the specified OSPF process and area do not exist, the command creates the OSPF process and area. Disabling an OSPF process on an interface does not delete the OSPF process or the area.
Configuring an NSSA area A stub area cannot import external routes, but an NSSA area can import external routes into the OSPF routing domain while retaining other stub area characteristics. Do not configure the backbone area as an NSSA area or totally NSSA area. To configure an NSSA area, configure the nssa command on all the routers attached to the area. To configure a totally NSSA area, configure the nssa command on all the routers attached to the area and configure the nssa no-summary command on the ABR.
Step Command Remarks By default, no virtual link is configured. 4. vlink-peer router-id [ dead seconds | hello seconds | { { hmac-md5 | md5 } key-id { cipher cipher-string | plain plain-string } | simple { cipher cipher-string | plain plain-string } } | retransmit seconds | trans-delay seconds ] * Configure a virtual link. Configure this command on both ends of a virtual link, and the hello and dead intervals must be identical on both ends of the virtual link.
Step 3. 4. Command Remarks Configure the OSPF network type for the interface as broadcast. ospf network-type broadcast By default, the network type of an interface depends on the link layer protocol. (Optional.) Configure a router priority for the interface. ospf dr-priority priority The default router priority is 1.
Step Enter interface view. 2. Command Remarks interface interface-type interface-number N/A By default, the network type of an interface depends on the link layer protocol. After you configure the OSPF network type for an interface as P2MP unicast, all packets are unicast over the interface. The interface cannot broadcast hello packets to discover neighbors, so you must manually specify the neighbors. Configure the OSPF network type for the interface as P2MP. ospf network-type p2mp [ unicast ] 4.
Configuring OSPF route summarization Configure route summarization on an ABR or ASBR to summarize contiguous networks into a single network and distribute it to other areas. Route summarization reduces the routing information exchanged between areas and the size of routing tables, and improves routing performance. For example, three internal networks 19.1.1.0/24, 19.1.2.0/24, and 19.1.3.0/24 are available within an area. You can summarize the three networks into network 19.1.0.
Configuring received OSPF route filtering Perform this task to filter routes calculated using received LSAs. The following filtering methods are available: • Use an ACL or IP prefix list to filter routing information by destination address. • Use the gateway keyword to filter routing information by next hop. • Use an ACL or IP prefix list to filter routing information by destination address and at the same time use the gateway keyword to filter routing information by next hop.
value is configured for an interface, OSPF computes the interface cost based on the interface bandwidth and default bandwidth reference value. To configure an OSPF cost for an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure an OSPF cost for the interface. ospf cost value By default, the OSPF cost is calculated according to the interface bandwidth.
Configuring OSPF preference A router can run multiple routing protocols, and each protocol is assigned a preference. If multiple routes are available to the same destination, the one with the highest protocol preference is selected as the best route. To configure OSPF preference: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a preference for OSPF.
To redistribute a default route: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A Redistribute a default route. 3. By default, no default route is redistributed. default-route-advertise [ [ [ always | permit-calculate-other ] | cost cost | route-policy route-policy-name | type type ] * | summary cost cost ] This command is applicable only to VPNs.
• Change the SPF calculation interval to reduce resource consumption caused by frequent network changes. • Configure OSPF authentication to improve security. Configuration prerequisites Before you configure OSPF network optimization, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • Enable OSPF. Configuring OSPF timers An OSPF interface includes the following timers: • Hello timer—Interval for sending hello packets.
Step Command Remarks The default setting is 5 seconds. 6. Specify the retransmission interval. ospf timer retransmit interval A retransmission interval setting that is too small can cause unnecessary LSA retransmissions. This interval is typically set bigger than the round-trip time of a packet between two neighbors. Specifying LSA transmission delay To avoid LSAs from aging out during transmission, set an LSA retransmission delay especially for low speed links.
Specifying the LSA arrival interval If OSPF receives an LSA that has the same LSA type, LS ID, and router ID as the previously received LSA within the LSA arrival interval, OSPF discards the LSA to save bandwidth and route resources. To configure the LSA arrival interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the LSA arrival interval.
To disable interfaces from receiving and sending routing information: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A By default, an OSPF interface can receive and send OSPF packets. 3. Disable interfaces from receiving and sending OSPF packets.
Configuring OSPF area authentication You must configure the same authentication mode and password on all the routers in an area. To configure OSPF area authentication: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enter area view. area area-id N/A • Configure MD5 authentication: 4. Configure area authentication mode.
Step 3. Enable the interface to add its MTU into DD packets. Command Remarks ospf mtu-enable By default, the interface adds an MTU value of 0 into DD packets. Configuring a DSCP value for OSPF packets Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a DSCP value for OSPF packets. dscp dscp-value By default, the DSCP value for OSPF packets is 48.
Enabling compatibility with RFC 1583 RFC 1583 specifies a different method than RFC 2328 for selecting the optimal route to a destination in another AS. When multiple routes are available to the ASBR, OSPF selects the optimal route by using the following procedure: 1. Selects the route with the highest preference: { { If RFC 2328 is compatible with RFC 1583, all these routes have equal preference.
Configure the maximum number of output SNMP notifications within a specified time interval. • SNMP notifications are sent to the SNMP module, which outputs SNMP notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide. To configure OSPF network management: Step Command Remarks 1. Enter system view. system-view N/A 2. Bind OSPF MIB to an OSPF process.
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. To enable OSPF ISPF: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable OSPF ISPF. ispf enable By default, OSPF ISPF is enabled.
Configuring prefix suppression on an interface Interface prefix suppression does not suppress prefixes of secondary IP addresses. To configure interface prefix suppression: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable prefix suppression on the interface. ospf prefix-suppression [ disable ] By default, prefix suppression is disabled on an interface.
Configuring OSPF GR GR ensures forwarding continuity when a routing protocol restarts. 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. OSPF GR has the following types: • IETF GR—Uses Opaque LSAs to implement GR.
Step Command Remarks 4. Enable the out-of-band re-synchronization capability. enable out-of-band-resynchronization By default, the out-of-band re-synchronization capability is disabled. 5. Enable non-IETF GR. graceful-restart [ nonstandard ] [ global | planned-only ] * By default, non-IETF GR capability is disabled. 6. (Optional.) Configure GR interval. graceful-restart interval interval-value The default setting is 120 seconds.
Triggering OSPF GR To trigger OSPF GR, perform the following command in user view: Task Command Trigger OSPF GR. reset ospf [ process-id ] process graceful-restart Configuring BFD for OSPF BFD provides a single mechanism to quickly detect and monitor the connectivity of links between OSPF neighbors, which improves the network convergence speed. For more information about BFD, see High Availability Configuration Guide.
Task Command Display OSPF process information. display ospf [ process-id ] [ verbose ] Display OSPF GR information. display ospf [ process-id ] graceful-restart [ verbose ] Display OSPF LSDB information. display ospf [ process-id ] lsdb [ area area-id | brief | [ { asbr | ase | network | nssa | opaque-area | opaque-as | opaque-link | router | summary } [ link-state-id ] ] [ originate-router advertising-router-id | self-originate ] ] Display OSPF next hop information.
OSPF configuration examples These configuration examples only cover commands for OSPF configuration. Basic OSPF configuration example Network requirements • Enable OSPF on all switches, and split the AS into three areas. • Configure Switch A and Switch B as ABRs. Figure 10 Network diagram Area 0 Switch A Switch B Vlan-int100 10.1.1.1/24 Vlan-int100 10.1.1.2/24 Vlan-int200 10.2.1.1/24 Area 1 Vlan-int200 10.2.1.2/24 Switch C Vlan-int300 10.4.1.1/24 Vlan-int200 10.3.1.1/24 Vlan-int200 10.3.1.
[SwitchB-ospf-1] quit # Configure Switch C. system-view [SwitchC] router id 10.4.1.1 [SwitchC] ospf [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.1] network 10.4.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit # Configure Switch D. system-view [SwitchD] router id 10.5.1.1 [SwitchD] ospf [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.
OSPF Process 1 with Router ID 10.2.1.1 Routing Tables Routing for Network Destination Cost Type NextHop 10.2.1.0/24 1 10.3.1.0/24 2 10.4.1.0/24 2 Stub 10.2.1.2 10.4.1.1 0.0.0.1 10.5.1.0/24 3 Inter 10.1.1.2 10.3.1.1 0.0.0.0 10.1.1.0/24 1 Transit 10.2.1.1 Inter 10.1.1.2 Transit 10.1.1.1 AdvRouter 10.2.1.1 10.3.1.1 Area 0.0.0.1 0.0.0.0 10.2.1.1 0.0.0.0 AdvRouter Area Total Nets: 5 Intra Area: 3 Inter Area: 2 ASE: 0 NSSA: 0 # Display OSPF routing information on Switch D.
• Split the AS into three areas. • Configure Switch A and Switch B as ABRs. • Configure Switch C as an ASBR to redistribute external routes (static routes). Figure 11 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable OSPF (see "Basic OSPF configuration example"). 3. Configure OSPF to redistribute routes: # On Switch C, configure a static route destined for network 3.1.2.0/24. system-view [SwitchC] ip route-static 3.1.2.
10.3.1.0/24 10 Transit 10.3.1.2 10.3.1.1 0.0.0.2 10.4.1.0/24 25 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.5.1.0/24 10 Stub 10.5.1.1 10.5.1.1 0.0.0.2 10.1.1.0/24 12 Inter 10.3.1.1 10.3.1.1 0.0.0.2 Destination Cost Type Tag NextHop AdvRouter 3.1.2.0/24 1 Type2 1 10.3.1.1 10.4.1.
[SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B. system-view [SwitchB] router id 11.2.1.1 [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. system-view [SwitchC] router id 11.1.1.2 [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.
# Configure Switch C. [SwitchC] bgp 100 [SwitchC-bgp] peer 11.1.1.1 as 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] import-route ospf [SwitchC-bgp-ipv4]import-route direct [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit 4. Configure Switch B and Switch C to redistribute BGP routes into OSPF: # Configure OSPF to redistribute routes from BGP on Switch B. [SwitchB] ospf [SwitchB-ospf-1] import-route bgp # Configure OSPF to redistribute routes from BGP on Switch C.
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0 10.0.0.0/8 OSPF 2 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 0 11.2.1.2 Vlan100 11.2.1.0/32 Direct 0 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0 11.2.1.255/32 Direct 0 0 11.2.1.2 Vlan100 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0 224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0 224.0.0.
# Display ABR/ASBR information on Switch C. display ospf abr-asbr OSPF Process 1 with Router ID 10.4.1.1 Routing Table to ABR and ASBR Type Destination Area Cost Nexthop RtType Intra 10.2.1.1 0.0.0.1 3 10.2.1.1 ABR Inter 10.5.1.1 0.0.0.1 7 10.2.1.1 ASBR # Display OSPF routing table on Switch C. display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Tables Routing for Network Destination Cost Type AdvRouter Area 10.2.1.0/24 3 Transit 10.2.1.
OSPF Process 1 with Router ID 10.4.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 4 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 3 Transit 10.2.1.2 10.2.1.1 0.0.0.1 10.3.1.0/24 7 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.4.1.0/24 3 Stub 10.4.1.1 10.4.1.1 0.0.0.1 10.5.1.0/24 17 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.1.1.0/24 5 Inter 10.2.1.1 10.2.1.1 0.0.0.
Figure 14 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. 2. Enable OSPF (see "Basic OSPF configuration example"). 3. Configure Area 1 as an NSSA area: # Configure Switch A. system-view [SwitchA] ospf [SwitchA-ospf-1] area 1 [SwitchA-ospf-1-area-0.0.0.1] nssa default-route-advertise no-summary [SwitchA-ospf-1-area-0.0.0.1] quit [SwitchA-ospf-1] quit # Configure Switch C. system-view [SwitchC] ospf [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.
Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 65536 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 65535 Transit 10.2.1.2 10.4.1.1 0.0.0.1 10.4.1.0/24 3 Stub 10.4.1.1 0.0.0.1 10.4.1.1 Total Nets: 3 Intra Area: 2 4. Inter Area: 1 ASE: 0 NSSA: 0 Configure route redistribution: # Configure Switch C to redistribute static routes. [SwitchC] ip route-static 3.1.3.1 24 10.4.1.
Figure 15 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable OSPF: # Configure Switch A. system-view [SwitchA] router id 1.1.1.1 [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 # Configure Switch B. system-view [SwitchB] router id 2.2.2.2 [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.
[SwitchD-ospf-1] return # Display OSPF neighbor information of Switch A. [SwitchA] display ospf peer verbose OSPF Process 1 with Router ID 1.1.1.1 Neighbors Area 0.0.0.0 interface 192.168.1.1(Vlan-interface1)'s neighbors Router ID: 2.2.2.2 State: 2-Way Address: 192.168.1.2 Mode: None DR: 192.168.1.4 GR State: Normal Priority: 1 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 38 sec Neighbor is up for 00:01:31 Authentication Sequence: [ 0 ] Router ID: 3.3.3.
OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 State: Full Address: 192.168.1.1 Mode:Nbr is DR: 192.168.1.4 Slave GR State: Normal Priority: 100 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 31 sec Neighbor is up for 00:11:17 Authentication Sequence: [ 0 ] Router ID: 2.2.2.2 State: Full Address: 192.168.1.2 Mode:Nbr is DR: 192.168.1.
Router ID: 2.2.2.2 State: 2-Way Address: 192.168.1.2 Mode: None DR: 192.168.1.1 GR State: Normal Priority: 0 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 35 sec Neighbor is up for 00:01:44 Authentication Sequence: [ 0 ] Router ID: 3.3.3.3 State: Full Address: 192.168.1.3 Mode: Nbr is Slave DR: 192.168.1.1 GR State: Normal Priority: 2 BDR: 192.168.1.
Figure 16 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Enable OSPF: # Configure Switch A. system-view [SwitchA] ospf 1 router-id 1.1.1.1 [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit # Configure Switch B. system-view [SwitchB] ospf 1 router-id 2.2.2.2 [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.
[SwitchB] display ospf routing OSPF Process 1 with Router ID 2.2.2.2 Routing Tables Routing for Network Destination Cost Type 10.2.1.0/24 2 10.1.1.0/24 2 NextHop AdvRouter Area Transit 10.2.1.1 3.3.3.3 0.0.0.1 Transit 10.1.1.2 2.2.2.2 0.0.0.0 Total Nets: 2 Intra Area: 2 Inter Area: 0 ASE: 0 NSSA: 0 Area 0 has no direct connection to Area 2, so the routing table of Switch B has no route to Area 2. 3. Configure a virtual link: # Configure Switch B.
Analysis If the physical link and lower layer protocols work well, verify OSPF parameters configured on interfaces. Two neighbors must have the same parameters, such as the area ID, network segment, and mask (a P2P or virtual link can have different network segments and masks). Solution 1. Use the display ospf peer command to verify OSPF neighbor information. 2. Use the display ospf interface command to verify OSPF interface information. 3.
Configuring BGP Overview Border Gateway Protocol (BGP) is an exterior gateway protocol (EGP). It is called internal BGP (IBGP) when it runs within an AS and called external BGP (EBGP) when it runs between ASs. The current version in use is BGP-4 (RFC 4271). BGP has the following characteristics: • Focuses on route control and selection rather than route discovery and calculation. • Uses TCP to enhance reliability.
BGP path attributes BGP uses the following path attributes in update messages for route filtering and selection: • ORIGIN The ORIGIN attribute specifies the origin of BGP routes. This attribute has the following types: { IGP—Has the highest priority. Routes generated in the local AS have the IGP attribute. { EGP—Has the second highest priority. Routes obtained through EGP have the EGP attribute. { • INCOMPLETE—Has the lowest priority. The source of routes with this attribute is unknown.
{ • Filter routes—By using an AS path list, you can filter routes based on AS numbers contained in the AS_PATH attribute. For more information about AS path list, see "Configuring a routing policy." 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.
Figure 19 MED attribute MED = 0 Router B 2.1.1.1 D = 9.0.0.0 Next_hop = 2.1.1.1 MED = 0 EBGP IBGP 9.0.0.0 IBGP Router A D = 9.0.0.0 Next_hop = 3.1.1.1 MED = 100 AS 10 EBGP Router D IBGP 3.1.1.1 Router C MED = 100 AS 20 Generally BGP only compares MEDs of routes received from the same AS. You can also use the compare-different-as-med command to force BGP to compare MED values of routes received from different ASs.
Figure 20 LOCAL_PREF attribute • COMMUNITY The COMMUNITY attribute identifies the community of BGP routes. A BGP community is a group of routes with the same characteristics. It has no geographical boundaries. Routes of different ASs can belong to the same community. A route can carry one or more COMMUNITY attribute values (each of which is represented by a 4-byte integer).
BGP route selection BGP discards routes with unreachable NEXT_HOPs. If multiple routes to the same destination are available, BGP selects the best route in the following sequence: 1. The route with the highest Preferred_value. 2. The route with the highest LOCAL_PREF. 3. The route generated by the network command, the route redistributed by the import-route command, or the summary route in turn. 4. The route with the shortest AS_PATH. 5. The IGP, EGP, or INCOMPLETE route in turn. 6.
the same number of next hops to forward packets. BGP load balancing based on route recursion is always enabled by the system rather than configured by using commands. • BGP load balancing through route selection. IGP routing protocols, such as RIP and OSPF, compute the metrics of routes, and implement load balancing over the routes with the same metric and to the same destination. The route selection criterion is metric.
The system supports both manual and automatic route summarization. Manual route summarization allows you to determine the attribute of a summary route and whether to advertise more specific routes. • Route dampening Route frapping (a route comes up and disappears in the routing table frequently) causes BGP to send many routing updates. It can consume too many resources and affect other operations. In most cases, BGP runs in complex networks where route changes are more frequent.
Using route reflectors can solve this issue. In an AS, a router acts as a route reflector, and other routers act as clients connecting to the route reflector. The route reflector forwards routing information received from a client to other clients. In this way, all clients can receive routing information from one another without establishing BGP sessions.
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 25, intra-confederation EBGP connections are established between sub-ASs in AS 200. Figure 25 Confederation network diagram A non-confederation BGP speaker does not need to know sub-ASs in the confederation. It considers the confederation as one AS, and the confederation ID as the AS number.
Address family MP-BGP uses address families and subsequent address families to identify different network layer protocols for routes contained in the MP_REACH_NLRI and MP_UNREACH_NLRI attributes. For example, an Address Family Identifier (AFI) of 2 and a Subsequent Address Family Identifier (SAFI) of 1 identify IPv6 unicast routing information carried in the MP_REACH_NLRI attribute. For address family values, see RFC 1700.
View names Ways to enter the views Remarks system-view [Sysname] bgp 100 BGP-VPN IPv6 unicast address family view [Sysname-bgp] ip vpn-instance vpn1 [Sysname-bgp-vpn1] address-family ipv6 unicast Configurations in this view are effective for IPv6 unicast routes and peers in the specified VPN instance.
Tasks at a glance Remarks Generating BGP routes (perform at least one of the following tasks): • Injecting a local network • Redistributing IGP routes N/A (Optional.) Controlling route distribution and reception: • • • • • • Configuring BGP route summarization Advertising optimal routes in the IP routing table Advertising a default route to a peer or peer group N/A Limiting routes received from a peer or peer group Configuring BGP route filtering policies Configuring BGP route dampening (Optional.
Tasks at a glance Remarks Configuring basic BGP: • (Required.) Enabling BGP • (Required.) Perform one of the following tasks: { Configuring a BGP peer { Configuring a BGP peer group • (Optional.) Specifying the source interface for TCP connections HP recommends that you configure BGP peer groups on large scale BGP networks for easy configuration and maintenance.
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 of a local loopback interface as the router ID. • If no router ID is specified in BGP view, the global router ID is used.
Configuring a BGP peer Configuring an IPv4 BGP peer Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Create an IPv4 BGP peer and specify its AS number. peer ip-address as-number as-number By default, no IPv4 BGP peer is created. 4. (Optional.) Configure a description for a peer.
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. A peer group is an IBGP peer group if peers in it belong to the local AS, and is an EBGP peer group if peers in it belong to different ASs.
Step Command Remarks • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Create an IBGP peer group. 3. group group-name [ internal ] By default, no IBGP peer group is created. By default, no peer exists in the peer group. 4. Add a peer into the IBGP peer group. peer ipv6-address group group-name [ as-number as-number ] 5. (Optional.) Configure a description for a peer group.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Create an EBGP peer group. Specify the AS number for the group. group group-name external peer group-name as-number as-number By default, no EBGP peer group is created. By default, no AS number is specified. If a peer group contains peers, you cannot remove or change its AS number.
Step Command Remarks By default, no peer exists in the peer group. 5. Add a peer into the EBGP peer group. peer ipv6-address group group-name [ as-number as-number ] 6. (Optional.) Configure a description for a peer group. peer group-name description description-text By default, no description is configured for the peer group. 7. Create the BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family and enter its view.
To configure an EBGP peer group by using Method 2 (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Create an EBGP peer group. group group-name external By default, no EBGP peer group is created. 4. Create an IPv6 BGP peer and specify its AS number.
Step 6. 7. Command Remarks Create the BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family and enter its view. address-family ipv4 [ unicast ] By default, the BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family is not created. Enable the router to exchange IPv4 unicast routing information with peers in the specified peer group. peer group-name enable By default, the router cannot exchange IPv4 unicast routing information with the peers.
• 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 TCP connections to each peer on the local router.
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. The specified network must be available and active in the local IP routing table. To inject a local network (IPv4): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2.
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 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b.
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. Therefore, a summary route must not be an optimal route on the originating router.
Step 3. 4. Command Remarks Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Create a summary route in the BGP routing table. aggregate ip-address { mask | mask-length } [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] * By default, no summary route is configured.
Step Enter system view. 1. Command Remarks system-view N/A • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Advertise a default route to a peer or peer group.
Step Enter system view. 1. Command Remarks system-view N/A • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Specify the maximum number of routes that a router can receive from a peer or peer group.
Use a routing policy, ACL, AS path list, or prefix list to filter routing information advertised to a peer or peer group. • If you configure multiple filtering policies, apply them in the following sequence: 1. filter-policy export 2. peer filter-policy export 3. peer as-path-acl export 4. peer prefix-list export 5. peer route-policy export Only routes passing all the configured policies can be advertised. To configure BGP route distribution filtering policies (IPv4): Step 1. Enter system view.
Step Command Remarks • Reference an ACL or IP prefix list to filter advertised BGP routes: filter-policy { acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ip-address } route-policy route-policy-name export 4. Configure BGP route distribution filtering policies.
Step Command Remarks • Reference an ACL or IPv6 prefix list to filter advertised BGP routes: filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ direct | isisv6 process-id | ospfv3 process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv6-address } route-policy route-policy-name export 4. Configure BGP route distribution filtering policies.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view.
Step 3. Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. Command Remarks address-family ipv6 [ unicast ] N/A • Reference ACL or IPv6 prefix list to filter BGP routes received from all peers: filter-policy { acl6-number | prefix-list ipv6-prefix-name } import • Reference a routing policy to filter BGP routes received from a peer or peer group: peer { group-name | ipv6-address } route-policy route-policy-name import 4.
Step 4. Configure BGP route dampening. Command Remarks dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] * By default, BGP route dampening is not configured. To configure BGP route dampening (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4.
Step 3. 4. Command Remarks Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Specify a preferred value for routes received from a peer or peer group. peer { group-name | ip-address } preferred-value value The default preferred value is 0. To specify a preferred value for routes from a peer or peer group (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A 4. Configure preferences for EBGP, IBGP, and local BGP routes.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Configure the default local preference. default local-preference value The default local preference is 100.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. address-family ipv4 [ unicast ] N/A Configure the default MED value. default med med-value The default MED value is 0. To configure the default MED value (IPv6): Step 1. Enter system view.
Step Enable MED comparison for routes from different ASs. 4. Command Remarks compare-different-as-med By default, this feature is disabled. To enable MED comparison for routes from different ASs (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A 4. Enable MED comparison for routes from different ASs.
* i 3.3.3.3 50 0 200e However, Router C and Router A reside in the same AS, and Router C has a greater MED, so network 10.0.0.0 learned from Router C should not be optimal. You can configure the bestroute compare-med command to enable MED comparison for routes from the same AS on Router D. After that, Router D puts the routes received from each AS into a group, selects the route with the lowest MED from each group, and compares routes from different groups.
not belong to the confederation, BGP does not compare it with other routes. As a result, the first route becomes the optimal route. To enable MED comparison for routes from confederation peers (IPv4): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4.
Figure 27 NEXT_HOP attribute configuration If a BGP router has two peers on a broadcast network, it does not set itself as the next hop for routes sent to an EBGP peer by default. As shown in Figure 28, Router A and Router B establish an EBGP neighbor relationship, and Router B and Router C establish an IBGP neighbor relationship. They are on the same broadcast network 1.1.1.0/24. When Router B sends EBGP routes to Router A, it does not set itself as the next hop by default.
To configure the NEXT_HOP attribute (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A peer { group-name | ipv6-address } next-hop-local By default, the router sets itself as the next hop for routes sent to an EBGP peer or peer group, but does not set itself as the next hop for routes sent to an IBGP peer or peer group. 4.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A Permit the local AS number to appear in routes from a peer or peer group and specify the appearance times.
Step 3. 4. Command Remarks Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A Disable BGP from considering AS_PATH during best route selection. bestroute as-path-neglect By default, BGP considers AS_PATH during best route selection.
Configuring AS number substitution IMPORTANT: Do not configure AS number substitution in normal circumstances. Otherwise, routing loops might occur. To use BGP between PE and CE in MPLS L3VPN, VPN sites in different geographical areas should have different AS numbers. Otherwise, BGP discards route updates containing the local AS number.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Configure AS number substitution for a peer or peer group. peer { group-name | ipv6-address } substitute-as By default, AS number substitution is not configured.
Step Command Configure BGP to remove private AS numbers from the AS_PATH attribute of updates sent to an EBGP peer or peer group. 4. peer { group-name | ipv6-address } public-as-only Remarks By default, this feature is not configured. This command is only applicable to EBGP peers or peer groups. Ignoring the first AS number of EBGP route updates By default, BGP checks whether the first AS number in the AS_PATH attribute of a route update received from a peer is the AS number of that peer.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name Use either method. • Configure the global keepalive interval and hold time: timer keepalive keepalive hold holdtime 3. Configure the keepalive interval and hold time.
this situation, perform this task to configure the interval for sending updates for the same route to a peer or peer group. To configure the interval for sending the same update to a peer or peer group (IPv4): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. Enable BGP to establish an EBGP session to an indirectly-connected peer or peer group and specify the maximum hop count. peer { group-name | ip-address } ebgp-max-hop [ hop-count ] By default, BGP cannot establish an EBGP session to an indirectly-connected peer or peer group.
Enabling 4-byte AS number suppression BGP supports 4-byte AS numbers. The 4-byte AS number occupies four bytes, in the range of 1 to 4294967295. By default, a device sends an Open message to the peer device for session establishment. The Open message indicates that the device supports 4-byte AS numbers. If the peer device supports 2-byte AS numbers instead of 4-byte AS numbers, the session cannot be established. To resolve this issue, enable the 4-byte AS number suppression function.
Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number Use either method. b. ip vpn-instance vpn-instance-name 3. Enable MD5 authentication for a BGP peer group or peer. peer { group-name | ip-address } password { cipher | simple } password By default, MD5 authentication is disabled. To enable MD5 authentication for BGP peers (IPv6): Step 1. Enter system view.
To specify the maximum number of BGP ECMP routes for load balancing (IPv6): Step 1. Enter system view. Command Remarks system-view N/A • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv6 unicast address family view or BGP-VPN IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A Specify the maximum number of BGP ECMP routes for load balancing.
Step Disable BGP to establish a session to a peer or peer group. 3. Command Remarks peer { group-name | ipv6-address } ignore By default, BGP can establish a session to a peer. Configuring BGP soft-reset After you modify the route selection policy (for example, modify the preferred value), you must reset BGP sessions to apply the new policy. The reset operation tears down and re-establishes BGP sessions.
Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address } capability-advertise route-refresh 3. Enable BGP route refresh for a peer or peer group. • Enable BGP route refresh and multi-protocol extension capability for the specified peer or peer group: undo peer { group-name | ip-address } capability-advertise conventional Use either method. By default, BGP route refresh is enabled.
Step Command Remarks • Enter BGP view: bgp as-number 2. Enter BGP view or BGP-VPN instance view. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name 3. 4. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. Save all route updates from the peer or peer group. address-family ipv4 [ unicast ] peer { group-name | ip-address } keep-all-routes N/A By default, the routes are not saved.
Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address } capability-advertise route-refresh 3. 4. 5. Enable BGP route refresh for a peer or peer group. • Enable BGP route refresh and Return to user view. return N/A Perform manual soft-reset.
Step Command Remarks 5. refresh bgp { ipv6-address | all | external | group group-name | internal } { export | import } ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] N/A Perform manual soft-reset. Protecting an EBGP peer when memory usage reaches level 2 threshold Memory usage includes the following threshold levels: normal, level 1, level 2, and level 3.
Configuring a large-scale BGP network In a large network, the number of BGP connections is huge and BGP configuration and maintenance are complicated. To simply BGP configuration, you can use the peer group, community, route reflector, and confederation features as needed. For more information about configuring peer groups, see "Configuring a BGP peer group." Configuring BGP community By default, a router does not advertise the COMMUNITY or extended community attribute to its peers or peer groups.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ] N/A • Advertise the COMMUNITY 4. 5. Advertise the COMMUNITY or extended community attribute to a peer or peer group. (Optional.) Apply a routing policy to routes advertised to a peer or peer group.
Step Command Remarks 5. Enable route reflection between clients. reflect between-clients By default, route reflection between clients is enabled. 6. (Optional.) Configure the cluster ID of the route reflector. reflector cluster-id { cluster-id | ip-address } By default, a route reflector uses its own router ID as the cluster ID. To configure a BGP route reflector (IPv6): Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3.
Step Enter system view. 1. Command Remarks system-view N/A • Enter BGP view: bgp as-number Enter BGP view or BGP-VPN instance view. 2. • Enter BGP-VPN instance view: a. bgp as-number N/A b. ip vpn-instance vpn-instance-name By default, BGP does not ignore the ORIGINATOR_ID attribute. Ignore the ORIGINATOR_ID attribute. 3. peer { group-name | ipv6-address } ignore-originatorid Make sure this command does not result in a routing loop.
To configure confederation compatibility: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enable confederation compatibility. confederation nonstandard By default, confederation compatibility is disabled. Configuring BGP GR GR ensures forwarding continuous when a routing protocol restarts or an active/standby switchover occurs. Two routers are required to complete a GR process.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enable GR capability for BGP. graceful-restart By default, GR capability is disabled for BGP. The default setting is 150 seconds. 4. Configure the GR timer. graceful-restart timer restart timer 5. Configure the maximum time to wait for the End-of-RIB marker. graceful-restart timer wait-for-rib timer The time that a peer waits to reestablish a session must be less than the hold time.
Step 3. Enable the logging of session state changes globally. Command Remarks log-peer-change By default, logging of session state changes is enabled globally. Configuring BFD for BGP IMPORTANT: If you have enabled GR, use BFD with caution because BFD might detect a failure before the system performs GR, which will result in GR failure. If you have enabled both BFD and GR for BGP, do not disable BFD during a GR process to avoid GR failure.
Displaying and maintaining BGP Execute display commands in any view and reset commands in user view (IPv4). Task Command Display BGP IPv4 unicast peer group information. display bgp group ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ group-name ] Display BGP IPv4 unicast peer or peer group information. display bgp peer ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ ip-address { log-info | verbose } | group-name log-info | verbose ] Display BGP IPv4 unicast routing information.
Task Command Clear dampened BGP IPv4 unicast routing information and release suppressed routes. reset bgp dampening ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ network-address [ mask | mask-length ] ] Clear BGP IPv4 unicast route flap information. reset bgp flap-info ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ network-address [ mask | mask-length ] | as-path-acl as-path-acl-number | peer peer-address ] Execute display commands in any view and reset commands in user view (IPv6).
Task Command Display the outgoing label of BGP IPv6 unicast routing information. display bgp routing-table ipv6 [ unicast ] outlabel Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp network ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] Display BGP path attribute information. display bgp paths [ as-regular-expression ] Display BGP IPv6 unicast address family update group information.
BGP connections. Enable OSPF in AS 65009 to make sure that Switch B can communicate with Switch C through loopback interfaces. The EBGP peers, Switch A and Switch B (usually belong to different carriers), are located in different ASs. Typically, their loopback interfaces are not reachable to each other, so directly connected interfaces are used for establishing BGP sessions. To enable Switch C to access the network 8.1.1.0/24 connected directly to Switch A, inject network 8.1.1.
Peer 2.2.2.2 AS MsgRcvd 65009 2 MsgSent OutQ PrefRcv Up/Down 2 0 State 0 00:00:13 Established The output shows that Switch C has established an IBGP peer relationship with Switch B. 3. Configure EBGP: # Configure Switch A. system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 3.1.1.1 as-number 65009 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 3.1.1.1 enable [SwitchA-bgp-ipv4] network 8.1.1.
* > 8.1.1.0/24 8.1.1.1 0 32768 i # Display the BGP routing table on Switch B. [SwitchB] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 2.2.2.2 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network * >e 8.1.1.0/24 NextHop MED 3.1.1.2 0 LocPrf PrefVal Path/Ogn 0 65008i # Display the BGP routing table on Switch C.
Network NextHop MED LocPrf PrefVal Path/Ogn * >e 2.2.2.2/32 3.1.1.1 0 0 65009? * >e 3.1.1.0/24 3.1.1.1 0 0 65009? * > 8.1.1.0/24 8.1.1.1 0 32768 i * >e 9.1.1.0/24 3.1.1.1 0 0 65009? Two routes, 2.2.2.2/32 and 9.1.1.0/24, have been added in Switch A's routing table. # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 4 BGP local router ID is 3.3.3.
Figure 31 Network diagram Configuration considerations Configure BGP to redistribute routes from OSPF on Switch B, so Switch A can obtain the route to 9.1.2.0/24. Configure OSPF to redistribute routes from BGP on Switch B, so Switch C can obtain the route to 8.1.1.0/24. Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure OSPF: Enable OSPF in AS 65009, so Switch B can obtain the route to 9.1.2.0/24. # Configure Switch B.
# Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 3.1.1.2 enable 4. Configure BGP and IGP route redistribution: # Configure route redistribution between BGP and OSPF on Switch B.
Verifying the configuration # Use ping for verification. [SwitchA] ping -a 8.1.1.1 9.1.2.1 Ping 9.1.2.1 (9.1.2.1) from 8.1.1.1: 56 data bytes, press CTRL_C to break 56 bytes from 9.1.2.1: icmp_seq=0 ttl=254 time=10.000 ms 56 bytes from 9.1.2.1: icmp_seq=1 ttl=254 time=12.000 ms 56 bytes from 9.1.2.1: icmp_seq=2 ttl=254 time=2.000 ms 56 bytes from 9.1.2.1: icmp_seq=3 ttl=254 time=7.000 ms 56 bytes from 9.1.2.1: icmp_seq=4 ttl=254 time=9.000 ms --- Ping statistics for 9.1.2.
Figure 32 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure static routing between Switch A and Switch B: # Configure a default route with the next hop 192.168.212.1 on Switch A. system-view [SwitchA] ip route-static 0.0.0.0 0 192.168.212.1 # Configure static routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 with the same next hop 192.168.212.161 on Switch B. system-view [SwitchB] ip route-static 192.
Summary Count : 5 OSPF Routing table Status : Summary Count : 3 Destination/Mask Proto Pre Cost NextHop Interface 192.168.64.0/24 OSPF 150 1 172.17.100.1 Vlan100 192.168.74.0/24 OSPF 150 1 172.17.100.1 Vlan100 192.168.99.0/24 OSPF 150 1 172.17.100.1 Vlan100 OSPF Routing table Status : Summary Count : 2 Destination/Mask Proto Pre Cost NextHop Interface 10.220.2.0/24 OSPF 10 1 10.220.2.16 Vlan200 172.17.100.0/24 OSPF 10 1 172.17.100.
192.168.99.0/24 BGP 255 1 10.220.2.16 Vlan200 BGP Routing table Status : Summary Count : 0 The output shows that Switch D has learned routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 through BGP. After the above configurations, ping hosts on networks 192.168.74.0/24, 192.168.99.0/24, and 192.168.64.0/18 from Switch D. The ping operations succeed. 5. Configure route summarization on Switch C to summarize 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.
Figure 33 Network diagram Configuration considerations On Switch A, establish EBGP connections with Switch B and Switch C. Configure BGP to advertise network 8.1.1.0/24 to Switch B and Switch C, so that Switch B and Switch C can access the internal network connected to Switch A. On Switch B, establish an EBGP connection with Switch A and an IBGP connection with Switch C. Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet through Switch B.
[SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] peer 3.3.3.3 as-number 65009 [SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 3.1.1.2 enable [SwitchB-bgp-ipv4] peer 3.3.3.3 enable [SwitchB-bgp-ipv4] network 9.1.1.0 24 [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit [SwitchB] ip route-static 3.3.3.3 32 9.1.1.2 # Configure Switch C.
Because Switch A has two routes to reach AS 65009, configuring load balancing over the two BGP routes on Switch A can improve link usage. # Configure Switch A. [SwitchA] bgp 65008 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] balance 2 [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit Verifying the configuration # Display the BGP routing table on Switch A. [SwitchA] display bgp routing-table ipv4 Total number of routes: 3 BGP local router ID is 1.1.1.
Figure 34 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure EBGP: # Configure Switch A. system-view [SwitchA] bgp 10 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 200.1.2.2 as-number 20 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 enable [SwitchA-bgp-ipv4] network 9.1.1.0 255.255.255.0 [SwitchA-bgp] quit # Configure Switch B. system-view [SwitchB] bgp 20 [SwitchB-bgp] router-id 2.2.
[SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1) Relay nexthop : 200.1.2.1 Original nexthop: 200.1.2.1 OutLabel : NULL AS-path : 10 Origin : igp Attribute value : pref-val 0 State : valid, external, best, # Display advertisement information of network 9.1.1.0 on Switch B. [SwitchB] display bgp routing-table ipv4 9.1.1.
[SwitchA-route-policy-comm_policy-0] quit # Apply the routing policy. [SwitchA] bgp 10 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 route-policy comm_policy export [SwitchA-bgp-ipv4] peer 200.1.2.2 advertise-community Verifying the configuration # Display the routing table on Switch B. [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 200.1.2.
• Between Switch A and Switch B is an EBGP connection, between Switch C and Switch B, and between Switch C and Switch D are IBGP connections. • Switch C is a route reflector with clients Switch B and D. • Switch D can learn route 20.0.0.0/8 from Switch C. Figure 35 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure BGP connections: # Configure Switch A. system-view [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.
[SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 193.1.1.2 as-number 200 [SwitchC-bgp] peer 194.1.1.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 193.1.1.2 enable [SwitchC-bgp-ipv4] peer 194.1.1.2 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Configure Switch D. system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] peer 194.1.1.1 as-number 200 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 194.1.1.
Network i 20.0.0.0 NextHop MED LocPrf PrefVal Path/Ogn 193.1.1.2 0 100 0 100i Switch D has learned route 20.0.0.0/8 from Switch C. BGP confederation configuration example Network requirements As shown in Figure 36, to reduce IBGP connections, AS 200 is split into three sub-ASs: AS65001, AS65002, and AS65003. Switches in AS65001 are fully meshed.
[SwitchA-bgp-ipv4] peer 10.1.1.2 enable [SwitchA-bgp-ipv4] peer 10.1.2.2 enable [SwitchA-bgp-ipv4] peer 10.1.1.2 next-hop-local [SwitchA-bgp-ipv4] peer 10.1.2.2 next-hop-local [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch B. system-view [SwitchB] bgp 65002 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] confederation id 200 [SwitchB-bgp] confederation peer-as 65001 65003 [SwitchB-bgp] peer 10.1.1.1 as-number 65001 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 10.
[SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 10.1.3.1 enable [SwitchD-bgp-ipv4] peer 10.1.5.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit # Configure Switch E. system-view [SwitchE] bgp 65001 [SwitchE-bgp] router-id 5.5.5.5 [SwitchE-bgp] confederation id 200 [SwitchE-bgp] peer 10.1.4.1 as-number 65001 [SwitchE-bgp] peer 10.1.5.1 as-number 65001 [SwitchE-bgp] address-family ipv4 unicast [SwitchE-bgp-ipv4] peer 10.1.4.1 enable [SwitchE-bgp-ipv4] peer 10.1.5.
* >i 9.1.1.0/24 10.1.1.1 0 100 0 (65001) 100i [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 65002 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 10.1.1.1 (1.1.1.1) Relay nexthop : 10.1.1.1 Original nexthop: 10.1.1.1 OutLabel : NULL AS-path : (65001) 100 Origin : igp Attribute value : MED 0, localpref 100, pref-val 0, pre 255 State : valid, external-confed, best, # Display the BGP routing table on Switch D.
The output indicates the following: • Switch F can send route information to Switch B and Switch C through the confederation by establishing only an EBGP connection with Switch A. • Switch B and Switch D are in the same confederation, but belong to different sub-ASs. They obtain external route information from Switch A and generate identical BGP route entries although they have no direct connection in between.
[SwitchC] ospf [SwitchC-ospf] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. system-view [SwitchD] ospf [SwitchD-ospf] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] quit 3.
[SwitchD-bgp] peer 194.1.1.2 as-number 200 [SwitchD-bgp] peer 195.1.1.2 as-number 200 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 194.1.1.2 enable [SwitchD-bgp-ipv4] peer 195.1.1.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit 4. Configure attributes for route 1.0.0.0/8, making Switch D give priority to the route learned from Switch C: { (Method 1.) Configure a higher MED value for the route 1.0.0.0/8 advertised from Switch A to peer 192.1.1.
Route 1.0.0.0/8 is the optimal. { (Method 2.) Configure different local preferences on Switch B and C for route 1.0.0.0/8, making Switch D give priority to the route from Switch C: # Define an ACL numbered 2000 on Switch C, permitting route 1.0.0.0/8. [SwitchC] acl number 2000 [SwitchC-acl-basic-2000] rule permit source 1.0.0.0 0.255.255.255 [SwitchC-acl-basic-2000] quit # Configure a routing policy named localpref on Switch C, setting the local preference of route 1.0.0.0/8 to 200 (the default is 100).
Figure 38 Network diagram Configuration procedure 1. Configure Switch A: # Configure IP addresses for interfaces. (Details not shown.) # Configure the EBGP connection. system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 200.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchA-bgp] graceful-restart # Inject network 8.0.0.0/8 to the BGP routing table. [SwitchA-bgp] address-family ipv4 [SwitchA-bgp-ipv4] network 8.0.0.
system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 9.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchC-bgp] graceful-restart # Enable Switch C to exchange IPv4 unicast routing information with Switch B. [SwitchC-bgp-ipv4] peer 9.1.1.1 enable Verifying the configuration Ping Switch C on Switch A. Meanwhile, perform an active/standby switchover on Switch B. The ping operation is successful during the whole switchover process.
Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure OSPF to make sure that Switch A and Switch C are reachable to each other. (Details not shown.) 3. Configure BGP on Switch A: # Establish two IBGP connections to Switch C. system-view [SwitchA] bgp 200 [SwitchA-bgp] peer 3.0.2.2 as-number 200 [SwitchA-bgp] peer 2.0.2.2 as-number 200 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 3.0.2.2 enable [SwitchA-bgp-ipv4] peer 2.0.2.
[SwitchC-bgp-ipv4] peer 3.0.1.1 enable [SwitchC-bgp-ipv4] peer 2.0.1.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Enable BFD for peer 3.0.1.1. [SwitchC-bgp] peer 3.0.1.1 bfd [SwitchC-bgp] quit [SwitchC] quit Verifying the configuration # Display detailed BFD session information on Switch C. display bfd session verbose Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 513 Source IP: 3.0.2.
Protocol: BGP Process ID: 0 SubProtID: 0x1 Cost: 50 Tag: 0 OrigTblID: 0x1 TableID: 0x2 NBRID: 0x15000001 AttrID: 0x1 Age: 00h00m09s Preference: 255 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 3.0.1.1 Flags: 0x10060 OrigNextHop: 3.0.1.1 Label: NULL RealNextHop: 3.0.2.1 BkLabel: NULL Tunnel ID: Invalid BkTunnel ID: Invalid BkNextHop: N/A Interface: Vlan-interface101 BkInterface: N/A The output shows that Switch C communicates with network 1.1.1.
Figure 40 Network diagram Configuration procedure 1. Configure IP addresses for interfaces. (Details not shown.) 2. Configure IBGP: # Configure Switch B. system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 9::2 as-number 65009 [SwitchB-bgp] address-family ipv6 [SwitchB-bgp-ipv6] peer 9::2 enable [SwitchB-bgp-ipv6] quit # Configure Switch C. system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.
# Configure Switch B. [SwitchB-bgp-ipv6] network 10:: 64 [SwitchB-bgp-ipv6] network 9:: 64 [SwitchB-bgp-ipv6] quit [SwitchB-bgp] quit # Configure Switch C. [SwitchC-bgp-ipv6] network 9:: 64 [SwitchC-bgp-ipv6] quit [SwitchC-bgp] quit Verifying the configuration # Display IPv6 BGP peer information on Switch B. [SwitchB] display bgp peer ipv6 BGP local router ID: 2.2.2.
PrefVal : 0 MED OutLabel : NULL : 0 Path/Ogn: 65009i * > Network : 50:: PrefixLen : 64 NextHop : :: LocPrf : PrefVal : 32768 OutLabel : NULL MED : 0 Path/Ogn: i The output shows that Switch A has learned routing information of AS 65009. # Display IPv6 BGP routing table information on Switch C. [SwitchC] display bgp routing-table ipv6 Total number of routes: 4 BGP local router ID is 3.3.3.
IPv6 BGP route reflector configuration example Network requirements In Figure 41, run EBGP between Switch A and Switch B, run IBGP between Switch C and Switch B, and between Switch C and Switch D. Switch C is a route reflector with clients Switch B and D. Figure 41 Network diagram Configuration procedure 1. Configure IPv6 addresses for interfaces and IPv4 addresses for loopback interfaces. (Details not shown.) 2.
[SwitchB-bgp] quit # Configure Switch C. system-view [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 101::2 as-number 200 [SwitchC-bgp] peer 102::2 as-number 200 [SwitchC-bgp] address-family ipv6 [SwitchC-bgp-ipv6] peer 101::2 enable [SwitchC-bgp-ipv6] peer 102::2 enable [SwitchC-bgp-ipv6] network 101:: 96 [SwitchC-bgp-ipv6] network 102:: 96 # Configure Switch D. system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.
* >i Network : 101:: PrefixLen : 96 NextHop : 102::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL MED : 0 Path/Ogn: i * > Network : 102:: PrefixLen : 96 NextHop : :: LocPrf : PrefVal : 32768 OutLabel : NULL MED : 0 Path/Ogn: i * i Network : 102:: PrefixLen : 96 NextHop : 102::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL MED : 0 Path/Ogn: i The output shows that Switch D has learned the network 1::/64 from Switch C through route reflection.
Switch B Vlan-int200 2000::1/64 Vlan-int100 3000::2/64 Vlan-int101 3001::2/64 Switch D Vlan-int201 2001::3/64 Vlan-int200 2000::2/64 Vlan-int201 2001::2/64 Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2. Configure OSPFv3 so that Switch A and Switch C can reach each other. (Details not shown.) 3. Configure IPv6 BGP on Switch A: # Establish two IBGP connections to Switch C. system-view [SwitchA] bgp 200 [SwitchA-bgp] router-id 1.1.1.
[SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 3000::1 as-number 200 [SwitchC-bgp] peer 2000::1 as-number 200 [SwitchC-bgp] address-family ipv6 [SwitchC-bgp-ipv6] peer 3000::1 enable [SwitchC-bgp-ipv6] peer 2000::1 enable [SwitchC-bgp-ipv6] quit # Enable BFD for peer 3001::1. [SwitchC-bgp] peer 3000::1 bfd [SwitchC-bgp] quit [SwitchC] quit Verifying the configuration # Display detailed BFD session information on Switch C.
Summary Count : 1 Destination: 1200::/64 Protocol: BGP4+ SubProtID: 0x1 Cost: 50 Tag: 0 OrigTblID: 0x1 TableID: 0xa NBRID: 0x25000001 AttrID: 0x1 Process ID: 0 Age: 00h01m07s Preference: 255 State: Active Adv OrigVrf: default-vrf OrigAs: 0 LastAs: 0 Neighbor: 3000::1 Flags: 0x10060 OrigNextHop: 3000::1 Label: NULL RealNextHop: FE80::20C:29FF:FE4A:3873 BkLabel: NULL Tunnel ID: Invalid BkTunnel ID: Invalid BkNextHop: N/A Interface: Vlan-interface101 BkInterface: N/A The output shows that Switch C comm
Troubleshooting BGP Symptom Display BGP peer information by using the display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command. The state of the connection to a peer cannot become established. Analysis To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange Open messages successfully. Solution 1. Use the display current-configuration command to verify the current configuration, and verify that the peer's AS number is correct. 2.
Configuring PBR Introduction to PBR Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: 1. The device uses PBR to forward matching packets. 2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets. 3.
Relationship between the match mode and clauses on the node Does a packet match all the if-match clauses on the node? Match mode Permit Deny • If the node is configured with an apply clause, PBR executes the apply clause on the node. • If PBR successfully guides the forwarding of the packet, PBR does not match the packet against the next node. Yes. The packet is forwarded according to the routing table.
Step Command Remarks 2. Enter policy node view. policy-based-route policy-name [ deny | permit ] node node-number N/A 3. Configure an ACL match criterion. if-match acl acl-number{ acl-number | name acl-name } By default, no ACL match criterion is configured. NOTE: An ACL match criterion uses the specified ACL to match packets regardless of the permit or deny action and the time range of the ACL. If the specified ACL does not exist, no packet can match the criterion.
Configuring interface PBR Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of packets received on the interface. The specified policy must already exist. Otherwise, the interface PBR configuration fails. You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface. You can apply a policy to multiple interfaces. To configure interface PBR: Step Command Remarks 1. Enter system view.
Figure 43 Network diagram Switch B Switch A Vlan-int10 1.1.2.1/24 Vlan-int10 1.1.2.2/24 Vlan-int20 1.1.3.1/24 Vlan-int20 1.1.3.2/24 Switch C Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20. system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20. [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ip address 1.1.2.
[SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IP address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ip address 1.1.3.2 24 Verifying the configuration # Telnet to Switch B on Switch A. The operation succeeds. # Telnet to Switch C on Switch A. The operation fails. # Ping Switch C from Switch A. The operation succeeds. Telnet uses TCP and ping uses ICMP. The preceding results show that all TCP packets sent from Switch A are forwarded to the next hop 1.1.
[SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20. [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ip address 1.1.2.1 24 [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.3.1 24 [SwitchA-Vlan-interface20] quit # Configure ACL 3101 to match TCP packets.
Verifying the configuration # Configure the IP address 10.110.0.20/24 for Host A, and specify its gateway address as 10.110.0.10. # On Host A, Telnet to Switch B that is directly connected to Switch A. The operation succeeds. # On Host A, Telnet to Switch C that is directly connected to Switch A. The operation fails. # Ping Switch C from Host A. The operation succeeds. Telnet uses TCP and ping uses ICMP.
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.
two routers for protocols, such as routing protocols. For more information about BFD, see High Availability Configuration Guide. IMPORTANT: Enabling BFD for a flapping route could worsen the situation. Bidirectional control mode To use BFD bidirectional control detection between two devices, enable BFD control mode for each device's static route destined to the peer.
Single-hop echo mode With BFD echo mode enabled for a static route, the output interface sends BFD echo packets to the destination device, which loops the packets back to test the link reachability. IMPORTANT: Do not use BFD for a static route with the output interface in spoofing state. To configure BFD echo mode for an IPv6 static route: Step 1. Enter system view. Command Remarks system-view N/A By default, the source address of echo packets is not configured. 2.
IPv6 static routing configuration examples Basic IPv6 static route configuration example Network requirements As shown in Figure 45, configure IPv6 static routes so that hosts can reach one another. Figure 45 Network diagram Host B 2::2/64 Vlan-int400 2::1/64 Vlan-int200 4::2/64 Vlan-int300 5::2/64 Switch B Vlan-int200 4::1/64 Vlan-int300 5::1/64 Vlan-int100 1::1/64 Host A 1::2/64 Vlan-int500 3::1/64 Switch C Switch A Host C 3::2/64 Configuration procedure 1.
Destination: :: Protocol NextHop : 4::2 Preference: 60 : Static Interface : Vlan-interface200 Cost : 0 Destination: 1::/64 Protocol : Static NextHop : 4::1 Preference: 60 Interface : Vlan-interface200 Cost : 0 Destination: 3::/64 Protocol : Static NextHop : 5::1 Preference: 60 Interface : Vlan-interface300 Cost Static Routing table Status : Summary Count : 0 # Display the IPv6 static route information on Switch B.
Figure 46 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int10 12::1/64 Switch B Vlan-int10 12::2/64 Vlan-int11 10::102/64 Vlan-int13 13::1/64 Switch C Vlan-int11 10:: 100/64 Vlan-int13 13::2/64 Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2.
Verifying the configuration # Display the BFD sessions on Switch A.
The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for IPv6 static routes configuration example (indirect next hop) Network requirements In Figure 47, Switch A has a route to interface Loopback 1 (2::9/128) on Switch B, with the output interface being VLAN-interface 10. Switch B has a route to interface Loopback 1 (1::9/128) on Switch A, with the output interface being VLAN-interface 12.
# Configure IPv6 static routes on Switch B and enable BFD control packet mode for the static route that traverses Switch D. system-view [SwitchB] bfd multi-hop min-transmit-interval 500 [SwitchB] bfd multi-hop min-receive-interval 500 [SwitchB] bfd multi-hop detect-multiplier 9 [SwitchB] ipv6 route-static 121:: 64 1::9 bfd control-packet bfd-source 2::9 [SwitchB] ipv6 route-static 121:: 64 13::2 preference 65 [SwitchB] quit # Configure IPv6 static routes on Switch C.
The output shows that Switch A communicates Switch B through VLAN-interface 10. The link over VLAN-interface 10 fails. # Display IPv6 static routes on Switch A again.
Configuring an IPv6 default route A default IPv6 route is used to forward packets that match no entry in the routing table. A default IPv6 route can be configured in either of the following ways: • The network administrator can configure a default route with a destination prefix of ::/0. For more information, see "Configuring an IPv6 static route." • Some dynamic routing protocols, such as OSPFv3, IPv6 IS-IS, and RIPng, can generate a default IPv6 route.
Configuring OSPFv3 This chapter describes how to configure RFC 2740-compliant Open Shortest Path First version 3 (OSPFv3) for an IPv6 network. For more information about OSPFv2, see "Configuring OSPF.
• Inter-Area-Router LSA—Type-4 LSA, originated by ABRs and flooded throughout the LSA's associated area. Each Inter-Area-Router LSA describes a route to ASBR. • AS External LSA—Type-5 LSA, originated by ASBRs, and flooded throughout the AS, except stub and NSSA areas. Each AS External LSA describes a route to another AS. A default route can be described by an AS External LSA. • NSSA LSA—Type-7 LSA, originated by ASBRs in NSSAs and flooded throughout a single NSSA.
Tasks at a glance (Optional.) Tuning and optimizing OSPFv3 networks: • • • • • • • • • Configuring OSPFv3 timers Specifying LSA transmission delay Configuring a DR priority for an interface Specifying SPF calculation interval Specifying the LSA generation interval Ignoring MTU check for DD packets Disabling interfaces from receiving and sending OSPFv3 packets Enabling the logging of neighbor state changes Configuring the LSU transmit rate (Optional.
Configuring OSPFv3 area parameters OSPFv3 has the same stub area, NSSA area, and virtual link features as OSPFv2. After you split an OSPFv3 AS into multiple areas, the LSA number is reduced and OSPFv3 applications are extended. To further reduce the size of routing tables and the number of LSAs, configure the non-backbone areas at an AS edge as stub areas.
To configure an NSSA area: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Enter OSPFv3 area view. area area-id N/A 4. Configure the area as an NSSA area.
• Broadcast—When the link layer protocol is Ethernet or FDDI, OSPFv3 considers the network type as broadcast by default. • NBMA—When the link layer protocol is ATM, Frame Relay, or X.25, OSPFv3 considers the network type as NBMA by default. • P2P—When the link layer protocol is PPP, LAPB, HDLC, or POS, OSPFv3 considers the network type as P2P by default. Follow these guidelines when you change the network type of an OSPFv3 interface: • An NBMA network must be fully connected.
Configuring OSPFv3 route control Configuration prerequisites Before you configure OSPFv3 route control, complete the following tasks: • Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes. • Enable OSPFv3. Configuring OSPFv3 route summarization If contiguous network segments exist in an area, you can use the abr-summary command to summarize them into one network segment on the ABR. The ABR will advertise only the summary route.
Configuring Inter-Area-Prefix LSA filtering Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Enter OSPFv3 area view. area area-id N/A 4. Configure OSPFv3 to filter Inter-Area-Prefix LSAs. filter { acl6-number | prefix-list prefix-list-name | route-policy route-policy-name } { export | import } By default, OSPFv3 accepts all Inter-Area-Prefix LSAs. This command takes effect only on ABRs.
To configure the maximum number of ECMP routes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A By default, the maximum number of OSPFv3 ECMP routes equals the maximum number of ECMP routes supported by the system. 3. Specify the maximum number of ECMP routes. Use the max-ecmp-num command to configure the maximum number of ECMP routes supported by the system.
Step Command Remarks By default, route redistribution is disabled. 4. Configure OSPFv3 to redistribute routes from other routing protocols. import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost | nssa-only | route-policy route-policy-name | tag tag | type type ] * 5. (Optional.) Configure OSPFv3 to redistribute a default route.
Step Command Remarks The default setting is 5 seconds. 6. Configure the LSA retransmission interval. ospfv3 timer retransmit interval [ instance instance-id ] The LSA retransmission interval cannot be too short. Otherwise, unnecessary retransmissions will occur. Specifying LSA transmission delay Each LSA in the LSDB has an age that is incremented by 1 every second, but the age does not change during transmission.
Specifying the LSA generation interval You can adjust the LSA generation interval to protect network resources and routers from being over consumed by frequent network changes. When network changes are not frequent, LSAs are generated at the minimum-interval. If network changes become frequent, the LSA generation interval is incremented by incremental-interval × 2n-2 (n is the number of generation times) each time an LSA generation occurs until the maximum-interval is reached.
Disabling interfaces from receiving and sending OSPFv3 packets After an OSPFv3 interface is set to silent, direct routes of the interface can still be advertised in Intra-Area-Prefix LSAs through other interfaces, but other OSPFv3 packets cannot be advertised. No neighboring relationship can be established on the interface. This feature can enhance the adaptability of OSPFv3 networking. To disable interfaces from receiving and sending OSPFv3 packets: Step Command Remarks 1. Enter system view.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the LSU transmit rate. transmit-pacing interval interval count count By default, an OSPFv3 interface sends a maximum of three LSU packets every 20 milliseconds. Configuring OSPFv3 GR GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs: Two routers are required to complete a GR process.
Configuring BFD for OSPFv3 Bidirectional forwarding detection (BFD) provides a mechanism to quickly detect the connectivity of links between OSPFv3 neighbors, improving the convergence speed of OSPFv3. For more information about BFD, see High Availability Configuration Guide. After discovering neighbors by sending hello packets, OSPFv3 notifies BFD of the neighbor addresses, and BFD uses these addresses to establish sessions. Before a BFD session is established, it is in the down state.
Purpose Command Display OSPFv3 next hop information. display ospfv3 [ process-id ] nexthop Display OSPFv3 neighbor information. display ospfv3 [ process-id ] [ area area-id ] peer [ [ interface-type interface-number ] [ verbose ] | peer-router-id | statistics ] Display OSPFv3 request list information. display ospfv3 [ process-id ] [ area area-id ] request-queue [ interface-type interface-number ] [ neighbor-id ] Display OSPFv3 retransmission list information.
[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 [SwitchA-Vlan-interface200] ospfv3 1 area 1 [SwitchA-Vlan-interface200] quit # Configure Switch B: enable OSPFv3 and specify the router ID as 2.2.2.2. system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.
Area: 0.0.0.1 ------------------------------------------------------------------------Router ID Pri State Dead-Time InstID Interface 1.1.1.1 1 00:00:40 Full/DR 0 Vlan200 # Display OSPFv3 neighbors on Switch C. [SwitchC] display ospfv3 peer OSPFv3 Process 1 with Router ID 3.3.3.3 Area: 0.0.0.0 ------------------------------------------------------------------------Router ID Pri State Dead-Time InstID Interface 2.2.2.2 1 00:00:40 Full/DR 0 Vlan100 Area: 0.0.0.
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 AdvRouter : 3.3.3.3 Area : 0.0.0.0 Preference : 10 Total: 4 Intra area: 1 3. Inter area: 3 ASE: 0 NSSA: 0 Configure Area 2 as a stub area: # Configure Switch D. [SwitchD] ospfv3 [SwitchD-ospfv3-1] area 2 [SwitchD-ospfv3-1-area-0.0.0.2] stub # Configure Switch C, and specify the cost of the default route sent to the stub area as 10. [SwitchC] ospfv3 [SwitchC-ospfv3-1] area 2 [SwitchC-ospfv3-1-area-0.0.0.2] stub [SwitchC-ospfv3-1-area-0.0.0.
*Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 : 4 AdvRouter : 3.3.3.3 Area : 0.0.0.0 Preference : 10 Total: 5 Intra area: 1 Inter area: 4 ASE: 0 NSSA: 0 The output shows that a default route is added, and its cost is the cost of a direct route plus the configured cost. 4. Configure Area 2 as a totally stub area: # Configure Area 2 as a totally stub area on Switch C. [SwitchC-ospfv3-1-area-0.0.0.
Figure 49 Network diagram Configuration procedure 1. Configure IPv6 addresses for interfaces. (Details not shown.) 2. Configure basic OSPFv3 (see "OSPFv3 stub area configuration example"). 3. Configure Area 1 as an NSSA area: # Configure Switch A. [SwitchA] ospfv3 [SwitchA-ospfv3-1] area 1 [SwitchA-ospfv3-1-area-0.0.0.2] nssa [SwitchA-ospfv3-1-area-0.0.0.2] quit [SwitchA-ospfv3-1] quit # Configure Switch B. [SwitchB] ospfv3 [SwitchB-ospfv3-1] area 1 [SwitchB-ospfv3-1-area-0.0.0.
Type : IA Cost NextHop : FE80::20C:29FF:FE74:59C6 Interface: Vlan200 : 2 AdvRouter : 2.2.2.2 Area : 0.0.0.1 : 1 Preference : 10 *Destination: 2001:1::/64 Type : I Cost Nexthop : :: Interface: Vlan200 AdvRouter : 1.1.1.1 Area : 0.0.0.2 : 3 Preference : 10 *Destination: 2001:2::/64 Type : IA Cost NextHop : FE80::20C:29FF:FE74:59C6 Interface: Vlan200 AdvRouter : 2.2.2.2 Area : 0.0.0.1 Preference : 10 Total: 3 Intra area: 1 4.
NextHop : :: Interface: Vlan400 AdvRouter : 4.4.4.4 Area : 0.0.0.2 : 1 Preference : 10 *Destination: 1234::/64 Type : E2 Cost NextHop : FE80::20C:29FF:FEB9:F2EF Interface: Vlan400 AdvRouter : 2.2.2.2 Tag : 0 Preference : 10 Total: 4 Intra area: 1 Inter area: 2 ASE: 1 NSSA: 0 The output shows an AS external route imported from the NSSA area exists on Switch D.
[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. system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 0 [SwitchB-Vlan-interface200] quit # Configure Switch C: enable OSPFv3 and specify the router ID as 3.3.3.3.
3. 2.2.2.2 1 Full/DROther 00:00:37 0 Vlan200 3.3.3.3 1 Full/BDR 00:00:31 0 Vlan100 Configure router priorities for interfaces: # Configure the router priority of VLAN-interface 100 as 100 on Switch A. [SwitchA] interface Vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 dr-priority 100 [SwitchA-Vlan-interface100] quit # Configure the router priority of VLAN-interface 200 as 0 on Switch B.
------------------------------------------------------------------------Router ID Pri State Dead-Time InstID Interface 2.2.2.2 0 Full/DROther 00:00:36 0 Vlan200 3.3.3.3 2 Full/BDR 00:00:35 0 Vlan100 4.4.4.4 1 Full/DROther 00:00:33 0 Vlan200 # Display neighbor information on Switch D. [SwitchD] display ospfv3 peer OSPFv3 Process 1 with Router ID 4.4.4.4 Area: 0.0.0.
[SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 2 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ospfv3 1 area 2 [SwitchA-Vlan-interface200] quit # Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B. system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.
Interface 3.
Interface : InLoop0 Cost : 0 Destination: 4::/64 Protocol : Direct NextHop : 4::1 Preference: 0 Interface : Vlan400 Cost : 0 Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost : 0 Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost : 0 Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 BFD for OSPFv3 configuration example Network requirements As shown i
2. Configure basic OSPFv3: # On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1. system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ospfv3 1 area 0 [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] ospfv3 1 area 0 [SwitchA-Vlan-interface11] quit # On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Switch A.
Configuring IPv6 PBR Introduction to IPv6 PBR Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: 1. The device uses PBR to forward matching packets. 2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets. 3.
Relationship between the match mode and clauses on the node Does a packet match all the if-match clauses on the node? Match mode In permit mode In deny mode • If the node is configured with an apply clause, IPv6 PBR executes the apply clause on the node. • If IPv6 PBR successfully guides the forwarding of the packet, IPv6 PBR does not match the packet against the next node. Yes The packet is forwarded according to the routing table.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 policy node view. ipv6 policy-based-route policy-name [ deny | permit ] node node-number N/A 3. Configure an ACL match criterion. if-match acl { acl6-number | name acl6-name } By default, no ACL match criterion is configured. NOTE: An ACL match criterion uses the specified ACL to match packets regardless of the permit or deny action and the time range of the ACL.
Configuring IPv6 interface PBR Configure IPv6 PBR by applying an IPv6 policy to an interface. IPv6 PBR uses the policy to guide the forwarding of IPv6 packets received on the interface. The specified policy must already exist. Otherwise, the IPv6 interface PBR configuration fails. You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface. You can apply a policy to multiple interfaces.
Figure 53 Network diagram Configuration procedure 1. Configure Switch A: # Create VLAN 10 and VLAN 20. system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure the IPv6 addresses of VLAN-interface 10 and VLAN-interface 20.
[SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IPv6 address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ipv6 address 2::2 64 Verifying the configuration # Telnet to Switch B on Switch A. The operation succeeds. # Telnet to Switch C on Switch A. The operation fails. # Ping Switch C from Switch A. The operation succeeds. Telnet uses TCP and ping uses ICMP.
Configuring routing policies Routing policies control routing paths by filtering and modifying routing information. This chapter describes both IPv4 and IPv6 routing policies. Overview Routing policies can filter advertised, received, and redistributed routes, and modify attributes for specific routes. To configure a routing policy: 1. Configure filters based on route attributes, such as destination address and the advertising router's address. 2.
Routing policy A routing policy can contain multiple nodes, which are in a logical OR relationship. A node with a smaller number is matched first. A route (except the route configured with the continue clauses) that matches one node matches the routing policy. Each node has a match mode of permit or deny. • permit—Specifies the permit match mode for a routing policy node. If a route matches all the if-match clauses of the node, it is handled by the apply clauses of the node.
Step Command Remarks 1. Enter system view. system-view N/A 2. Configure an IPv4 prefix list. ip prefix-list prefix-list-name [ index index-number ] { deny | permit } ip-address mask-length [ greater-equal min-mask-length ] [ less-equal max-mask-length ] By default, no IPv4 prefix list is configured. Configuring an IPv6 prefix list If all items are set to deny mode, no routes can pass the IPv6 prefix list.
Step Command Remarks • Configure a basic community list: 2. Configure a community list. ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit } [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] * Use either method. • Configure an advanced community list: ip community-list { adv-comm-list-num | advanced adv-comm-list-name } { deny | permit } regular-expression By default, no community list is configured.
Configuring if-match clauses You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit-mode node, all routing information can pass the node. If no if-match clause is specified for a deny-mode node, no routing information can pass the node. The if-match clauses of a routing policy node have a logical AND relationship. A route must meet all if-match clauses before it can be executed by the apply clauses of the node.
Step Command Remarks if-match local-preference preference By default, no local preference is configured for BGP routes. 10. Match routes having the specified route type. if-match route-type { external-type1 | external-type1or2 | external-type2 | internal | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 } * By default, no route type match criterion is configured. 11. Match OSPF routes having the specified tag value.
Step Command Remarks • Set the next hop for IPv4 Set the next hop for routes. 9. routes: apply ip-address next-hop ip-address [ public | vpn-instance vpn-instance-name ] • Set the next hop for IPv6 routes: apply ipv6 next-hop ipv6-address By default, no next hop is set for IPv4/IPv6 routes. The apply ip-address next-hop and apply ipv6 next-hop commands do not apply to redistributed IPv4 and IPv6 routes. 10. Set a local preference for BGP routes.
Step 3. Command Specify the next node to be matched. Remarks By default, no continue clause is configured. continue [ node-number ] The specified next node must have a larger number than the current node. Displaying and maintaining the routing policy Execute display commands in any view and reset commands in user view. Task Command Display BGP AS path list information. display ip as-path [ as-path-number ] Display BGP community list information.
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index Numerics IPv4 BGP route summarization, 148 4-byte IPv4 BGP-IGP route redistribution, 145 IPv6 BGP basic configuration, 172 IPv4 BGP AS number suppression, 124 IPv6 BGP BFD configuration, 178 IPv6 BGP AS number suppression, 124 IPv6 BGP COMMUNITY configuration, 132 A IPv6 BGP configuration, 172 ABR IPv6 BGP fake AS number advertisement, 117 OSPF route summarization on ABR, 34 IPv6 BGP route reflector configuration, 176 OSPF router type, 22 OSPF configuration, 19, 26 action OSPF host ro
IPv4 BGP best route selection, 116 BGP path AS_SET attribute, 73 IPv4 BGP 4-byte AS number suppression, 124 IPv4 BGP AS number substitution, 118 IPv6 BGP best route selection, 116 ASBR IPv4 BGP basic configuration, 141 OSPF ASBR summary LSA, 19 IPv4 BGP BFD configuration, 169 OSPF redistributed route summarization on ASBR, 34 IPv4 BGP COMMUNITY configuration), 154 IPv4 BGP confederation configuration, 160 IPv4 BGP configuration, 141 OSPF router type, 22 attribute BGP AS_PATH attribute, 115 IPv4 BGP
OSPF area authentication configuration, 43, 43 community, 78 authentication confederation, 78 confederation compatibility, 135 OSPF configuration, 42 automatic confederation configuration, 135 configuration, 72, 83 IPv4 BGP route automatic summarization, 97 configuration views, 82 B default route advertisement to peer/peer group, 98 backbone EBGP direct connections after link failure, 123 OSPF backbone area, 21 enabling, 86 OSPF router type, 22 first AS number of EBGP route updates, 120 back
session state change logging, 137 IPv4 BGP ORIGINATOR_ID attribute, 134 soft reset configuration, 127 IPv4 BGP route reflector configuration, 133 speaker, 72 IPv6 BGP COMMUNITY configuration, 132 TCP connection source interface, 93 IPv6 BGP ORIGINATOR_ID attribute, 134 trap enable, 137 IPv6 BGP route reflector configuration, 133 troubleshooting, 182 routing policy community list configuration, 241 troubleshooting peer connection state, 182 routing policy extended community list, 239 tuning net
IP routing FIB route max lifetime, 4 IPv6 BGP route dampening, 105 IP routing max number ECMP routes, 5 IPv6 BGP route distribution filtering policies, 100 IP routing RIB label max lifetime, 3 IPv6 BGP route preference, 107 IP routing RIB route max lifetime, 3 IPv6 BGP route reception filtering policies, 103 IPv4 BGP, 141 IPv6 BGP route reflector, 133, 176 IPv4 BGP AS number substitution, 118 IPv6 BGP route update interval, 121 IPv4 BGP basics, 141 IPv6 default route, 201 IPv4 BGP BFD, 138, 16
OSPFv3 network type, 206 OSPF interface cost, 35 OSPF LSDB max number external LSAs, 44 OSPFv3 network type (for interface), 207 OSPF LSU transmit rate, 46 OSPFv3 NSSA area, 205, 221 OSPF max number ECMP routes, 36 OSPFv3 P2MP neighbor, 207 OSPF NBMA network type for interface, 32 OSPFv3 preference, 210 OSPF network management, 45 OSPFv3 received route filtering, 208 OSPF network type, 31 OSPFv3 route control, 208 OSPF NSSA area, 30, 62 OSPFv3 route redistribution, 210, 227, 227 OSPF P2MP net
BGP TCP connection source interface, 93 IPv4 BGP BFD configuration, 138 EBGP direct connections after link failure, 123 IPv6 BGP BFD configuration, 138 continue clause (routing policy), 240, 245 OSPF BFD configuration, 51 controlling OSPF BFD detection (bidirectional control), 51 OSPF BFD detection (single-hop echo), 51 BGP path selection, 106 BGP route distribution, 96 device BGP route reception, 96 IPv4 BGP basic configuration, 141 IPv6 static route BFD control mode (direct next hop), 192 IPv
OSPFv3 stub area configuration, 217 E PBR configuration (interface/packet type-based), 188 EBGP BGP first AS number of route updates, 120 PBR configuration (local/packet type-based), 186 direct connections after link failure, 123 IPv4 BGP multiple hop EBGP session establishment, 122 static routing basic configuration, 11 static routing BFD configuration (direct next hop), 13 IPv4 BGP private AS number removal from EBGP peer/peer group update, 119 static routing BFD configuration (indirect next hop),
IPv6 BGP MED AS route comparison (per-AS), 111 IPv4 BGP GR configuration, 167 IPv6 BGP multiple hop EBGP session establishment, 122 IPv4 BGP path selection configuration, 164 IPv4 BGP load balancing configuration, 151 IPv4 BGP route distribution filtering policies, 100 IPv6 BGP peer MD5 authentication, 124 IPv4 BGP route reception filtering policies, 103 IPv6 BGP route refresh, 127 IPv4 BGP route reflector configuration, 157 OSPF, 27 IPv4 BGP route summarization, 148 OSPF ISPF, 47 IPv4 BGP-IGP r
BGP confederation, 135 OSPFv3 BFD configuration, 216 PBR configuration, 183, 184, 185, 186 IPv4 BGP ORIGINATOR_ID attribute, 134 PBR configuration (interface), 186 IPv4 BGP route reflector configuration, 133 PBR configuration (interface/packet type-based), 188 IPv6 BGP ORIGINATOR_ID attribute, 134 IPv6 BGP route reflector configuration, 133 PBR configuration (local), 185 PBR configuration (local/packet type-based), 186 peer, 72 ICMP OSPF basic configuration, 53 PBR policy configuration, 184 OSPF c
BGP route recursion, 77 interval BGP soft reset, 127 BGP route reflection configuration, 133 IPv4 BGP keepalive interval, 120 BGP route selection, 77, 77 IPv4 BGP route update interval, 121 BGP route summarization, 78, 97 IPv6 BGP keepalive interval, 120 BGP session state change logging, 137 IPv6 BGP route update interval, 121 BGP soft reset configuration, 127 OSPF exit overflow interval, 44 BGP TCP connection source interface, 93 OSPF LSA arrival interval, 41 BGP trap enable, 137 OSPF LSA ge
OSPFv3 max number ECMP routes, 209 static route BFD bidirectional control mode (indirect next hop), 9 OSPFv3 NBMA neighbor configuration, 207 static route BFD configuration, 9 OSPFv3 neighbor state change logging, 214 static route BFD single-hop echo mode, 10 OSPFv3 network optimization, 211 OSPFv3 network tuning, 211 static route configuration, 8 OSPFv3 network type configuration, 206 static routing basic configuration, 11 static routing BFD configuration (direct next hop), 13 OSPFv3 network type
peer group configuration, 89 COMMUNITY configuration, 132, 154 confederation configuration, 160 configuration, 141 peer protection (low memory exemption), 131 IPv4 IBGP default local preference, 108 default route advertisement to peer/peer group, 98 peer group configuration, 88 IPv6 FIB route max lifetime, 4 displaying, 139 OSPFv3 area parameter configuration, 205 fake AS number advertisement, 117 OSPFv3 BFD configuration, 216, 230 GR configuration, 167 OSPFv3 configuration, 202, 203, 217 holdtim
peer protection (low memory exemption), 131 routing policy prefix list, 239 IPv6 BGP IPv6 IBGP 4-byte AS number suppression, 124 AS number substitution, 118 peer group configuration, 88 IPv6 PBR AS_PATH best route selection, 116 apply clause, 233 basic configuration, 172 configuration, 233, 234, 235, 236 BFD configuration, 138, 178 configuration (local/packet type-based), 236 COMMUNITY configuration, 132 displaying, 236 configuration, 172 if-match clause, 233 default local preference, 108 in
IPv6 EBGP peer protection (level 2 threshold exemption), 131 limiting PBR local configuration, 185 logging BGP session state change logging, 137 IPv4 BGP routes received from peer/peer group, 99 IPv6 BGP routes received from peer/peer group, 99 OSPF neighbor state change, 45 OSPFv3 neighbor state change logging, 214 LSA OSPF AS External LSA, 19 link OSPF ASBR summary LSA, 19 EBGP direct connection after link failure, 123 OSPF exit overflow interval, 44 IPv4 BGP BFD configuration, 138 OSPF LSA arriv
IPv4 EBGP peer protection (low memory exemption), 131 M maintaining IPv6 EBGP peer protection (low memory exemption), 131 IP routing table, 6 IPv4 BGP, 139 IPv6 BGP, 139 message BGP notification, 72 IPv6 PBR, 236 BGP open, 72 OSPF, 51 BGP route-refresh, 72 PBR, 186 routing policy, 246 managing BGP update, 72 mode enhanced ECMP mode enable, 5 BGP large scale network management, 78 IPv6 static route BFD control mode (direct next hop), 192 manual IPv4 BGP route manual summarization, 97 IPv6 stati
BGP MED attribute, 109 overview, 81 protocols and standards, 83 BGP optimal route advertisement rules, 98 MTU BGP optimization, 120 OSPF DD packet interface MTU, 43 BGP path selection, 106 OSPFv3 DD packet ignore MTU check, 213 BGP peer configuration, 87 multicast BGP peer group, 78 BGP peer group configuration, 88 OSPF network type, 24 Multiprotocol Extensions for BGP-4.
IPv4 BGP load balancing, 125 IPv6 BGP route preference, 107 IPv4 BGP local AS number appearance, 115, 115 IPv6 BGP route reflector configuration, 133 IPv4 BGP local network injection, 95 IPv6 BGP route update interval, 121 IPv6 BGP route reception filtering policies, 103 IPv4 BGP manual soft reset, 129 IPv6 BGP route update save, 128 IPv4 BGP multiple hop EBGP session establishment, 122 IPv6 BGP routes received from peer/peer group, 99 IPv6 BGP route-refresh, 127 IPv4 BGP NEXT_HOP attribute, 113
OSPF LSU transmit rate, 46 OSPFv3 interface cost configuration, 209 OSPF NBMA network type configuration for interface, 32 OSPFv3 interface packet send/receive disable, 214 OSPF neighbor state change logging, 45 OSPFv3 LSA generation interval, 213 OSPFv3 interface DR priority, 213 OSPF network LSA, 19 OSPFv3 LSA transmission delay, 212 OSPF network management, 45 OSPFv3 LSU transmit rate, 214 OSPF network summary LSA, 19 OSPFv3 max number ECMP routes, 209 OSPF network type configuration, 31 OS
tuning BGP, 120 PBR configuration (interface/packet type-based), 188 network management PBR configuration (local/packet type-based), 186 BGP configuration, 72, 83 PBR policy, 183 BGP large scale networks, 78 IP routing configuration, 1 routing policy configuration, 239 IPv4 BGP basic configuration, 141 static routing basic configuration, 11 static routing BFD configuration (direct next hop), 13 IPv4 BGP BFD configuration, 169 static routing BFD configuration (indirect next hop), 15 IPv4 BGP COMM
configuring authentication, 42 OSPF NSSA area, 22 OSPF NSSA area configuration, 30, 62 DD packet interface MTU add, 43 OSPF NSSA LSA, 19 default route redistribution, 37 OSPF totally NSSA area, 22 displaying, 51 OSPFv3 NSSA area configuration, 205 DR election, 25 number DR election configuration, 64 BGP first AS number of EBGP route updates, 120 ECMP route max number configuration, 36 IPv4 BGP 4-byte AS number suppression, 124 exit overflow interval, 44 enabling, 27 IPv4 BGP AS number substi
prefix suppression (interface configuration), 48 interface packet send/receive disable, 214 protocols and standards, 25 LSA generation interval, 213 received route filtering configuration, 35 LSA transmission delay, 212 redistributed route default parameters, 38 LSA types, 202 redistributed route summarization on ASBR, 34 LSU transmit rate, 214 RFC 1583 compatibility, 45 max number ECMP routes, 209 route calculation, 24 NBMA neighbor configuration, 207 route control configuration, 33 neighbor
OSPFv3 stub area configuration, 217 IP routing route backup, 3 IP routing route preference, 2 PBR configuration, 183, 184, 185, 186 IP routing route recursion, 3 PBR configuration (interface/packet type-based), 188 IP routing route redistribution, 3 IPv6 PBR configuration, 233, 234, 235, 236 PBR configuration (local/packet type-based), 186 IPv6 PBR configuration (local/packet type-based), 236 PBR interface configuration, 186 IPv6 PBR interface configuration, 236 PBR policy configuration, 184 IPv6
BGP configuration, 87 IPv6 policy configuration, 234 BGP default route advertisement to peer/peer group, 98 PBR, 183 BGP peer group, 78 BGP peer group configuration, 88 PBR configuration (interface/packet type-based), 188 EBGP, 72 PBR configuration (local/packet type-based), 186 IBGP, 72 PBR interface configuration, 186 IPv4 BGP configuration, 87 PBR local configuration, 185 IPv4 BGP MED AS route comparison (confederation peers), 112 PBR node action, 185 IPv4 BGP peer MD5 authentication, 124
configuring IPv4 BGP MED default value, 109 OSPF prefix prioritization, 48 priority configuring IPv4 BGP NEXT_HOP attribute, 113 OSPF route level priority, 23 configuring IPv4 BGP path selection, 164 OSPFv3 interface DR priority, 213 configuring IPv4 BGP peer, 87 procedure configuring IPv4 BGP route automatic summarization, 97 advertising BGP default route to peer/peer group, 98 configuring IPv4 BGP route dampening, 105 advertising IPv4 BGP fake AS number, 117 configuring IPv4 BGP route distribu
configuring IPv6 PBR (interface), 236 configuring OSPF max number ECMP routes, 36 configuring IPv6 PBR (local), 235 configuring OSPF NBMA network type for interface, 32 configuring IPv6 PBR (local/packet type-based), 236 configuring OSPF network management, 45 configuring IPv6 policy, 234 configuring OSPF network type, 31 configuring IPv6 static route, 191 configuring OSPF NSSA area, 30, 62 configuring IPv6 static route BFD, 191 configuring OSPF P2MP network type for interface, 32 configuring IP
configuring OSPFv3 max number ECMP routes, 209 configuring static route BFD single-hop echo mode, 10 configuring OSPFv3 NBMA neighbor, 207 configuring static routing, 11 configuring OSPFv3 network type, 206 configuring static routing basics, 11 configuring OSPFv3 network type (for interface), 207 configuring static routing BFD (direct next hop), 13 configuring OSPFv3 NSSA area, 205, 221 configuring static routing default route, 18 configuring OSPFv3 P2MP neighbor, 207 controlling BGP path selecti
maintaining IP routing table, 6 enabling IPv4 BGP MED AS route comparison (per-AS), 111 maintaining IPv4 BGP, 139 enabling IPv4 BGP multiple hop EBGP session establishment, 122 maintaining IPv6 BGP, 139 maintaining IPv6 PBR, 236 enabling IPv4 BGP peer MD5 authentication, 124 maintaining OSPF, 51 maintaining PBR, 186 enabling IPv4 BGP route-refresh, 127 maintaining routing policy, 246 enabling IPv6 BGP 4-byte AS number suppression, 124 optimizing BGP network, 120 optimizing OSPF network, 38 enabli
IPv4 EBGP peer (low memory exemption), 131 BGP route filtering policies, 100 IPv6 EBGP peer (low memory exemption), 131 BGP route generation, 94 protocols and standards BGP route recursion, 77 BGP, 83 BGP route reflection configuration, 133 IP routing dynamic routing protocols, 2 BGP route reflector, 78 MP-BGP, 83 BGP route selection, 77, 77 OSPF, 25 BGP route summarization, 78 OSPF preference, 37 BGP route-refresh message, 72 OSPF RFC 1583 compatibility, 45 FIB table optimal routes, 1 OSP
static routing basic configuration, 11 IPv6 BGP route refresh, 127 IPv6 BGP route update interval, 121 static routing BFD configuration (direct next hop), 13 IPv6 BGP route update save, 128 static routing BFD configuration (indirect next hop), 15 IPv6 BGP routes received from peer/peer group, 99 static routing configuration, 8, 11 IPv6 default route configuration, 201 IPv6 static route BFD configuration, 191 static routing default route configuration, 18 router IPv6 static route BFD control mode (d
policy extended community list configuration, 242 OSPF LSA transmission delay, 40 OSPF LSU transmit rate, 46 policy filter configuration, 240 OSPF NBMA network type configuration for interface, 32 policy filtering, 240 OSPF network management traps, 45 policy if-match clause configuration, 243 policy filters, 239 OSPF network optimization, 38 policy IP prefix list configuration, 240 OSPF network tuning, 38 policy-based routing.
OSPF SPF calculation interval, 40 OSPF summary route advertisement, 57 OSPFv3 LSA generation interval, 213 OSPFv3 LSA transmission delay, 212 OSPFv3 route summarization, 208 suppressing OSPFv3 SPF calculation interval, 212 IPv4 BGP 4-byte AS number suppression, 124 SPF IPv6 BGP 4-byte AS number suppression, 124 OSPF prefix suppression, 47 OSPF SPF calculation interval, 40 OSPFv3 SPF calculation interval, 212 switch state IPv6 PBR configuration (local/packet type-based), 236 BGP session state cha
OSPF no neighbor relationship established, 70 IPv4 BGP configuration, 141 IPv4 BGP GR configuration, 167 tuning IPv4 BGP load balancing configuration, 151 BGP network, 120 IPv4 BGP path selection configuration, 164 OSPF network, 38 IPv4 BGP route reflector configuration, 157 OSPFv3 network, 211 IPv4 BGP route summarization, 148 Type 1 external IPv4 BGP-IGP route redistribution, 145 IPv6 BGP basic configuration, 172 OSPF route type, 23 Type 2 external IPv6 BGP BFD configuration, 178 IPv6 BGP con
