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 171 to Favourites
    image text
    Enable zoom 
    							5 
[Sysname] interface gigabitethernet 3/0/1 
[Sysname-GigabitEthernet3/0/1] port link-type trunk 
File system naming conventions 
On a standalone switch, you can use the name of storage device to access its file system. For more 
information about storage device naming conventions, see  Fundamentals Configuration Guide. 
On an IRF fabric, you can use the name of storage device to access the file system of the master. To 
access the file system of any other member switch, use the name in the 
slot member-ID#storage-device-name  format. For example: 
To  a c c ess  t h e   test folder under the root directory of the Flash on the master switch: 
 mkdir test 
... 
%Created dir flash:/test. 
 dir 
Directory of flash:/ 
   0     -rw-  10105088  Apr 26 2000 13:44:57   test.bin 
   1     -rw-      2445  Apr 26 2000 15:18:19   config.cfg 
   2     drw-         -  Jul 14 2008 15:20:35   test 
30861 KB total (20961 KB free) 
To create and access the test folder under the root directory of the Flash on member switch 3: 
 mkdir slot3#flash:/test 
%Created dir slot3#flash:/test. 
 cd slot3#flash:/test 
 pwd 
slot3#flash:/test 
Or: 
 cd slot3#flash:/ 
 mkdir test 
%Created dir slot3#flash:/test. 
To  c o py  t h e  fi l e   test.bin on the master to the root directory of the Flash on member switch 3: 
# Display the current working path. In this example, the current working path is the root directory of the 
Flash on member switch 3.  
 pwd 
slot3#flash: 
# Change the current working path to the root directory of the Flash on the master switch:  
 cd flash:/ 
 pwd 
flash: 
# Copy the file to member switch 3.  
 copy test.bin slot3#flash:/ 
Copy flash:/test.bin to slot3#flash:/test.bin?[Y/N]:y 
%Copy file flash:/test.bin to slot3#flash:/test.bin...Done.
    Add page 172 to Favourites
    image text
    Enable zoom 
    							6 
Configuration synchronization mechanism 
IRF uses a strict running-configuration synchronization mechanism so all chassis in an IRF fabric can work 
as a single node, and after the master fails, other members can operate normally. 
In an IRF fabric, all chassis get and run the running configuration of the master. Any configuration you 
have made is propagated to all members.  
When you execute the  save [ safely  ] [ backup | main ] [  force ] command or the  save file -url  all 
command, the system saves the running configuration, as follows:  
•   If the configuration auto-update function (the slave auto-update config  command) is enabled, saves 
the configuration as the startup configuration on all member switches for the next startup.  
•   If the configuration auto-update function is disabled, saves the configuration as the startup 
configuration on the master for the next startup. 
For more information about configuration management, see  Fundamentals Configuration Guide. 
Master election 
Master election is held each time the IRF fabric to pology changes, for example, when the IRF fabric is 
established, a new member device is plugged in, the  master device fails or is removed, the IRF fabric 
splits, or IRF fabrics merge. 
Master election uses the following rules in descending order: 
1.  Current master, even if a new member has higher priority.  
When an IRF fabric is being formed, all member  switches consider themselves as the master, and 
this rule is skipped 
2.  Member with higher priority. 
3. Member with the longest system uptime.  
4. Member with the lowest bridge MAC address. 
The IRF fabric is formed on election of the master.  
During an IRF merge, the switches of the IRF fabric that fails the master election reboot automatically to 
re-join the IRF fabric that wins the election.  
After a master election, all subordinate switches initia lize and reboot with the configuration on the master. 
Their original configuration, even if has been saved, does not take effect.  
IRF multi-active detection 
An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 
configurations, including the same IP address. To avoid IP address collision and network problems, IRF 
uses multi-active detection (MAD) mechanisms to dete ct the presence of multiple identical IRF fabrics, 
handle collisions, and recover from faults.  
Multi-active handling procedure 
The multi-active handling procedure includes dete ction, collision handling and failure recovery.
    Add page 173 to Favourites
    image text
    Enable zoom 
    							7 
Detection 
The MAD implementation of this switch series detects active IRF fabrics with the same Layer 3 global 
configuration by extending the LACP, BFD, or gratuitous ARP protocol.  
These MAD mechanisms identify each IRF fabric with a domain ID and an active ID (the member ID of 
the master). If multiple active IDs are detected in a  domain, MAD determines that an IRF collision or split 
has occurred.  
You can use at least one of these mechanisms in an IRF fabric, depending on your network topology. For 
a comparison of these MAD mechanisms, see  Configuring MAD.  
Collision handling 
When multiple identical active IRF fabrics are detect ed, MAD compares the member IDs of their masters. 
If the master in one IRF fabric has the lowest member ID among all the masters, the members in the fabric 
continue to operate in Active state and forward traf fic. MAD sets all the other IRF fabrics in Recovery 
(disabled) state and shuts down all their physical port s but the console ports, physical IRF ports, and any 
ports you have specified with the mad exclude interface  command.  
Failure recovery 
To merge two split IRF fabrics, first repair the failed IRF link and remove the IRF link failure.  
If the IRF fabric in Recovery state fails before the failure is recovered, repair the failed IRF fabric and the 
failed IRF link.  
If the IRF fabric in Active state fails before the failure is recovered, first enable the IRF fabric in Recovery 
state to take over the active IRF fabric and protect the services from being affected. After that, recover the 
MAD failure. 
LACP MAD 
LACP MAD requires that every IRF member have a link with an intermediate device, and all these links 
form a dynamic link aggregation group, as shown in  Figure 5. In addit
 ion, the intermediate device must 
be an HP device that supports extended LACP for MAD. 
T h e  I R F  m e m b e r  swi t c h e s  s e n d  ex t e n d e d  L AC P D U s  wi t h   TLVs that convey the domain ID and the active ID 
of the IRF fabric. The intermediate device transpar ently forwards the extended LACPDUs received from 
one member switch to all the other member switches: 
•   If the domain IDs and the active IDs in the exte nded LACPDUs sent by all the member devices are 
the same, the IRF fabric is integrated. 
•   If the extended LACPDUs convey the same domain ID but different active IDs, a split has occurred. 
To handle this situation, L ACP MAD sets the IRF fabric with higher active ID in Recovery state, and 
shuts down all its physical ports but the console  port, IRF ports, and any ports you have specified 
with the  mad exclude interface  command. The IRF fabric with lower active ID is still in Active state 
and forwards traffic.
    Add page 174 to Favourites
    image text
    Enable zoom 
    							8 
Figure 5 LACP MAD application scenario 
 
 
BFD MAD 
BFD MAD can work with or without intermediate devices. Figure 6 shows a typical BFD MAD application 
scenario. 
To use BFD MAD:  
•   Set up dedicated BFD MAD link between each pai r of IRF members or between each IRF member 
and the intermediate device. Do not use the BFD MAD links for any other purpose. 
•   Assign the ports connected by BFD MAD links to  the same VLAN, create a VLAN interface for the 
VLAN, and assign a MAD IP address to each member on the VLAN interface.  
The MAD addresses identify the  member switches and must belong to the same subnet. 
With BFD MAD, the master tries to establish BFD sessions with other member switches by using its MAD 
IP address as the source IP address: 
•   If the IRF fabric is integrated, only the MAD IP  address of the master is effective, and the master 
cannot establish a BFD session with any other member. If you execute the  display bfd session 
command, the state of the BFD sessions is  Down.  
•   When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect, and the 
two masters can establish a BFD session. If you execute the  display bfd session command, the state 
of the BFD session between the two devices is  Up.
    Add page 175 to Favourites
    image text
    Enable zoom 
    							9 
Figure 6 BFD MAD application scenario 
 
 
ARP MAD 
ARP MAD detects multi-active collisions by using extended gratuitous ARP packets that convey the IRF 
domain ID and the active ID.  
You can set up ARP MAD links between neighbor IRF member devices, or more commonly, between each 
IRF member device and an intermediate device (see  Figure 7)
.  I f  a n  i n t e r m e d i a t e  d e v i c e  i s  u s e d ,  yo u  m u s t  
also run the spanning tree feature between the IRF fabric and the intermediate device. 
Device
Master
IRF
Internet
Terminal  network
IRF link
Link aggregation
BFD MAD linkVLAN 2
192.168.1.2/24 VLAN 2
192.168.1.3/24
    Add page 176 to Favourites
    image text
    Enable zoom 
    							10 
Figure 7 ARP MAD application scenario 
 
 
Each IRF member compares the domain ID and the active ID in incoming extended gratuitous ARP 
packets with its domain ID and active ID: 
•  If the domain IDs are different, the extended gratuitous ARP packet is from a different IRF fabric, and 
the device does not continue to proc ess the packet with the MAD mechanism. 
•   If the domain IDs are the same, the device compares the active IDs: 
{ If the active IDs are different, the IRF fabric has split. 
{ If the active IDs are the same, the IRF fabric is integrated.
    Add page 177 to Favourites
    image text
    Enable zoom 
    							11 
Configuring IRF 
Read the configuration restrictions and guidelines carefully when you connect and set up an IRF fabric.  
General restrictions and configuration guidelines 
This section describes the restrictions and configuration guidelines you must follow.  
Software requirements 
All IRF member switches must run the same system software image version.  
IRF physical port restrictions and cabling requirements 
Candidate IRF physical ports include 10-GE ports on ex pansion interface cards. To use IRF, purchase at 
least one interface card. The following are the interface cards available for IRF connections: 
•   LSPM1XP1P (JD361B) 
•   LSPM1XP2P (JD359B) 
•   LSPM1CX2P (JD360B) 
•   LSPM2SP2P (JD368B) 
For long-distance IRF connections, us e XFP or SFP+ transceiver modules and fibers. For short-distance IRF 
connections, use CX4 or SFP+ cables. For more info rmation about transceiver modules available for an 
interface card, see the interface card user guide. 
For more information about transceiver modules, see  HP A-Series Switches Transceiver Modules User 
Guide. 
The SFP+ modules and SFP+ cables available for this  switch series are subject to change over time. For 
the most up-to-date list of SFP+ modules and cables , contact HP technical support or marketing staff. 
IRF link redundancy 
This switch series supports up to two physical ports to one IRF port. These two ports must be located on 
the same interface card. 
MAD 
•   Configure at least one MAD mechanism for prompt  IRF split detection and IRF fabric recovery.  
•   If LACP MAD or ARP MAD runs between two IRF fabr ics, assign each fabric a unique IRF domain 
ID. For BFD MAD, this task is optional. 
•   BFD MAD is available only on 5500 EI switches.  
•   To exclude a port from the shutdown action performed when an IRF fabric to the Recovery state, use 
the mad exclude interface  command. To bring up a port after the IRF fabric transits to the Recovery 
state, you must use the mad restore  command to activate the entire IRF fabric, rather than using the 
undo shutdown  command.
    Add page 178 to Favourites
    image text
    Enable zoom 
    							12 
Other configuration guidelines 
•  Strictly follow the IRF fabric setup procedure described in  Setup and configuration task list to pla n 
the IRF fabric, identify IRF physical ports, connect IRF member switches, and configure basic 
settings.  
•   Assign each member a unique IRF member ID to make sure they can merge. You must reboot the 
members to validate the IRF member ID settings.  
•   Assign the highest member priority to the device you want to use as the master. 
•   Before removing an interface card that has physical IRF ports in an IRF fabric, remove the IRF 
connection cables, or use the  shutdown command to shut down the IRF physical ports.  
•   If a subordinate switch uses the same next-startup configuration file name as the master switch, the 
file might be overwritten depending on your configuration file management settings. To continue to 
use the configuration file after removing the switch from the IRF fabric, back up the file before setting 
up the IRF fabric. 
•   Save any configuration you have made to the startup configuration file before rebooting the IRF 
member devices.  
•   The Layer 3 Ethernet port in this book refers to an Ethernet port that can perform IP routing and 
inter-VLAN routing. You can set an Ethernet port  as a Layer 3 Ethernet interface by using the port 
link-mode route  command (see  Layer 2—LAN Switching Configuration Guide ). 
•   You can configure an Ethernet port as a Layer  3 Ethernet port only on the 5500 EI switch. 
Setup and configuration task list 
HP recommends the configuration procedure in  Figure 8.  
Figure 8  IRF setup and 
configuration flow chart 
 
 
HP recommends the following IRF fabric setup and configuration procedure:  
Task Remarks 
1.  Planning the IRF fabric setup 
Required.  
2.  Assigning a member ID to each IRF member switch  Required.  
Perform
 this task on each member 
switch. 
3.   Specifying a priority for each member switch  Required. 
Perform
 this task on each member 
switch. 
4.   Connecting physical IRF ports 
Required.
    Add page 179 to Favourites
    image text
    Enable zoom 
    							13 
Task Remarks 
5.  Binding physical ports to IRF ports  Required. 
Perform
 this task on each member 
switch. 
6.   Accessing the IRF fabric : 
{ Accessing the CLI of the master switch 
{ Accessing the CLI of a subordinate switch  Login to the masters CLI is 
required. You configure all 
member switches at the masters 
CLI.  
From the masters CLI, you can log 
in to any other member switchs 
CLI to execute a limited set of 
maintenance commands.  
7.
  Assigning an IRF domain ID to the IRF fabric  T his task is required for ARP MAD 
and LACP MAD.  
8.   Configuring a member switch description 
Optional.  
9.  Configuring IRF link load sharing mode : 
{ Configuring the global load sharing mode 
{ Configuring port-specific load sharing criteria  Optional. 
10.
 Configuring IRF bridge MAC persistence 
Optional.  
11. Enabling software auto-update for system software image 
s
ynchronization  Optional. HP recommends 
enabling software auto-update to 
make sure system software image 
synchronization  
12.
 Setting the IRF link down report delay 
Optional.  
13. Configuring MAD : 
{ Configuring LACP MAD 
{ Configuring BFD MAD 
{ Configuring ARP MAD 
{ Excluding a port from the shutdown action upon detection of 
multi-active collision 
{ Recovering an IRF fabric  Required. MAD mechanisms are 
independent of one another. You 
can configure at least one MAD 
mechanism for an IRF fabric.  
 
Planning the IRF fabric setup 
Consider the following items when you plan an IRF fabric:  
•
  Hardware compatibility and restrictions 
•   IRF fabric size 
•   Master switch 
•   IRF physical ports 
•   Member ID and priority assignment scheme 
•   Fabric topology and cabling scheme 
For more information about hardware and cabling, see the installation guide for the device.
    Add page 180 to Favourites
    image text
    Enable zoom 
    							14 
Assigning a member ID to each IRF member switch 
 
 CAUTION: 
In an IRF fabric, chan
ging IRF member IDs might cause undesirable configuration changes and even data
loss. Before you do that, back up the confi
guration and make sure you fully understand the impact on your
network. For example, all member switches in an IR F fabric are the same model. If you swapped the IDs
of any two members, their interfac e settings would also be swapped.  
 
By default, the member IDs of all switches are 1. To create an IRF fabric, you must assign a unique IRF 
member ID to each switch.  
Perform this task before the IRF fabric is formed. To prevent any undesirable configuration change or data 
loss, avoid changing member IDs after the IRF fabric is formed.  
The new member ID takes effect at a reboot. After the switch reboots, the settings on all member-ID 
related physical resources (including common ph ysical network ports) are removed and require 
reconfiguration, regardless of whether you have saved the configuration.  
To set a member ID for a switch: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Assign an IRF member ID to 
the switch.  irf member 
member-id renumber 
new-member-id   The default IRF member ID is 1.  
3.
  Save the configuration.   save [ safely
 ] [ backup | main ] 
[ force  ]  Optional.  
If you have bound physical ports 
to IRF ports or assigned member 
priority, save the configuration 
before rebooting the switch so 
these settings can continue to 
take effect after the reboot. 
4.
  Reboot the switch.  
reboot [ slot slot-number  ]  N/A 
 
Specifying a priority for each member switch 
IRF member priority represents the possibility for a de vice to be elected the master in an IRF fabric. The 
higher the priority, the higher the possibility. 
A member priority change affects the election result  at the next master election, but does not cause 
immediate master re-election. 
To specify a priority for the switch: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Specify a priority for the 
switch.  irf priority 
priority  The default IRF member priority 
is 1.
    All HP manuals Comments (0)

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