Fibre channel over ethernet (FCOE) pinning system

An FCoE pinning system includes a second switch device that is coupled to a first switch device via a link aggregation group (LAG). The second switch device transmits a first communication that indicates a first port that is included on the second switch device and that is coupled to a first member of the LAG has a first FCoE pinning configuration and is in a willing mode. In response to determining that a second communication received from the first switch device indicates that a second port that is included on the first switch device and that is coupled to a second member link of the LAG has a second FCoE pinning configuration, and that the first switch device is in a willing mode, the second switch device forwards, in response to determining that no mismatch exists between the FCoE pinning configurations, FCoE type traffic via the first port.

BACKGROUND

The present disclosure relates generally to information handling systems, and more particularly to Fibre Channel over Ethernet (FCoE) pinning and pinning mismatch detection in information handling systems.

Some information handling systems are utilized to provide a Fibre Channel (FC) Storage Area Network (SAN) for the storage of data. For example, an FC switch device may be utilized to couple storage systems to server systems via a Fibre Channel over Ethernet (FCoE) Forwarder (FCF) device that performs FC over Ethernet (FCoE)-to-FC protocol conversions on Ethernet communications sent from the server systems to the storage systems, as well as FC-to-FCoE protocol conversions on FC communications sent from the storage devices to the servers. Such FCF devices allow for server systems that communicate via the Ethernet protocol to be utilized with storage systems in FC SANs that communicate via the FC protocol. However, the server systems are sometimes coupled to the storage systems discussed above via switch device aggregations provided by a plurality of switch devices (e.g., FCF devices, FCoE Initialization Protocol (FIP) snooping bridge (FSB) devices, Ethernet switch devices, etc.).

For example, the Virtual Link Trunking (VLT) protocol is a proprietary aggregation protocol available in switch devices provided by Dell Inc. of Round Rock, Tex., United States, and operates to provide a redundant, load-balancing connection in a loop-free environment that eliminates the need to use the Spanning Tree Protocol (STP). The VLT protocol may be utilized in a plurality of switch devices provided between the server system and the storage system discussed above to provide a VLT switch aggregation that provides for the transmission of packets between the server systems and the storage systems. As will be appreciated by one of skill in the art in possession of the present disclosure, the VLT switch aggregation provides Active/Active LAN connectivity on converged links via the forwarding of traffic in multiple paths to multiple upstream devices without STP blocking any of the uplinks, which works for Ethernet traffic, but FCoE traffic requires dedicated links for each SAN Fabric, as FCoE traffic sent via VLT switch aggregation breaks SAN fabric isolation as discussed below.]

For example, FC sessions are provided between FC nodes, while FCoE sessions are provided between Ethernet nodes, and in order to form FC sessions or FCoE sessions, the fabric login request and fabric login reply must be provided through the same port on a switch device. However, according to the VLT protocol, when the fabric login request that was initiated by a server system and transmitted through a switch device reaches the SAN Fabric, the login accept response may be the subject of hashing operations that provide for its transmittal out of any of the ports that are included in a VLT port-channel (i.e., a VLT Link Aggregation Group (LAG)). In the event the server system receives the response via a port that is different than the port upon which the request was sent, the server system will keep retrying the request. In such situations, FC sessions or FCoE sessions that are learnt based on login accept responses will enteran unstable state that is often referred to as “flapping”, and the FC sessions or FCoE sessions may keep flapping until the fabric login request and fabric login response converge (e.g., are transmitted and received) on the same port. To avoid this and to support FCoE traffic on multi-level networks that utilize the VLT protocol, port pinning is used in VLT LAGs to provide a static configuration that restricts FIP traffic and FCoE traffic to one port that is included in the port-channel in order to override the hardware LAG hashing discussed above. For example, conventional port pinning systems may classify and redirect packets exchanged during FCoE sessions to the same port (e.g., a “pinned” port) utilizing Access Control Lists (ACLs), which allow the remaining Ethernet traffic to flow through both the pinned port and other ports that are included in the port-channel based on the LAG hashing operations discussed above.

However, for a link to be pinned for FCoE traffic, both ports that provide that link must be pinned, and pinning operations for a port for the purposes of FIP traffic and FCoE traffic require an administrator to manually provide pinning commands via a command line interface (CLI). As such, mismatched FCoE pinning configurations often occur in which peer ports that provide a link are not both pinned. For example, one peer port that is included on a first switch device and that provides a first link may be pinned, while no FCoE pinning configuration may exist on the peer port that is included on the second switch device and that provides that first link, or the FCoE pinning configuration on the second switch may be provided on a port that is included on the second switch and that provides a second link that is different than the first link that is provided by the pinned port on the first switch.

Accordingly, it would be desirable to provide an improved FCoE pinning system.

SUMMARY

According to one embodiment, an Information Handling System (IHS) includes a communication system that includes a plurality of ports; a processing system coupled to the communication system; and a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a switch engine that is configured to: transmit, via a port that is included in the plurality of ports and that is coupled to a member link that is coupled to a switch device and that is included in a plurality of member links that are provided in a link aggregation group, a first communication that indicates: a first port of the plurality of ports that is included on the communication system and that is coupled to a first member link that is included in the plurality of member links has a first Fiber Channel over Ethernet (FCoE) pinning configuration; and the communication system is in a willing mode that indicates the communication system is willing to update the first FCoE pinning configuration; and in response to determining that a second communication received from the switch device indicates that a second port that is included on the switch device and that is coupled to a second member link that is included in the plurality of member links has a second FCoE pinning configuration, and that the switch device is in a willing mode that indicates the switch device is willing to update the second FCoE pinning configuration: determine whether a mismatch exists between the first FCoE pinning configuration and the second FCoE pinning configuration; and forward, in response to determining that no mismatch exists between the first FCoE pinning configuration and the second FCoE pinning configuration, FCoE type traffic via the first port.

DETAILED DESCRIPTION

Referring now toFIG. 2, an embodiment of an FCoE pinning system200is illustrated. In the illustrated embodiment, the FCoE pinning system200incudes a server system202. In an embodiment, the server system202may be provided by the IHS100discussed above with reference toFIG. 1, and/or may include some or all of the components of the IHS100. However, while illustrated and discussed as a server system202including one or more server devices, one of skill in the art in possession of the present disclosure will recognize that server system202provided in the FCoE pinning system200may be provided by a variety of host systems that include any devices that may be configured to operate similarly as the server system/server devices discussed below. The server system202may include one or more server subsystems that may include any hardware and/or software (e.g., a server device, a processing system, an application, etc.) that is configured to generate and transmit packets, as well as perform any of the other server subsystem operations described below. The server system202may also include one or more initiator/adapter devices, each of which is coupled to a respective server subsystem. In a specific example, initiator/adapter devices included in the server system202may be provided by Converged Network Adapters (CNAs), although other initiator devices and/or adapter devices will fall within the scope of the present disclosure as well.

The FCoE pinning system200also includes an aggregated switch system204that is coupled to the server system202. In the illustrated embodiment, the aggregated switch system204includes the switch devices204aand204b. Either or both of the switch devices204aand204bmay be provided by the IHS100discussed above with reference toFIG. 1, and/or may include some or all of the components of the IHS100. In a specific embodiment, the aggregated switch system may be provided by a Virtual Link Trunking (VLT) switch system that utilizes the VLT protocol, which is a proprietary aggregation protocol available in switch devices provided by DELL® Inc. of Round Rock, Tex., United States, and operates to provide a redundant, load-balancing connection in a loop-free environment that eliminates the need to use the Spanning Tree Protocol (STP). As such, each of the switch devices204aand204bmay operate as VLT switch devices within a VLT domain. However, other aggregated switch systems and switch devices will fall within the scope of the present disclosure as well.

In the illustrated embodiment, the switch device204ain the aggregated switch system204may be directly connected to the initiator/adapter device in the server system202via a link203a, the switch device204bin the aggregated switch system204may be directly connected to the initiator/adapter device in the server system202via link203b, and the switch devices204aand204bmay be connected to each other via Inter-Chassis Links (ICLs)205aand205bthat are aggregated to form an ICL aggregation (e.g., multiple ICLs205aand205bthat have been aggregated). In the embodiments illustrated and discussed below the ICL aggregation is described as a VLT interconnect (VLTi)208, although other ICL aggregations may fall within the scope of the present disclosure as well. In some embodiments, the server system202may be coupled to an orphan port on the switch device204aand/or to an orphan port on the switch device204b. As will be appreciated by one of skill in the art in possession of the present disclosure, orphan ports in a VLT switch system may be ports on the VLT switch devices that are not part of the VLT (e.g., non-VLT ports), and thus are not connected to a VLT port channel provided by the VLT switch device. However, in the illustrated embodiment, the server system202is coupled to the switch device204aand204band supports a link aggregation protocol such as the Link Aggregation Control Protocol (LACP), and thus the links203aand203bhave been aggregated (e.g., in a VLT Link Aggregation Group (LAG)) to form a VLT port channel210. Furthermore, the switch device204aincludes links212aand212bto a switch device204c, and the switch device202bincludes links212cand212dto the switch device204c, while each of those links212a-212dhave been aggregated (e.g., in a VLT Link Aggregation Group (LAG)) to form a VLT port channel214. However, while a specific example is illustrated and described below, one of skill in the art in possession of the present disclosure will recognize that the switch devices204aand202bmay include different numbers of links to the switch device204c, and those links may be aggregated in the VLT LAG to form the VLT port channel214.

The FCoE pinning system200also includes storage system206that is coupled to the switch device204c(e.g., provided by a Fibre Channel switch device coupled to the storage system206) via a link216. In an embodiment, the storage system206may be provided by the IHS100discussed above with reference toFIG. 1, and/or may include some or all of the components of the IHS100. However, while illustrated and discussed as a storage system206including one or more storage devices, one of skill in the art in possession of the present disclosure will recognize that storage system206provided in the FCoE pinning system200may be provided by a variety of components that include any devices that may be configured to operate similarly as the storage system/storage devices discussed below. While a specific FCoE pinning system200has been illustrated and described, one of skill in the art in possession of the present disclosure will recognize that the FCoE pinning system of the present disclosure may include a variety of components (e.g., additional switch devices) and component configurations while remaining within the scope of the present disclosure as well.

Referring now toFIG. 3, an embodiment of a switch device300is illustrated that may provide any or all of the switch devices204a,204b, and/or204cdiscussed above with reference toFIG. 2. As such, the switch device300may be provided by the IHS100discussed above with reference toFIG. 1and/or may include some or all of the components of the IHS100. Furthermore, while illustrated and discussed as a VLT switch device in some of the examples below, one of skill in the art in possession of the present disclosure will recognize that the functionality of the switch device300discussed below may be provided by other devices (e.g., an FCF device, an FSB device, and/or other switch devices that would be apparent to one of skill in the art in possession of the present disclosure) that are configured to operate similarly as discussed below. In the illustrated embodiment, the switch device300includes a chassis302that houses the components of the switch device300, only some of which are illustrated below. For example, the chassis302may house a processing system (not illustrated, but which may include the processor102discussed above with reference toFIG. 1) and a memory system (not illustrated, but which may include the memory114discussed above with reference toFIG. 1) that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a switch engine304that is configured to perform the functionality of the switch engines and/or switch devices discussed below.

The chassis302may also house a storage system (not illustrated, but which may include the storage108discussed above with reference toFIG. 1) that is coupled to the switch engine304(e.g., via a coupling between the storage system and the processing system) and that includes a switch database306that is configured to store any of the information utilized by the switch engine304discussed below. The chassis302may also house a communication system308that is coupled to the switch engine304(e.g., via a coupling between the communication system308and the processing system) and that may be provided by a Network Interface Controller (NIC), wireless communication systems (e.g., BLUETOOTH®, Near Field Communication (NFC) components, WiFi components, etc.), and/or any other communication components that would be apparent to one of skill in the art in possession of the present disclosure. As will be appreciated by one of skill in the art in possession of the present disclosure, the communication system308in the switch device300may include any of the ports utilized in the manners described below. While a specific switch device300has been illustrated, one of skill in the art in possession of the present disclosure will recognize that switch devices (or other devices operating according to the teachings of the present disclosure in a manner similar to that described below for the switch device300) may include a variety of components and/or component configurations for providing conventional switch device functionality, as well as the functionality discussed below, while remaining within the scope of the present disclosure as well.

Referring now toFIGS. 4A-40, an embodiment of a method400for FCoE pinning is illustrated. As discussed below, the systems and methods of the present disclosure may provide for the automatic detection of FCoE pinning mismatches and the automatic reconfiguration of mismatched ports to eliminate FCoE pinning mismatches between two switch devices that are coupled together via an aggregated interface (e.g., a VLT port channel, also referred to as a VLT LAG). The systems and methods of the present disclosure may also provide for the removal of an FCoE pinning configuration provided for a port on a switch device when its peer port on a peer switch device cannot be configured as a pinned port, which allows a VLT LAG that includes a link provided by those ports to operate as a VLT LAG without pinning. For example, in an FCoE pinning system including a first switch device and a second switch device that is coupled to the first switch device via a link aggregation group, with the link aggregation group including a plurality of member links between the first switch device and the second switch device, the first switch device and/or the second switch device may exchange communications that include pinning advertisements (e.g., FCoE pinning configuration Time Length Value (TLV) communications) that indicate that a port on that switch device includes an FCoE pinning configuration, as well as whether or not that switch device is willing to update a FCoE pinning configuration provided for its ports.

For example, switch devices that include an FCoE pinning configuration may send an FCoE pinning configuration TLV communication in an LLDP exchange, and advertise whether they are willing to update an FCoE pinning configuration. However, switch devices that do not include an FCoE pinning configuration will not send FCoE pinning configuration TLV communications. Furthermore, switch devices that are willing to update an FCoE pinning configuration but that do not include an FCoE pinning configuration will not send the FCoE pinning configuration TLV communication during the LLDP exchange, but will update their FCoE pinning configuration according to any FCoE pinning configuration TLV communications received during the LLDP exchange in order to match their peer switch devices, and will then operate to send an FCoE pinning configuration TLV communication in the next LLDP exchange. Further still, switch devices that are not willing to update an FCoE pinning configuration and that do not include an FCoE pinning configuration will not send FCoE pinning configuration TLV communications, which causes their peer switch devices that include FCoE pinning configurations to mark those FCoE pinning configurations as mismatched and the FCoE pinned port state will go down so that any VLT LAG between the two switch devices may operate normally. As such, FCoE pinning mismatches may be detected by peer switch devices using FCoE pinning configuration TLV communications and, in some cases, may be correctable without an administrator having to identify and correct the mismatch. Finally, an FCoE pinning configuration provided for a port may be brought down if its peer port cannot be configured with an FCoE pinning configuration.

The method400begins at decision block402where it is determined whether a first switch device, which is coupled to a second switch device via a link aggregation group that includes a plurality of member links between the first switch device and the second switch device, is in a willing mode and has an FCoE pinning configuration. In an embodiment, at decision block402, the switch engine304in the switch device204a/300may determine whether the switch device204ais in a willing mode and includes an FCoE pinning configuration on a port that is included in a link aggregation group (e.g., the VLT port channel214). While method400is described from the perspective of the switch device204a, one of skill in the art in possession of the present disclosure will recognize that the method400may also be performed by each of the switch devices204band/or204cas well. In various embodiments, the willing mode may indicate either that the switch device204ais willing to update the FCoE pinning configuration for a port on the switch device204a, or that the switch device204ais willing to add an FCoE pinning configuration to one of the ports on the switch device204a. In various embodiments, a non-willing mode may indicate that the switch device204ais not willing to update an FCoE pinning configuration for a port on the switch device204a, and not willing to add an FCoE pinning configuration to one of the ports on the switch device204a.

In an embodiment, the switch engine304in the switch device204a/300may determine the switch device204ais in willing mode or non-willing mode by a configurable setting so that a user can configure one switch device, which is non-willing and the other switch device will get automatically configured due to it being willing to take on the other switch's configuration. As discussed above, one or more of the ports on the switch device204amay be coupled to the links212aand212bthat are included in the VLT port channel214, and may include an FCoE pinning configuration that “pins” that port in order to, for example, restrict certain data traffic such as FIP traffic and/or FCoE traffic to that port, and/or provide a variety of other pinning functionality that would be apparent to one of skill in the art in possession of the present disclosure. As will be appreciated by one of skill in the art in possession of the present disclosure, in such a situation, Ethernet traffic may also be provided on the pinned ports or non-pinned ports, but FIP traffic and FCoE traffic will not be provided on non-pinned ports that are included in the VLT port channel214when there are pinned ports that are configured to transmit the FIP traffic and FCoE traffic. In one example, the switch engine304in the switch device204a/300may determine whether one the ports on the switch device204aincludes an FCoE pinning configuration by referencing a pinning table stored in the switch database306that identifies pinned ports (e.g., ports that include an FCoE pinning configuration) that are provided on the switch device204a

If, at decision block402, it is determined that the switch device204aincludes an FCoE pinning configuration and the switch device204ais in a willing mode, the method400then proceeds to block404where a communication that includes an advertisement is transmitted that indicates that the first switch device is in willing mode and has an FCoE pinning configuration. In an embodiment, at block404, the switch engine304in the switch device204a/300may transmit a communication, which includes an advertisement that indicates that the switch device204ais in the willing mode and has an FCoE pinning configuration, to the switch device204cvia the link212aand/or the link212b. In an embodiment, the communication transmitted at block404may be provided by Type-Length-Value (TLV) communications that is referred to below as an FCoE pinning configuration TLV communication that includes information such as, for example, an indication that there is an FCoE pinning configuration on switch device204a, whether the switch device204ais in a willing mode or in a non-willing mode, as well as any other information that would be apparent to one of skill in the art in possession of the present disclosure. For example, the FCoE pinning configuration TLV communication may be provided as part of an existing Data Center Bridging Capability Exchange (DCBx) TLV communication. As discussed in further detail below, the switch device204amay only transmit the communication at block404when there is an FCoE pinning configuration for a port on the switch device204a.

The method400then proceeds to decision block406where it is determined whether a communication is received from a peer switch device. In an embodiment, at decision block406, the switch engine304in the switch device204a/300may determine whether a communication has been received from the switch device204cthat includes an advertisement indicating whether the switch device204cis in the willing mode or non-willing mode and whether the switch device204chas an FCoE pinning configuration. Similarly as described above, any communication determined to be received from the switch device204cat decision block406may be an FCoE pinning configuration TLV communication. In some embodiments, the determining of whether the communication from the switch device204chas been received may include the switch engine304monitoring a timer to determine whether a time period has lapsed subsequent to the switch engine304in the switch device204a/300transmitted its FCoE pinning configuration TLV communication, discussed above, and in the event the time period has lapsed, the switch engine304in the switch device204amay determine that the communication from the switch device204chas not been received.

If, at decision block406, it is determined that the communication from the peer switch device has not been received, the method400proceeds to block408where the switch device marks the FCoE pinning configuration as mismatched. In an embodiment, at block408, the switch engine304in the switch device204a/300may remove the FCoE pinning configuration for the switch device204a. As discussed in further detail below, if the switch device204adoes not receive the FCoE pinning configuration TLV communication from its peer switch device (e.g., the switch device204c), that may indicate that the switch device204cis in a non-willing mode and has no FCoE pinning configuration and, as such, an FCoE pinning mismatch exists between peer ports on the switch device204aand the switch device204cbecause there is no pinned port on the switch device204cand the switch device204cis not willing to automatically configure its ports with an FCoE pinning configuration. Thus, the switch device204amay mark its FCoE pinning configuration as mismatched and the FCoE pinned status will be down to prevent issues discussed above that occur with mismatched pinned ports, and instead use the VLT port channel214as a normal LAG for Ethernet traffic. FCoE/FIP is not sent on that port that has the mismatch.

For example, and with reference toFIGS. 5A and 5B, the switch device204amay have an FCoE pinning configuration502on the port coupled to the link212a, and the switch device204amay transmit the communication504(e.g., an FCoE pinning configuration TLV communication) to the switch device204cand wait for a response. As illustrated inFIG. 5B, when an FCoE pinning configuration TLV communication is not received from the switch device204cby the switch device204ain some time period, the switch device204amay remove the FCoE pinning configuration502, and the VLT port channel214may be used for Ethernet traffic or other non-FCoE traffic.

If at decision block406, it is determined that a communication is received, the method400proceeds to decision block410where it is determined whether the peer switch device is in a willing mode. In an embodiment, at decision block410, the switch engine304in the switch device204a/300may determine whether the received communication (e.g., the FCoE pinning configuration TLV communication) indicates that the switch device204cis in a willing mode by, for example, processing the FCoE pinning configuration TLV communication. The FCoE pinning configuration TLV communication may include searchable fields in a TLV information string in a TLV packet that indicate whether the switch device is in willing mode and the presence of the FCoE pinning configuration. The switch engine304can search these fields to determine whether switch device is in willing node and the FCoE pinning configuration

If, at decision block410, the peer switch device is not in the willing mode, then the method400proceeds to decision block411where the switch device determines whether there is a mismatch between the FCoE pinning configurations provided for the switch device and its peer switch device. In an embodiment, at decision block411, the switch engine304in the switch device204a/300may determine whether there is a mismatch between the FCoE pinning configurations provided for the switch device204aand the switch device204c. For example, an FCoE pinning configuration mismatch between the switch devices204aand204cmay be detected when the FCoE pinning configuration TLV communication includes pinning information that indicates which port on the switch device204cis pinned or not and comparing that information to the pinned port of the switch device204a.

If, at decision block411, a mismatch between the FCoE pinning configurations provided for the switch device and its peer switch device is detected, the method400may proceed to block412where the switch device reconfigures its FCoE pinning configuration to match the FCoE pinning configuration provided for its peer switch device. In an embodiment, at block412, the switch engine304in the switch device204a/300may reconfigure its FCoE pinning configuration by updating the pinning table stored in its switch database306to match the FCoE pinning configuration provided for the switch device204c. For example, in response to the switch device204cadvertising to switch device204athat it is in a non-willing mode, the switch device204amay update its FCoE pinning configuration to correct the mismatch. The switch device204amay then send a subsequent communication (e.g., a subsequent FCoE pinning configuration TLV communication in a subsequent LLDP exchange) that indicates the FCoE pinning configuration at the switch device204ahas changed. For example, the subsequent FCoE pinning configuration TLV communication may be sent via the port on the switch device204athat is now pinned, through the link, and to the port that includes the FCoE pinning configuration on the switch device204c.

The method400may then proceed to block414where FCoE traffic is transmitted on the port that includes the FCoE pinning configuration. In an embodiment, at block414, the switch engine304in the switch device204a/300may transmit FCoE type traffic such as, for example, FIP traffic and FCoE traffic, to the switch device204cvia the port that was provided the FCoE pinning configuration. Furthermore, the switch engine304in the switch device204a/300may receive FIP traffic and/or FCoE traffic from the switch device204cand via the port that was provided the FCoE pinning configuration. As would be apparent to one of skill in the art in possession of the present disclosure, the FCoE pinning configuration overrides hardware LAG hashing operations and restricts the FIP traffic and FCoE traffic to one port that is included in the VLT port channel214. One of skill in the art in possession of the present disclosure will also recognize that ports that include the FCoE pinning configuration will also transmit Ethernet traffic, as Ethernet traffic is allowed to flow through both the pinned port and other ports in the VLT port channel214via the hardware LAG hashing operations discussed above.

For example, and with reference toFIGS. 6A and 6Band blocks406,410,411,412and414of method400, the switch device204amay have an FCoE pinning configuration602aprovided for the port coupled to the link212a, and the switch device204cmay have an FCoE pinning configuration602bprovided for the port coupled to the link212b. The switch device204amay transmit the communication604a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication604b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. With reference toFIG. 6B, in this embodiment the switch device204cis in a non-willing mode, and thus the switch device204amay update the FCoE pinning configuration602ato an FCoE pinning configuration602cthat is provided on the port coupled to the link212bin order to match the FCoE pinning configuration602b, and may transmit a communication604cto the switch device204cthat advertises the new FCoE pinning configuration602c. As such, data traffic606may then be transmitted on the link212b, with the FCoE pinning configurations602band602crestricting the link212bto FCoE type traffic (e.g., FCoE traffic and/or FIP traffic).

Referring back to decision block411, if no mismatch between the FCoE pinning configurations provided for the switch device and its peer switch device is detected, then the method400proceeds to block414where FCoE traffic is transmitted on the port that includes the FCoE pinning configuration. In an embodiment, at block414, the switch engine304in the switch device204a/300may transmit FCoE type traffic such as, for example, FIP traffic and/or FCoE traffic, to the switch device204cand via the port that includes the FCoE pinning configuration. Furthermore, the switch engine304in the switch device204a/300may also receive FIP traffic and/or FCoE traffic from the switch device204con the port that includes the FCoE pinning configuration. As discussed above, the FCoE pinning configuration overrides the hardware LAG hashing operations discussed above and restricts the FIP traffic and/or FCoE traffic to one port that is included in the VLT port-channel214.

For example, and with reference toFIGS. 7A and 7Band blocks406,410,411and414of method400, the switch device204amay have an FCoE pinning configuration702aprovided for the port coupled to the link212a, and the switch device204cmay have an FCoE pinning configuration702bprovided for the port coupled to the link212a. The switch device204amay transmit the communication704a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication704b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. In this embodiment, the FCoE pinning configuration702aand702bare on the same link212aand thus do not result in a mismatch. As illustrated inFIG. 7B, data traffic706may then be transmitted on the link212a, with the FCoE pinning configurations702aand702brestricts FIP traffic and/or FCoE traffic to the link212a.

Referring back to decision block410, if it is determined that the peer switch device is in willing mode, then the method400proceeds to decision block416where the switch device determines whether there is a mismatch in the FCoE pinning configurations provided for the switch device and its peer switch device. In an embodiment, at decision block416, the switch engine304in the switch device204a/300may determine whether there is a mismatch in the FCoE pinning configurations provided for the switch device204aand the switch device204cby, for example, determining whether the communication received from the switch device204cwas received at a different port on the switch device204athan the port on the switch device204athat includes the FCoE pinning configuration.

If, at decision block416, it is determined that there is no mismatch in the FCoE pinning configurations provided for the switch device and its peer switch device, the method400may proceed to block414where FCoE traffic is transmitted on the port that includes the FCoE pinning configuration. In an embodiment, at block414and in response to determining there is no mismatch in the FCoE pinning configurations provided for the switch devices204aand204c, the switch engine304in the switch device204a/300may transmit FCoE traffic such as, for example, FIP traffic and FCoE traffic, to the switch device204cvia the port that includes the FCoE pinning configuration. Furthermore, the switch engine304in the switch device204a/300may also receive FIP traffic and FCoE traffic from the switch device204cvia the port that includes the FCoE pinning configuration. As discussed above, other data traffic such as, for example, Ethernet traffic, may be transmitted on the link that is pinned as well.

For example, and with reference toFIGS. 7A and 7Band blocks406,410,416and414of method400, the switch device204amay have the FCoE pinning configuration702aprovided for the port coupled to the link212a, and the switch device204cmay have the FCoE pinning configuration702bprovided for the port coupled to the link212a. The switch device204amay transmit the communication704a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication704b(e.g., an FCoE pinning configuration TLV communication) to the switch device204athat indicates that the switch device204cis willing. In this embodiment, the FCoE pinning configurations702aand702bare on the same link212aand, as such, no mismatch is detected. Thus, as illustrated inFIG. 7B, data traffic706may be transmitted on the link212a, with the FCoE pinning configurations702aand702brestricting FCoE traffic and/or FIP traffic to the link212a. As discussed above, the data traffic may include Ethernet traffic as well.

If, at decision block416, it is determined that there is a mismatch between the FCoE pinning configurations provided for the switch device and its peer switch device, the method400may proceed to block418where the switch device reconfigures its FCoE pinning configuration to match the FCoE pinning configuration of its peer switch device, or its peer switch device reconfigures its FCoE pinning configuration to match the FCoE pinning configuration provided for the switch device. In an embodiment, at block418, the switch engine304in the switch device204a/300may reconfigure the FCoE pinning configuration by updating the pinning table stored in switch database306in order to match the FCoE pinning configuration provided for the switch device204c. In this embodiment, the switch device204cadvertised to the switch device204athat it is in the willing mode, and thus the switch device204amay update its FCoE pinning configuration to correct the mismatch. The switch device204amay then send a subsequent communication (e.g., a subsequent FCoE pinning configuration TLV communication in a subsequent LLDP exchange) that indicates the FCoE pinning configuration provided for the switch device204ahas changed. For example, the subsequent FCoE pinning configuration TLV communication may be sent via the port on the switch device204athat is now pinned, through the link, and to the port that includes the FCoE pinning configuration on the switch device204c.

Alternatively, the switch engine304in the switch device204c/300may reconfigure the FCoE pinning configuration by updating the pinning table stored in the switch database306to match the FCoE pinning configuration provided for the switch device204a. In this embodiment, the switch device204aadvertised to the switch device204cthat it is in the willing mode, and thus the switch device204cmay update its FCoE pinning configuration to correct the mismatch. The switch device204cmay then send a subsequent communication (e.g., a subsequent FCoE pinning configuration TLV communication in a subsequent LLDP exchange) that indicates the FCoE pinning configuration provided for the switch device204chas changed, and that subsequent communication may be received by the switch device204a. For example, the subsequent FCoE pinning configuration TLV communication may be sent via the port on the switch device204cthat is now pinned, through the link, and to the port that includes the FCoE pinning configuration on the switch device204a. Thus, when there is a mismatch and both switch devices204aand204care in a willing mode and include FCoE pinning configurations, the switch device that receives the FCoE pinning configuration TLV communication first will update their configuration and sends the new values in the next TLV communication. The method400then proceeds to block414as discussed above.

For example, and with reference toFIGS. 6A and 6Band blocks406,410,416,418and414, the switch device204amay have the FCoE pinning configuration602aprovided for the port coupled to the link212a, and the switch device204cmay have the FCoE pinning configuration602bprovided for the port coupled to the link212b. The switch device204amay transmit the communication604a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication604b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. In this embodiment, both switches204aand204care in the willing mode, and thus the switch devices204aand204cmay determine which switch device204aor204cwill change its FCoE pinning configuration based on which switch receives the FCoE pinning configuration TLV communication first. As illustrated inFIG. 6B, in one example, the switch device204amay update the FCoE pinning configuration602ato an FCoE pinning configuration602cthat is provided for the port that is coupled to the link212bin order to match the FCoE pinning configuration602b, and may transmit the communication604cto the switch device204cthat advertises the new FCoE pinning configuration602c. As discussed above, data traffic606may then be transmitted on the link212b, with the FCoE pinning configurations602aand602brestricting the link212bto FCoE traffic and/or FIP traffic. However, in other embodiments, the switch device204cmay update the FCoE pinning configuration602bto an FCoE pinning configuration (not illustrated) provided for the port coupled to the link212ain order to match the FCoE pinning configuration602a, and may transmit a communication to the switch device204athat advertises the new FCoE pinning configuration on the switch device204c. As discussed above, data traffic may then be transmitted on the link212a, with the FCoE pinning configurations restricting FCoE traffic and FIP traffic to the link212a.

Referring back to decision block402, if it is determined that the switch device is in a non-willing mode and/or does not include an FCoE pinning configuration, then the method400proceeds to decision block420where it is determined whether the switch device is willing and does not include an FCoE pinning configuration. In an embodiment, at decision block420, the switch engine304in the switch device204a/300may determine whether the switch device204ais in a willing mode and does not includes an FCoE pinning configuration provided for a port that is included in the link aggregation group (e.g., the VLT port channel214). For example, the switch engine304in the switch device204a/300may determine that the switch device204ais in willing mode by checking a willing mode enabled setting. Furthermore, the switch engine304in the switch device204a/300may determine whether ports on the switch device204ainclude an FCoE pinning configuration by referencing a pinning table that is stored in the switch database306and that identifies a pinned port (e.g., a port that includes an FCoE pinning configuration).

If, at decision block420, it is determined that the switch device is in a willing mode and has no FCoE pinning configuration, the method400then proceeds to decision block422where it is determined whether a communication is received from a peer switch device. In an embodiment, at decision block422, the switch engine304in the switch device204a/300may determine whether a communication is received from the switch device204cthat includes an advertisement indicating whether the switch device204cis in the willing mode or the non-willing mode, and indicating the switch device204chas an FCoE pinning configuration. In this embodiment, the switch device204ais in the willing mode and has no FCoE pinning configuration, and thus the switch device204adoes not transmit a communication to the switch device204cduring the LLDP exchange. Furthermore, the communication transmitted from the switch device204cto the switch device204amay be an FCoE pinning configuration TLV communication, discussed above, and in determining whether the communication is received from the switch device204c, the switch engine304in the switch device204a/300may determine that the communication from the switch device204chas not been received at decision block422.

If, at decision block422, it is determined that the communication from the peer switch device has not been received, the method400proceeds to block424where the ports on the switch device are utilized as part of the VLT port channel via LAG hashing operations in which data traffic is hashed to determine which link available via the VLT port channel is used to transmit that data traffic. In an embodiment, at block424, the switch engine304in the switch device204a/300may utilize its ports that provide the links212aand212band that are included in the VLT port channel214via standard LAG protocols that operate to hash data traffic to determine which of those links that are available via the VLT port channel214are used to transmit that data traffic. In an embodiment, in the event the switch device204adoes not receive the FCoE pinning configuration TLV communication from its peer switch device (e.g., the switch device204c), that lack of communication may indicate that the switch device204chas no FCoE pinning configuration. As such, in this embodiment, there is no FCoE pinning configuration on either of the switch device204aand the switch device204c, which will result in the switch devices204aand204cusing the VLT port channel214as a normal LAG for Ethernet traffic.

If, at decision block422, it is determined that the communication from the peer switch device has been received, the method400proceeds to block426where the switch device configures its FCoE pinning configuration to match the FCoE pinning configuration provided for its peer switch device. In an embodiment, at block426, the switch engine304in the switch device204a/300may configure its FCoE pinning configuration by updating the pinning table stored in its switch database306to match the FCoE pinning configuration provided for the switch device204c. In this embodiment, the switch device204cadvertised to switch device204athat the switch device204cincludes an FCoE pinning configuration, and the switch device204amay operate to update its FCoE pinning configuration to correct the mismatch that was present due to the switch device204anot having an FCoE pinning configuration. The switch device204amay then send a subsequent communication (e.g., a subsequent FCoE pinning configuration TLV communication in a subsequent LLDP exchange) that indicates the FCoE pinning configuration at the switch device204ahas changed. For example, the subsequent FCoE pinning configuration TLV communication may be sent via the port on the switch device204athat is now pinned, through the link, and to the port that includes the FCoE pinning configuration on the switch device204c.

The method400may then proceed to block428where FCoE traffic is transmitted on the port that includes the FCoE pinning configuration. In an embodiment, at block414, the switch engine304in the switch device204a/300may transmit FCoE type traffic such as, for example, FIP traffic and/or FCoE traffic, to the switch device204cvia the port that includes the FCoE pinning configuration. Furthermore, the switch engine304in the switch device204a/300may receive FIP traffic and/or FCoE traffic from the switch device204cvia the port that includes the FCoE pinning configuration. As discussed above, the FCoE pinning configuration restricts the FCoE type traffic to one port of the VLT port-channel214, thus overriding hardware LAG hashing operations (while still allowing Ethernet traffic that is subject to LAG hashing operations to be transmitted via that port.)

For example, and with reference toFIGS. 8A and 8Band blocks422,426, and428of method400, the switch device204amay not have an FCoE pinning configuration provided for the ports coupled to the links212aand212b, and the switch device204cmay have an FCoE pinning configuration802aon the port coupled to the link212b. The switch device204cmay transmit the communication804a(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. As illustrated inFIG. 8B, in this embodiment, the switch device204ais in the willing mode, and the switch device204amay configure the port coupled to the link212bwith an FCoE pinning configuration802bin order to match the FCoE pinning configuration802a, and transmit the communication804bto the switch device204cthat advertises the new FCoE pinning configuration802b. As discussed above, data traffic806may then be transmitted on the link212b, with the FCoE pinning configurations802aand802brestricting the link212bto transmitting FCoE traffic and/or FIP traffic.

Referring back to decision block420, if it is determined that the switch device is in a non-willing mode and includes an FCoE pinning configuration, or that the switch device is in a non-willing mode and does not include an FCoE pinning configuration, the method400proceeds to decision block430where it is determined whether the switch device is in a non-willing mode and includes an FCoE pinning configuration. In an embodiment, at decision block430, the switch engine304in the switch device204a/300may determine whether the switch device204ais in a non-willing mode and includes an FCoE pinning configuration provided for a port that is included in the link aggregation group (e.g., the VLT port channel214). For example, the switch engine304in the switch device204a/300may determine the switch device204ais in the non-willing mode by checking a willing mode configuration setting. The switch engine304in the switch device204a/300may also determine whether one the ports on the switch device204ais provided with an FCoE pinning configuration by referencing a pinning table stored in its switch database306that identifies a pinned port (e.g., a port that includes an FCoE pinning configuration).

If, at decision block430, it is determined that the switch device includes an FCoE pinning configuration and the switch device is in a non-willing mode, the method400then proceeds to block432where a communication is transmitted that includes an advertisement indicating that the switch device is in a non-willing mode and has an FCoE pinning configuration. In an embodiment, at block432, the switch engine304in the switch device204a/300may transmit a communication to the switch device204cvia the one of the link212aor the link212bthat includes the FCoE pinning configuration, with that communication including an advertisement that the switch device204ais in the non-willing mode and has an FCoE pinning configuration. Similarly as discussed above, the communication may be provided an FCoE pinning configuration TLV communication that includes information such an indication that there is an FCoE pinning configuration on the switch device204a, whether the switch device204ais in the willing mode or the non-willing mode, as well as any other information that would be apparent to one of skill in the art in possession of the present disclosure.

The method400then proceeds to decision block434where it is determined whether a communication is received from a peer switch device. In an embodiment, at decision block434, the switch engine304in the switch device204a/300may determine whether a communication has been received from the switch device204cthat includes an advertisement indicating whether the switch device204cis in the willing mode or the non-willing mode, and indicating that the switch device204chas an FCoE pinning configuration. Similarly as discussed above, the communication from the switch device204cmay be an FCoE pinning configuration TLV communication, discussed above. In an embodiment, the determination of whether the communication from the switch device204cis received may include the switch engine304in the switch device204a/300monitoring a timer to determine whether a time period has lapsed subsequent to the switch engine304in the switch device204a/300transmitting its FCoE pinning configuration TLV communication. As such, if the time period has lapsed, the switch engine304in the switch device204a/300may determine that the communication from the switch device204chas not been received.

If, at decision block434, it is determined that the communication from the peer switch device has not been received, the method400proceeds to block436where the switch device marks its FCoE pinning configuration as mismatched. In an embodiment, at block436, the switch engine304in the switch device204a/300may remove its FCoE pinning configuration. In an embodiment, if the switch device204adetermines that the FCoE pinning configuration TLV communication has not been received from its peer switch device (e.g., the switch device204c), that lack of communication may indicate that the switch device204cis in a non-willing mode and has no FCoE pinning configuration. As such, there will be an FCoE pinning configuration mismatch, as there is no pinned port on the switch device204cand the switch device204cis not willing to automatically configure its ports with an FCoE pinning configuration (i.e., because the switch device204chas not responded to the communication sent by the switch device204a.) In response, the switch device204amay mark its FCoE pinning configuration as mismatched and the FCoE pinned status will be down to prevent the issues discussed above that may occur due to mismatched pinned ports, and use the VLT port channel214as a normal LAG for the transmittal of Ethernet traffic.

For example, and with reference toFIGS. 5A and 5Band blocks434and436, the switch device204amay have an FCoE pinning configuration502provided for the port coupled to the link212a, and the switch device204amay transmit the communication504(e.g., an FCoE pinning configuration TLV communication) to the switch device204cand wait for a response. In this example, the communication504may indicate that the switch device204ais in a non-willing mode and includes an FCoE pinning configuration, and if it is determined that an FCoE pinning configuration TLV communication is not received back from the switch device204c(e.g., due to the switch device204cbeing in the non-willing mode and having no FCoE pinning configuration), the switch device204amay remove its FCoE pinning configuration502as illustrated inFIG. 5B, and the VLT port channel214may be used for Ethernet traffic or other non-FCoE traffic.

If, at decision block434, it is determined that the communication from the peer switch device has been received, the method400proceeds to decision block438where the switch device determines whether there is a mismatch in the FCoE pinning configurations provided for the switch device and its peer switch device. In an embodiment, at decision block438, the switch engine304in the switch device204a/300may determine whether there is a mismatch in the FCoE pinning configurations provided for the switch device204aand the switch device204c. For example, at decision block438, the communication from the switch device204cmay be received at a different port on the switch device204athan the port on the switch device204athat includes the FCoE pinning configuration, which may indicate a mismatch in FCoE pinning configurations, or the communication may be received at the port on the switch device204athat includes the FCoE pinning configuration, which may indicate no mismatch in FCoE pinning configurations.

If, at decision block438, it is determined that there is no mismatch in the FCoE pinning configurations provided for the switch device and the peer switch device, the method400proceeds to block440where FCoE traffic is transmitted on the port that includes the FCoE pinning configuration. In an embodiment, at block414, the switch engine304in the switch device204a/300may transmit FCoE type traffic such as, for example, FIP traffic and/or FCoE traffic, to the switch device204cvia the port that includes the FCoE pinning configuration. Furthermore, the switch engine304in the switch device204a/300may also receive data traffic (e.g., FIP traffic, FCoE traffic, Ethernet traffic) from the switch device204cvia the port that includes the FCoE pinning configuration. As discussed above, the FCoE pinning configuration restricts the FIP and/or FCoE traffic, to one port of the VLT port-channel214, thus overriding the hardware LAG hashing operations discussed above.

For example, and with reference toFIGS. 7A and 7Band blocks434,438and440of method400, the switch device204amay have an FCoE pinning configuration702aprovided for the port coupled to the link212a, and the switch device204cmay have an FCoE pinning configuration702bprovided for the port coupled to the link212a. The switch device204amay transmit the communication704a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication704b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. In this embodiment, the FCoE pinning configuration702aand702bare on the same link212a, and thus no FCoE pinning configuration mismatch may be detected. As illustrated inFIG. 7B, data traffic706may then be transmitted on the link212a, with the FCoE pinning configurations702aand702brestricting the link212ato transmitting FCoE type traffic (e.g., FCoE traffic and/or FIP traffic).

If, at decision block438, it is determined that there is a mismatch in the FCoE pinning configurations of the switch device and its peer switch device, the method400proceeds to decision block442where it is determined whether the peer switch device is in the willing mode. In an embodiment, at decision block442, the switch engine304in the switch device204a/300may process the received communication (e.g., the FCoE pinning configuration TLV communication) to determine whether the switch device204cis in a willing mode or not. If, at decision block442, it is determined that the peer switch device is in non-willing mode, the method400may proceed to block436where the switch device removes its FCoE pinning configuration. For example, each of the switch device204aand the switch device204cmay remove their FCoE pinning configurations, as both switch device204aand204care in non-willing mode and include FCoE pinning configurations that are mismatched.

For example, and with reference toFIGS. 9A and 9Band blocks434,438,442, and436of method400, the switch device204amay have an FCoE pinning configuration702aprovided for the port coupled to the link212a, and the switch device204cmay have an FCoE pinning configuration902bprovided for the port coupled to the link212b. The switch device204amay transmit the communication904a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication904b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. In this embodiment, the FCoE pinning configurations1002aand902bare provided for ports associated with different links, and thus there is mismatch in those FCoE pinning configurations, and with both of the switch devices204aand204cin the non-willing mode, that mismatch in the FCoE pinning configurations cannot be corrected. As such, as illustrated inFIG. 9B, the switch device204amay remove the FCoE pinning configuration902a, the switch device204cmay remove the FCoE pinning configuration902b, and the VLT port channel214may be used for Ethernet traffic or other non-FCoE traffic.

If, at decision block442, it is determined that the peer switch device is in the willing mode, the method400may proceed to block444where the switch device waits until a second communication is received from the peer switch device. In an embodiment, at block444, the switch engine304in the switch device204a/300may determine from the communication received at decision block434that the switch device204cis in the willing mode and includes an FCoE pinning configuration that is mismatched with the FCoE pinning configuration provided for the switch device204a. In this embodiment, the switch device204ais in the non-willing mode and the switch device204cis in the willing mode, and thus the switch device204amay wait for the switch device204cto update its FCoE pinning configuration such that the FCoE pinning configuration provided for the switch device204cmatches the FCoE pinning configuration provided for the switch device204a. The switch device204cmay then indicate that its FCoE pinning configuration has been updated by sending a subsequent FCoE pinning configuration TLV communication to the switch device204ain a subsequent LLDP exchange with the switch device204athat indicates the newly updated FCoE pinning configuration on the switch device204c. The method400may then proceed to block440.

For example, and with reference toFIGS. 10A and 10Band blocks434,438,442,444and440of method400, the switch device204amay have an FCoE pinning configuration702aprovided for the port coupled to the link212a, and the switch device204cmay have an FCoE pinning configuration1002bprovided for the port coupled to the link212b. The switch device204amay transmit the communication1004a(e.g., an FCoE pinning configuration TLV communication) to the switch device204c, and the switch device204cmay transmit the communication1004b(e.g., an FCoE pinning configuration TLV communication) to the switch device204a. In this embodiment, the FCoE pinning configurations1002aand1002bare provided for ports associated with different links, and thus there is mismatch in those FCoE pinning configurations. As such, with the switch device204ais the non-willing mode and the switch device204cis in the willing mode, a mismatch in the FCoE pinning configurations may be corrected by the switch device204cby, for example, the switch device204cupdating the FCoE pinning configuration1002bto an FCoE pinning configuration1002cto match the FCoE pinning configuration1002aas illustrated inFIG. 10B, and transmitting a communication1004cto the switch device204athat advertises the new FCoE pinning configuration1002c, as discussed above, data traffic1006may then be transmitted on the link212bsuch that the FCoE pinning configurations1002aand1002brestrict the link212ato transmitting FCoE type traffic (e.g., FCoE traffic and/or FIP traffic).

Referring back to decision block430, if it is determined that the switch device is in a non-willing mode and does not include an FCoE pinning configuration, then the method400proceed to block446where the switch device utilizes LAG hashing operations with its ports that are included in the VLT port channel by hashing data traffic to determine which of the links that are provided by ports that are included in the VLT port channel will be used to transmit that data traffic. In an embodiment, at block446, the switch engine304in the switch device204a/300may utilize its ports that are coupled to the links212aand212band that are included in the VLT port channel214via LAG protocols that operate to hash data traffic to determine which of the links available via the VLT port channel214will be used to transmit that data traffic. In this embodiment, the switch device204adoes not include an FCoE pinning configuration and is in the non-willing mode, and thus the switch device204amay not send an FCoE pinning configuration TLV communication to the switch device204c(e.g., as an FCoE pinning configuration cannot be added to a port of the switch device204a.) Thus, in the event the switch device204cincludes an FCoE pinning configuration, the switch device204cwill remove that FCoE pinning configuration as there is a mismatch in the FCoE pinning configuration that cannot be corrected.

For example, and with reference toFIGS. 11A and 11B, the switch device204cmay have an FCoE pinning configuration1102provided for the port coupled to the link212a. The switch device204cmay transmit the communication1104(e.g., an FCoE pinning configuration TLV communication) to the switch device204aand wait for a response. In this embodiment, an FCoE pinning configuration TLV communication is not received at the switch device204cdue to the switch device204abeing in the non-willing mode and not having an FCoE pinning configuration, and in response the switch device204cmay remove the FCoE pinning configuration1102as illustrated inFIG. 11B, and the VLT port channel214may be used for Ethernet traffic or other non-FCoE traffic.

Thus, systems and methods have been described that provide for FCoE pinning configuration mismatch and correction for switch devices in a VLT topology. In some embodiments, switch devices that include an FCoE pinning configuration will advertise that FCoE pinning configuration and whether that switch device is in a willing mode or a non-willing mode to peer switch devices. Furthermore, switch devices that do not include an FCoE pinning configuration will not send an advertisement and will instead wait for any advertisements from peer switch devices. In the event peer switch devices includes an FCoE pinning configuration, those the peer switch devices will advertise that FCoE pinning configuration and whether that peer switch device is in a willing mode or a non-willing mode. Furthermore, peer switch devices that do not include an FCoE pinning configuration will not send an advertisement, and will instead wait for any advertisements. The switch devices and/or peer switch devices may use the advertisement (or lack of advertisements received) to detect mismatches, reconfigure FCoE pinning configurations to correct mismatches, and/or remove FCoE pinning configurations in order to minimize problems associated with mismatched FCoE pinning configurations.