WO2014029079A1 - PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE - Google Patents

PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE Download PDF

Info

Publication number
WO2014029079A1
WO2014029079A1 PCT/CN2012/080426 CN2012080426W WO2014029079A1 WO 2014029079 A1 WO2014029079 A1 WO 2014029079A1 CN 2012080426 W CN2012080426 W CN 2012080426W WO 2014029079 A1 WO2014029079 A1 WO 2014029079A1
Authority
WO
WIPO (PCT)
Prior art keywords
fcoe
node
management server
network
link
Prior art date
Application number
PCT/CN2012/080426
Other languages
English (en)
Chinese (zh)
Inventor
李科
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201280002786.XA priority Critical patent/CN103262470B/zh
Priority to PCT/CN2012/080426 priority patent/WO2014029079A1/fr
Publication of WO2014029079A1 publication Critical patent/WO2014029079A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/356—Switches specially adapted for specific applications for storage area networks
    • H04L49/357—Fibre channel switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route

Definitions

  • FCoE network link management method FCoE network link management method, device and system
  • the present invention relates to communication technologies, and in particular, to a FCoE network link management method, device and system. Background technique
  • Fibre Channel over Ethernet (FCoE) technology maps Fibre Channel to Ethernet and transmits Fibre Channel (FC) data over Ethernet. This allows the LAN to be transmitted over Ethernet. Local Area Network (LAN) data also transmits FC data, which facilitates multiple data transmission functions with fewer network infrastructure devices and reduces network costs.
  • FCoE Fibre Channel over Ethernet
  • FCoE Nodes a plurality of FCoE nodes (ie, FCoE Nodes) are included, and each FCoE node communicates through a lossless Ethernet switch, and multiple lossless Ethernet switches form a Lossless Ethernet.
  • each FCoE node needs to periodically detect the link status with other FCoE nodes.
  • the specific mode is as follows: Each FCoE node periodically broadcasts Beacon to other FCoE nodes in the network. The node identifier of the FCoE node of the Beacon is sent. When the other node receives the Beacon, it determines that the link to the FCoE node is normal and keeps the neighbor table information unchanged.
  • a neighbor table is maintained on each FCoE node. Maintain the node information of the normal link); If the Beacon is not received within the preset time, if the link to the FCoE node is disconnected, the FCoE node is deleted from the neighbor list. Since the above Beacon is periodically sent in the network, it can be called the network heart if mega.
  • each FCoE node in the FCoE network mainly detects the link state of the node by periodically performing Beacon broadcast.
  • the Beacon broadcast will cause broadcast storms in the FCoE network.
  • the Beacon broadcast occupies network bandwidth and affects network performance.
  • it will take a lot of time to detect the link status with other nodes and affect the normal operation of the FCoE node. Summary of the invention
  • the present invention provides an FCoE network link management method, device and system, which reduces the network bandwidth occupied by the heartbeat of the FCoE network and reduces the burden on the FCoE node.
  • an FCoE network link management method including:
  • the FCoE node periodically sends a data packet Beacon to the management server for maintaining the network link status of the device in a heartbeat manner, and the Beacon is configured to notify the management server that the local link is normally connected to the FCoE network;
  • the Beacon sent by the management server determines the link status of the management server in the FCoE network according to the Beacon sent by the management server;
  • the node change notification message carries node information of an FCoE node whose link state changes in the FCoE network, and the FCoE node whose link state changes is that the management server detects the FCoE network.
  • the Beacon determined by the FCoE node is determined;
  • a local neighbor table is updated, and the neighbor table is used to record node information of other FCoE nodes that can establish a link with the FCoE node.
  • the node change notification message carries the node information of the FCoE node whose link state changes in the FCoE network, specifically:
  • the node change notification message carries a node identifier of the FCoE node that is disconnected and a link disconnection identifier, and the node change notification message is that the management server does not receive the FCoE node within a preset time set by the management server. Sent when sending Beacon;
  • the local neighbor table specifically: according to the node identifier of the FCoE node that is disconnected and the link disconnection identifier, disconnecting the node identifier of the linked FCoE node from the local neighbor table Deleted.
  • the node change notification message carries the node information of the FCoE node whose link state changes in the FCoE network, specifically:
  • the node change notification message carries a node identifier of the FCoE node newly added to the FCoE network and a link establishment identifier; the node change notification message is that the management server carries the Beacon carried by the FCoE node that is received by the management server.
  • the node identifier is sent when first received; the local neighbor table is updated according to the node information, specifically: according to the new addition to the The node identifier of the FCoE node of the FCoE network and the link establishment identifier are added, and the node identifier of the FCoE node newly added to the FCoE network is added to the local neighbor table.
  • the method further includes:
  • the identifier of the management server is recorded in the local neighbor table, and the Beacon is periodically sent to the management server according to the identifier of the management server.
  • the first possible implementation of the first aspect, or the second possible implementation of the first aspect a fourth possible implementation manner of the first aspect is also provided. Determining, by the Beacon according to the management server, a link status of the management server in the FCoE network, including:
  • the Beacon sent by the management server is not received within the preset time set by the timer, determining that the management server is disconnected from the FCoE network, and the identifier of the management server is localized. Deleted in the neighbor table.
  • an FCoE network link management method including:
  • the management server periodically broadcasts a data packet Beacon for maintaining the network link status of the device in a heartbeat manner to each FCoE node of the FCoE network, so that the FCoE node determines the link of the management server in the FCoE network according to the Beacon. And periodically detecting a Beacon sent by the FCoE node, and determining, according to the Beacon sent by the FCoE node, a link state of the FCoE node in the FCoE network;
  • the FCoE node When determining that the FCoE node has a link state change in the FCoE network, broadcasting a node change notification message to the FCoE network, where the node change notification message carries node information of the FCoE node whose link state changes, so that The other FCoE nodes in the FCoE network update the neighbor table of the other FCoE nodes according to the node information, where the other FCoE nodes are nodes in the FCoE network whose link status is normal and has not changed.
  • the determining, by the Beacon sent by the FCoE node, the link state of the FCoE node in the FCoE network specifically: if the timer is set If the Beacon sent by the FCoE node is not received within the preset time, it is determined that the FCoE node is disconnected in the FCoE network, and the FCoE node is disconnected.
  • the link state in the FCoE network is changed from normal to offline; the FCoE node whose link state changes is the FCoE node that is disconnected;
  • the node change notification message carries the node information of the FCoE node whose link status changes, and specifically: the node change notification message carries the node identifier of the FCoE node that is disconnected and the link disconnection identifier, so that the node change notification message
  • the other FCoE nodes in the FCoE network delete the node identifier of the FCoE node that is disconnected from the neighbor list.
  • the method before the periodically starting the timer to detect the Beacon sent by the FCoE node, the method further includes:
  • a third possible implementation manner of the second aspect is further provided, where determining, by the Beacon sent by the FCoE node, the FCoE node in FCoE
  • the link status in the network is specifically:
  • FCoE node If it is determined that the node identifier carried in the Beacon sent by the FCoE node is not stored in the local neighbor table, determining that the FCoE node is newly added to the FCoE node of the FCoE network, and the link status of the FCoE node in the FCoE network Changed from offline to normal; the FCoE node whose link status changes is the FCoE node newly added to the FCoE network;
  • the node change notification message carries the node information of the FCoE node whose link status changes, and specifically: the node change notification message carries a node identifier of the FCoE node newly added to the FCoE network, and a link establishment identifier, so that The other FCoE nodes in the FCoE network add the node identifier of the FCoE node to the neighbor table of the other FCoE node.
  • an FCoE node including:
  • a heartbeat interaction unit configured to periodically send, to the management server, a data packet, a beacon, for maintaining a network link state of the device in a heartbeat manner, where the Beacon is configured to notify the management server to be locally linked in the FCoE network;
  • the timer detects the Beacon sent by the management server, and determines, according to the Beacon sent by the management server, the link status of the management server in the FCoE network;
  • a message receiving unit configured to receive, when the link status of the management server is normal, a node change notification message broadcast by the management server on the FCoE network, where the node change notification message carries a link state change in the FCoE network Node information of the FCoE node, the FCoE node whose link state changes is determined by the management server by detecting a Beacon sent by the FCoE node in the FCoE network;
  • a neighbor management unit configured to update a local neighbor table according to the node information received by the message receiving unit, where the neighbor table is used to record node information of other FCoE nodes that can establish a link with the FCoE node.
  • the message receiving unit is configured to receive a node change notification message that is broadcast by the management server on the FCoE network, where the node change notification message is carried a node identifier of the linked FCoE node and a link disconnection identifier, where the node change notification message is sent by the management server when the Beacon sent by the FCoE node is not received within a preset time set by the management server;
  • the neighbor management unit is specifically configured to delete the node identifier of the FCoE node that is disconnected from the local neighbor list according to the node identifier of the FCoE node that is disconnected and the link disconnection identifier.
  • the message receiving unit is specifically configured to receive a node change notification message that is broadcast by the management server on the FCoE network, where the node change notification message carries a new message. Adding a node identifier of the FCoE node to the FCoE network and a link establishment identifier; the node change notification message is sent by the management server when determining that the received node identifier carried in the Beacon sent by the FCoE node is received for the first time ;
  • the neighboring management unit is specifically configured to add, according to the node identifier and the link establishment identifier of the FCoE node newly added to the FCoE network, the node identifier of the FCoE node newly added to the FCoE network to the local neighbor table. in.
  • the heartbeat interaction unit is further configured to: determine whether the management server exists before the beacon is periodically sent to the management server; and when the determination result is yes, execute the orientation according to the identifier of the management server.
  • the management server periodically sends a Beacon;
  • the neighbor management unit is further configured to: when the judgment result of the heartbeat interaction unit is yes, The identity of the management server is recorded in the local neighbor table.
  • the heartbeat interaction unit is further configured to: when the Beacon sent by the management server is not received within a preset time set by the timer, determine that the management server is disconnected from the FCoE network;
  • the neighbor management unit is further configured to: when the heartbeat interaction unit determines that the link between the management server and the management server is disconnected, delete the identifier of the management server from the local neighbor table.
  • a management server including:
  • a heartbeat interaction unit configured to periodically broadcast, to each FCoE node of the FCoE network, a data packet Beacon for maintaining a network link state of the device in a heartbeat manner, so that the FCoE node determines, according to the Beacon, that the management server is in FCoE a link state in the network; and periodically starting a timer to detect a Beacon sent by the FCoE node, and determining, according to the Beacon sent by the FCoE node, a link state of the FCoE node in the FCoE network;
  • a message sending unit configured to: when the heartbeat interaction unit determines that the FCoE node in the FCoE network has a link state change, broadcast a node change notification message to the FCoE network, where the node change notification message carries the link state Node information of the changed FCoE node, so that other FCoE nodes in the FCoE network update the neighbor table of the other FCoE node according to the node information, where the other FCoE nodes are link states in the FCoE network A node that is normal and has not changed.
  • the heartbeat interaction unit is configured to: when the Beacon sent by the FCoE node is not received within a preset time set by the timer, Determining that the link of the FCoE node in the FCoE network is disconnected, the link state of the FCoE node in the FCoE network is changed from normal to offline; and the FCoE node whose link state changes is the FCoE node that is disconnected from the link;
  • the message sending unit is specifically configured to broadcast a node change notification message to the FCoE network, where the node change notification message carries a node identifier of the FCoE node that is disconnected and a link disconnection identifier, so that the FCoE network
  • the other FCoE nodes in the node delete the node ID of the FCoE node that is disconnected from the neighbor table.
  • the heartbeat interaction unit is further used Receiving a Beacon or a Claim sent by the FCoE node, where the Beacon or the Claim carries a node identifier of the FCoE node;
  • the method further includes: a neighbor management unit, configured to receive the Beacon in the heartbeat interaction unit, or instruct the heartbeat interaction unit to restart a timer, and wait to receive the next Beacon sent by the FCoE node; otherwise, the local neighbor table The node identifier is recorded in .
  • a neighbor management unit configured to receive the Beacon in the heartbeat interaction unit, or instruct the heartbeat interaction unit to restart a timer, and wait to receive the next Beacon sent by the FCoE node; otherwise, the local neighbor table The node identifier is recorded in .
  • a third possible implementation manner of the fourth aspect is further provided, where the heartbeat interaction unit is further configured to determine, in the neighbor management unit When the node identifier carried in the Beacon sent by the FCoE node is not stored in the local neighbor table, the FCoE node is newly added to the FCoE node of the FCoE network, and the link state of the FCoE node in the FCoE network is changed offline. Normal; the FCoE node whose link status changes is the FCoE node newly added to the FCoE network;
  • the message sending unit is specifically configured to: broadcast a node change notification message to the FCoE network, where the node change notification message carries a node identifier of the FCoE node newly added to the FCoE network, and a link establishment identifier, so that the FCoE Other FCoE nodes in the network add the node id of the FCoE node to the neighbor table of the other FCoE node.
  • an Ethernet Fibre Channel FCoE network link management system comprising the FCoE node of the present invention, and the management server of the present invention.
  • an FCoE node comprising: at least one processor, and a memory coupled to the at least one processor; the at least one processor reading code in the memory, configured to perform the present invention Methods.
  • a management server at least one processor, and a memory coupled to the at least one processor; the at least one processor reading code in the memory, configured to perform the method of the present invention .
  • the FCoE node only needs to periodically exchange the Beacon detection link with the management server, compared with the existing
  • the way in which the FCoE nodes in the technology broadcast the Beacon on the FCoE network greatly reduces the amount of information in the FCoE network and reduces the occupation of the network bandwidth.
  • the FCoE node updates the local neighbor table according to the node change notification message sent by the management server. Compared with the Beacon of each other node detected by the node itself in the prior art, The burden on FCoE nodes is greatly reduced.
  • FIG. 1 is a schematic diagram of an application system architecture of an FCoE network link management method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an FCoE network link management method according to an embodiment of the present invention
  • 4 is a schematic flowchart of a management server in another embodiment of the FCoE network link management method according to the present invention
  • FCoE node in another embodiment of the FCoE network link management method according to the present invention
  • FCoE node 6 is a schematic structural diagram of an embodiment of an FCoE node according to the present invention.
  • FIG. 7 is a schematic structural diagram of an embodiment of a management server according to the present invention.
  • FCoE node 8 is a structural diagram of an entity of an embodiment of an FCoE node according to the present invention.
  • FIG. 9 is a structural diagram of an entity of an embodiment of a management server according to the present invention. detailed description
  • ENode1 E ENode6 are multiple FCoE nodes in an FCoE network, and the FCoE node may be, for example, a server or a memory. Or devices such as user terminals; communication between FCoE nodes can be achieved through an enhanced Ethernet switch in Lossless Ethernet.
  • a management server (Manager Server) is also provided, and each FCoE node can also communicate with the management server through an enhanced Ethernet switch in the lossless Ethernet.
  • the link state is maintained by periodically switching the Beacon between the management server and each FCoE node, and each FCoE node only needs to detect the link with the management server, without the need of the prior art.
  • the Beacon detection link must be used with all FCoE nodes in the FCoE network.
  • the Beacon is a special-purpose data packet used to maintain the network link status of the device that sends the data message in a heartbeat manner.
  • the special-purpose data message is simply referred to as Beacon; and, the management server notifies the FCoE node of the event change of the FCoE network, for example, a node is disconnected, and the FCoE node does not need to Detection also saves time on FCoE nodes, enabling FCoE nodes to be more Focus on other businesses.
  • Embodiment 1 The FCoE network link management method of the present invention will be described in detail below with reference to FIG. 1 : Embodiment 1
  • FIG. 2 is a schematic flowchart of an FCoE network link management method according to an embodiment of the present invention.
  • the method in this embodiment is performed by an FCoE node.
  • the method may include:
  • the Beacon is periodically sent to the management server, and the Beacon is periodically started to detect the Beacon sent by the management server, and the link status of the management server in the FCoE network is determined according to the Beacon sent by the management server.
  • each FCoE node and the management server periodically exchange Beacons to detect the link state of the other party in the FCoE network, and the link state is normal or offline, for example, if the link state of an FCoE node is normal.
  • the FCoE node periodically sends the Beacon, and the management server receives the Beacon, and can determine that the normal link of the FCoE node is on the network. If the FCoE node is offline, the FCoE node no longer sends the Beacon.
  • the server will not receive the Beacon of the FCoE node, and can determine that the FCoE node is disconnected from the network.
  • the FCoE node also determines the link status of the management server in the FCoE network according to the Beacon sent by the management server.
  • each FCoE node periodically sends a Beacon to the management server, where the Beacon carries the node identifier of the FCoE node, so as to notify the management server that the FCoE node is normally linked to the FCoE network, and the management server can receive the FCoE.
  • the Beacon sent by the node can determine that the FCoE node is normally linked to the FCoE network, that is, the link state of the FCoE node is normal; therefore, the management server can determine the link status of all the FCoE nodes by detecting whether the Beacon of each FCoE node is received. For example, normal or offline.
  • each FCoE node periodically detects the Beacon sent by the management server to determine whether the management server is normally linked to the FCoE network.
  • the Beacon is sent by the management server on the FCoE network broadcast, and the bearer of the management server is also carried.
  • the FCoE node identifies the Beacon sent by the management server by the identifier.
  • the FCoE node can start a timer. If the Beacon sent by the management server is received within the preset time set by the timer, it can be determined that the management server is normally linked to the FCoE network, that is, the link status of the management server is normal, and is updated. The timer waits to receive the Beacon for the next transmission. If the Beacon sent by the management server is not received within the preset time, the management server may have left the FCoE network, that is, the management service. The link is disconnected from the FCoE network, and the link status of the management server is offline.
  • the link state of the node is changed from offline to normal, that is, the FCoE node just establishes a link with the FCoE network
  • the node information includes the node identifier and the link establishment identifier; indicates the node identifier and the link state of the node
  • the node information of the FCoE node that the FCoE network leaves, and the change of the link state at this time refers to the link state of the FCoE node being changed from normal to offline, that is, the FCoE node is just disconnected from the FCoE network, and the node information includes the node. Identification and link disconnection ID.
  • the manner in which the FCoE node in the FCoE network detects the link state of each node changes with respect to the prior art.
  • each FCoE node needs to broadcast the Beacon in the FCoE network, so that each FCoE node performs Beacon detection on each other to confirm the link state between the nodes; in this embodiment, each FCoE node Only the unicast mode and the management server can be used to detect the link through the Beacon.
  • the link status of other nodes is determined by the management server through the Beacon sent by the detection node and notified to the FCoE node, for example, the management server and the FCoE. If the link between node A and FCoE node B is normal, the link between FCoE node A and FCoE node B is also normal.
  • the management server can change the link state of the FCoE node in the FCoE network. Notify all nodes. For example, when the management server does not receive the Beacon sent by the FCoE node A within the preset time, it determines that the FCoE node A disconnects the link, and broadcasts a node change notification message to the entire FCoE network, where the message carries the node identifier of the FCoE node A. And the link disconnection flag to inform other FCoE nodes that FCoE node A has broken the link.
  • the FCoE node Since the FCoE node only needs to interact with the management server Beacon, compared to the prior art broadcast Beacon on the FCoE network, the node burden is greatly reduced, and the FCoE node can focus on self.
  • the main service, and for the FCoE network, the Beacon is reduced, which also reduces the network bandwidth occupied by the Beacon and improves the network performance.
  • Each of the FCoE nodes maintains a neighbor table, which is used to record information about other nodes that can establish a link with the FCoE node, such as a node identifier, where only the neighbor node in the neighbor table is in the FCoE network.
  • the link state is normal, the FCoE node can establish a link with the other node, for example, each can send the beacon normally, and can receive the information sent by the other party; when the FCoE node receives the node change notification message broadcast by the management server When the node information of the FCoE node in the node change notification message is updated, the local neighbor table is updated.
  • the FCoE node that receives the node change notification message will query its local neighbor table, if the neighbor table has the disconnection.
  • the node identifier of the linked FCoE node for example, the FCoE node A disconnects, the node identifier of the FCoE node A is deleted from the local neighbor list, indicating that the link with the FCoE node A is disconnected; If there is no node identifier of the FCoE node A in the table, it indicates that there is no link between the local and the FCoE node A, and the neighbor table can be kept unchanged.
  • the FCoE node that receives the node change notification message will query its local neighbor table, if the neighbor table does not have the node identifier of the newly added FCoE node, and the local To establish a link with the newly added FCoE node, the node identifier newly added to the FCoE node can be added to the local neighbor table.
  • each FCoE node when an FCoE node disconnects from the FCoE network, it needs to be notified to each other FCoE node by the management server, because in the FCoE network, each FCoE node only works with the management server.
  • Unicast interaction Beacon each FCoE node does not interact with Beacon. Only the management server can detect whether an FCoE node has been disconnected. Therefore, the management server can only notify the FCoE network of the event that the node is disconnected. Each node in the middle. The event that a new FCoE node is added to the FCoE network is optionally notified by the management server.
  • the management server When the management server detects that a certain FCoE node is a newly added node, it can broadcast to other nodes; or, newly added The FCoE node can also be used in the Claim process before sending Beacon.
  • the middle broadcasts its own node ID broadcast to other nodes in the network.
  • FIG. 3 is a schematic flowchart of another embodiment of an FCoE network link management method according to the present invention.
  • the method in this embodiment is performed by a management server. As shown in FIG. 3, the method may include:
  • the Beacon is periodically broadcasted to each FCoE node of the FCoE network, and the timer is periodically started to detect the Beacon sent by the FCoE node, and the link status of the FCoE node in the FCoE network is determined according to the Beacon sent by the FCoE node.
  • the management server and each FCoE node periodically exchange the Beacon to detect the link state of the other party in the FCoE network.
  • the management server periodically broadcasts the Beacon to the entire FCoE network, and also detects the Beacon periodically sent by each FCoE node. .
  • the management server detects the Beacon sent by the FCoE node, it also detects by starting the timer. If the Beacon sent by the FCoE node is received within the preset time set by the timer, it indicates that the FCoE node is in the FCoE network link. Otherwise, it indicates that the FCoE node is down on the FCoE network link.
  • FCoE node When it is determined that the FCoE node has a link state change in the FCoE network, broadcast a node change notification message to the FCoE network, and carry the node information of the FCoE node whose link state changes.
  • the management server determines, according to the Beacon sent by the FCoE node, that the FCoE node changes the link state of the FCoE network, and notifies the FCoE network of the event that the link state changes. For example, when an FCoE node newly joins an FCoE network, the link state of the node changes from offline to normal; or, when the FCoE node leaves the FCoE network, the link state of the node changes from normal to offline.
  • the management server detects the Beacon of the FCoE node, it is found that an FCoE node such as FCoE node A has been disconnected, that is, the management server does not receive the Beacon sent by FCoE node A within the preset time set by the timer.
  • the management server will broadcast a node change notification message to the FCoE network, carrying the node identifier of the FCoE node A and the link disconnection identifier to notify other FCoE nodes in the network that the FCoE node A has disconnected.
  • Embodiment 3 The other FCoE nodes in the FCoE network will delete the node identifier of the disconnected FCoE node A from its neighbor list according to the node change notification message sent by the management server; the other FCoE nodes are links in the FCoE network. A node whose status has not changed.
  • the FCoE network link management method in this embodiment will be described in more detail below, and the respective workflows of the FCoE node and the management server will be described in two embodiments: Embodiment 3
  • FIG. 4 is a flowchart of a management server in another embodiment of the FCoE network link management method according to the present invention. As shown in FIG. 4, the execution process of the management server is as follows:
  • the management server completes the initialization work.
  • the initialization refers to the management server performing power-on, completing various preparations before the work, and entering the working state; and, the identifier of the management server may be configured in advance on the management server, for example, the management may be configured.
  • the address of the server is used as its identifier.
  • the management server periodically broadcasts the Beacon to the FCoE network.
  • the beacon transmission period can be preset. For example, the Beacon is sent every minute.
  • the Beacon transmission period here can be in the normal way. Beacon is also a regular format, but only carries the identity of the management server.
  • the management server waits to receive information sent by the FCoE node.
  • 403 and 402 are actually managed by the management server at the same time, that is, the management server broadcasts the Beacon to the FCoE network while waiting to receive the information sent by the FCoE node, and there is no order restriction between the two steps.
  • the information sent by the FCoE node for example, the information sent by the FCoE node, or the Beacon; specifically, each FCoE node first randomly generates a node identifier for identifying the node itself when initially joining the FCoE network, and
  • the Probe process, the Claim process, and the Beacon process are sequentially executed in sequence.
  • the Probe, the Claim, and the Beacon are respectively a special-purpose data packet, and the process of sending the data packet may be referred to as a process corresponding to the data packet.
  • a Beacon process sends a data packet such as Beacon;
  • the FCoE node broadcasts a Probe probe message to the network, carries its randomly generated node identifier, and asks whether other nodes use the node identifier; if so, the node that has used the node identifier returns a notification to the FCoE node. In response, the FCoE node will regenerate another node identifier; otherwise, if no other nodes are used, the FCoE node will continue to execute the Claim process;
  • the FCoE node broadcasts the Claim to the FCoE network, carries its randomly generated node identifier, notifies other nodes in the network that the node identifier has been used, and continues to perform Beacon process;
  • the Beacon process refers to that the FCoE node periodically sends a data packet to the management server for maintaining the network link state of the device in a heartbeat manner in a unicast manner, the Beacon. Carry the node identifier used by itself, so that the management server determines that the link status is normal according to the Beacon.
  • the management server when the management server joins the FCoE network, it may actually receive the Probe inquiring message, or the Claim message, or the Beacon sent by the FCoE node.
  • the FCoE node only indicates when the Cell is sent by the FCoE node. The node has officially started to use the node identifier carried in the node. Therefore, the management server focuses on receiving the Claim message or the Beacon, and performs the next processing according to the Claim message or the node identifier carried in the Beacon, for example, recording the node identifier.
  • the management server joins the FCoE network
  • the FCoE node is in the process phase of the Claim, then the management server receives the Claim message; when the management server joins the FCoE network, the FCoE node is in the Beacon phase, and the management server receives it. It will be Beacon friendship
  • the management server may also receive the query message sent by the FCoE node, for example, the query message sent by the FCoE node newly joining the FCoE network, for querying whether the management server exists, and the query message is carried in the query message.
  • the identity of the management server (each FCoE node knows the identity of the management server, for example, it may be pre-configured on the FCoE node).
  • the management server Upon receiving the query message, the management server returns a response message to the FCoE node, so that the FCoE node knows that the management server exists. After returning the response message, the management server will then wait to receive information sent by the FCoE node, such as a Beacon or Claim sent by the FCoE node.
  • the management server receives the Beacon sent by the FCoE node or the data packet used for identity declaration, and carries the node identifier of the FCoE node.
  • the information sent by the FCoE node received by the management server may be a Claim message or a Beacon, depending on which process stage the FCoE node is currently in. But no matter which process, Beacon or Claim carries the node identifier of the FCoE node.
  • the management server determines whether the node identifier is stored in the local neighbor table.
  • the management server is responsible for determining the FCoE by detecting the Beacon of each FCoE node.
  • the link state of the node so the management server also sets a neighbor table in itself, and records the node identifier of the FCoE node with the link normal in the neighbor table; the link normally means that the management server can receive the node
  • the Beacon of the FCoE node also indicates that the FCoE node can communicate with other nodes in the network.
  • the management server if the management server queries that the node identifier is not stored in the neighbor table, it indicates that, for the management server, this is a newly added FCoE node, and then proceeds to perform 406; if the node identifier is in the neighbor If the table has been stored, continue to execute 407;
  • the management server records the node identifier in the neighbor table, and continues to execute 407;
  • the management server starts a timer, and starts to wait for receiving the Beacon sent by the FCoE node. If the node identifier in the 405 is not stored in the neighbor table, the management server starts the timer after starting the node identifier in the neighbor table, and starts. Waiting to receive the Beacon sent by the FCoE node;
  • the FCoE node should be in the Beacon phase, and the management server has also started the timer. At this time, when the Beacon is received, it is assumed that the management server is timing. When the Beacon is received within the preset time, the management server restarts the timer at 407, which is equivalent to restarting the timer and waiting to receive the next Beacon.
  • the management server continues to execute 408 after the timer is started; of course, for the case where the above node identifier has been stored in the neighbor table, the management server actually receives the FCoE node transmission in 404. At the time of Beacon, it is necessary to first perform the judgment of 408.
  • the management server determines whether the timeout does not receive the Beacon sent by the FCoE node
  • the management server executes whether the timeout does not receive the judgment of the Beacon sent by the FCoE node;
  • the timer has a preset time. If the management server receives the Beacon sent by the FCoE node when the preset time has not arrived, the management server can obtain the above judgment result: No, that is, no timeout Not received; then the management server will execute the above restart timer, waiting to receive the next Beacon; waiting for the next Beacon is equivalent to returning to 403.
  • the management server can obtain the above judgment result: Yes, the timeout is not received. Upon receipt; the management server can then determine that the FCoE node has lost the link and will continue to execute 409.
  • the management server clears a node identifier of the FCoE node in the neighbor table.
  • the management server records the node identifier of the normally linked FCoE node in the neighbor table, so when it is determined in 408 that the link of the FCoE node has been disconnected, the node identifier needs to be from the neighbor list. delete.
  • the management server broadcasts a node change notification message to the FCoE network, where the node change notification message carries the node identifier of the FCoE node that is disconnected and the link disconnection identifier.
  • the management server needs to broadcast the event to other nodes in the entire FCoE network by detecting the receiving condition of the Beacon between the FCoE node and the FCoE node, so that other FCoE nodes know that the FCoE node is disconnected. Open the link; therefore, the node change notification message carries the node identifier of the FCoE node and the link disconnection identifier.
  • the other FCoE node can query its own neighbor table according to the node change notification message, and determine whether the node identifier carried in the node change notification message is stored in its neighbor table; if there is no storage, it indicates that it is disconnected from the node.
  • the linked FCoE node can not establish the link relationship originally, so the node change notification message can be ignored, and the neighbor table can be kept unchanged; if there is storage, it indicates that the FCoE node itself and the disconnected FCoE node can establish a link before, now
  • the neighbor table needs to be updated, and the node identifier of the disconnected FCoE node is deleted from the neighbor table.
  • management server may continue to execute 411;
  • the management server broadcasts a node change notification message to the FCoE network, where the node change notification message carries a node identifier of the newly added node and a link establishment identifier.
  • the newly added FCoE node is not stored in the neighbor table for the management server; if the FCoE node is learned by the management server by receiving the Claim message, the node is really newly added to the node.
  • FCoE network and if the FCoE node is known by the management server by receiving the Beacon, the node is already in the FCoE network, but only notified to the management server for the first time.
  • the newly added FCoE node may be stored in other node's own neighbor table or not yet stored for other nodes; if it is already stored , other nodes can keep their neighbor table unchanged; If it is not yet stored, in the case that other nodes themselves need to establish a link with the newly added FCoE node, other nodes will add the node identifier of the FCoE node to its neighbor table, and the other nodes themselves do not need to be new with the node. In the case where an added FCoE node establishes a link, it can also keep its neighbor table unchanged.
  • the management server is responsible for the Beacon interaction with the FCoE node, and the FCoE node's Probe process, and the Claim process can still be sent in the conventional broadcast form, so that other nodes are If the Claim message of the FCoE node is received, the node identifier carried in the Claim message can be obtained.
  • the node identifier can be recorded; of course, optionally, the Claim process of the FCoE node can also be limited to The management server performs the process, that is, the FCoE node sends the Claim message to the management server in unicast mode, carries the randomly generated node identifier, and then the management server notifies the other node through the broadcast node change notification message.
  • FIG. 5 is a flowchart of the operation of the FCoE node in another embodiment of the FCoE network link management method according to the present invention. As shown in FIG. 5, the execution process of the FCoE node is as follows:
  • the FCoE node randomly generates a node identifier.
  • the FCoE node generates the node identifier according to the scheme specified by the conventional VN2VN, and is not detailed here.
  • the FCoE node detects whether a management server exists.
  • this step is not necessarily performed immediately after the FCoE node randomly generates the node identifier, as long as it is executed before the FCoE node sends the Beacon.
  • FCoE nodes are provided to detect whether there is a management server:
  • the FCoE node can determine whether the Beacon sent by the management server can be received, and the Beacon carries the identifier of the management server; if received, it indicates that the management server exists; otherwise, the management server does not exist;
  • the FCoE node can set a detection time, and determine whether the Beacon sent by the management server can be received within the preset detection time; the Beacon of the management server is periodic.
  • the detection time set by the FCoE node is usually greater than the transmission period of the management server Beacon. For example, it can be set to a length of about 2 cycles.
  • the preset time of the timer is also greater than the transmission period of the FCoE node Beacon, for example, 2 cycles.
  • the FCoE node if the FCoE node does not receive the Beacon sent by the management server within the preset detection time, it indicates that there is no management server, and continues to execute 503; otherwise, executes 504; in another manner, the FCoE node actively queries Whether there is a management server;
  • the FCoE network adds a new FCoE node, and the new FCoE node can broadcast a query message to the FCoE network, where the query message carries the identifier of the management server, and is used to query whether the management server exists in the FCoE network. If there is a management server, the management server will return a response message to the FCoE node.
  • the FCoE node receives the response message, it determines that the management server exists, and then proceeds to execute 504; otherwise, if the FCoE node does not receive the response message, If it is determined that there is no management server, proceed to 503.
  • the FCoE node when the FCoE node waits to receive the response message returned by the management server, it may also set a detection time, and determine whether the response message returned by the management server can be received within the preset detection time, and the detection time is only It is reasonable to set up a response message.
  • the FCoE node executes the VN2VN process.
  • FCoE node If the FCoE node does not receive the Beacon sent by the management server within the preset detection time, it indicates that the FCoE network does not have a management server, and the FCoE node performs the normal process.
  • the FCoE node records the identifier of the management server in the local neighbor table.
  • the FCoE node If the FCoE node receives the Beacon sent by the management server within the preset detection time, it indicates that the management server exists in the FCoE network, and the FCoE node records the identity of the management server in the local neighbor table, indicating the FCoE node and the management server. It is also possible to communicate.
  • the FCoE node periodically sends a Beacon to the management server.
  • the Beacon is configured to notify the management server that the link is normally linked to the FCoE network, and the management server starts the timer. If the Beacon is received within the preset time of the timer, the link of the FCoE node is normal. The management server will update the timer and wait for the next Beacon to be periodically detected.
  • the FCoE node starts a timer. After the FCoE node records the management server, the Beacon is periodically sent to the management server in 505, and the Beacon sent by the management server is periodically detected to determine the link state of the management server on the FCoE network.
  • the FCoE node needs to start a timer, which is used to determine the receiving time of the management server Beacon in the subsequent steps.
  • the preset time set by the timer is usually greater than the sending period of the management server Beacon, for example, it can be set to 2 The length of time around a period.
  • the FCoE node determines whether the Beacon sent by the management server is not received after timeout
  • the FCoE node If the FCoE node receives the Beacon sent by the management server within a preset time set by the timer, it determines that the link of the management server in the FCoE network is normal; and returns to execution 506, that is, restarts the timer. Waiting for the next Beacon from the receiving management server
  • FCoE node does not receive the Beacon sent by the management server within the preset time set by the timer, it is determined that the link of the management server in the FCoE network is disconnected, and execution 508 is continued.
  • the FCoE node deletes the identifier of the management server from the local neighbor table.
  • the FCoE node may determine the identity of the management server from its local neighbor list after determining that the management server is disconnected from the FCoE network. delete.
  • the FCoE node can return to execution 502 to detect the presence of other management servers.
  • the FCoE node may receive the link.
  • the node change notification message sent by the management server for notifying that a node is disconnected is performed 509; or the FCoE node may also receive a node change notification message sent by the management server for notifying a node to newly add, that is, Execute 511.
  • the FCoE node receives a node change notification message broadcasted by the management server on the FCoE network, and carries a node identifier of the FCoE node that disconnects the link and a link disconnection identifier.
  • the node change notification message is sent by the management server when periodically detecting the Beacon sent by the FCoE node and not receiving the Beacon sent by the FCoE node, where the FCoE node refers to the disconnected FCoE node.
  • the management server does not receive the Beacon sent by the disconnected FCoE node within a preset time of its timer, it determines that the link of the FCoE node is disconnected, and the disconnected link is broadcasted on the FCoE network.
  • the node ID of the FCoE node and the link disconnection identifier is sent by the management server when periodically detecting the Beacon sent by the FCoE node and not receiving the Beacon sent by the FCoE node, where the FCoE node refers to the disconnected FCoE node.
  • the FCoE node will query its own neighbor table to determine whether there is a node identifier of the FCoE node storing the disconnected link in the neighbor table; if there is storage, the FCoE node will continue to execute 510; if there is no storage, the FCoE node can Keep the neighbor table unchanged.
  • the FCoE node deletes the node identifier of the disconnected FCoE node from the local neighbor table according to the node change notification message.
  • the FCoE node receives a node change notification message broadcasted by the management server on the FCoE network, and carries a node identifier and a link establishment identifier of the FCoE node newly added to the FCoE network.
  • the node change notification message is sent by the management server when receiving the node identifier of the FCoE node newly added to the FCoE network for the first time. If the FCoE node needs to establish a link with the newly added FCoE node, and its neighbor table has not been stored, execute 512;
  • the FCoE node adds the node identifier of the FCoE node newly added to the FCoE network to the local neighbor table according to the node change notification message.
  • the FCoE network link management method in the embodiment of the present invention by setting a management server in the FCoE network, each FCoE node only needs to periodically send the Beacon to the management server, instead of broadcasting the Beacon to the entire network, thereby effectively saving network bandwidth; Unifiedly receive the Beacons of all FCoE nodes in the network, detect the link status of all FCoE nodes, and notify the other nodes in the network when a node loses the link, thereby reducing the burden on the FCoE nodes.
  • FIG. 6 is a schematic structural diagram of an FCoE node according to an embodiment of the present invention.
  • the FCoE node may perform the method according to any embodiment of the present invention.
  • the FCoE node includes: a heartbeat interaction unit 61, a message receiving unit 62, and a neighbor management unit. 63; Among them,
  • the heartbeat interaction unit 61 is configured to periodically send, to the management server, a data packet Beacon for maintaining a network link state of the device in a heartbeat manner, where the Beacon is used to notify the management server to be locally linked in the FCoE network; Starting a timer to detect a Beacon sent by the management server, and determining, according to the Beacon sent by the management server, a link status of the management server in the FCoE network;
  • the message receiving unit 62 is configured to: when the link state of the management server is normal, receive a node change notification message broadcast by the management server on the FCoE network, where the node change notification message carries a link state in the FCoE network. Node information of the changed FCoE node, said The FCoE node whose link status changes is determined by the management server by detecting the Beacon sent by the FCoE node in the FCoE network;
  • the neighbor management unit 63 is configured to update a local neighbor table according to the node information in the node change notification message received by the message receiving unit, where the neighbor table is used to record other FCoE nodes that can establish a link with the FCoE node. Node information.
  • the message receiving unit 62 is specifically configured to receive a node change notification message that is broadcast by the management server on the FCoE network, where the node change notification message carries a node identifier of the FCoE node that disconnects the link and a link disconnection identifier,
  • the node change notification message is sent by the management server when the Beacon sent by the FCoE node is not received within a preset time set by the management server;
  • the neighbor management unit 63 is specifically configured to be used according to the disconnected FCoE node.
  • the node identifier and the link disconnection identifier delete the node identifier of the FCoE node that is disconnected from the local neighbor table.
  • the message receiving unit 62 is specifically configured to receive a node change notification message that is broadcast by the management server on the FCoE network, where the node change notification message carries a node identifier and a link of an FCoE node newly added to the FCoE network. Establishing an identifier; the node change notification message is sent by the management server when determining that the received node identifier carried in the Beacon sent by the FCoE node is received for the first time;
  • the neighbor management unit 63 is specifically configured to add the node identifier of the FCoE node newly added to the FCoE network to the local neighbor according to the node identifier of the FCoE node newly added to the FCoE network and the link establishment identifier. In the table.
  • the heartbeat interaction unit 61 is further configured to: before the periodically sending the Beacon to the management server, determine whether the Beacon sent by the management server is received in a preset detection time, where the Beacon carries the management The identifier of the server; and when the determination result is yes, performing the sending of the Beacon to the management server periodically according to the identifier of the management server; the neighbor management unit 63 is further configured to be used in the heartbeat interaction unit When the judgment result is YES, the identifier of the management server is recorded in the local neighbor table.
  • the heartbeat interaction unit 61 is further configured to: when the Beacon sent by the management server is not received within the preset time set by the timer, determine that the link of the management server in the FCoE network is disconnected;
  • the neighbor management unit 63 is further configured to determine, in the heartbeat interaction unit, the management service When the link between the devices is broken, the identity of the management server is deleted from the local neighbor table.
  • FIG. 7 is a schematic structural diagram of an embodiment of a management server according to the present invention.
  • the management server may perform the method of any embodiment of the present invention.
  • the management server includes: a heartbeat interaction unit 71 and a message sending unit 72;
  • the heartbeat interaction unit 71 is configured to periodically broadcast, to each FCoE node of the FCoE network, a data packet Beacon for maintaining a network link state of the device in a heartbeat manner, so that the FCoE node determines, according to the Beacon, that the management server is a link state in the FCoE network; and periodically detecting a Beacon sent by the FCoE node, and determining, according to the Beacon sent by the FCoE node, a link state of the FCoE node in the FCoE network;
  • the message sending unit 72 is configured to: when the heartbeat interaction unit determines that the FCoE node in the FCoE network has a link state change, broadcast a node change notification message to the FCoE network, where the node change notification message carries the link Node information of the FCoE node whose state changes, so that other FCoE nodes in the FCoE network change according to the link state
  • the node information of the FCoE node updates the neighbor table of the other FCoE node, and the other FCoE node is a node whose link state in the FCoE network is normal and has not changed.
  • the heartbeat interaction unit 71 is configured to: when the Beacon sent by the FCoE node is not received within a preset time set by the timer, determine that the FCoE node is disconnected in the FCoE network.
  • the link state of the FCoE node in the FCoE network is changed from normal to offline; the FCoE node whose link state changes is the FCoE node with the link disconnected;
  • the message sending unit 72 is specifically configured to: broadcast a node change notification message to the FCoE network, where the node change notification message carries a node identifier of the FCoE node that is disconnected and a link disconnection identifier, so that the FCoE Other FCoE nodes in the network delete the node identifier of the FCoE node that is disconnected from the neighbor list.
  • the heartbeat interaction unit 71 is further configured to receive a Beacon sent by the FCoE node or a data message Claim for performing identity declaration, where the Beacon or the Claim carries a node identifier of the FCoE node;
  • the method further includes: a neighbor management unit 73, configured to: when the beacon interaction unit receives the Beacon, instruct the heartbeat interaction unit to restart a timer, and wait to receive the FCoE node to send The next Beacon; otherwise, the node ID is recorded in the local neighbor table.
  • a neighbor management unit 73 configured to: when the beacon interaction unit receives the Beacon, instruct the heartbeat interaction unit to restart a timer, and wait to receive the FCoE node to send The next Beacon; otherwise, the node ID is recorded in the local neighbor table.
  • the heartbeat interaction unit 71 is further configured to: when the neighbor management unit determines that the node identifier carried in the Beacon sent by the FCoE node is not stored in the local neighbor table, determine that the FCoE node is newly added to the FCoE.
  • the FCoE node of the network the link state of the FCoE node in the FCoE network is changed from offline to normal; the FCoE node whose link state changes is the newly added FCoE node to the FCoE network;
  • the message sending unit 72 is specifically configured to: broadcast a node change notification message to the FCoE network, where the node change notification message carries a node identifier of the FCoE node newly added to the FCoE network, and a link establishment identifier, so that the Other FCoE nodes in the FCoE network add the node identifier of the FCoE node to the neighbor table of the other FCoE node.
  • the present embodiment provides an Ethernet Fibre Channel FCoE network link management system.
  • the structure of the system may be as shown in FIG. 1 , including the FCoE node according to any embodiment of the present invention, and any embodiment of the present invention. Management server.
  • FCoE node and the management server For the structure of the FCoE node and the management server, refer to the fifth embodiment and the sixth embodiment.
  • FCoE network link management method of the present invention For the principle of performing the FCoE network link management method of the present invention, refer to the method embodiment of the present invention.
  • FCoE node 8 is a physical configuration diagram of an FCoE node embodiment of the present invention, the FCoE node includes at least one processor, and a memory connected to the at least one processor; the at least one processor reads a first application in the memory Code, execute the corresponding processing steps.
  • the at least one processor and memory are random access memory (RAM) as an example in FIG.
  • the processor is configured to:
  • the Beacon is periodically sent to the management server in the FCoE network, and the Beacon is configured to notify the management server to be locally linked to the FCoE network; and periodically start a timer to detect the Beacon sent by the management server, according to the management server.
  • the transmitted Beacon determines the link status with the management server;
  • the node change notification message carrying The node information of the FCoE node in which the link state changes in the FCoE network, and the FCoE node in which the link state changes is determined by the management server by detecting the Beacon sent by the FCoE node;
  • the processor may also be configured to perform various steps in the first embodiment of the method, which are not described herein.
  • FIG. 9 is a diagram showing an entity configuration of an embodiment of a management server according to the present invention, the management server including at least one processor and a memory connected to the at least one processor; the at least one processor reads a second application in the memory Code, execute the corresponding processing steps.
  • the management server including at least one processor and a memory connected to the at least one processor; the at least one processor reads a second application in the memory Code, execute the corresponding processing steps.
  • RAM random access memory
  • the processor is configured to:
  • the Beacon is periodically broadcasted to each FCoE node of the FCoE network, so that the FCoE node determines the link state with the local device according to the Beacon, and periodically starts a timer to detect the Beacon sent by the FCoE node, according to the FCoE.
  • the Beacon sent by the node determines the link status with the FCoE node;
  • the FCoE node When determining that the FCoE node has a link state change in the FCoE network, broadcasting a node change notification message to the FCoE network, where the node change notification message carries node information of the FCoE node whose link state changes, so that The other FCoE nodes in the FCoE network update the neighbor table of the other FCoE nodes according to the node information of the FCoE node whose link status changes, and the other FCoE nodes are that the link status in the FCoE network does not change. Node.
  • the processor may also be configured to perform the steps in the second embodiment of the method, which are not described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé, un dispositif et un système de gestion de liaisons réseau FCoE. Selon ledit procédé : un nœud FCoE envoie périodiquement une balise à un serveur de gestion, cette balise servant à indiquer au serveur de gestion que le plan local est relié normalement au réseau FCoE; un temporisateur est lancé périodiquement afin de détecter une balise envoyée par ledit serveur de gestion, et l'état de la liaison du serveur de gestion dans le réseau FCoE est déterminé en fonction de la balise envoyée par ledit serveur; un message d'indication de modification de nœud diffusé par le serveur de gestion au sein du réseau FCoE est reçu, ce message contenant les informations de nœud d'un nœud FCoE ainsi que l'état de la liaison modifiée au sein du réseau FCoE; puis une liste de voisins locaux est mise à jour suivant les informations de nœud, cette liste de voisins servant à enregistrer les informations de nœud d'autres nœuds FCoE capables d'établir une liaison vers le nœud FCoE. La présente invention réduit l'occupation de la largeur de bande du réseau et allège la charge imposée au nœud FCoE.
PCT/CN2012/080426 2012-08-21 2012-08-21 PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE WO2014029079A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201280002786.XA CN103262470B (zh) 2012-08-21 2012-08-21 FCoE网络链接管理方法、设备和系统
PCT/CN2012/080426 WO2014029079A1 (fr) 2012-08-21 2012-08-21 PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/080426 WO2014029079A1 (fr) 2012-08-21 2012-08-21 PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE

Publications (1)

Publication Number Publication Date
WO2014029079A1 true WO2014029079A1 (fr) 2014-02-27

Family

ID=48964009

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/080426 WO2014029079A1 (fr) 2012-08-21 2012-08-21 PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE

Country Status (2)

Country Link
CN (1) CN103262470B (fr)
WO (1) WO2014029079A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3039822A1 (fr) 2013-08-30 2016-07-06 Hewlett Packard Enterprise Development LP Identification d'état d'élément réseau sur la base d'un service
CN104468158B (zh) * 2013-09-16 2018-07-13 华为技术有限公司 一种节点间状态通告的方法和设备
CN105306387B (zh) * 2014-07-31 2018-11-13 华为技术有限公司 一种分区方法及设备
CN109218126B (zh) * 2017-06-30 2023-10-17 中兴通讯股份有限公司 监测节点存活状态的方法、装置及系统
CN113382447A (zh) * 2021-05-25 2021-09-10 北京小米移动软件有限公司 一种邻居信息的更新方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588365A (zh) * 2009-06-18 2009-11-25 杭州华三通信技术有限公司 链路协商的控制方法和光纤通道承载以太协议整合系统
CN101656721A (zh) * 2009-08-27 2010-02-24 杭州华三通信技术有限公司 虚链路发现控制方法和以太网承载光纤通道协议系统
CN102474464A (zh) * 2009-08-04 2012-05-23 国际商业机器公司 在fcoe中建立点对点连接的装置、系统和方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546426B (zh) * 2012-02-02 2014-09-24 杭州华三通信技术有限公司 用于实现以太网承载光纤通道的路由生成方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588365A (zh) * 2009-06-18 2009-11-25 杭州华三通信技术有限公司 链路协商的控制方法和光纤通道承载以太协议整合系统
CN102474464A (zh) * 2009-08-04 2012-05-23 国际商业机器公司 在fcoe中建立点对点连接的装置、系统和方法
CN101656721A (zh) * 2009-08-27 2010-02-24 杭州华三通信技术有限公司 虚链路发现控制方法和以太网承载光纤通道协议系统

Also Published As

Publication number Publication date
CN103262470A (zh) 2013-08-21
CN103262470B (zh) 2015-09-30

Similar Documents

Publication Publication Date Title
US9474101B2 (en) Apparatus and system for managing a sensor network
JP6204510B2 (ja) ハイブリッドネットワーク内のトポロジ発見
US8582500B2 (en) Methods for providing an ad hoc mobile communication network and systems thereof
JP5759024B2 (ja) 地理的冗長ゲートウェイでセッションを復元するシステムおよび方法
JP4216255B2 (ja) 無線ローカルエリアネットワークとユーザ端末装置との間のサービス接続に関する処理方法
WO2014029079A1 (fr) PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE
KR20050018156A (ko) 디스트리뷰션시스템에서 빠른 ｄａｄ 수행을 위해 정보를관리하는 빠른 ｄａｄ 관리자 및 이를 이용한 빠른 ｄａｄ수행방법
CN102546427B (zh) 一种基于ospf协议的平滑重启方法和路由器
CN102624635A (zh) 一种平滑重启实现方法及设备
WO2013004093A1 (fr) Procédé de changement de contrôleur d'accès sans fil et point d'accès sans fil
EP2658172A1 (fr) Procédé de diffusion groupée et dispositif de diffusion groupée
CN110572808A (zh) 蓝牙Mesh网络系统及其建立方法
WO2011100907A2 (fr) Procédé de configuration de paramètre et dispositif d'élément de réseau
US9350621B2 (en) Synchronization after restart of a FC switch
CN109089289A (zh) 切换到电路交换域的方法和装置
KR101173628B1 (ko) 애드혹 무선 인스턴트 메신저 시스템 및 서비스 보안 방법
WO2013037318A1 (fr) Procédé de traitement de données et nœud de traitement de données
WO2012167710A1 (fr) Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes
JP2004064429A (ja) 中継装置及びネットワーク中継方法
CN101304379A (zh) 边界网关协议路由决策方法及装置
CN101764737B (zh) 基于边界网关协议的路由老化方法、装置和路由器
WO2013189130A1 (fr) Système de communication et procédé de communication dans un système de communication basé sur un réseau ad hoc
WO2015013876A1 (fr) Procédé de construction de topologie de réseau maillé pour réseau local sans fil et station sans fil
KR101043765B1 (ko) 애드혹 무선 인스턴트 메신저 시스템 및 서비스 관리 방법
JP2012004912A (ja) パケット交換局、サービングゲートウェイ装置及びｐｄｎコネクション切断方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12883143

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12883143

Country of ref document: EP

Kind code of ref document: A1