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 831 to Favourites
    image text
    Enable zoom 
    							 142 
A  h o s t  n a m e  i s  e a s i e r  t o  r e m e m b e r  t h a n  a  s y s t e m  I D.  After enabling this feature on the router, you can see 
the host names instead of system IDs using the  display command. 
BFD 
Bidirectional forwarding detection (BFD) provides a si ngle mechanism to quickly detect any link failures 
between IS-IS neighbors to reduce network conver gence time. For more information about BFD, see High 
Availability Configuration Guide . 
Protocols and standards 
•  ISO 10589 ISO IS-IS Routing Protocol  
•   ISO 9542 ES-IS Routing Protocol  
•   ISO 8348/Ad2 Network Services Access Points 
•   RFC 1 19 5 ,  Use of OSI IS-IS for Routing in TCP/IP and Dual Environments  
•   RFC 2763,  Dynamic Hostname Exchange Mechanism for IS-IS  
•   RFC 2966,  Domain-wide Prefix Distribution with Two-Level IS-IS  
•   RFC 3277,  IS-IS Transient Blackhole Avoidance  
•   RFC 3358,  Optional Checksums in ISIS  
•   RFC 3373,  Three-Way Handshake for IS-IS Point-to-Point Adjacencies  
•   RFC 3567,  Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication  
•   RFC 3719,  Recommendations for Interoperable Networks using IS-IS 
•   RFC 3786,  Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit  
•   R F C  3787,   Recommendations for Interoperable IP Networks using IS-IS  
•   RFC 3784,  IS-IS extensions for Traffic Engineering  
•   RFC 3847,  Restart signaling for IS-IS  
IS-IS configuration task list 
 
Task  Remarks 
Configuring IS-IS 
basic functions Enabling IS-IS  
Required Configuring the IS level and circuit level Required 
Configuring the network type of an interface as P2P Required 
Configuring IS-IS 
routing information 
control Configuring IS-IS link cost  
Optional 
Specifying a priority for IS-IS Required 
Configuring the maximum number of ECMP routes  Optional 
Configuring IS-IS route summarization  Optional 
Advertising a default route Optional 
Configuring IS-IS route redistribution Optional 
Configuring IS-IS route filtering  Optional 
Configuring IS-IS route leaking Optional 
Tuning and Specifying intervals for sending IS-IS hello and CSNP packets 
Optional
    Add page 832 to Favourites
    image text
    Enable zoom 
    							 143 
Task  Remarks 
optimizing IS-IS 
networks Specifying the IS-IS hello multiplier 
Optional 
Configuring a DIS priority for an interface Optional 
Disabling an interface from sending or receiving IS-IS packets Optional 
Enabling an interface to send small hello packets Optional 
Configuring LSP parameters Optional 
Configuring SPF parameters Optional 
Assigning a high priority to IS-IS routes Optional 
Setting the LSDB overload bit Optional 
Configuring system ID to host name mappings Optional 
Enabling the logging of neighbor state changes Optional 
Enhancing IS-IS 
network security Configuring neighbor rela
tions
 hip authentication  Optional 
Configuring area authentication  Optional 
Configuring routing domain authentication Optional 
Configuring IS-IS GR  Optional 
Configuring IS-IS NSR Optional 
Configuring IS-IS FRR Optional 
Enabling IS-IS SNMP trap Optional 
Binding an IS-IS process with MIBs Optional 
Configuring BFD for IS-IS Optional 
 
Configuring IS-IS basic functions 
Configuration prerequisites 
Before you configure IS-IS basic functions, complete the following tasks: 
•  Configure the link layer protocol. 
•   Configure an IP address for each interface, and make sure all neighboring nodes can reach each 
other at the network layer. 
Enabling IS-IS  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enable the IS-IS routing 
process and enter its view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  Not enabled by default. 
3.
  Assign a network entity title 
(NET).  network-entity 
net  Not assigned by default. 
4.  Return to system view. 
quit  N/A
    Add page 833 to Favourites
    image text
    Enable zoom 
    							 144 
Step Command Remarks 
5.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
6.
  Enable an IS-IS process on the 
interface.  isis enable
 [ process-id  ]  Disabled by default. 
 
Configuring the IS level and circuit level 
If only one area is available, HP recommends you to perform the following operations: 
•  Configure the IS level of all routers as Level-1 or Level-2 rather than different levels because the 
routers do not need to maintain two identical LSDBs.  
•   Configure the IS level as Level-2 on all routers in an IP network for scalability. 
For an interface of a Level-1 (or Level-2) router, the circuit level can only be Level-1 (or Level-2). For an 
interface of a Level-1-2 router, the default circuit level is Level-1-2; if the router only needs to form Level-1 (or 
Level-2) neighbor relationships, then configure the circuit level for its interfaces as Level-1 (or Level-2) to 
limit neighbor relationship establishment. 
To configure the IS level and circuit level: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A 
3.
  Specify the IS level.  is-level 
{ level-1  | level-1-2 | 
level-2  }  Optional. 
The default is Level-1-2. 
4.
  Return to system view. 
quit  N/A 
5.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
6.
  Specify the circuit level.  isis circuit-level 
[ level-1  | level-1-2  
|  level-2  ]  Optional. 
By default, an interface can establish 
the Level-1 or Level-2 adjacency. 
 
 
Configuring the network type of an interface as P2P 
Perform this task only for a broadcast network that has up to two attached routers. 
Interfaces with different network types operate differently. For example, broadcast interfaces on a 
network must elect the DIS and flood CSNP packets to  synchronize the LSDBs, but P2P interfaces on a 
network do not need to elect the DIS, and have  a different LSDB synchronization mechanism. 
If only two routers exist on a broadcast network, conf igure the network type of attached interfaces as P2P 
to avoid DIS election and CSNP flooding, saving network bandwidth and speeding up network 
convergence. 
To configure the network type of an interface:
    Add page 834 to Favourites
    image text
    Enable zoom 
    							 145 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter interface view.   interface
 interface-type 
interface-number   N/A 
3.
  Configure the network type for the 
interface as P2P.  isis circuit-type p2p  Optional. 
By default, the 
network type of an 
interface depends on 
the physical media. 
The network type of a 
VLAN interface is 
broadcast. 
Configuring IS-IS routing information control 
Configuration prerequisites 
Before configuring IS-IS routing information control, complete the following tasks: 
•
  Configure network layer addresses for interfaces, and make sure that adjacent nodes can reach 
each other at the network layer. 
•   Enable IS-IS. 
Configuring IS-IS link cost 
The IS-IS cost of an interface is determined in the following order: 
1. IS-IS cost specified in interface view. 
2. IS-IS cost specified in system view. The cost is  applied to the interfaces associated with the IS-IS 
process. 
3.  Automatically calculated cost. If  the cost style is wide  or wide-compatible, IS-IS automatically 
calculates the cost using the formula: interfac e cost = (bandwidth reference value/interface 
bandwidth) ×10, which is in the range of 1 to 16777214. For other cost styles,  Table 6 applies.
  
Table 6  Automatic cost calculation scheme for cost  styles other than wide and wide-compatible 
Interface bandwidth  Interface cost
 
≤ 10 Mbps  60 
≤ 100 Mbps
  50 
≤ 155 Mbps 
40 
≤ 622 Mbps 30 
≤ 2500 Mbps
  20 
> 2500 Mbps
  10 
 
4.
 If none of the above costs are used , a default cost of 10 applies.  
Configuring an IS-IS cost for an interface
    Add page 835 to Favourites
    image text
    Enable zoom 
    							 146 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Specify an IS-IS cost style.  cost-style
 { narrow  | wide  | wide-compatible  
| { compatible  | narrow-compatible  } 
[ relax-spf-limit  ] }  Optional. 
narrow
 by default.  
4.  Return to system view. 
quit  N/A 
5.  Enter interface view.  
interface  interface-type interface-number N/A 
6.   Specify a cost for the 
interface.  isis cost 
value [ level-1  | level-2  ]  Optional. 
No cost is specified for the 
interface by default. 
 
Configuring a global IS-IS cost 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  
isis [ process-id  ] [ vpn-instance  vpn-instance-name  ]N/A
 
3.  Specify an IS-IS 
cost style.  cost-style
 { narrow  | wide  | wide-compatible  | 
{  compatible  | narrow-compatible  } 
[ relax-spf-limit  ] }  Optional. 
narrow
 by default.  
4.  Specify a global 
IS-IS cost.  circuit-cost 
value [ level-1  | level-2  ]  By default, no global cost is 
specified.  
 
Enabling automatic IS-IS cost calculation 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Specify an IS-IS cost style. 
cost-style { wide | wide-compatible  } narrow by default.  
4.  Enable automatic IS-IS cost 
calculation.  auto-cost enable 
Disabled by default. 
5.  Configure a bandwidth 
reference value for 
automatic IS-IS cost 
calculation.  bandwidth-reference 
value  Optional. 
100 Mbps by default.  
 
Specifying a priority for IS-IS 
A router can run multiple routing protocols. When ro
utes to the same destination are found by multiple 
routing protocols, the route learned by the protocol  with the highest priority can be adopted. You can 
reference a routing policy to specify a priority for specific routes. For information about routing policy, 
see  Configuring routing policies .
    Add page 836 to Favourites
    image text
    Enable zoom 
    							 147 
To configure the priority of IS-IS:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  
isis [ process-id  ] [ vpn-instance  vpn-instance-name  ]
  N/A 
3.
  Specify a priority for IS-IS.  preference { route-policy 
route-policy-name | 
preference  } *  15 by default. 
 
Configuring the maximum number of ECMP routes 
Perform this task to implement load sharing over ECMP routes. 
To configure the maximum number of ECMP routes: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.   isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Specify the maximum number 
of ECMP routes for load 
balancing.  maximum load-balancing 
number  8 by default. 
 
Configuring IS-IS route summarization 
T h i s  t a s k  a l l o w s  y o u  t o  c o n f i g u r e  a  s u m m a r y  r o u t e  s o  r o u t e s  f a l l i n g  i n t o  t h e  n e t w o r k  r a n g e  o f  t h e  s u m m a r y  
route are summarized into one route for advertisement. Doing so can reduce the size of routing tables, as 
well as the scale of LSP and LSDB. Both IS-IS rout es and redistributed routes can be summarized. 
The router summarizes only the routes in the locally generated LSPs. The cost of the summary route is the 
lowest one among the costs of summarized routes. 
To configure route summarization: 
 
Step Command  Remarks 
1.  Enter system 
view.  system-view 
N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Configure IS-IS 
route 
summarization.  summary 
ip-address  { mask  | mask-length } 
[ avoid-feedback |  generate_null0_route  | tag 
tag  | [ level-1  | level-1-2  | level-2  ] ] *  By default, no route summarization 
is configured. 
 
Advertising a default route 
A router running IS-IS cannot redistribute any default routes or advertise a default route to neighbors. Use 
the following commands to advertise a default route of 0.0.0.0/0 to the same level neighbors.
    Add page 837 to Favourites
    image text
    Enable zoom 
    							 148 
The default route is only advertised to routers at the same level. You can use a routing policy to generate 
the default route only when a local routing entry is matched by the policy. 
To advertise a default route: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Advertise a default 
route.  default-route-advertise 
[ route-policy 
route-policy-name  | [ level-1 | level-1-2 | 
level-2  ] ] *  By default, the function is disabled. 
 
Configuring IS-IS route redistribution 
Redistributing large numbers of routes on a device may affect the performance of other devices in the 
network. If this happens, you can configure a limit on 
the number of redistributed routes in order to limit 
the number of routes to be advertised.  
Only active routes can be redistributed. Use the  display ip routing-table protocol  command to display 
route state information.  
To configure IS-IS route redistribution from other routing protocols: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Redistribute routes 
from another 
routing protocol.  import-route 
protocol [ process-id  | 
all-processes  |  allow-ibgp  ] [ cost cost  | 
cost-type  { external |  internal } | [  level-1  | 
level-1-2 |  level-2 ] | route-policy  
route-policy-name  | tag  tag ] *  By default: •
 No route is redistributed. 
• If no level is specified, routes 
are redistributed into the Level-2 
routing table. 
4.   Configure the 
maximum number 
of redistributed 
Level 1/Level 2 
IPv4 routes.  import-route limit number
   Optional.  
The default varies with devices. 
 
Configuring IS-IS route filtering 
You can reference a configured ACL, IP prefix list, or routing policy to filter routes calculated from the 
received LSPs and the routes redistributed from other routing protocols. 
Filtering routes calculated from received LSPs 
IS-IS saves the LSPs received from neighbors in the LSDB, uses the SPF algorithm to calculate the shortest 
path tree with itself as the root, and installs the routes into the IS-IS routing table. 
By referencing a configured ACL, IP prefix list, or routing policy, you can filter the calculated routes. Only 
the routes matching the filter can be
 added into the IS-IS routing table.
    Add page 838 to Favourites
    image text
    Enable zoom 
    							 149 
To filter routes calculated from received LSPs:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Filter routes calculated 
from received LSPs.  filter-policy { acl-number
 | ip-prefix  
ip-prefix-name  | route-policy  route-policy-name  } 
import   By default, no filtering is 
configured. 
 
Filtering redistributed routes 
IS-IS can redistribute routes from other routing protoc
ols (or other IS-IS processes), add them into the IS-IS 
routing table, and advertise them in LSPs. 
By reference a configured ACL, IP prefix list, or routing policy, you can filter redistributed routes and only 
the routes matching the filter can be added into the  IS-IS routing table and advertised to neighbors.  
To configure the filtering of redistributed routes: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.   isis
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
3.  Configure the filtering of 
routes redistributed from 
another routing protocol or 
IS-IS process.  filter-policy { acl-number
 | ip-prefix  
ip-prefix-name  | route-policy  
route-policy-name  } export  [ protocol 
[ process-id  ] ]  Not configured by 
default. 
 
Configuring IS-IS route leaking 
With IS-IS route leaking enabled, the Level-1-2 router can advertise the routing information of other Level-1 
areas and Level-2 area routing information to Level-1 routers.  
If a filter policy is specified, only routes 
passing it can be advertised into Level-1 area. 
You can specify a routing policy in the import-route isis level-2 into level-1  c o m m a nd  to  fi l te r  ro u tes  fro m  
Level-2 to Level-1. Other routing policies specified for  route reception and redistribution does not affect the 
route leaking. 
To configure IS-IS route leaking: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter IS-IS view.  
isis [ process-id  ] [ vpn-instance  vpn-instance-name  ]
  N/A
 
3.  Enable IS-IS route 
leaking.  import-route isis level-2 into level-1 
[ filter-policy 
{  acl-number  |  ip-prefix  ip-prefix-name  | route-policy  
route-policy-name  } | tag  tag ] *  Disabled by 
default.
    Add page 839 to Favourites
    image text
    Enable zoom 
    							 150 
Tuning and optimizing IS-IS networks 
Configuration prerequisites 
Before you tune and optimize IS-IS networks, complete the following tasks: 
•   Configure IP addresses for interfaces, and make  adjacent nodes can reach each other at the 
network layer. 
•   Enable IS-IS. 
Specifying intervals for sending IS-IS hello and CSNP packets  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number   N/A
 
3.  Specify the interval for 
sending hello packets.  isis timer hello 
seconds [  level-1 |  
level-2  ]  Optional. 
10 seconds by default. 
4.
  Specify the interval for 
sending CSNP packets on the 
DIS of a broadcast network.  isis timer csnp 
seconds [  level-1 | 
level-2  ]  Optional. 
10 seconds by default. 
 
 
NOTE: 
The interval between hello packets sent by the DIS is 1/3 the hello interval set with the  isis timer hello 
command. 
 
Specifying the IS-IS hello multiplier 
If a neighbor receives no hello packets from the router within the advertised hold time, it considers the 
router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello 
interval. 
On a broadcast link, Level-1 and Level-2 hello packets  are advertised separately; therefore, you need to 
set a hello multiplier for each level.  
On a P2P link, Level-1 and Level-2 hello packets are advertised in P2P hello packets, so you do not need 
to specify Level-1 or Level-2. 
To specify the IS-IS hello multiplier: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter interface view.   interface
 interface-type 
interface-number   N/A
 
3.  Specify the number of hello packets a 
neighbor must miss before declaring 
the router is down.  isis timer holding-multiplier
 value  
[ level-1  | level-2  ]  Optional. 
3 by default.
    Add page 840 to Favourites
    image text
    Enable zoom 
    							 151 
Configuring a DIS priority for an interface 
On an IS-IS broadcast network, you must elect a router as the DIS at a routing level. You can specify a 
DIS priority at a level for an interface. The greater the interface’s priority, the more likely it becomes the 
DIS. If multiple routers in the broadcast network have the same highest DIS priority, the router with the 
highest MAC address becomes the DIS. 
To specify a DIS priority 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.  Specify a DIS priority for the 
interface.  isis dis-priority 
value [ level-1 | 
level-2  ]  Optional. 
64 by default. 
 
Disabling an interface from sending or receiving IS-IS packets 
After being disabled from sending or receiving he
llo packets, an interface cannot form a neighbor 
relationship, but can advertise directly connected networks in LSPs through other interfaces. This can save 
bandwidth and CPU resources, and ensures other routers know networks directly connected to the 
interface.  
To disable an interface from sending and receiving IS-IS packets: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number   N/A
 
3.  Disable the interface from 
sending and receiving IS-IS 
packets.  isis silent 
Not disabled by default. 
 
Enabling an interface to send small hello packets 
IS-IS messages cannot be fragmented at the IP layer  because they are directly encapsulated into frames. 
Any two IS-IS neighboring routers must negotiate a co mmon MTU. To avoid sending big hellos for saving 
bandwidth, enable the interface to send small hello packets without CLVs.  
To enable an interface to send small hello packets: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
3.
  Enable the interface to send 
small hello packets without 
CLVs.  isis small-hello 
Standard hello packets are sent by 
default.
    All HP manuals Comments (0)

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