WO2016124155A1 - Packet transmission - Google Patents

Packet transmission Download PDF

Info

Publication number
WO2016124155A1
WO2016124155A1 PCT/CN2016/073608 CN2016073608W WO2016124155A1 WO 2016124155 A1 WO2016124155 A1 WO 2016124155A1 CN 2016073608 W CN2016073608 W CN 2016073608W WO 2016124155 A1 WO2016124155 A1 WO 2016124155A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
management
port
server
vlan
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.)
Ceased
Application number
PCT/CN2016/073608
Other languages
French (fr)
Inventor
Donghong YANG
Yin Liang
Xiyuan PAN
Dian WANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies Co Ltd
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 Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Publication of WO2016124155A1 publication Critical patent/WO2016124155A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing

Definitions

  • a Data Center (DC) server may be managed via an Integrated Light-Out (ILO) port, also called a server out-of-band management port.
  • ILO is also referred to as “in case of line out” .
  • the ILO port is a separate dedicated physical port, and the DC server sets a physical port aside as the ILO port. Management packets are transmitted between a network management device and the DC server via the ILO port.
  • a dedicated management network is necessary so that the network management device can manage the DC server via the ILO port.
  • the management network is separate from a service network of the DC server.
  • Figure 1 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure.
  • Figure 2 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure.
  • Figure 3 is a schematic diagram illustrating the structure of a DC network according to some examples of the present disclosure.
  • Figure 4 is a schematic diagram illustrating a TOR device according to some examples of the present disclosure.
  • Figure 5 is a schematic diagram illustrating a hardware structure of a TOR device according to some examples of the present disclosure.
  • a DC server sets a physical port aside as an ILO port.
  • a network management device transmits management packets via the ILO port, so as to manage the DC server. Accordingly, physical port resources of the DC server are occupied.
  • a dedicated management network is necessary so that the network management device can manage the DC server, which causes high network construction costs.
  • FIG. 1 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure.
  • the method may be applicable to an Intelligent Resilient Framework (IRF) system.
  • IRF Intelligent Resilient Framework
  • multiple network devices may be connected through physical IRF ports and may be virtualized into a device after necessary configurations are performed.
  • the method includes the following blocks.
  • a top-of-rack (TOR) device receives a layer 3 management packet whose destination address is an address of a DC server from a network management center.
  • the layer 3 management packet carries a tag of a management Virtual Local Area Network (VLAN) for indicating the layer 3 management packet to be transmitted in the management VLAN.
  • VLAN Virtual Local Area Network
  • the TOR device searches an Address Resolution Protocol (ARP) forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtains an egress port of the layer 3 management packet.
  • ARP Address Resolution Protocol
  • the egress port is a physical port in an aggregation port, and the egress port is bound with the management VLAN and is connected with a physical port bound with the management VLAN on the DC server.
  • the physical ports bound with the management VLAN may be also bound with a service VLAN.
  • the TOR device transmits the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
  • a physical port in the aggregation port for transmitting service packets of the DC server is bound with the management VLAN.
  • the management packet is transmitted via the physical port bound with the management VLAN after the management packet is received.
  • the management packet may be transmitted via a service network and it is unnecessary to set a physical port for transmitting management packets aside, thereby reducing network construction costs and utilizing physical port resources of the IRF system effectively.
  • forwarding entries used for transmitting management packets in the ARP forwarding table may be preconfigured by a user or obtained by the TOR device via learning.
  • the TOR device broadcasts a first ARP request packet, and the first ARP request packet carries the address of the DC server and the tag of the management VLAN.
  • the TOR device receives a first ARP response packet from the DC server.
  • a port receiving the first ARP response packet is configured as the egress port corresponding to the address of the DC server and the management VLAN.
  • the port receiving the first ARP response packet is a physical port included in the aggregation port.
  • the TOR device may learn and obtain the ARP forwarding table via the following processing.
  • a TOR switch After a TOR switch receives a layer 3 management VLAN packet from a network management device, if it is determined that an ARP forwarding table does not include a forwarding entry corresponding to a management VLAN tag and a destination Internet Protocol (IP) address which are carried by the layer 3 management VLAN packet, the TOR switch broadcasts an ARP request packet.
  • the ARP request packet carries the management VLAN tag, a destination IP address of the ARP request packet is the destination address of the layer 3 management VLAN packet, and a destination Media Access Control (MAC) address is a broadcast MAC address.
  • IP Internet Protocol
  • the DC server after any one DC server connected to the TOR switch receives the ARP request packet if the DC server determines that the destination IP address of the ARP request packet is an IP address of the DC server, the DC server returns a ARP response packet.
  • the ARP response packet carries the management VLAN tag, and a source IP address and a source MAC address of the ARP response packet are the IP address and a MAC address of the DC server respectively.
  • the TOR switch receives the ARP response packet, learns and obtains a forwarding entry as follows.
  • IP address the source IP address of the ARP response packet
  • MAC address the source MAC address of the ARP response packet
  • VLAN tag the management VLAN tag
  • egress port an ingress physical port of the ARP response packet.
  • an ingress port of the ARP response packet is an aggregation port
  • the egress port in the forwarding entry is configured as an ingress physical port
  • the ingress physical port is a physical port connected with a physical port bound with the management VLAN on the DC server.
  • the egress port of the forwarding entry is configured as the aggregation port.
  • the TOR device is located in an Intelligent Resilient Framework (IRF) system.
  • IRF Intelligent Resilient Framework
  • the TOR device is located in the IRF system.
  • the TOR device receives a layer 3 service packet from a core network, and the layer 3 service packet carries an address of a DC server and a tag of a service VLAN.
  • the TOR device searches a ARP forwarding table according to the address of the DC server and the tag of the service VLAN, and obtains an egress port of the layer 3 service packet.
  • the egress port of the layer 3 service packet is an aggregation port.
  • the TOR device distributes the layer 3 service packet to a physical port included in the aggregation port for transmission.
  • the forwarding entries used for transmitting service packets may be preconfigured by a user or obtained by the TOR device via learning.
  • the TOR device broadcasts a second ARP request packet, and the second ARP request packet carries the address of the DC server and the tag of the service VLAN.
  • the TOR device receives a second ARP response packet from the DC server.
  • an aggregation port including a physical port receiving the second ARP response packet is recorded as the egress port corresponding to the address of the DC server and the service VLAN.
  • the physical port bound with the management VLAN may be used for transmit management packets
  • the physical port bound with the service VLAN may be used for transmit service packets.
  • the physical port may bound with both the management VLAN and the service VLAN.
  • the aggregation port may be regarded as being bound with the service VLAN. After the aggregation port is found according to the destination address of the service packet and the tag of the service VLAN, one or more physical ports may be selected from the physical ports bounding with the service VLAN in the aggregation port according to load sharing algorithm and may be used for transmitting service packets.
  • the TOR device synchronizes the ARP forwarding table to other TOR devices in the same IRF system.
  • the TOR device is a TOR switch.
  • Figure 2 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure. As shown in Figure 2, the method includes the following block.
  • a management VLAN is configured to manage DC servers in advance.
  • a tag of the management VLAN is VLAN 401.
  • the physical port bound with the management VLAN on the DC server is called a first physical port.
  • the first physical port may be also bound with a service VLAN, so as to transmit service packets.
  • an egress port in a forwarding entry corresponding to the management VLAN is configured as each physical port which is on the TOR switch and is connected with a first physical port of each DC server connected with the TOR switch.
  • an egress port in the forwarding entry is configured as a physical port which is on the TOR switch and is connected with a first physical port of the DC server.
  • the TOR switch receives a layer 3 management packet from a network management device, finds a forwarding entry according to the tag of the management VLAN and a destination address of the layer 3 management packet, and sends the layer 3 management packet to a DC server according to an egress port in the found forwarding entry.
  • the management VLAN for managing DC servers is configured.
  • the egress port in the forwarding entry is configured as the physical port on the TOR device which is connected with the physical port bound with the managing WLAN on the DC server.
  • the physical port on the DC server may be bound with the service VLAN after bounded with the management VLAN. Accordingly, both management packets and service packets may be transmitted via the physical port. Therefore, it is unnecessary for the DC server to set a physical port for transmitting management packets aside, thereby utilizing physical port resources of the DC server effectively.
  • layer 3 management packets may be successfully transmitted in an service network. Accordingly, it is unnecessary to establish a dedicated management network separate from the service network, thereby saving network establishment costs.
  • FIG 3 is a schematic diagram illustrating the structure of a DC network according to some examples of the present disclosure.
  • a IRF system includes a TOR switch 1 and a TOR switch 2, and a DC server 1 and a DC server 2 are connected with the IRF system.
  • the physical port P11 of the DC server 1 is connected with the physical port G1/0/1 of the TOR switch 1.
  • the physical port P12 of the DC server 1 is connected with the physical port G2/0/1 of the TOR switch 2.
  • the physical port P21 of the DC server 2 is connected with the physical port G1/0/2 of the TOR switch 1.
  • the physical port P22 of the DC server 2 is connected with the physical port G2/0/2 of the TOR switch 2.
  • the physical port G1/0/1 of the TOR switch 1 and the physical port G2/0/1 of the TOR switch 2 are bound as an aggregation port G1 according to Link Aggregation Control Protocol (LACP)
  • LACP Link Aggregation Control Protocol
  • the physical port G1/0/2 of the TOR switch 1 and the physical port G2/0/2 of the TOR switch 2 are bound as an aggregation port G2 according to the LACP.
  • the physical port P11 of the DC server 1 is bound with a management VLAN 401, and the physical port P21 of the DC server 2 is bound with the management VLAN 401.
  • the physical port G1/0/1 connected with the physical port P11 is bound with the management VLAN 401
  • the physical port G1/0/2 connected with the physical port P21 is bound with the management VLAN 401.
  • an egress port in a forwarding entry corresponding to the management VLAN 401 may be configured as the physical port G1/0/1 or the physical port G1/0/2.
  • the following procedure is performed when the TOR switch learns the ARP forwarding table.
  • the TOR switch 1 receives an ARP response packet sent by the DC server 1 via the physical port G1/0/1 and learns a forwarding entry.
  • the TOR switch 1 discovers that a VLAN tag in the ARP response packet is VLAN 401, and configures an egress port of the forwarding entry as the ingress physical port G1/0/1 (rather than the ingress aggregation port G1) according to the above configurations.
  • the TOR switch 1 receives an ARP response packet sent by the DC server 2 via the physical port G1/0/2 and learns a forwarding entry.
  • the TOR switch 1 discovers that a VLAN tag in the ARP response packet is VLAN 401, and configures an egress port of the forwarding entry as the ingress physical port G1/0/2 (rather than the ingress aggregation port G1) according to the above configurations in B.
  • the TOR switch 1 receives an ARP response packet sent by the DC server 1 via the physical port G1/0/1 and learns a forwarding entry.
  • the TOR switch 1 discovers that a VLAN tag in the ARP response packet is a service VLAN, and configures an egress port of the forwarding entry as the aggregation port G1 corresponding to the ingress physical port G1/0/1.
  • the TOR switch 1 receives an ARP response packet sent by the DC server 2 via the physical port G1/0/2 and learns a forwarding entry.
  • the TOR switch 1 discovers that a VLAN tag in the ARP response packet is the service VLAN, and configures an egress port of the forwarding entry as the aggregation port G2 corresponding to the ingress physical port G1/0/2.
  • an egress port is configured as the aggregation port G1 or G2.
  • the device may synchronize the new forwarding entry to other devices in the IRF system.
  • the procedure of forwarding the layer 3 management packet by the TOR switch includes the following processing.
  • the TOR switch 1 receives a layer 3 management packet sent from a network management device to the DC server 1.
  • the VLAN tag in the packet is the VLAN 401
  • the destination IP address of the packet is the address of the DC server 1.
  • the TOR switch 1 locally searches out a forwarding entry corresponding to the packet, and sends the packet according to the egress port in the forwarding entry, i. e. the physical port G1/0/1.
  • the packet may arrive at the physical port P11 of the DC server 1.
  • the TOR switch 1 receives a layer 3 management packet sent from the network management device to the DC server 2.
  • the VLAN tag in the packet is the VLAN 401, and the destination IP address of the packet is the address of the DC server 2.
  • the TOR switch 1 locally searches out a forwarding entry corresponding to the packet, and sends the packet according to the egress port in the forwarding entry, i. e. the physical port G1/0/2.
  • the packet may arrive at the physical port P21 of the DC server 2.
  • the TOR switch 1 Because the TOR switch 1 has synchronized the learned forwarding entry of the management VLAN 401 to the TOR switch 2, if the TOR switch 2 receives a layer 3 management packet sent from the network management device to the DC server 1 or the DC server 2, the TOR switch 2 may find an forwarding entry corresponding to the received packet in an ARP forwarding table, and determine the egress port (G1/0/1 or G1/0/2) of the forwarding entry is located on the TOR switch 1. The TOR switch 2 sends the packet and information of the egress port to the TOR switch 1. After receiving the packet and information of the egress port, the TOR switch 1 directly sends the packet according to the information of the egress port.
  • the procedure of forwarding the layer 3 service packet by the TOR switch includes the following processing.
  • the TOR switch 1 receives a layer 3 service packet sent from a core network, searches the ARP forwarding table stored locally according to the VLAN tag and the destination address in the service packet, and finds a forwarding entry corresponding to the packet.
  • the TOR switch 1 determines that the egress port in the forwarding entry is the aggregation port, and according to load sharing algorithm, distributes the packet to a physical port included in the aggregation port to send the packet.
  • a calculation process is performed by the TOR switch according to a predefined hash algorithm, e.g. a hash calculation may be performed for five tuple information of the received layer 3 service packet, and maps a calculation result to a physical port included in the aggregation port, e.g. G1/0/1 or G2/0/1.
  • the TOR switch 1 then sends the packet via the mapped physical port. If the calculation result is mapped to the G2/0/1, the TOR switch 1 sends the service packet to the TOR switch 2, and the TOR switch 2 sends the service packet via the port G2/0/1.
  • the procedure of forwarding the layer 3 service packet by the TOR switch 2 is similar with that performed by the TOR switch 1.
  • the layer 3 management packets may be forwarded via a fixed physical port in the IRF system, and the layer 3 service packets may be forwarded via the physical ports in the IRF system according to the load balance algorithm.
  • FIG. 4 is a schematic diagram illustrating a TOR device according to some examples of the present disclosure.
  • the TOR device includes a non-transitory storage medium 410 and a processor 420.
  • the non-transitory storage medium 410 may store machine readable instructions that can be executed by the processor 420.
  • the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to perform a process of:
  • the layer 3 management packet whose destination address is an address of a DC server from a network management center, the layer 3 management packet carrying a tag of a management VLAN for indicating the layer 3 management packet to be transmitted in the management VLAN;
  • the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server; the physical port being bound with a service VLAN; and
  • the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
  • the broadcasting a first ARP request packet; the first ARP request packet carrying the address of the DC server and the tag of the management VLAN;
  • the port receiving the first ARP response packet being a physical port included in the aggregation port.
  • the TOR device is located in a IRF system, and the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
  • the egress port of the layer 3 service packet being the aggregation port;
  • the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
  • the second ARP request packet carrying the address of the DC server and the tag of the service VLAN;
  • an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  • the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of: synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
  • a non-transitory storage medium may store machine readable instructions, and a processor may read the machine readable instructions stored in the non-transitory storage medium to perform a process of:
  • the layer 3 management packet whose destination address is an address of a DC server from a network management center; the layer 3 management packet carrying a tag of a management VLAN for indicating the layer 3 management packet to be transmitted in the management VLAN;
  • the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server; the physical port being bound with a service VLAN; and
  • the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
  • the broadcasting a first ARP request packet; the first ARP request packet carrying the address of the DC server and the tag of the management VLAN;
  • the port receiving the first ARP response packet being a physical port included in the aggregation port.
  • the TOR device is located in a IRF system, and the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
  • the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
  • the second ARP request packet carrying the address of the DC server and the tag of the service VLAN;
  • an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  • the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of: synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
  • the non-transitory storage medium for storing the machine readable instructions may be any electric, magnetic or optical storage medium or other physical storage medium.
  • the machine readable storage medium may include or store information, e.g. executable instructions and data etc.
  • the non-transitory storage medium may be a Radom Access Memory (RAM) , a Flash card, a storage driver (e.g. a disk driver) , a solid-state disk, a storage disk of any type (e.g. an optical disk, a DVD) , or a similar storage medium, or any combination of the above.
  • FIG. 5 is a schematic diagram illustrating a hardware structure of a TOR device according to some examples of the present disclosure.
  • the TOR device includes a receiving unit 510, a searching unit 520 and a transmitting unit 530.
  • the receiving unit 510 is to receive a layer 3 management packet whose destination address is an address of a DC server from a network management center.
  • the layer 3 management packet carries a tag of a management VLAN for indicating that the layer 3 management packet to be transmitted in the management VLAN.
  • the searching unit 520 is to search an ARP forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtain an egress port of the layer 3 management packet.
  • the egress port is a physical port in an aggregation port, and the physical port is bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server; the physical port is bound with a service VLAN.
  • the transmitting unit 530 is to transmit the layer 3 management packet to the DC server via the egress port of the layer management packet.
  • the transmitting unit 530 is further to broadcast a first ARP request packet; the first ARP request packet carries the address of the DC server and the tag of the management VLAN.
  • the receiving unit 510 is further to receive a first ARP response packet sent by the DC server.
  • the TOR device further includes a configuring unit 540.
  • the configuring unit 540 is to configure a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table; the port receiving the first ARP response packet is a physical port included in the aggregation port.
  • the TOR device is located in a IRF system.
  • the receiving unit 510 is further to receive a layer 3 service packet from a core network, and the layer 3 service packet carries the address of the DC server and a tag of the service VLAN.
  • the searching unit 520 is further to search the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtain an egress port of the layer 3 service packet.
  • the egress port of the layer 3 service packet is the aggregation port.
  • the transmitting unit 530 is further to transmit the service packet via a physical port included in the aggregation port according to preconfigured load sharing algorithm.
  • the transmitting unit 530 is further to broadcast a second ARP request packet; the second ARP request packet carries the address of the DC server and the tag of the management VLAN.
  • the receiving unit 510 is further to receive a second ARP response packet sent by the DC server.
  • the configuration unit 540 is further to configure an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  • the transmitting unit 530 is further to synchronize the ARP forwarding table to each of other TOR devices in the IRF system.

Landscapes

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

Abstract

In an example, a TOR device receives a layer 3 management packet whose destination address is an address of a DC server from a network management center, the layer 3 management packet carries a tag of a management VLAN for indicating the layer 3 management packet to be transmitted in the management VLAN. The TOR device searches an ARP forwarding table according to the tag of the management VLAN and the destination address, and obtains an egress port of the layer 3 management packet. The egress port is a physical port in an aggregation port, the physical port is bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server, and is bound with a service VLAN. The TOR device transmits the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.

Description

PACKET TRANSMISSION
This application claims the benefit of priority from Chinese Patent Application No. 201510064873.3, entitled “Method and apparatus for managing data center servers” , filed on February 6, 2015, the entire content of which is hereby incorporated by reference.
Background
A Data Center (DC) server may be managed via an Integrated Light-Out (ILO) port, also called a server out-of-band management port. ILO is also referred to as “in case of line out” . The ILO port is a separate dedicated physical port, and the DC server sets a physical port aside as the ILO port. Management packets are transmitted between a network management device and the DC server via the ILO port.
A dedicated management network is necessary so that the network management device can manage the DC server via the ILO port. The management network is separate from a service network of the DC server.
Brief Description of the Drawings
Features of the present disclosure are illustrated by way of example and not limited in the following figure (s) , in which like numerals indicate like elements, in which:
Figure 1 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure.
Figure 2 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure.
Figure 3 is a schematic diagram illustrating the structure of a DC network according to some examples of the present disclosure.
Figure 4 is a schematic diagram illustrating a TOR device according to some examples of the present disclosure.
Figure 5 is a schematic diagram illustrating a hardware structure of a TOR device according to some examples of the present disclosure.
Detailed Description
For simplicity and illustrative purposes, the present disclosure is described by referring mainly to an example thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure. Throughout the present disclosure, the terms “a” and “an” are intended to denote at least one of a particular element. As used herein, the term “includes” means includes but not limited to, the term “including” means including but not limited to.
In a management packet transmission method, a DC server sets a physical port aside as an ILO port. A network management device transmits management packets via the ILO port, so as to manage the DC server. Accordingly, physical port resources of the DC server are occupied. In addition, a dedicated management network is necessary so that the network management device can manage the DC server, which causes high network construction costs.
Figure 1 is a schematic flowchart illustrating a packet transmission method according to some examples of the present disclosure. The method may be applicable to an Intelligent Resilient Framework (IRF) system. In the IRF system, multiple network devices may be connected through physical IRF ports and may be virtualized into a device after necessary configurations are performed.
As shown in Figure 1, the method includes the following blocks.
At block 101, a top-of-rack (TOR) device receives a layer 3 management packet whose destination address is an address of a DC server from a network management center. The layer 3 management packet carries a tag of a management Virtual Local Area Network (VLAN) for indicating the layer 3 management packet to be transmitted in the management VLAN.
At block 102, the TOR device searches an Address Resolution Protocol (ARP) forwarding table according to the tag of the management VLAN and the  destination address of the layer 3 management packet, and obtains an egress port of the layer 3 management packet. The egress port is a physical port in an aggregation port, and the egress port is bound with the management VLAN and is connected with a physical port bound with the management VLAN on the DC server. The physical ports bound with the management VLAN may be also bound with a service VLAN.
At block 103, the TOR device transmits the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
In some examples, a physical port in the aggregation port for transmitting service packets of the DC server is bound with the management VLAN. The management packet is transmitted via the physical port bound with the management VLAN after the management packet is received. Thus, the management packet may be transmitted via a service network and it is unnecessary to set a physical port for transmitting management packets aside, thereby reducing network construction costs and utilizing physical port resources of the IRF system effectively.
In some examples, forwarding entries used for transmitting management packets in the ARP forwarding table may be preconfigured by a user or obtained by the TOR device via learning. In some examples, the TOR device broadcasts a first ARP request packet, and the first ARP request packet carries the address of the DC server and the tag of the management VLAN. The TOR device receives a first ARP response packet from the DC server. In the ARP forwarding table, a port receiving the first ARP response packet is configured as the egress port corresponding to the address of the DC server and the management VLAN. The port receiving the first ARP response packet is a physical port included in the aggregation port.
In some examples, the TOR device may learn and obtain the ARP forwarding table via the following processing.
a. after a TOR switch receives a layer 3 management VLAN packet from a network management device, if it is determined that an ARP forwarding table does not include a forwarding entry corresponding to a management VLAN tag and a destination Internet Protocol (IP) address which are carried by the layer 3 management VLAN packet, the TOR switch broadcasts an ARP request packet. The ARP request packet carries the  management VLAN tag, a destination IP address of the ARP request packet is the destination address of the layer 3 management VLAN packet, and a destination Media Access Control (MAC) address is a broadcast MAC address.
b. after any one DC server connected to the TOR switch receives the ARP request packet if the DC server determines that the destination IP address of the ARP request packet is an IP address of the DC server, the DC server returns a ARP response packet. The ARP response packet carries the management VLAN tag, and a source IP address and a source MAC address of the ARP response packet are the IP address and a MAC address of the DC server respectively.
c. the TOR switch receives the ARP response packet, learns and obtains a forwarding entry as follows.
IP address: the source IP address of the ARP response packet；
MAC address: the source MAC address of the ARP response packet；
VLAN tag: the management VLAN tag；
egress port: an ingress physical port of the ARP response packet.
In some examples, if an ingress port of the ARP response packet is an aggregation port, the egress port in the forwarding entry is configured as an ingress physical port, and the ingress physical port is a physical port connected with a physical port bound with the management VLAN on the DC server. While in processing of learning a forwarding entries of a service VLAN, if the ingress port of the ARP response packet is the aggregation port, the egress port of the forwarding entry is configured as the aggregation port.
In some examples, the TOR device is located in an Intelligent Resilient Framework (IRF) system. When the TOR device determines that a new forwarding entry in the ARP forwarding table is configured or learned, the new forwarding entry is synchronized to other TOR devices in the IRF system.
In some examples, the TOR device is located in the IRF system. The TOR  device receives a layer 3 service packet from a core network, and the layer 3 service packet carries an address of a DC server and a tag of a service VLAN. The TOR device searches a ARP forwarding table according to the address of the DC server and the tag of the service VLAN, and obtains an egress port of the layer 3 service packet. The egress port of the layer 3 service packet is an aggregation port. According to preconfigured load sharing algorithm, the TOR device distributes the layer 3 service packet to a physical port included in the aggregation port for transmission.
In the ARP forwarding table, the forwarding entries used for transmitting service packets may be preconfigured by a user or obtained by the TOR device via learning. In some examples, the TOR device broadcasts a second ARP request packet, and the second ARP request packet carries the address of the DC server and the tag of the service VLAN. The TOR device receives a second ARP response packet from the DC server. In the ARP forwarding table, an aggregation port including a physical port receiving the second ARP response packet is recorded as the egress port corresponding to the address of the DC server and the service VLAN.
In some examples, the physical port bound with the management VLAN may be used for transmit management packets, and the physical port bound with the service VLAN may be used for transmit service packets. The physical port may bound with both the management VLAN and the service VLAN.
If all of or parts of the physical ports in the aggregation port are bound with the service VLAN, the aggregation port may be regarded as being bound with the service VLAN. After the aggregation port is found according to the destination address of the service packet and the tag of the service VLAN, one or more physical ports may be selected from the physical ports bounding with the service VLAN in the aggregation port according to load sharing algorithm and may be used for transmitting service packets.
In some examples, the TOR device synchronizes the ARP forwarding table to other TOR devices in the same IRF system.
In some examples, the TOR device is a TOR switch.
Figure 2 is a schematic flowchart illustrating a packet transmission method  according to some examples of the present disclosure. As shown in Figure 2, the method includes the following block.
At block 200, a management VLAN is configured to manage DC servers in advance. Generally, a tag of the management VLAN is VLAN 401.
AT block 201, for any one of the DC servers, one physical port of the DC server is bound with the management VLAN.
In various examples of the present disclosure, the physical port bound with the management VLAN on the DC server is called a first physical port.
The first physical port may be also bound with a service VLAN, so as to transmit service packets.
At block 202, following configurations are performed for any one TOR switch connected with the DC server in advance. In an ARP forwarding table, an egress port in a forwarding entry corresponding to the management VLAN is configured as each physical port which is on the TOR switch and is connected with a first physical port of each DC server connected with the TOR switch.
At block 203, when the TOR switch generates a forwarding entry in which a VLAN is the management VLAN and a destination address is an address of a DC server connected with the TOR switch, according to the configurations at 202, an egress port in the forwarding entry is configured as a physical port which is on the TOR switch and is connected with a first physical port of the DC server.
At block 204, the TOR switch receives a layer 3 management packet from a network management device, finds a forwarding entry according to the tag of the management VLAN and a destination address of the layer 3 management packet, and sends the layer 3 management packet to a DC server according to an egress port in the found forwarding entry.
According to the above examples, the management VLAN for managing DC servers is configured. When the TOR device learns the forwarding entry of the managing VLAN in the ARP forwarding table, the egress port in the forwarding entry is configured  as the physical port on the TOR device which is connected with the physical port bound with the managing WLAN on the DC server.
Because one physical port may support multiple VLANs, the physical port on the DC server may be bound with the service VLAN after bounded with the management VLAN. Accordingly, both management packets and service packets may be transmitted via the physical port. Therefore, it is unnecessary for the DC server to set a physical port for transmitting management packets aside, thereby utilizing physical port resources of the DC server effectively.
In addition, layer 3 management packets may be successfully transmitted in an service network. Accordingly, it is unnecessary to establish a dedicated management network separate from the service network, thereby saving network establishment costs.
An application example is provided.
Figure 3 is a schematic diagram illustrating the structure of a DC network according to some examples of the present disclosure. As shown in Figure 3, a IRF system includes a TOR switch 1 and a TOR switch 2, and a DC server 1 and a DC server 2 are connected with the IRF system.
The physical port P11 of the DC server 1 is connected with the physical port G1/0/1 of the TOR switch 1.
The physical port P12 of the DC server 1 is connected with the physical port G2/0/1 of the TOR switch 2.
The physical port P21 of the DC server 2 is connected with the physical port G1/0/2 of the TOR switch 1.
The physical port P22 of the DC server 2 is connected with the physical port G2/0/2 of the TOR switch 2.
In the IRF system, the physical port G1/0/1 of the TOR switch 1 and the physical port G2/0/1 of the TOR switch 2 are bound as an aggregation port G1 according to Link Aggregation Control Protocol (LACP) , and the physical port G1/0/2 of the TOR  switch 1 and the physical port G2/0/2 of the TOR switch 2 are bound as an aggregation port G2 according to the LACP.
The following configurations are performed in advance.
The physical port P11 of the DC server 1 is bound with a management VLAN 401, and the physical port P21 of the DC server 2 is bound with the management VLAN 401.
On the TOR switch 1, the physical port G1/0/1 connected with the physical port P11 is bound with the management VLAN 401, and the physical port G1/0/2 connected with the physical port P21 is bound with the management VLAN 401.
Configurations are performed for the TOR switch 1 and the TOR switch 2: in an ARP forwarding table, an egress port in a forwarding entry corresponding to the management VLAN 401 may be configured as the physical port G1/0/1 or the physical port G1/0/2.
The following procedure is performed when the TOR switch learns the ARP forwarding table.
The TOR switch 1 receives an ARP response packet sent by the DC server 1 via the physical port G1/0/1 and learns a forwarding entry. The TOR switch 1 discovers that a VLAN tag in the ARP response packet is VLAN 401, and configures an egress port of the forwarding entry as the ingress physical port G1/0/1 (rather than the ingress aggregation port G1) according to the above configurations.
The TOR switch 1 receives an ARP response packet sent by the DC server 2 via the physical port G1/0/2 and learns a forwarding entry. The TOR switch 1 discovers that a VLAN tag in the ARP response packet is VLAN 401, and configures an egress port of the forwarding entry as the ingress physical port G1/0/2 (rather than the ingress aggregation port G1) according to the above configurations in B.
The TOR switch 1 receives an ARP response packet sent by the DC server 1 via the physical port G1/0/1 and learns a forwarding entry. The TOR switch 1 discovers that a VLAN tag in the ARP response packet is a service VLAN, and configures an egress  port of the forwarding entry as the aggregation port G1 corresponding to the ingress physical port G1/0/1.
The TOR switch 1 receives an ARP response packet sent by the DC server 2 via the physical port G1/0/2 and learns a forwarding entry. The TOR switch 1 discovers that a VLAN tag in the ARP response packet is the service VLAN, and configures an egress port of the forwarding entry as the aggregation port G2 corresponding to the ingress physical port G1/0/2.
Similarly with the processing performed by the TOR switch 1, when the TOR switch 2 learns a forwarding entry of the service VLAN, an egress port is configured as the aggregation port G1 or G2.
According to characteristics of the IRF system, once each device in the IRF system, such as the TOR switches 1 and 2 in this example, learns a new forwarding entry, the device may synchronize the new forwarding entry to other devices in the IRF system.
The procedure of forwarding the layer 3 management packet by the TOR switch includes the following processing.
The TOR switch 1 receives a layer 3 management packet sent from a network management device to the DC server 1. The VLAN tag in the packet is the VLAN 401, and the destination IP address of the packet is the address of the DC server 1. The TOR switch 1 locally searches out a forwarding entry corresponding to the packet, and sends the packet according to the egress port in the forwarding entry, i. e. the physical port G1/0/1. The packet may arrive at the physical port P11 of the DC server 1.
The TOR switch 1 receives a layer 3 management packet sent from the network management device to the DC server 2. The VLAN tag in the packet is the VLAN 401, and the destination IP address of the packet is the address of the DC server 2. The TOR switch 1 locally searches out a forwarding entry corresponding to the packet, and sends the packet according to the egress port in the forwarding entry, i. e. the physical port G1/0/2. The packet may arrive at the physical port P21 of the DC server 2.
Because the TOR switch 1 has synchronized the learned forwarding entry of the management VLAN 401 to the TOR switch 2, if the TOR switch 2 receives a layer 3  management packet sent from the network management device to the DC server 1 or the DC server 2, the TOR switch 2 may find an forwarding entry corresponding to the received packet in an ARP forwarding table, and determine the egress port (G1/0/1 or G1/0/2) of the forwarding entry is located on the TOR switch 1. The TOR switch 2 sends the packet and information of the egress port to the TOR switch 1. After receiving the packet and information of the egress port, the TOR switch 1 directly sends the packet according to the information of the egress port.
The procedure of forwarding the layer 3 service packet by the TOR switch includes the following processing.
The TOR switch 1 receives a layer 3 service packet sent from a core network, searches the ARP forwarding table stored locally according to the VLAN tag and the destination address in the service packet, and finds a forwarding entry corresponding to the packet. The TOR switch 1 determines that the egress port in the forwarding entry is the aggregation port, and according to load sharing algorithm, distributes the packet to a physical port included in the aggregation port to send the packet.
In some examples, if the egress port in the forwarding entry is the aggregation port G1, a calculation process is performed by the TOR switch according to a predefined hash algorithm, e.g. a hash calculation may be performed for five tuple information of the received layer 3 service packet, and maps a calculation result to a physical port included in the aggregation port, e.g. G1/0/1 or G2/0/1. The TOR switch 1 then sends the packet via the mapped physical port. If the calculation result is mapped to the G2/0/1, the TOR switch 1 sends the service packet to the TOR switch 2, and the TOR switch 2 sends the service packet via the port G2/0/1.
The procedure of forwarding the layer 3 service packet by the TOR switch 2 is similar with that performed by the TOR switch 1.
According to the above examples, the layer 3 management packets may be forwarded via a fixed physical port in the IRF system, and the layer 3 service packets may be forwarded via the physical ports in the IRF system according to the load balance algorithm.
Figure 4 is a schematic diagram illustrating a TOR device according to some examples of the present disclosure. As shown in Figure 4, the TOR device includes a non-transitory storage medium 410 and a processor 420. The non-transitory storage medium 410 may store machine readable instructions that can be executed by the processor 420. The processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to perform a process of:
receiving a layer 3 management packet whose destination address is an address of a DC server from a network management center, the layer 3 management packet carrying a tag of a management VLAN for indicating the layer 3 management packet to be transmitted in the management VLAN；
searching an ARP forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtaining an egress port of the layer 3 management packet； the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port being bound with a service VLAN； and
transmitting the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
In some examples, the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
broadcasting a first ARP request packet； the first ARP request packet carrying the address of the DC server and the tag of the management VLAN；
receiving a first ARP response packet sent by the DC server；
configuring a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet being a physical port included in the aggregation port.
In some examples, the TOR device is located in a IRF system, and the  processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
receiving a layer 3 service packet from a core network, and the layer 3 service packet carrying the address of the DC server and a tag of the service VLAN；
searching the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtaining an egress port of the layer 3 service packet； the egress port of the layer 3 service packet being the aggregation port；
transmitting the service packet via a physical port included in the aggregation port according to preconfigured load sharing algorithm.
In some examples, the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of:
broadcasting a second ARP request packet； the second ARP request packet carrying the address of the DC server and the tag of the service VLAN；
receiving a second ARP response packet sent by the DC server；
configuring an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
In some examples, the processor 420 may read the machine readable instructions stored in the non-transitory storage 410 to further perform a process of: synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
A non-transitory storage medium is provided according to some examples of the present disclosure. The non-transitory storage medium may store machine readable instructions, and a processor may read the machine readable instructions stored in the non-transitory storage medium to perform a process of:
receiving a layer 3 management packet whose destination address is an address of a DC server from a network management center； the layer 3 management packet carrying a tag of a management VLAN for indicating the layer 3 management  packet to be transmitted in the management VLAN；
searching an ARP forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtaining an egress port of the layer 3 management packet； the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port being bound with a service VLAN； and
transmitting the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
In some examples, the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
broadcasting a first ARP request packet； the first ARP request packet carrying the address of the DC server and the tag of the management VLAN；
receiving a first ARP response packet sent by the DC server；
configuring a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet being a physical port included in the aggregation port.
In some examples, the TOR device is located in a IRF system, and the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
receiving a layer 3 service packet from a core network, and the layer 3 service packet carrying the address of the DC server and a tag of the service VLAN；
searching the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtaining an egress port of the layer 3 service packet； the egress port of the layer 3 service packet being the aggregation port； and
transmitting the service packet via a physical port included in the aggregation port according to preconfigured load sharing algorithm.
In some examples, the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of:
broadcasting a second ARP request packet； the second ARP request packet carrying the address of the DC server and the tag of the service VLAN；
receiving a second ARP response packet sent by the DC server；
configuring an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
In some examples, the processor may read the machine readable instructions stored in the non-transitory storage to further perform a process of: synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
The non-transitory storage medium for storing the machine readable instructions may be any electric, magnetic or optical storage medium or other physical storage medium. The machine readable storage medium may include or store information, e.g. executable instructions and data etc. For example, the non-transitory storage medium may be a Radom Access Memory (RAM) , a Flash card, a storage driver (e.g. a disk driver) , a solid-state disk, a storage disk of any type (e.g. an optical disk, a DVD) , or a similar storage medium, or any combination of the above.
Figure 5 is a schematic diagram illustrating a hardware structure of a TOR device according to some examples of the present disclosure. As shown in Figure 5, the TOR device includes a receiving unit 510, a searching unit 520 and a transmitting unit 530.
The receiving unit 510 is to receive a layer 3 management packet whose destination address is an address of a DC server from a network management center. The layer 3 management packet carries a tag of a management VLAN for indicating that the layer 3 management packet to be transmitted in the management VLAN.
The searching unit 520 is to search an ARP forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtain an egress port of the layer 3 management packet. The egress port is a physical port in an aggregation port, and the physical port is bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port is bound with a service VLAN.
The transmitting unit 530 is to transmit the layer 3 management packet to the DC server via the egress port of the layer management packet.
In some examples, the transmitting unit 530 is further to broadcast a first ARP request packet； the first ARP request packet carries the address of the DC server and the tag of the management VLAN.
The receiving unit 510 is further to receive a first ARP response packet sent by the DC server.
As shown in Figure 6, the TOR device further includes a configuring unit 540. The configuring unit 540 is to configure a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet is a physical port included in the aggregation port.
In some examples, the TOR device is located in a IRF system.
The receiving unit 510 is further to receive a layer 3 service packet from a core network, and the layer 3 service packet carries the address of the DC server and a tag of the service VLAN.
The searching unit 520 is further to search the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtain an egress port of the layer 3 service packet. The egress port of the layer 3 service packet is the aggregation port.
The transmitting unit 530 is further to transmit the service packet via a physical port included in the aggregation port according to preconfigured load sharing  algorithm.
In some examples, the transmitting unit 530 is further to broadcast a second ARP request packet； the second ARP request packet carries the address of the DC server and the tag of the management VLAN.
The receiving unit 510 is further to receive a second ARP response packet sent by the DC server.
The configuration unit 540 is further to configure an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
In some examples, the transmitting unit 530 is further to synchronize the ARP forwarding table to each of other TOR devices in the IRF system.
Although described specifically throughout the entirety of the instant disclosure, representative examples of the present disclosure have utility over a wide range of applications, and the above discussion is not intended and should not be construed to be limiting, but is offered as an illustrative discussion of aspects of the disclosure.
What has been described and illustrated herein is an example along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Many variations are possible within the spirit and scope of the subject matter, which is intended to be defined by the following claims --and their equivalents --in which all terms are meant in their broadest reasonable sense unless otherwise indicated.

Claims (15)

  1. A packet transmission method, comprising:
    receiving, by a top-of-rack (TOR) device, a layer 3 management packet whose destination address is an address of a Data Center (DC) server from a network management center； the layer 3 management packet carrying a tag of a management Virtual Local Area Network (VLAN) for indicating the layer 3 management packet to be transmitted in the management VLAN；
    searching an Address Resolution Protocol (ARP) forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtaining an egress port of the layer 3 management packet； the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port being bound with a service VLAN； and
    transmitting the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
  2. The method of claim 1, further comprising:
    before searching the ARP forwarding table,
    broadcasting a first ARP request packet； the first ARP request packet carrying the address of the DC server and the tag of the management VLAN；
    receiving a first ARP response packet sent by the DC server；
    configuring a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet being a physical port included in the aggregation port.
  3. The method of claim 1, wherein the TOR device is located in an Intelligent Resilient Framework (IRF) system, and the method further comprises:
    receiving a layer 3 service packet from a core network, the layer 3 service packet carrying the address of the DC server and a tag of the service VLAN；
    searching the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtaining an egress port of the layer 3 service packet；  the egress port of the layer 3 service packet being the aggregation port；
    transmitting the service packet via a physical port included in the aggregation port according to a preconfigured load sharing algorithm.
  4. The method of claim 3, further comprising:
    before searching the ARP forwarding table,
    broadcasting a second ARP request packet； the second ARP request packet carrying the address of the DC server and the tag of the service VLAN；
    receiving a second ARP response packet sent by the DC server；
    configuring an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  5. The method of claim 3, further comprising:
    synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
  6. A top-of-rack (TOR) device, comprising a non-transitory storage medium and a processor； wherein
    the non-transitory storage medium storing machine readable instructions executable by the processor； and
    the processor is to read the machine readable instructions stored in the non-transitory storage medium to perform a process of:
    receiving a layer 3 management packet whose destination address is an address of a Data Center (DC) server from a network management center； the layer 3 management packet carrying a tag of a management Virtual Local Area Network (VLAN) for indicating the layer 3 management packet to be transmitted in the management VLAN；
    searching an Address Resolution Protocol (ARP) forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtaining an egress port of the layer 3 management packet； the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port being bound with a service VLAN； and
    transmitting the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
  7. The TOR device of claim 6, wherein the processor is to read the machine readable instructions stored in the non-transitory storage medium to further perform a process of:
    broadcasting a first ARP request packet； the first ARP request packet carrying an address of the DC server and the tag of the management VLAN；
    receiving a first ARP response packet sent by the DC server；
    configuring a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet being a physical port included in the aggregation port.
  8. The TOR device of claim 6, wherein the TOR device is located in an Intelligent Resilient Framework (IRF) system, and the processor is to read the machine readable instructions stored in the non-transitory storage medium to further perform a process of:
    receiving a layer 3 service packet from a core network, and the layer 3 service packet carrying the address of the DC server and a tag of the service VLAN；
    searching the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtaining an egress port of the layer 3 service packet； the egress port of the layer 3 service packet being the aggregation port；
    transmitting the service packet via a physical port included in the aggregation port according to preconfigured load sharing algorithm.
  9. The TOR device of claim 8, wherein the processor is to read the machine readable instructions stored in the non-transitory storage medium to further perform a process of:
    broadcasting a second ARP request packet； the second ARP request packet carrying the address of the DC server and the tag of the service VLAN；
    receiving a second ARP response packet sent by the DC server；
    configuring an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  10. The TOR device of claim 8, wherein the processor is to read the machine readable instructions stored in the non-transitory storage medium to further perform a process of:
    synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
  11. A non-transitory storage medium, located in a top-of-rack (TOR) device, storing machine readable instructions executable by a processor, wherein the machine readable instructions are executed by the processor to perform a process of:
    receiving a layer 3 management packet whose destination address is an address of a Data Center (DC) server from a network management center； the layer 3 management packet carrying a tag of a management Virtual Local Area Network (VLAN) for indicating the layer 3 management packet to be transmitted in the management VLAN；
    searching an Address Resolution Protocol (ARP) forwarding table according to the tag of the management VLAN and the destination address of the layer 3 management packet, and obtaining an egress port of the layer 3 management packet； the egress port being a physical port in an aggregation port, and the physical port being bound with the management VLAN and connected with a physical port bound with the management VLAN on the DC server； the physical port being bound with a service VLAN；
    transmitting the layer 3 management packet to the DC server via the egress port of the layer 3 management packet.
  12. The non-transitory storage medium of claim 11, wherein the machine readable instructions are executed by the processor to further perform a process of:
    broadcasting a first ARP request packet； the first ARP request packet carrying the address of the DC server and the tag of the management VLAN；
    receiving a first ARP response packet sent by the DC server；
    configuring a port receiving the first ARP response packet as an egress corresponding to the address of the DC server and the management VLAN in the ARP forwarding table； the port receiving the first ARP response packet being a physical port included in the aggregation port.
  13. The non-transitory storage medium of claim 11, wherein the TOR device is  located in an Intelligent Resilient Framework (IRF) system, and the machine readable instructions are executed by the processor to further perform a process of:
    receiving a layer 3 service packet from a core network, and the layer 3 service packet carrying the address of the DC server and a tag of the service VLAN；
    searching the ARP forwarding table according to the tag of the service VLAN and the address of the DC server, and obtaining an egress port of the layer 3 service packet； the egress port of the layer 3 service packet being the aggregation port；
    transmitting the service packet via a physical port included in the aggregation port according to preconfigured load sharing algorithm.
  14. The non-transitory storage medium of claim 13, wherein the machine readable instructions are executed by the processor to further perform a process of:
    broadcasting a second ARP request packet； the second ARP request packet carrying the address of the DC server and the tag of the service VLAN；
    receiving a second ARP response packet sent by the DC server；
    configuring an aggregation port including a physical port receiving the second ARP response packet as an egress corresponding to the address of the DC server and the service VLAN in the ARP forwarding table.
  15. The non-transitory storage medium of claim 13, wherein the machine readable instructions are executed by the processor to further perform a process of:
    synchronizing the ARP forwarding table to each of other TOR devices in the IRF system.
PCT/CN2016/073608 2015-02-06 2016-02-05 Packet transmission Ceased WO2016124155A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510064873.3 2015-02-06
CN201510064873.3A CN105991321B (en) 2015-02-06 2015-02-06 Manage the method and device of data center server

Publications (1)

Publication Number Publication Date
WO2016124155A1 true WO2016124155A1 (en) 2016-08-11

Family

ID=56563480

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/073608 Ceased WO2016124155A1 (en) 2015-02-06 2016-02-05 Packet transmission

Country Status (2)

Country Link
CN (1) CN105991321B (en)
WO (1) WO2016124155A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7264767B2 (en) * 2019-08-22 2023-04-25 アラクサラネットワークス株式会社 Packet relay device and packet relay system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101764752A (en) * 2009-12-25 2010-06-30 杭州华三通信技术有限公司 Method and system for managing remote concentrated image
US20120287785A1 (en) * 2011-05-14 2012-11-15 International Business Machines Corporation Data traffic handling in a distributed fabric protocol (dfp) switching network architecture
CN103166874A (en) * 2013-03-25 2013-06-19 杭州华三通信技术有限公司 A message forwarding method and device
CN103227757A (en) * 2012-08-31 2013-07-31 杭州华三通信技术有限公司 Message forwarding method and equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006267B (en) * 2009-09-03 2014-08-13 中兴通讯股份有限公司 Access authentication method and device based on simple network protocol
CN102143138A (en) * 2010-09-15 2011-08-03 华为技术有限公司 Method and device for configuring virtual local area network (VLAN) in live migration process of virtual machine
US8793351B2 (en) * 2011-05-24 2014-07-29 Facebook, Inc. Automated configuration of new racks and other computing assets in a data center
CN103856358B (en) * 2014-03-28 2017-02-15 潍坊学院 Ethernet port VLAN (virtual local area network) configuration system and method of EOC (Ethernet over coax) equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101764752A (en) * 2009-12-25 2010-06-30 杭州华三通信技术有限公司 Method and system for managing remote concentrated image
US20120287785A1 (en) * 2011-05-14 2012-11-15 International Business Machines Corporation Data traffic handling in a distributed fabric protocol (dfp) switching network architecture
CN103227757A (en) * 2012-08-31 2013-07-31 杭州华三通信技术有限公司 Message forwarding method and equipment
CN103166874A (en) * 2013-03-25 2013-06-19 杭州华三通信技术有限公司 A message forwarding method and device

Also Published As

Publication number Publication date
CN105991321A (en) 2016-10-05
CN105991321B (en) 2019-05-17

Similar Documents

Publication Publication Date Title
US9374294B1 (en) On-demand learning in overlay networks
EP2874359B1 (en) Extended ethernet fabric switches
US9515930B2 (en) Intelligent handling of virtual machine mobility in large data center environments
US10432428B2 (en) Automatic resolution of virtual network instance to VLAN mapping conflicts in dual-homed deployments in a dynamic fabric automation network architecture
US10572509B2 (en) Scalable spine nodes with partial replication of routing information in a network environment
US9825859B2 (en) Item aggregation in shortest path bridging mac-in-mac mode (SPBM) network
US20190235909A1 (en) Forwarding policy configuration
US10333845B2 (en) Forwarding data packets
US9641417B2 (en) Proactive detection of host status in a communications network
US20180006969A1 (en) Technique for gleaning mac and ip address bindings
CN107800625B (en) Message forwarding method and device
EP3292659B1 (en) Multicast data packet forwarding
US9509602B2 (en) Limiting MAC address learning on access network switches
US20180351878A1 (en) Multicast data packet forwarding
WO2016124156A1 (en) Packet transmission
WO2018171722A1 (en) Mac address synchronization
CN102394825B (en) Method and device for processing message
EP3493482A1 (en) Device detection
US9762489B2 (en) Local packet switching at a satellite device
WO2013159667A1 (en) Virtual router redundancy protocol load balancing mode (vrrpe)
US9985926B2 (en) Address acquiring method and network virtualization edge device
EP2908476A1 (en) Method and apparatus for sending multi-link transparent interconnected data frame
CN105991321B (en) Manage the method and device of data center server

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

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

Country of ref document: EP

Kind code of ref document: A1