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 971 to Favourites
    image text
    Enable zoom 
    							 282 
Step Command Remarks 
5.  Enable an OSPFv3 process on 
the interface.  ospfv3 
process-id  area area-id  
[  instance  instance-id  ]  Not enabled by default. 
 
Configuring OSPFv3 area parameters 
The stub area and virtual link features of OSPFv3 are the same as OSPFv2. 
Splitting an OSPFv3 AS into multiple areas re
duces the number of LSAs and extends OSPFv3 
applications. For those non-backbone areas residing on the AS boundary, configure them as stub areas 
to further reduce the size of routing tables and the number of LSAs. 
Non-backbone areas exchange routing informatio n through the backbone area. The backbone and 
non-backbone areas—including the backbone itself —must be contiguous. In practice, necessary 
physical links may not be available for this connectivity. You can configure virtual links to address the 
problem. 
Configuration prerequisites 
Before you configure OSPFv3 area parameters, complete the following tasks: 
•   Enable IPv6 packet forwarding. 
•   Configure OSPFv3 basic functions. 
Configuring an OSPFv3 stub area 
Follow these guidelines when you configure an OSPFv3 stub area: 
•  You cannot remove an OSPFv3 area directly. The area can be removed only when you remove all 
configurations in area view and all interfaces attached to the area become down. 
•   All the routers attached to a stub area must be configured with the  stub command. The keyword 
no-summary  is only available on the ABR of the stub area. 
•   If you use the stub command with the keyword no-summary  on an ABR, the ABR advertises a 
default route in an Inter-Area-Prefix-LSA into the stub area. No AS -external-LSA, Inter-Area-Prefix-LSA, 
or Inter-Area-Router-LSA is advertised in the area. The stub area of this kind is also known as a 
totally stub area. 
To configure an OSPFv3 stub area: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Enter OSPFv3 area view. 
area area-id   N/A 
4.  Configure the area as a stub 
area.  stub 
[ no-summary  ]  Not configured by default. 
5.  Specify a cost for the default 
route advertised to the stub 
area.  default-cost
 value   Optional. 
1 by default.
    Add page 972 to Favourites
    image text
    Enable zoom 
    							 283 
Configuring an OSPFv3 virtual link 
You can configure a virtual link to maintain connectivity between a non-backbone area and the 
backbone, or in the backbone itself.  
 
 IMPORTANT: 
•
  Both ends of a virtual link are ABRs that must be configured with the  vlink-peer command. 
•   Do not configure virtual links in the areas of a GR-capable process. 
 
To configure a virtual link:  
Step Command 
1.  Enter system view. 
system-view 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
 
3.   Enter OSPFv3 area view. 
area area-id  
4.  Configure a virtual link.  vlink-peer 
router-id [ hello seconds  | retransmit  seconds  | trans-delay  
seconds  | dead  seconds  | instance  instance-id  ] * 
 
Configuring OSPFv3 network types 
OSPFv3 classifies networks into the foll owing types by the link layer protocol. 
By default, the default OSPFv3 interface network types va ry with the link layer protocols of the interfaces:   
•   When the link layer protocol is PPP, OSPFv3 considers the network type as P2P by default. 
•   When the link layer protocol is Ethernet, OSPF v3 considers the network type as broadcast by 
default. 
You can change the network type of an OSPFv3 interface as needed. For example: 
•   An NBMA network must be fully connected. Any two routers in the network must be directly 
reachable to each other through a virtual circuit. If  no such direct link is available, you must change 
the network type through a command. 
•   If direct connections are not av ailable between some routers in an NBMA network, the type of 
i nte r fa c e s  asso cia te d  mus t  be  c o n fig u re d  as  P 2 M P,  o r  as  P 2 P  fo r  i nte r fa c es  wi t h  o n ly o n e  n eig h b or.  
Configuration prerequisites 
Before you configure OSPFv3 network types, complete the following tasks: 
•   Configure IPv6 functions. 
•   Configure OSPFv3 basic functions. 
Configuring the OSPFv3 network type for an interface  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A
    Add page 973 to Favourites
    image text
    Enable zoom 
    							 284 
Step Command Remarks 
2.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
3.
  Configure a network type for 
the OSPFv3 interface.  ospfv3 network-type {
 broadcast | 
nbma  | p2mp  [ non-broadcast  ] | 
p2p  } [ instance  instance-id  ]  Optional. 
The network type of an interface 
depends on the media type of the 
interface.
 
 
Configuring an NBMA or P2MP neighbor 
For NBMA and P2MP interfaces (only when in unicast  mode), specify the link-local IP addresses of their 
neighbors because these interfaces cannot find ne ighbors through broadcasting hello packets. You can 
also specify DR priorities for neighbors. 
To configure an NBMA or P2MP (unicast) neighbor and its DR priority: 
 
Step Command 
1.   Enter system view. 
system-view 
2.  Enter interface view.  
interface interface-type interface-number 
3.   Specify an NBMA or P2MP 
(unicast) neighbor and its 
DR priority.  ospfv3 peer
 ipv6-address  [ dr-priority dr-priority ] [ instance  instance-id  ] 
 
Configuring OSPFv3 routing information control 
This section describes how to configure the control of OSPF routing information advertisement and 
reception, and redistribution from other protocols. 
Configuration prerequisites 
Before you configure OSPFv3 routing information control, complete the following tasks: 
•   Enable IPv6 packet forwarding. 
•   Configure OSPFv3 basic functions. 
Configuring OSPFv3 route summarization 
If contiguous network segments exist in an area, use the  abr-summary command to summarize them into 
one network segment on the ABR. The ABR will advertise only the summary route. Any LSA in the 
specified network segment will not be advertised, reducing the LSDB size in other areas. 
To configure route summarization: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Enter OSPFv3 area view. 
area area-id   N/A
    Add page 974 to Favourites
    image text
    Enable zoom 
    							 285 
Step Command Remarks 
4.  Configure a summary route.  abr-summary
 ipv6-address 
prefix-length [ not-advertise  ] Not configured by default. 
The 
abr-summary  command takes 
effect on ABRs only. 
 
Configuring OSPFv3 inbound route filtering 
According to some rules, you can configure OSPFv3 to filter routes that are computed from received 
LSAs. 
To configure OSPFv3 inbound route filtering: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3  [ process-id  ]
  N/A 
3.
  Configure inbound 
route filtering.  filter-policy { acl-number
 | ipv6-prefix  
ipv6-prefix-name  } import   Not configured by default. 
The 
filter-policy  import command 
can only filter routes computed by 
OSPFv3. Only routes not filtered 
out can be added into the local 
routing table. 
 
Configuring an OSPFv3 cost for an interface 
You can configure an OSPFv3 cost for an interface with one of the following methods: 
•   Configure the cost value in interface view. 
•   Configure a bandwidth reference value for the interface, and OSPFv3 computes the cost 
automatically based on the bandwidth reference value: Interface OSPFv3 cost = Bandwidth 
reference value (100 Mbps) ÷ Interface bandwidth (M bps). If the calculated cost is greater than 
65535, the value of 65535 is used; if the calculated cost is smaller than 1, the value of 1 is used. 
If the cost value is not configured for an interface, OSPFv3 computes the interface cost value 
automatically.  
To configure an OSPFv3 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 OSPFv3 
cost for the interface.  ospfv3 cost 
value [ instance 
instance-id  ]  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:
    Add page 975 to Favourites
    image text
    Enable zoom 
    							 286 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view. 
ospfv3 [ process-id  ]  N/A  
3.  Configure a bandwidth 
reference value.  bandwidth-reference 
value
  Optional. 
100 Mbps by default.
 
 
Configuring the maximum number of OSPFv3 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 OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Specify the maximum number 
of ECMP routes.   maximum load-balancing
 
maximum   Optional. 
8 by default. 
 
Configuring a priority for OSPFv3 
A router may run multiple routing protocols. The syst
em assigns a priority to each protocol. When these 
routing protocols find the same route, the route found by the protocol with the highest priority is selected.   
To configure a priority for OSPFv3: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view. 
ospfv3 [ process-id  ] N/A 
3.  Configure a priority for 
OSPFv3.  preference [ 
ase ] [ route-policy  
route-policy-name  ] preference  Optional. 
By default, the priority of OSPFv3 internal 
routes is 10, and priority of OSPFv3 
external routes is 150. 
 
Configuring OSPFv3 route redistribution 
Follow these guidelines when you configure OSPFv3 route redistribution: 
•
  Executing the import-route or  default-route-advertise command on a router makes it become an 
ASBR. 
•   You can only inject and advertise a default route using the  default-route-advertise command. 
•   Because OSPFv3 is a link state routing protocol, it  cannot directly filter LSAs to be advertised. You 
must filter redistributed routes first. Routes that ar e not filtered out can be advertised in LSAs into the 
routing domain.
    Add page 976 to Favourites
    image text
    Enable zoom 
    							 287 
•  Using the filter-policy  export  command filters routes redistributed with the  import-route command. 
If the  import-route command is not configured, executing the filter-policy export command does 
not take effect. 
To configure OSPFv3 route redistribution: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Specify a default cost for 
redistributed routes.  default cost
 value   Optional. 
1 by default. 
4.
  Redistribute routes from 
another protocol, or another 
OSPFv3 process.  import-route 
protocol [ process-id  | allow-ibgp  ] 
[  cost  value  |  route-policy  route-policy-name  | 
type  type  ] *  Not configured by 
default. 
5.
  Inject a default route.  default-route-advertise 
[ always | cost  value | 
type  type  | route-policy  route-policy-name  ] *  Optional. 
Not injected by 
default. 
6.
  Filter redistributed routes.  filter-policy { acl6-number
 | ipv6-prefix  
ipv6-prefix-name  } export  [ isisv6  process-id  | 
ospfv3  process-id  |  ripng  process-id  | bgp4+  | 
direct  | static ]  Optional. 
Not configured by 
default. 
 
Tuning and optimizing OSPFv3 networks 
This section describes configurations of OSPFv3 timers, interface DR priority, MTU check ignorance for 
DD packets, and disabling interfaces from sending OSPFv3 packets. 
The following are OSPFv3 timers: 
•
  Pac ke t time r —Specified to adjust topology convergence speed and network load. 
•   LSA delay timer —Specified especially for low-speed links. 
•   SPF timer —Specified to protect networks from being overloaded due to frequent network changes. 
For a broadcast network, you can configure DR prioriti es for interfaces to affect DR or BDR election. 
After an interface is disabled from sending OSPFv3  packets, other routers cannot obtain any information 
from the interface. 
Configuration prerequisites 
Before you tune and optimize OSPFv3 networks, complete the following tasks: 
•   Enable IPv6 packet forwarding. 
•   Configure OSPFv3 basic functions. 
Configuring OSPFv3 timers  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A
    Add page 977 to Favourites
    image text
    Enable zoom 
    							 288 
Step Command Remarks 
2.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
3.
  Configure the hello interval.  ospfv3 timer hello
 seconds 
[ instance  instance-id  ]   Optional. 
By default, the hello interval on 
P2P, broadcast interfaces is 10 
seconds. 
4.
  Specify the poll interval.  ospfv3 timer poll 
seconds 
[  instance  instance-id  ]  Optional. 
By default, the poll interval is 120 
seconds. 
5.
  Configure the dead interval.  ospfv3 timer dead
 seconds 
[ instance  instance-id  ]  Optional. 
By default, the dead interval on 
P2P, broadcast interfaces is 40 
seconds. 
The dead interval set on 
neighboring interfaces cannot be 
too short. Otherwise, a neighbor is 
easily considered down. 
6.
  Configure the LSA 
retransmission interval.  ospfv3 timer retransmit 
interval 
[ instance  instance-id  ]   Optional. 
By default, the LSA retransmission 
interval is 5 seconds. 
The LSA retransmission interval 
cannot be too short; otherwise, 
unnecessary retransmissions 
occur. 
7.
  Configure the LSA 
transmission delay.  ospfv3 trans-delay
 seconds 
[ instance  instance-id  ]  Optional. 
By default, the LSA transmission 
delay is 1 second.
 
8.  Return to system view. 
quit  N/A 
9.
  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
10.
 Configure the SPF timers.  spf timers delay-interval 
hold-interval
  Optional. 
By default, 
delay-interval is 5 
seconds and  hold-interval is 10 
seconds. 
Setting both the  delay-interval and 
hold-interval to 0 triggers an SPF 
calculation at once, improving the 
network convergence speed.  
 
Configuring a DR 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
    Add page 978 to Favourites
    image text
    Enable zoom 
    							 289 
Step Command Remarks 
3.  Configure a DR priority.  ospfv3 dr-priority
 priority  [ instance 
instance-id  ]   Optional. 
By default, the DR priority is 1. 
The DR priority of an interface 
determines the interface’s 
qualification in DR election. 
Interfaces having the priority 0 
cannot become a DR or BDR. 
 
Ignoring MTU check for DD packets 
When LSAs are few in DD packets, it is unnecessary to check the MTU in DD packets to improve 
efficiency. 
To ignore MTU check for DD packets: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
3.
  Ignore MTU check for DD 
packets.   ospfv3 mtu-ignore 
[ instance 
instance-id  ]
  Not ignored by default. 
 
Disabling interfaces from receiving and sending OSPFv3 
packets 
Follow these guidelines when you disable interf
aces from receiving and sending OSPF packets: 
•   Multiple OSPFv3 processes can disable the same  interface from receiving and sending OSPFv3 
packets. Using the  silent-interface command disables only the interfaces associated with the current 
process. 
•   After an OSPF interface is set to  silent, direct routes of the interface can still be advertised in 
Intra-Area-Prefix-LSAs via other  interfaces, but other OSPFv3 packets cannot be advertised. No 
neighboring relationship can be established on the interface. This feature can enhance the 
adaptability of OSPFv3 networking. 
To disable interfaces from rece iving and sending OSPFv3 packets: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Disable interfaces from 
receiving and sending 
OSPFv3 packets.  silent-interface { interface-type 
interface-number
 | all }  Not disabled by default. 
 
Enabling the logging of neighbor state changes
    Add page 979 to Favourites
    image text
    Enable zoom 
    							 290 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Enable the logging of 
neighbor state changes.  log-peer-change 
Enabled by default. 
 
Configuring OSPFv3 GR 
 
 IMPORTANT: 
You cannot confi
gure OSPFv3 GR after configuring OSPFv3 virtual links, because they are not supported
at the same time. 
 
Graceful Restart ensures the continuity of packet fo rwarding when a routing protocol restarts or a 
master/slave switchover occurs: 
•   GR Restarter —Graceful restarting router. It must be Graceful Restart capable. 
•   GR Helper — Th e  n e i g h b o r  o f  t h e  G R  Re s t a r t e r.  I t  h e l p s  t h e  G R  Re s t a r t e r  t o  c o m p l e t e  t h e  G R  p ro c e s s.    
To prevent service interruption after a master/slave switchover, a GR Restarter running OSPFv3 must 
complete the following tasks: 
•   Keep the GR Restarter forwarding entries stable during reboot. 
•   Establish all adjacencies and obtain comp lete topology information after reboot. 
After the master/slave switchover, the GR Restarter sends a Grace-LSA to tell its neighbors that it performs 
a GR. Upon receiving the Grace-LSA, the neighbors with the GR Helper capability enter the helper mode 
(and are then called GR Helpers). Then, the GR Re starter retrieves its adjacencies and LSDB with the 
help of the GR Helpers.  
Configuring GR Restarter 
You can configure the GR Restarter capability on a GR Restarter. 
To  c o n fig u re  G R  Res ta r ter:  
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Enable the GR 
capability.  graceful-restart enable 
Disabled by default.  
4.  Configure the GR 
interval.  graceful-restart interval 
interval-value
  Optional. 
120 seconds by default.
 
 
Configuring GR Helper 
You can configure the GR Helper capability on a GR Helper. 
To configure GR Helper
    Add page 980 to Favourites
    image text
    Enable zoom 
    							 291 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3  [ process-id  ]
  N/A 
3.
  Enable the GR Helper 
capability.  graceful-restart helper enable  Optional. 
Enabled by default. 
4.
  Enable strict LSA 
checking.  graceful-restart helper 
strict-lsa-checking  Optional. 
Disabled by default.  
 
Configuring BFD for OSPFv3 
Bidirectional forwarding detection (BFD) provides a mechanism to quickly detect the connectivity of links 
between OSPFv3 neighbors, thus to improve the convergence speed of OSPFv3. For more information 
about BFD, see 
High Availability Configuration Guide . 
After discovering neighbors by sending hello packets, OSPFv3 notifies BFD of the neighbor addresses, 
and BFD uses these addresses to establish sessions. Before  a BFD session is established, it is in the down 
state. In this state, BFD control packets are sent at an  interval of no less than one second to reduce BFD 
control packet traffic. After the BFD session is establ ished, BFD control packets are sent at the negotiated 
interval, thereby implementing fast fault detection.  
To configure BFD for OSPFv3, you need to configure OSPFv3 first.  
To configure BFD for OSPFv3: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter OSPFv3 view.  
ospfv3 [ process-id  ]
  N/A 
3.
  Specify a router ID. 
router-id router-id   N/A 
4.  Quit the OSPFv3 view. 
quit  N/A 
5.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
6.
  Enable an OSPFv3 process 
on the interface.  ospfv3 
process-id  area area-id  
[  instance  instance-id  ]  Not enabled by default. 
7.
  Enable BFD on the interface.  ospfv3 bfd enable 
[ instance 
instance-id  ]  Not enabled by default. 
 
Applying IPsec policies for OSPFv3 
To protect routing information and defend attacks, 
OSPFv3 can authenticate protocol packets by using 
an IPsec policy.  
Outbound OSPFv3 packets carry the Security Parameter Index (SPI) defined in the relevant IPsec policy. 
A device uses the SPI carried in a received packet to match against the configured IPsec policy. If they 
match, the device accepts the packet; otherwise, it  discards the packet and will not establish a neighbor 
relationship with the sending device.   
You can configure an IPsec policy for an area, an interface or a virtual link.
    All HP manuals Comments (0)

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