Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, referring to the accompanying drawing embodiment that develops simultaneously, scheme of the present invention is described in further detail.
Propose three layers of method of realizing group broadcasting in a kind of software vertical stack system in the embodiment of the present invention, the member device in this pile system comprises three layers of equipment and three layers of equipment that the multicast list specification is little that the multicast list specification is large.Arbitrary described member device is when issuing three layers of multicast list to hardware, determine the incoming interface of the Multicast Routing in these three layers of multicast lists and the distribution situation of outgoing interface, realize issuing as required on the member device of three layers of multicast list in the software stack system, perhaps use equivalent Layer 2 Multicast list item to issue, can reduce the resource occupation of three layers of multicast list of each member device, greatly promote the Multicast Routing specification of vertical stack entire system, avoid in the vertical stack system three layers of little equipment of multicast list specification to become the bottleneck of Multicast Routing performance.
In the specific embodiment of the invention, the incoming interface of Multicast Routing refers to that this Multicast Routing advances the interface of this pile system, and the outgoing interface of Multicast Routing refers to that this Multicast Routing goes out the interface of this pile system, does not comprise the stacking opening of pile system inside.
How to generate for three layers of multicast list, and pass through the spanning tree of calculating between each member device in pile system, how the multicast data flow that each Multicast Routing is relevant is forwarded, can be with the existing mode realized, the present invention also is indifferent to.The present invention just determines whether as the case may be to issue when three layers of multicast list are issued to hardware, or uses alternative list item to issue, and reaches and reduces by three layers of effect that multicast list issues.
Embodiment mono-
Referring to Fig. 2, Fig. 2 is three layers of method of realizing group broadcasting schematic flow sheet in the embodiment of the present invention one.Concrete steps are:
Step 201, in the vertical stack system, arbitrary member device is when issuing three layers of multicast list to hardware, if determine, the incoming interface of the Multicast Routing in these three layers of multicast lists is on other member devices, two above outgoing interfaces are on this member device, and described two above outgoing interfaces belong to same Virtual Local Area Network,, in described VLAN, these three layers of multicast lists are mapped as to the Layer 2 Multicast list item, and this Layer 2 Multicast list item is issued to hardware.
In this vertical stack system, according to multicast routing protocol, generate three layers of multicast list, the content that three floor multicast list comprise is source Internet Protocol (SIP) address, purpose Internet Protocol (DIP) address, incoming interface number and outgoing interface number.In the vertical stack system, each member device can be known the port case on other member devices, and incoming interface that therefore can this Multicast Routing according to the incoming interface in three floor multicast list number and outgoing interface number and outgoing interface are on which member device.
Issue Layer 2 Multicast list item by the mapping of three layers of multicast list in this step to hardware in this VLAN, and do not issue these three layers of multicast lists to hardware, with the Layer 2 Multicast list item, substitute issuing of three layers of multicast list.Wherein the Layer 2 Multicast list item can be (VLAN ID, (purpose Media Access Controlled) dmac address) or (VLAN ID, the DIP address), perhaps (VLAN ID, sip address, the DIP address), and outgoing interface number, specifically depend on the realization of different vendor, wherein dmac address directly gets by the mapping of DIP address in accordance with current multicast protocol standard.As: use rear 28 latter 23 of being mapped as MAC Address of IP address, first 25 of MAC Address immobilize.If outgoing interface exists a plurality of, outgoing interface number is an outgoing interface collection, comprises a plurality of outgoing interfaces number.
Referring to Fig. 3, Fig. 3 is vertical stack schematic diagram in the embodiment of the present invention one.In Fig. 3, member device 1, member device 2, member device 3 and member device 4 are stacked as a vertical stack system, member device 1 and member device 2 are three layers of large equipment of multicast forwarding list item specification, and member device 3 and member device 4 are three layers of little equipment of multicast forwarding list item specification.When specific implementation, can be only to three layers of multicast forwarding list item three layers of multicast list on little equipment when hardware issues, processed, also can when issuing to hardware, all by the processing mode of the embodiment of the present invention, be processed three layers of multicast list on all member devices.
Suppose that each member device in Fig. 3 is for Multicast Routing 1(S, G) the corresponding forward-path of multicast data flow in this pile system is as shown by the arrows in Figure 3.Interface 1 by member device 1 enters this vertical stack system, arrive member device 2 by interface 2, member device 2 goes out this vertical stack system by interface 3, arrive respectively member device 3 and member device 4 by interface 4 and interface 5, this multicast data flow goes out this vertical stack system by the outgoing interface 6 and 7 of member device 3, and the outgoing interface 8 by member device 4 goes out this vertical stack system.
Suppose that outgoing interface 6 and outgoing interface 7 on member device 3 belong to same VLAN, for member device 3, the incoming interface of this Multicast Routing 1 is on other member devices, be on member's equipment 1, wherein exist two outgoing interfaces on this member device, and these two outgoing interfaces belong to same VLAN, on member device 3, three layers of multicast list are mapped as to the Layer 2 Multicast list item, use this Layer 2 Multicast list item to replace three layers of multicast list of Multicast Routing 1 correspondence, be issued to hardware.
Three layers of little equipment of multicast forwarding list item specification, although the specification of three layers of multicast list is limited, but the specification of Layer 2 Multicast list item is but very large, therefore, use the Layer 2 Multicast list item to replace three layers of multicast list and be issued to hardware, can not affect issuing of Layer 2 Multicast list item, save again the resource of three layers of multicast list on hardware.
If it is different with the VLAN under outgoing interface 7 with outgoing interface 6 that member device 2 receives and need be transmitted to the affiliated VLAN of the multicast data flow of member device 3, member device 2, when to member device 3, forwarding this multicast data flow, replaces with by VLAN the VLAN that same outgoing interface 6 is identical with outgoing interface 7.
Step 201 when this member device receives the multicast data flow of this Multicast Routing of coupling, forwards this multicast data flow according to the Layer 2 Multicast list item that is issued to hardware in this VLAN.
The content that the Layer 2 Multicast list item of supposing here to realize comprises is VLAN ID, dmac address and outgoing interface number, in the VLAN under this multicast data flow, search the Layer 2 Multicast list item, according to the dmac address of this multicast data flow, the outgoing interface of corresponding outgoing interface number 6 and 7 correspondences forwards this multicast data flow.
Embodiment bis-
Referring to Fig. 4, Fig. 4 is three layers of method of realizing group broadcasting schematic flow sheet in the embodiment of the present invention two.Concrete steps are:
Step 401, in the vertical stack system, arbitrary member device is when issuing three layers of multicast list to hardware, if determine, the incoming interface of the Multicast Routing in these three layers of multicast lists is on other member devices, two above outgoing interfaces are on this member device, and described two above outgoing interfaces do not belong to same VLAN, and the port that described two above outgoing interfaces are access style is the ACCESS mouth, described two above outgoing interfaces are joined in the VLAN of a system reservation, in the VLAN retained in this system, these three layers of multicast lists are mapped as to the Layer 2 Multicast list item, and this Layer 2 Multicast list item is issued to hardware.
Still take Fig. 3 as example, suppose that in Fig. 3, the VLAN of the outgoing interface on member device 36 and outgoing interface 7 is not identical, and outgoing interface 6 and outgoing interface 7 be the ACCESS mouth, in the VLAN that adds a system to retain outgoing interface 6 and outgoing interface 7, be the VLAN that the user can not use, as 4095.
For member device 3, the incoming interface of this Multicast Routing 1 is on other member devices, be on member's equipment 1, wherein exist two outgoing interfaces on this member device, and these two outgoing interfaces (outgoing interface 6 and outgoing interface 7) belong to different VLAN, on member device 3, use the Layer 2 Multicast list item to replace the corresponding three layers of multicast list of this Multicast Routing 1, be issued to hardware.Wherein, the VLAN ID in the Layer 2 Multicast list item is 4095, and outgoing interface number is 6 and 7.
Here for the outgoing interface that belongs to different VLAN, also can use the Layer 2 Multicast list item to replace three layers of multicast list, mainly the characteristics by means of the ACCESS mouth, after arriving the recipient by the ACCESS mouth, can not be with VLAN TAG, therefore, the Layer 2 Multicast list item issued is forwarded, and can play and issue three layers of multicast list and forward identical effect.
Step 402, when this member device receives the multicast data flow of this Multicast Routing of coupling, in the VLAN retained in system, forward this multicast data flow according to the Layer 2 Multicast list item that issues hardware.
Embodiment tri-
In pile system, arbitrary member device is when issuing three layers of multicast list to hardware, if the incoming interface of the Multicast Routing in definite these three layers of multicast lists and outgoing interface be not on this member device, and do not need this member device to forward the multicast data flow of this Multicast Routing of coupling, to hardware, do not issue the multicast list that this Multicast Routing is relevant.
Here to hardware, do not issue the multicast list that this Multicast Routing is relevant, do not issue three layers of multicast list and do not issue the Layer 2 Multicast list item yet, because this multicast can not be forwarded on this member device, therefore, do not need to issue any list item.
Still take Fig. 3 as example, suppose Multicast Routing 2(S, G) corresponding multicast data flow is forwarded to member device 2 by member device 1, then be forwarded to member device 3 from member device 2, transfer this pile system from member device 3.On member device 4, do not have outgoing interface and the incoming interface of this Multicast Routing, the multicast data flow that this Multicast Routing is corresponding also forwards without member device 4, on member device 4, the multicast list of these Multicast Routing 2 correspondences is not issued to hardware.
Embodiment tetra-
Referring to Fig. 5, Fig. 5 is three layers of method of realizing group broadcasting schematic flow sheet in the embodiment of the present invention four.Concrete steps are:
Step 501, in the vertical stack system, arbitrary member device is when issuing three layers of multicast list to hardware, if the incoming interface of the Multicast Routing in these three layers of multicast lists, on other member devices, and only has an outgoing interface on this member device; Or, the incoming interface of this Multicast Routing is on this member device, and outgoing interface is on other member devices, and this member device only has an interface can reach other member devices at described outgoing interface place, these three layers of multicast lists are mapped as to acl rule, and described acl rule is issued to hardware.
Still be described as example with Fig. 3 in embodiment mono-, multicast data flow for Multicast Routing 1 correspondence, member device 4 has an outgoing interface (interface 8), and incoming interface is not on member device 4, on member device 1, therefore, for member device 4, while issuing three layers of multicast list of Multicast Routing 1 correspondence, use corresponding acl rule to substitute three layers of multicast list and be issued to hardware.
For Multicast Routing 1, member device 1 has an incoming interface (interface 1), and outgoing interface is at this member device, on other member devices, as, the interface 3 of member device 2, the interface 6 of member device 3 and interface 7, the interface 8 of member device 4.And member device 1 has and only has an interface (interface 2) to arrive on other member devices at outgoing interface place.At this moment, on member device 1, three layers of multicast list of Multicast Routing 1 correspondence are mapped as to corresponding acl rule, and use the alternative three layers of multicast list of this acl rule to be issued to hardware.
How three layers of multicast list are mapped as to acl rule, concrete processing is as follows:
As (s, g) be (1.1.1.1,225.1.1.1) multicast data flow, enter from the Port1 of VLAN10, need to be forwarded to the Port2 of VLAN20, the rule field that can on port1, issue ACL is SIP=1.1.1.1, GIP=225.1.1.1, the ACL list item of VLAN=10, the action of this list item is: revising VLAN ID is 20, message redirecting is arrived to Port2 simultaneously.
Step 502, when this member device receives the multicast data flow of this Multicast Routing of coupling, mated and forwarded this multicast data flow according to the acl rule that is issued to hardware.
Above-mentioned four embodiment can combination in any be implemented on a member device, all can reduce by three layers of multicast list and be issued to hardware.
Below with specific embodiment, be described in detail in the vertical stack system how to realize three layers of multicast.
Referring to Fig. 6, Fig. 6 is applied to above-mentioned vertical stack system schematic in the specific embodiment of the invention.In Fig. 6, member device 1, member device 2, member are that equipment 3 and member device 4 are stacked as in a vertical stack system, wherein, member device 1 and member device 2 are three layers of equipment that the multicast list specification is large, and member device 3 and member device 4 are three layers of little equipment of multicast performance specification.When specific implementation, can be only to three layers of multicast list specification three layers of multicast list on little equipment when hardware issues, processed, also can when issuing to hardware, all by the processing mode of the embodiment of the present invention, be processed three layers of multicast list on all member devices.
Three layers of multicast data flow 3(1.1.1.1 that enter from member device 1 in Fig. 6,225.1.1.1), its downstream recipient is on member device 1, as shown in the dotted arrow in Fig. 6, three layers of multicast data flow 4(2.2.2.2 simultaneously that enter from member device 1,225.2.2.2), its outgoing interface is on member device 3 and member device 4, and on member device 3, two interface P31, P32 are in VLAN10; P41 in two interfaces on member device 4 belongs to VLAN20, and P42 belongs to VLAN30, both the ACCESS style interface.Although there is no outgoing interface and incoming interface on member device 2, three layers of multicast data flow 2 need to be transmitted to member device 3 and member device 4 by member device 2.
For the outgoing interface of the route (1.1.1.1,225.1.1.1) of three layers of multicast data flow 3 correspondence and incoming interface, all on member device 1, the Local Multicast Routing that this route is member device 1, need issue three layers of multicast list of correspondence in this locality.
Due to the incoming interface of this Multicast Routing and outgoing interface all on member device 1, and there do not is outgoing interface on other member devices, therefore, can not be forwarded on member device 2, member device 3 and member device 4, therefore, member device 2, member device 3 and member device 4 do not need to issue this Multicast Routing.
Route (2.2.2.2 for three layers of multicast data flow 4 correspondence, 225.2.2.2), due to member device 1 incoming interface that is this Multicast Routing, and this member device only has an interface that these three layers of multicast data flows are forwarded to other member devices (member device 2), therefore, on member device 1, these three layers of multicast lists are mapped as to acl rule, and use acl rule to substitute issuing of three layers of multicast list.Because member device 1 is three layers of equipment that the multicast list specification is large, also can still three layers of multicast list of correspondence directly be issued to hardware.
Although do not have the incoming interface of these three layers of multicast data flows 4 there is no outgoing interface on member device 2 yet, but three layers of multicast data flow 4 need to forward through member device 2, and be transmitted to other member devices (member device 3 and member device 4) by two interfaces, therefore, on member device 2, three layers of multicast list of correspondence are issued to hardware.
The incoming interface that there is no these three layers of multicast data flows 4 on member device 3, but two outgoing interfaces are arranged, and these two outgoing interfaces are in same VLAN10, member device 2 is when forwarding this three layers of multicast data flows to member device 3, if this multicast data flow does not belong to VLAN10, replace with, or disguise as VLAN10 is forwarded on member device 3.Member device 3, in VLAN10, is mapped as the Layer 2 Multicast list item by these three layers of multicast lists, and uses the alternative three layers of multicast list of Layer 2 Multicast list item to be issued to hardware.In concrete Layer 2 Multicast list item, VLAN ID is 10, and dmac address is 0100-5e02-0202, and outgoing interface number is P31, P32.
The incoming interface that there is no these three layers of multicast data flows 4 on member device 4, but two outgoing interfaces are arranged, two outgoing interfaces are the ACCESS mouth, and these two outgoing interfaces belong in different VLAN, add system to retain in VLAN interface P41 and P42, as VLAN4095, during specific implementation, can be also VLAN0.Member device 4, in VLAN4095, is mapped as the Layer 2 Multicast list item by these three layers of multicast lists, and uses the alternative three layers of multicast list of Layer 2 Multicast list item to be issued to hardware.In concrete Layer 2 Multicast list item, VLAN ID is 4095, and dmac address is 0100-5e02-0202, and outgoing interface number is P41, P42.
VLAN4095, VLAN0 are the obsolete VLAN of user, the system that is generally retains, the message that the list item by above-mentioned VLAN4095 is forwards two interfaces from VLAN4095, owing to being the Access style interface, message is gone out and can be with VLAN-Tag, therefore downstream recipient's angle is seen, and the message of receiving from VLAN20 and VLAN30 is without any difference.
Therefore, can issue two three layers of multicast lists on member device 1, also can issue three layers of multicast list and an acl rule.Member device 2 has issued three layers of multicast list, and does not issue three layers of multicast list on member's equipment 3 and member device 4, has all issued a Layer 2 Multicast list item.Each member device has greatly reduced issuing of three layers of multicast list like this, especially three layers of little member device of multicast list specification have reduced the resource occupation of three layers of multicast list in hardware, guarantee that whole vertical stack system can support three layers of larger Multicast Routing specification.
Remove the Multicast Routing outside the route of above-mentioned special characteristic, realize with existing, need on each member device, all be issued to hardware.And no matter whether three layers of multicast list are issued to hardware, all can buffer memory in software.
When above-mentioned route-type changes in the agreement running, need to re-issue or temporarily delete the route hardware table item by new feature.
When member device receives multicast data flow, on hardware, mated., therefore, always there be list item or the acl rule that can mate in owing to arbitrary Multicast Routing only can being issued on this member device in acl rule, three layers of multicast list and Layer 2 Multicast list item one.
Inventive concept based on same in the specific embodiment of the invention, a kind of equipment is also proposed, be applicable as the arbitrary member device in software vertical stack system, the member device in this pile system comprises three layers of equipment and three layers of equipment that the multicast list specification is little that the multicast list specification is large.Referring to Fig. 7, Fig. 7 is applied to the structural representation of the equipment of above-mentioned technology in the specific embodiment of the invention.This equipment comprises: determining unit 701, receiving element 702 and processing unit 703.
Determining unit 701, when issuing three layers of multicast list to hardware, determine incoming interface and the outgoing interface of these three layers of multicast lists for this equipment.
Receiving element 702, for receiving the multicast data flow of this Multicast Routing of coupling.
Processing unit 703, if determine for determining unit 701, the incoming interface of Multicast Routing of these three layers of multicast lists is at other member devices, two above outgoing interfaces are on this equipment, and described two above outgoing interfaces belong to same VLAN, in described VLAN, these three layers of multicast lists are mapped as to the Layer 2 Multicast list item, and this Layer 2 Multicast list item is issued to hardware; Wherein, described incoming interface is the interface that described Multicast Routing advances this pile system, and described outgoing interface is the interface that described Multicast Routing goes out this pile system; When receiving element 702 receives the multicast data flow of this Multicast Routing of coupling, in this VLAN, according to the Layer 2 Multicast list item that is issued to hardware, forward this multicast data flow.
Preferably,
Processing unit 703, determine that the incoming interface of the Multicast Routing in these three layers of multicast lists is on other member devices if be further used for determining unit 701, two above outgoing interfaces are on this equipment, and described two above outgoing interfaces do not belong to same VLAN, and described two above outgoing interfaces are the ACCESS mouth, described two above outgoing interfaces are joined in the VLAN of a system reservation, in the VLAN retained in this system, these three layers of multicast lists are mapped as to the Layer 2 Multicast list item, and this Layer 2 Multicast list item is issued to hardware; When receiving element 702 receives the multicast data flow of this Multicast Routing of coupling, in the VLAN retained in system, according to the Layer 2 Multicast list item that issues hardware, forward this multicast data flow.
Preferably,
Processing unit 703, determine that the incoming interface of the Multicast Routing in these three layers of multicast lists and outgoing interface be not on this equipment if be further used for determining unit 701, and do not need this device forwards to mate the multicast data flow of this Multicast Routing, to hardware, do not issue the multicast list that this Multicast Routing is relevant.
Preferably,
Processing unit 703, the incoming interface that determining unit 701 determines the Multicast Routing in these three layers of multicast lists if be further used for, on other member devices, and only has an outgoing interface on this equipment; Or the incoming interface of this Multicast Routing is on this equipment, outgoing interface is on other member devices, and this equipment only has an interface can reach other member devices at described outgoing interface place; These three layers of multicast lists are mapped as to acl rule, and described acl rule is issued to hardware; When receiving element 702 receives the multicast data flow of this Multicast Routing of coupling, according to the acl rule that is issued to hardware, this multicast data flow is mated and forwarded.
The unit of above-described embodiment can be integrated in one, and also can separate deployment; A unit can be merged into, also a plurality of subelements can be further split into.
In sum, in the specific embodiment of the invention, member device is when issuing three layers of multicast list to hardware, determine the incoming interface of the Multicast Routing in these three layers of multicast lists and the distribution situation of outgoing interface, realize issuing as required on the equipment of three layers of multicast list in the software stack system, perhaps use equivalent Layer 2 Multicast list item to issue, can reduce the resource occupation of three layers of multicast list of each member device, greatly promote the Multicast Routing specification of vertical stack entire system, avoid in the vertical stack system three layers of little equipment of multicast list specification to become the bottleneck of Multicast Routing performance.
The above, be only preferred embodiment of the present invention, is not intended to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.