Method and system for dynamically presenting multicast data flow topology of IP (Internet Protocol) network
By obtaining the multicast forwarding information and receiving member information of the switch, generating the multicast distribution tree topology diagram and dynamically presenting the IP address of the multicast receiving member, the problem of difficulty in dynamically presenting the multicast data flow forwarding path in the prior art is solved, real-time display of the multicast topology structure and fast positioning of illegal multicast receivers are realized.
Patent Information
- Application Number
- CN202510268725.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-07
- Publication Date
- 2025-06-06
AI Technical Summary
Existing network management systems have difficulty presenting multicast data stream forwarding paths dynamically, resulting in difficulties in management and maintenance in complex and dynamically changing multicast networks, especially in terms of fault location and identification of illegal multicast receivers.
By obtaining multicast forwarding information on each switch, a multicast distribution tree topology map is generated, and multicast receiving member information is obtained. The IP addresses of the multicast receiving member are dynamically presented on the leaf nodes of the multicast distribution tree topology, and the dynamic presentation of the multicast data flow topology is realized.
Real-time display of the multicast topology structure is realized, user terminals that can timely grasp the multicast service, quickly locate illegal multicast receivers, and improve network management efficiency and accuracy.
Smart Images
Figure CN120110985A_ABST
Abstract
Description
Technical Field
[0001] The present application generally relates to the field of network communication technology. More specifically, the present application relates to a method and system for dynamically presenting multicast data flow topology in an IP network. Background Art
[0002] With the development of Internet technology, multicast technology has been widely used in multimedia broadcasting, real-time data transmission and other fields. Multicast technology allows a sender to send information to multiple receivers at the same time, thereby effectively reducing network bandwidth consumption and server load. However, with the popularity of multicast applications, network administrators are facing a series of new challenges, especially in the management and maintenance of large-scale multicast networks.
[0003] Existing network management systems can usually only display the basic topology of the network and monitor the overall connectivity status of the network. Such systems lack the ability to dynamically present the forwarding path of specific data flows, which is an obvious shortcoming for complex and dynamically changing multicast networks. Traditionally, in order to analyze network performance, people rely on deploying probes to capture multicast network mirror traffic and calculate the forwarding path of the message by comparing the message timestamps. Although this method can reveal the flow of data packets in the network to a certain extent, it has significant limitations: on the one hand, it is necessary to widely deploy network probes, which not only increases the complexity of the system but also increases the operating costs; on the other hand, this method has high requirements for time synchronization between network devices, because it heavily relies on the consistency and accuracy of message timestamps when calculating data forwarding paths. In actual operations, it is often difficult to achieve such precise time synchronization, which limits the effectiveness and reliability of this method.
[0004] In view of this, there is an urgent need to provide a dynamic presentation solution for multicast data flow topology in IP networks to display the multicast topology in real time and provide comprehensive and effective information when handling multicast failures. Summary of the invention
[0005] In order to at least solve one or more of the technical problems mentioned above, the present application proposes a dynamic presentation solution for multicast data flow topology in an IP network in multiple aspects.
[0006] In a first aspect, the present application provides a method for dynamically presenting a multicast data flow topology for an IP network, comprising: obtaining multicast forwarding table information on each switch; generating a multicast distribution tree topology map based on the obtained multicast forwarding table information; obtaining multicast receiving member information of each switch; obtaining an IP address of a multicast receiving member corresponding to each switch based on the multicast receiving member information; and presenting a multicast receiving member corresponding to the IP address of the multicast receiving member on a leaf node of the multicast distribution tree topology map based on the IP address of the multicast receiving member corresponding to each switch.
[0007] In some embodiments, in the process of obtaining multicast forwarding table information on each switch, the following steps are performed: selecting a connection mode of the switch according to the management method supported by the switch; using a corresponding library function to implement a session connection between the client and the switch according to the selected connection mode; sending a first instruction to the switch through the client to obtain its corresponding multicast forwarding table information; wherein the first instruction is an instruction to view the multicast forwarding table information.
[0008] In some embodiments, the multicast forwarding table information includes a multicast source IP address, a multicast group IP address, uplink interface information, and downlink interface information.
[0009] In some embodiments, in the process of generating a multicast distribution tree topology map based on the acquired multicast forwarding table information, the following steps are performed: the acquired multicast forwarding table information is subjected to string extraction processing to obtain the uplink interface information and the downlink interface information of the switch; the multicast forwarding table information is parsed, the multicast source is used as the root node, and the multicast group is used as the leaf node; according to the uplink interface information and the downlink interface information of the switch, switches are gradually added as branch nodes between the multicast source and the multicast group to form a path from the root node to the leaf node, thereby obtaining a multicast distribution tree topology map.
[0010] In some embodiments, in the process of obtaining the multicast receiving member information of each switch, the following steps are performed: selecting the connection mode of the switch according to the management method supported by the switch; using the corresponding library function to realize the session connection between the client and the switch according to the selected connection mode; sending a second instruction to the switch through the client to obtain its corresponding multicast receiving member information; wherein, the second instruction is an instruction to view the multicast receiving member information.
[0011] In some embodiments, the connection mode of the switch includes a telnet connection mode and an SSH connection mode.
[0012] In some embodiments, in the process of obtaining the IP addresses of the multicast receiving members corresponding to each switch according to the multicast receiving member information, the following steps are performed: using the first regular expression and the second regular expression to match the multicast receiving member information respectively to obtain the source address and the last reporter address; storing the matched source address and the last reporter address in the source address list and the group list respectively; judging whether each source address in the source address list matches the queried multicast source IP address; in response to the source address in the source address list not matching the queried multicast source IP address, not processing the last reporter address stored in the group list; in response to each source address in the source address list matching the specified multicast source IP address, extracting the last reporter address stored in the group list and storing it in the IGMP group list; reading the IGMP group list to obtain the IP address of the multicast receiving member corresponding to the corresponding switch; wherein, the first regular expression is a regular expression for matching the source address; and the second regular expression is a regular expression for matching the last reporter address.
[0013] In some embodiments, the IGMP group list includes a designated multicast source IP address, a multicast group address associated with the designated multicast source, and a last reporter address associated with the designated multicast source.
[0014] In some embodiments, in the process of reading the IGMP group list to obtain the IP address of the multicast receiving member corresponding to the corresponding switch, the following steps are performed: reading the IGMP group list; parsing the last reporter address associated with the specified multicast source in the IGMP group list; and using the parsed last reporter address associated with the specified multicast source as the IP address of the multicast receiving member corresponding to the corresponding switch.
[0015] In a second aspect, the present application provides a system for dynamically presenting multicast data flow topology for an IP network, which adopts the method for dynamically presenting multicast data flow topology for an IP network as described in any embodiment of the first aspect to dynamically present multicast data flow topology, and the system includes: a multicast forwarding table information acquisition module, which is used to obtain multicast forwarding table information on each switch; a multicast distribution tree topology map acquisition module, which is used to generate a multicast distribution tree topology map based on the acquired multicast forwarding table information; a multicast receiving member information acquisition module, which is used to obtain the multicast receiving member information of each switch; a multicast receiving member IP address acquisition module, which is used to obtain the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information; a multicast receiving member presentation module, which is used to present the multicast receiving member corresponding to the IP address of the multicast receiving member on the leaf node of the multicast distribution tree topology map according to the IP address of the multicast receiving member corresponding to each switch.
[0016] Through the dynamic presentation scheme of multicast data flow topology for IP network provided above, the embodiment of the present application can display the multicast topology structure in real time. By presenting the multicast receiving members corresponding to the IP addresses of the multicast receiving members on the leaf nodes of the multicast distribution tree topology diagram, the user terminals of the multicast service can be grasped in time, and the illegal multicast receivers can be located in time when illegal requests for WAN multicast cause export network congestion failure. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] By reading the detailed description below with reference to the accompanying drawings, the above and other purposes, features and advantages of the exemplary embodiments of the present application will become easy to understand. In the accompanying drawings, several embodiments of the present application are shown in an exemplary and non-limiting manner, and the same or corresponding reference numerals represent the same or corresponding parts, wherein:
[0018] Figure 1 An exemplary flow chart of a method for dynamically presenting a multicast data flow topology in an IP network according to an embodiment of the present application is shown;
[0019] Figure 2 An exemplary flow chart of obtaining the IP addresses of multicast receiving members corresponding to each switch according to an embodiment of the present application is shown;
[0020] Figure 3 A schematic diagram showing a multicast distribution tree topology diagram of a network composed of four switches according to some embodiments of the present application;
[0021] Figure 4 An exemplary structural block diagram of a system for dynamically presenting multicast data flow topology in an IP network according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0022] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.
[0023] It should be understood that the terms "include" and "comprising" used in the specification and claims of the present application indicate the presence of described features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or collections thereof.
[0024] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in this application specification and claims, unless the context clearly indicates otherwise, the singular forms of "a", "an" and "the" are intended to include plural forms. It should also be further understood that the term "and / or" used in this application specification and claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.
[0025] As used in this specification and claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.
[0026] The specific implementation of the present application is described in detail below with reference to the accompanying drawings.
[0027] Figure 1 An exemplary flow chart of a system 100 for dynamically presenting multicast data flow topology in an IP network according to an embodiment of the present application is shown.
[0028] like Figure 1 As shown, in step S110, multicast forwarding table information is obtained on each switch.
[0029] In an embodiment of the present application, in the process of obtaining multicast forwarding table information on each switch, first, the connection mode of the switch is selected according to the management mode supported by the switch. Then, according to the selected connection mode, a corresponding library function is used to implement a session connection between the client and the switch. Then, the client sends a first instruction to the switch to obtain its corresponding multicast forwarding table information.
[0030] Specifically, the management methods supported by the switch include out-of-band management and in-band management. Out-of-band management refers to device management through a dedicated management interface, which does not occupy the normal service traffic channel. In-band management uses the service port of the switch for remote management and monitoring.
[0031] In some embodiments of the present application, the connection mode of the switch includes a telnet connection mode and an SSH connection mode. In other embodiments of the present application, the connection mode of the switch may also select other connection modes in addition to the telnet connection mode and the SSH connection mode according to the management mode it supports, and the present application does not limit this.
[0032] By selecting the switch connection mode according to the management method supported by the switch, you can select a connection mode suitable for the switch management method, which can ensure the efficiency and stability of network data transmission. At the same time, selecting a connection mode suitable for the switch management method can simplify network management operations and reduce management costs.
[0033] In the embodiment of the present application, when the switch connection mode is telnet connection mode, the session connection between the client and the switch is realized through the library function org.apache.commons.net.telnet.TelnetClient. When the switch connection mode is SSH connection mode, the session connection between the client and the switch is realized through the library function com.jcraft.jsch.*.
[0034] By using the corresponding library function to realize the session connection between the client and the switch according to the selected connection mode, the communication compatibility and interoperability between the client and the switch can be ensured. At the same time, the use of appropriate library functions can optimize the data transmission process, reduce communication delays and packet loss rates, and thus improve the communication efficiency between the client and the switch.
[0035] Specifically, the first instruction is an instruction for viewing multicast forwarding table information, and the first instruction uses "displaymulticast forwarding-table".
[0036] In an embodiment of the present application, the multicast forwarding table information includes a multicast source IP address, a multicast group IP address, an uplink interface information, and a downlink interface information.
[0037] After executing step S110, in step S120, a multicast distribution tree topology diagram is generated according to the acquired multicast forwarding table information.
[0038] In an embodiment of the present application, in the process of generating a multicast distribution tree topology diagram according to the obtained multicast forwarding table information, first, the obtained multicast forwarding table information is subjected to a character string extraction process to obtain the uplink interface information and downlink interface information of the switch. Next, the multicast forwarding table information is parsed, with the multicast source as the root node and the multicast group as the leaf node. Then, according to the uplink interface information and downlink interface information of the switch, switches are gradually added as branch nodes between the multicast source and the multicast group to form a path from the root node to the leaf node, thereby obtaining a multicast distribution tree topology diagram.
[0039] In an embodiment of the present application, the obtained multicast forwarding table information is subjected to character string extraction processing, and the specific process involved in obtaining the uplink interface information and the downlink interface information of the switch is as follows: First, the obtained multicast forwarding table information is parsed into an operable character string format. This usually involves reading data from a network protocol or a file, and converting it into a character string or a data structure that a program can process. Then, according to the format of the multicast forwarding table information, the extraction rules of the uplink interface and the downlink interface are defined, and these rules may include searching for specific keywords, separators or field positions, etc. Then, using a character string matching algorithm, the character string related to the uplink interface and the downlink interface is searched in the parsed multicast forwarding table information, and according to the defined extraction rules, the specific information of the uplink interface and the downlink interface is extracted from the matched character string. In addition, the extracted uplink interface and the downlink interface information can be processed by removing redundant characters, converting formats, and storing them in a database.
[0040] The above process of forming a multicast distribution tree topology provides an intuitive way to view the propagation path of multicast data streams in the network. By drawing the complete path from the multicast source to the multicast group, the administrator can clearly see which devices are involved in the data transmission and the connection relationship between them. When there is a problem with multicast data transmission, such as packet loss or increased latency, the problem can be quickly located by analyzing the multicast distribution tree. For example, if a switch is abnormal, it may cause all multicast group members downstream to not receive data. By checking the status of the switch and its position in the tree, the problem can be found and solved more quickly. At the same time, the multicast distribution tree can help identify potential bottlenecks in the network. For example, if it is found that some switches carry a large amount of multicast traffic, it may be necessary to consider adjusting the routing policy or upgrading the hardware to improve performance.
[0041] After executing step S120, in step S130, the multicast receiving member information of each switch is obtained.
[0042] In the embodiment of the present application, in the process of obtaining the multicast receiving member information of each switch, first, the connection mode of the switch is selected according to the management mode supported by the switch. Then, according to the selected connection mode, the corresponding library function is used to implement the session connection between the client and the switch. Then, the client sends a second instruction to the switch to obtain its corresponding multicast receiving member information.
[0043] Specifically, the specific contents involved in selecting the connection mode of the switch according to the management mode supported by the switch and the specific contents involved in using the corresponding library function to implement the session connection between the client and the switch according to the selected connection mode can be referred to the previous text, and this application will not repeat them here.
[0044] Specifically, the second instruction is an instruction for viewing the multicast receiving member information, and the second instruction adopts "display igmpgroup verbose".
[0045] After executing step S130, in step S140, the IP address of the multicast receiving member corresponding to each switch is obtained according to the multicast receiving member information.
[0046] In the embodiment of the present application, the specific process involved in obtaining the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information can be found in Figure 2 .
[0047] Figure 2 An exemplary flow chart of obtaining the IP addresses of multicast receiving members corresponding to each switch according to an embodiment of the present application is shown.
[0048] like Figure 2 As shown, in step S210, the first regular expression and the second regular expression are respectively used to match the multicast receiving member information to obtain the source address and the last reporter address. In step S220, the matched source address and the last reporter address are respectively stored in the source address list and the group list. In step S230, it is determined whether each source address in the source address list matches the queried multicast source IP address. In response to the source address in the source address list not matching the queried multicast source IP address, in step S240, the last reporter address stored in the group list is not processed. In response to the source addresses in the source address list matching the specified multicast source IP address, in step S250, the last reporter address stored in the group list is extracted and stored in the IGMP group list. Then, in step S260, the IGMP group list is read to obtain the IP address of the multicast receiving member corresponding to the corresponding switch.
[0049] In an embodiment of the present application, the first regular expression is a regular expression for matching a source address, and the second regular expression is a regular expression for matching a last reporter address. Specifically, the first regular expression uses "Pattern.compile("Source:(\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3})")", and the second regular expression uses "Pattern.compile("Last reporter:(\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3})")".
[0050] In the embodiment of the present application, the IGMP group list includes the designated multicast source IP address, the multicast group address associated with the designated multicast source, and the last reporter address associated with the designated multicast source.
[0051] In an embodiment of the present application, the designated multicast source IP address is a multicast source IP address input by a network administrator through a user terminal when performing network diagnosis, monitoring or management.
[0052] In an embodiment of the present application, in the process of reading the IGMP group list to obtain the IP address of the multicast receiving member corresponding to the corresponding switch, first, the IGMP group list is read. Then, the last reporter address associated with the specified multicast source in the IGMP group list is parsed. Then, the parsed last reporter address associated with the specified multicast source is used as the IP address of the multicast receiving member corresponding to the corresponding switch.
[0053] By reading the IGMP group list and parsing the last reporter address, you can accurately identify which are the multicast receiving members of the current multicast group, especially the members associated with the specified multicast source. By reading and parsing the IGMP group list in real time, network administrators can dynamically manage multicast groups to ensure accurate transmission of multicast data. At the same time, network administrators can easily track and manage the membership of multicast groups, reducing the complexity of network management.
[0054] After step S140 is executed, in step S150, the multicast receiving members corresponding to the IP addresses of the multicast receiving members corresponding to the switches are presented on the leaf nodes of the multicast distribution tree topology diagram.
[0055] By presenting the multicast receiving members corresponding to the IP addresses of the multicast receiving members on the leaf nodes of the multicast distribution tree topology map according to the IP addresses of the multicast receiving members corresponding to each switch, network administrators can obtain a refined view of the reception of multicast traffic. This allows administrators to know exactly which devices are receiving a specific multicast stream, which helps to perform more detailed management and optimization. When a multicast stream transmission problem occurs, such as some multicast receiving members cannot receive data, you can directly view the leaf nodes on the multicast distribution tree topology map to quickly locate the affected multicast receiving members and the switches they are connected to. This can greatly shorten the troubleshooting time and speed up the problem solving. At the same time, by mapping the specific multicast receiving member IP addresses to the leaf nodes of the multicast distribution tree topology map, you can understand the distribution of multicast receiving members on each switch, so that you can reasonably allocate bandwidth and other resources according to actual needs, and help implement more stringent security measures. For example, you can configure access control lists (ACLs) to restrict unauthorized devices from joining specific multicast groups, thereby enhancing network security protection capabilities. In addition, as the multicast receiving members in the network change, the multicast distribution tree topology map can reflect these changes in a timely manner. This is especially important in situations where network settings need to be adjusted dynamically, such as in large-scale enterprise networks or data center environments, where the addition or removal of new devices requires real-time updates to the network status.
[0056] In summary, through the dynamic presentation scheme of multicast data flow topology for IP network as provided above, the embodiment of the present application can display the multicast topology structure in real time. By presenting the multicast receiving members corresponding to the IP addresses of the multicast receiving members on the leaf nodes of the multicast distribution tree topology diagram, the user terminals of the multicast service can be grasped in time, and the illegal multicast receivers can be located in time when illegal requests for WAN multicast cause export network congestion failure.
[0057] In some embodiments of the present application, in a network structure composed of four switches SWA, SWB, SWC and SWD, the four switches realize interconnection between networks through the OSPF dynamic routing protocol. The multicast routing protocol adopts the PIM SM protocol, and the IGMPv3 protocol is enabled on the switch on the terminal receiving side.
[0058] The dynamic presentation of the multicast data flow topology of the network structure is achieved through the aforementioned method 100 for dynamic presentation of the multicast data flow topology of the IP network.
[0059] First, obtain the multicast forwarding table information on each switch, and obtain the multicast forwarding table corresponding to the switch SWA as shown in Table 1:
[0060] Table 1 Multicast forwarding table corresponding to switch SWA
[0061] Source 192.168.50.5 Group 232.77.1.1 Incoming interface Vlanif100 Outgoing interfaces Vlanifl0
[0062] The multicast forwarding table corresponding to the switch SWB is shown in Table 2:
[0063] Table 2 Multicast forwarding table corresponding to switch SWB
[0064] Source 192.168.50.5 Group 232.77.1.1 Incoming interface Vlanif20 Outgoing interfaces Vlanif100; Vlanif200
[0065] The multicast forwarding table corresponding to the switch SWC is shown in Table 3:
[0066] Table 3 Multicast forwarding table corresponding to switch SWC
[0067] Source 192.168.50.5 Group 232.77.1.1 Incoming interface Vlanif200 Outgoing interfaces Vlanif300
[0068] The multicast forwarding table corresponding to the switch SWD is shown in Table 4:
[0069] Table 4 Multicast forwarding table corresponding to switch SWD
[0070] Source 192.168.50.5 Group 232.77.1.1 Incoming interface Vlanif300 Outgoing interfaces Vlanif20
[0071] It can be concluded from Tables 1 to 4 that a multicast source is configured in the network. The IP address of the multicast source is 192.168.50.5, and the IP address of the multicast group is 232.77.1.1.
[0072] Next, a multicast distribution tree topology is generated based on the obtained multicast forwarding table information. Then, the multicast receiving member information of each switch is obtained. Next, the IP address of the multicast receiving member corresponding to each switch is obtained based on the multicast receiving member information, and the multicast receiving member corresponding to the IP address of the multicast receiving member is presented on the leaf node of the multicast distribution tree topology according to the IP address of the multicast receiving member corresponding to each switch. The multicast distribution tree topology corresponding to the network presented in the end can be found in Figure 3 .
[0073] like Figure 3 As shown, there are two multicast receiving members in the network, the IP address of the first multicast receiving member is 192.168.10.10, and the IP address of the second multicast receiving member is 192.168.11.10.
[0074] An embodiment of the present application also provides a system for dynamically presenting the multicast data flow topology for an IP network, which may adopt the aforementioned method 100 for dynamically presenting the multicast data flow topology for an IP network to dynamically present the multicast data flow topology for an IP network, or may adopt other systems for dynamically presenting the multicast data flow topology for an IP network to dynamically present the multicast data flow topology for an IP network, and the present application does not make any limitation thereto.
[0075] Figure 4 An exemplary structural block diagram of a system for dynamically presenting multicast data flow topology for an IP network according to an embodiment of the present application is shown.
[0076] like Figure 4 As shown, the system 400 includes a multicast forwarding table information acquisition module 410, a multicast distribution tree topology acquisition module 420, a multicast receiving member information acquisition module 430, a multicast receiving member IP address acquisition module 440, and a multicast receiving member presentation module 450. In the embodiment of the present application, the multicast forwarding table information acquisition module 410, the multicast distribution tree topology acquisition module 420, the multicast receiving member information acquisition module 430, the multicast receiving member IP address acquisition module 440, and the multicast receiving member presentation module 450 can be separate units or integrated in the same integrated circuit, and the present application does not limit this.
[0077] Specifically, the multicast forwarding table information acquisition module 410 is used to acquire the multicast forwarding table information on each switch.
[0078] Specifically, the multicast distribution tree topology map acquisition module 420 is used to generate a multicast distribution tree topology map according to the acquired multicast forwarding table information.
[0079] Specifically, the multicast receiving member information obtaining module 430 is used to obtain the multicast receiving member information of each switch.
[0080] Specifically, the multicast receiving member IP address acquisition module 440 is used to acquire the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information.
[0081] Specifically, the multicast receiving member presenting module 450 is used to present the multicast receiving members corresponding to the IP addresses of the multicast receiving members on the leaf nodes of the multicast distribution tree topology diagram according to the IP addresses of the multicast receiving members corresponding to each switch.
[0082] When the system 400 uses the aforementioned system 100 for dynamically presenting the multicast data flow topology of the IP network to dynamically present the multicast data flow topology of the IP network, the multicast forwarding table information acquisition module 410 executes the aforementioned step S110, the multicast distribution tree topology map acquisition module 420 executes the aforementioned step S120, the multicast receiving member information acquisition module 430 executes the aforementioned step S130, the multicast receiving member IP address acquisition module 440 executes the aforementioned step S140, and the multicast receiving member presentation module 450 executes the aforementioned step S150. The specific execution process can be referred to the above text, which will not be repeated here.
[0083] Although multiple embodiments of the present application have been shown and described herein, it is obvious to those skilled in the art that such embodiments are provided only by way of example. Those skilled in the art can think of many changes, modifications and alternatives without departing from the thought and spirit of the present application. It should be understood that in the process of practicing the present application, various alternatives to the embodiments of the present application described herein can be adopted. The attached claims are intended to limit the scope of protection of the present application, and therefore cover equivalents or alternatives within the scope of these claims.
Claims
1. A method for dynamically presenting multicast data flow topology in an IP network, characterized in that: include: Obtain multicast forwarding table information on each switch; Generate a multicast distribution tree topology diagram based on the acquired multicast forwarding table information; Get the multicast receiving member information of each switch; Obtain the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information; According to the IP addresses of the multicast receiving members corresponding to the switches, the multicast receiving members corresponding to the IP addresses of the multicast receiving members are presented on the leaf nodes of the multicast distribution tree topology diagram.
2. The method for dynamically presenting multicast data flow topology in an IP network according to claim 1, characterized in that: To obtain multicast forwarding table information on each switch, perform the following steps: Select the switch connection mode according to the management method supported by the switch; According to the selected connection mode, the corresponding library function is used to realize the session connection between the client and the switch; Sending a first instruction to the switch through the client to obtain the corresponding multicast forwarding table information; The first instruction is an instruction for checking multicast forwarding table information.
3. The method for dynamically presenting multicast data flow topology in an IP network according to claim 1, characterized in that: The multicast forwarding table information includes a multicast source IP address, a multicast group IP address, uplink interface information, and downlink interface information.
4. The method for dynamically presenting multicast data flow topology in an IP network according to claim 3, characterized in that: In the process of generating a multicast distribution tree topology map according to the obtained multicast forwarding table information, the following steps are performed: Perform string extraction processing on the obtained multicast forwarding table information to obtain the uplink interface information and downlink interface information of the switch; Parse the multicast forwarding table information, take the multicast source as the root node, and the multicast group as the leaf node; According to the uplink interface information and downlink interface information of the switch, switches are gradually added as branch nodes between the multicast source and the multicast group to form a path from the root node to the leaf node, thereby obtaining a multicast distribution tree topology diagram.
5. The method for dynamically presenting multicast data flow topology in an IP network according to claim 1, characterized in that: In the process of obtaining the multicast receiving member information of each switch, perform the following steps: Select the switch connection mode according to the management method supported by the switch; According to the selected connection mode, the corresponding library function is used to realize the session connection between the client and the switch; The client sends a second instruction to the switch to obtain the corresponding multicast receiving member information; The second instruction is an instruction for checking the multicast receiving member information.
6. The method for dynamically presenting multicast data flow topology in an IP network according to claim 2 or 5, characterized in that: The connection modes of the switch include telnet connection mode and SSH connection mode.
7. The method for dynamically presenting multicast data flow topology in an IP network according to claim 1, characterized in that: In the process of obtaining the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information, the following steps are performed: The first regular expression and the second regular expression are respectively used to match the multicast receiving member information to obtain the source address and the last reporter address; The matched source address and the last reporter address are stored in the source address list and the group list respectively; Determine whether each source address in the source address list matches the queried multicast source IP address; In response to the presence of a source address in the source address list not matching the queried multicast source IP address, not processing the last reporter address stored in the group list; In response to each source address in the source address list matching the designated multicast source IP address, extracting the last reporter address stored in the group list and storing it in the IGMP group list; Read the IGMP group list to obtain the IP address of the multicast receiving member corresponding to the corresponding switch; Wherein, the first regular expression is a regular expression for matching a source address; The second regular expression is a regular expression for matching the last reporter address.
8. The method for dynamically presenting multicast data flow topology in an IP network according to claim 7, characterized in that: The IGMP group list includes the designated multicast source IP address, the multicast group address associated with the designated multicast source, and the last reporter address associated with the designated multicast source.
9. The method for dynamically presenting multicast data flow topology in an IP network according to claim 8, characterized in that: In the process of reading the IGMP group list to obtain the IP address of the multicast receiving member corresponding to the corresponding switch, the following steps are performed: Read the IGMP group list; Parse the last reporter address associated with the specified multicast source in the IGMP group list; The resolved last reporter address associated with the designated multicast source is used as the IP address of the multicast receiving member corresponding to the corresponding switch.
10. A system for dynamically presenting multicast data flow topology in an IP network, characterized in that: The method for dynamically presenting the multicast data flow topology of an IP network as claimed in any one of claims 1 to 9 is used to dynamically present the multicast data flow topology, and the system comprises: A multicast forwarding table information acquisition module is used to obtain multicast forwarding table information on each switch; A multicast distribution tree topology acquisition module is used to generate a multicast distribution tree topology according to the acquired multicast forwarding table information; A multicast receiving member information acquisition module is used to obtain the multicast receiving member information of each switch; The IP address acquisition module of the multicast receiving member is used to acquire the IP address of the multicast receiving member corresponding to each switch according to the multicast receiving member information; The multicast receiving member presenting module is used to present the multicast receiving members corresponding to the IP addresses of the multicast receiving members on the leaf nodes of the multicast distribution tree topology diagram according to the IP addresses of the multicast receiving members corresponding to each switch.