Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    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+.

    View all the pages
    Page
    of 2513
    Add page 1361 to Favourites
    image text
    Enable zoom 
    							 225 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Advertise a default route to an 
MBGP peer or peer group.  peer { group-name |
 ip-address } 
default-route-advertise 
[ route-policy  route-policy-name ]  Not advertised by default. 
 
 
NOTE: 
With the peer  default-route-advertise  command executed, the router sends a default route with the next
hop as itself to the specified MBGP  peer or peer group, whether the defa ult route is available or not in the
routing table. 
 
Configuring outbound MBGP route filtering 
If several filtering policies are configured,  they are applied in the following sequence: 
1. filter-policy export 
2. peer filter-policy export 
3. peer as-path-acl export 
4. peer ip-prefix export 
5. peer route-policy export 
Only the routes that have passed all the configured policies can be advertised. 
To configure BGP route distribution filtering policies: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A
    Add page 1362 to Favourites
    image text
    Enable zoom 
    							 226 
Step Command Remarks 
4.  Configure BGP route 
distribution filtering policies. 
• Configure the filtering of redistributed 
routes:  
filter-policy  { acl-number  |  ip-prefix  
ip-prefix-name  }  export [ direct |  isis 
process-id  | ospf process-id  | rip 
process-id  | static ] 
• Apply a routing policy to 
advertisements to an IPv4 MBGP peer 
or a peer group:  
peer {  group-name  | peer-address  } 
route-policy  route -policy-name  export
 
•  Reference an ACL to filter 
advertisements to an IPv4 MBGP peer 
or a peer group:  
peer { group-name  | ip-address  } 
filter-policy  acl-number  export 
•  Reference an AS path ACL to filter 
route advertisements to an IPv4 MBGP 
peer or a peer group:  
peer { group-name  | ip-address  } 
as-path-acl  as-path-acl-number  export
 
•  Reference an IP prefix list to filter route 
advertisements to an IPv4 MBGP peer 
or a peer group:  
peer { group-name  | ip-address  } 
ip-prefix  ip-prefix-name  export  Use one of these commands
 
No outbound route filtering 
is configured by default. 
 
Configuring inbound MBGP route filtering 
By configuring MBGP route reception filtering policies, you can filter out unqualified routes from an 
MBGP peer or peer group. Members of a peer group 
can have different route reception filtering policies 
from the peer group. 
If several filtering policies are configured,  they are applied in the following sequence: 
1. filter-policy import 
2. peer filter-policy import 
3. peer as-path-acl import 
4. peer ip-prefix import 
5. peer route-policy import 
Only the routes that have passed all the configured policies can be advertised. 
To configure MBGP route reception filtering policies: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A
    Add page 1363 to Favourites
    image text
    Enable zoom 
    							 227 
Step Command Remarks 
4.  Configure MBGP route 
reception filtering policies. 
• Filter incoming routes using an 
ACL or IP prefix list: 
filter-policy  { acl-number  | 
ip-prefix  ip-prefix-name  } 
import  
• Reference a routing policy to 
routes from an IPv4 MBGP peer 
or a peer group: 
peer { group-name  | 
ip-address  } route-policy  
policy-name  import  
• Reference an ACL to filter 
routing information from an 
IPv4 MBGP peer or a peer 
group: 
peer { group-name  | 
ip-address  } filter-policy  
acl-number  import  
• Reference an AS path ACL to 
filter routing information from 
an IPv4 MBGP peer or a peer 
group: 
peer { group-name  | 
ip-address  } as-path-acl  
as-path-acl-number  import  
• Reference an IP prefix list to 
filter routing information from 
an IPv4 MBGP peer or a peer 
group: 
peer { group-name  | 
ip-address  } ip-prefix  
ip-prefix-name  import   Use one of these command 
No inbound route filtering is 
configured by default. 
5.
  Specify the maximum number 
of routes that can be received 
from an IPv4 MBGP peer or a 
peer group.  peer {
 group-name  | ip-address  } 
route-limit  limit [ percentage  ]  Optional 
The number is unlimited by default.
 
 
Configuring MBGP route dampening 
By configuring MBGP route dampening, you can suppress unstable routes from being added to the 
MBGP routing table or being advertised to MBGP peers. 
To configure BGP route dampening: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A
    Add page 1364 to Favourites
    image text
    Enable zoom 
    							 228 
Step Command Remarks 
4.  Configure BGP route 
dampening parameters.  dampening
 [ half-life-reachable 
half-life-unreachable reuse 
suppress ceiling  | route-policy  
route-policy-name  ] *  Not configured by default. 
 
Configuring MBGP route attributes 
You can modify MBGP route attributes to affect route selection. 
Configuration prerequisites 
Before you configure this task, you need to configure basic MBGP functions. 
Configuring MBGP route preferences 
You can reference a routing policy to set preferences for routes matching it. Routes not matching it use the 
default preferences. 
To configure 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 IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Configure preferences for 
external, internal, and local 
MBGP routes.  preference { external-preference 
internal-preference 
local-preference 
| route-policy  
route-policy-name  }  Optional. 
The default preferences of 
multicast MBGP EBGP, MBGP 
IBGP, and local MBGP 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 IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Configure the default local 
preference.  default local-preference 
value  Optional. 
100 by default.
    Add page 1365 to Favourites
    image text
    Enable zoom 
    							 229 
Configuring the MED attribute 
When other conditions of routes to a destination are identical, the route with the smallest MED is 
selected. 
To configure the MED attribute: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Configure the default MED 
value.  default med 
med-value  Optional. 
0 by default. 
5.
  Enable the comparison of the 
MED of routes from different 
ASs.  compare-different-as-med 
Optional. 
Not enabled by default. 
6.
  Enable the  comparison of the 
MED of routes from each AS.  bestroute compare-med  Optional. 
Not enabled by default. 
7.
  Enable the comparison of the 
MED of routes from 
confederation peers.  bestroute med-confederation 
Optional. 
Not enabled 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 an MBGP IBGP peer or peer group. If load balanci ng is configured, the router specifies itself as the 
next hop of route advertisements to the multicast IB GP peer or peer group regardless of whether the peer 
next-hop-local command is configured. 
In a third-party next-hop network (that is, when the local router has two multicast EBGP peers in a 
broadcast network), the router does not specify itself as the next hop of routing information sent to the 
EBGP peers unless the  peer next-hop-local command is configured. 
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 IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Specify the router as the next 
hop of routes sent to a peer or 
a peer group.  peer { group-name |
 ip-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 MBGP IBGP peer or a peer 
group.
    Add page 1366 to Favourites
    image text
    Enable zoom 
    							 230 
Configuring the AS-PATH attributes 
In general, MBGP checks whether the AS-PATH attribute of a route from a peer contains the local AS 
number. If it does, it discards the route to avoid routing loops. 
To configure the AS-PATH attributes: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
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 
{ group-name |  ip-address } 
allow-as-loop  [ number ]  Optional. 
By default, the local AS number 
cannot appear in routes from a 
peer or a peer group. 
5.
  Disable BGP from considering 
the AS_PATH during best 
route selection.  bestroute as-path-neglect  Optional. 
By default, BGP considers 
AS_PATH during best route 
selection. 
6.
  Configure updates to a peer 
or a peer group not to keep 
private AS numbers.  peer { group-name | 
ip-address } 
public-as-only   Optional. 
By default, BGP updates carry 
private AS numbers. 
 
Tuning and optimizing MBGP networks 
This task involves resetting MBGP connections and configuring load balancing.  
Configuration prerequisites 
You need to configure basic MBGP functions before configuring this task. 
Configuring MBGP soft reset 
After modifying a route selection policy, you have to 
reset MBGP connections to make it take effect.  
The current MBGP implementation supports the route refresh feature that enables dynamic route refresh 
without terminating MBGP connections. 
However, if a peer that does not support route refr esh 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 updates the MBGP routing table and applies the new policy. 
Performing soft reset through route refresh 
If the peer is enabled with route refresh, when the MBGP route selection policy is modified on a router, 
the router advertises a route -refresh message to its MBGP peers, which resend their routing information
    Add page 1367 to Favourites
    image text
    Enable zoom 
    							 231 
to the router after receiving the message. Therefore, the local router can perform dynamic route update 
and apply the new policy without terminating MBGP connections. 
To perform 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 
3.  Enable BGP route refresh for a 
peer or a peer group.  peer { group-name
 | ip-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 ipv4 multicast command to soft-reset MBGP 
connections to refresh the MBGP routing table an d apply the new policy without terminating MBGP 
connections. 
To perform a manual soft reset: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Disable BGP route refresh and 
multiprotocol extensions for a 
peer or a peer group.  peer { group-name
 | ip-address } 
capability-advertise conventional  Optional. 
Enabled by default. 
4.
  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
5.  Keep all original routes from a 
peer or a peer group 
regardless of whether they 
pass the inbound filtering 
policies.  peer { group-name
 | ip-address } 
keep-all-routes   Not kept by default. 
6.
  Return to user view. 
return  N/A 
7.  Soft-reset MBGP connections 
manually.  refresh bgp ipv4 multicast 
{ all  | 
ip-address |  group group-name  | 
external  | internal  } { export  | 
import  }  Optional. 
 
Enabling the MBGP ORF capability 
The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its 
MBGP 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  MBGP speaker, reducing update messages and saving 
network resources.  
After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the 
BGP peer through Open messages. That is, the BGP router determines whether to carry ORF information 
in messages and, if so, whether to carry nonstan dard ORF information in the packets. After completing
    Add page 1368 to Favourites
    image text
    Enable zoom 
    							 232 
the negotiation process and establishing the neighboring 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  7. 
T

o enable the MBGP ORF capability:  
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enable BGP route refresh for a 
peer or a peer group.  peer { group-name
 | ip-address  } 
capability-advertise route-refresh  Optional. 
Enabled by default. 
If this feature is not enabled, you 
need to configure this 
command.  
For more information about the 
command, see 
Layer 3—IP 
Routing Command Reference .  
4.  Enable the non-standard BGP 
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 
need to configure this 
command.  
For more information about the 
command, see  Layer 3—IP 
Routing Command Reference . 
5.  Enter MBGP address family 
view.  ipv4-family multicast 
N/A 
6.  Enable the ORF IP prefix 
negotiation capability for an 
MBGP peer or a peer group.  peer { group-name
 | ip-address  } 
capability-advertise orf ip-prefix  
{  both |  receive | send  }  Optional. 
Not enabled by default. 
 
Table 7
 Description of the both, send, and receive 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 MBGP routes for load 
balancing
    Add page 1369 to Favourites
    image text
    Enable zoom 
    							 233 
Step Command Remarks 
1.  Enter system view. 
system-view N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast
 N/A 
4.  Configure the maximum 
number of MBGP routes for 
load balancing.  balance 
number  Not configured by default. 
 
Configuring a large scale MBGP network 
Configuration prerequisites 
Before you configure this task, you must make peering nodes accessible to each other at the network 
layer. 
Configuring IPv4 MBGP peer groups 
In a large-scale network, configuration and maintenance become difficult because of large numbers of 
MBGP peers. You can configure peer groups to make management easier and improve route distribution 
efficiency.  
 
 IMPORTANT: 
•
  To configure an MBGP peer group, you must enable the correspondin
g IPv4 BGP unicast peer group in
IPv4 MBGP address family view. 
•   Before adding an MBGP peer to an MBGP peer group, you must add the corresponding IPv4 unicast 
peer to the IPv4 BGP peer group. 
 
To configure an IPv4 MBGP peer group:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Create a BGP peer group.  group
 group-name  [ external | 
internal  ]  Not created by default. 
4.
  Add a peer into the peer 
group.  peer 
ip-address  group  group-name  
[ as-number  as-number  ]  No peer is added by default. 
5.
  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
6.  Enable the IPv4 unicast peer 
group.  peer 
group-name  enable  N/A 
7.  Add an IPv4 MBGP peer to 
the peer group.  peer 
ip-address  group  group-name Not configured by default.
    Add page 1370 to Favourites
    image text
    Enable zoom 
    							 234 
Configuring MBGP community 
The community attribute can be advertised between MBGP peers in different ASs. Routers in the same 
community share the same policy. 
You can reference a routing policy to modify the community attribute for routes sent to a peer. In addition, 
you can define extended community attributes as needed. 
When you configure MBGP community, you must reference a routing policy to define the specific 
community attributes, and apply the routing policy for route advertisement. For routing policy 
configuration, see  Layer 3—IP Routing Configuration Guide . 
To configure MBGP community: 
 
Step Command Remarks 
1.   Enter system view. system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast
 N/A 
4.  Advertise the community 
attribute to an MBGP peer or 
a peer group. 
• Advertise the community attribute to an 
MBGP peer or a peer group: 
peer {  group-name  | ip-address  } 
advertise-community  
• Advertise the extended community attribute 
to an MBGP peer or a peer group: 
peer {  group-name  | ip-address  } 
advertise-ext-community  Use either command 
Not configured by 
default. 
5.
  Apply a routing policy to 
routes advertised to an MBGP 
peer or a peer group.  peer {
 group-name  | ip-address  } route-policy 
route-policy-name  export  Not configured by 
default. 
 
Configuring an MBGP route reflector 
To guarantee the connectivity between multicast IBGP peers in an AS, you need to make them fully 
meshed. But this becomes unpractical when large numbers of multicast IBGP peers exist. Configuring 
route reflectors can solve this problem.  
In general, it is not required that clients of a route reflector be fully meshed. The route reflector forwards 
routing information between clients. If clients are fully meshed, you can disable route reflection between 
clients to reduce routing costs. 
In general, a cluster has only one route reflector, and the router ID of the route reflector identifies the 
cluster. You can configure multiple route reflectors to improve network stability. In this case, you need to 
specify the same cluster ID for these route reflectors to avoid routing loops. 
To configure an MBGP route reflector:
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide