Method and device realizing PVLAN through OpenFlow protocol

An openflow protocol and purpose technology, applied in the communication field, can solve the problems of large main VLAN MAC table, decreased forwarding rate, lack of application layer connection flow monitoring, etc.

CN104022960AActive Publication Date: 2014-09-03NEW H3C TECH CO LTD
5 Cites 16 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Publication Date
2014-09-03

Smart Images

  • Figure 1
    Figure 1
  • Figure 2
    Figure 2
  • Figure 3
    Figure 3
Patent Text Reader

Abstract

The invention discloses a method realizing a PVLAN through an OpenFlow protocol; the method uses the OpenFlow protocol to realize the PVLAN; whether a message is forwarded or not can be controlled in a OpenFlow controller; a MAC chart in a sub VLAN needs not to be copied to a main VLAN. The invention also provides a device based on the same invention conception; a chart item of the main VLAN cannot use a large memory when the PVLAN is realized, and a message forwarding rate cannot be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

technical field

[0001] The present application relates to the field of communication technologies, and in particular to a method and device for realizing PVLAN based on the OpenFlow protocol. Background technique

[0002] With the increasing business of data centers and the continuous improvement of user requirements, the scale and functions of data centers are becoming more and more complex, and the management difficulty is also becoming more and more difficult. In this context, integrating data centers, reducing data center management costs, and fully exploiting existing resource capabilities to meet higher business needs have become important tasks for enterprise data centers. Virtualizing data center resources has become an important trend in data center integration.

[0003] Virtualization technology abstracts physical resources and provided services, so that resource users and system managers do not care about the details of the physical characteristics of objects and...

Examples

example 1

[0040] Example 1: Uplink unicast packets of isolated VLAN

[0041] When the message is a unicast message in which the sub-VLAN to which the ingress port belongs is an isolated VLAN, if the VDSs to which the ingress port and the destination port respectively belong are different, construct a first flow table; otherwise, discard the unicast message Wherein, the packet header field of the first flow table includes the ingress port and the destination MAC, and the action field includes setting the VLAN as the main VLAN and forwarding through the uplink port.

[0042] In this example, when the OpenFlow controller receives a unicast packet sent by the server and the source port of the sub-VLAN belongs to the isolated VLAN, the port in the isolated VLAN can only communicate with ports other than the VDS where it is located. , cannot communicate with any port in the isolated VLAN or Community VLAN in the same VDS, so after determining that the destination port of the unicast message d...

example 2

[0048] Example 2: Uplink unicast packets of Community VLAN

[0049] When the message is a unicast message in which the sub-VLAN to which the ingress port belongs is a Community VLAN, if the respective sub-VLANs to which the ingress port and the destination port belong are the same Community VLAN in the same main VLAN, or the ingress port Different from the VDS to which the destination ports belong respectively, construct a second flow table; otherwise, discard the unicast message; wherein, the packet header field of the second flow table includes the ingress port and destination MAC, and the action field includes Set the VLAN as the main VLAN and forward it through the uplink port.

[0050] Here, the ingress port and destination MAC address in the delivered flow table are the contents contained in the Header Fields, and the egress port and the set primary VLAN are the contents contained in the Action. Wherein, the outgoing port is the port number of the VEPA switch connected ...

example 3

[0053] Example 3: Downlink unicast packets of isolated VLAN / Community VLAN

[0054] When the message is a unicast message whose ingress port is an uplink port, construct a third flow table, the header field of the third flow table includes the ingress port and destination MAC, and the action domain includes forwarding through the destination port .

[0055] In the flow table delivered in this example, the Header Fields can include the inbound port number, primary VLAN ID, source MAC address, and destination MAC address, and the Action includes the forwarded outbound port number. Wherein, the inbound port number is the uplink port receiving the unicast message, that is, the port number connecting the VEPA switch to the edge switch, and the outbound port number is the port corresponding to the destination MAC address of the unicast message.

[0056] Since the uplink unicast packets of isolated VLAN and community VLAN are filtered according to their characteristics at the sendin...