HP 5500 Ei 5500 Si Switch Series Configuration Guide

 362 
An IP prefix list is configured to match the destination address of routing information. You can use the 
gateway option to allow only routing information from certain routers to be received. For  gateway option 
information, see  Configuring RIP and Configuring OSPF .  
A

n IP prefix list, identified by name, can comprise multiple items. Each item, identified by an index 
n u m b e r,  c a n  s p e ci f y  a  p re f ix  r a n g e  t o  m a t c h.  A n  i t e m  wi t h  a  s m a l l e r  i n d e x...

 363 
Defining filters 
Configuration prerequisites 
Before you configure this task, you must determine IP-prefix list name, matching address range, and 
extcommunity list sequence number.  
Defining an IP-prefix list 
Defining an IPv4 prefix list 
Identified by name, an IPv4 prefix list can comprise multiple items. Each item specifies a prefix range to 
match and is identified by an index number.  
An item with a smaller index number is matched first. If one item is matched, the IP prefix list is...

 364 
Step Command Remarks 
2.  Define an IPv6 
prefix list.  ip ipv6-prefix 
ipv6-prefix-name  [ index  index-number  ] 
{  deny  | permit  } ipv6-address prefix-length 
[ greater-equal  min-prefix-length  ] [ less-equal 
max-prefix-length  ]  Not defined by default. 
 
If all items are set to the 
deny mode, no routes can pass the IPv6 prefix list. You must define the  permit :: 
0  less-equal 128 item following multiple  deny items to allow other IPv6 routing information to pass. 
For example, the...

 365 
Defining an extended community list 
You can define multiple items for an extended community list that is identified by number. During 
matching, the relation between items is logic OR. If routing information matches one of these items, it 
passes the extended community list. 
To define an extended community list: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Define an extended 
community list.  ip extcommunity-list
 ext-comm-list-number  { deny | 
permit  } { rt...

 366 
To create a routing policy:  
Step Command 
1.  Enter system view. 
system-view 
2.  Create a routing policy, 
specify a node for it, and 
enter routing policy view.  route-policy 
route-policy-name  { deny  | permit  } node  node-number  
 
Defining if-match clauses 
Follow these guidelines when you define  if-match clauses:  
•   The  if-match  clauses of a routing policy node are in logic AND relationship. Routing information 
must satisfy all of its  if-match clauses before being executed with...

 367 
Step Command Remarks 
5.  Match BGP routing information whose AS 
path attribute is specified in the AS path 
lists.  if-match as-path
 
AS-PATH-number &  Optional. 
Not configured by 
default. 
6.
  Match BGP routing information whose 
community attribute is specified in the 
community lists.   if-match community
 
{  {  basic-community-list-number  | 
comm-list-name  } [ whole-match  ] | 
adv-community-list-number  }& Optional. 
Not configured by 
default. 
7.
  Match routes having the specified...

 368 
Step Command Remarks 
6.  Set a cost for routing 
information.  apply cost
 [ + | - ] value   Optional. 
Not set by default. 
7.
  Set a cost type for routing 
information.  apply cost-type
 [ external  | internal 
|  type-1  | type -2  ]  Optional. 
Not set by default. 
8.
  Set the extended community 
attribute for BGP routing.  apply extcommunity
 { { rt 
route-target }& [  additive ] }
 
Optional. 
Not set by default. 
9.  Set the next hop. 
• Set the next hop for IPv4 routes: 
apply ip-address...

 369 
combined by the continue clause, the  apply clause configured on the last matching node takes 
effect.  
•   If you configure the  apply community clause for multiple nodes that are combined by the  continue 
clause, the  apply comm-list delete  clause configured on the current node cannot delete the 
community attributes of preceding nodes.  
To define a  continue clause: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create a routing policy and 
enter routing policy view....

 370 
Routing policy configuration examples 
Applying a routing policy to IPv4 route redistribution 
Network requirements 
As shown in Figure 119, S witch B exchanges routing information with Switch A using OSPF, and with 
Switch C using IS-IS. 
On Switch B, enable route redistribution from IS-IS to OSPF, and apply a routing policy to set the cost of 
route 172.17.1.0/24 to 100 and the tag of route 172.17.2.0/24 to 20. 
Figure 119  Network diagram 
 
 
Configuration procedure 
1. Specify IP addresses for...

 371 
 system-view 
[SwitchB] isis 
[SwitchB-isis-1] is-level level-2  
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00 
[SwitchB-isis-1] quit 
[SwitchB] interface vlan-interface 200 
[SwitchB-Vlan-interface200] isis enable 
[SwitchB-Vlan-interface200] quit 
3. Configure OSPF and route redistribution: 
# Configure OSPF on Switch A. 
 system-view 
[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]...