CN109921960B - IDC machine room network anomaly testing method and device - Google Patents
IDC machine room network anomaly testing method and device Download PDFInfo
- Publication number
- CN109921960B CN109921960B CN201910239356.3A CN201910239356A CN109921960B CN 109921960 B CN109921960 B CN 109921960B CN 201910239356 A CN201910239356 A CN 201910239356A CN 109921960 B CN109921960 B CN 109921960B
- Authority
- CN
- China
- Prior art keywords
- flow
- test
- abnormal event
- target
- executed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 209
- 230000002159 abnormal effect Effects 0.000 claims abstract description 152
- 238000012544 monitoring process Methods 0.000 claims abstract description 30
- 238000000034 method Methods 0.000 claims abstract description 28
- 238000010276 construction Methods 0.000 claims abstract description 14
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 5
- 230000005540 biological transmission Effects 0.000 claims description 2
- 230000006870 function Effects 0.000 description 12
- 230000005856 abnormality Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000013100 final test Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for testing network abnormity of an IDC machine room, wherein the method comprises the following steps: analyzing a preset flow construction file to obtain target flow information, equipment information and port information; generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed; under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information; monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period; and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet. The invention solves the problem of poor reliability of the IDC machine room network abnormity test.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a method and a device for testing network abnormity of an IDC machine room.
Background
The robustness of the network is mainly realized by the backup of the equipment, namely, a group of equipment on the same flow path are mutually backed up, a single piece of equipment or a single link fails, the flow is switched to the normal link of the same group, and the robustness test or abnormal test of the network is that the affected degree of the flow is observed by the abnormal simulation of the link or the equipment. In the prior art, network anomaly testing mainly depends on manual flow deployment and manual anomaly manufacturing, and due to the fact that an Internet Data Center (IDC) is large in network scale and large in workload of network anomaly testing, and a bug is prone to being missed by means of manual testing. Therefore, the reliability of the prior art for the IDC machine room network abnormity test is poor.
Disclosure of Invention
The embodiment of the invention provides a method and a device for testing the network abnormity of an IDC machine room, which are used for solving the problem of poor reliability of the network abnormity test of the IDC machine room.
In a first aspect, an embodiment of the present invention provides a method for testing an IDC room network anomaly, which is characterized by including:
analyzing a preset flow construction file to obtain target flow information, equipment information and port information;
generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed;
under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information;
monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period;
and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet.
In a second aspect, an embodiment of the present invention further provides an IDC room network anomaly testing apparatus, which is characterized by including:
the control module is used for analyzing a preset flow construction file to obtain target flow information, equipment information and port information;
the abnormal event generating module is used for generating an abnormal event sequence according to the equipment information and the port information, and the abnormal event sequence comprises at least one abnormal event to be executed;
the flow generation module is used for starting ping operation and constructing test flow according to the target flow information under the condition that the abnormal event sequence is not empty;
the monitoring module is used for monitoring the test flow and the ping packet in real time;
the abnormal event execution module is used for executing the target abnormal event to be executed in the abnormal event sequence after the ping operation is started for a preset time period;
and the control module is further used for obtaining a test result of the target to-be-executed abnormal event according to the test flow and the monitoring result of the ping packet after the target to-be-executed abnormal event is finished.
The embodiment of the invention obtains target flow information, equipment information and port information by analyzing a preset flow construction file; generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed; under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information; monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period; and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet. Therefore, the network abnormity test can be automatically realized, and the reliability of the network abnormity test of the IDC machine room can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a flowchart of an IDC room network anomaly testing method provided in an embodiment of the present invention;
fig. 2 is a schematic diagram of a device and a port through which target traffic information passes in the IDC room network anomaly testing method provided in the embodiment of the present invention;
fig. 3 is a schematic diagram of a unit of a flow configuration context in the IDC room network anomaly testing method according to the embodiment of the present invention;
fig. 4 is a schematic diagram of an abnormal event sequence in the IDC room network abnormality testing method provided in the embodiment of the present invention;
fig. 5 is a schematic diagram of a test result output in the IDC room network anomaly test method provided in the embodiment of the present invention;
fig. 6 is a flowchart illustrating a method for testing an IDC room network anomaly according to an embodiment of the present invention;
fig. 7 is one of the structural diagrams of the IDC room network anomaly testing apparatus provided in the embodiment of the present invention;
fig. 8 is a second structural diagram of an IDC room network anomaly testing apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart of an IDC room network anomaly testing method provided by an embodiment of the present invention, and as shown in fig. 1, the method includes the following steps:
in the embodiment of the present invention, the traffic configuration file describes a set of devices and interfaces through which a test traffic may pass, and as shown in fig. 2, there may be n types of traffic paths from device a to device B. The purpose of the exception test is to traverse the devices and ports on the n possible paths and test the influence of the exception condition of each device and port on the traffic. A plurality of devices form a backup group on each level node of the device, the purpose is that when a single device is abnormal, the flow has an alternative path, and the abnormal test is to simulate the abnormality to check the robustness of the network.
Specifically, the form of the flow configuration file may be set according to actual needs, and as shown in fig. 3, a schematic unit diagram of the flow configuration file is given. In fig. 3, the target traffic information specifically includes IP addresses corresponding to the starting and ending devices, and the IP address corresponding to the starting device may be specifically represented as "start: 10.30.105.80 "; the IP address corresponding to the terminating device may be specifically denoted as "end: 10.30.104.79' of the product. The flow construction file also comprises path equipment of target flow information, and equipment information is obtained according to the path equipment; specifically, as shown in fig. 3, the target traffic information may be determined by a traffic path device, and the path device may include multiple devices, where & & connection in a device group indicates that the operating mode is load sharing (working simultaneously and sharing traffic), and | | | connection indicates that the operating mode is a master/standby mode (traffic passes through master, and standby only does hot standby and does not work). The port information represents a port corresponding to each device; as shown in fig. 3, a path port representation is employed in the traffic construction file.
102, generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed;
the number of the to-be-executed exception events may be set according to actual needs, as shown in fig. 4, in this embodiment, the number of the to-be-executed exception events may be three, and the to-be-executed exception events may have a sequential execution order. In fig. 4, the to-be-executed exception events in the exception event sequence are an to-be-executed exception event 1, an to-be-executed exception event 2, and an to-be-executed exception event 3, where the to-be-executed exception event may include an object of an operation, an event, and a delay time in an operation process, and the insertion of the delay time is mainly used to ensure that the exception event completely occurs. The abnormal operation object can be a single port of the equipment or a group of equipment. In a device group with more than two devices, a plurality of device exceptions need to be inserted, and only one abnormal operation scene of normal operation of the device is reserved.
Specifically, specific contents of the exception event to be executed may be set according to actual needs, and referring to fig. 4, in this embodiment, the exception event 1 to be executed may specifically be: performing exception on the port 5 of the device C (the specific exception operation comprises closing operation, waiting for 5 seconds, activating operation, and waiting for 5 seconds); the exception event 2 to be executed may be: performing exception on the equipment H, the equipment I and the equipment J (the specific exception operation comprises restarting operation and waiting for 15 minutes); the exception event 3 to be executed may be: and (4) performing exception on the device M and the device L (main/standby switching operation, waiting for 10 seconds, main/standby switching operation, waiting for 10 seconds).
103, starting ping operation and constructing test flow according to the target flow information under the condition that the abnormal event sequence is not empty;
in this embodiment, the exception sequence being empty indicates that there is no exception to be executed, and the exception sequence not being empty indicates that there is an exception to be executed. Specifically, the to-be-executed abnormal event in the abnormal event sequence may be read first, and whether the to-be-executed abnormal event exists in the abnormal event sequence is determined; when the abnormal event sequence has an abnormal event to be executed, reading the abnormal event to be executed which is arranged at the front as a target abnormal event to be executed according to the sequence position of the abnormal event to be executed in the sequence order of the abnormal event sequence. At the same time, a ping operation will be initiated and the test traffic described above will be generated.
It should be understood that the above test traffic may include a plurality of traffic, and specifically, the step 103 may include:
and constructing test flow of a plurality of different paths from the source IP to the destination IP according to the source IP and the destination IP in the target flow information.
In this embodiment, the test traffic of different paths may be obtained by changing the original port and the target port. Further, in an alternative embodiment, the test traffic may be Transmission Control Protocol (TCP) traffic constructed using Secure Copy (scp) or iperf tools.
in this embodiment, after the ping operation is started, the test flow and the ping packet are monitored, and after the ping operation reaches the time length of the preset time period, the abnormal operation corresponding to the target to-be-executed abnormal event is started to be executed. The time length of the preset time period can be set according to actual needs, and can be 5 seconds, for example.
And 105, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet after the target abnormal event to be executed is ended.
In the embodiment of the present invention, the ping operation may be used to record the traffic switching time of the test traffic when the target to-be-executed abnormal event occurs, where the test traffic is used to record whether the network has a robustness problem when the target to-be-executed abnormal event occurs. For example, it may be determined that there is a problem in the network robustness by monitoring whether the test traffic has a broken link, when the test traffic has a broken link condition.
The embodiment of the invention obtains target flow information, equipment information and port information by analyzing a preset flow construction file; generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed; under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information; monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period; and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet. Therefore, the network abnormity test can be automatically realized, and the reliability of the network abnormity test of the IDC machine room can be improved.
Further, based on the foregoing embodiment, in this embodiment, the obtaining, according to the test traffic and the monitoring result of the ping packet, the test result of the target to-be-executed exception event includes:
judging whether the test flow is normal or not;
stopping ping operation when the test flow is normal;
counting the flow bandwidth of the test flow and the ping packet data of the ping operation;
when the traffic bandwidth after the test traffic switching is smaller than the traffic bandwidth before the test traffic switching, outputting a first abnormal warning and generating first abnormal data;
and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
In the embodiment of the present invention, the standard for judging whether the test flow is normal is as follows: and testing whether the traffic is broken. When the test flow is broken, the test flow is abnormal; and if the test flow is not broken, indicating that the test flow is normal.
Specifically, the time for switching the traffic may be determined according to the packet loss number of the ping packet in the data of the ping packet. The traffic data may determine whether the traffic is normal or abnormal.
It should be noted that after the test of the target to-be-executed exception event is completed, the next to-be-executed exception event is returned to be read again until the exception event sequence is empty. After the abnormal event sequence is empty, a final test result can be output according to the test result of each target to-be-executed abnormal event. The final test result may be a summary display of the test results of each target to-be-executed exception event, where the summary display may be: test flow + test result. For example, the test result for test flow 1 may appear as: the flow switching time of the event 1 is 50ms, the flow switching time of the event 2 is cut off, the test is terminated, and the like.
Further, the traffic configuration file may include a plurality of target traffic information, and in an optional embodiment, each target traffic information may be tested, and a final output test result is shown in fig. 5.
For a better understanding of the present invention, reference is made to fig. 6, which is a detailed description of the overall cycle.
Step 1: the flow construction file is read. After reading the traffic construction file, the traffic construction file can be analyzed to obtain target traffic information, device information and port information
Step 2: an abnormal event sequence is generated. Specifically, the abnormal event sequence may be generated according to the device information and the port information.
And step 3: and judging whether the abnormal event sequence is empty or not. If yes, the flow is ended, otherwise, step 4 is executed.
And 4, step 4: and reading one abnormal event in the abnormal event sequence, wherein the read abnormal event is the target to-be-executed abnormal event in the embodiment.
And 5: and generating N TCP flows. TCP traffic for a plurality of different paths from the source IP to the destination IP may be constructed according to the source IP and the destination IP in the destination traffic information.
Step 6: a ping operation is performed.
And 7: and monitoring the flow and the ping packet.
And 8: an exception event is made. Specifically, an exception is made by an exception event that performs a read.
And step 9: waiting for a specified time. The time length of the designated time can be set according to actual needs, and all the devices can be enabled to be recovered to a normal working state only after the execution of the abnormal event is finished.
Step 10: and (6) counting. Specifically, the statistics refers to statistics of the test flow and the monitoring data of the ping packet to obtain a test result. For example, in an alternative embodiment, the following steps may be included:
judging whether the test flow is normal or not;
stopping ping operation when the test flow is normal;
counting the flow bandwidth of the test flow and the ping packet data of the ping operation;
when the traffic bandwidth after the test traffic switching is smaller than the traffic bandwidth before the test traffic switching, outputting a first abnormal warning and generating first abnormal data;
and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
And stopping the flow and ping operation after the statistics is finished, and continuously judging whether the abnormal event sequence is empty or not.
It should be noted that, various optional implementations described in the embodiments of the present invention may be implemented in combination with each other or implemented separately, and the embodiments of the present invention are not limited thereto.
Referring to fig. 7, fig. 7 is a structural diagram of an IDC room network anomaly testing apparatus according to an embodiment of the present invention, and as shown in fig. 7, an IDC room network anomaly testing apparatus 700 includes:
the control module 701 is configured to analyze a preset traffic configuration file to obtain target traffic information, device information, and port information;
an abnormal event generating module 702, configured to generate an abnormal event sequence according to the device information and the port information, where the abnormal event sequence includes at least one abnormal event to be executed;
a traffic generation module 703, configured to start ping operation and construct a test traffic according to the target traffic information when the abnormal event sequence is not null;
a monitoring module 704, configured to monitor the test traffic and the ping packet in real time;
an abnormal event executing module 705, configured to execute a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period;
the control module 701 is further configured to obtain a test result of the target to-be-executed abnormal event according to the test flow and a monitoring result of the ping packet after the target to-be-executed abnormal event is ended.
Optionally, the traffic generation module 703 is specifically configured to: and constructing test flow of a plurality of different paths from the source IP to the destination IP according to the source IP and the destination IP in the target flow information.
Optionally, the control module 101 includes:
the judging unit is used for judging whether the test flow is normal or not;
the control unit is used for stopping the ping operation when the test flow is normal;
a counting unit, configured to count a traffic bandwidth of the test traffic and ping packet data of the ping operation;
the processing unit is used for outputting a first abnormal warning and generating first abnormal data when the flow bandwidth after the test flow switching is smaller than the flow bandwidth before the test flow switching; and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
Optionally, the control module 701 is further configured to: and when the test flow is abnormal, outputting a second abnormal warning and generating second abnormal data.
Optionally, the test traffic is TCP traffic constructed by using a secure copy scp tool or an iperf tool.
The IDC room network anomaly testing device provided by the embodiment of the invention can realize each process realized by the IDC room network anomaly testing device in the method embodiments of fig. 1 to 6, and is not repeated here for avoiding repetition.
Fig. 8 is a schematic diagram of a hardware structure of an IDC room network anomaly testing apparatus for implementing various embodiments of the present invention.
The IDC computer room network anomaly testing device 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, a processor 810, and a power supply 811. Those skilled in the art will appreciate that the structure of the IDC room network anomaly testing apparatus shown in fig. 8 does not constitute a limitation of the IDC room network anomaly testing apparatus, which may include more or fewer components than those shown, or some components in combination, or a different arrangement of components. In the embodiment of the invention, the network anomaly testing device of the IDC machine room comprises but is not limited to a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.
The processor 810 is configured to parse a preset traffic configuration file to obtain target traffic information, device information, and port information; generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed; under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information; monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period; and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet.
Optionally, the processor 810 is specifically configured to construct test traffic of a plurality of different paths from the source IP to the destination IP according to the source IP and the destination IP in the target traffic information.
Optionally, the processor 810 is specifically configured to:
judging whether the test flow is normal or not;
stopping ping operation when the test flow is normal;
counting the flow bandwidth of the test flow and the ping packet data of the ping operation;
when the traffic bandwidth after the test traffic switching is smaller than the traffic bandwidth before the test traffic switching, outputting a first abnormal warning and generating first abnormal data;
and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
Optionally, the processor 810 is further configured to: and when the test flow is abnormal, outputting a second abnormal warning and generating second abnormal data.
Optionally, the test traffic is TCP traffic constructed by using a secure copy scp tool or an iperf tool.
The embodiment of the invention obtains target flow information, equipment information and port information by analyzing a preset flow construction file; generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed; under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information; monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period; and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet. Therefore, the network abnormity test can be automatically realized, and the reliability of the network abnormity test of the IDC machine room can be improved.
It should be understood that, in the embodiment of the present invention, the radio frequency unit 801 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 810; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. Further, the radio frequency unit 801 can also communicate with a network and other devices through a wireless communication system.
The IDC computer room network anomaly testing device provides wireless broadband internet access for users through the network module 802, such as helping users receive and send e-mails, browse webpages, access streaming media and the like.
The audio output unit 803 may convert audio data received by the radio frequency unit 801 or the network module 802 or stored in the memory 809 into an audio signal and output as sound. Also, the audio output unit 803 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the IDC room network abnormality testing apparatus 800. The audio output unit 803 includes a speaker, a buzzer, a receiver, and the like.
The input unit 804 is used for receiving an audio or video signal. The input Unit 804 may include a Graphics Processing Unit (GPU) 8041 and a microphone 8042, and the Graphics processor 8041 processes image data of a still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 806. The image frames processed by the graphics processor 8041 may be stored in the memory 809 (or other storage medium) or transmitted via the radio frequency unit 801 or the network module 802. The microphone 8042 can receive sound, and can process such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 801 in case of a phone call mode.
The IDC room network abnormality testing apparatus 800 further includes at least one sensor 805 such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 8061 according to the brightness of ambient light and a proximity sensor that can turn off the display panel 8061 and/or backlight when the IDC room network abnormality testing apparatus 800 moves to the ear. As one type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), can detect the magnitude and direction of gravity when stationary, and can be used for identifying the attitude of the IDC room network anomaly testing device (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration identification related functions (such as pedometer and tapping) and the like; the sensors 805 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.
The display unit 806 is used to display information input by the user or information provided to the user. The Display unit 806 may include a Display panel 8061, and the Display panel 8061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 807 may be used to receive inputted numerical or character information and generate key signal inputs related to user settings and function control of the IDC room network abnormality testing apparatus. Specifically, the user input unit 807 includes a touch panel 8071 and other input devices 8072. The touch panel 8071, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 8071 (e.g., operations by a user on or near the touch panel 8071 using a finger, a stylus, or any other suitable object or accessory). The touch panel 8071 may include two portions of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 810, receives a command from the processor 810, and executes the command. In addition, the touch panel 8071 can be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 8071, the user input unit 807 can include other input devices 8072. In particular, other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
Further, the touch panel 8071 can be overlaid on the display panel 8061, and when the touch panel 8071 detects a touch operation on or near the touch panel 8071, the touch operation is transmitted to the processor 810 to determine the type of the touch event, and then the processor 810 provides a corresponding visual output on the display panel 8061 according to the type of the touch event. Although in fig. 8, the touch panel 8071 and the display panel 8061 are two independent components to implement the input and output functions of the IDC computer room network abnormality testing apparatus, in some embodiments, the touch panel 8071 and the display panel 8061 may be integrated to implement the input and output functions of the IDC computer room network abnormality testing apparatus, which is not limited herein.
The interface unit 808 is an interface through which an external device is connected to the IDC room network abnormality testing apparatus 800. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 808 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the IDC room network anomaly testing device 800 or may be used to transmit data between the IDC room network anomaly testing device 800 and the external device.
The memory 809 may be used to store software programs as well as various data. The memory 809 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 809 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 810 is a control center of the IDC room network anomaly testing device, connects each part of the entire IDC room network anomaly testing device by using various interfaces and lines, and executes various functions and processes data of the IDC room network anomaly testing device by running or executing software programs and/or modules stored in the memory 809 and calling data stored in the memory 809, thereby integrally monitoring the IDC room network anomaly testing device. Processor 810 may include one or more processing units; preferably, the processor 810 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 810.
The IDC room network abnormality testing apparatus 800 may further include a power supply 811 (such as a battery) for supplying power to each component, and preferably, the power supply 811 may be logically connected to the processor 810 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.
In addition, the IDC engine room network anomaly testing apparatus 800 includes some functional modules that are not shown, and are not described herein again.
Preferably, an embodiment of the present invention further provides an IDC room network anomaly testing apparatus, including a processor 810, a memory 809, and a computer program stored in the memory 809 and capable of running on the processor 810, where the computer program, when executed by the processor 810, implements each process of the IDC room network anomaly testing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The embodiment of the invention also provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program realizes each process of the embodiment of the IDC room network anomaly testing method, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (12)
1. An IDC machine room network anomaly testing method is characterized by comprising the following steps:
analyzing a preset flow construction file to obtain target flow information, equipment information and port information, wherein the target flow information comprises a source IP and a target IP;
generating an abnormal event sequence according to the equipment information and the port information, wherein the abnormal event sequence comprises at least one abnormal event to be executed;
under the condition that the abnormal event sequence is not empty, starting ping operation and constructing test flow according to the target flow information;
monitoring the test flow and the ping packet in real time, and executing a target to-be-executed abnormal event in the abnormal event sequence after the ping operation is started for a preset time period;
and after the target abnormal event to be executed is finished, obtaining a test result of the target abnormal event to be executed according to the test flow and the monitoring result of the ping packet.
2. The method of claim 1, wherein the constructing test traffic from the target traffic information comprises:
and constructing test flow of a plurality of different paths from the source IP to the destination IP according to the source IP and the destination IP in the target flow information.
3. The method according to claim 1, wherein the obtaining a test result of the target exceptional event to be executed according to the test traffic and the monitoring result of the ping packet comprises:
judging whether the test flow is normal or not;
stopping ping operation when the test flow is normal;
counting the flow bandwidth of the test flow and the ping packet data of the ping operation;
when the traffic bandwidth after the test traffic switching is smaller than the traffic bandwidth before the test traffic switching, outputting a first abnormal warning and generating first abnormal data;
and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
4. The method of claim 3, wherein after determining whether the test traffic is normal, the method further comprises:
and when the test flow is abnormal, outputting a second abnormal warning and generating second abnormal data.
5. The method of claim 1, wherein the test traffic is Transmission Control Protocol (TCP) traffic constructed using a secure copy (scp) tool or an iperf tool.
6. The utility model provides an IDC computer lab network anomaly testing arrangement which characterized in that includes:
the control module is used for analyzing a preset flow construction file to obtain target flow information, equipment information and port information, wherein the target flow information comprises a source IP and a target IP;
the abnormal event generating module is used for generating an abnormal event sequence according to the equipment information and the port information, and the abnormal event sequence comprises at least one abnormal event to be executed;
the flow generation module is used for starting ping operation and constructing test flow according to the target flow information under the condition that the abnormal event sequence is not empty;
the monitoring module is used for monitoring the test flow and the ping packet in real time;
the abnormal event execution module is used for executing the target abnormal event to be executed in the abnormal event sequence after the ping operation is started for a preset time period;
and the control module is further used for obtaining a test result of the target to-be-executed abnormal event according to the test flow and the monitoring result of the ping packet after the target to-be-executed abnormal event is finished.
7. The IDC room network anomaly testing device of claim 6, wherein the traffic generation module is specifically configured to: and constructing test flow of a plurality of different paths from the source IP to the destination IP according to the source IP and the destination IP in the target flow information.
8. The IDC room network anomaly testing device of claim 6, wherein said control module comprises:
the judging unit is used for judging whether the test flow is normal or not;
the control unit is used for stopping the ping operation when the test flow is normal;
a counting unit, configured to count a traffic bandwidth of the test traffic and ping packet data of the ping operation;
the processing unit is used for outputting a first abnormal warning and generating first abnormal data when the flow bandwidth after the test flow switching is smaller than the flow bandwidth before the test flow switching; and when the flow bandwidth after the test flow switching is larger than or equal to the flow bandwidth before the test flow switching, recording and displaying the ping packet data and the flow data of the test flow.
9. The IDC room network anomaly testing device of claim 8, wherein the control module is further configured to: and when the test flow is abnormal, outputting a second abnormal warning and generating second abnormal data.
10. The IDC room network anomaly testing device of claim 6, wherein the test traffic is TCP traffic constructed using a secure copy scp tool or an iperf tool.
11. An IDC room network anomaly testing device, which is characterized by comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, wherein the computer program is executed by the processor to realize the steps of the IDC room network anomaly testing method according to any one of claims 1 to 5.
12. A computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when being executed by a processor, realizes the steps of the IDC room network anomaly testing method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910239356.3A CN109921960B (en) | 2019-03-27 | 2019-03-27 | IDC machine room network anomaly testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910239356.3A CN109921960B (en) | 2019-03-27 | 2019-03-27 | IDC machine room network anomaly testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109921960A CN109921960A (en) | 2019-06-21 |
| CN109921960B true CN109921960B (en) | 2020-09-11 |
Family
ID=66967257
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910239356.3A Active CN109921960B (en) | 2019-03-27 | 2019-03-27 | IDC machine room network anomaly testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109921960B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112887148B (en) * | 2021-01-29 | 2022-06-21 | 烽火通信科技股份有限公司 | Method and device for simulating and predicting network flow |
| CN112929292A (en) * | 2021-03-07 | 2021-06-08 | 百果园技术(新加坡)有限公司 | Flow scheduling method, system, equipment and storage medium based on machine room comparison |
| CN116319467B (en) * | 2023-05-22 | 2023-07-21 | 中国信息通信研究院 | Depth synthesis audio detection method and system based on bidirectional flow of IDC machine room |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741595A (en) * | 2008-11-26 | 2010-06-16 | 华为技术有限公司 | Method, device and system for appraisal of network reliability |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120023220A1 (en) * | 2010-07-21 | 2012-01-26 | Chih-Ming Ma | Automatic testing system of dynamic host configuration protocol server |
| CN102571466A (en) * | 2010-12-16 | 2012-07-11 | ***通信集团安徽有限公司 | Method, device and system for testing service |
| CN104731698A (en) * | 2013-12-20 | 2015-06-24 | 深圳中兴力维技术有限公司 | Abnormal test case automatic generation processing method and device based on automatic tests |
| CN104270282B (en) * | 2014-09-11 | 2019-03-12 | 浙江宇视科技有限公司 | A kind of IP network end-to-end test method and apparatus |
| CN104243114A (en) * | 2014-09-26 | 2014-12-24 | 浙江中控技术股份有限公司 | Communication robustness test method and platform |
| CN104702463B (en) * | 2014-12-17 | 2018-03-23 | 北京百度网讯科技有限公司 | A kind of method, apparatus and system that more computer rooms bypass with test |
| CN108415835B (en) * | 2018-02-22 | 2019-07-30 | 北京百度网讯科技有限公司 | Distributed data library test method, device, equipment and computer-readable medium |
| CN108667548B (en) * | 2018-05-14 | 2019-11-19 | 烽火通信科技股份有限公司 | A kind of automated testing method and system based on ASON signaling network |
| CN109495336A (en) * | 2018-08-28 | 2019-03-19 | 优视科技（中国）有限公司 | Network Abnormal test method and device, computer equipment and readable medium |
-
2019
- 2019-03-27 CN CN201910239356.3A patent/CN109921960B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741595A (en) * | 2008-11-26 | 2010-06-16 | 华为技术有限公司 | Method, device and system for appraisal of network reliability |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109921960A (en) | 2019-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107977144B (en) | Screen capture processing method and mobile terminal | |
| CN109921960B (en) | IDC machine room network anomaly testing method and device | |
| CN110677224B (en) | Beam state detection method and terminal | |
| CN109995862B (en) | Resource scheduling method and terminal | |
| CN110895509B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN110990172A (en) | Application sharing method, first electronic device and computer-readable storage medium | |
| CN110673770A (en) | Message display method and terminal equipment | |
| CN109831359A (en) | A kind of detection method and its terminal device of data network connection state | |
| CN112415367A (en) | Drive chip abnormality detection method and device, electronic equipment and readable storage medium | |
| CN110069407B (en) | Function test method and device for application program | |
| CN107066374B (en) | Data processing method and mobile terminal | |
| CN110225040B (en) | Information processing method and terminal equipment | |
| CN110022551B (en) | Information interaction method and terminal equipment | |
| CN109218082B (en) | Network configuration parameter processing method, device and equipment | |
| WO2016019695A1 (en) | Voice interaction method and terminal | |
| CN112596980A (en) | ios performance collection method and device, mobile terminal and computer readable storage medium | |
| CN107979385A (en) | The information processing method and mobile terminal of a kind of radio-frequency devices | |
| CN112199246A (en) | Terminal testing method and device, storage medium and mobile terminal | |
| CN115328770A (en) | Application program testing method and device, electronic equipment and storage medium | |
| CN115480974A (en) | Method and device for testing device interface, electronic device and storage medium | |
| CN109905851A (en) | A kind of reminding method and terminal device | |
| CN109783379B (en) | Script execution exception determining method and device | |
| CN108459796A (en) | A kind of response method and mobile terminal of function key | |
| CN108989350B (en) | Method, device and equipment for detecting denial of service vulnerability | |
| CN108646928B (en) | Character input method and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240619 Address after: Building 10, Gutian 1967 Project, No. 10, Fengshuo Road, Qiaokou District, Wuhan, Hubei Province, 430000 Patentee after: Wuhan Xinghuo Zhongda Information Technology Co.,Ltd. Country or region after: China Address before: 2 / F, *** building, 10 Shangdi 10th Street, Haidian District, Beijing 100085 Patentee before: BEIJING BAIDU NETCOM SCIENCE AND TECHNOLOGY Co.,Ltd. Country or region before: China |