Professional Documents
Culture Documents
HP Irf PDF
HP Irf PDF
IRF
Configuration Guide
Abstract
This document describes the software features for the HP 5820X & 5800 Series products and guides you
through the software configuration procedures. These configuration guides also provide configuration
examples to help you apply software features to different network scenarios.
This documentation is intended for network planners, field technical support and servicing engineers, and
network administrators working with the HP 5820X & 5800 Series products.
Contents
IRF configuration 4
IRF overview 4
Benefits 4
Application scenario 5
IRF topologies 5
Basic concepts6
Establishment, operation, and maintenance of an IRF virtual device7
Connecting the IRF member switches7
Topology collection 10
Master election 10
IRF virtual device management and maintenance 10
IRF multi-active detection 12
IRF virtual device configuration task list 13
Configuring an IRF virtual device 14
Specifying a domain ID for an IRF virtual device 14
Changing the IRF member ID of a switch 16
Configuring IRF ports 16
Specifying a priority for a member switch 18
Configuring a description for a member switch 18
Configuring load sharing criteria for IRF links 18
Specifying the preservation time of bridge MAC address 20
Enabling automatic boot file updating 21
Setting the IRF link down report delay 22
Configuring MAD detection 22
Configuring LACP MAD 23
Configuring BFD MAD 25
Accessing an IRF virtual device 31
Accessing the master 31
Accessing a slave switch 32
Displaying and maintaining an IRF virtual device 32
IRF virtual device configuration examples 33
LACP MAD detection-enabled IRF configuration example 33
BFD MAD detection-enabled IRF configuration example 35
ARP MAD detection-enabled IRF configuration example 38
Contacting HP 41
Subscription service 41
Related information 41
Documents 41
Websites 41
Conventions 42
Index 44
iii
IRF configuration
Establish an IRF virtual device that comprises switches of the HP 5820X series or 5800 series, or establish
a mixed IRF virtual device that comprises both the HP 5820X and 5800 switches.
IRF overview
The HP proprietary IRF technology creates a large IRF virtual device from multiple switches to provide data
center class availability and scalability. IRF virtualization technology takes advantage of the augmented
processing power, interaction, unified management, and uninterrupted maintenance of multiple switches.
Benefits
IRF delivers the following benefits:
Simplified topology and streamlined management. An IRF virtual device appears as one node on
the network. Log in at any member switch to manage all members of the IRF virtual device.
High availability and reliability. The member switches in an IRF virtual device work in 1:N
redundancy. One member switch works as the master to manage and maintain the entire IRF virtual
device. All other member switches process services as well as back up the master. As soon as the
master fails, all other member switches elect a new master among them to prevent service
interruption. In addition, you can perform link aggregation not only for IRF links, but also for
physical links between the IRF virtual device and its upper or lower layer devices for link redundancy.
Network scalability and resiliency. Increase ports, bandwidth, and processing capability of an IRF
virtual device simply by adding member switches.
Application scenario
Figure 1 shows an IRF virtual device that comprises two switches, which appear as a single node to the
upper and lower layer devices.
Figure 1 IRF application scenario
IP network
IP network
Slave
Master
IRF link
Equal to
IRF topologies
Create an IRF virtual device in daisy chain topology, or more reliably, ring topology, as shown in Figure 2.
In ring chain topology, the failure of one IRF link does not cause the IRF virtual device to split as in daisy
chain topology. Rather, the IRF virtual device changes to a daisy chain topology without affecting network
services.
Figure 2 IRF connections
Basic concepts
IRF member switch roles
IRF uses two member switch roles: master and subordinate (slave).
When switches form an IRF virtual device, they elect a master to manage the IRF virtual device, 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 avoid service interruption. For more information about master election,
see Master election.
IRF port
An IRF port is a logical interface for the internal connection between IRF member switches. Each IRF
member switch has two IRF ports: IRF-port 1 and IRF-port 2. An IRF port is activated when you bind a
physical port to it.
IRF partition
IRF partition occurs when an IRF virtual device splits into two or more IRF virtual devices because of IRF
link failures, as shown in Figure 3. The partitioned IRF virtual devices operate with the same IP address
and cause routing and forwarding problems on the network.
Figure 3 IRF partition
IRF merge
IRF merge occurs when two partitioned IRF virtual devices re-unite or when you configure and connect
two independent IRF virtual devices to be one IRF virtual device, as shown in Figure 4.
Figure 4 IRF merge
Member priority
Member priority determines the role that a member switch can play in an IRF virtual device. A member
with a higher priority is more likely to be a master. The member priority of a switch is user configurable,
and defaults to 1. Modify the priority at the CLI.
5800-48G-PoE+ TAA
Requirements
5800AF-48G Switch
(JG225A)
5800-48G-PoE+
5800-48G-PoE+ TAA
Switch model
5800-24G Switch
(JC100A)
5800-24G-PoE+
Switch (JC099A)
5800-24G-PoE+TAA
Requirements
Switch (JG254A)
5800-24G-SFP Switch
with 1 Interface Slot
(JC103A)
5800-24G-SFP TAA
5820X-14XG-SFP+
5820X-14XG-SFP+
5820X-24XG-SFP+
Switch (JC102A)
5820X-24XG-SFP+
TAA-compliant Switch
(JG243A)
HP 5820AF-24XG Switch
For a complete list of supported SFP+ ports and interface cards, see HP 5800 Switch Series Installation
Guide and HP 5820X Switch Series Installation Guide.
Table 2 lists the SFP+ transceiver modules, optical fibers, and SFP+ cables available for connecting the
physical IRF ports on the HP 5800 and 5820X switches.
Table 2 SFP+ transceivers, optical fibers, and SFP+ cables available for physical IRF ports
Product code
Module
description
Central
wavelengt
h (in nm)
Connector
Fiber
specifications
Maximum
transmission distance
300 m (984.25 ft)
JD092B
JD093B
HP X130 10G
SFP+ LC SR
Transceiver
HP X130 10G
SFP+ LC LRM
Transceiver
50/125 m
multimode fiber
850
LC
66 m (216.54 ft)
62.5/125 m
multimode fiber
62.5/125 m
multimode fiber
1310
LC
82 m (269.03 ft)
50/125 m
multimode fiber
33 m (108.27 ft)
26 m (85.30 ft)
220 m (721.78 ft)
220 m (721.78 ft)
100 m (328.08 ft)
JD094B
HP X130 10G
SFP+ LC LR
Transceiver
JD095B
HP X240 10G
SFP+ SFP+
0.65m DA
Cable
JD096B
HP X240 10G
SFP+ SFP+
1.2m DA
Cable
1310
1550
N/A
LC
N/A
9/125 m
single-mode fiber
10 km (6.21 miles)
40 km (24.86 miles)
SFP+ cable
JD097B
HP X240 10G
SFP+ SFP+ 3m
DA Cable
3 m (9.8 ft)
JG081B
HP X240 10G
SFP+ SFP+ 5m
DA Cable
5 m (16.4 ft)
If the IRF member switches are located far from each other, use the SFP+ transceivers with optical fibers. If
the IRF member switches are all in one equipment room, use the SFP+ cable.
For more information about the interface 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.
Topology collection
Each member switch exchanges IRF hello packets with its directly connected neighbors to collect topology
data, including IRF port connection states, member IDs, priorities, and bridge MAC addresses.
Each member switch has a local topology database. At startup, an IRF member switch has only local
topology data. When an IRF port goes up, the member switch sends its topology data out of the port
periodically. The neighbor switch then updates its topology database with the received topology data.
The topology collection lasts for a period of time. After all members eventually get complete topology
information (topology convergence), the IRF virtual device enters the next stage: master election.
Master election
Master election is held each time the topology changes, for example, when the IRF virtual device is
established, a new member switch is plugged in, the master switch fails or is removed, or the partitioned
IRF virtual devices merge.
The master is elected based on the following rules in descending order:
1.
The current master, even if a new member has a higher priority. When an IRF virtual device is
being formed, all member switches consider themselves as the master, this rule is skipped.
2.
3.
The member with the longest system up-time. The member switches exchange system up-time in the
IRF hello packets.
4.
Member ID
An IRF virtual device uses member IDs to uniquely identify its members. Member IDs are also included in
interface names and file system names for interface and file system identification. To guarantee the
operation of the IRF virtual device, you must assign each member switch a unique member ID.
10
The member ID identifies the IRF member switch on which the interface resides. 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 virtual device.
The subslot number is the number of the slot in which the interface card resides. On the 5800 series
or 5820X series, the subslot for the fixed ports on the front panel is numbered 0. If the switch has
one expansion slot, the number of the slot is 1. If the switch has two expansion slots, their numbers
are 1 and 2, from left to right.
The interface serial number depends on the number of interfaces provided by the switch. Look at the
number on the silkscreen on the interface card for the number of supported interfaces.
For 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:
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port link-type trunk
For another example, on the IRF virtual device Master, GigabitEthernet 3/0/1 represents the first fixed
port on the front panel of member switch 3. Set its link type to trunk:
<Master> system-view
[Master] interface gigabitethernet 3/0/1
[Master-GigabitEthernet3/0/1] port link-type trunk
1.
-rw-
10105088
test.app
-rw-
2445
config.cfg
drw-
test
2.
To create and access the test folder under the root directory of the Flash on member switch 3,
perform the following steps:
11
Or:
<Master> cd slot3#flash:/
<Master> mkdir test
%Created dir slot3#flash:/test.
3.
To copy the test.app file on the master to the root directory of the Flash on member switch 3,
perform the following steps:
<Master> pwd
slot3#flash:
//The current working path is the root directory of the Flash on slave 3.
<Master> cd flash:/
<Master> pwd
flash:
//The current working path is the root directory of the Flash on the master.
<Master> copy test.app slot3#flash:/
Copy flash:/test.app to slot3#flash:/test.app?[Y/N]:y
%Copy file flash:/test.app to slot3#flash:/test.app...Done.
When a subordinate switch starts up, it automatically gets and runs the master's configuration file. If
all switches in an IRF virtual device start up simultaneously, the subordinate switches get and run the
master's startup configuration file.
Any configuration you made on the IRF virtual device is stored on the master and synchronized in
real time to each member switch. When you save the current configuration to the startup
configuration file of the master by using the save command, all subordinate switches execute the
same saving operation.
This real-time configuration synchronization ensures that all the IRF member switches keep the same
configuration file. If the master fails, all the other switches can still operate with the same configuration file.
Detection
12
MAD detects active IRF devices with the same Layer 3 global configuration by extending the LACP, the
BFD protocol, or the gratuitous ARP. For more information, see Configuring MAD detection.
2.
Collision handling
If multiple identical active IRF virtual devices are detected, only the one that has the lowest master ID can
operate in active state and forward traffic normally. MAD sets all other IRF virtual devices in the recovery
state (disabled) and shuts down all physical ports but the IRF ports and any other ports you have
specified with the mad exclude interface command.
3.
Failure recovery
An IRF link failure triggers IRF virtual device partition and causes multi-active collision. In this case, repair
the failed IRF link to make the collided IRF virtual devices merge into one and recover the failure. If the IRF
virtual device in the recovery state fails before the failure is recovered, repair both the failed IRF virtual
device and the failed IRF link, and then the collided IRF virtual devices can merge into one and the failure
is recovered. If the IRF virtual device in the active state fails before the failure is recovered, enable the IRF
virtual device in the recovery state at the CLI to make it take over the active IRF virtual device and protect
the services from being affected. Then, recover the MAD failure.
For more information about LACP, see Layer 2LAN Switching Configuration Guide. For information
about BFD, see High Availability Configuration Guide. For information about gratuitous ARP, see Layer
3IP Services Configuration Guide.
Connect physical IRF ports with SFP+ cables or fibers after activating IRF port configurations. After the
device detects that the IRF ports are connected normally, master election starts immediately, and then the
elected subordinate switches reboot automatically.
After an IRF virtual device is formed, configure and manage the IRF virtual device by logging in to any
device in the IRF.
Complete the following tasks to configure an IRF virtual device:
Task
Remarks
Optional.
Required.
Required.
Optional.
Optional.
13
Task
Remarks
Optional.
Optional.
Optional.
Optional.
Connect the physical IRF ports of devices and make sure that the physical IRF ports are interconnected (a
ring connection is recommended).
Configuring MAD
detection
Accessing an IRF
virtual device
Optional.
Optional.
Optional.
Required.
Optional.
14
Switch A
Switch B
IRF link
Switch C
Switch D
IRF link
Access network
Remarks
system-view
You must assign a domain ID for an IRF virtual device before enabling LACP MAD detection.
Although switches with different domain IDs can form an IRF virtual device, HP recommends that you
assign the same domain ID to the members of the same IRF virtual device. Otherwise, the LACP MAD
detection function cannot function properly.
To display the domain IDs and verify your configuration, execute the display irf command in any view.
15
If you do not reboot the switch, the original member ID still takes effect and all physical resources
are identified by the original member ID. In the configuration file, only the IRF port numbers,
configurations on IRF ports, and priority of the device change with the member ID, other
configurations do not change.
If you save the current configuration and reboot the switch, the new member ID takes effect and all
physical resources are identified by the new member ID. In the configuration file, only the IRF port
numbers, configurations on IRF ports, and priority of the device still take effect, other configurations
(such as configuration for physical IRF ports) no longer take effect and you will need to configure
them again.
Change the IRF member ID of a switch when it is standalone or after it joins an IRF virtual device. If the
switch is standalone, make sure that the member ID of the switch does not conflict with the member ID of
any other switch, so the change does not affect the operation of the IRF virtual device. After changing the
member ID, save the current configuration, power off the switch, connect the switch to its neighbor switch,
power it on, and configure the IRF port to enable IRF on the switch.
To change the IRF member ID of a switch:
To do
Remarks
system-view
Optional.
The member ID of a switch
defaults to 1.
Verify the IRF member ID of a switch with the display irf configuration command.
16
Remarks
system-view
shutdown
Required.
quit
irf-port member-id/port-number
Required.
By default, no physical port is
bound to any IRF port.
quit
undo shutdown
Required.
quit
save
Required.
irf-port-configuration active
Required.
Bind up to four physical ports to an IRF port for link redundancy and load sharing. The physical ports
must meet the requirements in Table 1.
Before you create or remove an IRF port binding, always shut down the physical IRF port. After you are
finished, perform the undo shutdown command to bring up the port.
Before unplugging an interface card that contains any IRF physical port, unplug the cable of the port or
shut down the port by using the shutdown command in IRF physical port view.
Perform only the shutdown, description and flow-interval commands on the physical port bound to an IRF
port. For more information about the shutdown, description, and flow-interval commands, see Layer 2
LAN Switching Command Reference.
17
Remarks
system-view
Optional.
The priority of a member
defaults to 1.
The priority setting takes effect immediately after configuration without the need to reboot the switch.
Remarks
system-view
Optional
Not configured by default
Source IP address
Destination IP address
Configure global or IRF port specific load sharing criteria. The switch preferentially uses the port-specific
load sharing criteria. If no port-specific load sharing criteria is available, it uses the global load sharing
criteria.
18
system-view
Remarks
Required.
By default:
Remarks
system-view
irf-port member-id/port-number
19
To do
Remarks
Required.
By default:
irf mac-address persistent timerPreserves the bridge MAC address for 6 minutes after the master
leaves. If the master does not come back before the timer expires, the IRF virtual device uses the
bridge MAC address of the newly elected master as its bridge MAC address. This option avoids
unnecessary switching of bridge MAC address due to a device reboot or transient link failure.
irf mac-address persistent alwaysKeeps the bridge MAC address even after the master leaves.
undo irf mac-address persistentUses the bridge MAC address of the newly elected master to
replace the original one as soon as the master leaves.
20
To specify the preservation time of the bridge MAC address of an IRF virtual device:
To do
Remarks
system-view
Optional.
By default, the IRF virtual device
preserves its bridge MAC
address for 6 minutes after the
master leaves.
Upload the software version file to be used to the master, and then use the bootrom upgrade
command to upgrade the BootROM of the master.
2.
Use the boot-loader command with the slot all keywords to specify the software version file as the
boot file to be used at the next reboot and apply this configuration on all member switches.
3.
Reboot the all member switches in the IRF virtual device to complete the software upgrade process.
When you add a switch to the IRF virtual device, the automatic boot file updating function compares the
software versions of the switch and the IRF master. If the versions are different, the switch automatically
downloads the boot file from the master, sets the downloaded file as the boot file for the next reboot, and
automatically reboots with the new boot file to re-join the IRF virtual device.
If automatic upgrade of boot file is enabled, as soon as a switch is added into an IRF virtual device, the
IRF virtual device compares its software version with that of the master. If the versions are not consistent,
the switch automatically downloads the boot file from the master, reboots with the new boot file, and joins
the IRF virtual device again. If the downloaded boot file and the local boot file have duplicate file names,
the local file is overwritten.
21
To enable an IRF virtual device to automatically synchronize the boot file of the master to the switch you
are adding to the IRF virtual device:
To do
Remarks
system-view
Optional
Enabled by default
If the IRF link state changes from up to down, the port does not immediately report the link state
changes to the IRF virtual device. If the IRF link state is still down when the configured time is
reached, the port reports the link state changes to the IRF virtual device.
If the link state changes from down to up, the link layer immediately reports the event to the IRF
virtual device.
Remarks
system-view
Optional.
The function is disabled by
default.
LACP MAD
BFD MAD
ARP MAD.
These MAD detection mechanisms operate independently, and you can configure all of them for an IRF
virtual device.
22
If the domain IDs are different, the extended LACPDU is from a different IRF virtual device, and the
switch does not continue to process the extended LACPDU with the MAD mechanism.
If the domain IDs are the same, the switch compares the active IDs:
1.
If the active IDs are different, the IRF virtual device has split.
If the active IDs are the same, the IRF virtual device is operating normally.
Network requirements
Every IRF member switch has a link with an intermediate switch, and all these links form a dynamic link
aggregation group, as shown in Figure 8.
The intermediate switch must be an HP switch capable of handling extended LACPDUs that carry the
Active ID field. For more information about LACP and the support of the switch for extended LACPDUs,
see Layer 2LAN Switching Configuration Guide.
23
Device
IRF virtual
device
IRF link
Slave
Master
Internet
2.
Configuring LACP MAD detection
Configure LACP MAD detection by following these steps:
Configure the aggregation group to work in dynamic aggregation mode (also required on the
intermediate device)
Enable LACP MAD detection on the dynamic aggregate interface (not required on the intermediate
device)
Add member ports to the aggregation group (also required on the intermediate device)
24
Remarks
system-view
interface bridge-aggregation
interface-number
Required.
By default, the domain ID of an
IRF virtual device is 0.
Required.
Required.
link-aggregation mode dynamic
mad enable
quit
Required.
BFD MAD is implemented with the BFD protocol. To configure BFD MAD detection, configure a MAD IP
address on a BFD-enabled Layer 3 interface for each member switch. This MAD address identifies the
member during BFD MAD detection. The MAD IP addresses assigned to the member switches must
belong to the same network segment.
25
When the IRF virtual device operates normally, only the MAD IP address of the master is effective
and the BFD session is down.
When the IRF virtual device partitions, the MAD IP addresses of the masters in different IRF virtual
devices become effective to activate the BFD sessions to detect for multi-active IRF virtual device
collision.
2.
Network requirements
BFD MAD detection can be achieved with or without intermediate devices. In a BFD MAD network
without an intermediate device, connect all IRF member switches with dedicated BFD MAD links in the full
mesh topology, as shown in Figure 9. The interfaces connected by BFD MAD links must belong to the
same VLAN. In VLAN interface view, assign different IP addresses on the same network segment for
different member switches.
Figure 9 Network diagram for BFD MAD detection
Create a VLAN dedicated for BFD MAD detection (also required on the intermediate device if any)
Select the physical IRF ports to be used for BFD MAD detection (at least one on each member switch)
and add them into the detection-dedicated VLAN (also required on the intermediate device if any)
Create VLAN interfaces for the detection-dedicated VLAN, enable BFD MAD detection on these
interfaces, and then assign MAD IP addresses for them.
26
Remarks
system-view
vlan vlan-id
quit
Access port
Required.
Trunk port
5. Assign the
port to the
VLAN
dedicated
for the BFD
MAD
detection
Hybrid port
Required.
quit
Required.
Disabled by default.
Required.
By default, no MAD IP address
is configured for any interface.
You must assign all ports on the BFD MAD detection link (on both the IRF member and the intermediate
device) to the BFD MAD VLAN, the VLAN specific to the BFD MAD-enabled VLAN interface.
A BFD MAD-enabled VLAN interface and all ports in the VLAN do not support any Layer 2 and Layer 3
protocol applications, including ARP and LACP.
You cannot enable BFD MAD on VLAN-interface 1.
Do not bind a BFD MAD-enabled Layer 3 interface to any VPN instance. The MAD function cannot work
with VPN.
Do not enable the spanning tree function on the ports on the BFD MAD detection link. The MAD function
cannot work with the spanning tree function.
Assign the MAD IP address for an interface used for BFD MAD detection only with the mad ip address
command, and cannot configure other IP addresses for it ( including common IP address or VRRP virtual
IP address configured with the ip address command).
If an IRF virtual device configured with the BFD MAD function is partitioned into two IRF virtual devices,
routing
collision
information
(for
example,
%May
5
16:15:47:733
2010
HP
ARP/3/ROUTECONFLICT:Chassis=2-Slot=5;Route conflict found, IP:192.168.2.1, VrfIndex:0) may be
generated because the new IRF virtual devices still keep the forwarding entries with the destination being
the original master. This collision information does not affect the switch forwarding and automatically
stops to be generated with the aging of the forwarding entries.
27
With ARP MAD, an IRF member switch sends extended gratuitous ARP packets that convey the domain ID
and active ID of the IRF virtual device for detecting an IRF split. The domain ID uniquely identifies an IRF
virtual device in the network, and the active ID is identical to the member ID of the master switch in the
IRF virtual device.
An IRF member switch compares the domain ID and the active ID in each received extended gratuitous
ARP packet with its domain ID and active ID:
If the domain IDs are different, the extended gratuitous ARP packet is from a different IRF virtual
device, and the switch does not continue to process the packet with the MAD mechanism.
If the domain IDs are the same, the switch compares the active IDs:
2.
If the active IDs are different, the IRF virtual device has split.
If the active IDs are the same, the IRF virtual device is operating normally.
Network requirements
Set up ARP MAD links between neighbor IRF member switches, or more commonly, between each IRF
member switch and an intermediate switch (see Figure 10). If an intermediate switch is used, you must
enable MSTP on the intermediate switch and the IRF virtual device.
Figure 10 Network diagram for ARP MAD detection
28
3.
Remarks
system-view
Required.
vlan vlan-id
quit
Access port
Required.
Trunk port
6. Assign the
port to the
VLAN
dedicated
for the ARP
MAD
detection
Hybrid port
quit
Required.
No IP address is assigned to
any VLAN interface by default.
Required.
Remarks
system-view
Required.
mad exclude interface interface-type
interface-number
29
Physical IRF ports are not shut down when the IRF virtual device transits to recovery state.
If a certain VLAN interface is required to go on receiving and sending packets (for example, the VLAN
interface is used for remote login) after the IRF virtual device transits to recovery state, you need to
configure this VLAN interface and its corresponding Layer 2 Ethernet interface not to shut down when the
IRF virtual device transits to recovery state. However, if the VLAN interface is up in the IRF virtual device in
active state, IP collision occurs in your network.
If the IRF virtual device in active state fails due to exceptions (a member fails or link failure occurs, for
example) before the IRF link is recovered, as shown in Figure 12, enable IRF virtual device 2 (in recovery
state) at the CLI by executing the mad restore command. Then, the state of IRF virtual device 2 changes
from recovery to active without the need of rebooting and takes over IRF virtual device 1. Repair the IRF
links. When the IRF link failure is recovered, the two IRF virtual devices merge. More specifically, the
priorities of two masters from the two IRF virtual devices are compared, and the IRF virtual device whose
masters priority is higher can operate normally. Members (only one in this example) of the IRF virtual
device whose masters priority is lower reboot themselves, and the join the other IRF virtual device to
complete the IRF virtual device merge. After that, the original IRF virtual device recovers.
30
Figure 12 Recover the IRF virtual device when the IRF link failure occurs and the IRF virtual device in
active state fails
Remarks
system-view
mad restore
Required
Remote login: Configure an IP address for a Layer 3 Ethernet interface of a member switch and
make sure that the route is reachable, and then access the IRF virtual device remotely through Telnet,
Web, or SNMP.
When you log in to the IRF virtual device, actually you log in to the master. The master is the
configuration and control center of an IRF virtual device. When you configure the IRF virtual device on the
master, the IRF virtual device synchronizes the configurations to the subordinate switches.
31
display
quit
return
system-view
debugging
terminal debugging
terminal trapping
terminal logging
To return to the master console, use the quit command. At that time, the master console is reactivated and
can output logs.
To log in to the specified subordinate switch:
To do
Remarks
system-view
Required.
An IRF virtual device allows 15 concurrent VTY log-in users at most. And the maximum number of allowed
console log-in users is equal to the number of IRF members.
Remarks
32
To do
Remarks
Configuration considerations
To increase the number of access ports, additional devices are needed. In this example, Device B is
added.
To address the requirements for high availability, ease of management and maintenance, use IRF2
technology to create an IRF virtual device with Device A and Device B at the access layer.
To offset the risk of IRF virtual device partition, configure MAD to detect multi-active collisions. In this
example, LACP MAD is adopted because the number of access devices tends to be large. In
33
addition, for the purpose of LACP MAD, an intermediate device that supports extended LACPDUs
must be used.
Configuration procedure
This example assumes that the system names of Device A, Device B and Device C are DeviceA, DeviceB,
and DeviceC, respectively, before the IRF virtual device is formed.
1.
2.
Power off the two devices and connect IRF links and LACP MAD detection links according to Figure
13. Then power on the two devices.
# Create IRF port 2 on Device A, and bind it to the physical IRF port Ten-GigabitEthernet 1/0/25. Then
save the configuration.
<DeviceA> system-view
[DeviceA] interface ten-gigabitethernet 1/0/25
[DeviceA-Ten-GigabitEthernet1/0/25] shutdown
[DeviceA] irf-port 1/2
[DeviceA-irf-port1/2] port group interface ten-gigabitethernet 1/0/25
[DeviceA-irf-port1/2] quit
[DeviceA] interface ten-gigabitethernet 1/0/25
[DeviceA-Ten-GigabitEthernet1/0/25] undo shutdown
[DeviceA-Ten-GigabitEthernet1/0/25] save
# Create IRF port 1 on Device B, and bind it to the physical IRF port Ten-GigabitEthernet 2/0/26. Then
save the configuration.
<DeviceB> system-view
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] shutdown
[DeviceB] irf-port 2/1
[DeviceB-irf-port2/1] port group interface ten-gigabitethernet 2/0/26
[DeviceB-irf-port2/1] quit
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] undo shutdown
[DeviceB-Ten-GigabitEthernet2/0/26] save
3.
Master election is held between the two devices. Master election rules are followed. Device B
reboots automatically and joins the Device A as a subordinate switch, and the IRF virtual device is
formed. The system name on both devices is DevcieA.
34
4.
# Add ports GigabitEthernet 1/0/1 and GigabitEthernet 2/0/1 to the aggregation interface and they
are dedicated to the LACP MAD detection for Device A and Device B.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] port link-aggregation group 2
[DeviceA-GigabitEthernet1/0/1] quit
[DeviceA] interface gigabitethernet 2/0/1
[DeviceA-GigabitEthernet2/0/1] port link-aggregation group 2
5.
Acting as the intermediate device, Device C needs to support LACP to forward and process LACP
protocol packets, and help Device A and Device B implement MAD detection. An LACP-supported switch
is used here to save the cost.
# Create a dynamic aggregation interface.
<DeviceC> system-view
[DeviceC] interface bridge-aggregation 2
[DeviceC-Bridge-Aggregation2] link-aggregation mode dynamic
[DeviceC-Bridge-Aggregation2] quit
# Add ports GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to the aggregation interface and they
are used for the LACP MAD detection.
[DeviceC] interface gigabitethernet 1/0/1
[DeviceC-GigabitEthernet1/0/1] port link-aggregation group 2
[DeviceC-GigabitEthernet1/0/1] quit
[DeviceC] interface gigabitethernet 1/0/2
[DeviceC-GigabitEthernet1/0/2] port link-aggregation group 2
35
Figure 14 Network diagram for an IRF virtual device that uses BFD MAD detection
Configuration considerations
Device A is located at the distribution layer of the network. To improve the forwarding capability at
this layer, additional devices are needed. In this example, Device B is added.
To address the requirements for high availability, ease of management and maintenance, use IRF2
technology to create an IRF virtual device with Device A and Device B at the distribution layer. The
access devices are each connected to the distribution layer with dual links.
To offset the risk of IRF virtual device partition, configure MAD to detect multi-active collisions. In this
example, BFD MAD is adopted because the number of member devices is small.
Configuration procedure
This example assumes that the system names of Device A and Device B are DeviceA and DeviceB,
respectively, before the IRF virtual device is formed.
1.
2.
Power off the two devices and connect IRF links and BFD MAD detection links according to Figure
14. Then power on the two devices.
# Create IRF port 2 on Device A, and bind it to the physical IRF port Ten-GigabitEthernet 1/0/25. Then
save the configuration.
<DeviceA> system-view
36
# Create IRF port 1 on Device B, and bind it to the physical IRF port Ten-GigabitEthernet 2/0/26. Then
save the configuration.
<DeviceB> system-view
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] shutdown
[DeviceB] irf-port 2/1
[DeviceB-irf-port2/1] port group interface ten-gigabitethernet 2/0/26
[DeviceB-irf-port2/1] quit
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] undo shutdown
[DeviceB-Ten-GigabitEthernet2/0/26] save
3.
Master election is held between the two devices. As a result of the master election, Device B
automatically reboots to join the IRF virtual device as a subordinate switch. The system name on
both devices is DevcieA.
4.
# Create VLAN 3, and add port GigabitEthernet 1/0/1 on Device A (with the member ID of 1) and port
GigabitEthernet 2/0/1 on Device B (with the member ID of 2) to VLAN 3.
<DeviceA> system-view
[DeviceA] vlan 3
[DeviceA-vlan3] port gigabitethernet 1/0/1 gigabitethernet 2/0/1
[DeviceA-vlan3] quit
# Create VLAN-interface 3 and configure the MAD IP address for the interface.
[DeviceA] interface vlan-interface 3
[DeviceA-Vlan-interface3] mad bfd enable
[DeviceA-Vlan-interface3] mad ip address 192.168.2.1 24 member 1
[DeviceA-Vlan-interface3] mad ip address 192.168.2.2 24 member 2
[DeviceA-Vlan-interface3] quit
37
Configuration considerations
Device A is located at the distribution layer of the network. To improve the forwarding capability at
this layer, additional devices are needed. In this example, Device B is added.
To address the requirements for high availability, ease of management and maintenance, use IRF2
technology to create an IRF virtual device with Device A and Device B at the access layer. The IRF
virtual device is connected to Device C with dual links.
To offset the risk of IRF virtual device partition, configure MAD to detect multi-active collisions. In this
example, ARP MAD is adopted because the number of members in the IRF virtual device is small,
and the ARP MAD packets are transmitted over dual links connected to Device C. Enable MSTP on
the IRF virtual device and Device to prevent loops.
Configuration procedure
This example assumes that the system names of Device A, Device B and Device C are DeviceA, DeviceB,
and DeviceC, respectively, before the IRF virtual device is formed.
1.
38
2.
Power off the two devices and connect IRF links and ARP MAD detection links according to Figure
14. Then power on the two devices.
# Create IRF port 2 on Device A, and bind it to the physical IRF port Ten-GigabitEthernet 1/0/25. Then
save the configuration.
<DeviceA> system-view
[DeviceA] interface ten-gigabitethernet 1/0/25
[DeviceA-Ten-GigabitEthernet1/0/25] shutdown
[DeviceA] irf-port 1/2
[DeviceA-irf-port1/2] port group interface ten-gigabitethernet 1/0/25
[DeviceA-irf-port1/2] quit
[DeviceA] interface ten-gigabitethernet 1/0/25
[DeviceA-Ten-GigabitEthernet1/0/25] undo shutdown
[DeviceA-Ten-GigabitEthernet1/0/25] save
# Create IRF port 1 on Device B, and bind it to the physical IRF port Ten-GigabitEthernet 2/0/26. Then
save the configuration.
<DeviceB> system-view
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] shutdown
[DeviceB] irf-port 2/1
[DeviceB-irf-port2/1] port group interface ten-gigabitethernet 2/0/26
[DeviceB-irf-port2/1] quit
[DeviceB] interface ten-gigabitethernet 2/0/26
[DeviceB-Ten-GigabitEthernet2/0/26] undo shutdown
[DeviceB-Ten-GigabitEthernet2/0/26] save
3.
Master election is held between the two devices. As a result of the master election, Device B
automatically reboots to join the IRF virtual device as a subordinate switch. The system name on
both devices is DevcieA.
4.
# Create VLAN 3, and add port GigabitEthernet 1/0/1 (located on Device A) and port GigabitEthernet
2/0/1 (located on Device B) to VLAN 3.
[DeviceA] vlan 3
[DeviceA-vlan3] port gigabitethernet 1/0/1 gigabitethernet 2/0/1
[DeviceA-vlan3] quit
39
# Create VLAN-interface 3, assign it an IP address, and enable ARP MAD on the interface.
[DeviceA] interface vlan-interface 3
[DeviceA-Vlan-interface3] ip address 192.168.2.1 24
[DeviceA-Vlan-interface3] mad arp enable
5.
Configure Device C
# Create VLAN 3, and add port GigabitEthernet 1/0/1 and port GigabitEthernet 1/0/2 to VLAN 3 to
forward ARP MAD packets.
[DeviceC] vlan 3
[DeviceC-vlan3] port gigabitethernet 1/0/1 gigabitethernet 1/0/2
[DeviceC-vlan3] quit
40
Error messages
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
For related documentation, navigate to the Networking section, and select a networking category.
For a complete list of acronyms and their definitions, see HP A-Series Acronyms.
Websites
HP.com http://www.hp.com
HP Networking http://www.hp.com/go/networking
HP manuals http://www.hp.com/support/manuals
41
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention
Description
Boldface
Bold text represents commands and keywords that you enter literally as shown.
Italic
Italic text represents arguments that you replace with actual values.
[]
Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
[ x | y | ... ] *
&<1-n>
The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
GUI conventions
Convention
Description
Boldface
Window names, button names, field names, and menu items are in bold text. For
example, the New User window appears; click OK.
>
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Convention
Description
Symbols
WARNING
An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION
An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT
NOTE
TIP
42
43
Index
IRF
application scenario, 2
basic concepts, 3
benefits, 1
configuration, 1
establishment of IRF virtual device, 4
maintenance of an IRF virtual device, 4
operation of IRF virtual device, 4
overview, 1
topologies, 2
virtual device task list, 12
IRF configuration, 1
IRF domain, 13
IRF link, 21
IRF member ID, 15
IRF member switch roles, 3
IRF merge, 4
IRF multi-active detection, 11
IRF overview, 1
IRF partition, 3
IRF ports, 3, 15
IRF topologies, 2
IRF virtual device, 13, 30
displaying and maintaining, 31
examples, 32
IRF virtual device maintenance, 9
IRF virtual device management, 9
IRF virtual device task list, 12
IRF virtual device topology maintenance, 11
LACP MAD, 22
LACP MAD detection-enabled IRF example, 32
load sharing criteria for IRF links, 17
MAD detection, 21
maintenance of an IRF virtual device, 4
manually recovering an IRF virtual device, 29
manuals, 40
master election, 9
master switch, 30
member ID, 10
member priority, 4
member switch description, 17
member switch priority, 17
network requirements, 32, 35, 37
operation of IRF virtual device, 4
physical IRF port, 3
subscription service, 40
support and other resources, 40
symbols, 41
topology collection, 9
websites, 41
45