HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
342 Configuring a large-scale IPv6 BGP network In a large-scale IPv6 BGP network, configuration and maintenance become inconvenient because of too many peers. Configuring peer groups makes mana gement easier and improves route distribution efficiency. Peer group includes IBGP peer group, where peers belong to the same AS, and EBGP peer group, where peers belong to different ASs. If peers in an EBGP group belong to the same external AS, the EBGP peer group is a pure EBGP peer grou p, and if not, a mixed EBGP peer group. In a peer group, all members have a common policy . Using the community attribute can make a set of IPv6 BGP routers in multiple ASs have the same policy because community sending between IPv6 BGP peers is not limited by AS. To assure connectivity between IBGP peers, make them fully meshed, but it becomes impractical when too many IBGP peers exist. Using route reflectors or confederation can solve this issue. In a large-scale AS, both of them can be used. Confederation configuration of IPv6 BGP is identical to that of BGP4, so it is not mentioned here. Configuration prerequisites Before you configure a large-scale IPv6 BGP network, complete the following tasks: • Make peer nodes accessible to each other at the network layer. • Enable BGP and configure a router ID. Configuring IPv6 BGP peer group Configuring an IBGP peer group Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A 4. Create an IBGP peer group. group ipv6-group-name [ internal ] N/A 5. Add a peer into the group. peer ipv6-address group ipv6-group-name [ as-number as-number ] Not added by default. Creating a pure EBGP peer group To create a pure EBGP peer group, specify an AS number for the peer group. If a peer was added into an EBGP peer group, you cannot specify any AS number for the peer group. To create a pure EBGP peer group: Step Command Remarks 1. Enter system view. system-view N/A
343 Ste p Command Remarks 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A 4. Create an EBGP peer group. group ipv6-group-name external N/A 5. Configure the AS number for the peer group. peer ipv6-group-name as-number as-number Not configured by default. 6. Add an IPv6 peer into the peer group. peer ipv6-address group ipv6-group-name Not added by default. Creating a mixed EBGP peer group When creating a mixed EBGP peer group, you must create a peer and specify its AS number that is different from AS numbers of other peers; however, you cannot specify AS number for the EBGP peer group. To create a mixed EBGP peer group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A 4. Create an EBGP peer group. group ipv6-group-name external N/A 5. Specify the AS number of an IPv6 peer. peer ipv6-address as-number as-number Not specified by default. 6. Add the IPv6 peer into the peer group. peer ipv6-address group ipv6-group-name Not added by default. Configuring IPv6 BGP community When configuring IPv6 BGP community, you must configure a routing policy to define the community attribute, and apply the routing policy to route ad vertisement. For routing policy configuration, see Configuring routing policies . Advertising community attribute to an IPv6 peer or peer group Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A
344 Ste p Command Remarks 4. Advertise community attribute to an IPv6 peer or peer group. peer { ipv6-group-name | ipv6-address } advertise-community Not advertised by default. 5. Advertise extended community attribute to an IPv6 peer or peer group. peer { ipv6-group-name | ipv6-address } advertise-ext-community Not advertised by default. Applying a routing policy to routes advertised to a peer or peer group Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A 4. Apply a routing policy to routes advertised to an IPv6 peer or peer group. peer { ipv6-group-name | ipv6-address } route-policy route-policy-name export Not applied by default. Configuring an IPv6 BGP route reflector Follow these guidelines when you configure an IPv6 BGP route reflector: Because the route reflector forwards routing informatio n between clients, you must make clients of a route reflector fully meshed. If clients are fully meshed, HP recommends disabling route reflection between clients to reduce routing costs. If a cluster has multiple route reflectors, you must specify the same cluster ID for these route reflectors to avoid routing loops. To configure an IPv6 BGP route reflector: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 address family view. ipv6-family N/A 4. Configure the router as a route reflector and specify an IPv6 peer or peer group as a client. peer { ipv6-group-name | ipv6-address } reflect-client Not configured by default. 5. Enable route reflection between clients. reflect between-clients Optional. Enabled by default. 6. Configure the cluster ID of the route reflector. reflector cluster-id cluster-id Optional. By default, a route reflector uses its router ID as the cluster ID.
345 Configuring BFD for IPv6 BGP IPv6 BGP maintains neighbor relationships based on the keepalive timer and holdtime timer, which are set in seconds. IPv6 BGP defines that the holdtime interval must be at least three times the keepalive interval. This mechanism makes the detection of a link failure rather slow and thus causes a large quantity of packets to be dropped especially when th e failed link is a high-speed link. You can enable BFD to detect the link to a peer. BFD can quickly detect any link failure and thus reduce network convergence time. After a link failure occurs, BFD may detect the failure before the system performs GR and as a result, GR will fail. Therefore, if GR capability is enabled for IPv6 BGP, use BFD with caution. For more information about BFD, see High Availability Configuration Guide . IMPORTANT: Before configuring BFD for IPv6 BGP, you must enable BGP. To enable BFD for a BGP peer: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable BGP and enter BGP view. bgp as-number Not enabled by default. 3. Enter IPv6 address family view. ipv6-family N/A 4. Enable BFD for the specified BGP peer. peer ipv6-address bfd Not enabled for any BGP peer by default. Displaying and maintaining IPv6 BGP Displaying BGP Task Command Remarks Display IPv6 BGP peer group information. display bgp ipv6 group [ ipv6-group-name ] [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP advertised routing information. display bgp ipv6 network [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP AS path information. display bgp ipv6 paths [ as-regular-expression | | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP peer or peer group information. display bgp ipv6 peer [ group-name log-info | ipv4-address verbose | ipv6-address { log-info | verbose } | verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view
346 Task Command Remarks Display the prefix entries in the ORF information of the specified BGP peer. display bgp ipv6 peer { ip-address | ipv6-address } received ipv6-prefix [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing table information. display bgp ipv6 routing-table [ ipv6-address prefix-length ] [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing information matching an AS path ACL. display bgp ipv6 routing-table as-path-acl as-path-acl-number [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing information with the specified community attribute. display bgp ipv6 routing-table community [ aa:nn ] [ no-advertise | no-export | no-export-subconfed ]* [ whole-match ] [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing information matching an IPv6 BGP community list. display bgp ipv6 routing-table community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number }& [ | { begin | exclude | include } regular-expression ] Available in any view Display dampened IPv6 BGP routing information. display bgp ipv6 routing-table dampened [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP dampening parameter information. display bgp ipv6 routing-table dampening parameter [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing information originated from different ASs. display bgp ipv6 routing-table different-origin-as [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing flap statistics. display bgp ipv6 routing-table flap-info [ regular-expression as-regular-expression | [ as-path-acl as-path-acl-number | ipv6-address prefix-length [ longer-match ] ] [ | { begin | exclude | include } regular-expression ] ] Available in any view Display BGP routing information to or from an IPv4 or IPv6 peer. display bgp ipv6 routing-table peer { ipv4-address | ipv6-address } { advertised-routes | received-routes } [ network-address prefix-length | statistic ] [ | { begin | exclude | include } regular-expression ] Available in any view Display IPv6 BGP routing information matching a regular expression. display bgp ipv6 routing-table regular-expression as-regular-expression Available in any view Display IPv6 BGP routing statistics. display bgp ipv6 routing-table statistic [ | { begin | exclude | include } regular-expression ] Available in any view Resetting IPv6 BGP connections
347 Task Command Remarks Perform soft reset on IPv6 BGP connections. refresh bgp ipv6 { ipv4-address | ipv6-address | all | external | group ipv6-group-name | internal } { export | import } Available in user view Reset IPv6 BGP connections. reset bgp ipv6 { as-number | ipv4-address | ipv6-address [ flap-info ] | all | external | group group-name | internal } Available in user view Clearing IPv6 BGP information Task Command Remarks Clear dampened IPv6 BGP routing information and release suppressed routes. reset bgp ipv6 dampening [ ipv6-address prefix-length ] Available in user view Clear IPv6 BGP route flap information. reset bgp ipv6 flap-info [ ipv6-address/prefix-length | as-path-acl as-path-acl-number | regexp as-path-regexp ] Available in user view IPv6 BGP configuration examples Some examples for IPv6 BGP configuration are similar to those of BGP4. For more information, see Configuring BGP. IPv6 BGP basic configuration example Network requirements All switches in Figure 1 15 ru n IPv6 BGP. Between Switch A and Switch B is an EBGP connection. Switch B, Switch C, and Switch D are fully meshed through IBGP connections. Figure 115 Network diagram Configuration procedure 1. Configure IPv6 addresses for inte rfaces. (Details not shown.) 2. Configure IBGP connections: # Configure Switch B.
348 system-view [SwitchB] ipv6 [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] peer 9:1::2 as-number 65009 [SwitchB-bgp-af-ipv6] peer 9:3::2 as-number 65009 [SwitchB-bgp-af-ipv6] quit [SwitchB-bgp] quit # Configure Switch C. system-view [SwitchC] ipv6 [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 9:3::1 as-number 65009 [SwitchC-bgp-af-ipv6] peer 9:2::2 as-number 65009 [SwitchC-bgp-af-ipv6] quit [SwitchC-bgp] quit # Configure Switch D. system-view [SwitchD] ipv6 [SwitchD] bgp 65009 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family [SwitchD-bgp-af-ipv6] peer 9:1::1 as-number 65009 [SwitchD-bgp-af-ipv6] peer 9:2::1 as-number 65009 [SwitchD-bgp-af-ipv6] quit [SwitchD-bgp] quit 3. Configure the EBGP connection: # Configure Switch A. system-view [SwitchA] ipv6 [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] peer 10::1 as-number 65009 [SwitchA-bgp-af-ipv6] quit [SwitchA-bgp] quit # Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] peer 10::2 as-number 65008 # Display IPv6 peer information on Switch B. [SwitchB] display bgp ipv6 peer
349 BGP local router ID : 2.2.2.2 Local AS number : 65009 Total number of peers : 3 Peers in established state : \ 3 Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State 10::2 65008 3 3 0 0 00:01:16 Established\ 9:3::2 65009 2 3 0 0 00:00:40 Established\ 9:1::2 65009 2 4 0 0 00:00:19 Established\ # Display IPv6 peer information on Switch C. [SwitchC] display bgp ipv6 peer BGP local router ID : 3.3.3.3 Local AS number : 65009 Total number of peers : 2 Peers in established state : \ 2 Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State 9:3::1 65009 4 4 0 0 00:02:18 Established\ 9:2::2 65009 4 5 0 0 00:01:52 Established\ Switch A and B have established an EBGP connection; Switch B, C, and D have established IBGP connections with each other. IPv6 BGP route reflector configuration example Network requirements As shown in the following figure, Switch B receives an EBGP update and sends it to Switch C, which is configured as a route reflector with two clients: Switch B and Switch D. Switch B and Switch D do not need to establish an IBGP connection because Switch C reflects updates between them. Figure 116 Network diagram Configuration procedure 1. Configure IPv6 addresses for VLAN interfaces. (Details not shown.) Vlan-int200 100::1/96Switch A AS 100 Vlan-int200 100::2/96 Vlan-int300 101::2/96 Vlan-int100 102::2/96 Vlan-int100 102::1/96 Vlan-int300 101::1/96 Switch C Switch B Switch D IBGP IBGP AS 200 Route Reflector Vlan-int100 1::1/64
350 2. Configure IPv6 BGP basic functions: # Configure Switch A. system-view [SwitchA] ipv6 [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] peer 100::2 as-number 200 [SwitchA-bgp-af-ipv6] network 1:: 64 #Configure Switch B. system-view [SwitchB] ipv6 [SwitchB] bgp 200 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] peer 100::1 as-number 100 [SwitchB-bgp-af-ipv6] peer 101::1 as-number 200 [SwitchB-bgp-af-ipv6] peer 101::1 next-hop-local # Configure Switch C. system-view [SwitchC] ipv6 [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 101::2 as-number 200 [SwitchC-bgp-af-ipv6] peer 102::2 as-number 200 # Configure Switch D. system-view [SwitchD] ipv6 [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family [SwitchD-bgp-af-ipv6] peer 102::1 as-number 200 3. Configure route reflector: # Configure Switch C as a route reflector, and co nfigure Switch B and Switch D as its clients. [SwitchC-bgp-af-ipv6] peer 101::2 reflect-client [SwitchC-bgp-af-ipv6] peer 102::2 reflect-client Use the display bgp ipv6 routing-table c o m m a n d o n S w i t c h B a n d S w i t c h D ; b o t h o f t h e m l e a r n e d the network 1::/64. IPv6 BGP IPsec policy configuration example Network requirements As shown in the following figure,
351 • Configure IPv6 BGP on the switches. Switches A and B establish an IBGP relationship. Switches B and C establish an EBGP relationship. • Configure IPsec policies on the switches to authenticate and encrypt protocol packets. Figure 117 Network diagram Configuration procedure 1. Configure IP addresses for inte rfaces. (Details not shown.) 2. Configure the IBGP connection: # Configure Switch A. system-view [SwitchA] ipv6 [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] group ibgp internal [SwitchA-bgp-af-ipv6] peer 1::2 group ibgp [SwitchA-bgp-af-ipv6] quit [SwitchA-bgp] quit # Configure Switch B. system-view [SwitchB] ipv6 [SwitchB] bgp 65008 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] group ibgp internal [SwitchB-bgp-af-ipv6] peer 1::1 group ibgp [SwitchB-bgp-af-ipv6] quit [SwitchB-bgp] quit 3. Configure the EBGP connection: # Configure Switch C. system-view [SwitchC] ipv6 [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] group ebgp external [SwitchC-bgp-af-ipv6] peer 3::1 as-number 65008 [SwitchC-bgp-af-ipv6] peer 3::1 group ebgp