CN106161128A - A kind of multicast traffic stream monitoring method, device and multicast forwarding equipment - Google Patents

Abstract

The present invention proposes a kind of multicast traffic stream monitoring method, device and multicast forwarding equipment, the method includes: flow monitoring step: during multicast forwarding equipment runs multicast service, upper united mouth based on multicast forwarding equipment and the respective multicast data traffic of receiving port, carry out network segment fault location.Apply in actual multicast network environment, only need to run the method on multicast forwarding equipment, just can easily test out the communication conditions between each receiving port and upper united mouth and between multicast forwarding equipment and upper network, facilitate opening and fault location of multicast network, improve equipment and the maintenance efficiency of network.

Description

A method and device for monitoring multicast data flow, and multicast forwarding equipment

technical field

The invention relates to the technical field of network equipment management, in particular to a multicast data stream monitoring method, device and multicast forwarding equipment.

Background technique

Multicast refers to sending the data of the multicast source end to a set of hosts in the form of best-effort delivery in the IP (Internet Protocol, Internet Protocol) network, that is, all members of the multicast group. The multicast source end only needs to send a copy of the destination For data whose address is the address of the multicast group, all members of the multicast group can receive the same copy of the data, and hosts other than members of the multicast group cannot receive the data.

Compared with unicast and broadcast, multicast technology realizes efficient point-to-multipoint data transmission in IP network, effectively saving network bandwidth and reducing network load. Therefore, multicast is widely used in network information service fields such as Internet TV, Internet radio, online live broadcast, distance education and medical treatment, and real-time video conferencing.

At present, there are relatively few detection methods for multicast networks, and most of them are limited to discovering and locating faults through the interaction between the multicast source end and the receiving port of the multicast forwarding device. This method is less feasible to adjust the data traffic at the end.

Contents of the invention

The technical problem to be solved by the present invention is to provide a multicast data stream monitoring method, device and multicast forwarding device, which monitor and locate faults based on the data stream forwarding channel on the multicast forwarding device.

The technical solution adopted by the present invention is that the multicast data flow monitoring method includes:

Traffic monitoring step: during the multicast forwarding device running multicast services, locate faults on the network segment based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device.

Further, in the flow monitoring step, based on the respective multicast data flows of the uplink port of the multicast forwarding device and the receiving port, network segment fault location is performed, including:

Based on the size and/or difference of the multicast data traffic between the uplink port and the receiving port of the multicast forwarding device, network segment fault location is performed between the upper-level network and the inside of the multicast forwarding device.

Further, based on the size and/or difference of the respective multicast data traffic of the uplink port and the receiving port of the multicast forwarding device, network segment fault location is performed between the upper-level network and the multicast forwarding device, including:

For any receiving port, if neither the uplink port of the multicast forwarding device nor the receiving port receives valid multicast data traffic, it is determined that there is a problem with the upper-level network connected to the uplink port; and/or,

For any receiving port, if the difference in multicast data flow between the uplink port of the multicast forwarding device and the receiving port is not within the set normal difference range, it is determined that there is a problem inside the multicast forwarding device.

Further, the type of multicast data traffic includes at least one of the following:

The peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the average value of the data flow per unit time.

Further, the multicast data flow monitoring method also includes:

Message monitoring step: simulate the multicast service establishment process on the multicast forwarding device, and perform port fault location based on the transmission situation of the messages involved in the multicast service establishment process at each port of the multicast forwarding device; Including: uplink port, or, uplink port and receiving port.

Further, as an optional technical solution, the simulating the establishment process of the multicast service on the multicast forwarding device includes:

Send a join message to the uplink port through the CPU of the multicast forwarding device;

The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

If the number of join messages sent by the CPU to the uplink port is different from the number of join messages sent by the uplink port, it is determined that there is a problem with the uplink port and an alarm is issued; otherwise, it is determined that there is no problem with the uplink port.

Further, as another optional technical solution, the simulating the establishment process of the multicast service on the multicast forwarding device includes:

For any receiving port, the CPU of the multicast forwarding device sends a join message to the uplink port through the receiving port;

The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

In the case that there is no problem with the uplink port, if the first condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the first condition is: the number of joining messages passing through the CPU, the receiving port and the uplink port The number is consistent;

In the case of a problem with the uplink port, if the second condition is not met, it is determined that there is a problem with the receiving port and an alarm is issued; the second condition is: the number of joining messages passing through the CPU and the receiving port are the same.

Further, as yet another optional technical solution, the simulating the establishment process of the multicast service on the multicast forwarding device includes:

For any receiving port: first, the CPU of the multicast forwarding device sends a leave message to the uplink port through the receiving port, and then the CPU of the multicast forwarding device sends a join message through the receiving port to the uplink port;

The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

When there is no problem with the uplink port, if the third condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the third condition is: the number of leaving messages passing through the CPU, the receiving port and the uplink port The numbers are all the same, and the number of joining messages passing through the CPU, the receiving port and the uplink port are all the same;

In the case that there is a problem with the uplink port, if the fourth condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the fourth condition is: the number of leaving messages passing through the CPU and the receiving port are the same, and The numbers of joining messages passing through the CPU and the receiving port are the same.

Further, the port fault location is performed based on the transmission status of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, and further includes:

A1: Determine whether the uplink port has received a query message within the set time period after sending the leave message to the upper-level network. If so, determine that there is a problem with the upper-level network, otherwise, perform step A2;

A2: If the number of leaving packets sent by the uplink port to the upper network is not equal to the number of leaving packets received by the receiving port, it is determined that there is a problem inside the multicast forwarding device.

The present invention also provides a multicast data stream monitoring device, comprising:

The flow monitoring module is used to locate faults based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device when the multicast forwarding device is running multicast services.

The present invention also provides a multicast forwarding device, including:

The processor is configured to perform fault location based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device during the operation of the multicast forwarding device;

The uplink port and receiving port are respectively used to forward multicast data traffic.

Adopt above-mentioned technical scheme, the present invention has following advantage at least:

The multicast data stream monitoring method, device and multicast forwarding device of the present invention are applied in the actual multicast network environment, and only need to run this method on the multicast forwarding device, and it is easy to test out the connection between each receiving port and the uplink. The communication status between ports and between multicast forwarding equipment and the upper-level network facilitates the opening and fault location of multicast networks, and improves the maintenance efficiency of equipment and networks.

Description of drawings

Fig. 1 is the flowchart of the multicast data flow monitoring method of the first embodiment of the present invention;

Fig. 2 is the flowchart of the multicast data flow monitoring method of the second embodiment of the present invention;

FIG. 3 is a schematic flowchart of step S203 in the fifth embodiment of the present invention;

FIG. 4 is a schematic composition diagram of a multicast data flow monitoring device according to a sixth embodiment of the present invention;

5 is a schematic composition diagram of a multicast data flow monitoring device according to a seventh embodiment of the present invention;

FIG. 6 is a schematic diagram of network connections in a real application scenario in the group test multicast service according to the ninth embodiment of the present invention;

FIG. 7 is a schematic diagram of a test flow executed in a switching device according to the ninth embodiment of the present invention.

detailed description

In order to further explain the technical means and functions adopted by the present invention to achieve the intended purpose, the present invention will be described in detail below in conjunction with the accompanying drawings and preferred embodiments.

In the first embodiment of the present invention, a multicast data flow monitoring method, as shown in Figure 1, includes the following specific steps:

Step S101, configure multicast information on the multicast forwarding device, the multicast information includes: the multicast source port and the multicast receiving port of the multicast group, and the multicast source port corresponds to the uplink of the multicast forwarding device port, the multicast receiving point port corresponds to the receiving port of the multicast forwarding device;

Step S102 , during the process of the multicast forwarding device running the multicast service according to the multicast information, based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device, fault location of the network segment is performed.

Specifically, in step S102, based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device, network segment fault location is performed, including:

Based on the size and/or difference of the multicast data traffic between the uplink port and the receiving port of the multicast forwarding device, network segment fault location is performed between the upper-level network and the inside of the multicast forwarding device. For example: For any receiving port, if the uplink port of the multicast forwarding device and the receiving port have not received valid multicast data traffic, for example: neither the uplink port of the multicast forwarding device nor the receiving port has received Multicast data traffic, or if the multicast data traffic received by the uplink port and the receiving port is within the flooding traffic range, it is determined that there is a problem with the upper-level network connected to the uplink port and an alarm is issued;

and / or,

For any receiving port, if the difference between the multicast data flow between the uplink port of the multicast forwarding device and the receiving port is not within the set normal difference range, it is determined that there is a problem inside the multicast forwarding device and an alarm is issued.

In the embodiment of the present invention, the type of the selected multicast data traffic includes at least one of the following:

The peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the average value of the data flow per unit time.

When the types of multicast data traffic are more than two types above, a normal difference range for judgment must be set for each type.

The second embodiment of the present invention is a multicast data flow monitoring method. The method described in this embodiment is substantially the same as that in the first embodiment, the difference is that, as shown in FIG. 2 , the multicast data flow monitoring in this embodiment In addition to steps S201-202 corresponding to steps S101-S102 in the first embodiment, the method also includes the following specific steps:

Step S203: Simulate the multicast service establishment process on the multicast forwarding device, and perform port fault location based on the transmission of packets involved in the multicast service establishment process at each port of the multicast forwarding device; the ports include: The uplink port, or, the uplink port and the receiving port, in this embodiment, each port only refers to the uplink port. In the third, fourth, and fifth embodiments, each port includes: an uplink port and a receiving port.

Specifically, in step S203, the process of simulating the establishment of a multicast service on the multicast forwarding device includes:

Send a join message to the uplink port through the CPU of the multicast forwarding device, so that the uplink port can send a join message to the upper network;

In step S203, the port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

If the number of join messages sent by the CPU to the uplink port is different from the number of join messages sent by the uplink port, it is determined that there is a problem with the uplink port and an alarm is issued; otherwise, it is determined that there is no problem with the uplink port.

The third embodiment of the present invention is a method for monitoring multicast data streams. The method described in this embodiment is substantially the same as that in the second embodiment. The difference is that in step S203 of the method for monitoring multicast data streams in this embodiment , the process of simulating the multicast service establishment on the multicast forwarding device includes:

For any receiving port, the CPU of the multicast forwarding device sends a joining message to the upward connection port through the receiving port, specifically: the CPU of the multicast forwarding device sends a joining message to the receiving port for the receiving port to connect to the upward connection port Forward the joining message, and then trigger the uplink port to send the joining message to the upper network;

In step S203, the port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

In the case that there is no problem with the uplink port, if the first condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the first condition is: the number of joining messages passing through the CPU, the receiving port and the uplink port The numbers are all consistent, for example: the number of joining messages sent by the CPU to the receiving port, the number of joining messages sent by the receiving port, and the number of joining messages sent by the uplink port are exactly the same;

In the case that there is a problem with the uplink port, if the second condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the second condition is: the number of added messages passing through the CPU and the receiving port are the same, for example : The number of joining messages sent by the CPU to the receiving port is the same as the number of joining messages sent by the receiving port.

Among them, whether there is a problem with the uplink port can be judged through step S203 in the second embodiment, or, based on the same principle, it is judged that the number of joining messages sent by the receiving port to the uplink port is different from the number of messages sent by the uplink port to the upper network. Whether the number of added messages is the same, if so, it is determined that there is no problem with the uplink port, otherwise it is determined that there is a problem with the uplink port and an alarm is issued. Since the principle of judgment has been given in the second embodiment, it will not be repeated in this embodiment.

The fourth embodiment of the present invention is a method for monitoring multicast data streams. The method described in this embodiment is substantially the same as that in the second embodiment. The difference is that in step S203 of the method for monitoring multicast data streams in this embodiment , the process of simulating the multicast service establishment on the multicast forwarding device includes:

For any receiving port: First, the CPU of the multicast forwarding device sends a leave message to the uplink port through the receiving port, and then the CPU of the multicast forwarding device sends a join message through the receiving port to the uplink port. For example: Firstly, the CPU of the multicast forwarding device sends a leave message to the receiving port, so that the receiving port forwards the leave message to the uplink port, and then triggers the uplink port to send the leave message to the upper network; and then through the multicast forwarding device The CPU sends a join message to the receiving port, so that the receiving port forwards the join message to the uplink port, and then triggers the uplink port to send the join message to the upper network;

The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including:

When there is no problem with the uplink port, if the third condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the third condition is: the number of leaving messages passing through the CPU, the receiving port and the uplink port and the number of joining packets passing through the CPU, the receiving port and the uplink port are all the same, for example: the number of leaving packets sent by the CPU to the receiving port, and the number of leaving packets sent by the receiving port and the number of departure packets sent by the uplink port are exactly the same, and the number of join packets sent by the CPU to the receiving port, the number of join packets sent by the receiving port, and the number of join packets sent by the uplink port are three are exactly the same;

In the case that there is a problem with the uplink port, if the fourth condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the fourth condition is: the number of leaving messages passing through the CPU and the receiving port are the same, and The number of joining messages passing through the CPU and the receiving port are the same, for example: the number of leaving messages sent by the CPU to the receiving port is the same as the number of leaving messages sent by the receiving port, and the number of leaving messages sent by the CPU to the receiving port The number of join messages is the same as the number of join messages sent by the receiving port.

Wherein, whether there is a problem with the uplink port can be judged through step S203 in the second embodiment, or, based on the same principle, by judging the number of leaving messages sent by the CPU to the uplink port and the number of messages sent by the uplink port Whether the number of leaving messages is the same, and judging whether the number of joining messages sent by the receiving port to the uplink port and the number of joining messages sent by the uplink port to the upper network are the same, can determine whether there is a problem with the uplink port. Since the principle of judgment has been given in the second embodiment, it will not be repeated in this embodiment.

The fifth embodiment of the present invention is a method for monitoring multicast data flow. The method described in this embodiment is substantially the same as that in the fourth embodiment. The difference is that, as shown in FIG. 3 , the multicast data flow in this embodiment In step S203 of the monitoring method, the port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, and further includes:

A1: Determine whether the uplink port has received a query message within the set time period after sending the leave message to the upper-level network. If so, it is determined that there is a problem with the upper-level network, and the process ends, otherwise, perform step A2;

A2: If the number of leaving packets sent by the uplink port to the upper network is not equal to the number of leaving packets received by the receiving port, it is determined that there is a problem inside the multicast forwarding device.

The sixth embodiment of the present invention corresponds to the first embodiment. This embodiment introduces a multicast data stream monitoring device, as shown in FIG. 4 , including the following components:

1) The configuration module 100 is used to configure multicast information on the multicast forwarding device, the multicast information includes: the multicast source port and the multicast receiving port of the multicast group, and the multicast source port corresponds to the multicast The uplink port of the forwarding device, the multicast receiving point port corresponds to the receiving port of the multicast forwarding device.

2) The flow monitoring module 200 is used for locating network segment faults based on the respective multicast data flows of the uplink port and receiving port of the multicast forwarding device during the operation of the multicast service by the multicast forwarding device.

Specifically, the flow monitoring module 200 is used for:

For any receiving port, if neither the uplink port of the multicast forwarding device nor the receiving port receives multicast data traffic, or the received multicast data traffic is within the flooding traffic range, it is determined that the uplink port There is a problem with the connected upper-level network and an alarm is issued;

and / or,

For any receiving port, if the data flow difference between the uplink port of the multicast forwarding device and the receiving port is not within the set normal difference range, it is determined that there is a problem inside the multicast forwarding device and an alarm is issued.

Further, the type of multicast data traffic includes at least one of the following:

The peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the average value of the data flow per unit time. When the types of multicast data traffic are more than two types above, a normal difference range for judgment must be set for each type.

The seventh embodiment of the present invention introduces a multicast data stream monitoring device corresponding to the second, third, fourth or fifth embodiments. This embodiment is roughly the same as the sixth embodiment, as shown in FIG. 5 , and also includes the following component:

3) The message monitoring module 300 is used to simulate the multicast service establishment process on the multicast forwarding device, and perform port fault location based on the transmission situation of the messages involved in the multicast service establishment process at each port of the multicast forwarding device .

Specifically, the specific monitoring functions of the message monitoring module 300 respectively correspond to the specific implementation process in step S203 in the second, third, fourth or fifth embodiment.

In the eighth embodiment of the present invention, a multicast forwarding device can be understood as a physical device, and the multicast forwarding device includes the following components:

1) The processor is used for fault location based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device during the operation of the multicast forwarding device;

Specifically, the processor is also used to pre-configure multicast information on the multicast forwarding device, the multicast information includes: the multicast source port and the multicast receiving port of the multicast group, and the multicast source port Corresponding to the uplink port of the multicast forwarding device, the multicast receiving point port corresponds to the receiving port of the multicast forwarding device.

2) The uplink port and the receiving port are respectively used for forwarding multicast data traffic. The details of the functions performed by the processor in this embodiment correspond to the specific steps involved in the multicast data stream monitoring method in the first, second, third, fourth or fifth embodiment.

The ninth embodiment of the present invention, this embodiment is based on the above embodiments, taking the multicast forwarding device as a switching device as an example, an application example of the present invention is introduced with reference to Figures 6-7.

Figure 6 is a schematic diagram of the network connection of a real application scenario in testing the multicast service. As shown in Figure 6, each receiving end device is connected to the switching device, and the switching device is then connected to the source device that provides the multicast data source through the routing network .

When the switching device is deployed, in order to detect the connectivity of the entire network service, ensure that the receiving end device can correctly receive the multicast data source and use the multicast environment after connecting to the switching device; only after placing the switching device is completed , 1. Remotely issue a multicast detection command through the network management or OAM (Operations, Administration and Maintenance) equipment, such as: a multicast detection command for a designated receiving port of the switching device, or a multicast detection command for the switching device The switching device will automatically complete the collection and analysis of the multicast flow information of each port, and report it to the network management or OAM device; 2. On-site testers can directly pass the PC device The serial port or TELNET (a member of the TCP/IP protocol family) logs into the switching device and executes a multicast detection command to complete the collection and analysis of the multicast flow information of each port and obtain the test results.

In order to realize the response of the switching device to the above-mentioned multicast detection command, as shown in Figure 7, the test process performed in the switching device is as follows:

Step 1, start the detection process, and configure multicast information in the switching device, including: multicast virtual local area network MVLAN, multicast group, multicast receiving port, multicast source port, multicast channel information to be tested, join/leave report The key fields of the text, etc., so that it conforms to the simulated real multicast forwarding device.

Wherein, the multicast receiving port in the multicast information corresponds to the receiving port of the switching device, and the multicast source port in the multicast information corresponds to the uplink port of the switching device.

Step 2, specify the multicast VLAN for port multicast monitoring.

Step 3, enable the uplink port multicast flow statistics.

Step 4, the CPU of the switching device sends a multicast join message to the uplink port under the control of the timer, counts the number of join messages sent by the CPU to the uplink port and the number of join messages sent by the uplink port, and is used to determine the number of join messages sent by the uplink port. Is there any problem with the connection port?

Step 5. After confirming that the uplink port receives the multicast traffic, make statistics on the uplink port: the peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the data flow per unit time average of.

Step 6, enable multicast flow statistics on the receiving port.

Step 7, the CPU of the switching device sends a multicast join message to the uplink port through the receiving port under the control of the timer, and counts the number of join messages sent by the CPU to the receiving port, the number of join messages sent by the receiving port, and the number of uplink messages sent by the receiving port. The number of joining packets sent by the port is used to determine whether there is a problem with the uplink port and the receiving port.

Step 8, close the multicast statistics flow of the uplink port.

Step 9. After confirming that the receiving port has received the multicast stream, make statistics on the receiving port: the peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the average value of the data flow per unit time value.

Step 10, according to the statistical results of steps 5 and 9, and the statistical results of steps 4 and 7, give corresponding monitoring results according to corresponding judgment strategies, including fault location and alarm. The judging strategy in this step may be the fault judging process in the first to fifth embodiments.

The traffic statistics in the above step 5 and step 9 conform to the multicast flow ACL (Access Control List, access control list) statistical rules.

It can be seen from Figure 6 that in a real networking environment, only one multicast flow monitoring command needs to be run on the receiving port to automatically complete the data display and evaluation of the current multicast network status, and give out the existing problems Fault location greatly improves the efficiency of network device management.

The multicast data flow monitoring method, device and multicast forwarding device described in the embodiment of the present invention are applied in an actual multicast network environment, and it is only necessary to run this method on the multicast forwarding device to easily test the connection between each receiving port and the multicast forwarding device. The communication status between the uplink ports and between the multicast forwarding equipment and the upper-level network facilitates the opening and fault location of the multicast network, and improves the maintenance efficiency of equipment and networks.

Due to the wide application fields and prospects of multicast, it is very important to ensure the timely and smooth flow of multicast data. When the multicast data flow is interrupted due to a fault, it is necessary to locate the fault location in time. The purpose of the present invention is to locate faults in the network segment between the source device and the data receiving device, and each switching device is regarded as a segment, and the devices with multicast data forwarding can use the technology of the present invention to troubleshoot. Fault location is realized by monitoring the multicast data flow of the uplink port and the receiving port of the device.

Through the description of the specific implementation, it should be possible to gain a deeper and more specific understanding of the technical means and effects of the present invention to achieve the intended purpose. However, the attached drawings are only for reference and description, and are not used to explain the present invention. limit.

Claims (11)

1. A method for monitoring multicast data streams, comprising: Traffic monitoring step: during the multicast forwarding device running multicast services, locate faults on the network segment based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device. 2. The multicast data flow monitoring method according to claim 1, characterized in that, in the flow monitoring step, based on the multicast data flow of the uplink port of the multicast forwarding device and the respective multicast data flow of the receiving port, the network segment is carried out Fault location, including: Based on the size and/or difference of the multicast data traffic between the uplink port and the receiving port of the multicast forwarding device, network segment fault location is performed between the upper-level network and the inside of the multicast forwarding device. 3. the multicast data flow monitoring method according to claim 2, is characterized in that, based on the size and/or difference of the respective multicast data flows of the uplink port of the multicast forwarding device and the receiving port, in the superior network and group Network segment fault location between broadcast and forwarding devices, including: For any receiving port, if neither the uplink port of the multicast forwarding device nor the receiving port receives valid multicast data traffic, it is determined that there is a problem with the upper-level network connected to the uplink port; and/or, For any receiving port, if the difference in multicast data flow between the uplink port of the multicast forwarding device and the receiving port is not within the set normal difference range, it is determined that there is a problem inside the multicast forwarding device. 4. The multicast data flow monitoring method according to any one of claims 1 to 3, wherein the type of the multicast data flow includes at least one of the following: The peak value of the data flow per unit time, the valley value of the data flow per unit time, the sum of the data flow per unit time, and the average value of the data flow per unit time. 5. The multicast data flow monitoring method according to claim 1, wherein the multicast data flow monitoring method further comprises: Message monitoring step: simulate the multicast service establishment process on the multicast forwarding device, and perform port fault location based on the transmission situation of the messages involved in the multicast service establishment process at each port of the multicast forwarding device; Including: uplink port, or, uplink port and receiving port. 6. The multicast data flow monitoring method according to claim 5, wherein said simulating a multicast service establishment process on the multicast forwarding device includes: Send a join message to the uplink port through the CPU of the multicast forwarding device; The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including: If the number of join messages sent by the CPU to the uplink port is different from the number of join messages sent by the uplink port, it is determined that there is a problem with the uplink port and an alarm is issued; otherwise, it is determined that there is no problem with the uplink port. 7. The multicast data flow monitoring method according to claim 5, wherein said simulating a multicast service establishment process on the multicast forwarding device comprises: For any receiving port, the CPU of the multicast forwarding device sends a join message to the uplink port through the receiving port; The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including: In the case that there is no problem with the uplink port, if the first condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the first condition is: the number of joining messages passing through the CPU, the receiving port and the uplink port The number is consistent; In the case of a problem with the uplink port, if the second condition is not met, it is determined that there is a problem with the receiving port and an alarm is issued; the second condition is: the number of joining messages passing through the CPU and the receiving port are the same. 8. The multicast data flow monitoring method according to claim 5, wherein said simulating a multicast service establishment process on the multicast forwarding device comprises: For any receiving port: first, the CPU of the multicast forwarding device sends a leave message to the uplink port through the receiving port, and then the CPU of the multicast forwarding device sends a join message through the receiving port to the uplink port; The port fault location is carried out based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, including: When there is no problem with the uplink port, if the third condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the third condition is: the number of leaving messages passing through the CPU, the receiving port and the uplink port The numbers are all the same, and the number of joining messages passing through the CPU, the receiving port and the uplink port are all the same; In the case that there is a problem with the uplink port, if the fourth condition is not met, it is determined that there is a problem with the receiving port and an alarm is given; the fourth condition is: the number of leaving messages passing through the CPU and the receiving port are the same, and The numbers of joining messages passing through the CPU and the receiving port are the same. 9. The method for monitoring multicast data streams according to claim 8, characterized in that, based on the transmission situation of the packets involved in the multicast service establishment process at each port of the multicast forwarding device, port fault location is carried out, Also includes: A1: Determine whether the uplink port has received a query message within the set time period after sending the leave message to the upper-level network. If so, determine that there is a problem with the upper-level network, otherwise, perform step A2; A2: If the number of leaving packets sent by the uplink port to the upper network is not equal to the number of leaving packets received by the receiving port, it is determined that there is a problem inside the multicast forwarding device. 10. A multicast data flow monitoring device, characterized in that, comprising: The flow monitoring module is used to locate faults based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device when the multicast forwarding device is running multicast services. 11. A multicast forwarding device, comprising: The processor is configured to perform fault location based on the respective multicast data flows of the uplink port and the receiving port of the multicast forwarding device during the operation of the multicast forwarding device; The uplink port and receiving port are respectively used to forward multicast data traffic.