US9270578B2 - Management of multiple network routes - Google Patents
Management of multiple network routes Download PDFInfo
- Publication number
- US9270578B2 US9270578B2 US13/950,188 US201313950188A US9270578B2 US 9270578 B2 US9270578 B2 US 9270578B2 US 201313950188 A US201313950188 A US 201313950188A US 9270578 B2 US9270578 B2 US 9270578B2
- Authority
- US
- United States
- Prior art keywords
- host
- physical network
- network ports
- ports
- available communication
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/14—Multichannel or multilink protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/125—Shortest path evaluation based on throughput or bandwidth
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Definitions
- This disclosure pertains in general to network communication, and in particular to managing network communications between network hosts that have multiple physical network ports coupled to a network.
- Hosts systems in a networked environment can each have multiple physical network ports that couple the host to the network. This creates multiple routes in the network through which the hosts can communicate with each other.
- the ports can be also configured with mismatched connection bandwidths (e.g. 100 Mb/s, 1 Gb/s). Due to the large number of available routes and potential configurations of the ports, it is difficult for the host systems to automatically identify an optimal subset of the routes that uses the routes efficiently.
- Embodiments of the present disclosure are related to managing network communications between network hosts that have multiple physical network ports coupled to the network.
- a method of operations is performed in a first host that communicates with a second host through a network.
- the first host includes a plurality of first physical network ports and the second host includes a plurality of physical network ports that are coupled to the network.
- the first host broadcasts address resolution requests from the first physical network ports of the first host to the second physical network ports of the second host.
- the first host then receives responses to the address resolution requests from the second physical network ports of the second host.
- the responses to the address resolution requests include respective connection bandwidths for the second physical network ports.
- the first host uses the responses, generates connectivity information describing a plurality of available communication routes in the network between a plurality of first physical network ports of the first host and a plurality of second physical network ports of the second host.
- the connectivity information can also describe the respective connection bandwidths of the second physical network ports.
- the first host selects a subset of the available communication routes for data transfer via the network between the first host and the second host based on the respective connection bandwidths of the second physical network ports. The first host then transfers data with the second host via the subset of the available communication routes. By selecting communication routes in this manner, the first host can automatically select a subset of routes that result in efficient use of network bandwidth. Additionally, the selected subset of routes can be a minimum subset of the available communication routes that fully utilizes all available bandwidth of at least one of the first physical network ports or the second physical network ports.
- FIG. 1 is a high-level block diagram of a computing environment for network communication across a storage area network, according to one embodiment.
- FIG. 2 is a detailed view of a networking module of FIG. 1 , according to one embodiment.
- FIG. 3 is a flowchart illustrating a process of network communications performed by the networking module of FIG. 1 according to one embodiment.
- FIG. 4 is a flowchart illustrating a more detailed view for the step of selecting a subset of routes from FIG. 3 , according to one embodiment.
- FIG. 5 is a hardware architecture of Network HostA from FIG. 1 , according to one embodiment.
- Embodiments disclosed herein describe a system and process for route management in a network environment when there are multiple hosts connected to the network, each of which has multiple physical network ports.
- the hosts automatically discover each other during address resolution and provide information about the connection bandwidths of their ports to the other hosts.
- Each host generates connectivity information describing all of the available routes for communicating with another host and which can also describe the connection bandwidths of the ports of the other host. From the connectivity information a subset of the available routes is selected for transferring data between the hosts.
- FIG. 1 is a high-level block diagram of a computing environment 100 for network communication across a storage area network (SAN) 120 , according to one embodiment.
- the computing environment 100 includes a network host A 110 (HostA) and a network host B 130 (HostB) connected to a SAN 120 .
- the computing environment 100 may exist within a datacenter. Only two hosts 110 and 130 are shown in FIG. 1 to simplify and clarify the description. In other embodiments the computing environment 100 can have a larger number of hosts 110 and 130 .
- SAN 120 is a dedicated network that provides access to consolidated, block level data storage.
- the SAN 120 may include communication links using technologies such as Ethernet. In other embodiments the communication links can use other technologies such as Fibre Channels or the like.
- HostA 110 and HostB 130 can communicate over the SAN 120 using a communication protocol such as ATA over Ethernet (AoE), Fiber Channel Protocol (FCP), Fiber Channel over Ethernet (FCoE), or other appropriate communication protocol.
- the SAN 120 can be located in one physical location or can span multiple physical locations.
- the SAN 120 may include one or more network switches (not shown) that route communications in the SAN 120 between HostA 110 and HostB 130 .
- HostA 110 and HostB 130 are both computing devices, such as server class computers.
- HostA 110 also known as an initiator host, initiates data transfer with HostB 130 across the SAN 120 .
- HostB 130 also known as a storage host, provides storage services to HostA 110 through the SAN 120 .
- HostB 130 includes several storage devices 140 , such as magnetic disk drives, solid state drives, etc.
- HostB 130 forms the storage devices 140 into logical unit numbers (LUNs) which are assigned to HostA 110 , accessed by HostA 110 via the SAN 120 and appear as local storage to HostA 110 .
- LUN logical unit numbers
- a LUN may be shared among multiple network hosts.
- Both HostA 110 and Host B 130 include several physical network ports 112 and 132 , respectively, that are coupled to the SAN 120 .
- HostA 110 includes ports 112
- HostB 130 includes ports 132 .
- a physical network port is piece of hardware that provides physical access to the SAN 120 through a wired (or wireless) connection.
- An example of a physical network port is an Ethernet card.
- each port When connected to the SAN 120 , each port negotiates a network connection bandwidth (e.g. 100 Mb/s, 1 Gb/s) with the SAN 120 .
- the network connection bandwidth of a port defines the rate at which data is transferred with the SAN 120 through the port.
- the negotiated network connection bandwidth of a port may be lower than the maximum bandwidth of a port due to the limitations of the SAN 120 .
- Some of the physical network ports may have different network connection bandwidths. For example port A0 112 may operate at 100 Mb/s while port A1 112 and port B0 132 operate at 1 Gb/s.
- Each port has a unique physical address that can be used by other hosts to communicate with the port.
- the physical address may be hardwired into the port such that it is not modifiable.
- an Ethernet based port may have a unique media access control (MAC) address.
- MAC media access control
- Each host e.g. HostA 110 and HostB 130
- a network address is used as a higher order identifier for a host that is independent of the physical addresses.
- An example of a network address in the AoE protocol is a major.minor address.
- Another example of a network address is an internet protocol (IP) address or similar type of address.
- IP internet protocol
- HostA 110 and HostB 130 include respective networking modules 114 and 134 .
- networking module 114 of HostA 110 will be described herein. However, it is understood that the description of networking module 114 can also apply to networking module 134 .
- Networking module 114 communicates with HostB 130 to discover available communication routes in the SAN 120 between HostA 110 and Host B 130 . Because HostA 110 has (m) number of ports 112 and network host B 130 has (n) number of ports 132 , there are a total of (m ⁇ n) available communication routes between HostA 110 and HostB 130 .
- networking module 114 broadcasts address resolution request packets to network host B 130 by transmitting address resolution request packets through the SAN 120 .
- Address resolution is a phase of network communications during which a host resolves network addresses of other hosts to physical addresses of the other hosts. The result of address resolution is that the mappings between network addresses and physical addresses are known. Address resolution is implemented in many different network standards, such as in IP communications and others.
- a different address resolution request packet is broadcast from each HostA port 112 .
- the HostB ports 132 receive the address resolution request packets and respond by providing address resolution response packets to the HostA ports 112 .
- the address resolution response packets also include information about the connection bandwidths of the remote HostB ports 132 .
- the networking module 114 processes the address resolution response packets to generate connectivity information, which describes all of the available communication routes between HostA 110 and HostB 130 and the connection bandwidths of the HostB ports 132 .
- the networking module 114 uses the connectivity information to select a subset of the communication routes for data transfer with HostB 130 .
- the subset of communication routes is selected in a manner that optimizes data transfer between HostA 110 and HostB 130 , even if one host has a different number of ports and/or ports with different connection bandwidths than the other host.
- the selection can be performed in an automatic manner at HostA 110 without the need for user intervention because the available routes and connection bandwidths of the HostB ports 132 are known to HostA 110 .
- obtaining connection bandwidth information during address resolution provides a simple and easy to implement technique for obtaining information about the capabilities of the HostB ports 130 that requires only minor modifications to existing address resolution mechanisms.
- the SAN 120 can be replaced with a generic network that represents the communication pathways between the HostA 110 and HostB 130 .
- the network can be an internal network or the Internet.
- the network uses standard communications technologies and/or protocols.
- the network can include links using technologies such as Ethernet, 802.11, integrated services digital network (ISDN), digital subscriber line (DSL), asynchronous transfer mode (ATM), etc.
- the networking protocols used on the network can include the transmission control protocol/Internet protocol (TCP/IP), the hypertext transport protocol (HTTP), the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc.
- the data exchanged over the network 120 can be represented using technologies and/or formats including the hypertext markup language (HTML), the extensible markup language (XML), etc.
- HTML hypertext markup language
- XML extensible markup language
- all or some of the links can be encrypted using conventional encryption technologies such as the secure sockets layer (SSL), Secure HTTP and/or virtual private networks (VPNs).
- SSL secure sockets layer
- VPNs virtual private networks
- FIG. 2 is a detailed view of a networking module 114 of FIG. 1 , according to one embodiment.
- Networking module 114 includes an address resolution module 204 , a connectivity module 206 , connectivity information 208 , a route selection module 210 and a data transfer module 212 .
- address resolution module 204 a connectivity module 206
- connectivity information 208 connectivity information 208
- route selection module 210 a route selection module 210
- data transfer module 212 a route selection module 210
- the address resolution module 204 generates address resolution request packets and broadcasts the address resolution request packets from the HostA ports 112 across the SAN 120 .
- a different address resolution request packet is broadcast from each HostA port 112 .
- one address resolution request packet is broadcast from port(A0) 112 and another address resolution request packet is broadcast from port(A1) 112 .
- An address resolution request packet broadcast from a given HostA port 112 can include the following fields, among others: the physical address of the HostA port 112 , the network address of the HostA port 112 , and the network address of HostB 130 .
- the address resolution request packet can include the connection bandwidth of the HostA port 112 .
- HostA port physical address 00-B0-D0-86-BB-F7 HostA network address 63.197.333.225
- the address resolution request packet is received at the HostB ports 132 , which respond by providing responses to the address resolution request packet.
- Each HostB port 132 provides its own response to the address resolution request packet in the form of an address resolution response packet. For example, port(B0) 132 returns an address resolution response packet to port(A0) 112 and port(B1) 132 also returns an address resolution response packet to port(A0) 112 .
- the address resolution response packet from a HostB port 132 can include the following fields: the physical address of the HostB Port 132 , a connection bandwidth of the HostB Port 132 , the network address of HostB 130 , the physical address of a HostA Port 112 and the network address of HostA 112 .
- the address resolution response packets include a field for the bandwidth of the HostB Port 132 .
- Conventional address resolution packets do not have a field for port bandwidth, so this bandwidth information may be transmitted in an optional extension field of an address resolution response packet.
- the optional extension field may be ignored by hosts that do not support the optional extension field.
- the address resolution module 204 then receives and decodes the address resolution response packets.
- the connectivity module 206 processes the address resolution response packets and generates connectivity information 208 describing available communication routes between HostA 110 and HostB 130 as well as the connection bandwidths of the HostB ports 132 .
- the available routes can be determined from the address resolution response packets.
- the connectivity module 206 assumes an available communication route exists between the HostA Port and the HostB Port and adds the route to the connectivity information 208 .
- the connectivity information 208 includes data that represents a connectivity matrix or connectivity map of the available communication routes.
- the connectivity information 208 can be stored in a computer-readable medium for later access, such as in a random access memory, solid state memory, etc.
- the connectivity information 208 includes a list of route entries for the available communication routes. Each route entry can include fields for: a timestamp of when the route entry was created or last updated, the physical address of a HostA port 112 , the HostA port bandwidth, the network address of HostB 130 , the physical address of a HostB port 132 , and the HostB port bandwidth. Most of the fields can be determined from the address resolution response packets, while the HostA port bandwidth can be determined locally by the connectivity module 206 .
- HostA port physical address 00-B0-D0-86-BB-F7 HostA port bandwidth 100 Mb/s HostB port physical address 1A-23-55-CE-15-F7 HostB port bandwidth 1 Gb/s HostB network address 63.197.333.222
- a route entry thus defines a communication route between a single HostA port 112 and a single HostB port 132 .
- the route entries represent all of the available communication routes through the SAN 120 between HostA 110 and HostB 130 .
- the address resolution module 204 periodically broadcasts new address resolution request packets from the HostA ports 112 .
- the connectivity module 206 can cull stale entries from the connectivity information 208 to account for changes in the SAN 120 if no responses to the address resolution request packets are received.
- the culling can occur at periodic intervals, such as 2.5 times the broadcast time of address resolution request packets. For example, if the periodic broadcast time is 3 seconds, route entries may be invalidated if they are 7.5 seconds old.
- the address resolution module 204 and connectivity module 206 thus work together to generate and continuously update the connectivity information 208 .
- the route selection module 210 selects a subset of the communication routes from the connectivity information 208 for data communications with remote HostB 110 .
- the route selection module 210 attempts to select a minimum number of routes that still consumes all of the available bandwidth for the HostA ports 112 or the HostB ports 132 .
- the exact communication routes that are selected depend on several factors, such as the number of HostA ports 112 , the number of HostB ports 132 , the bandwidths of the HostA ports 112 , and the bandwidths of the HostB ports 132 .
- Route selection can also re-occur periodically as the connectivity information 208 is updated. Route selection will be described in greater detail by reference to FIG. 4 .
- the data transfer module 212 transfers data with HostB 130 via the subset of communication routes selected by the route selection module 210 .
- Data transfer can include either receiving data from HostB 130 or transmitting data to HostB 130 for storage into the storage devices 140 .
- the data is divided amongst the selected communication routes in order to make full use of the available bandwidth between HostA 110 and HostB 130 .
- FIG. 3 is a flowchart illustrating a process of network communications performed by the networking module 114 of FIG. 1 , according to one embodiment.
- address resolution request packets are broadcast from HostA 110 to HostB 130 . Separate address resolution request packets are broadcast from each HostA port 112 .
- address resolution response packets are received from the HostB ports 132 that describe the connection bandwidths of the HostB ports 132 .
- the address resolution response packets are used to generate connectivity information 208 that describes available communication routes between HostA 110 and HostB 130 .
- the connectivity information also describes the connectivity bandwidths of the HostB ports 132 .
- step 308 using the connectivity information, a subset of the communication routes are selected for data transfer with HostB 130 .
- data is transferred with HostB 130 via the selected subset of communication routes.
- FIG. 4 is a flowchart illustrating a more detailed view for the step 308 of selecting a subset of routes from FIG. 3 , according to one embodiment.
- the available bandwidth for each HostA port 112 and each HostB port 132 is determined. Initially the available bandwidth for each port is equal to the connection bandwidth for the port as indicated in the connectivity information 208 .
- the total available bandwidth for HostA 110 is determined by combining the individual bandwidths of the HostA ports 112 .
- the total available bandwidth for HostB 130 is also determined by combining the individual bandwidths of the HostB ports 132 .
- step 404 the next hostA port with available bandwidth is selected.
- step 404 the next HostB port 132 with available bandwidth is selected.
- step 408 the selected HostA port 112 and the selected HostB port 132 are compared to the connectivity information 208 to determine if the HostA port 112 and HostB port 132 match an available route through the SAN 120 . If there is a match, the communication route is selected for data transfer in step 410 . For example, the selected communication route can be added to a table of selected communication routes. If there is not a match, the route selection process returns to step 406 to select the next HostB port 132 with available bandwidth.
- the available bandwidth for the selected HostA port 112 and the available bandwidth for the selected HostB port 132 are reduced, which indicates that some or all of the bandwidth of the ports has been allocated to a selected route.
- the amount of the reduction is equal to the smaller of the available bandwidth of the HostA port 112 and the HostB port 132 . For example, if the available bandwidth for a HostA port is 1 Gb/s and the available bandwidth for a HostB port 132 is 100 Mb/s, both ports would have their available bandwidth reduced by 100 Mb/s.
- the total available bandwidth for both HostA 110 and HostB 112 are also reduced in the same manner.
- step 414 it is determined if HostA 110 has any available bandwidth remaining. If so, in step 416 it is determined if HostB 130 has any available bandwidth remaining. If either HostA 110 or HostB 130 has no remaining bandwidth, the route selection process is completed because all of the available bandwidth has been consumed and there is no more bandwidth to be allocated.
- the process returns to step 404 and selects the next HostA port 112 with available bandwidth instead of selecting the same HostA port 112 from the previous iteration of the route selection process. For example, if HostA port(A0) was selected in one iteration of the route selection process, the next iteration will select HostA port(A1) for route selection. As a result, the HostA ports 112 are selected in a round-robin manner (A0 ⁇ A1 ⁇ A2 ⁇ A0 ⁇ A1 ⁇ A2) that balances data transmission across the ports of HostA.
- step 406 the next HostB port 132 with available bandwidth is selected instead of selecting the same HostB port 132 from the previous iteration of the route selection process. This also balances data transmission across the HostB ports 132 . The process repeats until all available bandwidth for the HostA ports 113 or the HostB ports 132 is consumed.
- the following examples illustrate route selections that are performed by the route selection process in FIG. 4 .
- HostA 110 has four 10 Gb/s ports 112 and HostB 130 also has four 10 Gb/s ports 132 .
- HostA's ports 112 are labeled A0, A1, A2 and A3.
- HostB's ports 132 are labeled B0, B1, B2 and B3.
- Table 1A The full connectivity matrix of routes between HostA 110 and HostB 130 can be visually represented in Table 1A as follows:
- HostA 110 could use every available route in transferring data with HostB 130 . However, this is unnecessary. Instead, the networking module 114 selects a subset of the routes for data transfer, so that from the available routes, the selected subset of routes would be as follows:
- the four selected routes represent the minimum subset of the available routes that still consumes all of the available bandwidth (40 Gb/s) between HostA 110 and HostB 130 .
- HostA 110 has four 1 Gb/s Ports 112 and HostB 130 also has two 10 Gb/s Ports 132 .
- HostA ports 112 are labeled A0, A1, A2 and A3.
- HostB ports 132 are labeled B0 and B1.
- Table 2A The full connectivity matrix of routes between HostA 110 and HostB 130 can be visually represented in Table 2A as follows:
- Route selection selects a subset of the routes for data transfer. Due to imbalance or mismatch between the bandwidths of the HostA ports 112 and the HostB ports 132 , the selected subset of routes would be as follows:
- the routes are selected such that HostB port B0 is matched with HostA ports A0 and A2.
- HostB port B1 is matched with HostA ports A1 and A3.
- the total bandwidth between HostA 110 and HostB 130 is 4 Gb/s, which is limited by the bandwidth of the HostA ports 112 .
- the 4 Gb/s bandwidth is split between the HostB ports 132 to balance data traffic amongst the HostB ports 132 .
- the routes are selected in a manner that can match ports with different connection bandwidths to each other.
- HostB port B0 has 10 Gb/s bandwidth but is still matched against HostA port A0, which only has 1 Gb/s bandwidth.
- HostA 110 has four 10 Gb/s Ports 112 and HostB 130 also has two 10 Gb/s Ports 132 .
- HostA ports 112 are labeled A0, A1, A2 and A3.
- HostB ports 132 are labeled B0 and B1.
- the full connectivity matrix of routes between HostA 110 and HostB 130 can be visually represented in Table 3A as follows:
- Route selection selects a subset of the routes for data transfer. Due to imbalance between the number of HostA ports 112 and the number of HostB ports 132 , the selected subset of routes would be as follows:
- two of the routes are selected for data transfer.
- the HostA ports A2 and A3 are not useful for data transfer as the total bandwidth is limited by the HostB ports 132 to 20 Gb/s.
- using additional routes actually creates a “Y” configuration whereby HostA 110 can create unnecessary network congestion by attempting to send 40 Gb/s of data when HostB 130 can only sustain 20 Gb/s of data.
- the two selected routes thus represent the minimum subset of available routes that still consume all of the available bandwidth (20 Gb/s) between HostA 110 and HostB 130 .
- FIG. 5 illustrates the hardware architecture of Network HostA 110 (or Network HostB 130 ), according to one embodiment.
- HostA is a server computer including components such as a processor 502 , a memory 503 , a storage module 504 , an input module (e.g., keyboard, mouse, and the like) 506 , a display module 507 and a communication interface 505 , exchanging data and control signals with one another through a bus 501 .
- the storage module 504 is implemented as one or more non-transitory computer readable storage media (e.g., hard disk drive, solid state memory, etc.), and stores software instructions that are executed by the processor 502 in conjunction with the memory 503 to implement the network communications described herein.
- the storage module 504 may include instructions in the form of a networking module 114 . Operating system software and other application software may also be stored in the storage module 504 to run on the processor 502 .
- the embodiments herein discover all available routes between hosts that have multiple physical network ports, as well as the connection bandwidths of the ports during address resolution. Using this information, a subset of routes can be selected for data transfer between the hosts. The routes are selected in a manner that fully utilizes the available bandwidth between the two hosts while also balancing data traffic across the ports of the hosts.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
HostA port physical address | 00-B0-D0-86-BB-F7 | ||
HostA network address | 63.197.333.225 | ||
HostB network address | 63.197.333.222 | ||
HostB port physical address | 1A-23-55-CE-15-F7 | ||
HostB port bandwidth | 1 Gb/s | ||
HostB network address | 63.197.333.222 | ||
HostA port physical address | 00-B0-D0-86-BB-F7 | ||
HostA network address | 63.197.333.225 | ||
Timestamp | 1:30 PM, Jul. 15, 2013 | ||
HostA port physical address | 00-B0-D0-86-BB-F7 | ||
|
100 Mb/s | ||
HostB port physical address | 1A-23-55-CE-15-F7 | ||
HostB port bandwidth | 1 Gb/s | ||
HostB network address | 63.197.333.222 | ||
TABLE 1A | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | B2 (10 Gb/s) | B3 (10 Gb/s) | |
A0 (10 Gb/s) | Available | Available | Available | Available |
A1 (10 Gb/s) | Available | Available | Available | Available |
A2 (10 Gb/s) | Available | Available | Available | Available |
A3 (10 Gb/s) | Available | Available | Available | Available |
TABLE 1B | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | B2 (10 Gb/s) | B3 (10 Gb/s) | |
A0 (10 Gb/s) | Selected | |||
A1 (10 Gb/s) | Selected | |||
A2 (10 Gb/s) | Selected | |||
A3 (10 Gb/s) | Selected | |||
TABLE 2A | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | |||
A0 (1 Gb/s) | Available | Available | ||
A1 (1 Gb/s) | Available | Available | ||
A2 (1 Gb/s) | Available | Available | ||
A3 (1 Gb/s) | Available | Available | ||
TABLE 2B | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | |||
A0 (1 Gb/s) | Selected | |||
A1 (1 Gb/s) | Selected | |||
A2 (1 Gb/s) | Selected | |||
A3 (1 Gb/s) | Selected | |||
TABLE 3A | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | |||
A0 (10 Gb/s) | Available | Available | ||
A1 (10 Gb/s) | Available | Available | ||
A2 (10 Gb/s) | Available | Available | ||
A3 (10 Gb/s) | Available | Available | ||
TABLE 3B | ||||
B0 (10 Gb/s) | B1 (10 Gb/s) | |||
A0 (10 Gb/s) | Selected | |||
A1 (10 Gb/s) | Selected | |||
A2 (10 Gb/s) | ||||
A3 (10 Gb/s) | ||||
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/950,188 US9270578B2 (en) | 2013-07-24 | 2013-07-24 | Management of multiple network routes |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/950,188 US9270578B2 (en) | 2013-07-24 | 2013-07-24 | Management of multiple network routes |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150030025A1 US20150030025A1 (en) | 2015-01-29 |
US9270578B2 true US9270578B2 (en) | 2016-02-23 |
Family
ID=52390503
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/950,188 Expired - Fee Related US9270578B2 (en) | 2013-07-24 | 2013-07-24 | Management of multiple network routes |
Country Status (1)
Country | Link |
---|---|
US (1) | US9270578B2 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6241319B2 (en) * | 2014-02-28 | 2017-12-06 | 富士通株式会社 | Information processing apparatus, communication path determination program, and communication path determination method |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6081845A (en) * | 1997-03-18 | 2000-06-27 | Fujitsu Limited | ARP server |
US20020085586A1 (en) * | 2000-11-14 | 2002-07-04 | Altima Communications, Inc. | Linked network switch configuration |
US20040088451A1 (en) * | 2002-11-01 | 2004-05-06 | Samsung Electronics Co., Ltd. | Device and method for controlling packet flow |
US20050080874A1 (en) * | 2003-10-14 | 2005-04-14 | Hitachi, Ltd. | Storage device and system for providing communications buffer reservation function |
US20080002739A1 (en) * | 2006-06-30 | 2008-01-03 | Sun Microsystems, Inc. | Reflecting the bandwidth assigned to a virtual network interface card through its link speed |
US20080056132A1 (en) * | 2006-08-30 | 2008-03-06 | Mcgee Michael Sean | method and system of network communication receive load balancing |
US7843906B1 (en) * | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
US20130051232A1 (en) * | 2011-08-30 | 2013-02-28 | International Business Machines Corporation | Managing data on infiniband (ib) networks |
US20140078935A1 (en) * | 2011-05-18 | 2014-03-20 | Zte Corporation | Multi-Interface Terminal, and Neighbor Topology Discovery and Cooperative Communication Method Therefore |
US8909766B1 (en) * | 2011-10-04 | 2014-12-09 | Amazon Technologies, Inc. | Techniques for providing information about network connection status |
-
2013
- 2013-07-24 US US13/950,188 patent/US9270578B2/en not_active Expired - Fee Related
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6081845A (en) * | 1997-03-18 | 2000-06-27 | Fujitsu Limited | ARP server |
US20020085586A1 (en) * | 2000-11-14 | 2002-07-04 | Altima Communications, Inc. | Linked network switch configuration |
US20040088451A1 (en) * | 2002-11-01 | 2004-05-06 | Samsung Electronics Co., Ltd. | Device and method for controlling packet flow |
US20050080874A1 (en) * | 2003-10-14 | 2005-04-14 | Hitachi, Ltd. | Storage device and system for providing communications buffer reservation function |
US7843906B1 (en) * | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
US20080002739A1 (en) * | 2006-06-30 | 2008-01-03 | Sun Microsystems, Inc. | Reflecting the bandwidth assigned to a virtual network interface card through its link speed |
US20080056132A1 (en) * | 2006-08-30 | 2008-03-06 | Mcgee Michael Sean | method and system of network communication receive load balancing |
US20140078935A1 (en) * | 2011-05-18 | 2014-03-20 | Zte Corporation | Multi-Interface Terminal, and Neighbor Topology Discovery and Cooperative Communication Method Therefore |
US20130051232A1 (en) * | 2011-08-30 | 2013-02-28 | International Business Machines Corporation | Managing data on infiniband (ib) networks |
US8909766B1 (en) * | 2011-10-04 | 2014-12-09 | Amazon Technologies, Inc. | Techniques for providing information about network connection status |
Also Published As
Publication number | Publication date |
---|---|
US20150030025A1 (en) | 2015-01-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11563672B2 (en) | Financial network | |
JP4740897B2 (en) | Virtual network configuration method and network system | |
JP4053967B2 (en) | VLAN server | |
US7165258B1 (en) | SCSI-based storage area network having a SCSI router that routes traffic between SCSI and IP networks | |
CN107078974B (en) | Network switch, method executed by network switch and memory resource | |
US20140355441A1 (en) | Method and apparatus of delivering assured services over unreliable internet infrastructure by using virtual overlay network architecture over a public cloud backbone | |
US20130007253A1 (en) | Method, system and corresponding device for load balancing | |
US6785715B2 (en) | Storage subsystem | |
US11489921B2 (en) | Kickstart discovery controller connection command | |
US11489723B2 (en) | Multicast domain name system (mDNS)-based pull registration | |
US8310953B2 (en) | Method and apparatus for enabling an adapter in a network device to discover the name of another adapter of another network device in a network system | |
US11240308B2 (en) | Implicit discovery controller registration of non-volatile memory express (NVMe) elements in an NVME-over-fabrics (NVMe-oF) system | |
US20120191769A1 (en) | Site-aware distributed file system access from outside enterprise network | |
US12052171B2 (en) | Communication system and communication method | |
US20210286741A1 (en) | Symbolic names for non-volatile memory express (nvme) elements in an nvme-over-fabrics (nvme-of) system | |
US9985840B2 (en) | Container tracer | |
US20110246600A1 (en) | Memory sharing apparatus | |
US9641611B2 (en) | Logical interface encoding | |
EP2991288A1 (en) | Method and device for determining next hop and distributing routing information | |
WO2014098117A1 (en) | Communication node, control device, method for managing control information entries, and program | |
US10574579B2 (en) | End to end quality of service in storage area networks | |
US9270578B2 (en) | Management of multiple network routes | |
CN101170544A (en) | A communication method in high-availability cluster system based on single practical IP address | |
WO2013069133A1 (en) | Frame relay apparatus, communication system, and data transfer method | |
KR101814411B1 (en) | Device capability addressable network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CORAID, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOPKINS, SAMUEL A.;SANDERS, SHERMAN J.;STALLION, STEVEN E.;SIGNING DATES FROM 20130722 TO 20130724;REEL/FRAME:030879/0770 |
|
AS | Assignment |
Owner name: TRIPLEPOINT CAPITAL LLC, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:CORAID, INC.;REEL/FRAME:031869/0790 Effective date: 20131224 |
|
AS | Assignment |
Owner name: TRIPLEPOINT VENTURE GROWTH BDC CORP., CALIFORNIA Free format text: ASSIGNMENT OF SECURITY AGREEMENT (REEL 031869, FRAME 0790);ASSIGNOR:TRIPLEPOINT CAPITAL LLC;REEL/FRAME:032410/0347 Effective date: 20140305 |
|
AS | Assignment |
Owner name: INTERMODAL DATA, INC., CALIFORNIA Free format text: SECURED PARTY BILL OF SALE;ASSIGNOR:CORAID, INC.;REEL/FRAME:035827/0886 Effective date: 20150415 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: TRIPLEPOINT VENTURE GROWTH BDC CORP., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:INTERMODAL DATA, INC.;REEL/FRAME:038576/0311 Effective date: 20150415 Owner name: INTERMODAL DATA, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CORAID, INC.;REEL/FRAME:038576/0184 Effective date: 20150415 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200223 |