WO2016068968A1 - Connexion réseau par adresses de substitution - Google Patents

Connexion réseau par adresses de substitution Download PDF

Info

Publication number
WO2016068968A1
WO2016068968A1 PCT/US2014/063302 US2014063302W WO2016068968A1 WO 2016068968 A1 WO2016068968 A1 WO 2016068968A1 US 2014063302 W US2014063302 W US 2014063302W WO 2016068968 A1 WO2016068968 A1 WO 2016068968A1
Authority
WO
WIPO (PCT)
Prior art keywords
fabric
switch
link
address
alternate
Prior art date
Application number
PCT/US2014/063302
Other languages
English (en)
Inventor
Siamack Ayandeh
Original Assignee
Hewlett Packard Enterprise Development Lp
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 Hewlett Packard Enterprise Development Lp filed Critical Hewlett Packard Enterprise Development Lp
Priority to PCT/US2014/063302 priority Critical patent/WO2016068968A1/fr
Publication of WO2016068968A1 publication Critical patent/WO2016068968A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports

Definitions

  • Computing networks can include multiple network devices including network devices such as routers, switches, hubs, and computing devices such as servers, desktop PCs, laptops, workstations, mobile devices and peripheral devices, e.g., printers, facsimile devices, and scanners, networked together across wired and/or wireless local and/or wide area network (LANs/WANs).
  • network devices such as routers, switches, hubs, and computing devices
  • computing devices such as servers, desktop PCs, laptops, workstations, mobile devices and peripheral devices, e.g., printers, facsimile devices, and scanners, networked together across wired and/or wireless local and/or wide area network (LANs/WANs).
  • LANs/WANs local area network
  • High Availability is a mode of operation for networks where redundant components are used to reduce service outage.
  • FC fibre channel
  • FCoE fibre channel over Ethernet
  • a gateway proxy may be used to connect multiple hosts or virtual machines to a network fabric.
  • the gateway proxy logs in to a switch on the network fabric on each link that it has with the switch to the network fabric. Any attempt by a host to connect to the network fabric is handled by the gateway proxy to register the host with the switch and receive an address for the host in the network fabric.
  • Figure 1 illustrates an example of a system including a switch in a network fabric connected to a plurality of hosts via a plurality of links consistent with the present disclosure.
  • Figure 2A illustrates an example of a fibre channel over Ethernet (FCoE) forwarder (FCF) node according to the present disclosure.
  • FCoE fibre channel over Ethernet
  • FCF fibre channel over Ethernet
  • Figure 2B illustrates an example of a gateway proxy switch according to an example of the present disclosure.
  • Figure 3 illustrates the structure of the addresses and the address components used by controlling FCFs to assign addresses according to the present disclosure.
  • Figure 4 illustrates an example of a login response control frame that can be returned by the logic and instructions of a switch in a network fabric according to one example of the present disclosure.
  • Figures 5A-5E illustrate an example of frame address rewrites consistent with at least one example of the present disclosure.
  • Figure 6 illustrates an affected connections control frame as may be generated, exchanged and processed by FCFs of a gateway proxy and/or a fabric switch, consistent with the present disclosure.
  • Figure 7A illustrates a connection list request for migration to a new link control frame consistent with the present disclosure.
  • Figure 7B illustrates a connection list reply for migration to a new link control frame consistent with the present disclosure.
  • Figure 8 illustrates an example method for alternate address login consistent with the present disclosure.
  • Examples of the present disclosure may include network devices, systems, and methods, including executable instructions and/or logic thereon for alternate address network login.
  • a network gateway switching device e.g., an N_Port Virtualizer (NPV) acts as a proxy between a host adapter and a switch in a network fabric.
  • the proxy e.g., NPV or gateway switch, may log in to a switch in the network fabric on each link that the proxy has with the switch in the network fabric.
  • the proxy may log in using a fibre channel initialization protocol (FIP) login (FLOGI) process in fibre channel (FC) or fibre channel over Ethernet (FCoE) on links to the switch in the network fabric.
  • FIP fibre channel initialization protocol
  • FC fibre channel
  • FCoE fibre channel over Ethernet
  • the proxy receives an address for that device on the host and the switch characteristics. This information is relayed back to the proxy and by the proxy back to the host as a login response.
  • the address will be unique in the fabric with the fabric including numerous switch elements.
  • the procedure is relatively lengthy in time and service disruptive.
  • the duration of a forced log-out and login may be of the order of seconds during which no service is available. That is, for the service disruption's duration, no useful payload data traffic is carried from the host.
  • Log-out and login events and associated outages are often used as a metric for service level agreements and are closely monitored as an indicator of quality of a given transport technology.
  • the login and logout out events are fabric wide and are processed by the entire fabric including associated end points of a connection, e.g., storage targets. Therefore the processing burden can be fabric wide.
  • a switch in the network fabric is provided with instructions and logic to return an alternate address network login (shadow login).
  • One example method includes receiving a login request to a fabric switch from a host on a network. Connection parameters are returned to the host from the fabric switch in response to the login request. The returned connection parameters include; a first fabric address assignment having a first link to the fabric switch, a second fabric address assignment having an alternate link to the fabric switch, and an alternate local port name to the fabric switch. The example method includes detecting a link event on the fabric switch and applying a forwarding rule based on a type of link event detected to determine use of the first or the second fabric address.
  • Figure 1 illustrates an example of a system 100 including a switch in a network fabric connected to a plurality of hosts via a plurality of links consistent with the present disclosure.
  • a plurality of host Host 1 , Host 2, . . ., Host N, (104-1 , 104-2, 104-N)
  • the gateway proxy 102 can include a gateway proxy such as an N_Port Virtualizer (NPV).
  • NV N_Port Virtualizer
  • the gateway proxy can be implemented as computer executable instructions executed by a processing resource and/or logic on a soft switch, in the form of an application specific integrated circuit (ASIC), or on a network interface card (NIC), such as network adaptor card 1 12 shown on Host 1 in Figure 1 .
  • the network adaptor card 1 12 can be an N_Port network interface card.
  • a switch e.g., 1 10-1
  • a plurality of hosts e.g., 104-1 , . . ., 104-N, via a plurality of links 1 1 1 1 -1 , . . ., 1 1 1 -3
  • a fibre channel switch e.g., a fibre channel over Ethernet (FCoE) forwarder (FCF) node, described and illustrated with Figure 2 [0023]
  • FCoE fibre channel over Ethernet
  • FCF fibre channel over Ethernet
  • VM1 and VM2 can each support a plurality of virtual machines VM1 and VM2, 106- 1 and 106-2, which can be connected to a network adaptor card 1 12 via a soft- switch 108.
  • Softswitch vSwitch
  • VM virtual machine
  • a host in intended to mean a compute component having memory resources, processing resources and instructions stored in the memory resources and executable by the processing resources.
  • FCoE fibre channel over Ethernet
  • the hosts 104-1 , . . ., 104-N, gateway proxy 102 and switch 1 10-1 in switch fabric can form a network.
  • a network can attach to a storage area network (SAN), e.g., a switching fabric 100, to form a SAN fabric.
  • a switch fabric 100 is a collection of fibre channel (FC) switches and/or fibre channel over Ethernet (FCoE) forwarders (FCF) which share a fibre channel fabric mapping (FCF_MAP) and run fabric protocols over their "E" ports
  • E_Ports and/or virtual E_Ports (VE_Ports).
  • E_Ports are a type of port for connecting switches.
  • F_Ports are a type of port for connecting to hosts and targets.
  • Figure 1 illustrates a plurality of F_Ports 1 13-1 , 1 13-2, 1 13-3, connecting independently to each of the plurality of links 1 1 1 -1 , 1 1 1 -2, 1 1 1 -3 which connect to the gateway proxy 102.
  • the FCF_MAP is a unique identifier for the switch fabric 100.
  • switches and switching fabric are used in the example of Figure 1 , examples are not limited to switches and switching fabric for network devices.
  • the term "virtual” in reference to a component, e.g., domain, port, connection and/or link, is intended to mean a logical connection versus an express physical connection.
  • the term "virtual machine” is intended to mean a software instantiation of a physical host, e.g., physical computing component.
  • the gateway proxy 102 can be an N-Port Virtualizer (NPV) gateway switch consisting of logic (shown in Figure 2B) similar to an FCF node (shown in Figure 2A), but with minimal FC control stack
  • NVM N-Port Virtualizer
  • FC_MAP FC_MAP
  • program instructions as stored in a fibre channel control stack and executable by a processing resource (e.g., within a control plane of a given switch), can execute instructions to detect a link event and provide an alternate address to connect a host or virtual machine to connect with a switch in a network fabric. That is the program instructions, e.g. control plane instructions of an FCF, can execute to change an address configuration in logic, e.g., hardware in the form of an application specific integrated circuit (ASIC) to process an alternate address.
  • ASIC application specific integrated circuit
  • FIG. 2A illustrates an example of an FCoE forwarder (FCF) node according to an example of the present disclosure.
  • an FCF node 202 can include a processor 220, e.g. processing resource, coupled to a memory 222.
  • the memory 222 may include a fibre channel control stack 224, e.g., control plane software (computer executable instructions or program instructions).
  • the program instructions may be executed to perform acts in connection with the examples of the present disclosure, e.g., to configure hardware of the FCF node to employ an alternate address.
  • FIG. 2B illustrates an example of a gateway proxy 204
  • a gateway proxy 204 can include a processor 220, e.g. processing resource, coupled to a memory 222.
  • the memory 222 may include a reduced, e.g., minimal, fibre channel (FC) control stack 225, e.g., control plane software (computer executable instructions or program instructions).
  • FC fibre channel
  • the program instructions may be executed to perform acts in connection with the examples of the present disclosure, e.g., to configure hardware of the gateway proxy to employ an alternate address.
  • the memory 222 associated with an FCF node 202 of Figure 2A or a gateway proxy 204 of Figure 2B may further include an Ethernet control stack 226, and a control state 228, including instructions executable to track and monitor a connection state of a given host, e.g., host 1 12-1 , . . ., 1 12-N in Figure 1 .
  • program instructions associated with the FCF 202 control stack 224 are executed by the processing resource 220 to detect a link event and provide and alternate address to route traffic without an interruption of service by assigning a first fabric address, a second fabric address and an alternate port name as part of a network login process.
  • the switch 1 10-1 in the network fabric provides this additional information for the host 104-1 or virtual machine VM1 , VM2, etc., which is attempting to connect with the fabric 100.
  • a VM/host name is associated with the given address.
  • the address is carried as part of a header in transmitted frames and is used to route frames to their destination.
  • an address can be made up of a number of bytes in length, e.g., 6, 4, 3 bytes, etc., and may have a structure which reflects the topology of the network.
  • the address structure may be used by the forwarding logic of the switches, e.g. fabric switch 1 10-1 and/or gateway proxy switch 102, to efficiently maintain table size and structure within such switch nodes which can be an expensive and limiting component to switches and switch nodes.
  • Figure 3 illustrates an example structure of an address and address components which may be used consistent with the present disclosure.
  • the example of Figure 3 can be an FCoE example showing an address with three fields.
  • the address 301 is shown including a domain ID portion 330, an area ID portion 332, and a port ID portion 334.
  • the domain ID port 330 can represent a switch in a switch fabric, e.g., switch 1 10-1 among the multiple switches in the switch fabric 100 in Figure 1 .
  • the area ID portion 332 can represent a port of the switch, e.g., 1 13-1 , 1 13-2 or 1 13-3 in Figure 1 , which can be a physical or virtual link, connection with some transmission and switching capacity.
  • the port ID portion 334 can uniquely identify a host or virtual machine, e.g., 104-1 , or VM1 , M2 (106-1 , 106-2), etc., that attempted to login over that port.
  • VM1 In a previous network operating environment, if service on link 1 (L1 ) were disrupted (e.g., via a link failure, etc.), VM1 would need to log out of the switch fabric 100 i.e., switch 10 (1 10-1 ) in this example, and log back in on a different link, e.g., link 3 (L3). As such, VM1 would receive a "new" fabric login address.10.3.5, where "5" to the port ID portion represents the new unique host ID or VM ID, e.g. VM1 , that is attempting to log back in.
  • examples of the present disclosure include logic and/or instructions that are executed by the switch, e.g., switch 10 (1 10-1 ) to return connection parameters from the switch to the host 104-1 in response to a login request.
  • the returned connection parameters include both a first fabric address assignment having a first link to the fabric switch, a second fabric address assignment having an alternate link to the fabric switch. Additionally, an alternate local port name to the fabric switch is returned.
  • Figure 4 illustrates an example of a login response control frame that can be returned by the logic and instructions of a switch in a network fabric (1 10-1 in Figure 1 ) according to one example of the present disclosure.
  • the returned login response control frame can include a field 402 having a set of normal login response parameters for the network.
  • a first fabric address can be provided to the host (104-1 in Figure 1 ) or virtual machine VM1 .
  • this first fabric address, or fabric login address can be 10.1 .1 in the respective domain ID portion 330, area ID portion 332, and port ID portion 334 of the address structure shown in Figure 3.
  • the normal address assignment e.g., 10.1 .1 for VMI , is returned to VM1 and is used to identify it throughout the fabric (100 in Figure 1 ).
  • a second fabric address assignment (or "alternate fabric address") having an alternate link to the fabric switch (1 10-1 in Figure 1 ) can be provided to the gateway proxy (102 in Figure 1 ).
  • an alternate local port name on the fabric switch (104-1 ) can be provided to the gateway proxy 102.
  • the second fabric address may be referred to as a "shadow" login address or alternate address.
  • the second fabric address can be assigned on an alternate port to the fabric switch (1 10-1 ).
  • the second fabric address (alternate address) assignment can be 10.3.5 in the respective domain ID portion 330, area ID portion 332, and port ID portion 334 of the address structure shown in Figure 3.
  • this alternate address assignment can be on an alternate port (e.g., 1 13-3) on the switch (1 10-1 ) on an alternate link (L3 1 1 1 -3 in Figure 1 ) which acts as a standby switch port and link for that connection.
  • the port ID portion "5" (334 in Figure 3) again uniquely identifies the host (104-1 ) or virtual machine VM1 .
  • the name and identity of the local port attached to the alternate link (L3) can enable a re-route around a link, e.g., link (L1 ), whose service may have been disrupted, e.g., due to a link failure.
  • the normal login response parameters 402 first fabric address 404, alternate fabric address 406, and local port name associated with the alternate address 408 are provided to a gateway proxy (102 in Figure 1 ) in the form of a login response control frame.
  • the normal login response parameters 402 first fabric address 404, alternate fabric address 406, and local port name associated with the alternate address 408 are provided to a gateway proxy (102 in Figure 1 ) in a fabric login response using an additional control field in such a way that allows an encapsulation with an additional header field for subsequent data frames.
  • the above additional information can be packaged and used as frame headers as an "alternate address" and can be carried and exchanged as a type, length, value (TLV) format used with control protocol exchanges.
  • This additional information can be removed by a Softswitch (108 in Figure 1 ), network adapter card (1 12), or by the gateway proxy 102, using logic or instructions described in connection with Figures 2A and 2B, to allow for the re-transmission of an original login response to the host (104-1 ) or virtual machine VM1 .
  • logic and/or instructions to an FCF in the fabric switch (1 10-1 ) detect a link event on the fabric switch and apply a forwarding rule based on a type of link event detected to determine use of the first or the second fabric address for routing traffic.
  • logic and/or instructions to the gateway proxy (102) detect a link event with the fabric switch (1 10-1 ) and apply a forwarding rule on the gateway proxy (102) based on a type of link event detected to determine use of the first or the second fabric address for routing traffic.
  • logic and/or instructions in both an FCF in the gateway proxy (102) and an FCF in the fabric switch (1 10-1 ) detect a link event with the fabric switch (1 10-1 ) and apply a respective forwarding rule based on a type of link event detected to determine use of the first or the second fabric address for routing traffic.
  • the following examples call out a given actor in the network as either a gateway proxy (102) or a fabric switch (1 10-1 ).
  • Figures 5A-5F illustrate an example of frame address rewrites consistent with the present disclosure.
  • the example in Figures 5A-5F is consistent with a "link down" event, but may also be used for discussion and description of a "link up” or a "link addition” event, described below.
  • logic and/or instructions on the gateway proxy (102) can detect a link down event, e.g., a failed link such as L1 used in the first fabric address of the above example.
  • An example of detecting a link down event by the gateway proxy can include detecting a link failure or taking down a port for administrative reasons, etc.
  • the gateway proxy would then use the logic and/or instructions, e.g., shown in Figure 2B and similar to the FCF of Figure 2A, to activate an alternate forwarding rule.
  • One example of an alternate forwarding rule includes selecting the second fabric address to route traffic from the host 104-1 or virtual machine VM1 .
  • the logic and/or instructions may be executed to check the connections associated with the failed link, e.g., L1 .
  • the connections associated with the failed link may be tracked and maintained in a table by instructions executing on the gateway proxy and may be stored and accessed from memory.
  • the gateway proxy 102 may further use logic and/or instructions to implement a selected alternate forwarding rule to detect incoming flows and/or frames affected by the failed link L1 as determined from checking the associated connections list stored in the table, such as shown and described in connection with Figure 6.
  • Figures 5A-5F illustrate an address mapping in reference to the example of Figure 1 and in reference to the same address examples given above in connection with Figure 4.
  • Figure 5A illustrates an example of an incoming frame to the gateway proxy 102 from a host 104-1 or virtual machine VM1 .
  • This frame can include a checksum value 502, data (payload) 504, and a header including a source identifier (address) 506 and a destination identifier (address) 508.
  • the source address 506 may be given as 10.1 .1 and the destination address 508 may be given as X.1 to an example switch "X" in the network fabric 100.
  • the logic in the gateway proxy 102 can rewrite the source address (506 in frame 5A) for incoming frames from the host 104-1 or virtual machine VM1 with the alternate source address 507, e.g., 10.3.5, and forward the affected incoming frame or flow on the alternate port towards the switch 1 10-1 in the network fabric 100.
  • the alternate source address 507 e.g. 10.3.5
  • Frame 5E illustrates an outgoing return frame from the switch 1 10- 1 in the network fabric 100 to the gateway proxy 102.
  • the source address 505 for a return frame from a switch "X" in the fabric may be given as X.1 .
  • the destination address 51 1 in the return frame received to the gateway proxy 102 from switch 1 10-1 in the fabric 100 may be given as 10.3.5.
  • the logic in the gateway proxy can rewrite the destination address 509 for outgoing frames from the gateway proxy 102 towards the host 104-1 or virtual machine VM1 .
  • This is a mapping from an alternate destination address provided by an FCF of the switch 1 10-1 to an original login address, e.g., a mapping of destination address from 10.3.5 in the example above to a destination address of 10.1 .1 .
  • logic and/or instructions on the switch 1 10-1 in the network fabric 100 can detect a link down event, e.g., a failed link such as L1 used in the first fabric address of the above example.
  • a link down event e.g., a failed link such as L1 used in the first fabric address of the above example.
  • an example of detecting a link down event by the gateway proxy can include detecting a link failure or taking down a port for administrative reasons, etc.
  • the switch 1 10-1 would then use the logic and/or instructions, e.g., shown in the FCF of Figure 2, to activate an alternate forwarding rule.
  • the switch 1 10-1 then may receive a frame such as frame 5B having a source address 507 given as 10.3.5. As shown in frame 5C, logic and/or instructions in the switch 1 10-1 can rewrite the source address 506 back to 10.1 .1 before sending the frame to switch X in the fabric 100 at destination address 508 X.1 .
  • one example of an alternate forwarding rule in an FCF of switch 1 10-1 includes rewriting the source address for incoming frames from the host 104-1 or virtual machine VM1 with the original login fabric address of the host 104-1 or virtual machine VM1 and forwarding the frame towards the rest of the switch fabric 100 and towards the frames ultimate destination, e.g., towards switch X at destination address 509 X.1 .
  • Frame 5D shows a return, incoming frame to switch 1 10-1 in the fabric 100 from switch X.
  • Frame 5D includes a source address 505 as X.1 and a destination address 509 as 10.1 .1 .
  • the logic and/or instructions in an FCF of the switch 1 10-1 will be used to select the second fabric address to route the frame from the switch 1 10-1 to the host 104-1 or virtual machine VM1 . That is, the logic and/or instructions of the switch 1 10-1 can rewrite the destination address for outgoing frames towards the host 104-1 or virtual machine VM1 for traffic from the switch fabric 100.
  • This is a mapping of the original fabric login address 10.1 .1 to the alternate fabric address 10.3.5.
  • frame 5E illustrates an outgoing frame from the switch 1 10-1 in the fabric 100 to the gateway proxy 102 having a rewritten destination address 51 1 as 10.3.5.
  • a link up event is intended to mean an event where a failed link, e.g., failed link 1 (L1 ) in the example above, returns to service prior to the state of connections timing out.
  • logic and/or instructions on the gateway proxy 102 may detect a link up event analogous to the above described manner to detecting a link down event.
  • the gateway proxy would then run a load balancing algorithm to detect affected connections and checking a table such as described in Figure 6.
  • the logic and/or instructions of the gateway proxy 102 can be used to send a control frame, as shown in Figure 6, to the switch 1 101 -1 in the fabric with a list of affected connections.
  • the logic and/or instructions may cause the gateway proxy to pause for a duration which allows a link buffer to clear for any frames
  • the pause duration may only be a few milliseconds or less.
  • the logic and/or instructions in the gateway proxy 102 would then activate an original forwarding rule, e.g., first fabric address assignment, for the identified connections.
  • the original forwarding rule detects the incoming flows and frames affected.
  • the logic and/or instructions of the gateway proxy then implement the original source address for incoming frames from the host or virtual machine, rather that the alternate address, e.g., second fabric address, and forward the traffic on the original port towards the switch 1 10-1 in the network fabric 100.
  • the alternate address e.g., second fabric address
  • a frame from the switch 1 10-1 has its original destination address 509 which may be left alone by the gateway proxy for outgoing frames toward the host or virtual machine.
  • the mapping is from an alternate address to an original fabric login address, e.g., 10.1 .1 .
  • logic and/or instructions on the switch 1 10-1 can cause the switch to detect the link up event and receive and process the control frame with the list of affected connections, e.g., from the gateway proxy.
  • the switch may pause for a duration which allows a link buffer to clear for any frames associated with the affected connections which may be in transit. Again, this is a function of link speed and, for high speed an accepted buffer sizes, the pause duration can be a few milliseconds or less.
  • the logic and/or instructions in the switch 1 10-1 would then activate the original forwarding rule, first fabric address, for the identified connections moving to back to original link, e.g., link 1 (L1 ) in the above example, and the alternate forwarding rule detects the incoming flows and frames affected.
  • the logic and/or instructions of the switch not have to rewrites the source address for incoming frames from the host or virtual machine, now no longer having the alternate address (e.g., 10.3.5), and will forward toward the rest of the switch fabric toward the ultimate destination, e.g., destination address X.1 in the above example in frame 5C.
  • the logic and/or instructions of the switch not have to rewrites the source address for incoming frames from the host or virtual machine, now no longer having the alternate address (e.g., 10.3.5), and will forward toward the rest of the switch fabric toward the ultimate destination, e.g., destination address X.1 in the above example in frame 5C.
  • a frame from switch X to switch 1 10-1 will no longer need to have its destination address 51 1 rewritten by the switch 1 10-1 for outgoing frames towards the host or virtual machine, e.g. as shown in frame 5E.
  • This is a mapping will already be the original fabric login address.
  • the logic and/or instructions can be executed to check the connections associated with the failed link, e.g., L1 .
  • the connections associated with the failed link may be tracked and maintained in a table by instructions executing on the gateway proxy and may be stored and accessed from memory.
  • Figure 6 illustrates an affected connections control frame as may be generated, exchanged and processed by logic and/or instruction of the FCFs in a gateway proxy 102 and/or in a switch 1 10-1 of the network fabric 100 shown in Figure 1 , consistent with the present disclosure.
  • the affected connection list control frame can include a source switch name field 602, a destination switch name field 604, and a target local port name field 606.
  • the affected connections control frame additionally contains a number of affected connections field 608 and a field for a local port name 610-1 , . . ., 610- N and address 612-1 , . . ., 612-N for each affected connection.
  • Detection of a local link failure is usually accomplished in very short order, micro seconds or milliseconds at most. While a link down event may cause loss of some frames, the detections and switch over to an alternate forwarding rule is as fast as current technology can respond to failures. Any lost or out of order frames are recovered by higher layer protocols. For example, in FC/FCoE the recovery is at the exchange layer.
  • a further example of the present disclosure includes a "link addition” event.
  • a similar process to that which is described above, can be employed for a "link addition” event.
  • a link addition event is intended to mean an event where a new link is added as a connection to a port on a fabric switch to a network.
  • logic and/or instructions on the gateway proxy 102 may detect a link addition event analogous to the above described manner to detecting a link up/down event.
  • the gateway proxy would then run a load balancing algorithm to detect affected connections and to create a table such as described in Figure 7A below.
  • instructions of the gateway proxy 102 can be used to send a control frame to the switch 1 10-1 in the fabric with a list of connections to migrate.
  • the gateway proxy can receive a response from the fabric switch 1 10-1 for migrating connections such as described in Figure 7B below.
  • the logic and/or instructions in the gateway proxy 102 would then activate an alternate forwarding rule such using an alternate fabric address and local port name as could be provided in the control frame shown in Figure 4, for the identified connections.
  • the alternate forwarding rule detects the incoming flows and frames affected.
  • the logic and/or instructions of the gateway proxy 102 then rewrites the source address for incoming frames from the host or virtual machine with an alternate address and forwards on an alternate port towards the switch 1 10-1 in the network fabric 100.
  • a frame from the switch 1 10-1 has a destination address rewritten by the gateway proxy for outgoing frames toward the host or virtual machine, e.g., as shown in frame 5F. This is a mapping from an alternate address to an original fabric login address.
  • logic and/or instructions on the switch 1 10-1 can cause the switch to detect the link addition event and receive, e.g., from the gateway proxy, and process the control frame with the list of connections to migrate to this new link as shown and described in connection with Figure 7A.
  • the switch can respond to the control frame received in Figure 7A with a control frame such as shown in Figure 7B.
  • the logic and/or instructions in the switch 1 10-1 would then activate an alternate forwarding rule on the switch for the connections moving to the new link and the alternate forwarding rule will detect the incoming flows and frames affected.
  • the logic and/or instructions of the switch then rewrites the source address for incoming frames from the host or virtual machine, having now an alternate address, with the original fabric login address of the host or virtual machine and forward toward the rest of the switch fabric toward the ultimate destination, e.g., destination address X.1 in the above example in frame 5C.
  • a frame from switch X to switch 1 10-1 has its destination address 51 1 rewritten by the switch 1 10-1 for outgoing frames towards the host or virtual machine, e.g. as shown in frame 5E. This is a mapping from of the original fabric login address to the alternate address.
  • Figure 7A illustrates a connections list request for migration to a new link control frame as may be generated, exchanged and processed by logic and/or instructions of the gateway proxy 102 and/or in a switch 1 10-1 of the network fabric shown in Figure 1 .
  • the connections list request for migration to a new link control frame can include a source switch name field 702, a destination switch name field 704, and a target local port name field 706.
  • the connections list request for migration to a new link control frame additionally contains a number of affected connections field 708 and a field for an address 710-1 , . . ., 710-N for each affected connection.
  • Figure 7B illustrates a connection list reply for migration to a new link control frame consistent with the present disclosure.
  • the connection list reply for migration to a new link control frame as may be generated, exchanged and processed by logic and/or instructions of the gateway proxy 102 and/or in a switch 1 10-1 of the network fabric shown in Figure 1 .
  • the connection list reply for migration to a new link control frame example shown in Figure 7B includes a source switch name field 702, a destination switch name field 704, and a target local port name field 706 as with the control frame in Figure 7A.
  • connections list reply for migration to a new link control frame also contains a number of affected connections field 708 and additionally contains a field for an alternate address 71 1 -1 , . . ., 71 1 -N for each affected connection.
  • Figure 8 illustrates an example method for alternate address login consistent with the present disclosure.
  • the method can include receiving a login request to a fabric switch from a host connected to a network.
  • a plurality of ports can connect a fabric switch via a plurality of links to a plurality of hosts.
  • the host may additionally be a virtual machine.
  • connection parameters including a first fabric address can be returned to the host and/or virtual machine and a second fabric address can be returned to the gateway proxy.
  • logic and/or instructions, used to return the connection parameters, including the first and the second fabric address can be through a gateway proxy, Softswitch or network adapter card connection from the fabric switch.
  • the connection parameters are returned in a fabric login response using an additional control field in such a way that allows an encapsulation with an additional header field or rewriting of the address in the header for subsequent data frames.
  • the connections parameters are returned using a control frame separate from a fabric login response on the alternate link from a first link.
  • Figure 4 illustrates an example of such a login response control frame.
  • a link event may be detected on a gateway proxy, Softswitch, or network adapter card and a list of affected connections can be generated, exchanged and processed as a control frame between a gateway proxy and a fabric switch.
  • the link event may be detected and its type determined by the gateway proxy and fabric switch hardware and software as referenced in Figures 2A and 2B.
  • Block 808 further illustrates the method includes applying a forwarding rule using logic and/or instructions on a gateway proxy, Softswitch, network adapter card and/or fabric switch, based on a type of link event detected, to select between a first and a second fabric address for routing traffic between the host or virtual machine and a fabric switch on the network fabric.
  • a forwarding rule using logic and/or instructions on a gateway proxy, Softswitch, network adapter card and/or fabric switch, based on a type of link event detected, to select between a first and a second fabric address for routing traffic between the host or virtual machine and a fabric switch on the network fabric.
  • examples disclosed herein are not service affecting.
  • upper layer protocols can recover through retransmission.
  • the techniques disclosed herein can thus improve the service level agreement for a transport technology which is often the cause of service calls and complaints about outages.
  • link up/down events can be reduced to a local event between a gateway proxy, Softswitch or network adapter card and the first hop switch (fabric switch), as opposed to a fabric wide event and thus such events will not affect the associated end points.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Des exemples se rapportent à la connexion réseau par adresses de substitution Un procédé cité à titre d'exemple comprend la réception d'une demande de connexion à un commutateur matriciel à partir d'un hôte sur un réseau. Les paramètres de connexion sont renvoyés par le commutateur matriciel en réponse à la demande de connexion. Les paramètres de connexion renvoyés comprennent : une première attribution d'adresse matricielle ayant une première liaison au commutateur matriciel, une seconde attribution d'adresse matricielle ayant une autre liaison au commutateur matriciel, et un autre nom de port local attribué au commutateur matriciel. Le procédé cité à titre d'exemple consiste à détecter un événement de liaison sur le commutateur matriciel et à appliquer une règle de transmission sur la base d'un type d'événement de liaison détecté pour déterminer l'utilisation de la première ou de la seconde adresse matricielle.
PCT/US2014/063302 2014-10-31 2014-10-31 Connexion réseau par adresses de substitution WO2016068968A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2014/063302 WO2016068968A1 (fr) 2014-10-31 2014-10-31 Connexion réseau par adresses de substitution

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2014/063302 WO2016068968A1 (fr) 2014-10-31 2014-10-31 Connexion réseau par adresses de substitution

Publications (1)

Publication Number Publication Date
WO2016068968A1 true WO2016068968A1 (fr) 2016-05-06

Family

ID=55858071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/063302 WO2016068968A1 (fr) 2014-10-31 2014-10-31 Connexion réseau par adresses de substitution

Country Status (1)

Country Link
WO (1) WO2016068968A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017198041A1 (fr) * 2016-05-16 2017-11-23 中兴通讯股份有限公司 Procédé et appareil d'attribution d'adresse, et commutateur

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020071386A1 (en) * 2000-12-07 2002-06-13 Gronke Edward P. Technique to provide automatic failover for channel-based communications
US20080181243A1 (en) * 2006-12-15 2008-07-31 Brocade Communications Systems, Inc. Ethernet forwarding in high performance fabrics
US20100232793A1 (en) * 2005-10-25 2010-09-16 Brocade Communications Systems, Inc. Interface Switch for use with Fibre Channel Fabrics in Storage Area Networks
WO2014089138A1 (fr) * 2012-12-04 2014-06-12 Plexxi Inc. Procédé et appareil de commande de connectivité dans un réseau de centre de données
WO2014142980A1 (fr) * 2013-03-15 2014-09-18 Hewlett-Packard Development Company, L.P. Entretien d'informations d'état de connexion d'un transmetteur de données

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020071386A1 (en) * 2000-12-07 2002-06-13 Gronke Edward P. Technique to provide automatic failover for channel-based communications
US20100232793A1 (en) * 2005-10-25 2010-09-16 Brocade Communications Systems, Inc. Interface Switch for use with Fibre Channel Fabrics in Storage Area Networks
US20080181243A1 (en) * 2006-12-15 2008-07-31 Brocade Communications Systems, Inc. Ethernet forwarding in high performance fabrics
WO2014089138A1 (fr) * 2012-12-04 2014-06-12 Plexxi Inc. Procédé et appareil de commande de connectivité dans un réseau de centre de données
WO2014142980A1 (fr) * 2013-03-15 2014-09-18 Hewlett-Packard Development Company, L.P. Entretien d'informations d'état de connexion d'un transmetteur de données

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017198041A1 (fr) * 2016-05-16 2017-11-23 中兴通讯股份有限公司 Procédé et appareil d'attribution d'adresse, et commutateur

Similar Documents

Publication Publication Date Title
EP3920484B1 (fr) Détection de caractère vivant et convergence de route dans un système distribué de réseautage défini par logiciel
US10534601B1 (en) In-service software upgrade of virtual router with reduced packet loss
US10645201B2 (en) Packet handling during service virtualized computing instance migration
US10630710B2 (en) Systems and methods of stateless processing in a fault-tolerant microservice environment
US10083026B1 (en) In-service software upgrade of software-defined networking controller
US9985869B2 (en) Support for high availability of service appliances in a software-defined network (SDN) service chaining infrastructure
US9225636B2 (en) Method and apparatus for exchanging IP packets among network layer 2 peers
US10742501B1 (en) Automation of maintenance mode operations for network devices
US20200403922A1 (en) Load balancing of l2vpn traffic over multiple ipsec vpn tunnels
CN110838992B (zh) 在不同网络堆栈中的内核模块间传送分组的系统和方法
US11336570B1 (en) Layer three multi-homing for virtual networks
US10511514B1 (en) Node-specific probes in a native load balancer
US10171361B1 (en) Service-specific probes in a native load balancer
US10447581B2 (en) Failure handling at logical routers according to a non-preemptive mode
US20180262387A1 (en) Restoring control-plane connectivity with a network management entity
US11477270B1 (en) Seamless hand-off of data traffic in public cloud environments
US11558220B2 (en) Uplink-aware monitoring of logical overlay tunnels
US11546242B2 (en) Logical overlay tunnel monitoring
US11362863B2 (en) Handling packets travelling from logical service routers (SRs) for active-active stateful service insertion
US20200274799A1 (en) Multi-vrf and multi-service insertion on edge gateway virtual machines
WO2016068968A1 (fr) Connexion réseau par adresses de substitution
US11929987B1 (en) Preserving packet flow information across bump-in-the-wire firewalls
US11271776B2 (en) Logical overlay network monitoring
US10931565B2 (en) Multi-VRF and multi-service insertion on edge gateway virtual machines
US10298458B2 (en) Distributed system partition

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: 14904672

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: 14904672

Country of ref document: EP

Kind code of ref document: A1