1. Manuals
  2. Brands
  3. HPE Manuals
  4. Switch
  5. FlexNetwork 10500 SERIES
  6. Configuration manual

HPE FlexNetwork 10500 Series Configuration Manual

Hide thumbs Also See for FlexNetwork 10500 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Configuration Manual
HPE FlexNetwork 10500 Switch Series
FCoE Configuration Guide
Part number: 5200-1885a
Software version: 10500-CMW710-R7557P01
Document version: 6W101-20171020

Advertisement

Table of Contents
loading

Related Manuals for HPE FlexNetwork 10500 Series

Summary of Contents for HPE FlexNetwork 10500 Series

  • Page 1 HPE FlexNetwork 10500 Switch Series FCoE Configuration Guide Part number: 5200-1885a Software version: 10500-CMW710-R7557P01 Document version: 6W101-20171020...
  • Page 2 © Copyright 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • 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 FCoE ·································································································································································· 5 Basic concepts ··········································································································································· 6 How FCoE works ······································································································································· 7 FCoE modes ······················································································································································...
  • Page 4 FC address assignment ··························································································································· 34 Fabric building configuration task list ··············································································································· 34 Building a fabric statically ························································································································· 34 Building a fabric dynamically ···················································································································· 35 Enabling or disabling the fabric configuration feature ······················································································ 35 Setting a fabric name ······································································································································· 36 Setting the switch priority ································································································································· 36 Configuring the allowed domain ID list ·············································································································...
  • Page 5 Zoning mode ············································································································································ 73 Zone database ········································································································································· 73 Pairwise ···················································································································································· 76 Zone distribution in basic zoning mode ···································································································· 76 Zone distribution in enhanced zoning mode ···························································································· 78 Zone merge in basic zoning mode ··········································································································· 79 Zone merge in enhanced zoning mode···································································································· 81 Access control ··········································································································································...
  • Page 6 Displaying and maintaining FIP snooping ······································································································ 107 FIP snooping configuration example ·············································································································· 107 Network requirements ···························································································································· 107 Configuration procedure ························································································································· 107 Verifying the configuration ······················································································································ 109 Configuring FCS ························································································ 110 Overview ························································································································································ 110 Starting a topology discovery ························································································································· 112 Stopping a topology discovery ······················································································································· 113 Displaying and maintaining FCS ····················································································································...
  • Page 7 Websites ················································································································································ 166 Customer self repair ······························································································································· 166 Remote support ······································································································································ 166 Documentation feedback ······················································································································· 166 Index ·········································································································· 168...

  • Page 8: Fcoe Overview

    FCoE overview 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. A SAN enables the universal connectivity of servers and disk devices. Compared to the conventional client/server computer system, a SAN delivers the following benefits: •...

  • 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

    Communication flow FC switches provide data transmission services. Through FC switches, a server sends instructions and data to disk devices and reads data from disk devices. Figure 4 FC SAN communication model Fabric FC switch FC switch Disk Server The following takes a server accessing a disk device as an example to see how data communication occurs in an FC SAN.

  • Page 12: Fc Zone

    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. This creates data security risks.

  • Page 13: Basic Concepts

    Basic concepts As shown in Figure 6, the link between the FCF switch and the ENode can receive and send both Ethernet frames and FC frames. ENodes can transport FC over Ethernet. ENodes include servers and disk devices. Figure 6 FCoE network diagram Ethernet FCF switch switch...

  • Page 14: How Fcoe Works

    For a node, this field is the fabric provided MAC address (FPMA) of the node. As shown in  Figure 7, an FPMA contains the following elements: − The FC-MAP as the 24 most significant bits. − The FC ID of the VN interface as the 24 least significant bits. The FC-MAP takes the value of the switch FC-MAP, 0x0efc00 by default and configurable by using the fcoe fcmap command.
  • Page 15 • Unsolicited Discovery Advertisement—Periodically sent to advertise the presence of a virtual link or maintain an existing virtual link. The following example shows how a virtual link is established between an FCF switch and an ENode. Figure 9 FIP operation ENode (1) Send Discovery Solicitation Learn FCoE MAC address...

  • Page 16: Fcoe Modes

    The FCF switch also periodically sends unsolicited Discovery Advertisements to maintain established virtual links. If the ENode fails to receive an unsolicited Discovery Advertisement within a period 2.5 times the FKA advertisement interval, it deletes the virtual link. FCoE modes The switch supports the following FCoE modes: •...

  • Page 17: Npv Mode

    Figure 10 FCF network diagram Ethernet FCF switch switch Ethernet VFC interface interface Ethernet interface VFC interface FCF switch VFC interface VN interface Ethernet FCoE Server In an FCoE environment as shown in Figure 10, FCF switches communicate with the ENode over a lossless Ethernet network.

  • Page 18: Transit Mode

    Transit mode FCoE supports FC SANs built on lossless Ethernet networks, and allows Transit switches to be added between FCF switches and ENodes. Figure 12 shows a scenario where ENodes are connected to FCF switches through a Transit switch. Figure 12 Transit network diagram FCF switch ENode mode...

  • Page 19: Protocols And Standards

    The primary responsibilities of Transit switches are filtering and forwarding FCoE protocol packets. They can recognize and control FCoE packets as compared to standard Ethernet switches. However, they do not provide FCoE traffic processing capabilities as complex as FCF switches or NPV switches.

  • Page 20: Fcoe Configuration Restrictions And Guidelines

    FCoE configuration restrictions and guidelines Only the following interface modules support FCoE: • EC interface modules. • SE interface modules: LSU1CGC2SE0 (JG916A).  LSUM2GP44TSSE0 (JH191A, JH199A).  LSUM2GT48SE0 (JH192A, JH200A).  • SF interface modules. • SG interface modules. Configuring the switch to operate in advanced mode The switch supports FCoE only when it is operating in advanced mode.
  • Page 21 Table 1 FCoE features supported in different FCoE modes 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 the 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 (Optional.) Set the expected bandwidth bandwidth-value (in kbps) is the interface baud rate bandwidth of the interface. divided by 1000. (Optional.) Restore the default settings for the VFC default interface. Bring up the VFC interface. undo shutdown By default, a VFC interface is up.

  • Page 24: Enabling Fcoe

    Enabling FCoE To make the FCoE features operate, you must enable FCoE. FCoE configuration task list Tasks at a glance (Required.) Enabling FCoE for a VLAN and mapping the VLAN to a VSAN (Optional.) Setting the FC-MAP value (Optional.) Setting the FKA advertisement interval value (Optional.) Setting the FCF priority Enabling FCoE for a VLAN and mapping the...

  • Page 25: Setting The Fc-Map Value

    Step Command Remarks 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. Setting the FC-MAP value The FC-MAP value identifies an FCoE network.

  • Page 26: Configuration Procedure

    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 is 90 seconds. In this scenario, a single-MPU FCF switch or NPV switch will experience FCoE traffic disruption during an ISSU reboot because of the following reasons: •...

  • Page 27: Setting The System Fcf Priority

    • VFC interface FCF priority—The VFC interface FCF priority is used in the fcf priority field in an unsolicited Discovery Advertisement. An ENode selects the FCF switch with the highest priority from the FCF switches sending Discovery Advertisements and sends a FLOGI request to the FCF switch for login. The FCF priority takes effect only on a VFC interface connected to an ENode (VFC interface operating in F mode).

  • Page 28: Configuration Procedure

    Figure 15 Network diagram FCF switch Ethernet VFC 2 Switch B switch XGE1/0/2 VFC 2 XGE1/0/3 XGE1/0/2 FCF switch Switch A VFC 1 XGE1/0/1 Ethernet FCoE Server Configuration procedure Configure Switch A: a. Configure the switch to operate in advanced mode, save the configuration, and reboot the switch.
  • Page 29 # Configure interface Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the interface to VLAN 20. [SwitchA] interface ten-gigabitethernet 1/0/2 [SwitchA-Ten-GigabitEthernet1/0/2] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/2] port trunk permit vlan 20 [SwitchA-Ten-GigabitEthernet1/0/2] quit # Configure interface Ten-GigabitEthernet 1/0/3 as a trunk port, and assign the interface to VLAN 10.
  • Page 30 # Configure the interface to trust the 802.1p priority carried in incoming packets. [SwitchA-Ten-GigabitEthernet1/0/1] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/0/1] quit # Forcibly enable PFC on interface Ten-GigabitEthernet 1/0/2. [SwitchA] interface ten-gigabitethernet 1/0/2 [SwitchA-Ten-GigabitEthernet1/0/2] priority-flow-control enable # Enable PFC for 802.1p priority 3 on the interface. [SwitchA-Ten-GigabitEthernet1/0/2] priority-flow-control no-drop dot1p 3 # Configure the interface to trust the 802.1p priority carried in incoming packets.
  • Page 31 # Create interface VFC 2, and configure the mode of VFC 2 as E. [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode e # Bind VFC 2 to interface Ten-GigabitEthernet 1/0/2, and assign VFC 2 to VSAN 10 as a trunk port. [SwitchA-Vfc2] bind interface ten-gigabitethernet 1/0/2 [SwitchA-Vfc2] port trunk vsan 10 [SwitchA-Vfc2] quit...
  • Page 32 [SwitchB-Ten-GigabitEthernet1/0/2] quit d. Configure FCoE: # Configure the switch to operate in FCF mode and create VSAN 10. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 10 [SwitchB-vsan10] quit # Create interface VFC 2, and configure the mode of VFC 2 as E. [SwitchB] interface vfc 2 [SwitchB-Vfc2] fc mode e # Bind VFC 2 to interface Ten-GigabitEthernet 1/0/2, and assign VFC 2 to VSAN 10 as a...

  • 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: •...

  • Page 34: Creating A Vsan

    Figure 16 Trunk VSAN network VSAN 1 VSAN 1 N_Port N_Port Disk A Server A FC Fabric F_Port F_Port E_Port E_Port F_Port F_Port FC switch B FC switch A Server B Disk B N_Port N_Port VSAN 2 VSAN 2 During the transmission process, VFT_Headers are added to and removed from the frames. A switch can use the same physical interface to support multiple VSANs.

  • Page 35: Displaying And Maintaining Vsans

    To assign a VFC interface to the specified VSANs as a trunk port: Step Command Remarks Enter system view. system-view Enter VFC interface view. interface vfc interface-number Assign the VFC interface to By default, a VFC interface does not the specified VSANs as a belong to any VSAN (including trunk port so that the VSAN 1) as a trunk port.
  • Page 36 Configure Switch A: # Configure the switch to operate in advanced mode, save the configuration, and reboot the switch. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] system-working-mode advance 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 37: Verifying The Configuration

    # Create interface VFC 4. [SwitchA] interface vfc 4 # Configure the mode of VFC 4 as E. [SwitchA-Vfc4] fc mode e # Bind VFC 4 to interface Ten-GigabitEthernet 1/0/4. [SwitchA-Vfc4] bind interface ten-gigabitethernet 1/0/4 # Assign VFC 4 to VSANs 10 and 20 as a trunk port. [SwitchA-Vfc4] port trunk vsan 10 20 [SwitchA-Vfc4] quit # Configure Ten-GigabitEthernet 1/0/4 as a trunk port, and assign the port to VLANs 10 and 20.
  • Page 38 Access Ports: Trunk Ports: Vfc2 Vfc4...

  • 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. You can build a fabric through one of the following modes: •...

  • Page 40: Domain Id Assignment

    The priority carried in the packet is higher.  The priority in the packet is the same and the WWN is smaller.  Finally, all switches in the network make an agreement on the principal switch. When the PSST times out, if the locally-recorded principal switch information is the local switch, the switch becomes the principal switch.

  • Page 41: Fc Address Assignment

    − The principal switch notifies the downstream switch that no domain ID can be assigned. For more information about domain ID types, see "Configuring a domain ID for a switch." Otherwise, the downstream switch performs the following operations:  − Accepts the domain ID assigned by the principal switch and records it in a hidden file.

  • Page 42: Building A Fabric Dynamically

    Tasks at a glance Remarks (Optional.) Configuring the allowed domain ID list When statically building a fabric, you must (Required.) Configuring a domain ID for a switch manually configure a domain ID for each switch. (Optional.) Configuring the persistent FC ID feature (Optional.) Setting the maximum number of logged-in nodes (Optional.)

  • Page 43: Setting A Fabric Name

    • To statically build a fabric, you must disable the fabric configuration feature on switches and manually configure domain IDs for the switches. To enable or disable the fabric configuration feature: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id •...

  • Page 44: Configuring The Allowed Domain Id List

    To set the switch priority: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Set the switch priority in the VSAN. priority value The default setting is 128. Configuring the allowed domain ID list Configuring the allowed domain ID list has an effect on switches as follows: •...

  • Page 45: Configuring The Persistent Fc Id Feature

    As a best practice, configure domain IDs of the same type for all switches in a VSAN. To configure a domain ID for a switch: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Configure a domain ID for domain-id domain-id { preferred By default, the domain ID of a switch the switch.

  • Page 46: Setting Fabric Timers

    Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Set the maximum number of By default, no maximum number logged-in nodes allowed in the fc login-limit max-number is configured. VSAN. Setting fabric timers The fabric operation involves the following timers: •...

  • Page 47: Configuring The Fabric Reconfiguration Feature

    Step Command Remarks Set the resource The default setting is 10000 allocation timeout period timer resource-allocation value milliseconds. for the VSAN. Configuring the fabric reconfiguration feature IMPORTANT: The fabric reconfiguration feature takes effects only when the fabric configuration feature is enabled. The fabric reconfiguration occurs in one of the following situations: •...

  • Page 48: Manually Initiating A Fabric Reconfiguration

    Step Command Remarks Enable the automatic By default, the automatic fabric fabric reconfiguration domain auto-reconfigure enable reconfiguration feature is disabled. feature. Manually initiating a fabric reconfiguration Step Command Enter system view. system-view Enter VSAN view. vsan vsan-id Manually initiate a fabric reconfiguration. domain restart [ disruptive ] Configuring a VFC interface to reject incoming RCF requests...

  • Page 49: Configuring Rscn Aggregation

    Configuring RSCN aggregation RSCN An FCF switch uses a name service database to store information about registered nodes on the local switch and on remote switches in the fabric. The switch sends Registered State Change Notifications (RSCNs) to inform node information changes (node registration, node deregistration, or registration information change).

  • Page 50: Configuring And Obtaining Fc4 Information Of Nodes

    Configuring and obtaining FC4 information of nodes After a node registers with a switch through a FLOGI, the node sends a name service registration request to the switch to register extended information, including FC4 information. FC4 information includes the following fields to describe the FC4-layer protocol supported by a node and the feature of the supported protocol.

  • Page 51: Configuring Smart San

    The switch replaces the default FC4 information with the registered FC4 information or obtained SCSI-FCP information when any of the following events occur: • A node registers FC4 information. • The switch obtains the SCSI-FCP information. The fc wwn default-fc4-type command can configure only one combination of FC4-Type and Feature at a time.

  • Page 52: Displaying And Maintaining A Fabric

    Step Command Remarks Enter system view. system-view smartsan enable [ fcoe | Enable Smart SAN. By default, Smart SAN is disabled. iscsi ] The default setting is 30 minutes. Set the interval for sending rdp request-polling-interval This command can be used only after RDP request packets.
  • Page 53 Figure 19 Network diagram VFC 1 VFC 2 VFC 2 VFC 1 XGE1/0/1 XGE1/0/2 XGE1/0/2 XGE1/0/1 Server Switch A Switch B Disk Configuration procedure This section describes only the fabric building configurations. Configure Switch A: # Configure the switch to operate in advanced mode, save the configuration, and reboot the switch.
  • Page 54 [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode e # Bind VFC 2 to interface Ten-GigabitEthernet 1/0/2, and assign VFC 2 to VSAN 1 as a trunk port. [SwitchA-Vfc2] bind interface ten-gigabitethernet1/0/2 [SwitchA-Vfc2] port trunk vsan 1 [SwitchA-Vfc2] quit # Configure Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 20. [SwitchA] vlan 20 [SwitchA-Vlan20] quit [SwitchA] interface ten-gigabitethernet1/0/2...
  • Page 55 # Create interface VFC 1, and configure it to operate in F mode. [SwitchB] interface vfc 1 [SwitchB-Vfc1] fc mode f # Bind VFC 1 to interface Ten-GigabitEthernet 1/0/1, and assign it to VSAN 1 as a trunk port. [SwitchB-Vfc1] bind interface ten-gigabitethernet1/0/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 20.

  • Page 56: Dynamic Fabric Building Configuration Example

    Domain ID: 1 Configuration information: Domain configure: Disabled Domain auto-reconfigure: Disabled Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 1 (static) Principal switch running time information: Priority: 128 No interfaces available. The output shows that the domain configuration is complete and that the runtime domain ID of Switch A is 1.
  • Page 57 Figure 20 Network diagram Switch A VFC 2 VFC 1 XGE1/0/2 XGE1/0/1 VFC 2 VFC 1 XGE1/0/2 XGE1/0/1 VFC 3 VFC 3 VFC 2 VFC 1 VFC 1 XGE1/0/3 XGE1/0/3 XGE1/0/2 XGE1/0/1 XGE1/0/1 VFC 2 XGE1/0/2 Switch B Disk Switch C Switch D Server Configuration procedure...
  • Page 58 # Create interface VFC 1, and bind it to interface Ten-GigabitEthernet 1/0/1. [SwitchA] interface Vfc 1 [SwitchA-Vfc1] bind interface ten-gigabitethernet1/0/1 # Configure VFC 1 to operate in E mode, and assign it to VSAN 1 as a trunk port. [SwitchA-Vfc1] fc mode e [SwitchA-Vfc1] port trunk vsan 1 [SwitchA-Vfc1] quit # Permit members in the default zone to access each other.
  • Page 59 [SwitchB-Vfc2] fc mode e [SwitchB-Vfc2] port trunk vsan 1 [SwitchB-Vfc2] quit # Create interface VFC 3, and bind it to interface Ten-GigabitEthernet 1/0/3. [SwitchB] interface Vfc 3 [SwitchB-Vfc3] bind interface ten-gigabitethernet1/0/3 # Configure VFC 3 to operate in E mode, and assign it to VSAN 1 as a trunk port. [SwitchB-Vfc3] fc mode e [SwitchB-Vfc3] port trunk vsan 1 [SwitchB-Vfc3] quit...
  • Page 60 [SwitchC-Vfc1] quit # Create interface VFC 2, and bind it to interface Ten-GigabitEthernet 1/0/2. [SwitchC] interface Vfc 2 [SwitchC-Vfc2] bind interface ten-gigabitethernet1/0/2 # Configure VFC 2 to operate in E mode, and assign it to VSAN 1 as a trunk port. [SwitchC-Vfc2] fc mode e [SwitchC-Vfc2] port trunk vsan 1 [SwitchC-Vfc2] quit...
  • Page 61 [SwitchD] interface Vfc 1 [SwitchD-Vfc1] bind interface ten-gigabitethernet1/0/1 # Configure VFC 1 to operate in F mode, and assign it to VSAN 1 as a trunk port. [SwitchD-Vfc1] fc mode f [SwitchD-Vfc1] port trunk vsan 1 [SwitchD-Vfc1] quit # Create interface VFC 2, and bind it to interface Ten-GigabitEthernet 1/0/2. [SwitchD] interface Vfc 2 [SwitchD-Vfc2] bind interface ten-gigabitethernet1/0/2 # Configure VFC 2 to operate in E mode, and assign it to VSAN 1 as a trunk port.
  • Page 62 Domain list of VSAN 1: Number of domains: 4 Domain ID 0x01(5) 48:33:43:2d:46:43:1B:1B [Principal] 0x0b(11) 48:33:43:2d:46:43:1A:1A [Local] 0x0d(13) 48:33:43:2d:46:43:1C:1C 0x0e(14) 48:33:43:2d:46:43:1D:1D The output shows that Switch B becomes the principal switch and assigns a random domain ID (ID 5) to itself.

  • Page 63: 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. •...

  • Page 64: Direct Routes

    • Preference—There might be direct routes, static routes, and FSPF routes to the same destination. All of these types of routes are assigned preferences. Direct routes have a preference of 0, static routes have a preference of 10, and FSPF routes have a preference of 20. The optimal route is the one with the highest priority (smallest preference value).

  • Page 65: Static Routes

    Static routes Static routes are manually configured by the administrator. After you configure a static route, an FC frame to a destination is forwarded along the specified path. In a simple network, static routes are enough for implementing network connectivity. By correctly setting up and using static routes, you can improve network performance and guarantee bandwidth for critical network applications.

  • Page 66: Configuring Static Fc Routes

    • Link state update (LSU)—Advertises local link state information in LSRs to the neighboring switches. • Link state acknowledgment (LSA)—Acknowledges the received LSR. After receiving an LSU, a switch needs to acknowledge its LSR with an LSA. Otherwise, the neighboring switch retransmits the LSR. How FSPF works FSPF works as follows: The switch periodically sends hello packets to establish neighbor relationships with other...

  • Page 67: Configuring Fspf

    Configuring FSPF FSPF is enabled by default. Typically, you do not need to perform special operations. You can change FSPF parameters on a per-VSAN or per-interface basis. FSPF configuration task list Tasks at a glance Remarks Change FSPF parameters in VSAN view •...

  • Page 68: Setting The Minimum Lsr Arrival Interval

    Step Command Remarks Enter VSAN view. vsan vsan-id Set the shortest SPF fspf spf-hold-time value The default setting is 0 seconds. calculation interval. Setting the minimum LSR arrival interval The minimum LSR arrival interval specifies the interval between received LSR updates in a VSAN. Any LSR updates that arrive before this interval expires are dropped.

  • Page 69: Setting The Hello Interval For An Interface

    Setting the hello interval for an interface The hello interval specifies the time between the hello packets sent periodically by the switch to discover and maintain neighbor relationships. NOTE: The set hello interval must be smaller than the dead interval and must be the same at the two ends of the link.

  • Page 70: Disabling Fspf For An Interface

    Step Command Remarks Set the LSR retransmission fspf retransmit-interval interval for the interface in a The default setting is 5 seconds. interval vsan vsan-id VSAN. Disabling FSPF for an interface With FSPF enabled, an interface can participate in SPF calculation. To avoid SPF calculations on an interface, disable FSPF on the interface.

  • Page 71: Displaying And Maintaining Fc Routing And Forwarding

    Displaying and maintaining FC routing and forwarding Execute display commands in any view and reset commands in user view. Task Command display fc routing-table [ vsan vsan-id ] [ statistics | verbose ] Display FC routing table information. display fc routing-table vsan vsan-id fc-id [ mask | mask-length ] [ verbose ] Display FC FIB table information.
  • Page 72 Figure 21 Network diagram Switch B Domain ID: 2 VFC1 VFC2 XGE1/0/1 XGE1/0/2 VFC1 VFC2 XGE1/0/1 XGE1/0/2 Switch A Switch C Domain ID: 1 Domain ID: 3 Configuration procedure Configure Switch A: # Configure the switch to operate in advanced mode, save the configuration, and reboot the switch.
  • Page 73 [SwitchA-Ten-GigabitEthernet1/0/1] port trunk permit vlan 10 [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 two static routes. [SwitchA] vsan 1 [SwitchA-vsan1] fc route-static 020000 8 vfc 1 [SwitchA-vsan1] fc route-static 030000 8 vfc 1 Configure Switch B # Configure the switch to operate in advanced mode, save the configuration, and reboot the...
  • Page 74 [SwitchB-Vfc2] fc mode e # Bind VFC 2 to interface Ten-GigabitEthernet 1/0/2. [SwitchB-Vfc2] bind interface ten-gigabitethernet 1/0/2 # Assign VFC 2 to VSAN 1 as a trunk port. [SwitchB-Vfc2] port trunk vsan 1 [SwitchB-Vfc2] quit # Configure Ten-GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 10. [SwitchB] interface ten-gigabitethernet 1/0/2 [SwitchB-Ten-GigabitEthernet1/0/2] port link-type trunk [SwitchB-Ten-GigabitEthernet1/0/2] port trunk permit vlan 10...
  • Page 75 [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 76: Fspf Configuration Example

    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 77 [SwitchA-vsan2] domain-id 1 static # Enable FSPF. [SwitchA-vsan2] fspf enable [SwitchA-vsan2] quit # Create interface VFC 1. [SwitchA] interface vfc 1 # Configure the mode of VFC 1 as E. [SwitchA-Vfc1] fc mode e # Bind VFC 1 to interface Ten-GigabitEthernet 1/0/1. [SwitchA-Vfc1] bind interface ten-gigabitethernet 1/0/1 # Assign VFC 1 to VSAN 2 as a trunk port.
  • Page 78 [SwitchB-vsan2] quit # Create interface VFC 1. [SwitchB] interface vfc 1 # Configure the mode of VFC 1 as E. [SwitchB-Vfc1] fc mode e # Bind VFC 1 to interface Ten-GigabitEthernet 1/0/1. [SwitchB-Vfc1] bind interface ten-gigabitethernet 1/0/1 # Assign VFC 1 to VSAN 2 as a trunk port. [SwitchB-Vfc1] port trunk vsan 2 [SwitchB-Vfc1] quit # Configure Ten-GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 10.
  • Page 79 --- 0xfffc02 fcping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 0.247/0.430/1.102 ms The output shows that Switch A can reach Switch B.

  • Page 80: 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 81 Figure 23 Zone database structure Zone set Zone Zone Zone Zone Zone Zone Zone Zone Zone member alias member member member Zone Zone Zone member member member 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 WWN (pWWN) or FC address of an N_Port.
  • Page 82 Figure 24 Active and full zone sets Full zone database Full zone database Zone set zs1 Zone set zs2 Zone set zs1 Zone set zs2 Zone A Zone C Zone A Zone C Zone B Zone D Zone B Zone D Zone set zs2 Zone set zs3 Zone set zs3...

  • Page 83: Pairwise

    Peer zone Peer zones are supported only in enhanced zoning mode. You can define a peer zone on a target device by specifying a zone name, the principal member, and peer members. The switch automatically creates the defined peer zone when receiving related packets from the target device.
  • Page 84 Managed switches replace their respective active zone sets or zone databases with the received data, regardless of the distribution types configured on them. If a managed switch receives only the zone database, the managed switch does not retain its active zone set (if present) after replacement. Zone distribution process The manager switch completes data synchronization with each managed switch by using the following packets:...

  • Page 85: Zone Distribution In Enhanced Zoning Mode

    IMPORTANT: For a fabric to be stable, make sure the routes are correctly and consistently configured, and no unreachable routes exist. If the managed switch has been in change authorization state or cannot process the ACA  request, it replies with an RJT (reject) packet. The manager switch starts data synchronization by sending an SFC request only after receiving ACC requests from all managed switches.

  • Page 86: Zone Merge In Basic Zoning Mode

    For both switchover-triggered distribution and zone distribution in enhanced zoning mode, the SFC request carries the zone policy whether or not the SFC request carries the active zone set and zone database. For zone distribution in enhanced zoning mode, the SFC request always carries hard zoning status. For zone distribution caused by a switchover from basic zoning to enhanced zoning, the SFC request carries hard zoning status.
  • Page 87 Figure 26 Zone merge process between two switches Switch A Switch B Switch B checks Switch A initiates a merge 1. MRRA request whether it is capable to Switch B. of accepting the merge. 2. ACC 3. MR request Switch B merges data from switch A with its local 4.

  • Page 88: Zone Merge In Enhanced Zoning Mode

    NOTE: Consistent active zone sets among switches can be achieved by a merge. Consistent zone databases achieved after a merge, however, require all participating switches to be configured with complete merge. Zone merge rules Table 5 Zone merge rules Local database Neighbor database Merge status Merge result...

  • Page 89: Access Control

    • The MR request carries hard zoning status and a merge flag field in addition to the active zone set and zone database. The merge flag field includes the merge control mode and default zone policy. • In the event of a merge failure, the link between participating switches is isolated, and both zone databases remain unchanged.

  • Page 90: 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 (Required.) Configuring the zone distribution and merge type zoning mode. This task can be performed only in (Required.) Configuring a merge control mode enhanced zoning mode.

  • Page 91: Configuring The Pairwise Feature

    Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id • Enable the enhanced zoning mode: zone mode enhanced By default, the basic zoning mode is Configure a zoning mode. • enabled. Enable the basic zoning mode: undo zone mode enhanced Configuring the Pairwise feature This feature allows a zone member to access only members with a different role in the same zone.

  • Page 92: Configuring Zones

    Configuring zones You can specify members of a zone by using their FC addresses, pWWNs, fWWNs, or zone aliases. An fWWN is the WWN of an F_Port. An F_Port member represents all N_Ports that log in through the F_Port. A zone alias represents a group of N_Ports. Any specified N_Port members can be indirectly connected to the switch.

  • Page 93: Configuring The Default Zone Policy

    Step Command Remarks Create a zone set (if the zone set does not exist) zoneset name zoneset-name By default, no zone set exists. and enter its view. Add a zone to the zone By default, no zone exists in a new member zone-name set.

  • Page 94: Configuring A Merge Control Mode

    Configuring a merge control mode Two merge control modes are available: Restrict and Allow. For information about these two modes, "Zone merge in enhanced zoning mode." In enhanced zoning mode, the merge control mode affects the result of a merge operation. Also, a merge operation is allowed only when the merge control mode is the same on both participating switches.

  • Page 95: Configuration Restrictions And Guidelines

    The two methods can work separately and supplement each other. They work together to implement node access control based on the zone configurations. Configuration restrictions and guidelines When you configure hard zoning, follow these restrictions and guidelines: • 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.

  • Page 96: Triggering A Complete Distribution

    Step Command Activate a zone set as the active zone set and zoneset activate name zoneset-name distribute it to the entire fabric. 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.

  • Page 97: 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 98: Displaying And Maintaining Fc Zones

    Displaying and maintaining FC zones Execute display commands in any view and reset commands in user view. Task Command display zone-alias [ [ name zone-alias-name ] vsan Display zone alias information. vsan-id ] display zone [ [ name zone-name ] vsan vsan-id ] Display zone information.

  • Page 99: Requirements Analysis

    Figure 27 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 100 <SwitchA> system-view [SwitchA] fcoe-mode fcf # Enable the enhanced zoning mode in VSAN 1. [SwitchA] vsan 1 [SwitchA-vsan1] zone mode enhanced The zoning database in this switch would be distributed throughout the fabric. Continue? [Y/N]:y [SwitchA-vsan1] # Create a zone alias named Alias1. [SwitchA-vsan1] zone-alias name Alias1 # Add pWWN 22:33:44:55:66:77:88:99 (Disk B) and FC ID 020004 (Disk C) as its target members.

  • Page 101: Verifying The Configuration

    Verifying the configuration Perform all verification tasks on Switch B. # Display zone set information for VSAN 1. <SwitchB> display zoneset vsan 1 VSAN 1: zoneset name Zoneset1 zone name Zone1 fcid 0x010001 zone name Zone2 fcid 0x010002 initiator pwwn 11:22:33:44:55:66:77:88 target zone-alias Alias1 fcid 0x020004 target pwwn 22:33:44:55:66:77:88:99 target...
  • Page 102 *fcid 0x010001 zone name Zone2 *fcid 0x010002 *fcid 0x020004 *fcid 0x020005 [pwwn 22:33:44:55:66:77:88:99] *fcid 0x020006 [pwwn 11:22:33:44:55:66:77:88] zone name Zone3 *fcid 0x010003 *fcid 0x020004 *fcid 0x020005 [pwwn 22:33:44:55:66:77:88:99]...

  • Page 103: 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 28 shows a typical NPV network diagram. Figure 28 NPV network diagram N_Port Node F_Port NP_Port Downlink interface Fabric...

  • Page 104: Downlink-To-Uplink Interface Mappings

    Downlink-to-uplink interface mappings NPV switches automatically map downlink interfaces to uplink interfaces. Before a downlink interface is brought up, the NPV switch maps it to the uplink interface to which the minimum number of downlink interfaces is mapped. Typically, automatic mapping can meet your requirements. When a downlink interface must be connected to a fabric through the specified uplink interfaces, you can manually map the downlink interface to the uplink interfaces.

  • Page 105: Configuring Uplink Interfaces

    Configuring uplink interfaces Step Command Remarks Enter system view. system-view Enter VFC interface interface vfc This VFC interface is connected to the core switch. view. interface-number Set the mode of the fc mode np The default setting is F mode. VFC interface to NP.

  • Page 106: Manually Initiating A Load-Balancing Process

    Manually initiating a load-balancing process CAUTION: This feature redistributes downlink traffic across all uplink interfaces for better load balancing. However, it causes traffic interruption. When traffic is not distributed evenly among interfaces in a VSAN, use this feature to force all nodes in the VSAN to log in again to the core switch.

  • Page 107: Npv Configuration Example

    Task Command 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 108 # Create interface VFC 1. [SwitchA] interface vfc 1 # Bind VFC 1 to interface Ten-GigabitEthernet 1/0/1. [SwitchA-Vfc1] bind interface ten-gigabitethernet 1/0/1 # Assign VFC 1 to VSAN 1 as a trunk port. [SwitchA-Vfc1] port trunk vsan 1 [SwitchA-Vfc1] quit # Configure Ten-GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 10.

  • Page 109: Verifying The Configuration

    [SwitchA-Vfc1] quit [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode f [SwitchA-Vfc2] quit Configure Switch B: # Configure the switch to operate in advanced mode, save the configuration, and reboot the switch. (Skip this step if the switch is operating in advanced mode.) <SwitchB>...
  • Page 110 # Display information about uplink and downlink interfaces on Switch A. [SwitchA] display npv status External Interfaces: Interface: Vfc3 VSAN tagging mode: Tagging VSAN State FCID 0x010000 Number of External Interfaces: 1 Server Interfaces: Interface : Vfc1 VSAN tagging mode: Tagging VSAN State Interface : Vfc2...

  • Page 111: Configuring Fip Snooping

    Configuring FIP snooping Overview To communicate with devices in the FC SAN, a node must register with an FC fabric. An FCF switch has point-to-point connections with nodes. An FCF switch brings up an interface connected to a node only after the node completes fabric login on the interface. In an FCoE implementation, Transit switches can be present between ENodes and FCF switches, so the connections between ENodes and FCF switches are no longer point-to-point.

  • Page 112: Fip Snooping Configuration Task List

    • FIP snooping rules generated on an Ethernet interface operating in ENode mode are called ENode FIP snooping rules. Establishing FIP snooping rules FIP snooping rules are established when a virtual link is established between an ENode and an FCF switch.

  • Page 113: Enabling Fip Snooping

    Tasks at a glance Remarks (Optional.) Setting the FC-MAP value Enabling FIP snooping FIP snooping is enabled on a per-VLAN basis. To enable FIP snooping for a VLAN: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable FIP snooping for By default, FIP snooping is disabled for fip-snooping enable...

  • Page 114: Displaying And Maintaining Fip Snooping

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set an FC-MAP value. fip-snooping fc-map fc-map The default setting is 0x0efc00. Displaying and maintaining FIP snooping Execute display commands in any view. Task Command Display ENode information obtained by a Transit display fip-snooping enode [ vlan vlan-id ] switch.
  • Page 115 The system working mode is changed, please save the configuration and reboot the system to make it effective. [Transit] save [Transit] quit <Transit> reboot # Configure the switch to operate in Transit mode. <Transit> system-view [Transit] fcoe-mode transit # Enable FIP snooping for VLAN 10. [Transit] vlan 10 [Transit-vlan10] fip-snooping enable # Set the FC-MAP value to 0x0EFC01 for VLAN 10.

  • Page 116: Verifying The Configuration

    # Create interface VFC 2. [FCF] interface vfc 2 # Configure the mode of VFC 2 as F. [FCF-vfc2] fc mode f # Assign VFC 2 to VSAN 10. [FCF-vfc2] port trunk vsan 10 # 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.

  • Page 117: 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 118 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 119: Starting A Topology Discovery

    Attribute Description The current speed can only be one of the following options: • 1 Gbps. • 2 Gbps. • 4 Gbps. Port speed operation • 8 Gbps. • 10 Gbps. • 16 Gbps. • 20 Gbps. Port zoning enforcement Zoning type supported by the port: soft zoning or hard zoning.

  • Page 120: Stopping A Topology Discovery

    Stopping a topology discovery Step Command Remarks Enter system view. system-view After you execute this command, the system performs the following operations: • Stops the topology discovery Stop a topology in progress. • discovery in specified fcs discovery stop vsan vsan-list Deletes the topology VSANs.

  • Page 121: Configuration Procedure

    : 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 : HPE#HPE 10508 #Version 7.1.045, Beta 7143 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 Domain ID : 0x03 Management address list : snmp://192.168.0.3 Fabric name : 10:00:00:11:22:00:01:01 Logical name : SwitchC Information list : HPE#HPE 10508 #Version 7.1.045, Beta 7143 IE_Ports: Interface Port WWN Port type Attached port WWNs e3:01:00:11:22:00:01:01 E_Port e1:01:00:11:22:00:01:02 e3:01:00:11:22:00:01:02 E_Port...
  • Page 123 IE WWN: 10:00:00:11:22:00:01:03 Port WWN Port type Tx type Module type e3:01:00:11:22:00:01:01 E_Port 10GBASE-CX4 SFP with serial ID e3:01:00:11:22:00:01:02 E_Port 10GBASE-CX4 SFP with serial ID e3:01:00:11:22:00:01:03 F_Port 10GBASE-CX4 SFP with serial ID Total 3 switch-ports in IE. IE WWN: 10:00:00:11:22:00:01:04 Port WWN Port type Tx type Module type...

  • Page 124: 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 125 Attribute Description Node Symbolic Name Symbolic name of the node where the HBA resides. Hardware Version Hardware version of the HBA. Driver Version Driver version of the HBA. Option ROM Version ROM version of the HBA. Firmware Version Firmware version of the HBA. OS Name and Version Operating system name and version number of the HBA.
  • Page 126 Field Description Speeds supported by the port: • 1 Gbps. • 2 Gbps. • 4 Gbps. • 8 Gbps. • 10 Gbps. • Supported Speed 16 Gbps. • 20 Gbps. • 32 Gbps. • 40 Gbps. This field displays Unknown for speeds other than the preceding ones. This field displays Speed not obtained when the supported speeds cannot be determined.

  • Page 127: Displaying And Maintaining Fdmi

    Field Description Security types supported by the port: • 0x00 (Not Supported). Smart SAN Security • 0x01 (Tier-1). Support • 0x02 (Tier-2). • 0x03 (Tier-3). Smart SAN Connected This field displays ports on remote nodes discovered by the port. Ports Displaying and maintaining FDMI Execute display commands in any view.

  • Page 128: 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 129 # Configure the switch to operate in advanced mode, save the configuration, and reboot the switch. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] system-working-mode advance 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 130: Verifying The Configuration

    system to make it effective. [SwitchB] save [SwitchB] quit <SwitchB> reboot # Configure the switch to operate in FCF mode. <SwitchB> system-view [SwitchB] fcoe-mode fcf # Enable the fabric configuration feature for VSAN 1. [SwitchB] vsan 1 [SwitchB-vsan1] domain configure enable # Set the domain ID to 2.
  • Page 131 --- 0xfffc02 fcping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 9/18/25 ms...

  • Page 132: 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: •...

  • Page 133: Configuration Procedure

    b. After receiving the packet, Switch B replies with an STR ACC packet to Switch A. c. Switch B adds its uplink path information to the received STR packet and sends it to the destination switch, Switch C. d. After receiving the packet, Switch C replies with an STR ACC packet to Switch B. e.
  • Page 134 # Configure the switch to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf # Enable the fabric configuration feature for VSAN 1. [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Set the domain ID to 1. [SwitchA-vsan1] domain-id 1 static # Disable FSPF for VSAN 1.
  • Page 135 [SwitchB] vsan 1 [SwitchB-vsan1] domain configure enable # Set the domain ID to 2. [SwitchB-vsan1] domain-id 2 static # Disable FSPF for VSAN 1. [SwitchB-vsan1] undo fspf enable # Configure a static route. [SwitchB-vsan1] fc route-static 010000 8 vfc 1 [SwitchB-vsan1] quit # Create interface VFC 1.
  • Page 136 The system working mode is changed, please save the configuration and reboot the system to make it effective. [SwitchC] save [SwitchC] quit <SwitchC> reboot # Configure the switch to operate in FCF mode. <SwitchC> system-view [SwitchC] fcoe-mode fcf # Enable the fabric configuration feature for VSAN 1. [SwitchC] vsan 1 [SwitchC-vsan1] domain configure enable # Set the domain ID to 3.

  • Page 137: Verifying The Configuration

    The output shows that Switch A cannot reach Switch C. Use the fctracert command to identify the faulty node. [SwitchA] fctracert fcid fffc03 vsan 1 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.

  • Page 138: 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 139: Requirements Analysis

    Figure 36 Network diagram Ethernet switch XGE1/0/10 XGE1/0/10 Switch A Switch B VFC1 VFC1 FCF switch FCF switch XGE1/0/1 XGE1/0/1 VFC10 VFC10 XGE1/0/5 to XGE1/0/8 XGE1/0/5 to XGE1/0/8 Server VFC10 VFC10 XGE1/0/5 to XGE1/0/8 XGE1/0/5 to XGE1/0/8 Switch C Switch D VFC1 VFC1 FCF switch...

  • Page 140: Configuration Restrictions And Guidelines

    To transmit the storage traffic of VSAN 100 within VLAN 4001, map VLAN 4001 to VSAN 100. To avoid physical loops in the LAN, enable STP on the Ethernet interfaces connecting Switch A and Switch B to the LAN and the server. To prevent STP from blocking the interfaces that are responsible for forwarding storage traffic on Switch A and Switch B, disable STP on the interfaces connecting the four FCF switches.
  • Page 141 # Create VLAN 1001 and 4001, which are intended to transmit Ethernet traffic and storage traffic, respectively. <SwitchA> system-view [SwitchA] vlan 1001 [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.
  • Page 142 [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 Configure DCBX:...
  • Page 143 [SwitchA-Ten-GigabitEthernet1/0/1] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/0/1] quit # Enable PFC by force on Ten-GigabitEthernet 1/0/5. [SwitchA] interface ten-gigabitethernet 1/0/5 [SwitchA-Ten-GigabitEthernet1/0/5] priority-flow-control enable # Enable PFC for 802.1p priority 3 on Ten-GigabitEthernet 1/0/5. [SwitchA-Ten-GigabitEthernet1/0/5] priority-flow-control no-drop dot1p 3 # Configure Ten-GigabitEthernet 1/0/5 to trust the 802.1p priority carried in incoming packets. [SwitchA-Ten-GigabitEthernet1/0/5] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/0/5] quit # Configure interfaces Ten-GigabitEthernet 1/0/6 through Ten-GigabitEthernet 1/0/8 in the...
  • Page 144 [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 0 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 2 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 3 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 4 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 5 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 6 group sp [SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 7 group sp [SwitchA-Ten-GigabitEthernet1/0/1] quit...
  • Page 145 # Enter the view of VSAN 100, and configure the members in the default zone to access each other. [SwitchA] vsan 100 [SwitchA-vsan100] zone default-zone permit [SwitchA-vsan100] quit Configuring Switch B Configure Switch B in the same way Switch A is configured. On Switch B, the Layer 2 aggregate interface is Bridge-Aggregation2.
  • Page 146 # Set the PVID to VLAN 4001 for Ten-GigabitEthernet 1/0/1. [SwitchC-Ten-GigabitEthernet1/0/1] port hybrid pvid vlan 4001 [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 147 [SwitchC-behavior-DCBX] quit # Create a QoS policy named DCBX, associate class DCBX with traffic behavior DCBX in the QoS policy, and specify that the association apply to DCBX. [SwitchC] qos policy 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 148 [SwitchC] fcoe-mode fcf # Enable the fabric configuration feature for 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 149: Verifying The Configurations

    Verifying the configurations Verifying the configuration on Switch A and Switch B Verify the configuration on Switch A and Switch B, for example, Switch A. # Display the domain information of VSAN 100. [SwitchA] display fc domain vsan 100 Domain Information of VSAN 100: Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1A:1A...

  • Page 150: Fcoe Configuration Example (In Irf Mode)

    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. [SwitchA] display fc login vsan 100 Interface VSAN FCID Node WWN Port WWN Vfc1 0x020000 21:01:00:1b:32:a0:fa:12 21:01:00:1b:32:a0:fa:11...

  • Page 151: Requirements Analysis

    Figure 37 Network diagram Ethernet switch XGE1/0/10 XGE2/0/10 Switch A Switch B FCF switch FCF switch VFC10 VFC11 VFC2 VFC1 XGE1/0/5 to XGE1/0/8 XGE2/0/5 to XGE2/0/8 XGE1/0/1 XGE2/0/1 Server VFC10 VFC10 XGE1/0/5 to XGE1/0/8 XGE1/0/5 to XGE1/0/8 Switch C Switch D VFC1 VFC1 FCF switch...

  • Page 152: Configuration Restrictions And Guidelines

    • Configure the interfaces connecting Switch A and Switch C to the SANs to allow VSAN 100. • Configure the interfaces connecting Switch B and Switch D to the SANs to allow VSAN 200. To transmit the storage traffic of VSAN 100 within VLAN 4001, map VLAN 4001 to VSAN 100. To transmit the storage traffic of VSAN 200 within VLAN 4002, map VLAN 4002 to VSAN 200.
  • Page 153 [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. Please wait... Saved the current configuration to mainboard device successfully. Slot 1: Save next configuration file successfully.
  • Page 154 # 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 155 [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 mode.
  • Page 156 [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 [SwitchA-Ten-GigabitEthernet2/0/10] quit # Configure Layer 2 aggregate interface 3 as a trunk port, and assign the aggregate interface to VLAN 1001. [SwitchA] interface bridge-aggregation 3 [SwitchA-Bridge-Aggregation3] port link-type trunk [SwitchA-Bridge-Aggregation3] port trunk permit vlan 1001...
  • Page 157 [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. [SwitchA-Ten-GigabitEthernet2/0/1] qos apply policy DCBX outbound [SwitchA-Ten-GigabitEthernet2/0/1] quit Configure PFC: # Enable PFC in auto mode on Ten-GigabitEthernet 1/0/1. [SwitchA] interface ten-gigabitethernet 1/0/1 [SwitchA-Ten-GigabitEthernet1/0/1] priority-flow-control auto # Enable PFC for 802.1p priority 3 on Ten-GigabitEthernet 1/0/1.
  • Page 158 [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 [SwitchA-Ten-GigabitEthernet2/0/6] quit [SwitchA] interface ten-gigabitethernet 2/0/7 [SwitchA-Ten-GigabitEthernet2/0/7] priority-flow-control enable [SwitchA-Ten-GigabitEthernet2/0/7] priority-flow-control no-drop dot1p 3 [SwitchA-Ten-GigabitEthernet2/0/7] qos trust dot1p [SwitchA-Ten-GigabitEthernet2/0/7] quit [SwitchA] interface ten-gigabitethernet 2/0/8...
  • Page 159 # Configure WRR on interface Ten-GigabitEthernet 2/0/1 as follows: Assign 50% of the interface bandwidth to the FCoE traffic (traffic assigned to queue 1).  Assign 50% of the interface bandwidth to the LAN traffic (traffic assigned to queue 0). ...
  • Page 160 # Create interface VFC 2. [SwitchA] interface vfc 2 # Configure the mode of VFC 2 as F. [SwitchA-Vfc2] fc mode f # Bind VFC 2 to interface Ten-GigabitEthernet 2/0/1. [SwitchA-Vfc2] bind interface ten-gigabitethernet 2/0/1 # Assign VFC 2 to VSAN 200 as a trunk port. [SwitchA-Vfc2] port trunk vsan 200 [SwitchA-Vfc2] quit # Create interface VFC 10.
  • Page 161 [SwitchA-vsan200] zone default-zone permit [SwitchA-vsan200] quit Configuring Switch C Configure the switch to operate in advanced mode, save the configuration, and reboot the switch. (Skip this step if the switch is operating in advanced mode.) <SwitchC> system-view [SwitchC] system-working-mode advance 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 162 [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. [SwitchC] interface ten-gigabitethernet 1/0/5 [SwitchC-Ten-GigabitEthernet1/0/5] port link-aggregation group 1 [SwitchC-Ten-GigabitEthernet1/0/5] quit [SwitchC] interface ten-gigabitethernet 1/0/6 [SwitchC-Ten-GigabitEthernet1/0/6] port link-aggregation group 1 [SwitchC-Ten-GigabitEthernet1/0/6] quit [SwitchC] interface ten-gigabitethernet 1/0/7 [SwitchC-Ten-GigabitEthernet1/0/7] port link-aggregation group 1...
  • Page 163 # Enable LLDP and DCBX TLV advertising on interface Ten-GigabitEthernet 1/0/1. [SwitchC] interface ten-gigabitethernet 1/0/1 [SwitchC-Ten-GigabitEthernet1/0/1] lldp enable [SwitchC-Ten-GigabitEthernet1/0/1] lldp tlv-enable dot1-tlv dcbx # Apply QoS policy DCBX to the outgoing traffic of Ten-GigabitEthernet 1/0/1. [SwitchC-Ten-GigabitEthernet1/0/1] qos apply policy DCBX outbound Configure PFC: # Enable PFC in auto mode on interface Ten-GigabitEthernet 1/0/1.

  • Page 164: Verifying The Configuration

    [SwitchC-vsan100] priority 1 # Set the domain ID to 1. [SwitchC-vsan100] domain-id 1 preferred Non-disruptive reconfiguration or isolating the switch may be performed. Continue? [Y/N]:y # Enable FSPF. [SwitchC-vsan100] fspf enable [SwitchC-vsan100] quit # Create interface VFC 1. [SwitchC] interface vfc 1 # Configure the mode of VFC 1 as F.
  • Page 165 Domain Information of VSAN 100: Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1A:1A Fabric name: 48:33:43:2d:46:43:1C:1C Priority: 128 Domain ID: 2 Configuration information: Domain configure: Enabled Domain auto-reconfigure: Disabled Fabric name: 48:33:43:2d:46:43:1A:1A Priority: 128 Domain ID: 2 (preferred) Principal switch running time information: Priority: 1 Path Interface...
  • Page 166 [SwitchA] display fc name-service database vsan 100 VSAN 100: FCID Type PWWN(vendor) FC4-type:feature 0x010000 0x01(N) 10:00:00:05:30:00:25:a3 SCSI-FCP:Target 0x020000 0x01(N) 21:01:00:1b:32:a0:fa:11 SCSI-FCP:Initiator Display information for VSAN 200: # Display the domain information of VSAN 200. [SwitchA] display fc domain vsan 200 Domain Information of VSAN 200: Running time information: State: Stable...
  • Page 167 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 200. [SwitchA] display fc login vsan 200 Interface VSAN FCID Node WWN Port WWN Vfc1...

  • Page 168: 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.
  • Page 169 FC ID Description 0xfffffc Path services (name services).

  • Page 170: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. 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.

  • Page 171: Network Topology Icons

    Network topology icons Convention Description 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 172: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 173: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
  • Page 174 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 175: Index

    Index FC FSPF SPF calculation (shortest interval), configuring accessing fabric configuration, FC zone access control, fabric reconfiguration, activating fabricconfiguration (dynamic building), FC zone set, fabricconfiguration (static building), active FC default zone policy, FC zone database active zone set, FC FSPF, address FC FSPF GR, fabric FC address assignment,...
  • Page 176 NPV downlink-uplink interface mapping, FCoE VSAN configuration, NPV load balancing configuration (automatic), FCS configuration, 110, 113 FDMI configuration, NPV uplink interface, 97, 98 NPV configuration, 96, 97 Smart SAN, NPV downlink, trunk VSAN, NPV downlink interface, 96, 97, 98 VFC interface, 15, 15 NPV downlink-to-uplink interface mapping, VSAN,...
  • Page 177 FC hard zoning, FC4 node default information, FC4 SCSI-FCP information autodiscovery, FC4 node information, FCoE for VLAN, FC4 SCSI-FCP information autodiscovery, FCoE VSAN fabric SNMP notifications, FCoE building, FCoE VSAN zone SNMP notifications, FCoE fabric address assignment, FIP snooping, FCoE fabric dynamic build, VSAN fabric reconfiguration (automatic), FCoE fabric static build, encapsulating...
  • Page 178 FSPF LSR refresh interval min, FIP snooping mode, FIP snooping rule establishment, FSPF packet types, FSPF routes, priority set, FSPF SPF calculation (shortest interval), priority set (system), 20, 20 FC-MAP hard zoning enable, merge control mode configuration, 87, 87 FCoE FIP snooping FC-MAP value, Pairwise configuration, 84, 84 value setting,...
  • Page 179 FC4 SCSI-FCP information autodiscovery, VSAN configuration, 26, 28 VSAN creation, FCF priority set, FCF priority set (system), VSAN display, FCF priority set (VFC interface), VSAN fabric reconfiguration (automatic), VSAN fabric reconfiguration (manual), FC-MAP value setting, FCS configuration, VSAN fabric SNMP notifications, FCS display, VSAN fundamentals, FCS topology discovery,...
  • Page 180 FCframe transmission over Ethernet, FC FSPF LSR arrival interval min, FIP snooping frame forwarding control, FC FSPF LSR refresh interval min, FSPF FC FSPF SPF calculation (shortest interval), configuration, 60, 69 FCoE FKA advertisement interval value, enable, FC FSPF hello packet type, FCoE configuration (IRF mode), FC FSPF LSA packet type, FC FSPF LSDB,...
  • Page 181 mapping FC FSPF enable, FC FSPF GR configuration, FCoE FC-MAP value, FCoE VLAN > VSAN mapping, FC FSPF interface cost, NPV downlink-to-uplink interface mapping, FC FSPF interface dead interval, NPV downlink-uplink interface mapping, FC FSPF interface disable, mode FC FSPF interface hello interval, fabricconfiguration (dynamic building), FC FSPF interface LSR retransmission interval, fabricconfiguration (static building),...
  • Page 182 FCoEbasic concepts, FCoE VFC interface, FCS topology discovery, 112, 113 FCoE VN interface, NPV downlink, VSAN logged-in nodes max, NPV downlink interface, 96, 97, 98 non-disruptive fabric reconfiguration, NPV downlink-to-uplink interface mapping, non-FCoE mode (FCoE), NPV downlink-uplink interface mapping notifying interface, FCoE VSAN fabric SNMP notifications, NPV load balancing (automatic),...
  • Page 183 trunk VSAN in FC network, configuring NPV, trunk VSAN in FCoE network, configuring NPV downlink interface, 97, 98 priority configuring NPV downlink-uplink interface mapping, fabric switch priority, configuring NPV load balancing configuration FCF priority set, (automatic), FCF priority set (system), configuring NPV uplink interface, 97, 98 FCF priority set (VFC interface),...
  • Page 184 maintaining VFC interfaces, FCoE configuration (VFC interface)(IRF mode), mapping FCoE VLAN > VSAN, FCoE configuration (VFC interface)(standalone renaming FC zone aliases, mode), renaming FC zone sets, FCoE VLAN > VSAN mapping, renaming FC zones, routing setting fabric name, FC default zone policy, setting fabric switch priority, FC direct routes, 56, 57...
  • Page 185 fabricconfiguration (static building), FC fabric timer (VSAN view), FC configuration, FC FSPF interface cost, FC ping configuration, FC FSPF interface dead interval, FC R&F configuration, FC FSPF interface hello interval, FC routing+forwardingconfiguration, FC FSPF interface LSR retransmission interval, FC SAN, FC FSPF LSR arrival interval min, FC tracert configuration, FC FSPF LSR refresh interval min,...
  • Page 186 FC SAN, FCS topology discovery, 112, 113 FC tracert configuration, FDMI configuration, FC VSAN, tracert FC zone alias, FC tracert configuration, FC zone configuration, 73, 82, 91 FCoE FC tracert configuration, FCoE configuration, 13, 20, 131 transit mode (FCoE), 9, 11, 13 FCoE configuration (IRF mode), transmitting FCoE configuration (standalone mode),...
  • Page 187 FCoE overview, FC zone distribution process, FCoE VSAN configuration, FC zone distribution+merge type, FCoE well-known fabric addresses, FC zone merge (basic zoning), 79, 79 FCS configuration, 110, 113 FC zone merge (enhanced zoning), FDMI configuration, FC zone merge process, NPV configuration, 96, 97 FC zone merge rules, VFC interface configuration,...
  • Page 188 FC zone alias, FC zone configuration, 73, 82, 91 FC zone database deletion, FC zone database structure active zone set, FC zone database structure default zone, FC zone database structure peer zone, FC zone distribution+merge type, FC zone set, FC zone set activation+fabric distribution, FC zone set distribution trigger, FC zone-related copy, FC zone-related renaming,...

Table of Contents