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+.
415 Task Remarks optimizing IPv6 MBGP networks Enabling the IPv6 MBGP orf capability Optional Configuring the maximum number of equal-cost routes for load-balancing Optional Configuring a large scale IPv6 MBGP network Configuring an IPv6 MBGP peer group Optional Configuring IPv6 MBGP community Optional Configuring an IPv6 MBGP route reflector Optional Configuring basic IPv6 MBGP functions Configuration prerequisites IPv6 MBGP is an application of multiprotocol BGP. Before you configure IPv6 MBGP, complete the following tasks: • Enable IPv6. • Configure network layer addresses for interfaces. • Complete BGP basic configuration. Configuring an IPv6 MBGP 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. Specify an IPv6 BGP peer and its AS number. peer ipv6-address as-number as-number Not configured by default. 5. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 6. Enable the IPv6 MBGP peer. peer ipv6-address enable Not enabled by default. Configuring a preferred value for routes from a peer or a peer group If you both reference a routing policy and use the command peer { ipv6-group-name | ipv6-address } preferred-value value to set a preferred value for routes from a peer or a peer group, the routing policy sets the specified preferred value for the routes that match it. Other routes that do not match the routing policy use the value set through the command. If the preferred value in the routing policy is 0, the routes that match it will also use the value set through the peer { ipv6-group-name | ipv6-address } preferred-value value command. To learn how to use a routing policy to set a preferred value, see the peer { ipv6-group-name | ipv6-address } route-policy route -policy-name { import | export } command and the apply preferred-value preferred-value command. For more information about these commands, see Layer 3—IP Routing Command Reference .
416 To configure a preferred value for routes from a peer or a 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 MBGP address family view. ipv6-family multicast N/A 4. Specify a preferred value for routes received from the IPv6 MBGP peer or the peer group. peer { ipv6-group-name | ipv6-address } preferred-value value Optional. The preferred value defaults to 0. Controlling route distribution and reception Configuration prerequisites Before you configure this task, complete the following tasks: • Enable IPv6. • Configure basic IPv6 MBGP functions. Injecting a local IPv6 MBGP route Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Inject a network into the IPv6 MBGP routing table. network ipv6-address prefix-length [ route-policy route-policy-name | short-cut ] Not injected by default. Configuring IPv6 MBGP route redistribution Step Command Description 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP multicast address family view. ipv6-family multicast N/A
417 Step Command Description 4. Enable default route redistribution into the IPv6 MBGP routing table. default-route imported Optional. By default, default route redistribution is not allowed. If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route. 5. Enable route redistribution from another routing protocol. import-route protocol [ process-id [ med med-value | route-policy route-policy-name ] * ] Not enabled by default. Configuring IPv6 MBGP route summarization To reduce the routing table size on medium and large BGP networks, you must configure route summarization on IPv6 MBGP routers. BGP supports only manual summarization of IPv6 multicast routes. To configure IPv6 MBGP route summarization: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure manual route summarization. aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ]* Not configured by default. Advertising a default route 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 MBGP address family view. ipv6-family multicast N/A 4. Advertise a default route to an IPv6 MBGP peer or peer group. peer { ipv6-group-name | ipv6-address } default-route-advertise [ route-policy route-policy-name ] Not advertised by default. With the peer default-route-advertise command executed, the router sends a default route with the next hop as itself to the specified IPv6 MBGP peer or the specified peer group, regardless of whether the default route is available in the routing table.
418 Configuring outbound IPv6 MBGP route filtering Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure outbound IPv6 MBGP route filtering. • Configure the filtering of outgoing routes: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export [ protocol process-id ] • Specify an IPv6 ACL to filter routes advertised to a peer or a peer group: peer { ipv6-group-name | ipv6-address } filter-policy acl6-number export • Specify an AS path ACL to filter IPv6 MBGP routing information advertised to a peer or a peer group: peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number export • Specify an IPv6 prefix list to filter routes advertised to a peer or a peer group: peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name export • Apply a routing policy to routes advertised to a peer or a peer group: peer { ipv6-group-name | ipv6-address } route-policy route -policy-name export Use any of the commands. No filtering is configured by default. You can configure filter policies as required. If you configure multiple filter policies, they are applied in the following order: 5. filter-policy export 6. peer filter-policy export 7. peer as-path-acl export 8. peer ipv6-prefix export 9. peer route-policy export A filter policy can be applied only after the previous one is passed. Routing information can be advertised only after passing all the configured filter policies. NOTE: • Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer group. • IPv6 BGP advertises the redistributed routes that pass the specified policy to the IPv6 MBGP peer. Configuring inbound IPv6 MBGP route filtering Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A
419 Step Command Remarks 4. Configure IPv6 MBGP inbound route filtering. • Configure inbound route filtering: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } import • Apply a routing policy to routes from a peer or a peer group: peer { ipv6-group-name | ipv6-address } route-policy route -policy-name import • Specify an IPv6 ACL to filter routes from a peer or a peer group: peer { ipv6-group-name | ipv6-address } filter-policy acl6-number import • S p e ci f y a n A S p a t h AC L t o f i l t e r I P v 6 B G P routing information from a peer or a peer group: peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number import • Specify an IPv6 prefix list to filter routes from a peer or a peer group: peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name import Use any of the commands By default, advertised routes are not filtered. You can configure a filtering policy as required. If you configure several filtering policies, they are applied in the following sequence: 5. filter-policy import 6. peer filter-policy import 7. peer as-path-acl import 8. peer ip-prefix import 9. peer route-policy import A filter policy can be applied only after the previous one is passed. Routing information can be received only after passing all the configured filter policies. 10. Specify the upper limit of prefixes that can be imported from a peer or a peer group. peer { ipv6-group-name | ipv6-address } route-limit limit [ percentage ] Optional. The number is unlimited by default. NOTE: A peer can have an inbound route filtering policy that is different from the policy of the peer group that it belongs to. That is, peer group members can have different inbound route filtering policies. Configuring IPv6 MBGP route dampening Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure IPv6 MBGP route dampening parameters. dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ]* Optional. Not configured by default. Configuring IPv6 MBGP route attributes This section describes how to use IPv6 MBGP route attr ibutes to affect IPv6 MBGP route selection. IPv6 MBGP route attributes involve:
420 • IPv6 MBGP protocol preference • Default LOCAL_PREF attribute • MED attribute • NEXT_HOP attribute • AS_PATH attribute Configuration prerequisites Before you configure IPv6 MBGP route attributes, complete the following tasks: • Enable IPv6. • Configure basic IPv6 MBGP functions. Configuring IPv6 MBGP route preferences Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure preferences for external, internal, and local IPv6 MBGP routes. preference { external-preference internal-preference local-preference | route-policy route-policy-name } Optional. The default preference values of external, internal, and local routes are 255, 255, and 130, respectively. Configuring the default local preference Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Set the default local preference. default local-preference value Optional. By default, the default local preference is 100. Configuring the MED attribute Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A
421 Step Command Remarks 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure a default MED value. default med med-value Optional. By default, the default med-value is 0. 5. Enable the comparison of the MED for routes from different ASs. compare-different-as-med Optional. Not enabled by default. 6. Enable the comparison of the MED for routes from each AS. bestroute compare-med Optional. Disabled by default. 7. Enable the comparison of the MED for routes from confederation peers. bestroute med-confederation Optional. Disabled by default. Configuring the next hop attribute You can use the peer next-hop-local command to specify the local router as the next hop of routes sent to a n I P v 6 mu l t ic as t I BG P p e e r o r a p e e r g ro u p. I f l o a d b a l a n ci ng i s c on fig u re d, t h e ro u te r s pe ci fies i t s e l f a s t h e n ex t h o p o f ro u te s s e nt t o t h e I P v 6 mu l t ic as t I BG P p e e r o r t h e p e e r g ro u p re g a rd l e s s of wh e t h e r t h e peer next-hop-local command is configured. In a third-party next-hop network, that is, the local router has two IPv6 multicast EBGP peers in a broadcast network, the router does not specify itself as the next hop of routes sent to the EBGP peers by default. To specify the router as the next hop of routes sent to a peer or a 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 MBGP address family view. ipv6-family multicast N/A 4. Configure the router as the next hop of routes sent to the peer or the peer group. peer { ipv6-group-name | ipv6-address } next-hop-local Optional. By default, IPv6 MBGP specifies the local router as the next hop for routes sent to an EBGP peer or a peer group, but not for routes sent to an IBGP peer or a peer group. Configuring the as_path attribute Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A
422 Step Command Remarks 4. Allow the local AS number to appear in the as-path of routes from a peer or a peer group and specify the number of times that the local AS number can appear in the as-path of routes from the peer or the peer group. peer { ipv6-group-name | ipv6-address } allow-as-loop [ number ] Optional. Not allowed by default. 5. Disable IPv6 MBGP from considering the as_path during best route selection. bestroute as-path-neglect Optional. Enabled by default. 6. Configure updates to a peer or a peer group to carry only the public AS number. peer { ipv6-group-name | ipv6-address } public-as-only Optional. By default, outbound IPv6 MBGP updates can carry private AS numbers. Tuning and optimizing IPv6 MBGP networks Configuration prerequisites Before you tune and optimize an OSPF network, complete the following tasks: • Enable IPv6. • Configure basic IPv6 MBGP functions. Configuring IPv6 MBGP soft reset After you modify a route selection policy, you must reset IPv6 MBGP connections to make the new one take effect. The current IPv6 MBGP implementation supports the route-refresh feature that enables dynamic route refresh without terminating IPv6 MBGP connections. If a peer that does not support route refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer. When the routing policy is changed, the system will update the IPv6 MBGP routing table and apply the new policy. Performing soft reset through route refresh If the peer is enabled with route refresh, when the IPv6 MBGP route selection policy is modified on a router, the router advertises a route -refresh message to its IPv6 MBGP peers, which resend their routing information to the router after they receive the message. Therefore, the local router can perform dynamic route update and apply the new policy with out terminating IPv6 MBGP connections. To configure IPv6 MBGP soft reset through route refresh: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A
423 Step Command Remarks 3. Enter IPv6 address family view. ipv6-family N/A 4. Enable IPv6 BGP route refresh for a peer or a peer group. peer { ipv6-group-name | ipv6-address } capability-advertise route-refresh Optional. Enabled by default. Performing soft reset manually If the peer does not support route refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv6 multicast command to soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without terminating IPv6 MBGP connections. To perform soft reset manually: 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. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 5. Keep all routes from a peer or a peer group regardless of whether they pass the inbound filtering policy. peer { ipv6-group-name | ipv6-address } keep-all-routes Not kept by default. 6. Perform soft reset manually. refresh bgp ipv6 multicast { all | ipv6-address | group ipv6-group-name | external | internal } { export | import } Optional. Enabling the IPv6 MBGP orf capability The BGP Outbound Route Filter (ORF) feature enables a BGP speaker to send a set of ORFs to its BGP peer through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the BGP spea ker, thus reducing the number of exchanged update messages and saving network resources. After you enable the ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through open messages. That is, the router determines whether to carry ORF information in messages, and if yes, whether to carry non-standar d ORF information in the packets. After completing the negotiation process and establishing the neighbor ing relationship, the BGP router and its BGP peer can exchange ORF information through specific route-refresh messages. For the parameters configured on both si des for ORF capability negotiation, see Tabl e 12. T o enable the IPv6 MBGP ORF capability: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A
424 Step Command Remarks 3. Enter IPv6 address family view. ipv6-family N/A 4. Enable BGP route refresh for a peer or a peer group. peer { group-name | ipv6-address } capability-advertise route-refresh Optional. Enabled by default. If this feature is not enabled, you must configure this command. 5. Enable the non-standard ORF capability for a BGP peer or a peer group. peer { group-name | ipv6-address } capability-advertise orf non-standard Optional. By default, standard BGP ORF capability defined in RFC 5291 and RFC 5292 is supported. If this feature is not enabled, you must configure this command. 6. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 7. Enable the ORF IP prefix negotiation capability for a BGP peer or a peer group. peer { group-name | ipv6-address } capability-advertise orf ip-prefix { both | receive | send } Not enabled by default. Table 12 Description of the send, receive, and bo th parameters and the negotiation result Local parameter Peer parameter Negotiation result send • receive • both The ORF sending capability is enabled locally and the ORF receiving capability is enabled on the peer. receive • send • both The ORF receiving capability is enabled locally and the ORF sending capability is enabled on the peer. both both Both the ORF sending and receiving capabilities are enabled locally and on the peer, respectively. Configuring the maximum number of equal-cost routes for load-balancing Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure the maximum number of equal-cost routes for load balancing. balance number By default, load ba lancing is disabled.