CN102377639B

CN102377639B - Multicast pruning method, protocol independent multicast (PIM) router and group management snooping exchanger

Info

Publication number: CN102377639B
Application number: CN201010249670.9A
Authority: CN
Inventors: 周迪; 史扬; 刘宇
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2010-08-10
Filing date: 2010-08-10
Publication date: 2015-03-11
Anticipated expiration: 2030-08-10
Also published as: CN102377639A

Abstract

The invention discloses a multicast pruning method, a protocol independent multicast (PIM) router and a group management snooping exchanger. A multicast source is connected to a first-hop PIM router through the group management snooping exchanger. The method comprises the following steps: if the first-hop PIM router receives a multicast flow sent by the multicast source, and finds that requirements for receiving the multicast flow do not exist locally, or if the first-hop PIM router receives a PIM pruning message for one multicast flow sent by a downstream PIM router, deletes an interface for receiving the message from an outlet interface list of the multicast flow, and then finds that requirements for receiving the multicast flow have not existed jet locally, sending out a group management pruning message from an inlet interface of the multicast flow; and when the group management snooping exchanger receives the group management pruning message, using the receiving port of the message as a pruning port, and no longer forwarding the multicast flow to the pruning port. The invention prunes the useless multicast flow between the multicast source and the first-hop PIM router.

Description

Multicast pruning method and protocol independent multicast router, fabric anomaly pry switch

Technical field

The present invention relates to technical field of multicast, be specifically related to multicast pruning method, protocol independent multicast router (PIM, Protocol Independent Multicast) and fabric anomaly pry switch.

Background technology

For ease of understanding, first provide following conceptual illustration:

Multicast: a kind of with clean culture with broadcast communication mode arranged side by side, multi-cast system is made up of multicast source, recipient and multicast group.Source host only sends a data, and the destination address in this number certificate is multicast group address; All recipients in multicast group can receive same data copy, and only have the main frame in multicast group can receive these data.

IGMP (IGMP, Internet Group Management Protocol): transmission control protocol/Internet Protocol (TCP/IP, Transmission Control Protocol/InternetProtocol) be responsible for the agreement of IP multicast member management in protocol suite, be used for IP main frame and and the multicast router of its direct neighbor between set up, safeguard multicast group membership.

IGMP spies upon (IGSP, Internet Group Management Protocol Snooping): operate in the multicast tied mechanism on two-layer equipment, for management and control multicast group.Run the two-layer equipment of IGMP pry by analyzing the IGMP message received, for port and medium education (MAC, Media Access Control) multicast address set up mapping relations, and according to this mapping relations multicast data forwarding.

PIM: represent can utilize static routing or arbitrarily unicast routing protocol as: RIP, OSPF, IS-IS, BGP etc. the unicast routing table that generates provide route for IP multicast; Realize the multicast data dissemination safeguarded between three-layer equipment.

IP multicasting technology efficiently solves the problem that single-point sends multipoint reception, achieves efficient data transmission point-to-multipoint in IP network, can save the network bandwidth in a large number, reduce offered load.Utilize the multicast feature of network, some new value-added services, the information service comprising the Internet such as live, Web TV, long-distance education, tele-medicine, network radio station, real-time video meeting online obtains and develops fast.

PIM agreement is the multicast routing protocol of current main flow.IGMP pry is the Layer 2 Multicast control protocol of main flow.

In the multicast application of program request character, industry solves the flow control of PIM router multicast source not yet well.Fig. 1 is a multicast networking exemplary plot, and as shown in Figure 1, multicast source and client are accessed by Layer 2 switch, and multiple Layer 2 switch converges on a PIM router.As: multicast source 1,2 is spied upon switch 6,7 respectively by IGMP and is accessed, and IGMP spies upon switch 1,2,3 and converges on PIM router two.

When the multicast data flow that multicast source sends arrives the first jumping PIM router by switch, if this PIM router is Designated Router (DR, Designated Router), then to point (RP) transmission source registration message, if RP finds that (the S corresponding with this multicast data flow is not set up in this locality, G) list item, namely without this multicast data flow of client program request, then returns to source to DR and suppresses message; After this, when there being this multicast data flow of client program request, client sends IGMP to leaf router and adds message, leaf router sends PIM to RP and adds message, RP receives this PIM when adding message, and send PIM to DR and add message, after this multicast data flow arrives multicast receivers via RP.

The shortcoming of prior art is as follows:

For arbitrary multicast data flow that multicast source sends, no matter whether have this multicast data flow of client program request, this multicast data flow all first will be sent to the first jumping PIM router through switch, like this, just adds the buffer memory consumption of switch.The outbound port buffer memory of switch is for guarantee Business Stream, particularly video etc. band bursty nature Business Stream orderly, prevent packet loss, reduce shake there is important effect, therefore, do not need the data flow forwarded should forbid that it forwards, thus reduce the consumption to switch outbound port buffer memory.Existing protocol cannot useless multicast traffic stream link layer beta pruning is from multicast source to PIM router.

Summary of the invention

The invention provides multicast pruning method and PIM router, fabric anomaly pry switch, with beta pruning from multicast source to PIM router useless multicast data flow.

Technical scheme of the present invention is achieved in that

A kind of multicast pruning method, multicast source is connected to the first jumping Protocol Independent Multicast PIM router by fabric anomaly pry switch, and the method comprises:

Described first jumping PIM router receives the multicast data flow that described multicast source is sent, and finds the local demand not receiving this multicast data flow, then outwards sends fabric anomaly prune message from the incoming interface of this multicast data flow; Or,

Described first jumping PIM router receives the PIM prune message for a multicast data flow that downstream PIM router is sent, the receiving interface of this message is deleted from the outgoing interface list of this multicast data flow, if find the local demand not received this multicast data flow, then outwards send fabric anomaly prune message from the incoming interface of this multicast data flow;

After described fabric anomaly pry switch receives described fabric anomaly prune message, using the receiving port of this message as beta pruning port, and add this beta pruning port to the fabric anomaly corresponding with described multicast data flow and spy upon in list item, no longer to multicast data flow described in described beta pruning port repeat.

The receiving port of this message comprises further by described fabric anomaly pry switch while beta pruning port:

For this beta pruning port arranges the beta pruning time,

And, after this beta pruning time arrives, start to allow to multicast data flow described in described beta pruning port repeat.

Described first jumps PIM router finds that the local demand not receiving this multicast data flow comprises:

First jumps PIM router finds that the multicast routing table item corresponding with described multicast data flow is not set up in this locality, though or establish the multicast routing table item corresponding with described multicast data flow but the outgoing interface list of this list item for empty, then determine the local demand not receiving this multicast data flow.

After described fabric anomaly pry switch receives described fabric anomaly prune message, the receiving port of this message is comprised as taking a step forward of beta pruning port:

Fabric anomaly pry switch finds that this locality is not set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, then set up the fabric anomaly corresponding with described multicast data flow and spy upon list item;

And described being added to by this beta pruning port after the fabric anomaly corresponding with described multicast data flow is spied upon in list item comprises further:

Fabric anomaly pry switch judges whether self exists router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, the outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

Fabric anomaly pry switch finds that this locality has been set up the fabric anomaly corresponding with described multicast data flow and spied upon list item;

And this beta pruning port is added to the fabric anomaly corresponding with described multicast data flow by described fabric anomaly pry switch spy upon in list item and comprises further afterwards:

Fabric anomaly pry switch judges whether described fabric anomaly pry list item comprises member port or router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

Described fabric anomaly pry switch comprises further after this outbound port outwards sends fabric anomaly prune message:

Described multicast source receives described fabric anomaly prune message, suspends and sends described multicast data flow.

Fabric anomaly pry switch outwards sends fabric anomaly beta pruning query messages from the receiving port of fabric anomaly prune message, if do not receive the fabric anomaly grafting message of any response in maximum response time, then perform described using the action of the receiving port of this message as beta pruning port.

Described fabric anomaly pry switch comprises further after the receiving port of fabric anomaly prune message outwards sends fabric anomaly beta pruning query messages:

Other fabric anomaly pry switch receives described fabric anomaly beta pruning query messages, clean culture MAC address entries is searched according to the source MAC of message, if to find and the outbound port of clean culture MAC address entries is consistent with the receiving port of fabric anomaly beta pruning query messages, then judge whether this locality has been set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, if set up and this fabric anomaly pry list item comprise member port or router port, or, if not set up but this switch has router port, then in maximum response time, respond fabric anomaly grafting message.

PIM router receives described fabric anomaly beta pruning query messages, judge whether this locality has the multicast routing table item corresponding with described multicast data flow, if have and the outgoing interface list of this multicast routing table item for empty, then in maximum response time, respond fabric anomaly grafting message.

This beta pruning port is added to the fabric anomaly corresponding with described multicast data flow by described fabric anomaly pry switch spy upon in list item and comprises further afterwards:

The fabric anomaly for described multicast data flow that the PIM for described multicast data flow adds message or under self, extension client is sent that described first jumping PIM router reception downstream PIM router is sent adds message, sends fabric anomaly grafting message to described multicast source direction;

Described fabric anomaly pry switch receives described fabric anomaly grafting message, and described beta pruning port is reverted to router port, starts to allow to forward described multicast data flow to this router port.

After the PIM for described multicast data flow that described first jumping PIM router reception downstream PIM router is sent adds message, comprise to described taking a step forward of multicast source direction transmission fabric anomaly grafting message:

First jumps PIM router judges whether this locality has set up the multicast routing table item corresponding with described multicast data flow, if and the outgoing interface list of this multicast routing table item is empty, the receiving interface then described PIM being added message adds in the outgoing interface list of this multicast routing table item, and performs the described action sending fabric anomaly grafting message to multicast source direction.

Described method comprises further:

The fabric anomaly that fabric anomaly pry switch receives for described multicast data flow adds message, search the fabric anomaly corresponding with this multicast data flow in this locality and spy upon list item, the receiving port this fabric anomaly being added message adds in described fabric anomaly pry list item as member port, and adds message to all-router port and this fabric anomaly of beta pruning port repeat;

Fabric anomaly pry switch judges that whether this fabric anomaly adds message from data source port, if from and also there is other data source port in described fabric anomaly pry list item, then send fabric anomaly grafting message to other data source port; If not from, then send fabric anomaly grafting message to all data source ports in described fabric anomaly pry list item.

After described fabric anomaly pry switch receives described fabric anomaly grafting message, described beta pruning port reverted to taking a step forward of router port comprise:

Described fabric anomaly pry switch judges that local fabric anomaly corresponding to described multicast data flow is spied upon list item and whether only comprised beta pruning port, if so, then forwards described fabric anomaly grafting message, and performs the described action described beta pruning port being reverted to router port; Otherwise, directly perform the described action described beta pruning port being reverted to router port.

Described fabric anomaly pry switch comprises after forwarding described fabric anomaly grafting message further:

Described multicast source receives described fabric anomaly grafting message, recovers to send described multicast data flow.

Described fabric anomaly pry switch supports that IGMP IGMP or multicast listener find agreement MLD agreement.

A kind of PIM router, this PIM router is directly connected to multicast source by fabric anomaly pry switch, and this PIM router comprises:

First module, receive the multicast data flow that described multicast source is sent, find the local demand not receiving this multicast data flow, or, receive the PIM prune message for a multicast data flow that downstream PIM router is sent, the receiving interface of this message is deleted from the outgoing interface list of this multicast data flow, if find the local demand not received this multicast data flow, then sends beta pruning instruction to the second module;

Second module, receives described beta pruning instruction, outwards sends fabric anomaly prune message from the incoming interface of described multicast data flow.

Described PIM router comprises further:

3rd module, receives fabric anomaly beta pruning query messages, and whether judge locally has the multicast routing table item corresponding with described multicast data flow, if to have and the outgoing interface list of this multicast routing table item is not sky, then in maximum response time, responds fabric anomaly grafting message.

Described PIM router comprises further:

Four module, the fabric anomaly for described multicast data flow that the PIM for described multicast data flow adds message or under self, extension client is sent that reception downstream PIM router is sent adds message, sends fabric anomaly grafting message to described multicast source direction.

Described four module is further used for,

After receiving the PIM for described multicast data flow that downstream PIM router sends and adding message, judge whether this locality has set up the multicast routing table item corresponding with described multicast data flow, if and the outgoing interface list of this multicast routing table item is empty, the receiving interface then described PIM being added message adds in the outgoing interface list of this multicast routing table item, and performs the described action sending fabric anomaly grafting message to multicast source direction.

A kind of fabric anomaly pry switch, jump between PIM router at multicast source and first, this switch comprises:

First module, receives fabric anomaly prune message, using the receiving port of this message as beta pruning port, and adds this beta pruning port to the fabric anomaly corresponding with described multicast data flow and spies upon in list item, no longer to multicast data flow described in described beta pruning port repeat.

Described first module is further used for, for described beta pruning port arranges the beta pruning time, and, after this beta pruning time arrives, start to allow to multicast data flow described in described beta pruning port repeat.

Described first module is further used for, and after receiving described fabric anomaly prune message, if find, this locality is not set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, then set up the fabric anomaly corresponding with described multicast data flow and spy upon list item; And, this beta pruning port is added to after the fabric anomaly corresponding with described multicast data flow spy upon in list item, judge whether this switch exists router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

Described first module is further used for, after receiving described fabric anomaly prune message, local set up the fabric anomaly corresponding with described multicast data flow if find and spy upon list item, then directly execution is described adds the fabric anomaly corresponding with described multicast data flow to and spies upon action in list item by this beta pruning port; And, judge whether described fabric anomaly pry list item comprises member port or router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

Described first module is further used for, after receiving described fabric anomaly prune message, fabric anomaly beta pruning query messages is outwards sent from the receiving port of fabric anomaly prune message, if do not receive the fabric anomaly grafting message of any response in maximum response time, then perform described using the action of the receiving port of this message as beta pruning port.

Described switch comprises further:

Second module, receive the fabric anomaly beta pruning query messages that other fabric anomaly pry switch is sent, clean culture MAC address entries is searched according to the source MAC of message, if to find and the outbound port of clean culture MAC address entries is consistent with the receiving port of fabric anomaly beta pruning query messages, then judge whether this locality has been set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, if set up and this fabric anomaly pry list item comprise member port or router port, or, if not set up but this switch has router port, then in maximum response time, respond fabric anomaly grafting message.

Described switch comprises further:

3rd module, receives fabric anomaly grafting message, described beta pruning port is reverted to router port, starts to allow to forward described multicast data flow to this router port.

Described switch comprises further:

Four module, the fabric anomaly received for described multicast data flow adds message, search the fabric anomaly corresponding with this multicast data flow in this locality and spy upon list item, the receiving port this fabric anomaly being added message adds in described fabric anomaly pry list item as member port, and adds message to all-router port and this fabric anomaly of beta pruning port repeat; Judge that whether this fabric anomaly adds message from data source port, if from and also there is other data source port in described fabric anomaly pry list item, then send fabric anomaly grafting message to other data source port; If not from, then send fabric anomaly grafting message to all data source ports in described fabric anomaly pry list item.

Described 3rd module is further used for, after receiving described fabric anomaly grafting message, judge that local fabric anomaly corresponding to described multicast data flow is spied upon list item and whether only comprised beta pruning port, if, then forward described fabric anomaly grafting message, and perform the described action described beta pruning port being reverted to router port; Otherwise, directly perform the described action described beta pruning port being reverted to router port.

A kind of multicast source, comprising:

First module, receives the fabric anomaly prune message for a multicast data flow, suspends and sends described multicast data flow.

Described multicast source comprises further: the second module, receives the fabric anomaly grafting message for described multicast data flow, recovers to send described multicast data flow.

Compared with prior art, in the present invention, when first jump PIM router receive the multicast data flow that multicast source sends time, or, receive the PIM prune message for a multicast data flow that downstream PIM router is sent, if find the local demand not received this multicast data flow, then outwards send fabric anomaly prune message from the incoming interface of this multicast data flow; After fabric anomaly pry switch receives described fabric anomaly prune message, using the receiving port of this message as beta pruning port, no longer to multicast data flow described in described beta pruning port repeat.The present invention without the need to making any restriction to networking, just can beta pruning from multicast source to PIM router useless multicast data flow, save the outbound port buffer memory of bandwidth sum switch.

Accompanying drawing explanation

Fig. 1 is a multicast networking exemplary plot;

The multicast pruning method flow chart that Fig. 2 provides for the embodiment of the present invention;

The first jumping PIM router that Fig. 3 provides for the embodiment of the present invention receives the process chart after multicast data flow;

The first jumping PIM router Rtr that Fig. 4 provides for the embodiment of the present invention receives the process chart after from the PIM prune message of downstream PIM router;

The IGMP pry switch that Fig. 5 provides for the embodiment of the present invention receives the process chart after IGMP prune message;

The IGMP pry switch that Fig. 6 provides for the embodiment of the present invention receives the process chart after IGMP beta pruning query messages;

The first jumping PIM router that Fig. 7 provides for the embodiment of the present invention receives the process chart after IGMP beta pruning query messages;

The PIM that the first jumping PIM router that Fig. 8 provides for the embodiment of the present invention receives from downstream PIM router adds the process chart after message;

The IGMP that Fig. 9 provides for the embodiment of the present invention spies upon switch and receives IGMP and add the process chart after message;

What Figure 10 provided for the embodiment of the present invention first jumps PIM router Rtr and receives IGMP and add the process chart after message;

The IGMP pry switch that Figure 11 provides for the embodiment of the present invention receives the process chart after IGMP grafting message;

Figure 12 receives the process chart after IGMP beta pruning and grafting message for the multicast source devices that the embodiment of the present invention provides;

The composition schematic diagram of the PIM router that Figure 13 provides for the embodiment of the present invention.

Embodiment

Below in conjunction with drawings and the specific embodiments, the present invention is further described in more detail.

In the present invention, suppose that the igmpinternet version that the whole network uses is identical, namely, or unified use IGMPv2, or unified use IGMPv3, or the unified multicast listener that uses finds protocol version 1 (MLDv1, Multicast Listener Discovery Protocol Version1) or unified use MLDv2.

If the igmpinternet that the embodiment of the present invention adopts is IGMPv2 or MLDv1, then different multicast data flows is distinguished with multicast group information; If the igmpinternet that the embodiment of the present invention adopts is IGMPv3 or MLDv2, then different multicast data flows is distinguished with information about multicast source+multicast group information.

Three message groups management prune message, fabric anomaly grafting message and fabric anomaly beta pruning query messages have been increased newly in the present invention.Wherein, according to IGMP, then these three message are respectively: IGMP prune message, IGMP grafting message, IGMP beta pruning query messages; According to MLD, then these three message are respectively: MLD prune message, MLD grafting message, MLD beta pruning query messages.Below these three message are described in detail:

One, fabric anomaly prune message.

The value of the type field of this message is the untapped value of existing igmpinternet, such as: according to IGMP, then and can value 0x27.The source IP address of message, source medium education (MAC, MediaAccess Control) address be respectively send this message the IP address of outgoing interface, MAC Address, object IP address, target MAC (Media Access Control) address are respectively unicast ip address, the unicast mac address of multicast source.Wherein, according to IGMPv2 or MLDv1, source IP address, source MAC also can extend this as full 0.

Two, fabric anomaly grafting message.

The value of the type field of this message is the untapped value of existing igmpinternet, such as: according to IGMP, then and can value 0x28.If this message source is from PIM router, then the source IP address of message, source MAC are respectively IP address, the MAC Address of the outgoing interface sending this message; If this message source spies upon switch from fabric anomaly, then the source IP address of message, source MAC can extend this as full 0.When message is not the response message for fabric anomaly beta pruning query messages, the object IP address of message, target MAC (Media Access Control) address are respectively unicast ip address, the unicast mac address of multicast source; When message is the response time for fabric anomaly beta pruning query messages, the object IP address of message, target MAC (Media Access Control) address are source IP address, the source MAC of fabric anomaly beta pruning query messages respectively.

Three, fabric anomaly beta pruning query messages.

The value of the type field of this message is the untapped value of existing igmpinternet, such as: according to IGMP, then and can value 0x21.According to IGMPv2 or MLDv1, then the source IP address of message, source MAC can extend this as full 0; According to IGMPv3 or MLDv2, then the source IP address of message, source MAC are object IP address, the target MAC (Media Access Control) address of IGMP prune message.The object IP address of message is multicast group address.The value of the maximum response time field in message is defaulted as 1 second.

In the present invention, fabric anomaly pry switch has increased two port roles newly: beta pruning port and data source port, be described in detail to this port role below:

One, beta pruning port.

When fabric anomaly pry switch receives the IGMP prune message for a multicast data flow that the first jumping PIM router sends, the receiving port of this message just becomes beta pruning port.After this, this multicast data flow must not from this beta pruning port repeat.

Can find out, beta pruning port is actually by the router port of beta pruning.

Beta pruning port, router port and member port are the control port roles that three classes are different, for the forwarding of control data stream.Three generic port separated maintenances.

Two, data source port.

Data source port is used to indicate the port in the data source direction of fabric anomaly pry list item.For IGMPv2 or MLDv1, a fabric anomaly pry list item may have multiple data source port; For IGMPv3 or MLDv2, then a fabric anomaly pry list item only has a data source port.

Data source port is the port that multicast data flow corresponding to fabric anomaly pry list item is come in, and it is not control port, and is not used in the forwarding of control data stream, is only used to indicate the port that multicast data flow is come in.The switch sending fabric anomaly prune message is only had just to have data source port.

For the present invention, according to IGMP, then fabric anomaly pry switch is that IGMP spies upon switch; According to MLD, then fabric anomaly pry switch is that MLD spies upon switch.

Adopt IGMP for igmpinternet below, the present invention is described in detail, when igmpinternet adopts MLD agreement, " IGMP " in all for the present invention embodiments replaced with " MLD ".

The multicast pruning method flow chart that Fig. 2 provides for the embodiment of the present invention, as shown in Figure 2, its concrete steps are as follows:

Step 201:IGMP spies upon switch and receives from the PIM hello message of PIM router or IGMP General Query message, and the receiving port of this message is set to router port.

Step 202: the multicast data flow that multicast source sends arrives first via router port and jumps PIM router, first jumps PIM router finds that the multicast routing table item corresponding with this multicast data flow is not set up in this locality, though or set up the multicast routing table item corresponding with this multicast data flow but the outgoing interface list of this list item for empty, then determine the local demand not receiving this multicast data flow, outwards send the IGMP prune message for this multicast data flow from the incoming interface of this multicast data flow; Or, first jumping PIM router receives the PIM prune message for a multicast data flow that downstream PIM router is sent, search the multicast routing table item corresponding with this multicast data flow, the receiving interface of this message is deleted from this list item, if find, the outgoing interface list of this list item is for empty, then outwards send the IGMP prune message for this multicast data flow from the incoming interface of this multicast data flow.

Here, the transmission of IGMP prune message is speed limit, namely can not frequently send identical IGMP prune message because receiving identical multicast data flow always, send interval and default to 1 minute once, until this multicast data flow is had the demand receiving this multicast data flow by beta pruning or this locality.

Step 203: the first IGMP jumped between PIM router and multicast source spies upon switch and receives this IGMP prune message, if find the current demand without receiving this multicast data flow, then the receiving port of this IGMP prune message is set to beta pruning port, after this no longer to this multicast data flow of beta pruning port repeat.

As can be seen from Figure 2, in following two kinds of situations, beta pruning is needed to jump multicast data flow PIM router from multicast source to first:

One, the local demand at all not receiving this multicast data flow;

Two, have the demand receiving this multicast data flow before this locality, but Current demands stops receiving.

Fig. 3, Fig. 4 sets forth the detailed process of the first jumping PIM router for above-mentioned two situations:

The first jumping PIM router that Fig. 3 provides for the embodiment of the present invention receives the process chart after multicast data flow, and as shown in Figure 3, its concrete steps are as follows:

Step 301: first jumps PIM router Rtr periodically outwards sends PIM hello message from each PIM interface of self.

Step 302:IGMP spies upon switch and receives PIM hello message, the receiving port of this message is set to router port (router port), and gives other Layer 2 switch by PIM hello message from each port repeat of self.

IGMP pry is the layer 2-switched fundamental characteristics of all support multicasts.IGMP spies upon switch and the port receiving IGMP general polling message and PIM message is considered as router port, and is considered as member port by receiving the port that IGMP joins message.IGMP spies upon exchange opportunity and all multicast data flows is all sent to router port, and only the multicast data flow of corresponding multicast group can be sent to member port.

After other Layer 2 switch receives PIM hello message, also can carry out the process of step 302.

Step 303: multicast source sends a multicast data flow, this multicast data flow arrives first via each router port and jumps PIM router Rtr.

Step 304:Rtr judges whether this locality has set up (S, G) list item corresponding with this multicast data flow, if so, performs step 305; Otherwise, perform step 308.

Step 305:Rtr judges whether the outgoing interface list of being somebody's turn to do (S, G) list item is empty, if so, performs step 306; Otherwise, perform step 307.

Step 306:Rtr upgrades the ageing time of being somebody's turn to do (S, G) list item, and outwards sends IGMP prune message from the incoming interface of this multicast data flow, and this flow process terminates.

Because Rtr outwards sends IGMP prune message from the incoming interface of multicast data flow, then the IGMP that this message can arrive between Rtr and multicast source spies upon switch.IGMP pry switch receives the handling process embodiment as shown in Figure 5 after this IGMP prune message.

Step 307:Rtr is according to the outgoing interface information in this outgoing interface list, and outwards forward this multicast data flow, this flow process terminates.

Step 308:Rtr sets up (S, G) list item corresponding with this multicast data flow, and arranges list item ageing time, outwards sends IGMP prune message from the incoming interface of this multicast data flow.

Here, (S, G) list item ageing time is generally 3 minutes.

If PIM sparse (SM, Sparse Mode) pattern, then in this step, after foundation (S, G) list item, Rtr also needs to send for the Login message of this multicast data flow to RP.

The first jumping PIM router Rtr that Fig. 4 provides for the embodiment of the present invention receives the process chart after from the PIM prune message of downstream PIM router, and as shown in Figure 4, its concrete steps are as follows:

Step 401: the first jumping PIM router Rtr receives the PIM prune message for a multicast data flow that downstream PIM router is sent, (the S corresponding with this multicast data flow is found in this locality, G) list item, should (S, G) list item according to existing PIM protocol processes.

When a multicast receivers no longer receives a multicast data flow, this multicast receivers can to the igmp leave message of the leaf router transmission of self for this multicast data flow, after leaf router receives this igmp leave message, send the PIM prune message for this multicast data flow to RP, RP can jump this PIM prune message of PIM router direction forwarding to first.

According to existing PIM agreement, the receiving interface of PIM prune message can be deleted by Rtr usually from the outgoing interface list of this (S, G) list item.

Step 402:Rtr judges whether the outgoing interface list of (S, G) list item is empty, if so, performs step 403; Otherwise, perform step 404.

Step 403:Rtr outwards sends IGMP prune message from the incoming interface of this multicast data flow, and this flow process terminates.

Step 404:Rtr does not make subsequent treatment.

The IGMP prune message that first jumping PIM router sends can arrive IGMP and spy upon switch, and this IGMP spies upon switch and jumps between PIM router at multicast source and first.

The IGMP pry switch that Fig. 5 provides for the embodiment of the present invention receives the process chart after IGMP prune message, and as shown in Figure 5, its concrete steps are as follows:

Step 501:IGMP spies upon the IGMP prune message of switch reception for a multicast data flow.

Step 502:IGMP spies upon switch and judges whether the receiving port of this IGMP prune message starts IGMP beta pruning query function, if so, performs step 503; Otherwise, perform step 506.

Step 503:IGMP pry switch outwards sends the IGMP beta pruning query messages for this multicast data flow from the receiving port of IGMP prune message.

Be connected to the equipment that other has this multicast data flow demand of reception after preventing the receiving port of IGMP prune message simultaneously, IGMP beta pruning query function can be opened on the port that IGMP spies upon switch, like this, after IGMP pry switch receives IGMP prune message, just can outwards send IGMP beta pruning query messages from the receiving port of this message, to be confirmed whether that miscellaneous equipment has the demand receiving this multicast data flow.

IGMP beta pruning query function is optional function.The situation that same port connects multiple switch is there is not when IGMP spies upon switch, and all switches all support the function (can not support beta pruning query function) that the IGMP pry switch mentioned in all embodiments of the present invention has, then need not open beta pruning query function, thus accelerate the beta pruning of useless multicast data flow.

What IGMP spied upon that the IGMP beta pruning query messages that sends of switch can arrive that other IGMP spies upon switch and spy upon that switch is connected with this IGMP first jumps PIM router.Other IGMP pry switch receives the handling process embodiment as shown in Figure 6 after IGMP beta pruning query messages, and the first jumping PIM router receives the handling process embodiment as shown in Figure 7 after IGMP beta pruning query messages.

Step 504:IGMP spies upon switch and judges whether the IGMP grafting message receiving response in maximum response time, if so, performs step 505; Otherwise, perform step 506.

Step 505:IGMP spies upon switch and does not deal with, and this flow process terminates.

Step 506:IGMP spies upon switch and judges whether that the IGMP set up for this multicast data flow spies upon list item, if so, performs step 507; Otherwise, perform step 514.

Step 507:IGMP spies upon switch and is added in this IGMP pry list item as beta pruning port by the receiving port of IGMP prune message.

Step 508:IGMP spies upon switch and judges that this IGMP spies upon list item and whether comprises member port or router port, if so, performs step 509; Otherwise, perform step 510.

Here router port does not comprise the receiving port of IGMP prune message.

Step 509:IGMP spies upon switch and does not deal with, and this flow process terminates.

If IGMP spies upon list item comprise member port or router port, then show there is this multicast data flow of miscellaneous equipment program request, therefore, no longer forward IGMP prune message.

Step 510:IGMP spies upon switch according to the clean culture target MAC (Media Access Control) address of IGMP prune message, in clean culture MAC address entries, find outbound port.

Step 511:IGMP spies upon switch and judges whether this outbound port has been marked as data source port, if so, performs step 512; Otherwise, perform step 513.

Step 512:IGMP spies upon switch and is forwarded from this outbound port by this IGMP prune message, and this flow process terminates.

If this IGMP prune message arrives multicast source, multicast source receives the handling process embodiment as shown in Figure 12 after IGMP prune message.

Step 513:IGMP spies upon switch and this outbound port is labeled as data source port, and forwarded from this outbound port by this IGMP prune message, this flow process terminates.

Step 514:IGMP spies upon the IGMP pry list item of switch foundation for this multicast data flow, and the receiving port of this IGMP prune message is recorded as the beta pruning port of this list item.

Step 515:IGMP spies upon switch and judges whether self exists router port, if so, performs step 516; Otherwise, perform step 517.

Here router port does not comprise the receiving port of IGMP prune message.

Step 516:IGMP spies upon switch and is added to by all router ports in the outbound port list of this IGMP pry list item, and do not forward this IGMP prune message, this flow process terminates.

Step 517:IGMP spies upon switch and searches clean culture MAC address entries according to the clean culture target MAC (Media Access Control) address of this IGMP prune message, the outbound port of this clean culture MAC address entries is recorded as the data source port that this IGMP spies upon list item, and this IGMP prune message is gone out from this data source port repeat.

In the present embodiment, the beta pruning port can spied upon in list item for IGMP arranges vital values, and the vital values of beta pruning port is 1/3 of (S, G) list item vital values of this multicast data flow on PIM router, is defaulted as 1 minute.Such PIM DR can receive this multicast data flow a every 1 minute.When the vital values one of beta pruning port arrives, then IGMP is spied upon all beta pruning ports in list item and temporarily revert to router port, to make this port can forwarding multicasting stream, if but do not receive any IGMP prune message in the Preset Time after the vital values of beta pruning port arrives, then this port is reverted to router port completely, judge this IGMP spies upon in list item whether only comprise router port simultaneously, and there is no the control port of other role as member port, if, then delete this IGMP and spy upon list item, to save list item resource.If this port to any IGMP prune message, is then reverted to beta pruning port, and resets the vital values of this beta pruning port by the Preset Time adduction after the vital values of beta pruning port arrives.

What IGMP spied upon that the IGMP beta pruning query messages that sends of switch can arrive that other IGMP spies upon switch and spy upon that switch is connected with this IGMP first jumps PIM router.

The IGMP pry switch that Fig. 6 provides for the embodiment of the present invention receives the process chart after IGMP beta pruning query messages, and as shown in Figure 6, its concrete steps are as follows:

Step 601:IGMP spies upon switch reception for the IGMP beta pruning query messages of a multicast data flow, searches the clean culture MAC address entries corresponding with the source MAC of this message in this locality.

Step 602:IGMP spies upon switch and judges whether to find, and if so, performs step 603; Otherwise, perform step 611.

Step 603:IGMP spies upon switch and judges that whether the outbound port of the clean culture MAC address entries found is consistent with the receiving port of this IGMP beta pruning query messages, if so, performs step 604; Otherwise, perform step 611.

Step 604:IGMP spies upon switch and judges that the local IGMP whether set up for this multicast data flow spies upon list item, if so, performs step 605; Otherwise, perform step 608.

Step 605:IGMP spies upon switch and judges that this IGMP spies upon list item and whether comprises member port or router port, if so, performs step 606; Otherwise, perform step 607.

Here router port does not comprise the receiving port of IGMP beta pruning query messages.

Step 606:IGMP spies upon switch in maximum response time, responds clean culture IGMP grafting message, and this flow process terminates.

Step 607:IGMP spies upon switch and does not deal with, and this flow process terminates.

Step 608:IGMP spies upon switch and judges whether self has router port, if so, performs step 609; Otherwise, perform step 610.

Step 609:IGMP spies upon switch sends response clean culture IGMP grafting message from the receiving port of IGMP beta pruning query messages, and this flow process terminates.

Step 610:IGMP spies upon switch and does not deal with, and this flow process terminates.

Step 611:IGMP spies upon switch and abandons this IGMP beta pruning query messages, and this flow process terminates.

If the receiving port of the outbound port of the clean culture MAC address entries found and IGMP beta pruning query messages is inconsistent, then illustrate that this multicast data flow does not enter IGMP from the receiving port of IGMP beta pruning query messages and spies upon switch or do not spy upon switch through this IGMP; If search the clean culture MAC address entries less than correspondence, then illustrate that not passing through this IGMP with this multicast data flow spies upon switch.Under both of these case, all need not comprehend this IGMP beta pruning query messages.

The first jumping PIM router that Fig. 7 provides for the embodiment of the present invention receives the process chart after IGMP beta pruning query messages, and as shown in Figure 7, its concrete steps are as follows:

Step 701: first jumps the IGMP beta pruning query messages of PIM router Rtr reception for a multicast data flow.

Step 702:Rtr judges whether this locality has the outgoing interface list corresponding with this multicast data flow for empty IGMP spies upon list item, if so, performs step 703; Otherwise, perform step 704.

Step 703:Rtr returns clean culture IGMP grafting message in maximum response time, and this flow process terminates.

Step 704:Rtr does not deal with.

For by the multicast data flow of beta pruning, after this when there being this multicast data flow of equipment program request, need this multicast data flow of grafting.In following three kinds of situations, grafting is needed to jump multicast data flow PIM router from multicast source to first:

One, when this multicast data flow of client program request of hanging under the PIM router of downstream, now, this client can send IGMP to downstream PIM router add message, and downstream PIM router receives after IGMP adds message, jumps PIM router send PIM and add message to first;

Two, when this multicast data flow of client program request of hanging under first jumps PIM router, now, this client can add message to the first jumping PIM router transmission IGMP;

Three, when IGMP spies upon this multicast data flow of client program request of hanging under switch, now, this client can add message to this IGMP pry switch transmission IGMP.

Below provide the correlation procedure of the grafting multicast data flow that the embodiment of the present invention provides.

The PIM that the first jumping PIM router that Fig. 8 provides for the embodiment of the present invention receives from downstream PIM router adds the process chart after message, and as shown in Figure 8, its concrete steps are as follows:

Step 801: the PIM for a multicast data flow that the first jumping PIM router Rtr reception downstream PIM router is sent adds message, finds (S, G) list item corresponding with this multicast data flow in this locality.

When hanging a client under first jumps the downstream PIM router of PIM router, as shown in Figure 1, wherein, PIM router two is the first jumping PIM router, PIM router one is the downstream PIM router of PIM router two, a client 1 is hung under PIM router one, if this client program request multicast data flow, the IGMP that then can send for this multicast data flow to this downstream PIM router adds message, downstream PIM router receives this IGMP when adding message, can jump PIM router to first, the PIM sent for this multicast data flow as the PIM router two in Fig. 1 adds message.

Step 802:Rtr judges whether the outgoing interface list of being somebody's turn to do (S, G) list item is empty, if so, performs step 803; Otherwise, perform step 804.

The receiving interface that this PIM is added message by step 803:Rtr joins this (S, in the outgoing interface list of G) list item, according to the singlecast router list item of object IP address search this locality of this message, send IGMP grafting message from the outgoing interface singlecast router list item, this flow process terminates.

Here, the object IP address of IGMP grafting message, target MAC (Media Access Control) address are IP address, the MAC Address of multicast source respectively.IGMP grafting message can spy upon switch arrival multicast source by the IGMP between Rtr and multicast source, IGMP pry switch receives the handling process embodiment as shown in Figure 11 after IGMP grafting message, and multicast source receives the handling process embodiment as shown in Figure 12 after IGMP grafting message.

For preventing IGMP grafting information drop-out to ensure to obtain multicast data flow as early as possible, Rtr can send IGMP grafting message with upper frequency, until receive this multicast data flow.

Step 804:Rtr adds message according to existing this PIM of PIM protocol processes.

The IGMP that Fig. 9 provides for the embodiment of the present invention spies upon switch and receives IGMP and add the process chart after message, and as shown in Figure 9, its concrete steps are as follows:

The IGMP that step 901:IGMP pry switch receives for a multicast data flow adds message, search the IGMP corresponding with this multicast data flow in this locality and spy upon list item, the receiving port of this message is joined as member port the IGMP found spy upon in list item, and add message to all-router port and this IGMP of beta pruning port repeat.

This IGMP adds message and may arrive other IGMP pry switch or arrive the first jumping PIM router, when other IGMP spy upon switch receive this IGMP add message time, its handling process is identical with the present embodiment, when first jump PIM router receive this IGMP add message after handling process embodiment as shown in Figure 10.

IGMP in this step adds the client of hanging under message spies upon switch from IGMP.

Step 902:IGMP spies upon switch and judges that whether IGMP adds message from data source port, if so, performs step 903; Otherwise, perform step 906.

Step 903:IGMP spies upon switch and judges that this IGMP spies upon list item and whether also there is other data source port, if so, performs step 904; Otherwise, perform step 905.

Step 904:IGMP pry switch sends the IGMP grafting message for this multicast data flow to other data source port, and this flow process terminates.

The object IP address of this IGMP grafting message, target MAC (Media Access Control) address are respectively IP address, the MAC Address of multicast source, then this message can be spied upon switch arrival multicast source through other IGMP or directly arrive multicast source, other IGMP pry switch receives the handling process embodiment as shown in Figure 11 after this IGMP grafting message, and multicast source receives the handling process embodiment as shown in Figure 12 after after IGMP grafting message.

Step 905:IGMP pry switch does not send the IGMP grafting message for this multicast data flow, and this flow process terminates.

Step 906:IGMP spies upon switch and spies upon the IGMP grafting message of all data source ports transmissions in list item for this multicast data flow to this IGMP.

Here, if IGMP spies upon list item do not have data source port, then do not need to forward IGMP grafting message.

What Figure 10 provided for the embodiment of the present invention first jumps PIM router Rtr and receives IGMP and add the process chart after message, and as shown in Figure 10, its concrete steps are as follows:

Step 1001: the IGMP that the first jumping PIM router Rtr receives for a multicast data flow adds message.

There is the following two kinds situation in the source that IGMP in this step adds message:

Source one, when hanging a client under first jumps PIM router, as shown in Figure 1, PIM router two is the first jumping PIM router, its lower extension one client 2, if this client program request multicast data flow, then this client can add message to the first jumping PIM router transmission IGMP.

Source two, when hanging a client under the first IGMP jumped between PIM router and multicast source spies upon switch, as shown in Figure 1, PIM router two is the first jumping PIM router, IGMP between PIM router two and multicast source 1,2 spies upon switch and hangs a client 3 for 1 time, if this client program request multicast data flow, then this client can add message to this IGMP pry switch transmission IGMP, and this IGMP is added message and is transmitted to the first jumping PIM router by IGMP pry exchange opportunity.

Step 1002:Rtr judges whether this locality has set up (S, G) list item corresponding with this multicast data flow, if so, performs step 1003; Otherwise, perform step 1008.

Step 1003:Rtr judges whether the outgoing interface list of being somebody's turn to do (S, G) list item is empty, if so, performs step 1004; Otherwise, perform step 1007.

Step 1004:Rtr judges that whether this IGMP adds message from the interface pointing to multicast source, if so, performs step 1005; Otherwise, perform step 1006.

IGMP adds message from the interface pointing to multicast source, namely the source that this IGMP adds message belongs to the source two in step 1001, now, adds correspondence (S to without the need to the receiving interface this IGMP being added message, in the outgoing interface list of G) list item, do not send IGMP grafting message yet.

Step 1005:Rtr does not deal with, and this flow process terminates.

The receiving interface that this IGMP is added message by step 1006:Rtr adds in the outgoing interface list of this (S, G) list item, and sends the IGMP grafting message for this multicast data flow to multicast source S direction, and this flow process terminates.

For preventing IGMP grafting information drop-out to ensure to obtain multicast data flow as early as possible, IGMP grafting message can be sent with upper frequency, until receive this multicast data flow.

Step 1007:Rtr is according to existing PIM protocol processes, and this flow process terminates.

Here, according to existing PIM agreement, the receiving interface that IGMP can be added message by Rtr adds in the outgoing interface list of (S, G) list item.

Step 1008:Rtr is according to existing PIM protocol processes.

Here, according to existing PIM agreement, Rtr can set up corresponding with multicast data flow (S, G) list item, and the receiving interface then IGMP being added message adds in the outgoing interface list of this (S, G) list item.

The IGMP pry switch that Figure 11 provides for the embodiment of the present invention receives the process chart after IGMP grafting message, and as shown in figure 11, its concrete steps are as follows:

Step 1101:IGMP spies upon the IGMP grafting message of switch reception for a multicast data flow.

Step 1102:IGMP spies upon switch and judges that the local IGMP whether set up for this multicast data flow spies upon list item, if so, performs step 1103; Otherwise, perform step 1110.

Step 1103:IGMP spies upon switch and judges whether the receiving port of this IGMP grafting message is the beta pruning port that this IGMP spies upon list item, if so, performs step 1104; Otherwise, perform step 1110.

Step 1104:IGMP spies upon switch and judges that this IGMP spies upon list item and whether only comprises beta pruning port, if so, performs step 1105; Otherwise, perform step 1106.

Do not consider data source port in this step, if that is: IGMP spies upon list item except the beta pruning port and data source port, do not comprise other port as router port or member port, then perform step 1105 yet.

Step 1105:IGMP spies upon switch and this IGMP grafting message is forwarded, and this flow process terminates.

Here, if IGMP grafting message is unicast messages, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of this message, this message is forwarded from the outbound port clean culture MAC address entries; If IGMP grafting message is multicast message, then this message is forwarded to all of the port.

This IGMP grafting message can be spied upon switch through other IGMP and arrived multicast source or directly arrive multicast source, the handling process that other IGMP pry switch receives after this IGMP grafting message is identical with embodiment, and multicast source receives the handling process embodiment as shown in Figure 12 after after IGMP grafting message.

Step 1106:IGMP spies upon switch and this beta pruning port is reverted to router port, to make this port can forwarding multicasting stream.

If this IGMP spies upon list item not only comprise beta pruning port, then illustrate that this IGMP spies upon list item and also comprises member port or router port, therefore, IGMP grafting message need not be forwarded.

Step 1107:IGMP spies upon switch and judges that this IGMP spies upon list item and whether also comprises other type port, if so, performs step 1108; Otherwise, perform step 1109.

Step 1108:IGMP spies upon switch and is not for further processing, and this flow process terminates.

Step 1109:IGMP spies upon switch and deletes this IGMP pry list item, and this flow process terminates.

Step 1110:IGMP spies upon switch and is not for further processing, and this flow process terminates.

The situation of step 1110 usually occurs in IGMP and spies upon the IGMP grafting message met with a response to outer transmission IGMP beta pruning query messages after switch receives IGMP prune message, therefore, now the IGMP grafting message received need not be continued to forward.

Figure 12 receives the process chart after IGMP beta pruning and grafting message for the multicast source devices that the embodiment of the present invention provides, and as shown in figure 12, its concrete steps are as follows:

Step 1201: multicast source receives the IGMP prune message for a multicast data flow, suspends and sends this multicast data flow, and arrange the beta pruning time.

The beta pruning time can be 1 minute, and the beta pruning time one arrives, then continue to send this multicast data flow.

Step 1202: multicast source receives the IGMP grafting message for a multicast data flow, recovers to send this multicast data flow.

If multicast source nonrecognition IGMP beta pruning and grafting message, then directly abandon this message, be left intact.

PIM agreement has four patterns, PIM DM, PIM SM, PIM SSM, bidirectional pim.Wherein PIM DM and bidirectional pim all need multicast data flow to design for supposed premise with upstream device, are not suitable for demand mode.Therefore, the embodiment of the present invention for be PIM SSM and PIM SM two patterns.

When adopting IGMP, if PIM agreement is PIM SSM, then igmp version must be IGMPv3, IGMP pry version must be IGMPv3-Snooping.

It should be noted that, in the present invention, do not require the beta pruning characteristic that all fabric anomaly pry switches and multicast source are all supported to mention in the embodiment of the present invention and grafting characteristic, simultaneously, if not all fabric anomaly pry switches all support the beta pruning characteristic mentioned in the embodiment of the present invention and grafting characteristic, then need enable fabric anomaly beta pruning query function on the fabric anomaly pry switch supporting beta pruning characteristic.

For do not support the fabric anomaly of beta pruning characteristic spy upon switch receive message that the present invention increases newly as: after fabric anomaly prune message, fabric anomaly grafting message, this message can be forwarded directly to all of the port; If the beta pruning characteristic that multicast source does not support the embodiment of the present invention to mention and grafting characteristic, then can ignore fabric anomaly prune message and fabric anomaly grafting message.

The composition schematic diagram of the PIM router that Figure 13 provides for the embodiment of the present invention, this PIM router is the first jumping PIM router, is directly connected to multicast source by fabric anomaly pry switch, as shown in figure 13, this PIM router comprises: the first module and the second module, wherein:

First module: receive the multicast data flow that described multicast source is sent, find the local demand not receiving this multicast data flow, or, receive the PIM prune message for a multicast data flow that downstream PIM router is sent, the receiving interface of this message is deleted from the outgoing interface list of this multicast data flow, if find the local demand not received this multicast data flow, then send the beta pruning instruction of carrying described multicast data flow mark to the second module.

Multicast data flow is designated multicast group information, or information about multicast source+multicast group information.

Second module: receive the beta pruning instruction that the first module is sent, according to the multicast data flow mark in this instruction, outwards sends fabric anomaly prune message from the incoming interface of described multicast data flow.

PIM router also can comprise the 3rd module: for receiving the fabric anomaly beta pruning query messages for a multicast data flow, judge whether this locality has the multicast routing table item corresponding with described multicast data flow, if have and the outgoing interface list of this multicast routing table item for empty, then in maximum response time, respond fabric anomaly grafting message.

PIM router also can comprise four module: the fabric anomaly for a multicast data flow that the PIM for a multicast data flow sent for receiving downstream PIM router adds message or under self, extension client is sent adds message, and the multicast source direction to this multicast data flow sends fabric anomaly grafting message.

Four module is further used for, after receiving the PIM for a multicast data flow that downstream PIM router sends and adding message, judge whether this locality has set up the multicast routing table item corresponding with described multicast data flow, if and the outgoing interface list of this multicast routing table item is empty, the receiving interface then described PIM being added message adds in the outgoing interface list of this multicast routing table item, and performs the action of the multicast source direction transmission fabric anomaly grafting message to this multicast data flow.

Below provide the composition of the fabric anomaly pry switch that the embodiment of the present invention provides, this fabric anomaly pry switch is jumped between PIM router at multicast source and first, this switch mainly comprises: the first module, the second module, the 3rd module and four module, wherein:

First module: receive the fabric anomaly prune message for a multicast data flow, using the receiving port of this message as beta pruning port, and add this beta pruning port to the fabric anomaly corresponding with described multicast data flow and spy upon in list item, no longer to multicast data flow described in described beta pruning port repeat.

First module is further used for, for described beta pruning port arranges the beta pruning time, and, after this beta pruning time arrives, start to allow to multicast data flow described in described beta pruning port repeat.

First module is further used for, and after receiving the fabric anomaly prune message for a multicast data flow, if find, this locality is not set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, then set up the fabric anomaly corresponding with described multicast data flow and spy upon list item; And, this beta pruning port is added to after the fabric anomaly corresponding with described multicast data flow spy upon in list item, judge whether this switch exists router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

First module is further used for, after receiving the fabric anomaly prune message for a multicast data flow, local set up the fabric anomaly corresponding with described multicast data flow if find and spy upon list item, then directly execution is described adds the fabric anomaly corresponding with described multicast data flow to and spies upon action in list item by this beta pruning port; And, judge whether described fabric anomaly pry list item comprises member port or router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

First module is further used for, after receiving the fabric anomaly prune message for a multicast data flow, fabric anomaly beta pruning query messages is outwards sent from the receiving port of fabric anomaly prune message, if do not receive the fabric anomaly grafting message of any response in maximum response time, then perform described using the action of the receiving port of this message as beta pruning port.

Second module: receive the fabric anomaly beta pruning query messages that other fabric anomaly pry switch is sent, clean culture MAC address entries is searched according to the source MAC of message, if to find and the outbound port of clean culture MAC address entries is consistent with the receiving port of fabric anomaly beta pruning query messages, then judge whether this locality has been set up the fabric anomaly corresponding with described multicast data flow and spied upon list item, if set up and this fabric anomaly pry list item comprise member port or router port, or, if not set up but this switch has router port, then in maximum response time, respond fabric anomaly grafting message.

3rd module: receive the fabric anomaly grafting message for a multicast data flow, search the fabric anomaly corresponding with this multicast data flow and spy upon list item, the beta pruning port in list item is reverted to router port, starts to allow to forward described multicast data flow to this router port.

3rd module is further used for, after receiving the fabric anomaly grafting message for a multicast data flow, judge that local fabric anomaly corresponding to described multicast data flow is spied upon list item and whether only comprised beta pruning port, if, then forward described fabric anomaly grafting message, and perform the described action described beta pruning port being reverted to router port; Otherwise, directly perform the described action described beta pruning port being reverted to router port.

Four module: the fabric anomaly received for a multicast data flow adds message, search the fabric anomaly corresponding with this multicast data flow in this locality and spy upon list item, the receiving port this fabric anomaly being added message adds in described fabric anomaly pry list item as member port, and adds message to all-router port and this fabric anomaly of beta pruning port repeat; Judge that whether this fabric anomaly adds message from data source port, if from and also there is other data source port in described fabric anomaly pry list item, then send fabric anomaly grafting message to other data source port; If not from, then send fabric anomaly grafting message to all data source ports in described fabric anomaly pry list item.

Below provide the composition of the multicast source that the embodiment of the present invention provides, it mainly comprises: the first module and the second module, wherein:

First module: receive the fabric anomaly prune message for a multicast data flow, suspends and sends described multicast data flow.

Second module: receive the fabric anomaly grafting message for described multicast data flow, recovers to send described multicast data flow.

The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.

Claims

1. a multicast pruning method, multicast source is connected to the first jumping Protocol Independent Multicast PIM router by fabric anomaly pry switch, and it is characterized in that, the method comprises:

Described first jumping PIM router receives the multicast data flow that described multicast source is sent, and finds the local demand not receiving this multicast data flow, then outwards sends fabric anomaly prune message from the incoming interface of this multicast data flow;

After described fabric anomaly pry switch receives described fabric anomaly prune message, using the receiving port of this message as beta pruning port, and add this beta pruning port to the fabric anomaly corresponding with described multicast data flow and spy upon in list item, no longer to multicast data flow described in described beta pruning port repeat;

2. method according to claim 1, is characterized in that, the receiving port of this message comprises further by described fabric anomaly pry switch while beta pruning port:

For this beta pruning port arranges the beta pruning time,

3. method according to claim 1, is characterized in that, described first jumps PIM router finds that the local demand not receiving this multicast data flow comprises:

4. method according to claim 1, is characterized in that, after described fabric anomaly pry switch receives described fabric anomaly prune message, is comprised as taking a step forward of beta pruning port by the receiving port of this message:

5. the method according to claim 1 or 4, is characterized in that, described fabric anomaly pry switch comprises further after this outbound port outwards sends fabric anomaly prune message:

6. method according to claim 1, is characterized in that, after described fabric anomaly pry switch receives described fabric anomaly prune message, is comprised as taking a step forward of beta pruning port by the receiving port of this message:

7. method according to claim 6, is characterized in that, described fabric anomaly pry switch comprises further after the receiving port of fabric anomaly prune message outwards sends fabric anomaly beta pruning query messages:

8. method according to claim 6, is characterized in that, described fabric anomaly pry switch comprises further after the receiving port of fabric anomaly prune message outwards sends fabric anomaly beta pruning query messages:

9. the method according to claim 1 or 4, is characterized in that, this beta pruning port is added to the fabric anomaly corresponding with described multicast data flow by described fabric anomaly pry switch spy upon in list item and comprise further afterwards:

10. method according to claim 9, it is characterized in that, after the PIM for described multicast data flow that described first jumping PIM router reception downstream PIM router is sent adds message, comprise to described taking a step forward of multicast source direction transmission fabric anomaly grafting message:

11. methods according to claim 9, is characterized in that, described method comprises further:

12. methods according to claim 9, is characterized in that, after described fabric anomaly pry switch receives described fabric anomaly grafting message, described beta pruning port is reverted to taking a step forward of router port comprise:

13. methods according to claim 12, is characterized in that, described fabric anomaly pry switch comprises after forwarding described fabric anomaly grafting message further:

14. methods according to claim 1, is characterized in that, described fabric anomaly pry switch supports that IGMP IGMP or multicast listener find agreement MLD agreement.

15. 1 kinds of fabric anomaly pry switches, jump between PIM router at multicast source and first, it is characterized in that, this switch comprises:

First module, receives fabric anomaly prune message, using the receiving port of this message as beta pruning port, and adds this beta pruning port to the fabric anomaly corresponding with described multicast data flow and spies upon in list item, no longer to multicast data flow described in described beta pruning port repeat,

16. switches according to claim 15, is characterized in that, described first module is further used for, for described beta pruning port arranges the beta pruning time, and, after this beta pruning time arrives, start to allow to multicast data flow described in described beta pruning port repeat.

17. switches according to claim 15, it is characterized in that, described first module is further used for, after receiving described fabric anomaly prune message, local set up the fabric anomaly corresponding with described multicast data flow if find and spy upon list item, then directly execution is described adds the fabric anomaly corresponding with described multicast data flow to and spies upon action in list item by this beta pruning port; And, judge whether described fabric anomaly pry list item comprises member port or router port, if not, then search clean culture MAC address entries according to the target MAC (Media Access Control) address of described multicast source, outbound port in the clean culture MAC address entries found is labeled as data source port, outwards sends fabric anomaly prune message from this outbound port.

18. switches according to claim 15, it is characterized in that, described first module is further used for, after receiving described fabric anomaly prune message, fabric anomaly beta pruning query messages is outwards sent from the receiving port of fabric anomaly prune message, if do not receive the fabric anomaly grafting message of any response in maximum response time, then perform described using the action of the receiving port of this message as beta pruning port.

19. switches according to claim 15, is characterized in that, described switch comprises further:

20. switches according to claim 15, is characterized in that, described switch comprises further:

21. switches according to claim 15 or 20, it is characterized in that, described switch comprises further:

22. switches according to claim 20, it is characterized in that, described 3rd module is further used for, after receiving described fabric anomaly grafting message, judge that local fabric anomaly corresponding to described multicast data flow is spied upon list item and whether only comprised beta pruning port, if so, then forward described fabric anomaly grafting message, and perform the described action described beta pruning port being reverted to router port; Otherwise, directly perform the described action described beta pruning port being reverted to router port.