Routing encapsulated data packets onto selected VLANs
AssigneeHewlett-Packard Development Company, L.P.
InventorsMichael Schlansker, Jean Tourrilhes, Jose Renato G. Santos, Stephen G. Low, Paul Allen Bottorff
Life of this patent
Estimating the term…
Abstract
A system and method are provided to route packets in a data center network. Individual packets are encapsulated at an edge of the data center network, so that each encapsulated packet includes a set of header fields, such as a tenant identifier. For each encapsulated packet, a hash class is determined from the set of header fields. A routing virtual local area network (VLAN) is selected for the packet based on the tenant identifier and the hash class.
Claims15
A method for routing packets in a data center network, the method being implemented by one or more network devices of the data center network and comprising:
- receiving individual packets at an entry location of the data center network, each of the individual packets including initial header fields corresponding to at least a tenant destination address (TDA) and a tenant source address (TSA);
- encapsulating each of the individual packets to include additional header fields, the additional header fields corresponding to a tenant identifier, the entry location, an exit location of the data center network, and a virtual local area network (VLAN) of the entry location;
- for each encapsulated packet, hashing the additional header fields to determine a hash class for the encapsulated packet;
- selecting a routing VLAN for the encapsulated packet based on at least the tenant identifier and the hash class;
- and
- overwriting the additional header field corresponding to the VLAN of the entry location with the selected routing VLAN.
A system for routing packets on a data center network, the system comprising:
- a network device to:
- receive individual packets at an entry location of the data center network, each of the individual packets including initial header fields corresponding to at least a tenant destination address (TDA) and a tenant source address (TSA);
- encapsulate each of the individual packets to include additional header fields, the additional header fields corresponding to a tenant identifier, the entry location, an exit location of the data center network, and a virtual local area network (VLAN) of the entry location;
- for each encapsulated packet, hashing the additional header fields to determine a hash class for the encapsulated packet;
- select a routing VLAN for the encapsulated packet based on at least the tenant identifier and the hash class;
- and
- overwrite the additional header field corresponding to the VLAN of the entry location with the selected routing VLAN;
- and
- a controller to optimize routing information for use by the network device based on measured traffic information on the data center network.
A system for routing packets in a data center network, the system comprising:
- one or more edge devices for the data center network;
- one or more controllers that communicate information to the one or more edge devices, the information including topology information for the data center network;
- wherein the one or more edge devices:
- receive individual packets each including initial header fields corresponding to at least a tenant destination address (TDA) and a tenant source address (TSA);
- encapsulate each of the individual packets to include additional header fields, the additional header fields corresponding to a tenant identifier, an entry location for the individual packet, and exit location for the encapsulated packet from the data center network, and a virtual local area network (VLAN) of the entry location;
- for each encapsulated packet, hash the additional header fields to determine a hash class for the encapsulated packet;
- select a routing VLAN for the encapsulated packet based on at least the tenant identifier and the hash class;
- and
- overwrite the additional header field corresponding to the VLAN identifier of the entry location with the selected routing VLAN.
Dependencies are inferred from the claim text.