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+.
82 calculated cost is greater than 65535, the value of 65535 is used. If the calculated cost is less than 1, the value of 1 is used. If the cost value is not configured for an interfac e, OSPF computes the interface cost automatically. To configure an OSPF cost 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. Configure an OSPF cost for the interface. ospf cost value Optional. The default cost depends on the interface type: 1 for a VLAN interface; 0 for a loopback interface; computed according to the bandwidth for other interfaces. To configure a bandwidth reference value: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a bandwidth reference value. bandwidth-reference value Optional. The value defaults to 100 Mbps. Configuring the maximum number of OSPF routes Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the maximum number of OSPF routes. maximum-routes { external | inter | intra } number Optional. The number varies with devices. 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
83 Step Command Remarks 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the maximum number of ECMP routes. maximum load-balancing maximum Optional. 8 by default. Configuring OSPF preference A router can run multiple routing protocols, and each protocol is assigned a preference. When the routing protocols find routes to the same destinatio n, the route found by the protocol with the highest preference is selected as the best route. To configure OSPF preference: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure a preference for OSPF. preference [ ase ] [ route-policy route-policy-name ] value Optional. By default, the preference of OSPF internal routes is 10, and the preference of OSPF external routes is 150. Configuring OSPF route redistribution This section describes configuring OSPF to redistribute manually configured routes or routes discovered by other routing protocols. Only active routes can be redistributed. Use the display ip routing-table protocol c o m m a n d t o vi ew ro u t e state information. Configuring route redistribution into OSPF On a router running OSPF and other routing protocol s, you can configure OSPF to redistribute routes from other protocols such as RIP, IS-IS, BGP, static, and direct routes, and advertise them in Type-5 LSAs or Type-7 LSAs. By filtering redistributed routes, OSPF translates only permitted routes into Type-5 LSAs or Type-7 LSAs for advertisement. To configure OSPF route redistribution: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A
84 Step Command Remarks 3. Configure OSPF to redistribute routes from another protocol. import-route protocol [ process-id | all-processes | allow-ibgp ] [ cost cost | type type | tag tag | route-policy route-policy-name ] * Not configured by default 4. Configure OSPF to filter redistributed routes before advertisement. filter-policy { acl-number | ip-prefix ip-prefix-name } export [ protocol [ process-id ] ] Optional Not configured by default Configuring OSPF to redistribute a default route Using the import-route command cannot redistribute a default external route. To do so, you must use the default-route-advertise command. To configure OSPF to redistribute a default external route: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Redistribute a default route. default-route-advertise [ [ [ always | permit-calculate-other ] | cost cost | route-policy route-policy-name | type type ] * | summary cost cost ] Not redistributed by default. The default-route-advertise summary cost command is applicable only to VPN, and the default route is redistributed in a Type-3 LSA. The PE router advertises the default route to the CE router. Configuring the default parameters for redistributed routes You can configure default parameters, such as the cost , upper limit, tag and type for redistributed routes. Tags indicate information related to protocols. For example, when redistributing BGP routes, OSPF uses tags to identify AS IDs. To configure the default parameters for redistributed routes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A
85 Step Command Remarks 3. Configure the default parameters for redistributed routes (cost, route number, tag, and type). default { cost cost | limit limit | tag tag | type type } * Optional. The default cost is 1, the default maximum number of routes redistributed per time is 1000, the default tag is 1, and default type of redistributed routes is Type-2. Advertising a host route Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enter area view. area area-id N/A 4. Advertise a host route. host-advertise ip-address cost Optional. Not advertised by default. Tuning and optimizing OSPF networks You can optimize your OSPF network in the following ways: • Change OSPF packet timers to adjust the OSPF network convergence speed and network load. On low-speed links, consider the delay time for sending LSAs. • Change the SPF calculation interval to reduce resource consumption caused by frequent network changes. • Configure OSPF authentication to improve security. • Configure OSPF network management functions, such as binding OSPF MIB with a process, sending trap information, and collecting log information. Configuration prerequisites Before you configure OSPF network optimization, complete the following tasks: • Configure IP addresses for interfaces. • Configure OSPF basic functions. Configuring OSPF packet timers You can configure the following timers on OSPF interfaces as needed. • Hello timer —Interval for sending hello packets. It must be identical on OSPF neighbors. The longer the interval, the lower the convergence speed, and the smaller the network load.
86 • Poll timer —Interval for sending hello packets to a neighbor that is down on the NBMA network. The poll interval is at least four times the hello interval. • Dead timer—Interval within which if the interface receives no hello packet from the neighbor, it declares the neighbor is down. The dead interval must be at least four times the hello interval on an interface. • LSA retransmission timer —Interval within which if the interface receives no acknowledgement packets after sending an LSA to the neighbor, it retr ansmits the LSA. An interval setting that is too small can cause unnecessary LSA retransmissions. This interval is typically set bigger than the round-trip time of a packet between two neighbors. To configure timers for OSPF 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 hello interval. ospf timer hello seconds Optional. The hello interval defaults to 10 seconds on P2P and broadcast interfaces, and defaults to 30 seconds on P2MP and NBMA interfaces. The default hello interval is restored when the network type for an interface is changed. 4. Specify the poll interval. ospf timer poll seconds Optional. The poll interval defaults to 120 seconds. 5. Specify the dead interval. ospf timer dead seconds Optional. The default dead interval is 40 seconds on P2P and broadcast interfaces and 120 seconds on P2MP and NBMA interfaces. The default dead interval is restored when the network type for an interface is changed. 6. Specify the retransmission interval. ospf timer retransmit interval Optional. The retransmission interval defaults to 5 seconds. Specifying LSA transmission delay Each LSA in the LSDB has an age that is incremen ted by 1 every second, but the age does not change during transmission. It is necessary to add a transmissi on delay into the age time especially for low-speed links. To specify the LSA transmission delay on an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A
87 Step Command Remarks 3. Specify the LSA transmission delay. ospf trans-delay seconds Optional. 1 second by default. Specifying SPF calculation interval LSDB changes lead to SPF calculations. When the topology changes frequently, a large amount of network and router resources are occupied by SPF calculation. Adjust the SPF calculation interval to reduce the impact. When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the SPF calculation interval is incremented by incremental-interval × 2n-2 (n is the number of calculation times) each time a calculation occurs until the maximum-interval is reached. To configure SPF calculation interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Specify the SPF calculation interval. spf-schedule-interval maximum-interval [ minimum-interval [ incremental-interval ] ] Optional. By default, the interval is 5 seconds. Specifying the LSA arrival interval After receiving the same LSA as the previously received LSA within the LSA arrival interval, OSPF discards the LSA. To configure the LSA arrival interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the LSA arrival interval. lsa-arrival-interval interval Optional. 1000 milliseconds by default. Make sure this interval is smaller than or equal to the interval set with the lsa-generation-interval command. Specifying the LSA generation interval You can adjust the LSA generation interval to protect network resources and routers from being over consumed by frequent network changes.
88 When network changes are not frequent, LSAs are generated at the minimum-interval. If network changes become frequent, the LSA generation interval is incremented by incremental-interval × 2n-2 (n is the number of generation times) each time a LSA generation occurs until the maximum-interval is reached. To configure the LSA generation interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the LSA generation interval. lsa-generation-interval maximum-interval [ initial-interval [ incremental-interval ] ] Optional. By default, the maximum interval is 5 seconds, the minimum interval is 0 milliseconds, and the incremental interval is 5000 milliseconds. Disabling interfaces from receiving and sending OSPF packets Follow these guidelines when you disable interf aces from receiving and sending OSPF packets: • Different OSPF processes can disable the same in terface from receiving and sending OSPF packets. The silent-interface command disables only the interfaces as sociated with the current process rather than interfaces associated with other processes. • After an OSPF interface is set to silent, other interfaces on the router can advertise direct routes of the interface in Router LSAs, but the interface cannot send any packet. This configuration can enhance OSPF adaptability and reduce resource consumption. To disable interfaces from receivin g and sending routing information: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Disable interfaces from receiving and sending OSPF packets. silent-interface { interface-type interface-number | all } Optional. Not disabled by default. Configuring stub routers A stub router is used for traffic control. It tells other OSPF routers to not use it to forward data. The Router LSAs from the stub router may contain different link type values. A value of 3 means a link to a stub network, and the cost of the link will not be changed. A value of 1, 2, or 4 means a point-to-point link, a link to a transit network, or a virtual link. On such links, a maximum cost value of 65535 is used. Thus, neighbors find that the links to the stub router have large costs that they will not send packets to the stub router for forwarding as long as an other route with a smaller cost exists. To configure a router as a stub router:
89 Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Configure the router as a stub router. stub-router By default, the router is not a stub router in any OSPF process. Configuring OSPF authentication You can configure OSPF packet authentication to ensure the security of packet exchanges. After authentication is configured, OSPF only receives packets that pass authentication. Failed packets cannot establish neighboring relationships. To configure OSPF authentication, you must configure the same area authentication mode on all the routers in the area. In addition, the authentication mo de and password for all interfaces attached to the same area must be identical. To configure OSPF authentication: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enter area view. area area-id N/A 4. Configure the authentication mode. authentication-mode { md5 | simple } Not configured by default. 5. Return to OSPF view. quit N/A 6. Return to system view. quit N/A 7. Enter interface view. interface interface-type interface-number N/A 8. Configure interface authentication mode. • Configure the simple authentication mode: ospf authentication-mode simple [ cipher | plain ] password • Configure the MD5 authentication mode: ospf authentication-mode { hmac-md5 | md5 } key-id [ cipher | plain ] password Use either approach. Not configured by default. Adding the interface MTU into DD packets By default, an interface adds 0 into the interface MTU field of a DD packet to be sent rather than the interface MTU. You can enable an interface to add its MTU into DD packets. To add the interface MTU into DD packets: Step Command Remarks 1. Enter system view. system-view N/A
90 Step Command Remarks 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the interface to add its MTU into DD packets. ospf mtu-enable Optional. Not enabled by default. Configuring the maximum number of external LSAs in LSDB Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Specify the maximum number of external LSAs in the LSDB. lsdb-overflow-limit number Optional. Not specified by default. Enabling compatibility with RFC 1583 RFC 1583 specifies a different method than RFC 2328 for selecting an external route from multiple LSAs. If RFC 1583 is made compatible with RFC 2328, the routes in the backbone area are preferred; if not, the routes in the non-backbone area are preferred to reduce the burden of the backbone area. To avoid routing loops, HP recommends configuring all the routers to be either compatible or incompatible with RFC 1583. To make them compatible: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable compatibility with RFC 1583. rfc1583 compatible Optional. Enabled by default. Logging neighbor state changes Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable the logging of neighbor state changes. log-peer-change Optional. Enabled by default.
91 Configuring OSPF network management With trap generation enabled, OSPF generates traps to report important events. Traps fall into the following levels. • Level-3 —Fault traps • Level-4 —Alarm traps • Level-5 —Normal but important traps • Level-6 —Notification traps The generated traps are sent to the information center of the device. The output rules of the traps such as whether to output the traps and the output direction are determined according to the information center configuration. (For information center configuration, see Network Management and Monitoring Configuration Guide .) To configure OSPF network management: Step Command Remarks 1. Enter system view. system-view N/A 2. Bind OSPF MIB to an OSPF process. ospf mib-binding process-id Optional. By default, the OSPF process with the smallest process-id is bound with OSPF MIB. 3. Enable OSPF trap generation. snmp-agent trap enable ospf [ process-id ] [ ifauthfail | ifcfgerror | ifrxbadpkt | ifstatechange | iftxretransmit | lsdbapproachoverflow | lsdboverflow | maxagelsa | nbrstatechange | originatelsa | vifcfgerror | virifauthfail | virifrxbadpkt | virifstatechange | viriftxretransmit | virnbrstatechange ] * Optional. Enabled by default. Enabling message logging Step Command Remarks 1. Enter system view. system-view N/A 2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * N/A 3. Enable message logging. enable log [ config | error | state ] Not enabled by default. Enabling the advertisement and reception of opaque LSAs With this feature enabled, OSPF can receive and advertise Type 9, Type 10, and Type 1 1 opaque LSAs. To enable the advertisement and reception of opaque LSAs: