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 161 to Favourites
    image text
    Enable zoom 
    							 149 
Obtaining the configuration file 
Figure 55 Obtaining the configuration file 
 
 
A device obtains its configuration file by using the following workflow: 
•  If the DHCP response contains the configuration file name, the device requests the specified 
configuration file from the TFTP server. 
•   If not, the device tries to get its host name from the host name file obtained from the TFTP server. If 
it fails, the device resolves its IP address to the  host name through DNS server. Once the device gets 
its host name, it requests the configuration file with the same name from the TFTP server.  
•   If all the above operations fail, the device requests the default configuration file from the TFTP server. 
TFTP request sending mode  
The device chooses whether to unicast or broadcast a TFTP request as follows: 
•  If a legitimate TFTP server IP addr ess is contained in the DHCP response, the device unicasts a TFTP 
request to the TFTP server.  
•   If not, the device resolves the TFTP server domain name contained in the DHCP response to the 
corresponding IP address through the DNS server. If successful, the device unicasts a TFTP request 
to the TFTP server; if not, the device broadcasts a TFTP request.
    Add page 162 to Favourites
    image text
    Enable zoom 
    							 150 
•  If the IP address and the domain name of the TFTP  server are not contained in the DHCP response 
or they are illegitimate, the device broadcasts a TFTP request. 
After broadcasting a TFTP request, the device selects  the TFTP server that responds first to obtain the 
configuration file. If the requested configuration file does not exist on the TFTP server, the request 
operation fails, and the device removes the temporary configuration and starts up with the factory 
defaults. 
If the device and the TFTP server reside in different subnets, you must configure the UDP Helper function 
for the gateway to change the broadcast TFTP request from the device to a unicast packet and forward 
the unicast packet to the specified TFTP server. For more information about UDP Helper, see Layer 3—IP 
Services Configuration Guide . 
Executing the configuration file 
After obtaining the configuration file, the device removes the temporary configuration and executes the 
configuration file. If no configuration file is obtained, the device removes the temporary configuration 
and starts up with the factory defaults. 
 
 NOTE:  
If the configuration file contains any IRF configur ation, the device does not execute the IRF confi
guration 
when executing the configuration file.  
The configuration file is deleted after executed. Save the configuration by using the  save command. 
Otherwise, the device has to perform automatic configuration again after reboot. For more information 
about the  save command, see  Fundamentals Command Reference .
    Add page 163 to Favourites
    image text
    Enable zoom 
    							 151 
Index 
A B C D E F H I L M N O P R S T U V  
A 
Accessing the CLI online help,4 
B 
Bac

king up the next-startup configuration file to a TFTP 
server, 96 
C 
C

hanging the brand name, 13 4 
C

hanging the system time, 13 0 
C

learing unused 16-bit interface indexes, 14 2 
CLI v

iews, 2 
C

ommand conventions, 1 
C

onfiguring banners, 13 5 
C

onfiguring configuration rollback, 93 
C

onfiguring HTTP login, 54 
C

onfiguring HTTPS login,55  
Co

nfiguring SNMP login, 61 
C

onfiguring source IP-based SNMP login control, 67 
C

onfiguring temperature thresholds for a device, 141 
C

onfiguring the device name, 13 0 
C

onfiguring the exception handling method, 13 7 
C

onfiguring the port status detection timer, 141 
C

onfiguring user privilege and command levels, 13 
C

onfiguring Web login control, 69 
C

ontrolling Telnet logins, 65 
C

ontrolling the CLI output, 10 
D 
D

eleting the next-startup configuration file, 97 
Disa

bling Boot ROM access, 141 
Displa

ying and maintaining a configuration file, 98 
Displa

ying and maintaining CLI, 19 
Displa

ying and maintaining CLI login, 53 
Displa

ying and maintaining device management, 14 3 
Displa

ying and maintaining FTP, 80 
Displa

ying and maintaining software upgrade, 10 8 
Displa

ying and maintaining the TFTP client, 82 
Displa

ying and maintaining Web login, 57  E 
Ena

bling displaying the copyright statement,
13 3 
En

tering a command, 5 
F 
F

ile system management examples, 88 
H 
Ho

w automatic configuration works, 14 6 
HT

TP login configuration example, 57 
HT

TPS login configuration example, 59 
I 
IS

SU overview, 112  
L 
L

ogging in through SSH, 40 
L

ogging in through Telnet,32  
L

ogging in through the console port for the first time, 23 
L

ogging in to the CLI, 1 
L

ogin methods at a glance, 21 
M 
Managing dir

ectories, 86 
Managing f

iles, 84 
Managing st

orage media,87  
Modem di

al-in through the console port, 43 
N 
Net

work requirements, 12 0 
Net

work status,12 0  
NM

S login example, 63 
O 
Ov

erview, 90 
P 
Pe

r fo rm i n g  a n  I SSU, 114  
P

erforming batch operations, 88 
Pr

erequisites,81  
R
    Add page 164 to Favourites
    image text
    Enable zoom 
    							 152 
Rebooting the device,13 7 
R
estoring the next-startup configuration file from a TFTP 
server, 97 
S 
S

aving the running configuration, 91 
S

aving the running configuration, 19 
Sc

heduling jobs, 13 9 
Set

ting the file system operation mode, 88 
S

oftware upgrade examples, 10 8 
S

oftware upgrade methods, 99 
S

pecifying a configuration file for the next startup, 96 
T 
T

FTP client configuration example, 82 
T

ypical application scenario, 14 5  U 
U

nderstanding command-line error messages,
8 
U

pgrade procedure, 121 
Upgr

ading software by installing hotfixes, 101 
U

pgrading software through a system reboot, 10 0 
Us

er interfaces, 22 
U

sing the command history function, 9 
U

sing the device as a TFTP client, 81 
U

sing the device as an FTP client, 71 
U

sing the device as an FTP server, 76 
U

sing the undo form of a command, 2 
V 
V

erifying and diagnosing transceiver modules, 14 2
    Add page 165 to Favourites
    image text
    Enable zoom 
    							i 
Contents 
IRF overview ··················\
··················\
··················\
··················\
··················\
··················\
························\
··················\
··········· 1 
Hardware compatibility ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
···  1 
IRF benefits ··················\
··················\
··················\
··················\
··················\
··················\
························\
··················\
··················\
· 1 
Application scenario ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
········  1 
Basic concepts ··················\
··················\
··················\
··················\
··················\
··················\
······················\
··················\
··············· 2 
IRF member roles ··················\
··················\
··················\
··················\
··················\
··················\
·· ··················\
··················\
···· 2 
IRF member ID ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
··········  2 
IRF port ··················\
··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
············ 2 
Physical IRF port ··················\
··················\
··················\
··················\
··················\
··················\
· ··················\
··················\
······ 3 
IRF domain ID ··················\
··················\
··················\
··················\
··················\
··················\
····· ··················\
··················\
······ 3 
IRF split ·················\
··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
············· 3 
IRF merge ·················\
··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
········· 4 
Member priority ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
·······  4 
Interface naming conventions ··················\
··················\
··················\
··················\
··················\
········ ··················\
··················\
···· 4 
File system naming conventions··················\
··················\
··················\
··················\
··················\
······· ··················\
··················\
·· 5 
Configuration synchronization mechanism ··················\
··················\
··················\
··················\
··············· ··················\
··········· 6 
Master election ··················\
··················\
··················\
··················\
··················\
··················\
··· ··················\
··················\
··············· 6 
IRF multi-active detection ··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
·········· 6 
Multi-active handling procedure ·················\
··················\
··················\
··················\
··················\
······ ··················\
············ 6 
LACP MAD ··················\
··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
······ 7 
BFD MAD ··················\
··················\
··················\
··················\
··················\
··················\
··········· ··················\
··················\
······· 8 
ARP MAD ··················\
··················\
··················\
··················\
··················\
··················\
··········· ··················\
··················\
······· 9 
Configuring IRF ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
··········  11 
General restrictions and configuration guidelines ··················\
··················\
··················\
··················\
··················\
············  11 
Software requirements ··················\
··················\
··················\
··················\
··················\
··············· ··················\
··············· 11 
IRF physical port restrictions  and cabling requirements ··················\
··················\
··················\
················· ············· 11 
IRF link re dundancy ··················\
··················\
··················\
··················\
··················\
················· ··················\
··················\
 11 
MAD ··················\
··················\
··················\
··················\
··················\
··················\
··············· ··················\
··················\
········ 11 
Other configuration guidelines ··················\
··················\
··················\
··················\
··················\
······ ··················\
·········· 12 
Setup and configuration task list ··················\
··················\
··················\
··················\
··················\
··· ··················\
··················\
· 12 
Planning the IRF fabric setup  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···········  13 
Assigning a member ID to each IRF member switch ··················\
··················\
··················\
··················\
······· ··················\
· 14 
Specifying a priority for each member switch ··················\
··················\
··················\
··················\
·········· ··················\
········ 14 
Connecting physical IRF ports  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
·········  15 
Connection restrictions ··················\
··················\
··················\
··················\
··················\
··················\
··················\
············  15 
IRF fabric topology ··················\
··················\
··················\
··················\
··················\
················· ··················\
··················\
· 15 
Binding physical ports to IR F ports ··················\
··················\
··················\
··················\
··················\
· ··················\
··················\
 16 
Accessing the IRF fabric ··················\
··················\
··················\
··················\
··················\
············ ··················\
··················\
······ 17 
Accessing the CLI of the master switch ··················\
··················\
··················\
··················\
················ ··················\
····· 17 
Accessing the CLI of a  subordinate switch ··················\
··················\
··················\
··················\
············· ··················\
·· 17 
Assigning an IRF domain  ID to the IRF fabric ··················\
··················\
··················\
··················\
··················\
··················\
··  18 
Configuring a member switch description··················\
··················\
··················\
··················\
················ ··················\
········· 19 
Configuring IRF link  load sharing mode ··················\
··················\
··················\
··················\
················ ··················\
············ 19 
Configuring the global  load sharing mode ··················\
··················\
··················\
··················\
·············· ··················\
 20 
Configuring port-specific  load sharing criteria ··················\
··················\
··················\
··················\
······· ··················\
· 20 
Configuring IRF bridge MAC persistence  ··················\
··················\
··················\
··················\
··················\
··················\
········  20 
Enabling software auto-update for system software image synchronization ··················\
··················\
··················\
· ···· 21 
Setting the IRF link  down report delay ··················\
··················\
··················\
··················\
················ ··················\
··············· 22 
    Add page 166 to Favourites
    image text
    Enable zoom 
    							ii 
Configuring MAD ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
··········  22 
Configuring LACP MAD ··················\
··················\
··················\
··················\
··················\
··················\
··················\
··········  23 
Configuring BFD MAD ··················\
··················\
··················\
··················\
··················\
················· ··················\
············· 24 
Configuring ARP MAD  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
············  25 
Excluding a port from the shutdown action upon detection of multi-active collision ··················\
··················\
·· 26 
Recovering an IRF fabric  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
·········  27 
Displaying and maintaining an IRF fabric ··················\
··················\
··················\
··················\
··················\
··················\
·······  28 
Configuration examples ··················\
··················\
··················\
··················\
··················\
·············· ··················\
··················\
···· 29 
LACP MAD-enabled IRF configuration example  ··················\
··················\
··················\
··················\
··················\
·······  29 
BFD MAD-enabled IRF configuration example ··················\
··················\
··················\
··················\
············· ·············· 31 
ARP MAD-enabled IRF configuration example  ··················\
··················\
··················\
··················\
··················\
·········  34 
Index ··················\
··················\
··················\
··················\
··················\
··················\
············· ··················\
··················\
·············· 37 
    Add page 167 to Favourites
    image text
    Enable zoom 
    							1 
IRF overview 
The HP Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple switches 
to provide data center class availability and scalability. IRF virtualization technology offers processing 
power, interaction, unified management, and uninterrupted maintenance of multiple switches.  
This book describes IRF concepts and guides you through the IRF setup procedure.  
Hardware compatibility 
5500 switches in an IRF fabric must be the same sub-series. For example, a 5500 EI and a 5500 SI 
cannot form an IRF fabric. 
To use IRF on these switches, you must purchase at least one 10-GE interface card listed in  IRF physical 
por

t restrictions and cabling requirements . 
IRF benefits 
IRF delivers the following benefits: 
•  Simplified topology and easy management —An IRF fabric appears as one node and is accessible 
at a single IP address on the network. You can use  this IP address to log in at any member device 
to manage all the members of the IRF fabric. In addition, you do not need to run the spanning tree 
feature among the IRF members.  
•   1:N redundancy —In an IRF fabric, one member works as the master to manage and control the 
entire IRF fabric, and all the other members proces s services while backing up the master. When the 
master fails, all the other member devices elect a  new master from among them to take over without 
interrupting services.  
•   IRF link aggregation —You can assign several physical links between neighboring members to their 
IRF ports to create a load-balanced aggregate IRF connection with redundancy.  
•   Multiple-chassis link aggregation —You can use the Ethernet link aggregation feature to aggregate 
the physical links between the IRF fabric and its upstream or downstream devices across the IRF 
members. 
•   Network scalability and resiliency —Processing capacity of an IRF fabric equals the total 
processing capacities of all the members. You can increase ports, network bandwidth, and 
processing capacity of an IRF fabric simply by adding member devices without changing the 
network topology.  
Application scenario 
Figure 1  shows an IRF fabric that comprises two switches, which appear as a single node to the upper 
and lower layer devices.
    Add page 168 to Favourites
    image text
    Enable zoom 
    							2 
Figure 1 IRF application scenario 
 
 
Basic concepts 
This section describes the basic concepts that you might encounter when working with IRF.  
IRF member roles 
IRF uses two member roles: master and slave (called subordinate throughout the documentation).  
When switches form an IRF fabric, they elect a mast er to manage the IRF fabric, and all other switches 
back up the master. When the master switch fails,  the other switches automatically elect a new master 
from among them to take over. For more information about master election, see  Master election.
  
IRF member ID 
An IRF fabric uses member IDs to uniquely identify and manage its members. This member ID information 
is included as the first part of interface numbers and fi le paths to uniquely identify interfaces and files in 
an IRF fabric. For more information about interface and file path naming, see  Interface naming 
co

nventions  and File system naming conventions .  
If t

wo switches have the same IRF member ID, they cannot form an IRF fabric.  
IRF port 
An IRF port is a logical interface for the connect ion between IRF member devices. Every IRF-capable 
device supports two IRF ports. Th e IRF ports are named IRF-port n/1 and IRF-port  n/2, where n  is the 
member ID of the switch. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book 
for simplicity. 
To use an IRF port, you must bind at least one physical port to it. The physical ports assigned to an IRF 
port automatically form an aggregate IRF link. An IRF port goes down only if all its physical IRF ports are 
down.
    Add page 169 to Favourites
    image text
    Enable zoom 
    							3 
Physical IRF port 
Physical IRF ports connect IRF member devices and must be bound to an IRF port. They forward IRF 
protocol packets between IRF member devices and data packets that must travel across IRF member 
devices. 
For more information about physical ports that can be used for IRF links, see  General restrictions and 
c

onfiguration guidelines . 
IRF domain ID 
One IRF fabric forms one IRF domain. IRF uses IRF doma in IDs to uniquely identify IRF fabrics and prevent 
IRF fabrics from interfering with one another.  
As shown in  Figure 2, S
witch A and Switch B form IRF fabric 1, and Switch C and Switch D form IRF fabric 
2. The fabrics have LACP MAD detection links between them. When a member switch in one IRF fabric 
receives an extended LACP packet for MAD detection,  it looks at the domain ID in the packet to see 
whether the packet is from the local IRF fabric or from a different IRF fabric. Then, the switch can handle 
the packet correctly. 
Figure 2  A network that comprises two IRF domains 
 
 
IRF split 
I RF split occurs when an I RF fabric breaks up into t wo or more I RF fabrics because of I RF link failures, as 
shown in Figure 3. T
he split IRF fabrics operate with the same IP address and cause routing and 
forwarding problems on the network. To quickly dete ct a multi-active collision, configure at least one 
MAD mechanisms (see  IRF multi-active detection)
 .  
Switch A
Switch BIRF 1 (domain 10)
IRF link
Core network
IRF 2 (domain 20)
IRF link
Switch C
Switch D
Access network
    Add page 170 to Favourites
    image text
    Enable zoom 
    							4 
Figure 3 IRF split 
 
 
IRF merge 
IRF merge occurs when two split IRF fabrics re-unite or when you configure and connect two independent 
IRF fabrics to be one IRF fabric, as shown in Figure 4. 
Figure 4  IRF merge 
 
 
Member priority 
Member priority determines the possibility of a member device to be elected the master. A member with 
higher priority is more like ly to be elected the master. 
The default member priority is 1. You can change the member priority of a member device to affect the 
master election result. 
Interface naming conventions 
An interface is named in the format of  member-id/slot-number /port-index , where:  
•   member-id —If the switch is standalone, the member ID  defaults to 1. If the standalone switch was 
once an IRF member switch, it uses the same member ID as it was in the IRF fabric.   
•   slot-number —Represents the slot number of the interfac e card. This argument takes 0 for the fixed 
ports on the front panel, and takes 1 and 2 for the two  interface cards (from left to right) on the rear 
panel.  
•   port-index —Port index depends on the number of ports available on the switch. To identify the 
index of a port, look at its port index mark on the chassis. 
For one example, on the standalone switch Sysname, GigabitEthernet 1/0/1 represents the first fixed 
port on the front panel. Set its link type to trunk, as follows: 
 system-view 
[Sysname] interface gigabitethernet 1/0/1 
[Sysname-GigabitEthernet1/0/1] port link-type trunk 
For another example, on the IRF fabric Master, Gigabi tEthernet 3/0/1 represents the first fixed port on 
the front panel of member switch 3. Set its link type to trunk, as follows: 
 system-view
    All HP manuals Comments (0)

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