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 2281 to Favourites
    image text
    Enable zoom 
    							 218 
     Master IP      : 192.168.0.102 
   VRRP Track Information: 
     Track Object   : 1               State : Negative   Pri Reduced : 2\
0 
# Display the detailed information about VRRP group 1 on Switch B. 
 display vrrp verbose 
 IPv4 Standby Information: 
     Run Mode       : Standard 
     Run Method     : Virtual MAC 
 Total number of virtual routers : 1 
   Interface Vlan-interface2 
     VRID           : 1               Adver Timer  : 1 
     Admin Status   : Up              State        : Master 
     Config Pri     : 100             Running Pri  : 100 
     Preempt Mode   : Yes             Delay Time   : 0 
     Auth Type      : None 
     Virtual IP     : 192.168.0.10 
     Virtual MAC    : 0000-5e00-0101 
     Master IP      : 192.168.0.102 
The output shows that when Switch A detects that the uplink fails through BFD, it decreases its 
priority by 20 to make sure that Switch B can preempt as the master. 
Static routing-track-NQA collaboration configuration example 
Network requirements 
As shown in  Figure 59, Switch A, Switch B, Switch C, and Switch D are connected to two segments 
20.1.1.0/24 and 30.1.1.0/24. Configure static routes on these switches so that the two segments can 
communicate with each other, and configure route backup to improve reliability of the network. 
Switch A is the default gateway of the hosts in segment 20.1.1.0/24. Two static routes to 30.1.1.0/24 exist 
on Switch A, with the next hop being Switch B and  Switch C, respectively. These two static routes back 
up each other as follows: 
•   The static route with Switch B as the next hop has a higher priority, and is the master route. If this 
route is available, Switch A forwards packets to 30.1.1.0/24 through Switch B. 
•   The static route with Switch C as the next hop acts as the backup route. 
•   Configure static routing-track-NQA collaboration to  determine whether the master route is available 
in real time. If the master route is unavailable, the backup route takes effect, and Switch A forwards 
packets to 30.1.1.0/24 through Switch C. 
Similarly, Switch D is the default gateway of the hosts in segment 30.1.1.0/24. Two static routes to 
20.1.1.0/24 exist on Switch D, with the next hop being Switch B and Switch C, respectively. These two 
static routes back up each other as follows: 
•   The static route with Switch B as the next hop has a higher priority, and is the master route. If this 
route is available, Switch D forwards packets to 20.1.1.0/24 through Switch B. 
•   The static route with Switch C as the next hop acts as the backup route. 
•   Configure static routing-track-NQA collaboration to  determine whether the master route is available 
in real time. If the master route is unavailable, the backup route takes effect, and Switch D forwards 
packets to 20.1.1.0/24 through Switch C.
    Add page 2282 to Favourites
    image text
    Enable zoom 
    							 219 
Figure 59 Network diagram 
 
 
Configuration procedure 
1. Create VLANs, and assign corres ponding ports to the VLANs. Configure the IP address of each 
VLAN interface as shown in  Figure 59. (D
 etails not shown.) 
2. Configure Switch A: 
# Configure a static rout e to 30.1.1.0/24, with the address of the next hop as 10.1.1.2 and the 
default priority 60. This static rout e is associated with track entry 1. 
 system-view 
[SwitchA] ip route-static 30.1.1.0 24 10.1.1.2 track 1 
# Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.3.1.3 and the 
priority 80. 
[SwitchA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80 
# Configure a static route to  10.2.1.4, with the address of the next hop as 10.1.1.2. 
[SwitchA] ip route-static 10.2.1.4 24 10.1.1.2 
# Create an NQA test group with the administrator  admin and the operation tag  test. 
[SwitchA] nqa entry admin test 
# Configure the test type as ICMP-echo. 
[SwitchA-nqa-admin-test] type icmp-echo 
# Configure the destination address of the test as 10.2.1.4 and the next hop address as 10.1.1.2 
to check the connectivity of the path from Switch A  to Switch B and then to Switch D through NQA. 
[SwitchA-nqa-admin-test-icmp-echo] destination ip 10.2.1.4 
[SwitchA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2 
# Configure the test frequency as 100 ms. 
[SwitchA-nqa-admin-test-icmp-echo] frequency 100 
# Configure reaction entry 1, specifying that five consecutive probe failures trigger the track 
module. 
[SwitchA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail\
 
threshold-type consecutive 5 action-type trigger-only 
[SwitchA-nqa-admin-test-icmp-echo] quit 
# Start the NQA test.
    Add page 2283 to Favourites
    image text
    Enable zoom 
    							 220 
[SwitchA] nqa schedule admin test start-time now lifetime forever 
# Configure track entry 1, and associate it with reaction entry 1 of the NQA test group (with the 
administrator admin, and the operation tag  test). 
[SwitchA] track 1 nqa entry admin test reaction 1 
3. Configure Switch B: 
# Configure a static route to 30.1.1.0/24, with  the address of the next hop as 10.2.1.4. 
 system-view 
[SwitchB] ip route-static 30.1.1.0 24 10.2.1.4 
# Configure a static route to 20.1.1.0/24, with the address of the next hop as 10.1.1.1. 
[SwitchB] ip route-static 20.1.1.0 24 10.1.1.1 
4. Configure Switch C: 
# Configure a static route to 30.1.1.0/24, with  the address of the next hop as 10.4.1.4. 
 system-view 
[SwitchC] ip route-static 30.1.1.0 24 10.4.1.4 
# Configure a static route to 20.1.1.0/24, with the address of the next hop as 10.3.1.1. 
[SwitchC] ip route-static 20.1.1.0 24 10.3.1.1 
5. Configure Switch D: 
# Configure a static rout e to 20.1.1.0/24, with the address of the next hop as 10.2.1.2 and the 
default priority 60. This static rout e is associated with track entry 1. 
 system-view 
[SwitchD] ip route-static 20.1.1.0 24 10.2.1.2 track 1 
# Configure a static route to 20.1.1.0/24, with the address of the next hop as 10.4.1.3 and the 
priority 80. 
[SwitchD] ip route-static 20.1.1.0 24 10.4.1.3 preference 80 
# Configure a static route to  10.1.1.1, with the address of the next hop as 10.2.1.2. 
[SwitchD] ip route-static 10.1.1.1 24 10.2.1.2 
# Create an NQA test group with the administrator  admin and the operation tag  test. 
[SwitchD] nqa entry admin test 
# Configure the test type as ICMP-echo. 
[SwitchD-nqa-admin-test] type icmp-echo 
# Configure the destination address of the test as 10.1.1.1 and the next hop address as 10.2.1.2 
to check the connectivity of the path from Switch D to Switch B and then to Switch A through NQA. 
[SwitchD-nqa-admin-test-icmp-echo] destination ip 10.1.1.1 
[SwitchD-nqa-admin-test-icmp-echo] next-hop 10.2.1.2 
# Configure the test frequency as 100 ms. 
[SwitchD-nqa-admin-test-icmp-echo] frequency 100 
# Configure reaction entry 1, specifying that fi ve consecutive probe failures trigger the track 
module. 
[SwitchD-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail\
 
threshold-type consecutive 5 action-type trigger-only 
[SwitchD-nqa-admin-test-icmp-echo] quit 
# Start the NQA test. 
[SwitchD] nqa schedule admin test start-time now lifetime forever 
# Configure track entry 1, and associate it with reaction entry 1 of the NQA test group (with the 
administrator  admin, and the operation tag  test).
    Add page 2284 to Favourites
    image text
    Enable zoom 
    							 221 
[SwitchD] track 1 nqa entry admin test reaction 1 
6. Verify the configuration: 
# Display information about the track entry on Switch A. 
[SwitchA] display track all 
Track ID: 1 
  Status: Positive 
  Duration: 0 days 0 hours 0 minutes 32 seconds 
  Notification delay: Positive 0, Negative 0 (in seconds) 
  Reference object: 
    NQA entry: admin test 
    Reaction: 1 
# Display the routing table of Switch A. 
[SwitchA] display ip routing-table 
Routing Tables: Public 
         Destinations : 10       Routes : 10 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.1.1.0/24         Direct 0    0            10.1.1.1        Vlan2 
10.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
10.2.1.0/24         Static 60   0            10.1.1.2        Vlan2 
10.3.1.0/24         Direct 0    0            10.3.1.1        Vlan3 
10.3.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
20.1.1.0/24         Direct 0    0            20.1.1.1        Vlan6 
20.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
30.1.1.0/24         Static 60   0            10.1.1.2        Vlan2 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
The output shows the NQA test result: the master rout e is available (the status of the track entry is 
Positive), and Switch A forwards packe ts to 30.1.1.0/24 through Switch B. 
# Remove the IP address of interface VLAN-interface 2 on Switch B. 
 system-view 
[SwitchB] interface vlan-interface 2 
[SwitchB-Vlan-interface2] undo ip address 
# Display information about the track entry on Switch A. 
[SwitchA] display track all 
Track ID: 1 
  Status: Negative 
  Duration: 0 days 0 hours 0 minutes 32 seconds 
  Notification delay: Positive 0, Negative 0 (in seconds) 
  Reference object: 
    NQA entry: admin test 
    Reaction: 1 
# Display the routing table of Switch A. 
[SwitchA] display ip routing-table 
Routing Tables: Public 
 
         Destinations : 10       Routes : 10
    Add page 2285 to Favourites
    image text
    Enable zoom 
    							 222 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.1.1.0/24         Direct 0    0            10.1.1.1        Vlan2 
10.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
10.2.1.0/24         Static 60   0            10.1.1.2        Vlan2 
10.3.1.0/24         Direct 0    0            10.3.1.1        Vlan3 
10.3.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
20.1.1.0/24         Direct 0    0            20.1.1.1        Vlan6 
20.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
30.1.1.0/24         Static 80   0            10.3.1.3        Vlan3 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
The output shows the NQA test result: the master route is unavailable (the status of the track entry 
is Negative). The backup static route takes effect and Switch A forwards packets to 30.1.1.0/24 
through Switch C. 
# When the master route fails, the hosts in 20.1.1.0/24 can still communicate with the hosts in 
30.1.1.0/24. 
[SwitchA] ping -a 20.1.1.1 30.1.1.1 
  PING 30.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms 
  --- 30.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 1/1/2 ms 
# The output on Switch D is similar to that on Sw itch A. When the master route fails, the hosts in 
30.1.1.0/24 can still communicate wi th the hosts in 20.1.1.0/24. 
[SwitchB] ping -a 30.1.1.1 20.1.1.1 
  PING 20.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 20.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=4 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms 
  --- 20.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 1/1/2 ms
    Add page 2286 to Favourites
    image text
    Enable zoom 
    							 223 
Static routing-Track-BFD collaboration configuration example 
(available only on the HP 5500 EI) 
Network requirements 
As shown in Figure 60, Switch A, Switch B, and Switch C are connected to two segments 20.1.1.0/24 
and 30.1.1.0/24. Configure static routes on these ro uters so that the two segments can communicate with 
each other, and configure route backup to improve reliability of the network. 
Switch A is the default gateway of the hosts in segment 20.1.1.0/24. Two static routes to 30.1.1.0/24 exist 
on Switch A, with the next hop being Switch B and  Switch C, respectively. These two static routes back 
up each other as follows: 
•   The static route with Switch B as the next hop has a higher priority and is the master route. If this 
route is available, Switch A forwards packets to 30.1.1.0/24 through Switch B. 
•   The static route with Switch C as the next hop acts as the backup route. 
•   Configure static routing-track-BFD collaboration to  determine whether the master route is available 
in real time. If the master route is unavailable, BFD can quickly detect the route failure to make the 
backup route take effect, and Switch A forwards packets to 30.1.1.0/24 through Switch C and 
Switch B. 
Similarly, Switch B is the default gateway of the hosts in segment 30.1.1.0/24. Two static routes to 
20.1.1.0/24 exist on Switch B, with the next hop being Switch A and Switch C, respectively. These two 
static routes back up each other as follows: 
•   The static route with Switch A as the next hop has a higher priority and is the master route. If this 
route is available, Switch B forwards packets to 20.1.1.0/24 through Switch A. 
•   The static route with Switch C as the next hop acts as the backup route. 
•   Configure static routing-track-BFD collaboration to  determine whether the master route is available 
in real time. If the master route is unavailable, BFD can quickly detect the route failure to make the 
backup route take effect, and Switch B forwards packets to 20.1.1.0/24 through Switch C and 
Switch A. 
Figure 60  Network diagram 
 
 
Configuration procedure 
1. Create VLANs, and assign corres ponding ports to the VLANs. Configure the IP address of each 
VLAN interface as shown in  Figure 60. (D
 etails not shown.) 
2. Configure Switch A: 
# Configure a static rout e to 30.1.1.0/24, with the address of the next hop as 10.2.1.2 and the 
default priority 60. This static rout e is associated with track entry 1.
    Add page 2287 to Favourites
    image text
    Enable zoom 
    							 224 
 system-view 
[SwitchA] ip route-static 30.1.1.0 24 10.2.1.2 track 1 
# Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.3.1.3 and the 
priority 80. 
[SwitchA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80 
# Configure the source address of BFD echo packets as 10.10.10.10. 
[SwitchA] bfd echo-source-ip 10.10.10.10 
# Configure track entry 1, and associate it with  the BFD session. Check whether Switch A can be 
interoperated with the next ho p of static route (Switch B). 
[SwitchA] track 1 bfd echo interface vlan-interface 2 remote ip 10.2.1.2\
 local ip 
10.2.1.1 
3. Configure Switch B: 
# Configure a static rout e to 20.1.1.0/24, with the address of the next hop as 10.2.1.1 and the 
default priority 60. This static rout e is associated with track entry 1. 
 system-view 
[SwitchB] ip route-static 20.1.1.0 24 10.2.1.1 track 1 
# Configure a static route to 20.1.1.0/24, with the address of the next hop as 10.4.1.3 and the 
priority 80. 
[SwitchB] ip route-static 20.1.1.0 24 10.4.1.3 preference 80 
# Configure the source address of  BFD echo packets as 1.1.1.1. 
[SwitchB] bfd echo-source-ip 1.1.1.1 
# Configure track entry 1 that is associated with  the BFD session to check whether Switch B can 
communicate with the next hop (Switch A) of the static route. 
[SwitchB] track 1 bfd echo interface vlan-interface 2 remote ip 10.2.1.1\
 local ip 
10.2.1.2 
4.  Configure Switch C: 
# Configure a static route to 30.1.1.0/24, with  the address of the next hop as 10.4.1.2. 
 system-view 
[SwitchC] ip route-static 30.1.1.0 24 10.4.1.2 
# Configure a static route to 20.1.1.0/24, with the address of the next hop as 10.3.1.1. 
[SwitchB] ip route-static 20.1.1.0 24 10.3.1.1 
5. Verify the configuration: 
# Display information about the track entry on Switch A. 
[SwitchA] display track all 
Track ID: 1 
  Status: Positive 
  Duration: 0 days 0 hours 0 minutes 32 seconds 
  Notification delay: Positive 0, Negative 0 (in seconds) 
  Reference object: 
    BFD Session: 
    Packet type: Echo 
    Interface  : Vlan-interface2 
    Remote IP  : 10.2.1.2 
    Local IP   : 10.2.1.1 
# Display the routing table of Switch A. 
[SwitchA] display ip routing-table
    Add page 2288 to Favourites
    image text
    Enable zoom 
    							 225 
Routing Tables: Public 
         Destinations : 9        Routes : 9 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.2.1.0/24         Direct 0    0            10.2.1.1        Vlan2 
10.2.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
10.3.1.0/24         Direct 0    0            10.3.1.1        Vlan3 
10.3.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
20.1.1.0/24         Direct 0    0            20.1.1.1        Vlan5 
20.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
30.1.1.0/24         Static 60   0            10.2.1.2        Vlan2 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
The output shows the BFD detection result: the next hop 10.2.1.2 is reachable (the status of the 
track entry is Positive). The master static route takes effect. Switch A forwards packets to 
30.1.1.0/24 through Switch B. 
# Remove the IP address of interface VLAN-interface 2 on Switch B. 
 system-view 
[SwitchB] interface vlan-interface 2 
[SwitchB-Vlan-interface2] undo ip address 
# Display information about the track entry on Switch A. 
[SwitchA] display track all 
Track ID: 1 
  Status: Negative 
  Duration: 0 days 0 hours 0 minutes 32 seconds 
  Notification delay: Positive 0, Negative 0 (in seconds) 
  Reference object: 
    BFD Session: 
    Packet type: Echo 
    Interface  : Vlan-interface2 
    Remote IP  : 10.2.1.2 
    Local IP   : 10.2.1.1 
# Display the routing table of Switch A. 
[SwitchA] display ip routing-table 
Routing Tables: Public 
         Destinations : 9        Routes : 9 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.2.1.0/24         Direct 0    0            10.2.1.1        Vlan2 
10.2.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
10.3.1.0/24         Direct 0    0            10.3.1.1        Vlan3 
10.3.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
20.1.1.0/24         Direct 0    0            20.1.1.1        Vlan5 
20.1.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
30.1.1.0/24         Static 80   0            10.3.1.3        Vlan3 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
The output shows the BFD detection result: the next  hop 10.2.1.2 is unreachable (the status of the 
track entry is Negative), and the backup static ro ute takes effect, and Switch A forwards packets 
to 30.1.1.0/24 through Switch C and Switch B.
    Add page 2289 to Favourites
    image text
    Enable zoom 
    							 226 
# When the master route fails, the hosts in 20.1.1.0/24 can still communicate with the hosts in 
30.1.1.0/24. 
[SwitchA] ping -a 20.1.1.1 30.1.1.1 
  PING 30.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms 
    Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms 
  --- 30.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 1/1/2 ms 
# The output on Switch B is similar to that on Switch A. When the master route fails, the hosts in 
30.1.1.0/24 can still communicate wi th the hosts in 20.1.1.0/24. 
[SwitchB] ping -a 30.1.1.1 20.1.1.1 
  PING 20.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 20.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=4 ttl=254 time=1 ms 
    Reply from 20.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms 
  --- 20.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 1/1/2 ms 
VRRP-track-interface management collaboration configuration 
example (the master monitors the uplink interface) (available 
only on the HP 5500 EI) 
Network requirements 
•  As shown in Figure 61 , Host A needs to access Host B on the Internet. The default gateway of Host 
A  i s  1 0 .1.1.1 0 / 2 4 .  
•   Switch A and Switch B belong to VRRP group 1, whose virtual IP address is 10.1.1.10. 
•   When Switch A works properly, packets from Host A to Host B are forwarded through Switch A. 
When VRRP detects that a fault is on the uplink interface of Switch A through the interface 
management module, packets from Host A to Host B are forwarded through Switch B.
    Add page 2290 to Favourites
    image text
    Enable zoom 
    							 227 
Figure 61 Network diagram 
 
 
Configuration procedure 
1. Create VLANs, and assign corres ponding ports to the VLANs. Configure the IP address of each 
VLAN interface as shown in  Figure 61. (D
 etails not shown.) 
2. Configure a track entry on Switch A: 
# Configure track entry 1, and associate it with the physical status of the uplink interface 
VLAN-interface 3. 
[SwitchA] track 1 interface vlan-interface 3 
3. Configure VRRP on Switch A: 
# Create VRRP group 1, and configure the  virtual IP address 10.1.1.10 for the group. 
[SwitchA] interface vlan-interface 2 
[SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10 
# Set the priority of Switch A in VRRP group 1 to 110. 
[SwitchA-Vlan-interface2] vrrp vrid 1 priority 110 
# Configure to monitor track entry 1, and specify the priority decrement as 30. 
[SwitchA-Vlan-interface2] vrrp vrid 1 track 1 reduced 30 
4. Configure VRRP on Switch B: 
 system-view 
[SwitchB] interface vlan-interface 2 
# Create VRRP group 1, and configure the  virtual IP address 10.1.1.10 for the group. 
[SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10 
5. Verify the configuration: 
After configuration, ping Host B on Host A, and you can see that Host B is reachable. Use the 
display vrrp  command to view the configuration result.  
# Display detailed information about VRRP group 1 on Switch A. 
[SwitchA-Vlan-interface2] display vrrp verbose 
 IPv4 Standby Information: 
     Run Mode       : Standard 
     Run Method     : Virtual MAC 
 Total number of virtual routers : 1 
   Interface Vlan-interface2
    All HP manuals Comments (0)

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