HP FlexFabric 12500 and 12500E Routing Switch Series Virtual Technologies Configuration Guide Part number: 5998-4860 Software version: 12500-CMW710-R7328 Document version: 6PW100-20140128...
Page 2
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Page 4
MDC configuration examples ······································································································································· 67 MDC configuration example in standalone mode ····························································································· 67 MDC configuration example in IRF mode ·········································································································· 72 Support and other resources ····································································································································· 79 Contacting HP ································································································································································ 79 Subscription service ·············································································································································· 79 Related information ························································································································································ 79 Documents ······························································································································································ 79 Websites ·································································································································································...
IRF overview The HP Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple devices to provide data center class availability and scalability. IRF virtualization technology offers processing power, interaction, unified management, and uninterrupted maintenance of multiple devices.
Figure 1 IRF application scenario Network topologies An IRF fabric can use a daisy-chain or ring topology. IRF does not support the full mesh topology. For information about connecting IRF member devices, see "Connecting physical IRF ports." Basic concepts This section uses Figure 2 to describe the basic concepts that you might encounter when you work with IRF.
Page 7
Figure 2 Two-chassis IRF fabric implementation schematic diagram In this figure, Device A and Device B form a two-chassis IRF fabric. The fabric has four MPUs (one active and three standbys), and two times the number of interface cards that a single device provides. The IRF fabric manages the physical and software resources of Device A and Device B in a centralized manner.
When devices form an IRF fabric, they elect a master to manage the IRF fabric, and all other devices back up the master. When the master device fails, the other devices elect a new master automatically. For more information about master election, see "Master election."...
For two neighboring devices, their IRF physical links must be bound to IRF-port 1 on one device and to IRF-port 2 on the other. IRF physical port IRF physical ports connect IRF member devices and must be bound to an IRF port. They forward the IRF protocol packets between IRF member devices and the data packets that must travel across IRF member devices.
To avoid a card removal causing an IRF split, bind physical ports on different cards to an IRF port. Figure 5 IRF split IRF merge IRF merge occurs when two split IRF fabrics reunite or when two independent IRF fabrics are combined, as shown in Figure Figure 6 IRF merge...
Allows the IRF fabric that has the lowest numbered master to forward traffic, and all other fabrics to the Recovery (inactive) state. To avoid network flapping caused by IRF split, HP recommends that you configure the lowest numbered member as the master in a two-chassis IRF fabric.
Figure 7. In addition, the intermediate device must be an HP device that supports extended LACP for MAD. The IRF member devices send extended LACPDUs with TLVs that convey the domain ID and the active ID of the IRF fabric. The intermediate device transparently forwards the extended LACPDUs received from one member device to all the other member devices: •...
Figure 7 LACP MAD application scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation LACP-enabled dynamic link aggregation IRF link Master Subordinate Internet Common traffic path LACP MAD traffic path BFD MAD BFD MAD can work with or without intermediate devices. Figure 8 shows a typical BFD MAD application scenario.
Figure 8 BFD MAD application scenario Customer premise network Device Link aggregation BFD MAD link VLAN 2 VLAN 2 192.168.1.2/24 192.168.1.3/24 IRF link Subordinate Master Internet ARP MAD ARP MAD detects multi-active collisions by using extended ARP packets that convey the IRF domain ID and the active ID.
Figure 9 ARP MAD application scenario Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID: If the domain IDs are different, the extended ARP packet is from a different IRF fabric. The device •...
Page 17
Figure 10 ND MAD application scenario Each IRF member device compares the domain ID and the active ID in incoming NS packets with its domain ID and active ID: If the domain IDs are different, the NS packet is from a different IRF fabric. The device does not •...
To use enhanced IRF, make sure each IRF member has two MPUs. Selecting IRF physical ports You must use Layer 2 Ethernet fiber or copper ports for IRF connection. HP recommends using 10-GE fiber ports for high performance. IRF physical port binding restrictions When you bind IRF physical ports to IRF ports, follow these restrictions and guidelines: Link aggregation member ports cannot be bound to an IRF port.
For link redundancy and load sharing, bind up to 12 physical ports to one IRF port. Physical ports bound to an IRF port can be located on different cards. • HP recommends using multicard IRF links to avoid a card removal causing an IRF split. • Multichassis link aggregation For high availability, connect a downstream device to each IRF member device, and assign the links to one link aggregation group.
To exclude a port from the shutdown action that is executed when an IRF fabric transits 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 instead of the undo shutdown command.
Setup and configuration task list HP recommends the following IRF fabric setup and configuration procedure: Setup and configuration procedure Remarks (Required.) Planning the IRF fabric setup (Required.) Preconfiguring IRF member devices in standalone mode: Perform this task on each member...
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. Preconfiguring IRF member devices in standalone mode Perform the tasks in this section on every IRF member device. These settings take effect on each member device after their operating mode changes to IRF.
Bind a physical IRF port to port group [ mdc mdc-id ] interface physical ports. the IRF port. interface-type interface-number HP recommends not creating MDCs or binding ports on non-default MDCs to an IRF port when the device is operating in standalone mode.
Step Command Remarks (Optional.) Verify the display irf configuration binding result. Enabling enhanced IRF in standalone mode Enhanced IRF allows you to create a three- or four-chassis IRF fabric. When you configure enhanced IRF on a standalone device, follow these restrictions and guidelines: •...
Connecting physical IRF ports When you connect two neighboring IRF members, connect the physical ports of IRF-port 1 on one member to the physical ports of IRF-port 2 on the other, as shown in Figure 1 If copper Ethernet ports are used, use straight-through or crossover copper Ethernet cables to connect them.
Figure 13 Daisy-chain topology with a relay Setting the operating mode to IRF mode By default, the device is operating in standalone mode. To assign the device to an IRF fabric, you must change its operating mode to IRF mode. Before changing to IRF mode, use the display irf configuration command to verify that a member ID has been assigned to the device.
Accessing the IRF fabric The IRF fabric appears as one device after it is formed. You configure and manage all IRF members at the CLI of the global active MPU. All settings you made are propagated automatically to the IRF members. When you log in to an IRF fabric, you are placed at the CLI of the global active MPU, regardless of at which member device you are logged in.
Step Command Remarks Enter system view. system-view Change the member ID of a irf member member-id renumber member device. new-member-id Save the running save [ safely ] [ force ] configuration. The chassis-number must be the same as the member-id specified Reboot the member device.
Page 29
Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-5> To shut down a range of physical IRF ports, enter interface range Method 2: Enter Ethernet interface view view.
Step Command Remarks Activating IRF port configurations can cause IRF merge and reboot. To avoid Save the running save data loss, save the running configuration. configuration to the startup configuration file before you perform the operation. After this step is performed, the state of the IRF port changes to UP, the member devices automatically elect a master,...
Step Command Remarks Enter system view. system-view By default, enhanced IRF is disabled. After enhanced IRF is enabled, you cannot create Layer 3 Enable enhanced IRF. irf mode enhanced Ethernet interfaces or subinterfaces or Layer 3 aggregate interfaces or subinterfaces. Save the configuration.
Configuring IRF bridge MAC persistence By default, an IRF fabric uses the bridge MAC address of the master device as its bridge MAC address. Layer 2 protocols, such as LACP, use this bridge MAC address to identify the IRF fabric. On a switched LAN, the bridge MAC address must be unique.
Enabling software auto-update for system software image synchronization IMPORTANT: To ensure a successful software auto-update in a multi-user environment, prevent users from rebooting MPUs or member devices during the software auto-update process. You can configure the information Network Management and center to output the software auto-update status to configuration terminals (see Monitoring Configuration Guide To synchronize software from the active MPU to the standby MPU in standalone mode, use the undo...
Application scenario mechanism Link aggregation is used between the IRF fabric and its upstream or • Detection speed is fast. Requires an intermediate HP downstream device. • device that supports LACP MAD Requires no MAD-dedicated For information about extended LACP for MAD.
Page 35
Configuring LACP MAD When you use LACP MAD, follow these guidelines: The intermediate device must be an HP device that support extended LACP for MAD. • If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for •...
Page 36
Step Command Remarks The default IRF domain ID is 0. Assign a domain ID to the IRF This command can be executed irf domain domain-id fabric. only on the default MDC (Admin). • Enter Layer 2 aggregate interface view: interface bridge-aggregation Use either command.
Page 37
Category Restrictions and guidelines • Do not enable BFD MAD on VLAN-interface 1. • If you are using an intermediate device, assign the ports of BFD MAD links to the BFD MAD VLAN on the device. • The IRF fabrics in a network must use different BFD MAD VLANs. BFD MAD VLAN •...
Page 38
Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type To assign a range of ports to the interface-number ] } &<1-5> BFD MAD VLAN, enter interface Method 2: range view. Enter Ethernet interface view interface range name name or interface range view.
Page 39
Run the spanning tree feature between the IRF fabric and the intermediate device. Enable the IRF fabric to change its bridge MAC address as soon as the master leaves. Create an ARP MAD VLAN and assign the ports on the ARP MAD links to the VLAN. If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection.
Page 40
Step Command Remarks Assign the interface an IP ip address ip-address { mask | By default, no IP address is address. mask-length } assigned to any VLAN interface. By default, ARP MAD is disabled. When you use the mad arp enable command, the system Enable ARP MAD.
Page 41
Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type To assign a range of ports to the interface-number ] } &<1-5> ND MAD VLAN, enter interface Method 2: range view. Enter Ethernet interface view interface range name name or interface range view.
Page 42
Step Command Remarks Enter system view. system-view By default, all network ports on a Configure a port to not shut mad exclude interface interface-type Recovery-state IRF fabric are shut down when the IRF fabric interface-number down, except for the IRF physical transits to the Recovery state.
MPU is damaged. This section describes a fast approach to restoring IRF configuration for one-MPU member devices. NOTE: HP recommends performing fast IRF configuration restoration in IRF mode. The recovery procedure differs depends on whether a two-member device is available. This section assumes that the failed member device is Device A.
Step Command • In IRF mode: irf chassis chassis-number slot slot-number member Change Device B's member ID on the standby member-id MPU to be the same as that of Device A. • In standalone mode: irf slot slot-number member member-id Remove the damaged MPU from Device A, and insert Device B's standby MPU into Device A.
As shown in Figure 16, set up a two-chassis IRF fabric at the access layer of the enterprise network. Configure LACP MAD on the multichassis aggregation to Device C, an HP device that supports extended LACP. Figure 16 Network diagram...
Page 46
[Sysname-irf-port2] quit [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit # Save the configuration. [Sysname] quit <Sysname> save # Enable IRF mode. <Sysname> system-view [Sysname] chassis convert mode irf The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup.
Saving the converted configuration file succeeded. Now rebooting, please wait... Device B and Device A form an IRF fabric after Device B reboots. Configure LACP MAD: # Assign domain ID 1 to the IRF fabric. <Sysname> system-view [Sysname] irf domain 1 # Create a dynamic aggregate interface and enable LACP MAD.
Page 48
Configure BFD MAD in the IRF fabric and set up BFD MAD links between the member devices. Disable the spanning tree feature on the ports used for BFD MAD, because the two features conflict with each other. Assign the highest member priority to Device A so it can be elected the master. Figure 17 Network diagram Configuration procedure Configure Device A:...
Page 49
<Sysname> system-view [Sysname] chassis convert mode irf The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Please wait...
[Sysname] vlan 3 [Sysname-vlan3] port gigabitethernet 1/4/0/1 gigabitethernet 2/4/0/1 [Sysname-vlan3] quit # Create VLAN-interface 3, and configure a MAD IP address for each member device on the VLAN interface. [Sysname] interface vlan-interface 3 [Sysname-Vlan-interface3] mad bfd enable [Sysname-Vlan-interface3] mad ip address 192.168.2.1 24 member 1 [Sysname-Vlan-interface3] mad ip address 192.168.2.2 24 member 2 [Sysname-Vlan-interface3] quit # Disable the spanning tree feature on GigabitEthernet 1/4/0/1 and GigabitEthernet 2/4/0/1.
Page 51
<Sysname> system-view [Sysname] irf member 1 Info: Member ID change will take effect after the member reboots and operates in IRF mode. [Sysname] irf-port 2 [Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port2] quit [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit # Save the configuration.
Page 52
The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Please wait...
ND MAD-enabled IRF configuration example for a two-chassis IRF fabric Network requirements As shown in Figure 19, set up a two-chassis IRF fabric at the distribution layer of the enterprise network. Configure ND MAD for the IRF fabric and use Device C as an intermediate device. Device C can come from any vendor.
Page 54
The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Please wait...
[Sysname] undo irf mac-address persistent # Set the domain ID of the IRF fabric to 1. [Sysname] irf domain 1 Configure ND MAD: # Create VLAN 3, and add GigabitEthernet 1/4/0/2 and GigabitEthernet 2/4/0/2 to VLAN 3. [Sysname] vlan 3 [Sysname-vlan3] port gigabitethernet 1/4/0/2 gigabitethernet 2/4/0/2 [Sysname-vlan3] quit # Create VLAN-interface 3, assign it an IP address, and enable ND MAD on the interface.
Page 56
Figure 20 Network diagram Configuration procedure Identify the master. <IRF> display irf MemberID Slot Role Priority CPU-Mac Description Master 00e0-fc0a-15e0 DeviceA Standby 1 00e0-fc0f-8c02 DeviceA Standby 1 00e0-fc0f-15e1 DeviceB Standby 1 00e0-fc0f-15e2 DeviceB -------------------------------------------------- * indicates the device is the master. + indicates the device through which the user logs in.
Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file. Please wait........The current configuration is saved to the active main board successfully. Configuration is saved to device successfully. Change the operating mode of Device A to standalone.
Page 58
Figure 21 Network diagram before IRF deployment Figure 22 Network diagram after IRF deployment Configuration procedure IMPORTANT: Between two neighboring IRF members, IRF links must be bound to IRF-port 1 on one member and to IRF-port 2 on the other.
Page 59
Configure Device A: # Assign member ID 1 and priority 12 to Device A. <Sysname> system-view [Sysname] irf member 1 [Sysname] irf priority 12 # Bind Ten-GigabitEthernet 3/0/2 and Ten-GigabitEthernet 3/0/1 to IRF-port 1 and IRF-port 2, respectively. [Sysname] irf-port 1 [Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/2 [Sysname-irf-port1] quit [Sysname] interface ten-gigabitethernet 3/0/2...
Page 60
[Sysname-Ten-GigabitEthernet3/0/1] quit [Sysname] irf-port 2 [Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/2 [Sysname-irf-port2] quit [Sysname] interface ten-gigabitethernet 3/0/2 [Sysname-Ten-GigabitEthernet3/0/2] undo shutdown [Sysname-Ten-GigabitEthernet3/0/2] quit # Enable enhanced IRF. [Sysname] irf mode enhanced # Save the configuration. [Sysname] save # Connect Device B to Device A, as shown in Figure 22.
Page 61
# Save the configuration. [Sysname] save # Connect Device C to Device B, as shown in Figure 22. Log in to Device C. # Enable IRF mode. <Sysname> system-view [Sysname] chassis convert mode irf The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup.
Page 62
The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Please wait...
Configuring MDCs Overview The Multitenant Device Context (MDC) technology can partition a physical device or an IRF fabric into multiple logical switches called "MDCs." Each MDC uses its own hardware and software resources, runs independently of other MDCs, and provides services for its own customer. Creating, starting, rebooting, or deleting an MDC does not affect any other MDC.
Figure 24 Network diagram Internet Internet Gateway 1 Gateway 3 Device Equals Device A Device B Device C Gateway 2 LAN 1 LAN 3 LAN 1 LAN 3 LAN 2 LAN 2 Default MDC and non-default MDCs A device supporting MDCs is an MDC itself, and it is called the "default MDC" (for example, Device Figure 24).
The physical IRF ports of an IRF link must belong to the same MDC. Otherwise, the link cannot be • set up. See Figure Figure 25 The physical IRF ports of an IRF link must belong to the same MDC Chassis 1 Chassis 2 Chassis 1...
Tasks at a glance (Required.) Accessing an MDC Although you can assign hardware resources to MDCs before or after you start the MDCs, HP recommends that you assign resources to MDCs before starting the MDCs. Creating an MDC You can create MDCs only on MPUs with a memory space that is equal to or greater than 4 GB.
Table 3 MDC support on LPUs Maximum number of MDCs LPUs with a 512-MB memory 1, including the default MDC. LPUs with a 1-GB memory 2, including the default MDC. LST1XP48LFD1, LST1XLP16RFD1 4, including the default MDC. LPUs with a 4-GB memory Others 2, including the default MDC.
interfaces are grouped by viewing the output of the allocate interface or undo allocate interface command: If the interfaces you specified for the command belong to the same group or groups and you have • specified all interfaces in the group or groups for the command, the command outputs no error information.
Step Command Remarks Enter system view. system-view Enter MDC view. mdc mdc-name [ id mdc-id ] By default, the default MDC has a CPU weight Specify a CPU of 10 (unchangeable) on each MPU and each limit-resource cpu weight weight for the LPU, and each non-default MDC has a CPU weight-value MDC.
Step Command Remarks Enter system view. system-view Enter MDC view. mdc mdc-name [ id mdc-id ] • In standalone mode: By default, all MDCs share limit-resource memory slot slot-number ratio Specify a memory the memory space in the limit-ratio space percentage system, and the memory •...
Task Command Display MDCs and their status. display mdc [ name mdc-name ] Display the interfaces of MDCs. display mdc [ name mdc-name ] interface Display the CPU, disk space, and memory space display mdc [ name mdc-name ] resource [ cpu | disk | usage of MDCs.
Figure 27 Network diagram Switch LPU 2 (in slot 2) LPU 3 (in slot 3) LPU 4 (in slot 4) Switch MDC A MDC B MDC C LPU 2 LPU 3 LPU 4 Company A Company B Company C Configuration considerations To meet the network availability and security requirements of Company B and Company C and the •...
Page 73
# Create MDCA. <Device> system-view [Device] mdc MDCA It will take some time to create MDC… This MDC was created successfully. # Authorize MDCA to use the LPU in slot 2. [Device-mdc-2-MDCA] location slot 2 # Assign interfaces GigabitEthernet 2/0/1 through GigabitEthernet 2/0/48 to MDCA. [Device-mdc-2-MDCA] allocate interface GigabitEthernet 2/0/1 to GigabitEthernet 2/0/48 The configurations of the interfaces will be lost.
Page 74
This MDC was created successfully. # Authorize MDCB to use the LPU in slot 3. [Device-mdc-3-MDCB] location slot 3 # Assign interfaces GigabitEthernet 3/0/1 through GigabitEthernet 3/0/48 to MDCB. [Device-mdc-3-MDCB] allocate interface GigabitEthernet 3/0/1 to GigabitEthernet 3/0/48 The configurations of the interfaces will be lost. Continue? [Y/N]:y # Start MDCB.
Page 75
The configurations of the interfaces will be lost. Continue? [Y/N]:y # Set the CPU weight of MDCC to 5. [Device-mdc-4-MDCC] limit-resource cpu weight 5 # Start MDCC. [Device-mdc-4-MDCC] mdc start It will take some time to start MDC... This MDC was started successfully. [Device-mdc-4-MDCC] quit # Log in to MDCC from the default MDC.
* no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <MDCA> display current-configuration version 7.1.034, Release 7128 sysname MDCA telnet server enable vlan 1 stp global enable interface NULL0 interface GigabitEthernet2/0/1 port link-mode bridge shutdown … interface M-Ethernet0/0/0 ip address 192.168.1.251 255.255.255.0 scheduler logfile size 16 user-interface vty 0 15 authentication-mode none...
Page 77
Figure 28 Network diagram Chassis 2 Chassis 1 IRF link GE 1/2/0/1 GE 2/4/0/1 GE 1/3/0/1 GE 2/5/0/1 Master Subordinate Chassis 2 Chassis 1 IRF link MDC A MDC A Company A of MDC A GE 1/2/0/1 GE 2/4/0/1 IRF link MDC B MDC B of MDC B...
Page 78
Figure 29 Correct configuration order Chassis 1 Chassis 1 Chassis 2 Chassis 1 Chassis 2 Chassis 2 × ① ② ③ MDC A MDC A MDC A MDC A Chassis 1 Chassis 2 Chassis 1 Chassis 2 ④ MDC A MDC A MDC A MDC A...
Page 79
<IRF> system-view [IRF] mdc MDCA It will take some time to create MDC... This MDC was created successfully. # Authorize MDCA to use the LPU in the master's slot 2 and the LPU in the subordinate member's slot 4. [IRF-mdc-2-MDCA] location chassis 1 slot 2 [IRF-mdc-2-MDCA] location chassis 2 slot 4 # Assign all interfaces on the LPUs to MDCA.
Page 80
# Assign an IP address to the virtual management Ethernet interface and enable the Telnet service on the interface to allow remote management of MDC A. [MDCA]interface M-Ethernet 1/0/0/0 [MDCA-M-Ethernet1/0/0/0]ip address 192.168.1.251 24 [MDCA-M-Ethernet1/0/0/0]quit [MDCA] telnet server enable [MDCA] user-interface vty 0 15 [MDCA-ui-vty0-15] authentication-mode none [MDCA-ui-vty0-15] user-role mdc-admin # Return to the default MDC.
Page 81
****************************************************************************** <MDCB> system-view [MDCB] interface GigabitEthernet 1/3/0/1 [MDCB-GigabitEthernet1/3/0/1] undo shutdown [MDCB-GigabitEthernet1/3/0/1] quit [MDCB] interface GigabitEthernet 2/5/0/1 [MDCB-GigabitEthernet2/5/0/1] undo shutdown [MDCB-GigabitEthernet2/5/0/1] quit # Change the device name to MDCB for easy identification of the MDC. [IRF] sysname MDCB # Assign an IP address to the virtual management Ethernet interface and enable the Telnet service on the interface to allow remote management of MDC B.
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. •...
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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 85
Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.