WO2014059590A1

WO2014059590A1 - Method and device for obtaining virtual link state

Info

Publication number: WO2014059590A1
Application number: PCT/CN2012/083006
Authority: WO
Inventors: 于来凯; 朱筠
Original assignee: 华为技术有限公司
Priority date: 2012-10-16
Filing date: 2012-10-16
Publication date: 2014-04-24
Also published as: CN103181187B; CN103181187A

Abstract

Disclosed are a method and device for obtaining virtual link state. An Ethernet fiber channel switch receives a link keep-alive message sent by a server. The Ethernet fiber channel switch analyses the link keep-alive message to obtain the identification information of the normal virtual link in the link keep-alive message; the Ethernet fiber channel switch determines the normal virtual link according to the identification information of the normal virtual link in the link keep-alive message. By improving the link keep-alive message sent by the prior server, and adding the identification information of the normal virtual link corresponding to the server in the message, the embodiments of the invention make the Ethernet fiber channel switch obtain the virtual link state according to link keep-alive message received, thus the amount of link keep-alive message sent via the virtual link is greatly reduced and the influence on the stability of the network is reduced.

Description

Method and device for knowing virtual link status

The present invention relates to the field of network technologies, and in particular, to a method and device for obtaining a virtual link state. Background technique

FCOE (Fiber Channel over Ethernet) network can support multiple FCFs

(FCOE Forwarder, FCOE switch) NE node, with the continuous expansion of cloud computing services, FCF as a sink node, at least support thousands or even tens of thousands of servers to access, each server can set multiple virtual links To meet business needs.

In the existing standard, each virtual link needs to periodically send a keepalive (link keepalive) message to the FCF. The FCF periodically monitors the packet to detect whether the status of the virtual link is normal. If the virtual link status of the virtual link is abnormal, the FCF deletes the virtual link and terminates the connection.

However, for the cloud computing service, each FCF can access thousands of servers, and each server can set dozens or even hundreds of virtual links. If the FCF needs to be processed periodically according to existing standards. The number of keepalive packets is hundreds of thousands. Obviously, such a large number of keepalive messages far exceed the processing power of the FCF's CPU, and it will inevitably affect the stability of the network. Summary of the invention

In the embodiment of the present invention, a method and a device for obtaining a virtual link state are provided, which can reduce the number of keepalive packets in a large amount.

In order to solve the above technical problem, the embodiment of the present invention discloses the following technical solutions:

In a first aspect, a method for obtaining a virtual link status is provided, including:

The Ethernet Fibre Channel switch receives the link keep-alive message sent by the server;

The Ethernet Fibre Channel switch parses the link keep-alive packet to obtain the identifier information of the normal virtual link included in the link keep-alive packet;

The Ethernet Fibre Channel switch determines a normal virtual link according to the identification information of the normal virtual link included in the link keep-alive packet.

In combination with the foregoing aspect, in a first possible implementation manner, the Ethernet Fibre Channel switch receives The link keep-alive packet that is sent includes the identifier information of all normal virtual links of the server.

In a second aspect, another method for obtaining a virtual link state is provided, including:

The server generates a link keep-alive packet, where the link keep-alive packet includes the identifier information of the normal virtual link; the server sends the generated link keep-alive packet to the Ethernet Fibre Channel switch, The Ethernet Fibre Channel switch determines a normal virtual link according to the identification information of the normal virtual link included in the link keep-alive packet.

With reference to the foregoing second aspect, in a first possible implementation manner, the link-preserving packet generated by the server includes identifier information of all normal virtual links of the server.

In a third aspect, an Ethernet Fibre Channel switch is provided, including:

a message receiving unit, configured to receive a link keep-alive message sent by the server;

a packet parsing unit, configured to parse the link keep-alive packet received by the packet receiving unit, and obtain identifier information of a normal virtual link included in the link keep-alive packet;

And a state determining unit, configured to determine a normal virtual link according to the identifier information of the normal virtual link included in the link keep-alive packet obtained by the packet parsing unit.

With reference to the foregoing third aspect, in a first possible implementation manner, the link keep-alive packet received by the packet receiving unit includes identifier information of all normal virtual links of the server.

In a fourth aspect, another Ethernet Fibre Channel switch is provided, including:

a transceiver, configured to receive a link keep-alive message sent by the server;

a processor, configured to parse the link keep-alive packet received by the transceiver, obtain identifier information of a normal virtual link included in the link keep-alive packet, and keep alive according to the link The identification information of the normal virtual link included in the packet determines the normal virtual link.

In a fifth aspect, a server is provided, including:

a message generating unit, configured to generate a link keep-alive packet, where the link keep-alive packet includes the identifier information of the normal virtual link;

a message sending unit, configured to send the link keep-alive message generated by the message generating unit to an Ethernet Fibre Channel switch, so that the Ethernet Fibre Channel switch keeps a message according to the link The identification information of the normal virtual link included in the normal link determines the normal virtual link.

With reference to the foregoing fifth aspect, in a first possible implementation manner, the link keep-alive packet generated by the packet generating unit includes identifier information of all normal virtual links of the server.

In a sixth aspect, another server is provided, including:

a processor, configured to generate a link keep-alive packet, where the link keep-alive packet includes an identifier of a normal virtual link Interest rate

a transceiver, configured to send the link keep-alive message generated by the processor to an Ethernet Fibre Channel switch, so that the Ethernet Fibre Channel switch according to the normality included in the link keep-alive message The identification information of the virtual link determines a normal virtual link.

The embodiment of the present invention improves the status of the virtual link by using the keepalive packet sent by the existing server, and adds the identifier of the normal virtual link in the packet to enable the FCF to know the status of the virtual link according to the received keepalive packet. Therefore, the keepalive packets sent by the virtual link are greatly reduced, and the impact on network stability is reduced. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic structural diagram of a keepalive packet sent by a server in the prior art;

2 is a schematic structural diagram of a keepalive packet sent by a virtual link in the prior art;

3 is a flowchart of a method for obtaining a virtual link state according to an embodiment of the present invention;

4 is a schematic structural diagram of a keepalive packet sent by a server according to an embodiment of the present invention;

FIG. 5 is a flowchart of another method for obtaining a virtual link state according to an embodiment of the present invention;

FIG. 6 is a flowchart of another method for obtaining a virtual link state according to an embodiment of the present invention;

7 is a schematic diagram of a packet sent by a server and a virtual link in the prior art;

8 is a schematic structural diagram of a message generated by a server in the embodiment shown in FIG. 6;

9 is a schematic diagram of a server sending a message in the embodiment shown in FIG. 6;

FIG. 10 is a schematic structural diagram of an FCF according to an embodiment of the present invention; FIG.

11 is a schematic structural diagram of another FCF according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a server according to an embodiment of the present invention; FIG.

FIG. 13 is a schematic structural diagram of another server according to an embodiment of the present invention. detailed description

In the FCOE network, there are two types of keepalive packets. One is the keepalive packet sent by the server. The packet structure is shown in Figure 1. The packet header includes FIP (FCOE Initialization Protocol, FCOE). Initialization Protocol) Message type (FIP_Type), version number (Version;), FIP code (FIP Code), sub-code (sub-code), FIP deep list length, FIP deep list length Carrying the MAC address (Medium Access Control) address description field of the server; the other is the keepalive packet sent by the virtual link. The packet structure is as shown in Figure 2, compared with the keepalive packet sent by the server. The keepalive packet sent by the virtual link carries the FIP Vx_Port Identification description field to identify the virtual link. In the prior art, according to the standard, each virtual link set on the server and the server periodically sends its own keepalive packets to the FCF. The FCF periodically monitors two types of keepalive packets to sense the server and its virtual link. If the FCF does not receive a keepalive packet sent by a certain server, the FCF will directly delete the server and terminate the connection. If the FCF exceeds a certain period, the virtual state is not received. If the link status is abnormal, the FCF will delete the virtual link and terminate the connection.

In the cloud computing service, the number of virtual links is very large. The packet storms generated by the keepalive packets sent by all the virtual link periods directly affect the stability of the network and are limited by the FCF processing capability. As a result, a single FCF cannot be expanded. If the FC0E switch agent or FCF is added, the network cost will be doubled.

Based on this, the embodiment of the present invention provides a method and a device for obtaining a virtual link state, and the identifier information of the normal virtual link in the server is added to the packet by improving the keepalive packet sent by the server. The FCF can learn the status of the virtual link according to the keepalive packets sent by the server, thereby greatly reducing the number of keepalive packets sent by the virtual link, reducing the impact on the network stability, and the FCF can be easily expanded. .

The above-mentioned objects, features, and advantages of the embodiments of the present invention will become more apparent and understood. Give further details.

Referring to FIG. 3, it is a flowchart of a method for obtaining a virtual link state according to an embodiment of the present invention.

The method can include:

Step 301: The FCF receives the keepalive packet sent by the server.

In the FCOE network, the virtual link is set by the server, and the number of virtual links that the server needs to be set, so that the server stores the information of each virtual link set by the server. In the embodiment of the present invention, the server is in the FCF. When the keepalive packet is sent, the identifier of the virtual link used by the server is added to the packet, that is, the identifier of the normal virtual link.

In a specific example, the structure of the keepalive message sent by the server may be as shown in FIG. 4. among them, The identifier information field of the normal virtual link is added after the MAC address description field of the packet, which may be a FIP Vx Port Identification description field. The difference between the packet and the keepalive packet sent by the virtual link in the prior art is that the packet sent by the virtual link in the prior art only includes the identifier information of the virtual link, for example, the FIP Vi_Port Identification description field is included. In the embodiment of the present invention, the keepalive packet sent by the server includes the identifier information of the normal virtual link, for example, the FIP Vi_Port Identification description field and the FIP V ₂ _Port Identification description field FIP V _n _Port Identification description field. The keepalive packet sent by the server may include the identifier information of multiple normal virtual links, so that the multiple normal virtual links do not need to send keepalive packets to the FCF period, thereby reducing the number of packets received by the FCF. Preferably, the keepalive packet sent by the server includes the identifier information of all the normal virtual links of the server, so that all normal virtual links under the server do not need to send keepalive packets to the FCF period, and only one server sends one Keepalive messages are fine.

After receiving the keepalive packet sent by the server, the FCF performs the next step.

Step 302: The FCF parses the keepalive packet to obtain the identifier information of the normal virtual link included in the keepalive packet.

The FCF parses the keepalive packet. The parsing process is the same as the parsing process in the prior art. The only difference is that the information obtained by the FCF parsing has the MAC address description field and the identity information of the normal virtual link.

Step 303: The FCF determines a normal virtual link according to the identifier information of the normal virtual link included in the keepalive packet.

After obtaining the identification information of the normal virtual link, the FCF can determine the normal virtual link.

The embodiment of the present invention improves the status of the virtual link by using the keepalive packet sent by the existing server, and adds the identifier of the normal virtual link in the packet to enable the FCF to know the status of the virtual link according to the received keepalive packet. Therefore, the keepalive packets sent by the virtual link are greatly reduced, and the impact on the network stability is reduced, and the FCF can be easily expanded.

FIG. 5 is a flowchart of another method for obtaining a virtual link state according to an embodiment of the present invention.

The difference between the embodiment of the present invention and the embodiment shown in FIG. 3 is that the peer end of the FCF, that is, the server side, is the execution subject, and the method may include:

Step 501: The server generates a keepalive packet, where the keepalive packet includes the identifier information of the normal virtual link.

Preferably, the server-generated keepalive packet includes identifier information of all normal virtual links of the server. Step 502: The server sends the generated keepalive packet to the FCF, so that the FCF determines the normal virtual link according to the identifier information of the normal virtual link included in the keepalive packet.

The embodiment of the present invention improves the identification information of the normal virtual link in the server by using the keepalive packet sent by the existing server, so that the FCF can obtain the virtual link according to the keepalive packet sent by the server. The state, which greatly reduces the keepalive packets sent by the virtual link, reduces the impact on the stability of the network, and the FCF can be easily expanded.

FIG. 6 is a flowchart of another method for obtaining a virtual link state according to an embodiment of the present invention.

In the embodiment of the present invention, three virtual links VI, V2, and V3 are set by the server as an example for description. According to the prior art solution, as shown in FIG. 7, the FCF needs to receive the keepalive message sent by the server, and the keepalive message sent by the virtual link VI, V2, and V3 respectively, for a total of four messages, and the FCF receives the message according to the FCF. The situation determines the state of each virtual link. In this embodiment, the method for determining the status of the virtual link may include:

Step 601: The server generates a keepalive packet.

The server uses the three virtual links VI, V2, and V3. That is, the three virtual links are in the normal state. The server adds the identification information of the virtual links VI, V2, and V3 to the V1_Port Identification descriptor V2_Port Identification. The descriptor V3_Port Identification descriptor generates a final keepalive packet. The structure of the packet can be as shown in Figure 8.

Step 602: The server sends the generated keepalive packet to the FCF.

In this embodiment, as shown in FIG. 9, only the server sends a keepalive message to the FCF, and the virtual link VI, V2, and V3 do not need to send a message.

Step 603: The FCF parses the received keepalive packet, and obtains the identifier information of the virtual link. Step 604: The FCF determines that the status of the virtual link corresponding to the obtained identification information is normal.

The embodiment of the present invention improves the identifier information of all the normal virtual links in the server by modifying the keepalive packets sent by the existing server, so that the FCF can obtain the virtual link according to the keepalive packets sent by the server. The status of the keepalive message is reduced by the FCF, which solves the problem that the massive keepalive packet affects the network stability in the FC0E network. With this method, a single FCF can be better expanded without being expanded. Because the number of keepalive packets is too large to be processed, the device must be added, which greatly reduces the network cost.

The above is a description of the embodiment of the method of the present invention. The apparatus for implementing the above method will be described below. Referring to FIG. 10, it is a schematic structural diagram of an FCF according to an embodiment of the present invention.

The FCF includes:

a message receiving unit 1001, configured to receive a keepalive message sent by the server; The message parsing unit 1002 is configured to parse the keepalive packet received by the packet receiving unit 1001, and obtain the identifier information of the normal virtual link included in the keepalive packet;

The state determining unit 1003 is configured to determine a normal virtual link according to the identifier information of the normal virtual link included in the keepalive packet obtained by the packet parsing unit 1002.

The keepalive packet received by the packet receiving unit 1001 may include identifier information of all normal virtual links of the server.

In the embodiment of the present invention, the FCF obtains the identifier information of the normal virtual link in the packet, and the state of the virtual link is obtained, thereby greatly reducing the keepalive packet received by the FCF. The impact on network stability, and thus the FCF can be easily expanded.

Referring to FIG. 11, a schematic structural diagram of another FCF according to an embodiment of the present invention is shown.

The FCF can include:

The transceiver 1101 is configured to receive a keepalive packet sent by the server.

The processor 1102 is configured to parse the keepalive packet received by the transceiver 1101, obtain the identifier information of the normal virtual link included in the keepalive packet, and obtain the normal virtual content included in the keepalive packet. The identification information of the link determines the normal virtual link.

In the embodiment of the present invention, the FCF obtains the identity information of the virtual link in the packet, and the state of the virtual link is obtained, thereby greatly reducing the keepalive packet received by the FCF, and reducing the network. The effect of stability, and thus the FCF can be easily expanded.

Referring to FIG. 12, it is a schematic structural diagram of a server according to an embodiment of the present invention.

The server can include:

The message generating unit 1201 is configured to generate a keepalive packet, where the keepalive packet includes the identifier information of the normal virtual link.

The message sending unit 1202 is configured to send the keepalive message generated by the message generating unit 1201 to the FCF, so that the FCF determines the normal virtual link according to the identity information of the normal virtual link included in the keepalive message. .

The keepalive packet generated by the packet generating unit 1201 includes identifier information of all normal virtual links of the server.

In the embodiment of the present invention, the server improves the keepalive message sent by the existing server by using the foregoing unit, and adds the identifier information of the normal virtual link in the server, so that the FCF can be based on the keepalive message sent by the server. The status of the virtual link is known, which greatly reduces the number of keepalive packets sent by the virtual link, and reduces the impact on the stability of the network. Therefore, the FCF can be easily expanded. FIG. 13 is a schematic structural diagram of another server according to an embodiment of the present invention.

The server can include:

The processor 1301 is configured to generate a keepalive packet, where the keepalive packet includes the identifier information of the normal virtual link.

The transceiver 1302 is configured to send the keepalive packet generated by the processor 1301 to the FCF, so that the FCF determines a normal virtual link according to the identifier information of the normal virtual link included in the keepalive packet. .

In the embodiment of the present invention, the server improves the identifier information of the normal virtual link in the server by modifying the keepalive packet sent by the existing server, so that the FCF can know according to the keepalive packet sent by the server. The state of the virtual link greatly reduces the number of keepalive packets sent by the virtual link, which reduces the impact on the stability of the network. Therefore, the FCF can be easily expanded.

One of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as a stand-alone product, Stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a Read-Only Memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Rights request

A method for obtaining a virtual link state, which is characterized by comprising:

The method according to claim 1, wherein the link keep-alive packet received by the Ethernet Fibre Channel switch includes identification information of all normal virtual links of the server.

3. A method for obtaining a virtual link state, the method comprising:

The server generates a link keep-alive packet, where the link keep-alive packet includes the identifier information of the normal virtual link.

Sending, by the server, the generated link keep-alive message to the Ethernet Fibre Channel switch, so that the Ethernet Fibre Channel switch according to the normal virtual link identifier information included in the link keep-alive packet Determine the normal virtual link.

The method according to claim 3, wherein the link keep-alive packet generated by the server includes identification information of all normal virtual links of the server.

5. An Ethernet Fibre Channel switch, comprising:

The Ethernet Fibre Channel switch according to claim 5, wherein the link keep-alive packet received by the packet receiving unit includes identification information of all normal virtual links of the server. .

7. An Ethernet Fibre Channel switch, comprising:

8. A server, comprising:

The server according to claim 8, wherein the link keep-alive packet generated by the packet generating unit includes identification information of all normal virtual links of the server.

10. A server, comprising:

a processor, configured to generate a link keep-alive packet, where the link keep-alive packet includes the identifier information of the normal virtual link;