Page 1: Configuration Guide
HP FlexFabric 5700 Switch Series FCoE Configuration Guide Part number: 5998-6676 Software version: Release 2416 Document version: 6W100-20150130...
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 3: Table Of Contents
Contents FCoE overview ····························································································································································· 1 Storage area network ······················································································································································· 1 FC SAN ·············································································································································································· 1 FC protocol ········································································································································································ 2 Basic concepts ·························································································································································· 2 Communication flow ················································································································································ 4 VSAN ········································································································································································· 4 FC zone ····································································································································································· 5 ...
Page 4 Building a fabric ························································································································································· 32 Overview ········································································································································································· 32 Principal switch selection ······································································································································ 32 Domain ID assignment ·········································································································································· 33 FC address assignment ········································································································································· 34 Fabric building configuration task list ·························································································································· 34 Building a fabric statically ···································································································································· 35 ...
Page 5 Displaying and maintaining FC routing and forwarding ·························································································· 60 FC routing configuration examples ······························································································································ 61 Static FC routing configuration example ············································································································ 61 FSPF configuration example ································································································································· 66 Configuring FC zones ················································································································································ 70 Overview ········································································································································································· 70 ...
Page 6 Network requirements ··········································································································································· 97 Configuration procedure ······································································································································ 97 Verifying the configuration ································································································································· 100 Configuring FIP snooping ······································································································································· 102 Overview ······································································································································································· 102 FIP snooping network diagram ·························································································································· 102 How FIP snooping works ···································································································································· 103 FIP snooping configuration task list ····························································································································...
Page 7 Appendix A Fabric address assignment ···················································································································· 159 Appendix B Well-known fabric addresses ················································································································ 159 Support and other resources ·································································································································· 161 Contacting HP ······························································································································································ 161 Subscription service ············································································································································ 161 Related information ······················································································································································ 161 Documents ···························································································································································· 161 ...
Page 8: Fcoe Overview
FCoE overview Fibre Channel (FC) is a data transmission protocol used in a storage area network (SAN). Fibre Channel over Ethernet (FCoE) transports FC over Ethernet. The following sections describe FCoE. Storage area network A SAN is any high-performance network whose primary purpose is to enable storage devices to communicate with computer systems and with each other.
Page 9: Fc Protocol
Figure 1 FC SAN networking 1) Point-to-point 2) Arbitrated loop connection Server Disk Server Disk Disk Disk Server 3) Switched fabric Disk Server FC switch Fabric NOTE: An FC SAN refers to a network that includes FC switches and nodes. •...
Page 10 Figure 2 shows the structure of an FC address. The FC address is 24 bits long and contains the following 8-bit fields: Domain_ID—A domain represents a switch and all N_Ports connected to the switch. For more • information about N_Ports, see "Port modes."...
Page 11: Communication Flow
If both ends are G_Ports, they both work as E_Ports. If the peer is an F_Port, the negotiation fails. NP_Port—Connects to an F_Port on another FC switch. For more information about NP_Port, see • "Configuring NPV." E_Ports connect FC switches to form a fabric, and F_Ports connect the nodes to FC switches in the fabric. Communication flow FC switches provide data transmission services.
Page 12: Fc Zone
of the network and offers more effective services for users. For more information about VSANs, see "Configuring VSANs." FC zone The VSAN technique divides one physical SAN into multiple logical SANs. A VSAN, however, cannot perform access control over the servers and disk devices (or the N_Ports) connected to a fabric. N_Ports in the same VSAN can access one another only if these N_Ports register name services.
Page 13: Basic Concepts
As shown in Figure • In the traditional network, the server is connected to the LAN through an Ethernet interface and to the SAN through an FC interface. In the FCoE network, the server is connected to the FCoE-capable FCF switch. Then, the FCF switch •...
Page 14: How Fcoe Works
FCoE frames To transmit an FC frame over Ethernet, FCoE encapsulates the FC frame in an FCoE frame by adding an Ethernet frame header to the FC frame. An FCoE frame uses Ethernet II encapsulation, which has the following fields in the Ethernet header: EtherType 0x8906.
Page 15 A VN interface of an ENode. A VFC interface of another FCF switch. After the virtual link is established, the FCF switch encapsulates the FC frame in an FCoE frame and sends it out. After receiving the FCoE frame, the FCF switch removes its Ethernet header to send the original FC frame to the upper layer for processing.
Page 16: Fcoe Modes
If they match, the switch replies with a solicited Discovery Advertisement, whose fcf priority − field carries the FCF priority of the VFC interface. If they do not match, the switch discards the Discovery Solicitation. − The FCF switch periodically sends unsolicited Discovery Advertisements, whose fcf priority field carries the FCF priority of the system.
Page 17: Fcf Mode
FCF mode An FCF switch encapsulates FC frames in Ethernet frames and uses FCoE virtual links to simulate physical FC links. In this way, an FCF switch provides standard FC switching capabilities and features on a lossless Ethernet network. Figure 10 FCF network diagram In an FCoE environment as shown in Figure 10, an FCF switch can perform the following operations:...
Page 18: Transit Mode
As shown in Figure 1 1, the NPV switch resides between nodes and the core switch on the edge of the fabric. The core switch is a switch operating in FCF mode. The NPV switch is connected to the nodes through its F_Ports and to the core switch through its NP_Port.
Page 19: Protocols And Standards
Figure 14 Network diagram for NPV and Transit switches The primary responsibilities of Transit switches are filtering and forwarding FCoE protocol packets. They can recognize and control FCoE frames as compared to standard Ethernet switches. However, they do not provide FCoE traffic processing capabilities as complex as FCF switches or NPV switches. Protocols and standards •...
Page 20: Fcoe Configuration Guidelines
FCoE configuration guidelines Configuring the switch to operate in advanced mode or expert mode The switch supports FCoE only when it is operating in advanced mode or expert mode. For more information about system operating modes, see Fundamentals Configuration Guide. The switch supports FCoE over S-channel only when it is operating in expert mode.
Page 21 Table 1 FCoE features supported in different FCoE modes FC and FCoE feature FCF mode NPV mode Transit mode Configuring VFC Supported. Supported. Not supported. interfaces Enabling FCoE Supported. Supported. Not supported. Configuring VSANs Supported. Supported. Not supported. Only the Setting fabric timers Building a fabric Supported.
Page 22: Configuring Vfc Interfaces
Configuring VFC interfaces A VFC interface can connect to an ENode, or a switch operating in FCF, NPV, or Transit mode. A VFC interface can operate in E mode, F mode (the default), or NP mode. A VFC interface is a virtual logical interface. It implements the functionality of an FC interface. To make a VFC interface work, bind it to a physical Ethernet interface.
Page 23: Displaying And Maintaining Vfc Interfaces
Step Command Remarks By default, the expected bandwidth (in kbps) is the interface baud rate (Optional.) Set the expected divided by 1000. bandwidth for the VFC bandwidth bandwidth-value interface. The default baud rate of a VFC interface is 10 Gbps. (Optional.) Restore the default settings for the VFC default...
Page 24: Enabling Fcoe
Enabling FCoE To make the FCoE features operate correctly, you must enable FCoE. FCoE enabling configuration task list Tasks at a glance (Required.) Enabling FCoE for a VLAN and mapping the VLAN to a VSAN Setting an FC-MAP value Setting an FKA advertisement interval value Setting the FCF priority Enabling FCoE for a VLAN and mapping the VLAN to a VSAN...
Page 25: Setting An Fc-Map Value
Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id By default, FCoE is disabled for a VLAN. Enable FCoE for the VLAN and fcoe enable [ vsan Make sure the VSAN to be mapped has map the VLAN to a VSAN. vsan-id ] been created.
Page 26 Table 2 Recommended values for different application scenarios Recommended Application scenarios Remarks value According to FC-BB-5, the upper limit of the FKA advertisement interval value is 90 seconds. In this scenario, an FCF switch or NPV switch operating in standalone mode or in IRF mode but without subordinate switches will experience FCoE traffic disruption during an ISSU reboot for the following reasons: •...
Page 27: Setting The Fcf Priority
Setting the FCF priority The FCF priority includes the system FCF priority and the VFC interface FCF priority. • System FCF priority—The system FCF priority is used in the fcf priority field in a solicited Discovery Advertisement. VFC interface FCF priority—The VFC interface FCF priority is used in the fcf priority field in an •...
Page 28: Fcoe Enabling Configuration Example
FCoE enabling configuration example Network requirements As shown in Figure 15, use FCoE in a data center combining a LAN and a SAN to reduce the number of devices, network adapters, and cables. Figure 15 Network diagram Configuration procedure Configure Switch A as follows: Enable the advanced mode: # Configure the switch to operate in advanced mode.
Page 29 Now rebooting, please wait... Configure VLANs and interfaces: # Create VLAN 10 and VLAN 20, which are intended to transmit Ethernet data traffic and storage data traffic, respectively. <SwitchA> system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure interface Ten-GigabitEthernet 1/0/1 as a hybrid port.
Page 30 [SwitchA-classifier-DCBX] if-match acl 4000 [SwitchA-classifier-DCBX] quit # Create a behavior named DCBX3. [SwitchA] traffic behavior DCBX # Configure the behavior to mark packets with 802.1p priority value 3. [SwitchA-behavior-DCBX] remark dot1p 3 [SwitchA-behavior-DCBX] quit # Create a QoS policy named DCBX. [SwitchA] qos policy DCBX # Associate class DCBX with traffic behavior DCBX in the QoS policy, and specify that the association apply to DCBX.
Page 31 [SwitchA-maptbl-dot1p-lp] import 5 export 0 [SwitchA-maptbl-dot1p-lp] import 6 export 0 [SwitchA-maptbl-dot1p-lp] import 7 export 0 [SwitchA-maptbl-dot1p-lp] quit # Enable byte-count WRR on interface Ten-GigabitEthernet 1/0/1. [SwitchA] interface ten-gigabitethernet 1/0/1 [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr byte-count # Configure WRR on interface Ten-GigabitEthernet 1/0/1: Assign 50% of the interface bandwidth to the FCoE traffic (traffic assigned to queue 1).
Page 32 [SwitchA-vlan20] fcoe enable vsan 10...
Page 33: Configuring Vsans
Configuring VSANs The virtual storage area network (VSAN) technology breaks a physical SAN into multiple VSANs, and provides more secure, reliable, and flexible services. Devices in a VSAN cannot get information about any other VSAN and devices in any other VSAN. Each VSAN performs the following operations independently: Selecting a principal switch.
Page 34: Creating A Vsan
list of the VFC interface. An FCoE frame transmitted from a VFC interface can use the VLAN ID in VLAN_Header to identify the VLAN to which it belongs. Creating a VSAN By default, only the default VSAN (VSAN 1) exists. You cannot create or delete VSAN 1. You can create VSANs 2 to 3839.
Page 35: Vsan Configuration Examples
VSAN configuration examples Network requirements As shown in Figure 16, configure the SAN to meet the following requirements: Server A can read and write only the data of Disk A and Disk B. • Server B can read and write only the data of Disk C. •...
Page 36 [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective. # Save the configuration. [SwitchA] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file.
Page 37: Verifying The Configuration
# Assign VFC 2 to VSAN 20 as a trunk port. [SwitchA-Vfc2] port trunk vsan 20 [SwitchA-Vfc2] quit # Configure Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 20. [SwitchA] interface ten-gigabitethernet 1/0/2 [SwitchA-Ten-GigabitEthernet1/0/1] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/1] port trunk permit vlan 20 [SwitchA-Ten-GigabitEthernet1/0/1] quit # Create interface VFC 4.
Page 38 VSAN 20: Access Ports: Trunk Ports: Vfc2 Vfc4 Verify the configuration on Switch B in the same way as you verify the configuration on Switch A.
Page 39: Building A Fabric
Building a fabric Overview A fabric transmits data for servers and disk devices. When building a fabric, you must perform the following tasks: • Assign a domain ID to each FCF switch in the fabric. Assign an FC address to each node connected to the fabric. •...
Page 40: Domain Id Assignment
Before the PSST expires, the switches exchange packets carrying the principal switch information to select a principal switch. On receiving such a packet, a switch compares the priority and WWN of the principal switch carried in the packet against those locally recorded. The switch replaces the locally-recorded principal switch information with the principal switch information recorded in the packet.
Page 41: Fc Address Assignment
The N_Port itself does not have a desired FC address. The desired FC address is unavailable. Fabric building configuration task list HP recommends that you use the dynamic mode for large networks to facilitate centralized management and use the static mode for small networks to avoid network flapping.
Page 42: Building A Fabric Statically
Building a fabric statically Tasks at a glance Remarks To statically build a fabric, you must (Required.) Enabling or disabling the fabric configuration feature disable the fabric configuration feature. When statically building a fabric, you must manually configure the fabric name, and (Required.) Setting a fabric name make sure all switches in the fabric are...
Page 43: Enabling Or Disabling The Fabric Configuration Feature
Enabling or disabling the fabric configuration feature After you enable the fabric configuration feature on FCF switches, the switches exchange messages to select the principal switch. Then the principal switch dynamically assigns domain IDs to all switches in the fabric. After you disable the fabric configuration feature on FCF switches, the switches will not select a principal switch and cannot obtain domain IDs dynamically.
Page 44: Configuring An Allowed Domain Id List
Otherwise, the non-principal switch refuses the assigned domain ID and isolates its interface connected to the principal switch. HP recommends that you configure the same allowed domain ID list for all switches in a VSAN. To configure an allowed domain ID list:...
Page 45: Configuring A Domain Id For A Switch
If the configured domain ID is static, the non-principal switch isolates the upstream principal link and refuses the assigned domain ID. HP recommends that you configure domain IDs of the same type for all switches in a VSAN. To configure a domain ID for a switch:...
Page 46: Setting Fabric Timers
Setting fabric timers The fabric operation involves the following timers: Distributed service timeout period. • Error detection timeout period. • Resource allocation timeout period. • For more information about these timers, see FC-related protocols and standards. You can set fabric timers in one of the following views: System view—The setting takes effect on all VSANs.
Page 47: Configuring Fabric Reconfiguration
Configuring fabric reconfiguration IMPORTANT: The fabric reconfiguration feature takes effects only when the fabric configuration feature is enabled. A fabric reconfiguration can be performed manually or automatically by using the automatic reconfiguration feature. A fabric reconfiguration triggers a principal switch selection phase. A fabric reconfiguration can be disruptive or nondisruptive.
Page 48: Configuring A Vfc Interface To Reject Incoming Rcf Requests
Configuring a VFC interface to reject incoming RCF requests In a stable fabric, to avoid unnecessary disruptive reconfigurations, you can configure a VFC interface to reject RCF requests received in a VSAN. With this feature, the switch replies with a reject message and isolates the interface that receives an RCF request.
Page 49: Rscn Aggregation
RSCN. Configuration procedure HP recommends that you enable RSCN aggregation and set the same timer value on all switches in a VSAN. The RSCN aggregation timer takes effect only when RSCN aggregation is enabled. To configure RSCN aggregation:...
Page 50: Enabling Scsi-Fcp Information Autodiscovery
Feature—Feature of the supported FC4-layer protocol. Each FC4-layer protocol can include one of • the four Features and defines the meaning of each Feature. Before communicating with other nodes, a node obtains information about all nodes that support SCSI-FCP from the switch. You can use the display fc name-service database command to display the FC4 information of nodes in the name service database.
Page 51: Displaying And Maintaining A Fabric
The fc wwn default-fc4-type command can configure only one combination of FC4-Type and Feature at a time. To configure the default FC4 information for a node: Step Command Remarks Enter system view. system-view fc wwn wwn-value default-fc4-type Configure the default { type-value feature feature-map | By default, no default FC4 FC4 information for a...
Page 52 Configuration procedure This section describes only fabric building configurations. Configure Switch A: # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective.
Page 53 (To leave the existing filename unchanged, press the enter key): Validating file. Please wait... Saved the current configuration to mainboard device successfully. [SwitchB] quit # Reboot the switch. <SwitchB> reboot Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device.
Page 54: Dynamic Fabric Building Configuration Example
[SwitchB-vsan1] display fc domain vsan 1 Domain Information of VSAN 1: Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1B:1B Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 2 Configuration information: Domain configure: Disabled Domain auto-reconfigure: Disabled Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 2 (static) Principal switch running time information: Priority: 128...
Page 55 Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective. # Save the configuration. [SwitchA] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file.
Page 56 Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device. Continue? [Y/N]:y Now rebooting, please wait... # Configure the switch to operate in FCF mode. <SwitchB> system-view [SwitchB] fcoe-mode fcf # Enable the fabric configuration feature in VSAN 1. By default, the fabric configuration feature is enabled.
Page 57 # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchD> system-view [SwitchD] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective.
Page 58 Fabric name: 48:33:43:2d:46:43:1A:1A Priority: 128 Domain ID: 11 (preferred) Principal switch running time information: Priority: 1 Path Interface Upstream Vfc1 Downstream Vfc2 The output shows that: The domain configuration was complete. The principal switch assigned domain ID 1 1 to Switch A. # Display the domain ID list of VSAN 1.
Page 59: Configuring Fc Routing And Forwarding
Configuring FC routing and forwarding Overview Routing and forwarding in an FC SAN is achieved through FCF switches. When an FCF switch receives a packet, an FCF switch performs the following operations: • Selects an optimal route based on the destination address. Forwards the packet to the next FCF switch in the path until the packet reaches the last FCF switch.
Page 60: Direct Routes
FCF switch is 0x010000. A network mask is made up of a certain number of consecutive 1s. It can be expressed in hexadecimal format or by the number of 1s. Protocol—Protocol type, which can be DIRECT (direct routes), STATIC (static routes), or FSPF (FSPF •...
Page 61: Static Routes
When an FCF switch assigns FC addresses to directly connected N_Ports, the FCF switch also adds • the direct routes of these addresses to the routing table. The direct route includes the following settings: The destination address is an assigned FC address. The mask is 0xFFFFFF.
Page 62: Configuring Static Fc Routes
Link ID, which identifies a link and includes the domain ID of the switch at the peer end of the link. Source interface and destination interface of the link. Link type, for example, point-to-point connection. Cost for packet transmission over the link. The smaller the cost, the better the link. The route selection algorithm uses this value to determine the best route.
Page 63: Configuration Procedure
Configuration procedure To configure a static FC route: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id fc route-static fcid { mask | mask-length } Configure a static FC interface-type interface-number [ cost By default, no static FC route exists. route.
Page 64: Setting The Shortest Spf Calculation Interval
Step Command Remarks Enter VSAN view. vsan vsan-id By default, FSPF is enabled after a VSAN is Enable FSPF in the VSAN. fspf enable created. Setting the shortest SPF calculation interval SPF calculations occur when the LSDB changes. To limit the amount of CPU resources consumed by frequent SPF calculations, you can change the shortest SPF calculation interval.
Page 65: Setting The Fspf Cost For An Interface
Step Command Remarks Enter VSAN view. vsan vsan-id Set the minimum LSR fspf min-ls-interval value The default setting is 5 seconds. refresh interval. Setting the FSPF cost for an interface Each link has a cost. The route selection algorithm uses this value to determine the best route. The smaller the interface FSPF cost, the smaller the link cost.
Page 66: Setting The Lsr Retransmission Interval For An Interface
NOTE: The configured dead interval must be greater than the hello interval and must be the same at the two ends of the link. To set the dead interval for an interface: Step Command Remarks Enter system view. system-view Enter VFC interface view. interface vfc interface-number Set the dead interval for the fspf dead-interval value vsan...
Page 67: Displaying And Maintaining Fc Routing And Forwarding
An active/standby switchover. • GR involves the following roles: GR restarter—GR-capable device where a protocol restart or active/standby switchover occurs. • GR helper—The GR restarter's neighboring device that assists in the GR process. • Configuring the GR restarter Step Command Remarks Enter system view.
Page 68: Fc Routing Configuration Examples
FC routing configuration examples Static FC routing configuration example Network requirements The fabric comprises three switches, Switch A, B, and C. Configure static routes to enable any two FC switches to communicate with each other. Figure 20 Network diagram Switch B Domain ID: 2 VFC1 VFC2...
Page 69 # Configure the switch to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf # Enable the fabric configuration feature in VSAN 1. [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Set the domain ID to 1 in VSAN 1. [SwitchA-vsan1] domain-id 1 static [SwitchA-vsan1] quit # Create interface VFC 1.
Page 70 [SwitchB] quit # Reboot the switch. <SwitchB> reboot Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device. Continue? [Y/N]:y Now rebooting, please wait... # Configure the switch to operate in FCF mode. <SwitchB>...
Page 71 [SwitchB] vlan 10 [SwitchB-vlan10] fcoe enable vsan 1 [SwitchB-vlan10] quit # Configure two static routes in VSAN 1. [SwitchB] vsan 1 [SwitchB-vsan1] fc route-static 010000 8 vfc 1 [SwitchB-vsan1] fc route-static 030000 8 vfc 2 Configure Switch C: # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchC>...
Page 72 [SwitchC-Vfc2] quit # Configure Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 10. [SwitchC] interface ten-gigabitethernet 1/0/2 [SwitchC-Ten-GigabitEthernet1/0/2] port link-type trunk [SwitchC-Ten-GigabitEthernet1/0/2] port trunk permit vlan 10 [SwitchC-Ten-GigabitEthernet1/0/2] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchC] vlan 10 [SwitchC-vlan10] fcoe enable vsan 1 [SwitchC-vlan10] quit...
Page 73: Fspf Configuration Example
0xfffffc/24 DIRECT InLoop0 0xfffffd/24 DIRECT InLoop0 # FCping Switch C from Switch A. [SwitchA-vsan1] fcping fcid fffc03 vsan 1 FCPING fcid 0xfffc03: 128 data bytes, press CTRL_C to break Reply from 0xfffc03: bytes = 128 time = 23 ms Reply from 0xfffc03: bytes = 128 time = 9 ms Reply from 0xfffc03: bytes = 128 time = 19 ms Reply from 0xfffc03: bytes = 128 time = 14 ms Reply from 0xfffc03: bytes = 128 time = 25 ms...
Page 74 <SwitchA> reboot Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device. Continue? [Y/N]:y Now rebooting, please wait... # Configure the switch to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf # Create VSAN 2, and enable the fabric configuration feature in VSAN 2. [SwitchA] vsan 2 [SwitchA-vsan2] domain configure enable # Set the domain ID to 1 in VSAN 2.
Page 75 # Save the configuration. [SwitchB] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file. Please wait... Saved the current configuration to mainboard device successfully. [SwitchB] quit # Reboot the switch.
Page 76 [SwitchB-Vfc1] quit Verifying the configuration # Display the FSPF neighbor information for Switch A. [SwitchA] display fspf neighbor FSPF neighbor information of VSAN 2(01): Interface NbrDomain IfIndex NbrIfIndex Dead Time State Vfc1 0x68 0x68 00:01:06 Full # Display the FC routing table for Switch A. [SwitchA] display fc routing-table vsan 2 Routing Table: VSAN 2 Destinations : 5...
Page 77: Configuring Fc Zones
Configuring FC zones Overview The VSAN technology divides a physical SAN into multiple VSANs, which are separated from one another, and provides more secure, reliable, and flexible services. A VSAN, however, cannot perform access control over the servers and disk devices (or the N_Ports) connected to a fabric. N_Ports in the same VSAN can access one another only if these N_Ports register name services.
Page 78 Figure 22 Zone database structure In the zone database structure: A zone set is a set of zones. A zone is a set of zone members, which are N_Ports or F_Ports. N_Port • membership can be identified by the port WWN (pWWN) or FC address of an N_Port. F_Port membership can be identified by the WWN of an F_Port (fWWN).
Page 79 Figure 23 Active and full zone sets In basic zoning mode, the system checks the size of the data to be distributed when you activate a zone set. If the size of the data exceeds the system limit, the activation fails, and an error message is displayed. In enhanced zoning mode, the system does not limit the size of the data to be distributed.
Page 80: Pairwise
Pairwise The Pairwise feature is supported only in enhanced zoning mode. Typically, servers do not need to access each other, and storage devices do not need to access each other. Without the Pairwise feature, an access entry is generated for any pair of members in a zone. The Pairwise feature allows a member to access only members with a different role in the same zone.
Page 81 Acquire Change Authorization (ACA). • • Stage Fabric Configuration Update (SFC). Update Fabric Configuration (UFC). • Release Change Authorization (RCA). • These types of packets implement locking, data synchronization, submission, and unlocking processes, respectively. These processes ensure that only one switch is the managing switch when multiple users trigger a data distribution on different switches at the same time.
Page 82: Zone Distribution In Enhanced Zoning Mode
If the managing switch does not receive ACC packets from one or more managed switches, it sends an RCA request to notify each managed switch to release the change authorization state. If the managed switch replies with neither an ACC packet nor an RJT packet because of its abnormal state, the managing switch cannot be released from its locked state.
Page 83: Zone Merge In Basic Zoning Mode
For zone distribution in enhanced zoning mode, the SFC request always has hard zoning status. For zone distribution caused by a switchover from basic zoning to enhanced zoning, the SFC request carries hard zoning status. For zone distribution caused by a switchover from enhanced zoning to basic zoning, the SFC request does not have hard zoning status.
Page 84 Figure 25 Zone merge process between two switches The zone merge process is as follows: Switch A and Switch B are new neighbors to each other. Suppose that Switch A first initiates a merge to Switch B. Switch A sends an MRRA request carrying the size of its data to be merged to Switch B. After receiving the MRRA request, Switch B determines whether to accept the merge according to its local data size.
Page 85: Zone Merge In Enhanced Zoning Mode
After the merge process initiated by Switch A is complete, Switch B initiates a merge process to all its neighbors. This synchronizes Switch B's local database changes resulting from the merge to the entire fabric. Two 1-way merge processes can ensure data consistency between Switch A and Switch B. NOTE: Consistent active zone sets among switches can be achieved by a merge.
Page 86: Access Control
In the event of a merge failure, the link between participating switches is isolated, and both zone • databases remain unchanged. Enhanced zoning has stricter rules than basic zoning. • The enhanced zoning mode includes the following merge rules: If either the merge control mode or default zone policy is different from that in the local zone •...
Page 87: Configuring A Zoning Mode
Tasks at a glance Remarks (Required.) Configuring zone sets (Required.) Configuring the default zone policy This task can be performed only in basic zoning (Required.) Setting the zone distribution and merge type mode. This task can be performed only in enhanced (Required.) Setting a merge control mode zoning mode.
Page 88: Configuring The Pairwise Feature
Step Command Remarks Enter VSAN view. vsan vsan-id • Enable the enhanced zoning mode: By default, the basic zoning mode is zone mode enhanced Configure a zoning mode. enabled. • Enable the basic zoning mode: undo zone mode enhanced Configuring the Pairwise feature This feature can be configured only in enhanced zoning mode.
Page 89: Configuring Zones
Step Command Remarks Create a zone alias and If the zone alias has been created, zone-alias name zone-alias-name enter its view. enter its view directly. Add a member to the zone member { fcid fcid | fwwn fwwn | By default, no member exists in a alias.
Page 90: Configuring The Default Zone Policy
Configuring the default zone policy In enhanced zoning mode, the switch distributes the default zone policy with other zone data. In basic zoning mode, you must manually configure a consistent default zone policy across the fabric. When the switch performs a zoning mode switchover, it also distributes the default zone policy with other zone data.
Page 91: Enabling Hard Zoning
This feature is supported only in enhanced zoning mode. To ensure a consistent merge control mode across the fabric, use the zone activate or zone distribute command after you set a merge control mode. To set a merge control mode: Step Command Remarks...
Page 92: Configuration Procedure
When soft zoning is enough for meeting the access control requirements of a VSAN, you can • disable hard zoning for the VSAN to save the hardware entry resources. In basic zoning mode, you must manually configure hard zoning to ensure consistency across the •...
Page 93: Triggering A Complete Distribution
NOTE: Active zone set information will not contain the alias names of zone members. If a zone in the active zone set has members with a zone alias, the non-overlapping N_Port members in the zone alias are added to the zone. You can view the zone member change by using the display zoneset active command. Triggering a complete distribution Use the zoneset distribute command to trigger a one-time complete distribution, which distributes both the active zone set and zone database.
Page 94: Copying Zone Aliases, Zones, And Zone Sets
Copying zone aliases, zones, and zone sets You can create a zone alias, zone, or zone set by copying an existing one. The source and the destination have the same contents but different names. To copy a zone alias, zone, and zone set: Step Command Remarks...
Page 95: Displaying And Maintaining Fc Zones
Step Command Remarks snmp-agent trap enable fc-zone Enable SNMP [ activation-completed | By default, SNMP notifications for notifications for the zone defaultzone-change | the zone module are disabled. module. hardzone-change | merge-failed | merge-succeeded ] * Displaying and maintaining FC zones Execute display commands in any view and reset commands in user view.
Page 96: Requirements Analysis
Figure 26 Network diagram Disk A Server A PWWN: Zone 1 FC_ID: 11:22:33:44:55:66:77:88 010001 (FC_ID:020006) Switch A Switch B Disk B Server B PWWN: FC_ID: 22:33:44:55:66:77:88:99 010002 (FC_ID:020005) Zone 2 Alias 1 Server C Disk C Zone 3 FC_ID: FC_ID: 010003 020004 Requirements analysis...
Page 97 Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file. Please wait... Saved the current configuration to mainboard device successfully. [SwitchA] quit # Reboot the switch. <SwitchA> reboot Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device.
Page 98: Verifying The Configuration
# Add the zone alias Alias1 to Zone3 as a member. [SwitchA-vsan1-zone-Zone3] member zone-alias Alias1 [SwitchA-vsan1-zone-Zone3] quit # Create a zone set named Zoneset1, and add zones Zone1, Zone2, and Zone3 as its members. [SwitchA-vsan1] zoneset name Zoneset1 [SwitchA-vsan1-zoneset-Zoneset1] member Zone1 [SwitchA-vsan1-zoneset-Zoneset1] member Zone2 [SwitchA-vsan1-zoneset-Zoneset1] member Zone3 [SwitchA-vsan1-zoneset-Zoneset1] quit...
Page 99 zone-alias name Alias1 fcid 0x020004 target pwwn 22:33:44:55:66:77:88:99 target # Display the zone or zone alias to which 020004 (FC ID type) belongs. <SwitchB> display zone member fcid 020004 fcid 0x020004 VSAN 1: zone-alias Alias1 zone Zone2 zone Zone3 # Display information about the active zone set in VSAN 1. <SwitchB>...
Page 100: Configuring Npv
Configuring NPV Overview NPV enables an FC SAN to accommodate more than 239 switches. NPV switches forward traffic from nodes to the core switch. Figure 27 shows a typical NPV network diagram. Figure 27 NPV network diagram NOTE: An NPV switch must be directly connected to the core switch. Downlink interface and downlink A downlink interface, also known as a server interface, is an interface through which an NPV switch connects to a node.
Page 101: Uplink Interface And Uplink
Uplink interface and uplink An uplink interface, also known as an external interface, is the interface through which an NPV switch connects to the core switch. It can be a VFC interface, both of which must be configured to operate in NP mode.
Page 102: Configuring Uplink Interfaces And Downlink Interfaces
Tasks at a glance Remarks (Optional.) Configuring downlink-to-uplink interface mappings (Optional.) Initiating a disruptive load-balancing process Configuring uplink interfaces and downlink interfaces After configuring the switch to operate in NPV mode, configure the uplink interfaces and downlink interfaces. Configuring uplink interfaces Uplink interfaces must be VFC interfaces in NP mode.
Page 103: Configuring Downlink-To-Uplink Interface Mappings
Configuring downlink-to-uplink interface mappings CAUTION: If an uplink interface mapped by a downlink interface is not in the configured mappings, the switch initializes the downlink interface, resulting in traffic interruption. NPV switches automatically map downlink interfaces to uplink interfaces. Typically, automatic mapping can meet your requirements.
Page 104: Npv Configuration Examples
Task Command display fc nport [ interface interface-type Display the login information of NP_Ports. interface-number ] display npv login [ vsan vsan-id ] [ interface Display the nodes on downlink interfaces and their interface-type interface-number ] mapped uplink interfaces. display npv login [ vsan vsan-id ] count display npv traffic-map [ vsan vsan-id ] [ interface Display the traffic mapping information.
Page 105 Saved the current configuration to mainboard device successfully. [SwitchA] quit # Reboot the switch. <SwitchA> reboot Start to check configuration with next startup configuration file, please wait..DONE! This command will reboot the device. Continue? [Y/N]:y Now rebooting, please wait... # Configure the switch to operate in NPV mode. <SwitchA>...
Page 106 # Configure Ten-GigabitEthernet 1/0/3 as a trunk port, and assign the port to VLAN 10. [SwitchA] interface ten-gigabitethernet 1/0/3 [SwitchA-Ten-GigabitEthernet1/0/3] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/3] port trunk permit vlan 10 [SwitchA-Ten-GigabitEthernet1/0/3] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit...
Page 107: Verifying The Configuration
[SwitchB-vsan1] quit # Create interface VFC 3. [SwitchB] interface vfc 3 # Configure the mode of VFC 3 as F. [SwitchB-Vfc3] fc mode f # Bind VFC 3 to interface Ten-GigabitEthernet 1/0/3. [SwitchB-Vfc3] bind interface ten-gigabitethernet 1/0/3 # Assign VFC 3 to VSAN 1 as a trunk port. [SwitchB-Vfc3] port trunk vsan 1 [SwitchB-Vfc3] quit # Configure Ten-GigabitEthernet 1/0/3 as a trunk port, and assign the port to VLAN 10.
Page 108 Number of Server Interfaces: 2 # Display the traffic mapping information on NPV switch Switch A. [SwitchA] display npv traffic-map NPV traffic map information of VSAN 1: Server Interface External Interface Vfc1 Vfc3 Vfc2 Vfc3...
Page 109: Configuring Fip Snooping
Configuring FIP snooping Overview To communicate with devices in the FC SAN, a node must register with an FC fabric. An FC switch has point-to-point connections with nodes. An FC switch brings up an interface connected to a node only after the node completes fabric login on the interface.
Page 110: How Fip Snooping Works
How FIP snooping works After FIP snooping is enabled for a VLAN, Ethernet interfaces on the Transit switch establish FIP snooping rules according to FIP frames (with EtherType as 0x8914). Then, the Ethernet interfaces control the forwarding of FCoE frames (with EtherType as 0x8906) based on the FIP snooping rules. To facilitate description, the following definitions are specified: FIP snooping rules generated on an Ethernet interface operating in FCF mode are called FCF FIP •...
Page 111: Fip Snooping Configuration Task List
Controlling forwarding of FCoE frames After establishing FIP snooping rules, a Transit switch forwards FCoE frames that match FIP snooping rules and drops those that do not match FIP snooping rules. As a result, only successfully registered ENodes can communicate with FCF switches. FIP snooping configuration task list Tasks at a glance Remarks...
Page 112: Setting The Fc-Map Value
Setting the FC-MAP value The FC-MAP value identifies an FCoE network. Switches (including FCF switches and Transit switches) in the same FCoE network must have the same FC-MAP value. You can use the fcoe fcmap command to set the FC-MAP value in frames sent out of an FCF switch. You can use the fip-snooping fc-map command to set an FC-MAP value for a VLAN on a Transit switch.
Page 113: Configuration Procedure
Figure 30 Network diagram Configuration procedure Configure the Transit switch: # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <Transit> system-view [Transit] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective.
Page 114 [Transit-Ten-GigabitEthernet1/0/1] fip-snooping port-mode enode [Transit-Ten-GigabitEthernet1/0/1] quit # Configure interface Ten-GigabitEthernet 1/0/2 as a trunk port. [Transit] interface ten-gigabitethernet 1/0/2 [Transit-Ten-GigabitEthernet1/0/2] port link-type trunk # Assign the interface to VLAN 10. [Transit-Ten-GigabitEthernet1/0/2] port trunk permit vlan 10 # Configure the interface to operate in FCF mode. [Transit-Ten-GigabitEthernet1/0/2] fip-snooping port-mode fcf [Transit-Ten-GigabitEthernet1/0/2] quit Configure the FCF switch:...
Page 115: Verifying The Configuration
# Bind VFC 2 to interface Ten-GigabitEthernet 1/0/2. [FCF-vfc2] bind interface ten-gigabitethernet 1/0/2 [FCF-Vfc2] quit # Configure Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 10. [FCF] interface ten-gigabitethernet 1/0/2 [FCF-Ten-GigabitEthernet1/0/2] port link-type trunk [FCF-Ten-GigabitEthernet1/0/2] port trunk permit vlan 10 [FCF-Ten-GigabitEthernet1/0/2] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 10.
Page 116: Configuring Fcs
Configuring FCS Only FCF switches support FCS. Switches described in this chapter refer to FCF switches. Overview The Fabric Configuration Server (FCS) feature provides discovery of topology information of a fabric, including switches in the fabric and ports on each switch. A management application (for example, SNMP NMS software) determines the physical and logical topologies of the fabric based on the FCS topology information.
Page 117 Attribute Description Transmitter type of the port: • 10GBASE-CX4. • 10GBASE-ER 1550nm laser. • 10GBASE-EW 1550nm laser. • 10GBASE-LR 1310nm laser. • 10GBASE-LW 1310nm laser. • Tx type 10GBASE-LX4 WWDM 1300nm laser. • 10GBASE-SR 850nm laser. • 10GBASE-SW 850nm laser. •...
Page 118: Starting A Topology Discovery
Attribute Description The supported speed can be one or any combination of the following options: • 1 Gbps. • 2 Gbps. • 4 Gbps. Port speed capability • 8 Gbps. • 10 Gbps. • 16 Gbps. • 20 Gbps. The current speed can only be one of the following options: •...
Page 119: Stopping A Topology Discovery
The switch processes local topology changes in real time, regardless of topology discovery. To start a topology discovery: Step Command Remarks Enter system view. system-view You can start a second topology discovery for the Start a topology fcs discovery start same VSAN only after the first topology discovery is discovery in specified [ age interval ] vsan...
Page 120: Configuration Procedure
Figure 31 Network diagram Configuration procedure This section describes only FCS configurations. # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective.
Page 121 : 10:00:00:11:22:00:01:01 Domain ID : 0x01 Management address list : snmp://192.168.0.1 Fabric name : 10:00:00:11:22:00:01:01 Logical name : SwitchA Information list : HP#HP FlexFabric 5700#Version 7.1.045, Release 2416 IE_Ports: Interface Port WWN Port type Attached port WWNs Vfc1 e1:01:00:11:22:00:01:01 E_Port e2:01:00:11:22:00:01:01...
Page 122 [SwitchA] display fcs ie vsan 1 IE List for VSAN 1: IE WWN Domain ID Mgmt addr list Logical name 10:00:00:11:22:00:01:01 0x01 snmp://192.168.0.1 SwitchA 10:00:00:11:22:00:01:02 0x02 snmp://192.168.0.2 SwitchB 10:00:00:11:22:00:01:03 0x03 snmp://192.168.0.3 SwitchC 10:00:00:11:22:00:01:04 0x04 snmp://192.168.0.4 SwitchD Total 4 IEs in Fabric. # Display brief information about ports in VSAN 1 on Switch A.
Page 123: Configuring Fdmi
Configuring FDMI Only FCF switches support FCS. Switches described in this chapter refer to FCF switches. Overview The Fabric Device Management Interface (FDMI) feature allows you to view information about host bus adapters (HBAs) on all registered nodes in a fabric. The HBA information includes HBAs and ports on each HBA.
Page 124: Displaying And Maintaining Fdmi
Table 9 Port object attributes Attribute Description Port WWN WWN of the port. • FCP—Fibre Channel Protocol. • GS3. • • LLC/SNAP. Supported FC4 types • NPV. • SNMP. • SW-ILS. • The supported speed can be one or more of the following options: •...
Page 125: Configuring Fc Ping
Configuring FC ping Overview In an FC SAN, use the fcping command to identify whether a destination address is reachable and to test network connectivity. In an FC ping operation, the source device sends echo requests to the destination device. It determines whether the destination is reachable based on whether it receives echo replies.
Page 126: Configuration Procedure
Configuration procedure Configure Switch A: # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective.
Page 127 [SwitchA-Ten-GigabitEthernet1/0/1] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit # Configure a static route in VSAN 1. [SwitchA] vsan 1 [SwitchA-vsan1] fc route-static 020000 8 vfc 1 [SwitchA-vsan1] quit Configure Switch B: # Configure the switch to operate in advanced mode.
Page 128: Verifying The Configuration
# Assign VFC 1 to VSAN 1. [SwitchB-Vfc1] port trunk vsan 1 [SwitchB-Vfc1] quit # Configure Ten-GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 10. [SwitchB] interface ten-gigabitethernet 1/0/1 [SwitchB-Ten-GigabitEthernet1/0/1] port link-type trunk [SwitchB-Ten-GigabitEthernet1/0/1] port trunk permit vlan 10 [SwitchB-Ten-GigabitEthernet1/0/1] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1.
Page 129: Configuring Fc Tracert
Configuring FC tracert Overview In an FC SAN, use the fctracert command to obtain bidirectional routing information between source and destination, and check the network connectivity. You can use this feature to identify failed nodes and test network connectivity. FC tracert includes the following processes: Uplink process—Beginning from the source, each switch along the path sends the Switch Trace •...
Page 130: Configuration Procedure
Uplink process Switch A adds its uplink path information (including its WWN and domain ID) to the STR request packet and sends the packet to the next hop, Switch B. After receiving the packet, Switch B replies with an STR ACC packet to Switch A. Switch B adds its uplink path information to the received STR packet and sends it to the destination switch, Switch C.
Page 131 [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective. # Save the configuration. [SwitchA] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file.
Page 132 # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit Configure Switch B: # Configure the switch to operate in advanced mode. (Skip this step if the switch is operating in advanced mode.) <SwitchB>...
Page 133 [SwitchB-Vfc1] port trunk vsan 1 [SwitchB-Vfc1] quit # Configure Ten-GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 10. [SwitchB] interface ten-gigabitethernet 1/0/1 [SwitchB-Ten-GigabitEthernet1/0/1] port link-type trunk [SwitchB-Ten-GigabitEthernet1/0/1] port trunk permit vlan 10 [SwitchB-Ten-GigabitEthernet1/0/1] quit # Create interface VFC 2. [SwitchB] interface vfc 2 # Configure the mode of VFC 2 as E.
Page 134 Now rebooting, please wait... # Configure the switch to operate in FCF mode. <SwitchC> system-view [SwitchC] fcoe-mode fcf # Enable the fabric configuration feature in VSAN 1. [SwitchC] vsan 1 [SwitchC-vsan1] domain configure enable # Set the domain ID to 3 in VSAN 1. [SwitchC-vsan1] domain-id 3 static # Disable FSPF in VSAN 1.
Page 135: Verifying The Configuration
Route present for: 0xfffc03, press CTRL_C to break 20:00:00:0b:46:00:02:82(0xfffc01) 20:00:00:05:30:00:18:db(0xfffc02) Fctracert uncompleted: no route to destination port. The output shows that: Switch A can reach Switch B. Switch B cannot reach Switch C. Verifying the configuration # Use the display fc routing-table command on Switch B to verify that there is not a route to Switch C. (Details not shown.)
Page 136: Comprehensive Fcoe Configuration Examples
Comprehensive FCoE configuration examples FCoE configuration example (in standalone mode) Network requirements As shown in Figure Switch A and Switch B are connected to an Ethernet switch, and operate at the access layer of the • LAN. Switch A and Switch B are connected to Switch C and Switch D, respectively. •...
Page 137: Requirements Analysis
To meet the network requirements, perform the following tasks: • To transmit the storage traffic over lossless Ethernet links in the SANs, HP recommends that you perform the following tasks: Configure DCBX, PFC in auto mode, and ETS on the Ethernet interfaces connecting the switches to the server.
Page 138: Configuration Procedures
Switch A and Switch B, disable STP on the interfaces connecting the four FCF switches. The SANs are complex. HP recommends that you use the dynamic mode to build the fabric and use • FSPF for FC routing.
Page 139 [SwitchA-vlan1001] description ToLAN [SwitchA-vlan1001] quit [SwitchA] vlan 4001 [SwitchA-vlan4001] description ToSAN [SwitchA-vlan4001] quit # Enable STP globally. [SwitchA] stp global enable # Configure interface Ten-GigabitEthernet 1/0/1 as a hybrid port. [SwitchA] interface ten-gigabitethernet 1/0/1 [SwitchA-Ten-GigabitEthernet1/0/1] port link-type hybrid # Assign Ten-GigabitEthernet 1/0/1 to VLAN 1001 as an untagged member. [SwitchA-Ten-GigabitEthernet1/0/1] port hybrid vlan 1001 untagged # Assign Ten-GigabitEthernet 1/0/1 to VLAN 4001 as a tagged member.
Page 140 [SwitchA-Ten-GigabitEthernet1/0/8] port link-aggregation group 1 [SwitchA-Ten-GigabitEthernet1/0/8] quit # Configure Layer 2 aggregate interface 1 as a trunk port, and assign the aggregate interface to VLAN 4001. [SwitchA] interface bridge-aggregation 1 [SwitchA-Bridge-Aggregation1] port link-type trunk [SwitchA-Bridge-Aggregation1] port trunk permit vlan 4001 [SwitchA-Bridge-Aggregation1] quit Configure DCBX: # Enable LLDP globally.
Page 141 # Configure Ten-GigabitEthernet 1/0/1 to trust the 802.1p priority included in incoming packets. [SwitchA-Ten-GigabitEthernet1/0/1] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/0/1] quit # Configure interfaces Ten-GigabitEthernet 1/0/5 through Ten-GigabitEthernet 1/0/8 as follows: Enable PFC by force on the interfaces. Enable PFC for 802.1p priority 3 on the interfaces. Configure the interfaces to trust the 802.1p priority included in incoming packets.
Page 142 Assign 50% of the interface bandwidth to Ethernet data traffic (traffic assigned to queue 0). [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af1 group 1 byte-count 1 [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr be group 1 byte-count 1 # Assign the other queues to the SP group on interface Ten-GigabitEthernet 1/0/1. [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af2 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af3 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af4 group sp...
Page 143: Configuring Switch B
# Enable FCoE for VLAN 4001 and map VLAN 4001 to VSAN 100. [SwitchA] vlan 4001 [SwitchA-vlan4001] fcoe enable vsan 100 [SwitchA-vlan4001] quit # Enter the view of VSAN 100, and configure the members in the default zone to access each other.
Page 144 # Assign the interface to VLAN 4001 as a tagged member. [SwitchC-Ten-GigabitEthernet1/0/1] port hybrid vlan 4001 tagged [SwitchC-Ten-GigabitEthernet1/0/1] quit # Create Layer 2 aggregate interface 1, and configure it to operate in dynamic aggregation mode. [SwitchC] interface bridge-aggregation 1 [SwitchC-Bridge-Aggregation1] link-aggregation mode dynamic [SwitchC-Bridge-Aggregation1] quit # Assign ports Ten-GigabitEthernet 1/0/5 through Ten-GigabitEthernet 1/0/8 to Layer 2 aggregation group 1.
Page 145 [SwitchC-behavior-DCBX] remark dot1p 3 [SwitchC-behavior-DCBX] quit # Create a QoS policy named DCBX. [SwitchC] qos policy DCBX # Associate class DCBX with traffic behavior DCBX in the QoS policy, and specify that the association apply to DCBX. [SwitchC-qospolicy-DCBX] classifier DCBX behavior DCBX mode dcbx [SwitchC-qospolicy-DCBX] quit # Enable LLDP and DCBX TLV advertising on interface Ten-GigabitEthernet 1/0/1.
Page 146 Configure FCoE: # Configure the switch to operate in FCF mode. [SwitchC] fcoe-mode fcf # Enable the fabric configuration feature in VSAN 100. By default, the fabric configuration feature is enabled. [SwitchC] vsan 100 [SwitchC-vsan100] domain configure enable # Set the switch priority to 1, so the switch can be selected as the principal switch. [SwitchC-vsan100] priority 1 # Set the domain ID to 1.
Page 147: Verifying The Configuration
Configuring Switch D Configure Switch D in a similar way Switch C is configured, with the following differences: • The aggregate interface configured on Switch C is Layer 2 aggregate interface 1. The aggregate interface configured on Switch D is Layer 2 aggregate interface 2. •...
Page 148: Fcoe Configuration Example (In Irf Mode)
Destinations : 5 Routes : 5 Destination/mask Protocol Preference Cost Interface 0x010000/8 FSPF Vfc10 0xfffc01/24 DIRECT InLoop0 0xfffffa/24 DIRECT InLoop0 0xfffffc/24 DIRECT InLoop0 0xfffffd/24 DIRECT InLoop0 The output shows that an FSPF route from Switch A to Switch C exists, with the outgoing interface VFC 10. # Display the node login information for VSAN 100.
Page 149: Requirements Analysis
IRF-port 1/1 and IRF-port 2/2 at the two ends, respectively. Aggregate the links from the Ethernet switch to Switch A and Switch B. To transmit the storage traffic over lossless Ethernet links in the SANs, HP recommends that you •...
Page 150: Configuration Procedures
IRF fabric, disable STP on the interfaces connecting the IRF fabric to Switch C and Switch D. The SANs are complex. HP recommends that you use the dynamic mode to build the fabric and use •...
Page 151 <SwitchA> system-view [SwitchA] system-working-mode AdvancedBridge Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective. # Save the configuration. [SwitchA] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): Validating file.
Page 152 [SwitchA-Ten-GigabitEthernet1/0/1] quit # Configure interface Ten-GigabitEthernet 2/0/1 as a hybrid port. [SwitchA] interface ten-gigabitethernet 2/0/1 [SwitchA-Ten-GigabitEthernet2/0/1] port link-type hybrid # Assign Ten-GigabitEthernet 2/0/1 to VLAN 1001 as an untagged member. [SwitchA-Ten-GigabitEthernet2/0/1] port hybrid vlan 1001 untagged # Assign Ten-GigabitEthernet 2/0/1 to VLAN 4002 as a tagged member. [SwitchA-Ten-GigabitEthernet2/0/1] port hybrid vlan 4002 tagged # Set the PVID to VLAN 1001 for Ten-GigabitEthernet 2/0/1.
Page 153 [SwitchA-Ten-GigabitEthernet1/0/7] quit [SwitchA] interface ten-gigabitethernet 1/0/8 [SwitchA-Ten-GigabitEthernet1/0/8] port link-aggregation group 1 [SwitchA-Ten-GigabitEthernet1/0/8] quit # Configure Layer 2 aggregate interface 1 as a trunk port, and assign the aggregate interface to VLAN 4001. [SwitchA] interface bridge-aggregation 1 [SwitchA-Bridge-Aggregation1] port link-type trunk [SwitchA-Bridge-Aggregation1] port trunk permit vlan 4001 [SwitchA-Bridge-Aggregation1] quit # Create Layer 2 aggregate interface 2, and configure it to operate in dynamic aggregation...
Page 154 The assigned domain ID is: 1 Info: MAD LACP only enable on dynamic aggregation interface. [SwitchA-Bridge-Aggregation3] quit # Assign ports Ten-GigabitEthernet 1/0/10 and Ten-GigabitEthernet 2/0/10 to Layer 2 aggregation group 3. [SwitchA] interface ten-gigabitethernet 1/0/10 [SwitchA-Ten-GigabitEthernet1/0/10] port link-aggregation group 3 [SwitchA-Ten-GigabitEthernet1/0/10] quit [SwitchA] interface ten-gigabitethernet 2/0/10 [SwitchA-Ten-GigabitEthernet2/0/10] port link-aggregation group 3...
Page 155 [SwitchA-Ten-GigabitEthernet1/0/1] lldp enable [SwitchA-Ten-GigabitEthernet1/0/1] lldp tlv-enable dot1-tlv dcbx # Apply QoS policy DCBX to the outgoing traffic of Ten-GigabitEthernet 1/0/1. [SwitchA-Ten-GigabitEthernet1/0/1] qos apply policy DCBX outbound [SwitchA-Ten-GigabitEthernet1/0/1] quit # Enable LLDP and DCBX TLV advertising on interface Ten-GigabitEthernet 2/0/1. [SwitchA] interface ten-gigabitethernet 2/0/1 [SwitchA-Ten-GigabitEthernet2/0/1] lldp enable [SwitchA-Ten-GigabitEthernet2/0/1] lldp tlv-enable dot1-tlv dcbx # Apply QoS policy DCBX to the outgoing traffic of Ten-GigabitEthernet 2/0/1.
Page 156 [SwitchA-Ten-GigabitEthernet1/0/7] quit [SwitchA] interface ten-gigabitethernet 1/0/8 [SwitchA-Ten-GigabitEthernet1/0/8] priority-flow-control enable [SwitchA-Ten-GigabitEthernet1/0/8] priority-flow-control no-drop dot1p 3 [SwitchA-Ten-GigabitEthernet1/0/8] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/0/8] quit [SwitchA] interface ten-gigabitethernet 2/0/5 [SwitchA-Ten-GigabitEthernet2/0/5] priority-flow-control enable [SwitchA-Ten-GigabitEthernet2/0/5] priority-flow-control no-drop dot1p 3 [SwitchA-Ten-GigabitEthernet2/0/5] qos trust dot1p [SwitchA-Ten-GigabitEthernet2/0/5] quit [SwitchA] interface ten-gigabitethernet 2/0/6 [SwitchA-Ten-GigabitEthernet2/0/6] priority-flow-control enable [SwitchA-Ten-GigabitEthernet2/0/6] priority-flow-control no-drop dot1p 3 [SwitchA-Ten-GigabitEthernet2/0/6] qos trust dot1p...
Page 157 [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr be group 1 byte-count 1 # Assign the other queues to the SP group on interface Ten-GigabitEthernet 1/0/1. [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af2 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af3 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr af4 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr ef group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr cs6 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr cs7 group sp [SwitchA-Ten-GigabitEthernet1/0/1] quit...
Page 158 Non-disruptive reconfiguration or isolating the switch may be performed. Continue? [Y/N]:y # Enable FSPF in VSAN 200. [SwitchA-vsan200] fspf enable [SwitchA-vsan200] quit # Create interface VFC 1. [SwitchA] interface vfc 1 # Configure the mode of VFC 1 as F. [SwitchA-Vfc1] fc mode f # Bind VFC 1 to interface Ten-GigabitEthernet 1/0/1.
Page 159 [SwitchA-Vfc11] quit # Enable FCoE for VLAN 4001 and map VLAN 4001 to VSAN 100. [SwitchA] vlan 4001 [SwitchA-vlan4001] fcoe enable vsan 100 [SwitchA-vlan4001] quit # Enable FCoE for VLAN 4002, and map VLAN 4002 to VSAN 200. [SwitchA] vlan 4002 [SwitchA-vlan4002] fcoe enable vsan 200 [SwitchA-vlan4002] quit # Enter the view of VSAN 100, and configure the members in the default zone to access each...
Page 160 [SwitchC-vlan4001] description ToSAN_A [SwitchC-vlan4001] quit # Configure interface Ten-GigabitEthernet 1/0/1 as a hybrid port. [SwitchC] interface ten-gigabitethernet 1/0/1 [SwitchC-Ten-GigabitEthernet1/0/1] port link-type hybrid # Assign Ten-GigabitEthernet 1/0/1 to VLAN 4001 as a tagged member. [SwitchC-Ten-GigabitEthernet1/0/1] port hybrid vlan 4001 tagged [SwitchC-Ten-GigabitEthernet1/0/1] quit # Create Layer 2 aggregate interface 1, and configure it to operate in dynamic aggregation mode.
Page 161 [SwitchC-classifier-DCBX] if-match acl 4000 [SwitchC-classifier-DCBX] quit # Create a behavior named DCBX. [SwitchC] traffic behavior DCBX # Configure the behavior to mark packets with 802.1p priority value 3. [SwitchC-behavior-DCBX] remark dot1p 3 [SwitchC-behavior-DCBX] quit # Create a QoS policy named DCBX. [SwitchC] qos policy DCBX # Associate class DCBX with traffic behavior DCBX in the QoS policy, and specify that the association apply to DCBX.
Page 162 [SwitchC-Ten-GigabitEthernet1/0/7] quit [SwitchC] interface ten-gigabitethernet 1/0/8 [SwitchC-Ten-GigabitEthernet1/0/8] priority-flow-control enable [SwitchC-Ten-GigabitEthernet1/0/8] priority-flow-control no-drop dot1p 3 [SwitchC-Ten-GigabitEthernet1/0/8] qos trust dot1p [SwitchC-Ten-GigabitEthernet1/0/8] quit Configure FCoE: # Configure the switch to operate in FCF mode. [SwitchC] fcoe-mode fcf # Enable the fabric configuration feature in VSAN 100. By default, the fabric configuration feature is enabled.
Page 163: Verifying The Configuration
[SwitchC-vlan4001] quit # Enter the view of VSAN 100, and configure the members in the default zone to access each other. [SwitchC] vsan 100 [SwitchC-vsan100] zone default-zone permit [SwitchC-vsan100] quit Configuring Switch D Configure Switch D in a similar way Switch C is configured, with the following differences: The VLAN, VSAN, and Layer 2 aggregate interface configured on Switch C are VLAN 4001, VSAN •...
Page 164 0x01(1) 48:33:43:2d:46:43:1C:1C [Principal] 0x02(2) 48:33:43:2d:46:43:1A:1A [Local] The output shows that Switch C is selected as the principal switch, and the principal switch assigns domain ID 1 to itself. # Display the routing table information for VSAN 100. [SwitchA] display fc routing-table vsan 100 Routing Table: VSAN 100 Destinations : 5 Routes : 5...
Page 165 Upstream Vfc11 The output shows that the domain configuration is complete on Switch A, and the principal switch assigns domain ID 2 to Switch A. # Display the domain list of VSAN 200. [SwitchA] display fc domain-list vsan 200 Domain list of VSAN 200: Number of domains: 2 Domain ID 0x01(1)
Page 166: Appendixes
Appendixes Appendix A Fabric address assignment Table 10 Fabric address assignment FC_ID Description Undefined (when an N_Port uses FLOGI to request for an address, an 0x000000 all-zero FC ID is used). 0x000001–0x00FFFF Reserved. 0x010000–0xEFFFFF N_Port address. 0xF00000–0xFFF9FF Reserved. 0xFFFA00–0xFFFA0F Reserved for internal loopback. 0xFFFA10–0xFFFA1F Reserved for external loopback.
Page 167 FC_ID Description 0xFFFFF9 Reserved. 0xFFFFFA Management services. 0xFFFFFB Time services. 0xFFFFFC Path services (name services).
Page 168: Support And Other 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. •...
Page 169: Conventions
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 170 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.
Page 171: Index
Index fabric statically, accessing FC zone access control, calculating activating FC FSPF SPF calculation (shortest interval), FC zone set, configuring active allowed domain ID list, FC zone database active zone set, fabric building (dynamic), address fabric building configuration (static), fabric FC address assignment, fabric configuration, fabric N_Port-WWN to FC address binding, fabric reconfiguration,...
Page 172 FIP snooping, 102, 104, FCoE configuration (VFC interface)(IRF mode), FIP snooping Ethernet interface operating FCoE configuration (VFC interface)(standalone mode, mode), FSPF (VFC interface), FCoE for VLAN enable, NPV, 93, 94, FCoE overview, NPV downlink interface, 95, FCoE switch mode configuration, NPV downlink-uplink interface mapping, FCoE VFC interface, NPV uplink interface, 95,...
Page 173 allowed domain ID list, Fibre Channel over Ethernet. Use FCoE fabric domain ID assignment, FIP snooping Ethernet interface operating mode, fabric switch domain ID, NPV configuration, 93, 94, downlink RSCN aggregation, FCoE downlink-uplink interface mapping, VSAN configuration, 26, NPV downlink interface configuration, 95, NPV downlink-uplink interface mapping, dynamic fabric...
Page 174 forwarding maintain, fabric building configuration (static), frame transmission over Ethernet, fabric configuration, merge control mode setting, fabric configuration enable/disable, mode feature support, fabric display, overview, fabric domain ID assignment, Pairwise configuration, fabric FC address assignment, routing display, fabric mode, routing maintain, fabric N_Port-WWN to FC address binding, switch operation, fabric name,...
Page 175 FC protocol, FIP, FC routing configuration, 52, FIP operation, FC routing display, FIP snooping configuration, 102, 104, FC routing maintain, FIP snooping Ethernet interface operating mode, FC routing table, FIP snooping FC-MAP value, FC SAN, FKA advertisement interval value, FC static route configuration, frames, FC static route configuration restrictions, FSPF configuration (VFC interface),...
Page 176 well-known fabric addresses, FC FSPF LSDB, WWN, FC FSPF LSR, FC FSPF LSU packet type, configuration, 109, 1 12 FC FSPF routes, topology discovery, 1 12 GR configuration, FDMI GR helper configuration, configuration, 1 16 GR restarter configuration, display, 1 17 how it works, interface cost, FC FIB table,...
Page 177 FCoE fabric dynamic, FCoE fabric static, link FCoE feature support, FC configuration, FCoE non-FCoE, FC FSPF interface LSR retransmission interval, FCoE port, FC FSPF LSA packet type, 55, FCoE switch mode configuration, FC FSPF LSDB, FCoE transit, 9, FC FSPF LSR, FCoE VFC interface E, FC FSPF LSR arrival interval min, FCoE VFC interface F,...
Page 178 FC FSPF interface disable, FCoE VSAN, FC FSPF interface hello interval, FCoE well-known fabric addresses, FC FSPF interface LSR retransmission interval, FCS topology discovery, 1 12 FC FSPF LSR arrival interval min, NPV disruptive load balancing, 94, FC FSPF LSR refresh interval min, NPV downlink, FC FSPF routes, NPV downlink interface, 93, 95,...
Page 179 non-FCoE mode (FCoE), fabric switch priority, notifying FCF priority, FCoE VSAN fabric SNMP notifications, FCoE FCF system priority, FCoE FCF VFC interface priority, configuration, 93, 94, procedure display, activating FC zone set, disruptive load balancing, building fabric, disruptive load balancing process initiation, building fabric dynamically, downlink, building fabric statically,...
Page 180 configuring NPV, 94, maintaining FC forwarding, configuring NPV downlink interface, 95, maintaining FC routing, configuring NPV downlink-uplink interface maintaining FC zones, mapping, maintaining VFC interfaces, configuring NPV uplink interface, 95, mapping FCoE VLAN-VSAN, configuring RSCN aggregation, renaming FC zone aliases, configuring trunk VSAN, renaming FC zone sets, configuring VFC interface, 15,...
Page 181 renaming aggregation configuration, FC zone aliases, rule FC zone sets, FCFC zone merge rules, FC zones, FIP snooping establishment, resource FC resource allocation timeout timer, restrictions fabric building, 32, FC static route configuration, fabric building configuration (dynamic), FCoE VLAN-VSAN mapping, fabric building configuration (static), routing fabric configuration,...
Page 182 trunk VSAN in FCoE network, allowed domain ID list, VSAN configuration, 26, fabric switch domain ID, VSAN creation, FC zone distribution (basic zoning), SCSI-FCP information autodiscovery, FC zone distribution (enhanced zoning), selecting switching fabric principal switch, fabric building, 32, setting fabric building configuration (dynamic), fabric name, fabric building configuration (static),...
Page 183 FC interface FIB table entry, virtualizing FC interface routing table entry, fabric building, 32, FC mask FIB table entry, fabric building configuration (dynamic), FC mask routing table entry, fabric building configuration (static), FC preference routing table entry, fabric configuration, FC routing table, FC configuration, 13, timer FC overview,...
Page 184 FC FSPF LSR refresh interval min, fundamentals, FC overview, NPV configuration, 93, 94, FC ping configuration, 1 18 trunk VSAN configuration, FC routing configuration, 52, trunk VSAN in FC network, FC SAN, trunk VSAN in FCoE network, FC static routing configuration (VFC zone database, interface), zone SNMP notifications,...
Page 185 FCmerge rules, zoning mode basic zoning, configuration, enhanced zoning,...

HP FlexFabric 5700 Series Configuration Manual

Quick Links

Configuration Guide

Related Manuals for HP FlexFabric 5700 Series

Summary of Contents for HP FlexFabric 5700 Series

Table of Contents