Multicast network automatic test method and test system based on SDN (Software Defined Network)

Abstract

The invention relates to the technical field of multicast networks, and discloses an SDN-based multicast network automatic test method and test system, and the method comprises the steps that an automatic test terminal obtains a current to-be-tested multicast network scene, calls a preset API interface of an SDN controller, and sends a configuration command corresponding to the multicast network scene to the SDN controller; the SDN controller is used for updating the network configuration of the multicast network based on the configuration command; and the automatic test terminal pulls up the message sending end container and the message receiving end container in the preset server, and tests the multicast network scene according to the message sending end container and the message receiving end container. According to the method provided by the embodiment of the invention, a containerization technology is adopted to deploy the message sending end and the message receiving end, so that the resource waste caused by a large number of independent hosts required in a traditional test method is reduced, and the container can be dynamically created and destroyed according to needs, thereby optimizing the utilization rate of test resources.

Description

Technical Field

[0001] The present disclosure relates to the technical field of multicast networks, and in particular to an SDN-based multicast network automation testing method and testing system. Background Art

[0002] Multicast technology is a method of achieving point-to-multipoint data transmission in a network. By sending data from a single source to multiple receivers, it can save bandwidth and reduce network load.

[0003] In the related art, the automated networking test for multicast technology needs to cover multiple multicast network scenarios, and needs to build different networks and configure multiple message sending and receiving hosts for each scenario, resulting in low utilization of test equipment and host resources and a large waste of test resources. Therefore, in the automated networking test scenario, how to improve the utilization of test resources during the test process has become a problem that needs to be solved. Summary of the invention

[0004] In view of this, the present disclosure provides an SDN-based multicast network automated testing method and testing system to solve the problem of how to improve the test resource utilization rate during the testing process in an automated networking test scenario.

[0005] On the one hand, the present disclosure provides an SDN-based multicast network automation test method, which is applied to a test system. The test system includes: an SDN controller and an automated test terminal. The method includes: the automated test terminal obtains the current multicast network scenario to be tested, calls a preset API interface of the SDN controller, and sends a configuration command corresponding to the multicast network scenario to the SDN controller; the SDN controller updates the network configuration of the multicast network based on the configuration command; the automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, and tests the multicast network scenario according to the message sending end container and the message receiving end container.

[0006] On the other hand, the present disclosure further provides a test system, which includes an SDN controller and an automated test terminal, wherein: the automated test terminal is used to obtain the current multicast network scenario to be tested, call the preset API interface of the SDN controller, and send a configuration command corresponding to the multicast network scenario to the SDN controller; the SDN controller is used to update the network configuration of the multicast network based on the configuration command; the automated test terminal is used to pull up a message sending end container and a message receiving end container in a preset server, and test the multicast network scenario according to the message sending end container and the message receiving end container.

[0007] On the other hand, the present disclosure further provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to enable a computer to implement the above-mentioned SDN-based multicast network automatic testing method.

[0008] Another aspect of the present disclosure further provides a computer program product, including computer instructions, which are used to enable a computer to execute the above-mentioned SDN-based multicast network automatic testing method.

[0009] Through the SDN-based multicast network automation testing method and testing system of the above-mentioned embodiments of the present invention, containerization technology is used to deploy the message sender and receiver, which reduces the resource waste of a large number of independent hosts required in traditional testing methods. Containers can be dynamically created and destroyed as needed, thereby optimizing the utilization rate of test resources.

[0010] In addition, the automated test terminal calls the preset API interface to control the SDN controller and automatically completes the configuration of the multicast network without manual intervention, saving a lot of manual operation time and improving test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1a An exemplary schematic diagram showing the architecture of a test system applied to an SDN-based multicast network automation test method according to an embodiment of the present disclosure;

[0013] Figure 1b It is a flow chart of an SDN-based multicast network automation testing method provided by an embodiment of the present disclosure;

[0014] Figure 2 A schematic diagram of preset switch configuration in an SDN-based multicast network automation testing method according to an embodiment of the present disclosure is shown;

[0015] Figure 3 A specific flow chart of another SDN-based multicast network automation testing method according to an embodiment of the present disclosure is shown;

[0016] Figure 4 is a structural schematic diagram of another test system provided by an embodiment of the present disclosure;

[0017] Figure 5It is a structural diagram of another test system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0018] Multicast is a point-to-multipoint data transmission technology. Compared with unicast and broadcast, multicast can effectively solve the problem of multiple receivers sharing the same data source. Through multicast technology, a single data source only needs to send one copy of data, and multiple receivers share the data, which significantly saves network bandwidth and reduces network load.

[0019] Software Defined Networking (SDN) is a network architecture that achieves flexible and centralized network control by separating the control plane from the data plane in traditional network devices. SDN makes network configuration, management, and optimization more efficient. OpenFlow, the core technology of SDN, provides precise control over network traffic, making network management more intelligent and enabling on-demand traffic allocation, dynamic adjustment, and fault repair.

[0020] In the related art, the automated networking test for multicast technology needs to cover multiple multicast network scenarios, and needs to build a different network and configure multiple message sending and receiving hosts for each scenario.

[0021] The following problems may exist in the related technology:

[0022] 1. The relevant technology requires an independent network environment to be built for each test scenario, and each scenario requires an independent message sending and receiving host, resulting in a large waste of physical equipment and network resources.

[0023] 2. It is difficult for related technologies to automatically generate, record and compare test results after testing, and it is impossible to achieve efficient test result backtracking and historical data analysis.

[0024] 3. Each switching and configuration of the test scenario may require manual intervention, which is cumbersome and error-prone.

[0025] To solve the above problems, various embodiments of the present disclosure provide an SDN-based multicast network automation testing method, which is applied to a test system. The test system includes: an SDN controller and an automated test terminal. The method includes: the automated test terminal obtains the current multicast network scenario to be tested, calls a preset API interface of the SDN controller, and sends a configuration command corresponding to the multicast network scenario to the SDN controller; the SDN controller updates the network configuration of the multicast network based on the configuration command; the automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, and tests the multicast network scenario according to the message sending end container and the message receiving end container.

[0026] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0027] Please refer to Figure 1a , Figure 1a FIG. 1 is an exemplary schematic diagram showing the architecture of a test system used in an SDN-based multicast network automation test method according to an embodiment of the present disclosure. Figure 1a As shown, the test system may include: an SDN controller and an automated test terminal.

[0028] like Figure 1a As shown, the SDN controller can be the core component in the SDN architecture, responsible for centralized control and management of data flows and network devices in the network. The SDN controller can separate the control plane of the network (i.e., network decision-making and policy formulation) from the data plane (i.e., actual data forwarding operations), thereby achieving centralized management and flexible configuration of network traffic. For example, SDN controllers can include but are not limited to: OpenDaylight, Floodlight.

[0029] The automated test terminal may refer to a computer device or terminal used to perform automated networking tests. The purpose of the automated test terminal may be to reduce manual intervention and improve test efficiency in an automated manner.

[0030] The components of the automated test terminal may include at least one of the following: hardware equipment, software, and a communication interface.

[0031] Further references Figure 1b , Figure 1b This is a flow chart of an SDN-based multicast network automation testing method provided by the present disclosure, which is applied to the above Figure 1a The test system shown in the figure may include the following steps:

[0032] Step S101: The automated test terminal obtains the current multicast network scenario to be tested, calls a preset API interface of the SDN controller, and sends a configuration command corresponding to the multicast network scenario to the SDN controller.

[0033] In this embodiment, the multicast network scenario may refer to a network topology, routing protocol, multicast group member configuration, and related network device parameters configured according to specific requirements in a multicast network environment.

[0034] The automated test terminal obtains the current multicast network scenario to be tested, which may include but is not limited to: the automated test terminal reads a preset configuration file, and the automated test terminal obtains user input information.

[0035] The preset API interface of the SDN controller may refer to an interface predefined in the SDN controller for managing and configuring network devices, wherein the network devices may include but are not limited to: switches, routers, and hosts.

[0036] As an example, the preset API interface may include at least one of the following: a network topology management interface, a routing configuration interface, and a multicast group configuration interface.

[0037] The configuration commands sent by the automated test terminal to the SDN controller can be network configuration instructions for configuring and managing multicast traffic transmission in the network. Based on the configuration commands, it is possible to control how network devices in the SDN network process and forward multicast traffic and adapt to different multicast scenarios.

[0038] Step S102: The SDN controller updates the network configuration of the multicast network based on the configuration command.

[0039] In this embodiment, the SDN controller updates the network configuration of the multicast network based on the configuration command, which may include: the SDN controller updates the multicast routing protocol based on the configuration command, manages the multicast group members, and configures the network topology and ports.

[0040] Step S103: The automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, and tests the multicast network scenario according to the message sending end container and the message receiving end container.

[0041] In this embodiment, the automated test terminal starts a container for sending multicast messages and a container for receiving multicast messages in a preset server.

[0042] A preset application is configured in the message sending end container, and multicast traffic is generated and sent based on the preset application. A preset application is configured in the message receiving end container, and multicast traffic is received based on the preset application. Here, the preset application may include but is not limited to: iperf.

[0043] Furthermore, the automated test terminal determines whether the message receiving end container completely receives the multicast message sent by the message sending end container during the process of testing the multicast network scenario.

[0044] Furthermore, the automated test terminal can also monitor the message receiving status of the message receiving end container to obtain data such as the delay and packet loss rate of the multicast message during the transmission process.

[0045] In the SDN-based multicast network automated testing method and testing system of the above-mentioned embodiments of the present disclosure, the containerization technology is used to deploy the message sender and receiver, which reduces the resource waste of a large number of independent hosts required in the traditional testing method. The container can be dynamically created and destroyed as needed, thereby optimizing the utilization rate of the test resources. The automated test terminal calls the preset API interface to control the SDN controller, automatically completes the configuration of the multicast network, and does not require manual intervention, which saves a lot of manual operation time and improves the test efficiency.

[0046] In a possible implementation of step S102, the SDN controller updates the network configuration of the multicast network based on the configuration command, including:

[0047] The SDN controller, based on the configuration command, includes at least one preset switch in the multicast network into the management scope, and performs preset logical connection and preset BGP neighbor configuration on the at least one preset switch.

[0048] In this embodiment, the preset switches may include: leaf, spine, and border.

[0049] Among them, the leaf switch can be an access switch, responsible for data forwarding, forwarding traffic from terminal devices or servers to the spine switch, or transmitting it back from the spine switch to the terminal device. The spine switch can be a core switch, responsible for connecting all leaf switches and forwarding traffic through these connections. The border switch can be a boundary switch, responsible for routing and forwarding between the data center network and the external network.

[0050] The SDN controller, based on the configuration command, includes at least one preset switch in the multicast network into the management scope, which may include: the SDN controller, based on the control protocol, includes the leaf switch, spine switch and border switch into the management scope, obtains the status, port, routing information and other data of each switch, and dynamically configures the switch based on the above data.

[0051] The control protocol may refer to OpenFlow.

[0052] The SDN controller performs preset logical connection on at least one preset switch, which may include: the SDN controller generates logical connection information between switches according to configuration commands, defines flow table rules of switches, and defines logical connections between switch ports according to flow table configuration protocols.

[0053] The SDN controller performs preset BGP neighbor configuration on at least one preset switch, which may include:

[0054] The SDN controller configures the neighbor relationship of each switch through the Border Gateway Protocol (BGP).

[0055] The neighbor relationship may refer to a direct communication link established between two routers or switches so as to exchange routing information with each other.

[0056] In the SDN-based multicast network automated testing method and testing system of the above-mentioned embodiment of the present disclosure, the SDN controller receives configuration commands and updates the network configuration of the multicast network, so as to realize dynamic configuration and real-time adjustment of the multicast network. The controller can flexibly configure the logical connection and BGP neighbor relationship between switches according to different requirements to ensure the efficient operation and topology adjustability of the multicast network. The SDN controller can automatically adjust the configuration and routing strategy of the switch according to factors such as the current network traffic and topology changes, so as to avoid waste of resources and improve the utilization of network bandwidth.

[0057] In a possible implementation of the above step S103, the automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, including:

[0058] The automated test terminal uses a preset container management tool to create and start a message sending end container and a message receiving end container in a preset server; wherein at least one different network card is bound to the message receiving end container.

[0059] In this embodiment, the preset container management tool may include but is not limited to: Docker.

[0060] The automated test terminal uses a preset container management tool to create and start a message sending end container in a preset server, which can include: the automated test terminal uses Docker to create a message sending end container in a preset server, configure a multicast target address for the message sending end container and start it.

[0061] By binding at least one network card to the preset server, you can ensure that you can receive multicast messages from different physical or virtual networks. With at least one network card, you can simulate multiple network interfaces in the same container, or simulate multiple receiving interfaces in different containers.

[0062] In the SDN-based multicast network automation test method and test system of the above-mentioned embodiment of the present disclosure, the message receiving container is bound to multiple network cards, which can receive multicast messages from different networks, thereby simulating a complex multi-network environment and effectively enhancing the authenticity and comprehensiveness of the test. Through containerization technology, the functions of network devices are virtualized into containers, which can not only efficiently reuse server hardware resources, but also avoid the repeated construction and management of traditional physical devices, thereby improving resource utilization.

[0063] In a possible implementation of the above step S101, the automated test terminal tests the multicast network scenario according to the message sending end container and the message receiving end container, based on the following steps:

[0064] The automated test terminal enables the message sending end container to send the original multicast message to the message receiving end container;

[0065] The automated test terminal obtains the message information received by the message receiving end container, compares the message information with the original multicast message, and generates a test report according to the comparison result.

[0066] As an example, the automated test terminal starts a message sending container and a message receiving container through Docker, instructs the message sending container to send an original multicast message to a specified multicast address, and enables the message receiving container to listen to and receive message information from the message sending container.

[0067] The original multicast message may contain a specific data payload for testing the connectivity and data transmission capability of the multicast network.

[0068] The automated test terminal compares the message information with the original multicast message, which may include: determining whether the message information is complete and determining whether the message information is correct.

[0069] Furthermore, the comparison results may also include but are not limited to: the number of received message information, packet loss rate, message reception delay, message sequence, etc.

[0070] The automated test terminal generates a test report based on the comparison results. The test report may include but is not limited to: test scenario description, message reception and transmission status, comparison results, and test result summary.

[0071] In the SDN-based multicast network automated testing method and testing system of the above-mentioned embodiments of the present disclosure, all test results are automatically recorded to ensure data traceability and provide support for network troubleshooting and optimization. Through containerization technology, the test environment can be quickly deployed and destroyed on the server, avoiding the waste of physical device resources.

[0072] In a possible implementation of the above embodiment, the method further includes:

[0073] The automated test terminal obtains a next multicast network scenario to be tested, and determines whether to retain or delete a container in a current preset server based on the next multicast network scenario to be tested.

[0074] In this embodiment, the automated test terminal obtains the next multicast network scenario to be tested, parses the relevant configuration of the network scenario, and determines the container information that needs to be retained or deleted;

[0075] Based on the current scenario and the status of existing containers on the preset server, determine whether to delete the existing containers or keep them;

[0076] If it is determined that the current container is not needed or the container configuration does not match the scenario to be tested, the automated test terminal will use Docker to delete the no longer needed container;

[0077] If it is determined that the current container is suitable for the scenario to be tested, the automated test terminal retains the container and performs configuration updates.

[0078] In the SDN-based multicast network automated testing method and testing system of the above embodiments of the present disclosure, the automated testing terminal flexibly determines whether to retain, delete or update the existing container according to each multicast network scenario to be tested. By using the container management tool, the automated testing process can be quickly executed while maintaining efficient resource utilization, avoiding unnecessary resource waste and misconfiguration.

[0079] In a specific embodiment, Figure 2 A schematic diagram of a preset switch configuration in an SDN-based multicast network automation test method according to an embodiment of the present disclosure is shown, wherein:

[0080] The spine switch is connected to the border switch, and the spine switch obtains the traffic exchange of the external network through the border switch. The spine switch is also connected to multiple leaf switches, and the spine switch can realize traffic forwarding between multiple leaf switches. In the terminal device of the leaf switch, the traffic reaches the connected preset server, which receives and processes the business data.

[0081] In a specific embodiment, Figure 3 A specific flow chart of another SDN-based multicast network automated testing method according to an embodiment of the present disclosure is shown, and the figure includes the following steps:

[0082] Step S301, obtaining the multicast network scenario to be tested;

[0083] Here, the automated test terminal obtains the current multicast network scenario to be tested;

[0084] Step S302, calling the SDN controller to issue a configuration command;

[0085] Here, the automated test terminal calls the preset API interface of the SDN controller and sends the configuration command corresponding to the multicast network scenario to the SDN controller;

[0086] Step S303, pull up the corresponding message sending end container and receiving end container;

[0087] Here, the automated test terminal uses Docker to pull up the message sender container and the message receiver container in the preset server;

[0088] Step S304, recording the message information received by the receiving end container and generating a test report;

[0089] Here, the automated test terminal enables the message sending end container to send the original multicast message to the message receiving end container, obtains the message information received by the message receiving end container, compares the message information with the original multicast message, and generates a test report according to the comparison result;

[0090] Step S305, determining whether to retain or delete the container based on the next multicast network scenario;

[0091] Here, the next multicast network scenario to be tested is obtained, and based on the next multicast network scenario to be tested, it is determined whether to retain or delete the container in the current preset server;

[0092] Step S306, determine whether to end the current multicast network scenario; if so, end the process; if not, return to step S301.

[0093] In one embodiment, a test system 40 is provided, and the test system 40 corresponds to the SDN-based multicast network automation test method in the above embodiment. Figure 4 As shown, the test system 40 includes an automated test terminal 401 and an SDN controller 402, wherein each functional module is described in detail as follows:

[0094] The automated test terminal 401 is used to obtain the current multicast network scenario to be tested, call the preset API interface of the SDN controller, and send a configuration command corresponding to the multicast network scenario to the SDN controller;

[0095] The SDN controller 402 is used to update the network configuration of the multicast network based on the configuration command;

[0096] The automated test terminal 401 is used to pull up a message sending end container and a message receiving end container in a preset server, and test the multicast network scenario according to the message sending end container and the message receiving end container.

[0097] In one embodiment, the SDN controller 402 is used to include at least one preset switch in the multicast network into the management scope based on the configuration command, and perform preset logical connection and preset BGP neighbor configuration on the at least one preset switch.

[0098] In one embodiment, the automated test terminal 401 is used to create and start a message sending end container and a message receiving end container in a preset server by using a preset container management tool; wherein at least one different network card is bound to the message receiving end container.

[0099] In one embodiment, the automated test terminal 401 is used to enable the message sending end container to send the original multicast message to the message receiving end container;

[0100] The message information received by the message receiving end container is obtained, the message information is compared with the original multicast message, and a test report is generated according to the comparison result.

[0101] In one embodiment, the automated test terminal 401 is further configured to obtain a next multicast network scenario to be tested, and determine whether to retain or delete a container in the current preset server based on the next multicast network scenario to be tested.

[0102] It should be noted that: when the test system provided in the above embodiment implements the corresponding SDN-based multicast network automation test method, only the division of the above program modules is used as an example. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the above system can be divided into different program modules to complete all or part of the above-described processing. Figure 1b The embodiments of the method shown belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0103] The present disclosure also provides a computer device having the above Figure 4 The test system shown.

[0104] See also Figure 5 , Figure 5 is a structural diagram of another test system provided by an embodiment of the present disclosure, such as Figure 5As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 5 A processor 10 is taken as an example.

[0105] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0106] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0107] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0108] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0109] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0110] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0111] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0112] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0113] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0114] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. An SDN-based multicast network automated testing method, characterized in that: Applied to a test system, the test system includes: an SDN controller and an automated test terminal, the method includes: The automated test terminal obtains the current multicast network scenario to be tested, calls a preset API interface of the SDN controller, and sends a configuration command corresponding to the multicast network scenario to the SDN controller; The SDN controller updates the network configuration of the multicast network based on the configuration command; The automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, and tests the multicast network scenario according to the message sending end container and the message receiving end container.

2. The method according to claim 1, characterized in that: The SDN controller updates the network configuration of the multicast network based on the configuration command, including: The SDN controller, based on the configuration command, includes at least one preset switch in the multicast network into the management scope, and performs preset logical connection and preset BGP neighbor configuration on the at least one preset switch.

3. The method according to claim 1, characterized in that The automated test terminal pulls up a message sending end container and a message receiving end container in a preset server, including: The automated test terminal uses a preset container management tool to create and start a message sending end container and a message receiving end container in a preset server; wherein at least one different network card is bound to the message receiving end container.

4. The method according to claim 3, characterized in that The automated test terminal tests the multicast network scenario according to the message sending end container and the message receiving end container, based on the following steps: The automated test terminal enables the message sending end container to send the original multicast message to the message receiving end container; The automated test terminal obtains the message information received by the message receiving end container, compares the message information with the original multicast message, and generates a test report according to the comparison result.

5. The method according to claim 4, characterized in that The method further comprises: The automated test terminal obtains a next multicast network scenario to be tested, and determines whether to retain or delete a container in a current preset server based on the next multicast network scenario to be tested.

6. A testing system, characterized in that: The test system includes an SDN controller and an automated test terminal, wherein: The automated test terminal is used to obtain the current multicast network scenario to be tested, call the preset API interface of the SDN controller, and send a configuration command corresponding to the multicast network scenario to the SDN controller; The SDN controller is used to update the network configuration of the multicast network based on the configuration command; The automated test terminal is used to pull up a message sending end container and a message receiving end container in a preset server, and test the multicast network scenario according to the message sending end container and the message receiving end container.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the SDN-based multicast network automatic testing method described in claims 1-5.

8. A computer program product, characterized in that It includes computer instructions, and the computer instructions are used to enable a computer to execute the SDN-based multicast network automatic testing method described in any one of claims 1-5.

Images