CN117675628A - Line quality monitoring method, device, equipment and storage medium - Google Patents

Line quality monitoring method, device, equipment and storage medium Download PDF

Info

Publication number
CN117675628A
CN117675628A CN202311340992.8A CN202311340992A CN117675628A CN 117675628 A CN117675628 A CN 117675628A CN 202311340992 A CN202311340992 A CN 202311340992A CN 117675628 A CN117675628 A CN 117675628A
Authority
CN
China
Prior art keywords
line
monitoring
task
hub
data
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.)
Pending
Application number
CN202311340992.8A
Other languages
Chinese (zh)
Inventor
瞿毅力
胡帅
李云龙
龙晓颖
裴斐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Merchants Bank Co Ltd
Original Assignee
China Merchants Bank Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Merchants Bank Co Ltd filed Critical China Merchants Bank Co Ltd
Priority to CN202311340992.8A priority Critical patent/CN117675628A/en
Publication of CN117675628A publication Critical patent/CN117675628A/en
Pending legal-status Critical Current

Links

Abstract

The invention discloses a line quality monitoring method, device, equipment and storage medium, and belongs to the field of network quality monitoring. The line quality monitoring method comprises the following steps: determining a target Hub device from Hub monitoring lines associated with a target Spoke monitoring line of a Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub device; acquiring first line monitoring task data and second line monitoring task data which are acquired by a simple network management protocol acquisition unit aiming at the target Hub equipment; and carrying out line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data. The invention realizes the accurate monitoring of the Spoke monitoring line in the Hub-Spoke networking architecture by the line quality monitoring equipment.

Description

Line quality monitoring method, device, equipment and storage medium
Technical Field
The present invention relates to the field of network quality monitoring, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring line quality.
Background
In the related art, network line quality is monitored mainly by conventional point-to-point dial testing technologies such as RPING (Remote Ping, a technology of sending a Ping command to a target host through a network and obtaining a response), NQA (Network Quality Analyzer, network quality monitoring technology), SQA (Service Quality Assurance, technology for comprehensively managing network service quality), ipla (IP Service Level Agreement, network management technology), and the like. Hub-Spoke networking is a popular headquarter-branch networking architecture: typically by an enterprise headquarters or data center as Hub sites; and each branch office of the enterprise serves as a Spoke site, server application deployed at a headquarter or a Hub site of a data center is accessed in a centralized way through a Wide Area Network (WAN), load and high availability are usually realized between the headquarter Hub site and the branch Spoke site through two operator networks, and if the Spoke of the enterprise needs to be communicated, the Spoke of the enterprise also needs to be transferred through the headquarter Hub site.
Therefore, the Hub-Spoke networking line is a point-to-multipoint line, and the multipoint side is often a branch mechanism of the inconvenient access equipment, so that the quality monitoring of the Hub-Spoke networking line cannot be directly realized by common point-to-point dial testing technologies such as RPING, NQA, SQA, IPSLA and the like.
Disclosure of Invention
The invention mainly aims to provide a line quality monitoring method, device, equipment and storage medium, and aims to solve the technical problem that related technologies cannot directly monitor quality of a Spoke monitoring line in a Hub-Spoke networking architecture.
In order to achieve the above object, the present invention provides a line quality monitoring method, which includes:
determining a target Hub device from Hub monitoring lines associated with a target Spoke monitoring line of a Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub device;
acquiring first line monitoring task data and second line monitoring task data which are acquired by a simple network management protocol acquisition unit aiming at target Hub equipment; the first line monitoring task data comprise a target Hub monitoring line access address, a device interface address of a target Spoke monitoring line and first line quality index data, and the second line monitoring task data comprise a target Hub monitoring line access address, an opposite interface address and second line quality index data;
And performing line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
Optionally, configuring the first dial testing task configuration content for the target Hub device includes:
acquiring Spoke line monitoring item data, dial testing global configuration parameters and alarm index data corresponding to a target Spoke monitoring line; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are associated with first line quality index data, and the Spoke line monitoring item data comprise a target Hub monitoring line access address and a device interface address of a target Spoke monitoring line;
filling a preset dial testing configuration template based on the Spoke line monitoring item data, dial testing global configuration parameters and alarm index data to obtain first dial testing task configuration content;
and issuing the configuration content of the first dial testing task to the target Hub equipment through the configuration automatic issuing tool.
Optionally, before the step of obtaining the first line monitoring task data and the second line monitoring task data collected by the simple network management protocol collector for the target Hub device, the method further includes:
obtaining Hub line monitoring item data, dial testing global configuration parameters and alarm index data corresponding to a target Hub monitoring line; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are associated with second line quality index data, and the Hub line monitoring item data comprise a target Hub monitoring line access address and an opposite port interface address;
Filling a preset dial testing configuration template based on Hub line monitoring item data, dial testing global configuration parameters and alarm index data to obtain second dial testing task configuration content;
and issuing second dial testing task configuration content to the target Hub equipment by the configuration automatic issuing tool, wherein the second dial testing task configuration content is used for obtaining second line monitoring task data.
Optionally, the first line quality indicator data comprises a first task delay;
after the step of obtaining the first line monitoring task data and the second line monitoring task data collected by the simple network management protocol collector aiming at the target Hub device, the method comprises the following steps:
determining a plurality of historical first line monitoring task data preceding the first line monitoring task data;
and obtaining a jitter value of the network delay based on the historical first task delay of the plurality of historical first line monitoring task data and the first task delay of the first line quality index data.
Optionally, the first line quality indicator data includes a first packet loss rate, and the second line quality indicator data includes a second packet loss rate;
according to the first line monitoring task data and the second line monitoring task data, the step of carrying out line monitoring on the target Spoke monitoring line comprises the following steps:
Judging whether the first packet loss rate is equal to a preset interrupt threshold value or not;
if the first packet loss rate is equal to a preset interrupt threshold, judging whether the second packet loss rate is equal to the preset interrupt threshold;
if the second packet loss rate is not equal to the preset interruption threshold value, determining the target Spoke monitoring line as a fault line, and pushing the line interruption alarm event.
Optionally, after the step of determining whether the first packet loss rate is equal to the preset interruption threshold, the method further includes:
if the first packet loss rate is not equal to the preset interruption threshold value, judging whether the first line quality index data is larger than a preset alarm threshold value or not;
if the first line quality index data is larger than the preset alarm threshold, pushing the super-threshold alarm event corresponding to the first line quality index data aiming at the target Spoke monitoring line.
Optionally, after the step of determining whether the first line quality indicator data is greater than the preset alarm threshold, the method further includes:
if the first line quality index data is smaller than or equal to a preset alarm threshold value, inquiring all historical super-threshold alarm events corresponding to the first line quality index data based on the target Hub monitoring line access address and the device interface address of the target Spoke monitoring line;
And if the query result is not null, all historical super-threshold alarm events are cleared, and super-threshold recovery events corresponding to the first line quality index data are pushed aiming at the target Spoke monitoring line.
In addition, in order to achieve the above object, the present invention also provides a line quality monitoring device, including:
the acquisition object determining and task configuring module is used for determining target Hub equipment from a monitoring line associated with a target Spoke monitoring line of Hub-Spoke networking and configuring first dial testing task configuration content for the target Hub equipment;
the monitoring task data acquisition module is used for acquiring first line monitoring task data and second line monitoring task data which are acquired by the simple network management protocol acquisition device aiming at the target Hub equipment;
and the monitoring task data analysis module is used for carrying out line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
In addition, to achieve the above object, the present invention also provides a line quality monitoring apparatus, including: the system comprises a memory, a processor and a line quality monitoring program stored on the memory and capable of running on the processor, wherein the line quality monitoring program is configured to realize the steps of the line quality monitoring method.
In addition, in order to achieve the above object, the present invention further provides a computer readable storage medium, on which a line quality monitoring program is stored, which when executed by a processor, implements the steps of the above-described line quality monitoring method.
The invention provides a line quality monitoring method, which comprises the following steps: determining a target Hub device from Hub monitoring lines associated with a target Spoke monitoring line of a Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub device; acquiring first line monitoring task data and second line monitoring task data which are acquired by a simple network management protocol acquisition unit aiming at target Hub equipment; the first line monitoring task data comprise a target Hub monitoring line access address, a device interface address of a target Spoke monitoring line and first line quality index data, and the second line monitoring task data comprise a target Hub monitoring line access address, an opposite interface address and second line quality index data; and performing line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
Therefore, the line quality condition of the target Spoke monitoring line can be obtained by determining the target Hub monitoring line corresponding to the target Spoke monitoring line and comparing the first line monitoring task data obtained by performing dial testing on the target Hub monitoring line and the target Spoke monitoring line with the second line monitoring data obtained by performing dial testing on the target Hub monitoring line independently, so that the accurate monitoring of the Spoke monitoring line in the Hub-Spoke networking architecture by the line quality monitoring device is realized.
Drawings
FIG. 1 is a schematic diagram of a line quality monitoring device of a hardware operating environment according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a first embodiment of a line quality monitoring method according to the present invention;
FIG. 3 is a schematic diagram of a Hub-Spoke networking architecture;
fig. 4 is a flow chart of a second embodiment of a line quality monitoring method according to the present invention;
fig. 5 is a schematic flow chart of a third embodiment of a line quality monitoring method according to the present invention;
fig. 6 is a flowchart of a fourth embodiment of a line quality monitoring method according to the present invention;
fig. 7 is a schematic diagram illustrating a flow chart of an example of a line quality monitoring method according to the present invention;
fig. 8 is a schematic diagram of a functional module of a first embodiment of a line quality monitoring method according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a line quality monitoring device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the line quality monitoring apparatus may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
It will be appreciated by those skilled in the art that the structure shown in fig. 1 does not constitute a limitation of the line quality monitoring apparatus, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 1, an operating system, a data storage module, a network communication module, a user interface module, and a line quality monitoring program may be included in a memory 1005, which is a computer readable storage medium.
In the line quality monitoring device shown in fig. 1, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the line quality monitoring device of the present invention may be disposed in the line quality monitoring device, and the line quality monitoring device invokes the line quality monitoring program stored in the memory 1005 through the processor 1001, and executes a line quality monitoring method provided by the embodiment of the present invention.
An embodiment of the present invention provides a line quality monitoring method, referring to fig. 2, fig. 2 is a schematic flow chart of a first embodiment of the line quality monitoring method of the present invention.
In this embodiment, a line quality monitoring method includes:
Step S10: and determining the target Hub equipment from the Hub monitoring line associated with the target Spoke monitoring line of the Hub-Spoke networking, and configuring the first dial testing task configuration content for the target Hub equipment.
It can be appreciated that in the Hub-Spoke networking architecture, the monitoring line includes a Hub monitoring line from a Hub device to an operator network and a Spoke monitoring line from the same operator network to a Spoke site device. Each Spoke monitoring line corresponds to Hub monitoring lines of the same operator network.
The Hub-Spoke networking architecture is shown in fig. 3. In a Hub-Spoke network, there are 2 Hub sites, including headquarter Hub A sites and headquarter Hub B sites, hub A sites include access devices Hub A01 and Hub A02, and Hub B sites include access devices Hub B01 and Hub B02; there are 2 branch office Spoke sites, including branch office Spoke a site and branch office Spoke b site, spoke a site includes access devices Spoke a01 and Spoke a02, and Spoke b site includes access devices Spoke b01 and Spoke b02. In addition, there are also a carrier network and a b carrier network. The Hub site and the Spoke site are connected through Hub lines, operator networks and Spoke lines. The Spoke sites pass through the Spoke lines, the operator networks and the Hub lines sequentially when the Spoke sites access the Hub sites, pass through the Hub lines, the operator networks and the Spoke lines sequentially when the Hub sites access the Spoke sites, and pass through the Spoke lines, the operator networks, the Hub lines, the Hub sites, the Hub lines, the operator networks and the Spoke lines sequentially when the Spoke sites access each other. From the figure, when the Spoke site and the Hub site visit each other, traffic isolation exists among different operator lines, and when the Spoke equipment or the Hub equipment initiates the visit, the operator lines are selected to be controlled by the equipment load balancing strategy, so that the line quality monitoring is not affected. It is easy to see that the Hub-Spoke networking line is a point-to-multipoint line, and most of the multipoint sides are inconvenient to access to the Spoke mechanism of the equipment, so that the quality monitoring of the Hub-Spoke networking line cannot be directly realized by common point-to-point dial testing technologies such as RPING, NQA, SQA, IPSLA and the like.
Before monitoring the target Spoke monitoring line, all Hub monitoring lines of the same operator network as the target Spoke monitoring line need to be inquired and obtained, and one target Hub monitoring line is determined from all Hub monitoring lines obtained. And taking the target Hub equipment corresponding to the target Hub monitoring line as the execution equipment of the dial testing task, configuring a first dial testing task configuration content of a target complete monitoring line aiming at the target Hub monitoring line and the target Spoke monitoring line for the target Hub equipment, and collecting line monitoring task data from the target Hub equipment through a simple network management protocol.
Referring to FIG. 3, there are four associated Hub lines per Spoke line. For example, take the example of the carrier a Spoke a01 line from the a carrier network to the device Spoke a01 in the Hub-Spoke networking of fig. 3: before monitoring the carrier a Spoke a01 line, a query is required to obtain four Hub line information connected to the carrier a network: operator nail Hub a01 line, operator nail Hub a02 line, operator nail Hub B01 line, and operator nail Hub B02 line. And acquiring four Hub devices connected with each Hub line according to the four Hub line monitoring item information as execution equipment of a dial testing task, and acquiring line monitoring task data from the four Hub devices through a simple network management protocol.
Step S50: the method comprises the steps of obtaining first line monitoring task data and second line monitoring task data which are collected by a simple network management protocol collector aiming at target Hub equipment.
Specifically, the line monitoring task data acquired from the target Hub device includes first line monitoring task data and second line monitoring task data. The first line monitoring task data is obtained by the target Hub device executing a first dial testing task configuration content of a target complete monitoring line configuration for a target Hub monitoring line and a target Spoke monitoring line, and the second line monitoring task data is line monitoring task data for the target Hub monitoring line in the target Hub device.
As shown in fig. 3, an operator a line from device Hub a01 to device Spoke a01 is exemplified, which includes an operator a Hub line from device Hub a01 to the a operator network and an operator a Spoke line from the a operator network to device Spoke a 01. The device Hub a01 is configured with a first line monitoring task and a second line monitoring task. The first line monitoring task is used for detecting the line quality of the whole line from the equipment Hub A01 to the equipment Spoke A01, namely the line quality of the equipment Hub A01 to the operator A network. The first line monitoring task data corresponding to the first line monitoring task and the second line monitoring task data corresponding to the second line monitoring task can be acquired from the device Hub A01 through a simple network management protocol acquirer.
In this embodiment, the first line monitoring task data includes a target Hub monitoring line access address, a device interface address of a target Spoke monitoring line, and first line quality index data, and the second line monitoring task data includes a target Hub monitoring line access address, an opposite interface address, and second line quality index data. The first line quality index data and the second line quality index data are all monitoring indexes obtained in the monitoring process of the corresponding monitoring line, the first line quality index data correspond to the target complete monitoring line, and the second line quality index data correspond to the target Hub monitoring line. In a specific application scenario, the first line quality index data and the second line quality index data may be a packet loss rate, a time delay, a number of transmitted probe messages, an average time delay, a packet loss rate, a number of transmitted probe messages, a response number of a received corresponding test, or a response time sum of successfully executing all the messages.
Step S80: and performing line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
Specifically, after the first line monitoring task data and the second line monitoring task data are obtained, first line quality index data are extracted from the first line monitoring task data, and second line quality index data are extracted from the second line monitoring task data. It will be appreciated that the first line quality index data reflects the line quality of the target full monitoring line and the second line quality index data reflects the line quality of the target Hub monitoring line. The line quality of the target Spoke monitoring line may be determined by comparing the first line quality index data with the second line quality index monitoring data.
For example: in Hub-Spoke network based on network equipment supporting NQA technology, setting the following global parameters for a simple network management protocol SNMP collector:
SNMP acquisition frequency, defaulting to 60 seconds;
SNMP protocol version, default to SNMPv2;
SNMP community name, default.
The precondition of the execution is that each line monitoring item has completed NQA configuration, NQA detection task is started, the access equipment has completed SNMP protocol function starting, the configuration of dial test SNMP collector service IP, supported SNMP protocol version and unified SNMP group name (community) is completed, and the strategy opening of network interview with dial test SNMP collector is completed.
When SNMP is collected, the OID to be collected is as follows:
the dial testing SNMP collector creates a timing task according to the set SNMP collection frequency, traverses all line monitoring items with line Hub-Spoke types of Hub lines at fixed time, initiates SNMP collection requests to the equipment and receives the responsive collection results according to given OID, access equipment information, SNMP group names, SNMP version numbers and other SNMP protocols in a unified mode, packages the collection time and the collection results, and finally transmits the collection time and the collection results to dial testing data consumption service processing through interfaces or message middleware such as kafka.
The dial testing data consumption service realizes consumption of the collected data through a receiving interface or a message middleware, and performs data processing after the consumption of the collected data according to the following steps:
and separating the acquisition results of the nqaResultsAddress, nqaResultsRttAvg, nqaResultsLostPacketRatio, nqaResultsSentProbes, nqaResultsProbeResponses, nqaResultsSumCompletionTime six indexes. The six acquisition results are ASCII codes of OID and NQA task test-instance configuration item parameter VALUEs (the VALUEs are uniformly set as ' admin ' in the example), acquisition task name ASCII codes, acquisition result sequence number ORDER (i.e. task execution times) and acquisition result codes of one integer task type which are spliced by ' are KEYs (KEY), and the KEY VALUE pair data of which the corresponding index acquisition result is a VALUE (VALUE). Wherein, the destination address of nqaResulttsAddress configured by NQA task is VALUE, nqaResultsRttAvg, nqaResulttsSumCompletionTime is VALUE, nqaResultsLostPacketRatio in integer millisecond, the packet loss rate is VALUE, nqaResultsSentProbes in integer, and nqaResulttsProbeResponses is VALUE in integer message number.
Traversing nqaaResultsAddress acquisition results, and constructing data IP_IDS_MAP by taking a destination address as a KEY and a VALUE KEY VALUE of an acquisition result coding list.
Traversing KEY value pairs IP_IDS_MAP to obtain an acquisition result coding list of each destination IP, sequencing the acquisition result coding list from low to high according to acquisition result sequence number ORDER contained in each acquisition result code, continuing traversing the sequenced acquisition result coding list to obtain the currently traversed acquisition result code, inquiring the acquisition result code into KEY value pairs and nqaResultsRttAvg, nqaResultsLostPacketRatio, nqaResultsSentProbes, nqaResultsProbeResponses, nqaResultsSumCompletionTime six KEY value pairs by the acquisition result code, obtaining six values of average time delay, packet loss rate, the number of transmitted detection messages, the response number of received corresponding tests, the response time sum of successfully executing all messages, analyzing task name ASCII codes contained in the acquisition result code, converting the task name ASCII codes into character string task names, dividing the character string task names into an actually detected interface address and an actually detected interface address by using "-" to package the acquisition time, the actually detected interface address, the acquisition result ORDER, the average time delay, the packet loss rate, the number of transmitted detection messages, the response number of received corresponding tests and the response time sum of successfully executing all messages. And then, matching the interface address of the target Hub device and the interface address of the device of the target Spoke monitoring line from the actually detected interface address and the actually detected opposite-end interface address to obtain corresponding first line monitoring task data and second line monitoring data.
In this embodiment, by determining the target Hub monitoring and the line corresponding to the target Spoke monitoring line, the line quality condition of the target Spoke monitoring line can be obtained by comparing the first line monitoring task data obtained by performing dial testing on the target Hub monitoring line and the target Spoke monitoring line with the second line monitoring data obtained by performing dial testing on the target Hub monitoring line alone. Therefore, the line quality monitoring device realizes accurate monitoring of the Spoke monitoring line in the Hub-Spoke networking architecture under the condition that the Spoke site side device is not subjected to nanotube and configuration.
Further, a second embodiment is proposed based on the first embodiment, referring to fig. 4, fig. 4 is a schematic flow chart of a second embodiment of a line quality monitoring method according to the present invention.
In this embodiment, step S10 includes:
step S11: and acquiring the Spoke line monitoring item data, the dial testing global configuration parameters and the alarm index data corresponding to the target Spoke monitoring line.
Step S12: and filling a preset dial testing configuration template based on the Spoke line monitoring item data, the dial testing global configuration parameters and the alarm index data to obtain the configuration content of the first dial testing task.
Step S13: and issuing the configuration content of the first dial testing task to the target Hub equipment through the configuration automatic issuing tool.
After step S10, the method includes:
step S20: obtaining Hub line monitoring item data, dial testing global configuration parameters and alarm index data corresponding to a target Hub monitoring line.
Step S30: and filling a preset dial testing configuration template based on Hub line monitoring item data, dial testing global configuration parameters and alarm index data to obtain second dial testing task configuration content.
Step S40: and issuing second dial testing task configuration content to the target Hub equipment by the configuration automatic issuing tool, wherein the second dial testing task configuration content is used for obtaining second line monitoring task data.
It can be understood that before the first line monitoring task data and the second line monitoring task data are collected, the configuration of the dial testing task needs to be performed for the target completion monitoring line and the monitoring item corresponding to the target Hub monitoring line, and the dial testing task needs to be issued to the corresponding target Hub device. In a specific embodiment, first, complete Spoke line monitoring item data is established for a target complete monitoring line, and complete Hub line monitoring item data is established for a target Hub monitoring line. In addition, unified dial testing global configuration parameters and alarm indexes are required to be set. And filling related variables in a preset dial testing configuration template according to the parameters of the Spoke line monitoring item, the dial testing global configuration parameters and the alarm indexes to obtain the configuration content of the first dial testing task. And filling related variables in the same preset dial testing configuration template according to the Hub line monitoring item data, the dial testing global configuration parameters and the alarm indexes to obtain second dial testing task configuration content.
The complete line monitoring item data comprises a line unique identifier, an operator, line description, line fault information, line Hub-Spoke type, access equipment information, an access interface address, an opposite interface address and an interface VPN instance name, the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, and the alarm index can comprise one or more of packet loss rate, time delay, continuous packet loss task number, network time delay jitter or line interruption.
The dial testing task configuration content corresponding to the line monitoring item can be generated according to the line monitoring item data and the dial testing configuration template, and the dial testing configuration template can be preset according to a specific dial testing technology. The configuration command parameters such as the message sending interval, the detection packet number, the detection task frequency and the like in the dial testing task configuration content directly acquire corresponding parameter values from the line monitoring item data of the target monitoring line.
When a target monitoring line for generating the dial testing task configuration content is a Hub line, each line generates a copy of corresponding dial testing task configuration content and configures the copy of corresponding dial testing task configuration content to the access Hub device, and the generated dial testing configuration content comprises the following steps: the VPN instance name directly acquires a recorded parameter value from line monitoring item data of a target Hub monitoring line, and the parameter value is consistent with the actual VPN instance configuration of the line on a Hub equipment access interface; the interface address and the opposite interface address directly acquire parameter values from line monitoring item data of a target monitoring line, and the two parameter values are kept globally unique in the whole Hub-Spoke network; the task name directly acquires the allocated task name from the line monitoring item data of the target monitoring line, the configured dial testing task with the same name as the task name does not exist on the target monitoring line access Hub equipment, and the task name meets the standard requirement of the adopted dial testing technology.
When the target monitoring line for generating the dial testing task configuration content is a Spoke line, generating a dial testing task configuration content according to each Hub line associated with the target monitoring line, and configuring the dial testing task configuration content to the access Hub device. In the dial testing configuration content generated for each associated Hub line: the VPN instance name directly acquires a recorded parameter value from line monitoring item data of a target monitoring line, and the parameter value is consistent with the actual VPN instance configuration of the associated Hub line on a Hub device access interface; the interface address takes the interface address in the line monitoring item data of the associated Hub line, and the address is the access interface address of the associated Hub line on the access Hub device; the opposite-end interface address is an interface address obtained from line monitoring item data of a target Spoke monitoring line, and the address is an access interface address of the target Spoke line on access Spoke equipment; the interface address and the opposite interface address should be kept globally unique in the whole Hub-Spoke network; the task name directly acquires the allocated task name from the line monitoring item data of the target monitoring line, and the task name is ensured to be in accordance with the standard requirement of the adopted dial testing technology, wherein the dial testing task with the same name as the task name does not exist on the access Hub equipment of each Hub line associated with the target monitoring line.
For example: in Hub-Spoke networking lines based on network devices supporting NQA technology, NQA monitoring configuration templates are shown in table 1:
TABLE 1
Wherein, the space occupation parameter which needs to be completed according to the line monitoring item data is marked by [ and the optional configuration item is marked by [ which is to generate the configuration content of [ when the space occupation parameter in [ exists ], otherwise, the whole [ configuration item takes the empty string. According to the template, NQA configuration required for monitoring can be automatically generated for each line monitoring item, and the method is specifically divided into two cases:
when the line Hub-Spoke type of the line monitoring item is Hub monitoring line, generating perfect NQA configuration for each parameter in the NQA configuration template according to the following value standard: the values of the interface address and the interface address are taken and spliced through the's'; an interface field value of an interface of a line monitoring item is fetched; get the line monitor access interface address field value; taking a line monitoring item interface VPN instance name field value; the transmission message interval parameter T is selected from the line monitoring item dial test configuration and the alarm parameter set; the method comprises the steps of (1) taking a detection task frequency parameter F in a line monitoring item dial testing configuration and an alarm parameter set; the number parameter N of the detected messages in the line monitoring item dial testing configuration and the alarm parameter set is taken. After the NQA configuration is generated, the NQA configuration is issued to the access equipment of the current line monitoring item according to the access equipment information of the current line monitoring item by configuring an automatic issuing tool or a manual configuration mode.
And when the line Hub-Spoke type of the line monitoring item is a Spoke monitoring line, inquiring line monitoring items which are all the same as the operators of the current line monitoring item and have the line Hub-Spoke type of Hub lines, namely the associated Hub line monitoring items of the current line monitoring item. Generating a perfect NQA configuration for each associated Hub line monitoring item of the current line monitoring item according to the following value standard: the values of the interface address and the interface address are taken and spliced through the's'; an opposite interface address takes the current line monitoring item access interface address field value; the interface address field value of the associated Hub line monitoring item is taken; the interface VPN instance name field value of the associated Hub line monitoring item is taken; the method comprises the steps of (1) acquiring a transmission message interval parameter T in a current line monitoring item dial test configuration and an alarm parameter set; the method comprises the steps of (1) acquiring a detection task frequency parameter F in a current line monitoring item dial testing configuration and an alarm parameter set; and (4) acquiring a number parameter N of the detection messages in the current line monitoring item dial test configuration and the alarm parameter set.
After the NQA configuration of each associated Hub line monitoring item is generated, the NQA configuration is issued to the access equipment of the associated Hub line monitoring item according to the access equipment information of the associated Hub line monitoring item by configuring an automatic issuing tool or a manual configuration mode. As shown in FIG. 3, four associated Hub lines and corresponding associated Hub line monitoring items exist for each Spoke line monitoring item, so that each Spoke line monitoring item generates four NQA configurations and issues the configuration to four devices Hub A01, hub A02, hub B01 and Hub B02.
In this embodiment, for a target complete monitoring line and an individual target Hub monitoring line consisting of a target Hub monitoring line and a target Spoke monitoring line, dial testing task configuration is performed on the basis of a preset dial testing configuration template, so that the target complete monitoring line and the individual target Hub monitoring line can be monitored respectively to obtain corresponding first line monitoring task data and second line monitoring task data, and further accurate monitoring of the Spoke monitoring line in a Hub-Spoke networking architecture by line quality monitoring equipment is achieved.
Further, a third embodiment is proposed based on the first embodiment, referring to fig. 5, fig. 5 is a schematic flow chart of a third embodiment of a line quality monitoring method according to the present invention.
In this embodiment, after step S50, the method includes:
step S60: a plurality of historical first line monitoring task data preceding the first line monitoring task data is determined.
Step S70: and obtaining a jitter value of the network delay based on the historical first task delay of the plurality of historical first line monitoring task data and the first task delay of the first line quality index data.
Specifically, in this embodiment, the alert indicator includes jitter of task delay and network delay. It can be understood that only the current task time delay can be extracted from the line monitoring task data, and the jitter value of the network time delay can be obtained only according to the difference value between the current task time delay and the average value of the corresponding historical task time delay.
For example: in a specific application scenario, the current time T of the system is first obtained now Counting task number C of detection task frequency F in NQA configuration parameters and continuous packet loss task number in alarm index task . Calculate T now –F*C task Obtaining the starting time T for counting the number of continuous packet loss tasks task Inquiring historical acquisition result data to acquire the acquisition time of the current line monitoring item at T task To T now The number of record items with the packet loss rate larger than 0 is obtained to obtain the continuous packet loss task number LN task 。
Inquiring the collection result set of the same NQA task record in the collection result database according to the interface address and the opposite interface address, and counting N as the history record total Greater than the backtracking task number N jitter Taking N with the smallest difference value between the sequence number of the acquisition result and the sequence number ORDER of the current acquisition result jitter The historical collection results are backtracking collection result sets, and when the number of the historical records is N total Less than or equal to the number of backtracking tasks N jitter And taking all the historical acquisition results as a backtracking acquisition result set. Calculating the average value of all time delays D in the backtracking acquisition result set to obtain the average time delay D jitter Finally, calculating the average time delay D jitter And obtaining the jitter J of the current network delay by the difference value of the current acquisition result delay D.
In this embodiment, by making a difference between the average value of the first task time delay and the historical first task time delay in the current first line monitoring task data, a jitter value of the network time delay can be obtained, so as to realize monitoring and alarming of a network jitter scene, and enrich the application scene of the line quality monitoring device.
Further, a fourth embodiment is proposed based on the first embodiment, referring to fig. 6, and fig. 6 is a schematic flow chart of a fourth embodiment of a line quality monitoring method according to the present invention.
In this embodiment, step S80 specifically includes:
step S81: and judging whether the first packet loss rate is equal to a preset interrupt threshold value.
Step S82: if the first packet loss rate is equal to the preset interrupt threshold, judging whether the second packet loss rate is equal to the preset interrupt threshold.
Step S83: if the second packet loss rate is not equal to the preset interruption threshold value, determining the target Spoke monitoring line as a fault line, and pushing the line interruption alarm event.
In this embodiment, the alarm indicator includes a preset interruption threshold, the first line monitoring quality indicator data includes a first packet loss rate, and the second line monitoring quality indicator data includes a second packet loss rate. The preset interrupt threshold may be set according to a specific application scenario, which is not limited herein. The first packet loss rate corresponds to the packet loss rate of the target complete monitoring line, and the second packet loss rate corresponds to the packet loss rate of the target Hub monitoring line. The first packet loss rate is compared with a preset interruption threshold value, whether the target complete monitoring line is interrupted or not can be judged, and the same whether the target Hub monitoring line is interrupted or not can be judged by comparing the second packet loss rate with the preset interruption threshold value.
It will be appreciated that if the target is monitoring for line breaks entirely, there may be two situations: firstly, a target Hub monitors line interruption; second, the target Spoke monitors for line breaks. If the first packet loss rate and the second packet loss rate are equal to the preset interruption threshold value at the same time, the target Hub monitoring line is interrupted, the target Hub monitoring line can be determined to be a fault line, and a line interruption alarm event is pushed. If the first packet loss rate is equal to a preset interruption threshold value and the second packet loss rate is not equal to the preset interruption threshold value, the target Spoke monitoring line is interrupted, the target Spoke monitoring line can be determined to be a fault line, and a line interruption alarm event is pushed.
Therefore, by simultaneously comparing and analyzing the first packet loss rate reflecting the line quality of the target Hub monitoring line and the target Spoke monitoring line and the second packet loss rate reflecting the independent target Hub monitoring line, the accurate monitoring of the interruption scene of the target Spoke monitoring line can be realized.
Further, in the present embodiment, after step S81, the method includes:
step S84: if the first packet loss rate is not equal to the preset interrupt threshold, judging whether the first line quality index data is larger than a preset alarm threshold.
Step S85: if the first line quality index data is larger than the preset alarm threshold, pushing the super-threshold alarm event corresponding to the first line quality index data aiming at the target Spoke monitoring line.
Step S86: if the first line quality index data is smaller than or equal to the preset alarm threshold value, inquiring all historical super-threshold alarm events corresponding to the first line quality index data based on the target Hub monitoring line access address and the device interface address of the target Spoke monitoring line.
Step S87: and if the query result is not null, all historical super-threshold alarm events are cleared, and super-threshold recovery events corresponding to the first line quality index data are pushed aiming at the target Spoke monitoring line.
It can be understood that the first line quality index data may include multiple indexes, if the first packet loss rate is not equal to the preset interrupt alarm threshold, the line interrupt alarm event of the target Spoke monitoring line will not be triggered, and other indexes except the first packet loss rate in the first line quality index data may be further analyzed.
Specifically, different preset alarm thresholds may be set for different indexes, and other indexes in the first line quality index data may be compared with the corresponding preset alarm thresholds. If the index is larger than the preset alarm threshold, pushing a super-threshold alarm event corresponding to the index aiming at the target Spoke monitoring line. If the index is smaller than or equal to the preset alarm threshold, inquiring all the historical super-threshold alarm events corresponding to the index according to the access address of the target Hub monitoring line and the equipment interface address of the target Spoke monitoring line, and if the corresponding historical super-threshold alarm event is inquired, clearing all the corresponding historical super-threshold alarm events, and pushing the super-threshold recovery event corresponding to the index aiming at the target Spoke monitoring line.
In addition, the time delay, the packet loss rate, the continuous packet loss number and the network jitter can be simultaneously included in the monitoring index, and monitoring alarm of various scenes such as the time delay exceeding threshold, the packet loss rate exceeding threshold, the continuous packet loss, the network jitter, the line interruption and the like can be realized.
For example: in the Hub-Spoke networking scenario, the line quality monitoring indicator alarm and recovery logic flow is shown in fig. 7. Before that, the following five global alarm parameters are preset: packet loss rate alarm threshold TH loss Super-threshold alert level L loss The method comprises the steps of carrying out a first treatment on the surface of the Time delay warning threshold TH delay Super-threshold alert level L delay The method comprises the steps of carrying out a first treatment on the surface of the Counting task number C of continuous packet loss task number task Alarm threshold TH task Super-threshold alert level L task The method comprises the steps of carrying out a first treatment on the surface of the Number of jitter backtracking tasks C jitter Alarm threshold TH jitter Super-threshold alert level L jitter The method comprises the steps of carrying out a first treatment on the surface of the Line interrupt alert level L down . Wherein TH is that loss Default value of 20%, TH delay Default value of 800 ms, C task Default value 10, TH task Default value 3, C jitter Default value 10, TH jitter Default value of 100, L loss 、L delay 、L task 、L jitter Default value is critics level, L down Default values are ALERT levels.
Furthermore, another premise is that a collection result database and an event cache database are already built. Specifically, the SNMP collector collects dial testing result data of the access equipment accessed to the network, the collected dial testing result data is sent to the dial testing data consumption service through the message middleware kafka to conduct data analysis to obtain line quality index data, and the line quality index data is stored in the collection result database. The acquisition result database stores acquisition time, interface address of opposite end, acquisition result sequence number ORDER, time delay D, packet loss rate LR, number of detection messages SN sent, response number RN of corresponding test received, and response time sum D of all messages successfully executed sum Data. The event cache database stores unrecovered alarm event information, and supports automatic deleting of data item overtime or creating of timing task to realize overtime data cleaning.
Firstly, the received acquisition time, interface address, opposite interface address and acquisition result serial number ORDER, time delay D, packet loss rate LR, number of detection messages SN sent, number of responses RN of corresponding tests received, and sum of response time D of successfully executing all messages sum The encapsulation body unpacks to obtain the data of each object, the acquisition result sequence number ORDER recorded by the same NQA task in the acquisition result database is inquired according to the interface address and the opposite interface address, if the acquisition result sequence number ORDER exists, the data is discarded, and if the acquisition result sequence number ORDER does not exist, the acquisition result is recorded in the acquisition result database.
And then, matching the acquisition result with a line monitoring item. Specifically, the acquired interface address is taken as the value of the access interface address of the line monitoring item, the acquired opposite-end interface address is taken as the value of the opposite-end interface address of the line monitoring item, and the Hub line is taken as the value of the line Hub-Spoke type to inquire the line monitoring item corresponding to the acquisition result. And if the matching is successful, returning the queried Hub line monitoring item. And if the matching fails, inquiring the line monitoring item corresponding to the acquisition result by taking the obtained opposite-end interface address as the value of the line monitoring item access interface address and taking the Spoke line as the value of the line Hub-Spoke type, inquiring the related Hub line monitoring item corresponding to the acquisition result by taking the obtained interface address as the value of the line monitoring item access interface address and taking the Hub line as the value of the line Hub-Spoke type, and returning the inquired Spoke line monitoring item and the related Hub line monitoring item.
Next, the current time T of the system is obtained now Counting task number C of detection task frequency F and global alarm parameter continuous packet loss task number in NQA configuration parameters of the matched line monitoring items task . Calculate T now –F*C task Obtaining the starting time T for counting the number of continuous packet loss tasks task Inquiring an acquisition result database to acquire the acquisition time of the current line monitoring item at T task To T now The number of record items with the packet loss rate larger than 0 is obtained to obtain the continuous packet loss task number LN task 。
And then judging whether the packet loss rate is 100%, and triggering a line interruption alarm event if the packet loss rate is equal to 100%. Calling a line monitoring item matching method to match line monitoring according to interface address and opposite interface addressIf only one line monitoring item is matched, the control item further comprises acquisition time, line monitoring item data, time delay D, packet loss rate LR, jitter J and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation down The level line interrupts the alarm event while recording this event information in the event cache database and setting the data item to timeout after 24 hours or automatically clear the data item after 24 hours by timing the task. The event cache database provides a search of historical alarm events for the dial testing data consumption service.
If a matched line monitoring item and an associated Hub line monitoring item are received, inquiring all historical line interruption alarm events of the associated Hub line monitoring item in an event cache database every 10 seconds until the same time length as SNMP acquisition frequency is passed or the inquiry result is not empty, stopping inquiring, if the final inquiry result is not empty, indicating that the associated Hub line of the line corresponding to the acquisition result is interrupted and alarmed, and if the inquiry result is always empty, indicating that the connectivity of the associated Hub line of the line corresponding to the acquisition result is normal, and if the inquiry result is always empty, indicating that the fault line is the line corresponding to the acquisition result, thus collecting the acquisition time, the matched line monitoring item data, the time delay D, the packet loss rate LR, the jitter J and the continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation down The level line interrupts the alarm event while recording this event information in the event cache database and setting the data item to timeout after 24 hours or automatically clear the data item after 24 hours by timing the task.
If the packet loss rate is less than 100%, firstly acquiring a line monitoring item matched by calling a line monitoring item matching method according to an interface address and an opposite interface address, querying an event cache database for all historical line interrupt alarm events of the line monitoring item, if the query result is not null, clearing the cached historical line interrupt alarm events, and acquiring the data Calling a fault line monitoring item matched by a line monitoring item matching method according to the interface address and the opposite interface address, and then collecting time, fault line monitoring item data, time delay D, packet loss rate LR, jitter J and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum And pushing the line interruption recovery event after encapsulation, and simultaneously clearing all historical line interruption alarm events of the line monitoring item in the event cache database.
If the line interruption alarm event is not triggered, judging whether the packet loss rate LR exceeds a threshold value TH loss If yes, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to the interface address and the opposite interface address, and then collecting time, fault line monitoring item data and a threshold value TH loss Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation loss The method comprises the steps of recording event information in an event cache database and setting overtime after 24 hours of the data item or automatically clearing the data item after 24 hours of a timing task, if not, inquiring the event cache database for all historical packet loss rate over-threshold alarm events of the line monitoring items, if not, clearing the cached historical alarm events, acquiring fault line monitoring items matched by calling a line monitoring item matching method according to an interface address and an opposite interface address, and collecting time, fault line monitoring item data and a threshold TH loss Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Pushing the packet loss rate super-threshold recovery event after packaging, and simultaneously clearing all historical packet loss rate super-threshold alarm events of the line monitoring items in the event cache database.
If not triggeredJudging whether the time delay D exceeds the threshold value TH or not when the line interrupt alarm event occurs delay If yes, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to the interface address and the opposite interface address, and then collecting time, fault line monitoring item data and a threshold value TH delay Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation delay The method comprises the steps of recording event information in an event cache database and setting overtime after 24 hours of the data item or automatically cleaning the data item after 24 hours of a timing task, if not, inquiring the event cache database for all historical delay overtime alarm events of the line monitoring item, if the inquiring result is not empty, cleaning the cached historical alarm events, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to an interface address and an opposite port interface address, and then collecting time, fault line monitoring item data and a threshold TH delay Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum And pushing the time delay exceeding threshold value recovery event after packaging.
If the line interruption alarm event is not triggered, judging the continuous packet loss task number LN task Whether or not to exceed the threshold value TH task If yes, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to the interface address and the opposite interface address, and then collecting time, fault line monitoring item data and a threshold value TH task Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation task The number of the continuous packet loss tasks of the level exceeds a threshold value to alarm an event, and meanwhile, the event information is recorded in an event cache databaseSetting the data item to overtime after 24 hours or automatically cleaning the data item after 24 hours through a timing task, if not, inquiring the event cache database about all historical continuous packet loss task number alarm events of the line monitoring item, if the inquiry result is not empty, cleaning the cached historical alarm events, and collecting time, fault line monitoring item data and a threshold value TH task Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation task The number of the level continuous packet loss tasks exceeds a threshold value to recover the event.
If the line interruption alarm event is not triggered, judging whether the jitter J exceeds a threshold TH or not jitter If yes, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to the interface address and the opposite interface address, and then collecting time, fault line monitoring item data and a threshold value TH jitter Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum Push L after encapsulation jitter Recording event information in an event cache database and setting overtime after 24 hours or automatically clearing the data item after 24 hours by a timing task, if not, inquiring all historical network delay jitter alarm events of the line monitoring item in the event cache database, if not, clearing the cached historical alarm events, acquiring a fault line monitoring item matched by calling a line monitoring item matching method according to an interface address and an opposite interface address, and then collecting time, fault line monitoring item data and a threshold TH jitter Delay D, packet loss rate LR, jitter J, and continuous packet loss task number LN task The number SN of the transmitted detection messages, the response number RN of the received corresponding test, and the sum D of the response time of successfully executing all the messages sum And pushing the network delay jitter recovery event after encapsulation.
The line monitoring item matching method specifically comprises the following steps: after the interface address and the opposite port interface address are obtained, firstly, the obtained interface address is taken as a value of a line monitoring item access interface address, the obtained opposite port interface address is taken as a value of a line monitoring item opposite port interface address, and a Hub line is taken as a line Hub-Spoke type value to inquire a line monitoring item corresponding to an acquisition result. And if the matching is successful, returning the queried Hub line monitoring item. And if the matching fails, inquiring the line monitoring item corresponding to the acquisition result by taking the obtained opposite-end interface address as the value of the line monitoring item access interface address and taking the Spoke line as the value of the line Hub-Spoke type, inquiring the related Hub line monitoring item corresponding to the acquisition result by taking the obtained interface address as the value of the line monitoring item access interface address and taking the Hub line as the value of the line Hub-Spoke type, and returning the inquired Spoke line monitoring item and the related Hub line monitoring item.
In this embodiment, the "target Hub monitoring line+target Spoke monitoring line" and the separate target Hub monitoring line are monitored respectively, and the two are analyzed and compared in combination with a preset alarm threshold value, so that a fault line can be rapidly and accurately determined, and the accurate pushing of an alarm event is realized. In addition, the history alarm event is searched and analyzed at the same time, the processed history alarm event is cleaned in time, and the timely pushing of the recovery event can be realized.
Further, to achieve the above object, the present invention further provides a line quality monitoring apparatus, which may include:
the acquisition object determining and task configuring module is used for determining target Hub equipment from Hub monitoring lines associated with target Spoke monitoring lines of Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub equipment;
the monitoring task data acquisition module is used for acquiring first line monitoring task data and second line monitoring task data which are acquired by the simple network management protocol acquisition device aiming at the target Hub equipment;
and the monitoring task data analysis module is used for carrying out line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
It should be noted that, the functions that can be achieved by each module in the line quality monitoring device and the technical effects that can be achieved by the corresponding modules in the line quality monitoring device provided in this embodiment may refer to descriptions of specific implementations in each embodiment of a line quality monitoring method according to the present invention, and for brevity of description, details are not repeated here.
In addition, the embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a line quality monitoring program, and the line quality monitoring program realizes the steps of the line quality monitoring method when being executed by a processor. Therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present invention, please refer to the description of the method embodiments of the present invention. As an example, the program instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the statement "comprising a Hub-Spoke networking line quality monitor" does not exclude that there are additional identical elements in a process, method, article or system comprising the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a computer readable storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (10)

1. The line quality monitoring method is characterized by comprising the following steps of:
determining a target Hub device from Hub monitoring lines associated with a target Spoke monitoring line of a Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub device;
acquiring first line monitoring task data and second line monitoring task data which are acquired by a simple network management protocol acquisition unit aiming at the target Hub equipment; the first line monitoring task data is obtained based on the first dial testing task configuration content and comprises the target Hub monitoring line access address, the device interface address of the target Spoke monitoring line and first line quality index data, and the second line monitoring task data comprises the target Hub monitoring line access address, an opposite port interface address and second line quality index data;
and carrying out line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
2. The method for monitoring line quality according to claim 1, wherein configuring the first dial testing task configuration content for the target Hub device includes:
Acquiring Spoke line monitoring item data, dial testing global configuration parameters and alarm index data corresponding to the target Spoke monitoring line; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are associated with first line quality index data, and the Spoke line monitoring item data comprise the target Hub monitoring line access address and the device interface address of the target Spoke monitoring line;
filling a preset dial testing configuration template based on the Spoke line monitoring item data, the dial testing global configuration parameters and the alarm index data to obtain first dial testing task configuration content;
and distributing the first dial testing task configuration content to the target Hub equipment through a configuration automatic distributing tool.
3. The line quality monitoring method of claim 2, wherein prior to the step of obtaining the first line monitoring task data and the second line monitoring task data collected by the simple network management protocol collector for the target Hub device, the method further comprises:
obtaining Hub line monitoring item data, dial testing global configuration parameters and alarm index data corresponding to the target Hub monitoring line; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are associated with second line quality index data, and the Hub line monitoring item data comprise the target Hub monitoring line access address and the opposite port interface address;
Filling a preset dial testing configuration template based on the Hub line monitoring item data, the dial testing global configuration parameters and the alarm index data to obtain second dial testing task configuration content;
and issuing second dial testing task configuration content to the target Hub equipment through a configuration automatic issuing tool, wherein the second dial testing task configuration content is used for obtaining the second line monitoring task data.
4. The line quality monitoring method of claim 1, wherein the first line quality indicator data comprises a first task delay;
after the step of obtaining the first line monitoring task data and the second line monitoring task data collected by the simple network management protocol collector for the target Hub device, the method includes:
determining a plurality of historical first line monitoring task data preceding the first line monitoring task data;
and obtaining a jitter value of the network delay based on the historical first task delay of the historical first line monitoring task data and the first task delay of the first line quality index data.
5. The method of line quality monitoring as set forth in claim 1, wherein the first line quality index data comprises a first packet loss rate and the second line quality index data comprises a second packet loss rate;
The step of performing line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data includes:
judging whether the first packet loss rate is equal to a preset interrupt threshold value or not;
if the first packet loss rate is equal to a preset interrupt threshold, judging whether the second packet loss rate is equal to the preset interrupt threshold;
and if the second packet loss rate is not equal to a preset interruption threshold value, determining the target Spoke monitoring line as a fault line, and pushing a line interruption alarm event.
6. The method for monitoring line quality according to claim 5, wherein after the step of determining whether the first packet loss rate is equal to a preset interruption threshold, the method further comprises:
if the first packet loss rate is not equal to a preset interruption threshold value, judging whether the first line quality index data is larger than a preset alarm threshold value or not;
and if the first line quality index data is larger than the preset alarm threshold value, pushing a super-threshold alarm event corresponding to the first line quality index data aiming at the target Spoke monitoring line.
7. The line quality monitoring method of claim 6, wherein after the step of determining whether the first line quality indicator data is greater than a preset alarm threshold, the method further comprises:
If the first line quality index data is smaller than or equal to the preset alarm threshold value, inquiring all historical super-threshold alarm events corresponding to the first line quality index data based on the target Hub monitoring line access address and the equipment interface address of the target Spoke monitoring line;
and if the query result is not null, clearing all the historical super-threshold alarm events, and pushing the super-threshold recovery event corresponding to the first line quality index data aiming at the target Spoke monitoring line.
8. A line quality monitoring device, the device comprising:
the acquisition object determining and task configuring module is used for determining target Hub equipment from Hub monitoring lines associated with target Spoke monitoring lines of Hub-Spoke networking, and configuring first dial testing task configuration content for the target Hub equipment;
the monitoring task data acquisition module is used for acquiring first line monitoring task data and second line monitoring task data which are acquired by the simple network management protocol acquisition unit aiming at the target Hub equipment;
and the monitoring task data analysis module is used for carrying out line monitoring on the target Spoke monitoring line according to the first line monitoring task data and the second line monitoring task data.
9. A line quality monitoring device, the device comprising: a memory, a processor and a line quality monitoring program stored on the memory and executable on the processor, the line quality monitoring program being configured to implement the steps of a line quality monitoring method as claimed in any one of claims 1 to 7.
10. A computer readable storage medium, characterized in that it has stored thereon a line quality monitoring program, which when executed by a processor, implements the steps of a line quality monitoring method according to any of claims 1 to 7.
CN202311340992.8A 2023-10-16 2023-10-16 Line quality monitoring method, device, equipment and storage medium Pending CN117675628A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311340992.8A CN117675628A (en) 2023-10-16 2023-10-16 Line quality monitoring method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311340992.8A CN117675628A (en) 2023-10-16 2023-10-16 Line quality monitoring method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN117675628A true CN117675628A (en) 2024-03-08

Family

ID=90067046

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311340992.8A Pending CN117675628A (en) 2023-10-16 2023-10-16 Line quality monitoring method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN117675628A (en)

Similar Documents

Publication Publication Date Title
JP3510658B2 (en) Network analysis method
US7562140B2 (en) Method and apparatus for providing trend information from network devices
US7120678B2 (en) Method and apparatus for configurable data collection on a computer network
US7783744B2 (en) Facilitating root cause analysis for abnormal behavior of systems in a networked environment
US6658367B2 (en) System for time-bucketing of baselined data collector data
US20030225876A1 (en) Method and apparatus for graphically depicting network performance and connectivity
CN103081407A (en) Failure analysis device, and system and method for same
WO2004079553A2 (en) System, method and model for autonomic management of enterprise applications
GB2418799A (en) Managing network slowdown by identifying a hop along a path which exceeds a hop limit within the path.
WO2019006008A1 (en) Apparatus and method for monitoring network performance of virtualized resources
WO2018010176A1 (en) Method and device for acquiring fault information
JP2004005085A (en) Storage network performance measuring system
WO2019006018A1 (en) Apparatus and method for establishing baseline network behavior and producing reports therefrom
CN114328107A (en) Monitoring method and system for optomagnetic fusion storage server cluster and electronic equipment
US20100036943A1 (en) Method of network management
CN117675628A (en) Line quality monitoring method, device, equipment and storage medium
JP3598394B2 (en) Service management method and device
US8639795B2 (en) Adaptive data acquisition for a network or services management system
JP5974905B2 (en) Response time monitoring program, method, and response time monitoring apparatus
JP4299210B2 (en) Network monitoring method and apparatus
CN113485891A (en) Service log monitoring method and device, storage medium and electronic equipment
CN102567470A (en) System-level performance data processing method and equipment utilizing same
CN112181929A (en) Cloud management platform log processing method and device, electronic device and storage medium
CN117354186A (en) Network line quality monitoring method, device, equipment and storage medium
CN111585819A (en) Distribution network communication equipment fault analysis method and system

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