CN102045603B - Negotiation method of fiber channel (FC) port and FC exchanger system - Google Patents

Abstract

The invention discloses a fiber channel (FC) port negotiation method and a fiber channel switch system. The present invention adds a mixed-mode virtual storage area network (VSAN) capability for the exchange of virtual fiber channel parameters (EVFP) negotiation. When the FC port local end and the opposite end are configured with Multi mode at the same time, if the opposite end VF_ID is consistent with the local end, and If there is a common trunk (Trunk) VSAN with the remote end, the mixed mode negotiation result can be obtained, and it is determined that the FC packets are transmitted without the VSAN extension header in the VSAN to which the VF_ID of the local end belongs. FC packets are transmitted in the VSAN with VSAN extended packet headers. At this time, the FC port can be made to support both a tagging (Tagging) mode and a non-tagging (Non-Tagging) mode, thereby improving the versatility of the FC port.

Description

Fiber channel port negotiation method and fiber channel switch system

technical field

The present invention relates to a Fiber Channel (Fibre Channel, FC) port initialization technology, in particular to an FC port negotiation method and an FC switch system capable of realizing FC port negotiation.

Background technique

With the continuous growth of Internet applications, the network server needs to store more and more information and data, which leads to the continuous increase of the storage capacity required by the network server. When the internal storage capacity of the web server cannot meet the demand of information growth, it is necessary to "externalize" the storage of the web server. In order to solve this problem, the existing technology proposes storage area network (Storage Area Networks, SAN), SAN can provide a dedicated external storage environment for network servers, make full use of new storage hardware technology and network technology, and meet the needs of large capacity and high reliability. Data storage, access and backup requirements. Among them, the FC protocol is the most widely used protocol in SAN. The FC protocol first appeared in the 1990s, with the purpose of providing higher-speed and more efficient large data transmission performance than the Ethernet and TCP/IP protocols.

Furthermore, in order to divide the SAN, the prior art proposes the concept of a virtual storage area network (VSAN), that is, to divide the SAN into multiple VSANs, and only the network servers and storage devices belonging to the same VSAN can pass through the FC The switch communicates. Wherein, the FC switch described in this article refers to a switch supporting the FC protocol, which can be a switch in a FC network, or a switch in a Fiber Channel Over Ethernet (FCoE) network over Ethernet, or a switch in a Fiber Channel Over Ethernet (FCoE) network. It is another switch that supports the FC protocol.

Specifically, in order to realize the transmission of FC packets in different VSANs, the following two methods are proposed in the prior art:

Method 1: Add a VSAN extension header (Virtual Fabric TaggingHeader, VFT_Header) to the FC message, and set the Virtual Fabric Identifier (VF_ID) field indicating the VSAN to which the FC message belongs, in the VFT_Header, the FC switch After receiving the FC message, check the VF_ID field in the VFT_Header of the FC message, and the transmission of the FC message can be limited to the VSAN to which it belongs, so as to ensure that different VSANs cannot communicate with each other, and thus achieve the physical connection of the network , but for logically isolated purposes.

For this method, you need to configure the trunk virtual storage area network (Trunk VSAN) list on each FC switch, and configure the trunk mode to be enabled (On). When the FC switch and the peer FC switch have a common Trunk VSAN, that is When the Trunk VSAN lists of the FC ports at both ends overlap, the FC ports connected to the two FC switches can perform Exchange Virtual Fiber Tagging) mode negotiation results, in Tagging mode, FC packets belonging to different VSANs can be transmitted in the common Trunk VSAN with VFT_Header.

Referring to Figure 1, it is assumed that there are network server 1 and disk 1 belonging to VSAN10, and network server 2 and disk 2 belonging to VSAN20, and the connections between network server 1 and disk 1 and between network server 2 and disk 2 pass through FC switch 1 in sequence Connect to FC switch 2.

FC switch 1 and FC switch 2 have a common Trunk VSAN10 and VSAN 20, therefore, after network server 1 sends an FC message without VFT_Header to the FC port of VF_ID10 of FC switch 1, FC switch 1 adds the FC message containing The VFT_Header of VF_ID10 is then sent to the peer FC switch 2, and the FC switch 2 can forward the received FC packet to disk 1 belonging to the same VSAN10 as the FC packet according to the VF_ID10 in the VFT_Header of the FC packet, and Remove the VFT_Header of the FC message when sending to the disk; after the network server 2 sends the FC message without VFT_Header to the FC port of the VF_ID20 of the FC switch 1, the FC switch 2 adds the VFT_Header containing VF_ID20 for the FC message, and then Then send it to the peer FC switch 2. According to the VF_ID20 in the VFT_Header of the FC message, the FC switch 2 can forward the received FC message to the disk 2 that belongs to the same VSAN20 as the FC message, and send it to the disk. Remove the VFT_Header of the FC packet. Similarly, only the transmission directions from disk 1 and disk 2 to network server 1 and network server 2 are different, and the processing methods of FC switch 1 and FC switch 2 are reversed, and the specific processing process is consistent with the above description.

Method 2. If none of the FC packets carries a VFT_Header, the interconnected FC ports of all FC switches in the VSAN must be configured with the VF_ID of the VSAN. Correspondingly, for each FC switch, the FC packets belong to The VSAN is determined by the VF_ID configured on the FC port receiving the FC packet.

For this method, when performing EVFP negotiation, the FC ports interconnected by every two FC switches belonging to the same VSAN need to be pre-configured as the same VF_ID to pass the negotiation and obtain the negotiation result of the non-tagging (Non Tagging) mode; If the VF_ID of an FC port is inconsistent with that of the remote end, the negotiation fails, that is, the link cannot be established.

Referring to Figure 2, suppose there is a network server 1 and disk 1 belonging to VSAN10, and the network server 1 and disk 1 are connected through FC switch 1 and FC switch 2 in sequence. When network server 1 sends an FC message without VFT_Header, the FC message After the message, FC switch 1 forwards the FC message through the FC port configured with VF_ID10 on the other side to the opposite FC port of switch 2 configured with VF_ID10 according to the VF_ID10 configured on the FC port receiving the FC message to indicate VSAN10 ; The FC switch 2 forwards the FC message to the disk 1 through the FC port configured with VF_ID10 on the other side according to the VF_ID10 configured on the FC port receiving the FC message and representing the VSAN10. Similarly, the transmission of FC packets without VFT_Header from disk 1 to network server 1 is only different in the transmission direction, and the specific processing process is consistent with the above description.

Although the above two methods can realize the transmission of FC packets of different VSANs, after EVFP negotiation, the FC ports either only support the transmission of FC packets with VFT_Header, or only support the transmission of FC packets without VFT_Header, that is, they cannot Supports two types of FC packet transmission at the same time. Moreover, if multiple VSANs need to be supported, FC packets must carry a VFT_Header. In this case, for FC ports that only support the transmission of FC packets without VFT_Header, even if the transmission between FC ports with the same VF_ID The FC message must also carry the VFT_Header, so the process of adding and removing the VFT_Header for the FC port directly connected to the network server and disk is also added.

It can be seen that the existing EVFP negotiation process of the FC port makes the universality of the FC port not high.

Contents of the invention

In view of this, the present invention provides an FC port negotiation method and an FC switch system, which can improve the versatility of the FC port.

A kind of FC port negotiation method provided by the present invention, set mixed Multi mode for exchanging virtual fiber channel parameter EVFP negotiation, described Multi mode can support label Tagging mode and non-label Non Tagging mode at the same time, and in EVFP negotiation process, After the local FC port configured with Multi mode learns that the remote FC port is also configured with Multi mode:

Determine whether the virtual storage area network identifier VF_ID of the opposite end FC port is consistent with the local end, and whether there is a common trunk virtual storage area network Trunk VSAN with the opposite end FC port;

If the VF_ID of the remote FC port is the same as that of the local end, and there is a common Trunk VSAN with the remote FC port, the negotiation result of the Multi mode is obtained, and it is determined that the VF_ID of the local end does not have the extended VFT_Header of the VSAN. FC packets are transmitted in the way of VFT_Header in the public trunk VSAN;

If the VF_ID of the remote FC port is different from that of the local end, but there is a common Trunk VSAN with the remote FC port, then the Tagging mode negotiation result is obtained, and it is determined that FC packets are only transmitted in the public Trunk VSAN with VFT_Header;

If the VF_ID of the remote FC port is the same as that of the local end, but there is no common Trunk VSAN with the remote FC port, the negotiation result of the Non Tagging mode is obtained, and it is determined that the VF_ID of the local end does not have a VFT_Header. Transmit FC message;

If the VF_ID of the remote FC port is different from that of the local end, and the remote FC port is not configured with a public trunk VSAN list, the negotiation fails.

When the VF_ID of the remote FC port is the same as that of the local end and there is a common TrunkVSAN with the remote FC port, if the VF_IDs of the local and remote FC ports belong to the VSAN and belong to the common Trunk VSAN, the VF_ID of the local FC packets are preferentially transmitted without VFT_Header.

The FC port configured with Multi mode on the local end receives the EVFP packet sent by the peer FC port during the EVFP negotiation process. The Message Payload of the EVFP packet sequentially carries the tag management status Tagging Adminidstative indicating the mode configured by the peer end. The Status descriptor, the port VF_ID descriptor representing the peer VF_ID, and the VF_ID list descriptor representing the Trunk VSAN list configured by the peer;

The FC port that received the EVFP message identifies whether the peer FC port is configured with Multi mode according to the Tagging Adminidstative Status descriptor, judges whether the peer VF_ID is consistent with the local port according to the port VF_ID descriptor, and judges whether the peer VF_ID is consistent with the local end according to the Trunk in the VF_ID list descriptor. Check whether the VSAN list overlaps with the local Trunk VSAN list to determine whether there is a common Trunk VSAN with the remote FC port.

The Tagging Adminidstative Status descriptor includes the Administrative Tagging Mode field;

The FC port that receives the EVFP message judges whether the peer FC port is configured with Multi mode according to the value of the Administrative Tagging Mode field;

The Administrative Tagging Mode field has the following optional values:

Indicates the first value of the Non Tagging mode;

Indicates the second value of the Tagging mode;

Indicates the third value of the automatic AUTO mode, and the AUTO mode indicates that as long as one end is configured with the Tagging mode, it can also support the Tagging mode;

Indicates the fourth value of the Multi mode.

The first to fourth values are sequentially: 00000001h, 00000002h, 00000003h, 00000004h.

A FC switch system provided by the present invention includes several FC switches, and each FC switch has an FC port,

Any FC switch is configured with a FC port in the preset hybrid multi mode. After learning that the peer FC port is also configured with the Multi mode during the EVFP negotiation process of exchanging virtual fiber channel parameters, determine the VSAN identifier VF_ID of the peer FC port. Whether the local end is the same, and whether there is a common trunk virtual storage area network Trunk VSAN with the remote FC port; among them, the Multi mode means that the tagging mode and non-tagging mode can be supported at the same time;

If the VF_ID of the remote FC port is the same as that of the local end, and there is a common Trunk VSAN with the remote FC port, the negotiation result of the Multi mode is obtained, and it is determined that the VF_ID of the local end does not have the extended VFT_Header of the VSAN. FC packets are transmitted in the way of VFT_Header in the public trunk VSAN;

If the VF_ID of the remote FC port is different from that of the local end, but there is a common Trunk VSAN with the remote FC port, then the Tagging mode negotiation result is obtained, and it is determined that FC packets are only transmitted in the public Trunk VSAN with VFT_Header;

If the VF_ID of the remote FC port is the same as that of the local end, but there is no common Trunk VSAN with the remote FC port, the negotiation result of the Non Tagging mode is obtained, and it is determined that the VF_ID of the local end does not have a VFT_Header. Transmit FC message;

If the VF_ID of the remote FC port is different from that of the local end, and the remote FC port is not configured with a public trunk VSAN list, the negotiation fails.

If the VF_ID of the remote FC port is the same as that of the local end, and there is a common TrunkVSAN with the remote FC port, and the VSAN to which the same VF_ID belongs also belongs to the common Trunk VSAN, then the FC packets in the VSAN to which the local VF_ID belongs are prioritized. It is transmitted without VFT_Header.

Any FC switch configured with a preset Multi mode FC port receives an EVFP packet sent by the peer FC port during EVFP negotiation. The state Tagging AdminidstativeStatus descriptor, the port VF_ID descriptor representing the peer VF_ID, and the VF_ID list descriptor representing the Trunk VSAN list configured by the peer;

The FC port that received the EVFP message identifies whether the peer FC port is configured with Multi mode according to the Tagging Adminidstative Status descriptor, judges whether the peer VF_ID is consistent with the local port according to the port VF_ID descriptor, and judges whether the peer VF_ID is consistent with the local end according to the Trunk in the VF_ID list descriptor. Check whether the VSAN list overlaps with the local Trunk VSAN list to determine whether there is a common Trunk VSAN with the remote FC port.

The Tagging Adminidstative Status descriptor includes the Administrative Tagging Mode field;

The FC port that receives the EVFP message judges whether the peer FC port is configured with Multi mode according to the value of the Administrative Tagging Mode field;

The Administrative Tagging Mode field has the following optional values:

Indicates the first value of the Non Tagging mode;

Indicates the second value of the Tagging mode;

Indicates the third value of the automatic AUTO mode, and the AUTO mode indicates that as long as one end is configured with the Tagging mode, it can also support the Tagging mode;

Indicates the fourth value of the Multi mode.

The first to fourth values are sequentially: 00000001h, 00000002h, 00000003h, 00000004h.

It can be seen from the above technical solution that the present invention adds a Multi mode VSAN capability for EVFP negotiation, and the Multi mode indicates that it can support Tagging mode and Non Tagging mode at the same time; If the VF_ID of the FC port on the local end is the same as that of the local end, and there is a common Trunk VSAN with the FC port on the remote end, the FC packets in the VSAN to which the VF_ID of the local end and the remote end belong can be identified and forwarded by using the VF_ID of the FC port, and The local end and the remote end have a common Trunk VSAN that can transmit FC packets with VFT_Header, so the negotiation result of the Multi mode can be obtained through EVFP negotiation, and the VF_ID of the local end belongs to the VSAN without VFT_Header. Transmit FC packets, and transmit FC packets with VFT_Header in the public trunk VSAN. At this point, the FC port can support both the Tagging mode and the Non-Tagging mode, thereby improving the versatility of the FC port.

Further, the present invention can realize above-mentioned scheme by improving the structure of EVFP protocol message, because the improvement to EVFP protocol message can utilize the part resource of existing EVFP protocol message, and need not carry out too much improvement to EVFP negotiation process, Therefore, the technical solution of the present invention is easy to realize.

Description of drawings

FIG. 1 is a schematic diagram of an existing FC switch transmitting packets in an unlabeled mode;

Fig. 2 is the schematic diagram that existing FC switchboard transmits message in label mode;

Fig. 3 is the exemplary flowchart of FC port negotiation method in the embodiment of the present invention;

Fig. 4 is the schematic diagram that FC switch transmits message in mixed mode in the embodiment of the present invention;

Fig. 5 is a schematic diagram of a message load structure of an EVFP protocol message in an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a label management status descriptor in the message load shown in FIG. 5;

FIG. 7 is a schematic diagram of examples of values that can be selected for the management tag mode field in the descriptor shown in FIG. 6 .

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples.

In this embodiment, a hybrid (Multi) mode VSAN capability is added for EVFP negotiation, and the Multi mode indicates that the Tagging mode and the Non-Tagging mode can be supported at the same time. Of course, this embodiment does not simply obtain the EVFP negotiation result of the Multi mode after the FC ports at both ends are configured with the Multi mode at the same time, but needs to perform a series of conditional judgments before determining whether to obtain the EVFP negotiation result of the Multi mode .

Fig. 3 is an exemplary flow chart of the FC port negotiation method in the embodiment of the present invention. As shown in Figure 3, the FC port negotiation method in this embodiment includes the following steps in the EVFP negotiation process:

In step 301, the FC port and the peer FC port exchange their respective VF_IDs, Trunk VSAN lists, and configured modes.

In step 302 , the FC port judges whether the local FC port and the remote FC port are configured with Multi mode, and if so, executes step 303 , otherwise executes step 307 .

Step 303, after the FC port configured with Multi mode on the local end learns that the FC port at the opposite end is also configured with Multi mode, determine whether the VF_ID of the FC port at the opposite end is consistent with the local end, and whether there is a common Trunk VSAN with the FC port at the opposite end. Wherein, in this step, it is judged whether there is a common Trunk VSAN between the local end and the opposite end FC port, which can be realized by comparing whether there is an intersection between the local end Trunk VSAN list and the opposite end Trunk VSAN list;

If the VF_ID of the remote FC port is the same as that of the local end, and there is a common Trunk VSAN with the remote FC port, it means that the FC packets in the VSAN to which the VF_ID of the local end and the remote end belong can be identified and forwarded by using the VF_ID of the FC port , and there is a public Trunk VSAN capable of transmitting FC packets with VFT_Header between the local end and the opposite end, so the Multi mode can be implemented and step 304 is executed;

If the VF_ID of the remote FC port is different from that of the local end, but there is a common Trunk VSAN with the remote FC port, it means that the local and remote VF_IDs are inconsistent and cannot be identified and forwarded by the VF_ID of the FC port. There is a public Trunk VSAN that can transmit FC packets with VFT_Header, so it is necessary to degenerate the Multi mode to the Tagging mode, and perform step 305;

If the VF_ID of the remote FC port is the same as that of the local end, but there is no common Trunk VSAN with the remote FC port, it means that the VF_ID of the FC port can be used to identify and Forwarding, but there is a public Trunk VSAN that can transmit FC packets with VFT_Header between the local end and the peer end, so it is necessary to degenerate the Multi mode to the Non Tagging mode and perform step 306;

If the VF_ID of the opposite end FC port is different from that of the local end, and the opposite end FC port is not configured with a public Trunk VSAN list, then the negotiation fails and directly ends this process (not shown in Figure 3).

Step 304: Obtain the negotiation result of the Multi mode through EVFP negotiation, and the local FC port and the remote FC port configured with the Multi mode determine to transmit the FC message without VFT_Header in the VSAN to which the local and remote VF_IDs belong 1. Transmit the FC message with the VFT_Header in the public Trunk VSAN, and then end this process.

In this step, there is a special case, that is, the VF_ID of the local end and the remote end belong to the VSAN, and at the same time belong to the public trunk VSAN. In this case, for the FC packets in the VSAN to which the local VF_ID It is transmitted in the form of the VSAN extended header VFT_Header.

Step 305: Obtain the negotiation result of the Tagging mode through EVFP negotiation, and determine that the local FC port and the remote FC port configured with Multi mode only transmit FC packets with VFT_Header in the public trunk VSAN, and then end this process .

Step 306: Obtain the negotiation result of the Non Tagging mode through EVFP negotiation, and determine that the local FC port and the remote FC port configured with the Multi mode only transmit the FC in the VSAN to which the VF_ID of the local end and the remote end belong without VFT_Header message, and then end this process.

Step 307, obtain the negotiation result of the Tagging mode or the Non-Tagging mode according to the existing method, that is, if both the local end and the opposite end are configured with the Tagging mode, obtain the negotiation result of the Tagging mode, the local FC port and the opposite end configured with the Tagging mode The FC port is determined to only transmit FC packets with VFT_Header in the public TrunkVSAN, that is, if both the local end and the remote end are configured with Non Tagging mode, the negotiation result of the Non Tagging mode is obtained, and the local FC port configured with the Non Tagging mode The FC port at the opposite end determines to transmit FC packets only in the VSAN to which the consistent VF_ID belongs without VFT_Header, and then ends this process.

So far, this process ends.

Based on the above method, a Fiber Channel FC switch system in this embodiment includes several FC switches, and each FC switch has an FC port, wherein,

If the local FC port of any FC switch is not configured with the aforementioned Multi mode, or the remote FC port is not configured with the aforementioned Multi mode, it can be processed according to the existing method, that is, if both the local end and the remote end are configured with Tagging Mode negotiation results, the local FC port configured with Tagging mode and the remote FC port are determined to only transmit FC packets with VFT_Header in the public trunk VSAN, that is, if both the local end and the remote end are configured with Non Tagging mode When the negotiation result of the Non-Tagging mode is obtained, the local FC port configured with the Non-Tagging mode and the remote FC port are determined to only transmit FC packets in the VSAN to which the VF_ID belongs without the VFT_Header extension of the VSAN.

However, the difference from the existing technology is that any FC switch is configured with the FC port in the aforementioned Multi mode. After learning that the peer FC port is also configured with the Multi mode during the EVFP negotiation process, it is determined whether the VF_ID of the peer FC port is consistent with that of the local end. Consistent, and whether there is a common Trunk VSAN with the peer FC port;

If the VF_ID of the remote FC port is the same as that of the local end, and there is a common Trunk VSAN with the remote FC port, the negotiation result of the Multi mode is obtained, and it is determined that the VF_ID of the local end belongs to the VSAN without VFT_Header. In this case, there may be a special case, that is, if the same VF_ID belongs to the VSAN and also belongs to the public Trunk VSAN, then the FC packet in the VSAN to which the local VF_ID belongs Files are preferentially transmitted without the VFT_Header extended VSAN header.

If the VF_ID of the remote FC port is different from that of the local end, but there is a common Trunk VSAN with the remote FC port, the negotiation result of the Tagging mode is obtained, that is, the Multi mode is degraded to the Tagging mode, and it is determined that only in the public Trunk VSAN with VFT_Header way to transmit FC message;

If the VF_ID of the remote FC port is the same as that of the local end, but there is no common Trunk VSAN with the remote FC port, then the negotiation result of the Non Tagging mode is obtained, that is, the Multi mode is reduced to the Non Tagging mode, and only the VF_ID of the local end belongs FC packets are transmitted in VSAN without VFT_Header;

If the VF_ID of the remote FC port is different from that of the local end, and the remote FC port is not configured with a public trunk VSAN list, the negotiation fails.

In this way, based on the above method and system, it is possible for the FC port to support both the Tagging mode and the Non-Tagging mode, thereby improving the versatility of the FC port.

Referring to Figure 4, it is assumed that there are network server 1 and disk 1 belonging to VSAN10, and network server 2 and disk 2 belonging to VSAN20, and the connections between network server 1 and disk 1 and between network server 2 and disk 2 pass through FC switch 1 in sequence It is connected to FC switch 2. The VF_IDs of the FC ports of FC switch 1 and FC switch 2 belong to VF_ID10 of VSAN10.

After network server 1 sends an FC packet without VFT_Header to the FC port of VF_ID10 of FC switch 1, since the VF_ID of the FC port interconnected between FC switch 1 and FC switch 2 is VF_ID10 belonging to VSAN10, that is, the FC packet belonging to VSAN10 VFT_Header may not be included, so FC switch 1 forwards the FC message without VFT_Header through the FC port configured with VF_ID10 on the other side to Switch 2 is configured with the peer FC port with VF_ID10; FC switch 2 forwards the FC packet to the disk through the FC port configured with VF_ID10 on the other side according to the VF_ID10 configured on the FC port that receives the FC packet, representing VSAN10 1. Similarly, only the transmission direction is different from the disk 1 to the network server 1, and the specific processing process is consistent with the above description.

After network server 2 sends the FC packet without VFT_Header to the FC port of VF_ID20 of FC switch 1, since the VF_ID of the FC port interconnected between FC switch 1 and FC switch 2 is VF_ID10 belonging to VSAN10, that is, the FC packet belonging to VSAN20 It must have a VFT_Header, and FC switch 1 and FC switch 2 have a common Trunk VSAN20, so FC switch 1 adds a VFT_Header containing VF_ID20 to the FC message, and then sends it to the peer FC switch 2, and FC switch 2 according to The VF_ID20 in the VFT_Header of the FC packet can forward the received FC packet to Disk 2 that belongs to the same VSAN as the FC packet, and remove the VFT_Header of the FC packet when sending to Disk 2. Similarly, only the transmission direction is different from the disk 2 to the network server 2, the processing methods of the FC switch 1 and the FC switch 2 are reversed, and the specific processing process is consistent with the above description.

During the EVFP negotiation process of the above method and system, the local FC port and the peer FC port can exchange their respective VF_IDs, Trunk VSAN lists, and configured modes by exchanging EVFP protocol messages.

Referring to Figure 5, the message payload (Message Payload) of the EVFP message can successively carry the Tagging Adminidstative Status (Tagging Adminidstative Status) descriptor representing the mode configured by the peer, and the Port VF_ID (Port VF_ID) descriptor representing the peer VF_ID , and the VF_ID list (Locally-Enabled VF_ID List) descriptor representing the Trunk VSAN list configured by the peer;

In this way, the FC port that receives the EVFP packet can identify whether the peer FC port is configured with Multi mode according to the Tagging AdminidstativeStatus descriptor, judge whether the peer VF_ID is consistent with the local port according to the port VF_ID descriptor, and judge whether the peer VF_ID is consistent with the local port according to the VF_ID list descriptor. Check whether there is an intersection between the TrunkVSAN list and the local TrunkVSAN list to determine whether there is a common TrunkVSAN with the remote FC port.

Referring further to Fig. 6, the Tagging Adminidstative Status descriptor includes an Administrative Tagging Mode field;

Correspondingly, the FC port receiving the EVFP message can judge whether the peer FC port is configured with the Multi mode according to the value of the Administrative TaggingMode field.

Among them, the Administrative Tagging Mode field has the following optional values:

Indicates the first value of the Non Tagging mode;

Indicates the second value of the Tagging mode;

Indicates the third value of the automatic AUTO mode, and the AUTO mode indicates that as long as one end is configured with the Tagging mode, it can also support the Tagging mode;

Indicates the fourth value of the Multi mode.

Figure 7 shows an example of values that can be selected for the Administrative Tagging Mode field, that is, the first to fourth values are: 00000001h, 00000002h, 00000003h, 00000004h.

Of course, based on the above solution of this embodiment, those skilled in the art can also think of other ways to realize the exchange of the respective VF_ID, Trunk VSAN list, and configured modes between the local FC port and the peer FC port. This will not list them one by one.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. optical-fibre channel FC port negotiation method, it is characterized in that, EVFP consults to arrange mixing Multi pattern for exchange virtual fiber channel parameters, described Multi modal representation can have been supported label Tagging pattern and no label Non Tagging pattern simultaneously, and in the EVFP negotiations process, after the FC port that local terminal disposes the Multi pattern knows that opposite end FC port also disposes the Multi pattern:

Whether the virtual memory LAN sign VF_ID that judges opposite end FC port and local terminal be consistent and whether have public backbone virtual memory LAN Trunk VSAN with opposite end FC port;

If the VF_ID of opposite end FC port is consistent with local terminal and have public Trunk VSAN with opposite end FC port, then obtain the negotiation result of Multi pattern, and determine under local terminal VF_ID, to transmit the FC message, in public Trunk VSAN, transmit the FC message in the mode that has VFT_Header in the mode that does not have VSAN amplifying message head VFT_Header in the VSAN;

There is public Trunk VSAN if the VF_ID of opposite end FC port is different with local terminal with opposite end FC port, then obtains the negotiation result of Tagging pattern, and determine only in public Trunk VSAN, to transmit the FC message in the mode that has VFT_Header;

There is not public Trunk VSAN if the VF_ID of opposite end FC port is consistent with local terminal with opposite end FC port, then obtain the negotiation result of Non Tagging pattern, and determine only under local terminal VF_ID, to transmit the FC message in the mode that does not have VFT_Header in the VSAN;

If the VF_ID of opposite end FC port is different with local terminal and opposite end FC port does not dispose public Trunk VSAN tabulation, then consult failure.

2. machinery of consultation as claimed in claim 1, it is characterized in that, consistent with local terminal and when having public Trunk VSAN with opposite end FC port at the VF_ID of opposite end FC port, if VSAN belongs to public Trunk VSAN simultaneously again under the VF_ID of local terminal and opposite end FC port, then for the FC message in the VSAN under the local terminal VF_ID, preferentially transmit in the mode that does not have VSAN amplifying message head VFT_Header.

3. machinery of consultation as claimed in claim 1 or 2, it is characterized in that, the FC port that local terminal disposes the Multi pattern receives the EVFP message that opposite end FC port sends in the EVFP negotiations process, carry the tag control state Tagging Adminidstative Status descriptor of expression opposite end institute configuration mode, the port VF_ID descriptor of representing opposite end VF_ID and expression opposite end among the message load Message Payload of this EVFP message successively and dispose the VF_ID list descriptor of Trunk VSAN tabulation;

Receive the FC port of this EVFP message, whether dispose the Multi pattern according to Tagging Adminidstative Status descriptor identification opposite end FC port, judge according to port VF_ID descriptor whether opposite end VF_ID is consistent with local terminal, whether exist to occur simultaneously with local terminal Trunk VSAN tabulation according to the tabulation of the Trunk VSAN in the VF_ID list descriptor to judge whether to have public Trunk VSAN with opposite end FC port.

4. machinery of consultation as claimed in claim 3 is characterized in that, comprises Management label Mode A dministrative Tagging Mode field in the Tagging Adminidstative Status descriptor;

Receive the FC port of this EVFP message according to the value of Administrative Tagging Mode field, judge whether opposite end FC port disposes the Multi pattern;

Described Administrative Tagging Mode field has following selected value:

First value of expression Non Tagging pattern;

Second value of expression Tagging pattern;

The 3rd value of representing automatic AUTO pattern is also supported the Tagging pattern as long as described AUTO modal representation has an end to dispose the Tagging pattern thereupon;

The 4th value of expression Multi pattern.

5. machinery of consultation as claimed in claim 4 is characterized in that, described first to fourth value is followed successively by: 00000001h, 00000002h, 00000003h, 00000004h.

6. an optical-fibre channel FC switch system comprises some FC switches, and every FC switch has the FC port, it is characterized in that,

The FC switch is configured with the FC port of the default Multi of mixing pattern arbitrarily, know that opposite end FC port also disposes the Multi pattern in exchange virtual fiber channel parameters EVFP negotiations process after, whether the virtual memory LAN of judging opposite end FC port identifies VF_ID and local terminal consistent and whether have public backbone virtual memory LAN Trunk VSAN with opposite end FC port; Wherein, the Multi modal representation can have been supported label Tagging pattern and no label Non Tagging pattern simultaneously;

If the VF_ID of opposite end FC port is consistent with local terminal and have public Trunk VSAN with opposite end FC port, then obtain the negotiation result of Multi pattern, and determine under local terminal VF_ID, to transmit the FC message, in public Trunk VSAN, transmit the FC message in the mode that has VFT_Header in the mode that does not have VSAN amplifying message head VFT_Header in the VSAN;

There is public Trunk VSAN if the VF_ID of opposite end FC port is different with local terminal with opposite end FC port, then obtains the negotiation result of Tagging pattern, and determine only in public Trunk VSAN, to transmit the FC message in the mode that has VFT_Header;

There is not public Trunk VSAN if the VF_ID of opposite end FC port is consistent with local terminal with opposite end FC port, then obtain the negotiation result of Non Tagging pattern, and determine only under local terminal VF_ID, to transmit the FC message in the mode that does not have VFT_Header in the VSAN;

If the VF_ID of opposite end FC port is different with local terminal and opposite end FC port does not dispose public Trunk VSAN tabulation, then consult failure.

7. system as claimed in claim 6, it is characterized in that, if the VF_ID of opposite end FC port is consistent with local terminal, have public Trunk VSAN with opposite end FC port, and VSAN belongs to public Trunk VSAN simultaneously again under the VF_ID of described unanimity, then for the FC message in the VSAN under the local terminal VF_ID, preferentially transmit in the mode that does not have VSAN amplifying message head VFT_Header.

8. as claim 6 or 7 described systems, it is characterized in that, the FC switch configuration has the FC port of default Multi pattern to receive the EVFP message that opposite end FC port sends in the EVFP negotiations process arbitrarily, carries the tag control state Tagging Adminidstative Status descriptor of expression opposite end institute configuration mode, the port VF_ID descriptor of representing opposite end VF_ID and expression opposite end among the message load Message Payload of this EVFP message successively and disposes the VF_ID list descriptor of Trunk VSAN tabulation;

Receive the FC port of this EVFP message, whether dispose the Multi pattern according to Tagging Adminidstative Status descriptor identification opposite end FC port, judge according to port VF_ID descriptor whether opposite end VF_ID is consistent with local terminal, whether exist to occur simultaneously with local terminal Trunk VSAN tabulation according to the tabulation of the Trunk VSAN in the VF_ID list descriptor to judge whether to have public Trunk VSAN with opposite end FC port.

9. system as claimed in claim 8 is characterized in that, comprises Management label Mode A dministrative Tagging Mode field in the Tagging Adminidstative Status descriptor;

Receive the FC port of this EVFP message according to the value of Administrative Tagging Mode field, judge whether opposite end FC port disposes the Multi pattern;

Described Administrative Tagging Mode field has following selected value:

First value of expression Non Tagging pattern;

Second value of expression Tagging pattern;

The 3rd value of representing automatic AUTO pattern is also supported the Tagging pattern as long as described AUTO modal representation has an end to dispose the Tagging pattern thereupon;

The 4th value of expression Multi pattern.

10. system as claimed in claim 9 is characterized in that, described first to fourth value is followed successively by: 00000001h, 00000002h, 00000003h, 00000004h.

Images