CN112953740B - Method and device for monitoring route information - Google Patents
Method and device for monitoring route information Download PDFInfo
- Publication number
- CN112953740B CN112953740B CN201911255643.XA CN201911255643A CN112953740B CN 112953740 B CN112953740 B CN 112953740B CN 201911255643 A CN201911255643 A CN 201911255643A CN 112953740 B CN112953740 B CN 112953740B
- Authority
- CN
- China
- Prior art keywords
- route
- information
- routing
- data network
- change information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000012544 monitoring process Methods 0.000 title claims abstract description 31
- 230000008859 change Effects 0.000 claims abstract description 116
- 238000004590 computer program Methods 0.000 claims description 10
- 238000003860 storage Methods 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 27
- 238000012545 processing Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000007689 inspection Methods 0.000 description 7
- 238000012806 monitoring device Methods 0.000 description 7
- 238000012216 screening Methods 0.000 description 6
- 241000721662 Juniperus Species 0.000 description 5
- 230000002354 daily effect Effects 0.000 description 3
- 230000003203 everyday effect Effects 0.000 description 3
- 101100136092 Drosophila melanogaster peng gene Proteins 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000005304 joining Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000013139 quantization Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a method and a device for monitoring route information, wherein the method comprises the following steps: periodically collecting the route information of each route device in the data network and storing the route information as a corresponding route snapshot file; comparing the next hop network addresses corresponding to the same destination network segment according to the route snapshot files of the adjacent two periods; determining route change information of each routing device in the data network according to the comparison result; and outputting the route change information of each routing device in the data network. According to the application, based on the periodically collected and stored route information snapshot file, the route change information of each route device in the data network is monitored, and the route receiving device for specially collecting the route information is not required to be deployed, so that the equipment investment cost can be greatly reduced.
Description
Technical Field
The present application relates to the field of data networks, and in particular, to a method and an apparatus for monitoring routing information.
Background
This section is intended to provide a background or context to the embodiments of the application that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
In the data network, the routing device is used for connecting two or more hardware devices of the network, and can analyze the destination IP address contained in the data packet, search the routing table, and then forward the data packet to the destination IP address in an optimal path. Its reliability directly influences the data transmission of the data network.
At present, data network faults caused by routing anomalies occur occasionally, and once the faults occur, the influence surface is larger. The conventional route monitoring needs to deploy route receiving equipment, and is realized by adopting a mode of making neighbor receiving route (BGP) with a route emitter (RR) or joining in a subnet receiving route (IGP), and the route monitoring mode leads to higher equipment investment cost.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the application provides a method for monitoring route information, which is used for solving the technical problem that the existing route monitoring scheme needs to deploy route receiving equipment to receive the route information, so that the equipment investment cost is high, and comprises the following steps: periodically collecting the route information of each route device in the data network and storing the route information as a corresponding route snapshot file; comparing the next hop network addresses corresponding to the same destination network segment according to the route snapshot files of the adjacent two periods; determining route change information of each routing device in the data network according to the comparison result; outputting route change information of each routing device in the data network;
outputting route change information of each routing device in the data network, including: outputting route change information of each routing device in the data network according to various modes aiming at different scene demands;
outputting route change information of each routing device in the data network according to various modes aiming at different scene demands, wherein the route change information comprises: full-scale route change information of the data network or route change information of single routing equipment in the data network;
periodically collecting the route information of each route device in the data network, storing the route information as corresponding route snapshot files, and comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of two adjacent periods, wherein the method comprises the following steps: and (3) regularly storing route snapshots by taking equipment as a unit, carrying out route comparison, generating a change history when the route is newly added, reduced and changed, presenting the route snapshots according to time granularity or equipment dimension on a page, storing the snapshots of the day before by the route snapshots actively initiated by the page for comparison, and feeding back the comparison condition in the form of the page.
The embodiment of the application also provides a device for monitoring the route information, which is used for solving the technical problem that the equipment investment cost is high because the route receiving equipment is required to be deployed to receive the route information in the existing route monitoring scheme, and comprises the following steps: the route snapshot acquisition module is used for periodically acquiring the route information of each route device in the data network and storing the route information as a corresponding route snapshot file; the route information comparison module is used for comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of the adjacent two periods; the route change information determining module is used for determining route change information of each routing device in the data network according to the comparison result; the route change information output module is used for outputting route change information of each routing device in the data network;
outputting route change information of each routing device in the data network, including: outputting route change information of each routing device in the data network according to various modes aiming at different scene demands;
outputting route change information of each routing device in the data network according to various modes aiming at different scene demands, wherein the route change information comprises: full-scale route change information of the data network or route change information of single routing equipment in the data network;
periodically collecting the route information of each route device in the data network, storing the route information as corresponding route snapshot files, and comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of two adjacent periods, wherein the method comprises the following steps: and (3) regularly storing route snapshots by taking equipment as a unit, carrying out route comparison, generating a change history when the route is newly added, reduced and changed, presenting the route snapshots according to time granularity or equipment dimension on a page, storing the snapshots of the day before by the route snapshots actively initiated by the page for comparison, and feeding back the comparison condition in the form of the page.
The embodiment of the application also provides a computer device which is used for solving the technical problem that the prior route monitoring scheme needs to deploy route receiving equipment to receive route information, so that the equipment investment cost is high.
The embodiment of the application also provides a computer readable storage medium for solving the technical problem that the prior route monitoring scheme needs to deploy route receiving equipment to receive route information, which results in higher equipment investment cost.
In the embodiment of the application, the routing information of each routing device in the data network is periodically collected and stored as the corresponding routing snapshot file, so that the next hop network address corresponding to the same destination network segment can be compared according to the routing snapshot files of two adjacent periods, the routing change information of each routing device in the data network can be determined according to the comparison result, and finally the routing change information of each routing device in the data network is output.
According to the embodiment of the application, the route change information of each routing device in the data network is monitored based on the periodically collected and stored route information snapshot file, and the route receiving device for collecting the route information is not required to be deployed, so that the equipment investment cost can be greatly reduced.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
fig. 1 is a flowchart of a method for monitoring route information according to an embodiment of the present application;
fig. 2 is a schematic diagram of vrf information of a cisco 76-series device provided in an embodiment of the present application;
FIG. 3 is a schematic diagram of routing table information of a Cisco 76-series device according to an embodiment of the present application;
FIG. 4 is a schematic diagram of routing information provided in an embodiment of the present application in which a Cisco 76 series device generates a reduction in the number of next hop addresses of the same destination network segment;
fig. 5 is a schematic diagram of route information of a cisco 76-series device with a change of a next hop address of the same destination network segment according to an embodiment of the present application;
fig. 6 is a schematic diagram of route information of a cisco 76-series device with a destination network segment missing in the embodiment of the present application;
FIG. 7 is a schematic view of vpn instance information of a device of the NE series according to an embodiment of the present application;
fig. 8 is a schematic diagram of routing table information of a NE series device according to an embodiment of the present application;
fig. 9 is a schematic diagram of route information provided in the embodiment of the present application, in which the NE-series device generates a reduction in the number of next hop addresses of the same destination network segment;
fig. 10 is a schematic diagram of routing information provided in the embodiment of the present application, where the next hop address of the same destination network segment changes for NE series devices;
fig. 11 is a schematic diagram of route information of destination network segment missing of NE series devices provided in an embodiment of the present application;
fig. 12 is a vrf information schematic diagram of an ericsson SE series device according to an embodiment of the present application;
fig. 13 is a context information schematic diagram of an ericsson SE series device provided in an embodiment of the present application;
fig. 14 is a schematic diagram of routing table information of an ericsson SE series device according to an embodiment of the present application;
fig. 15 is a schematic diagram of routing information of change of a next hop address of the same destination network segment of an ericsson SE series device provided in an embodiment of the present application;
fig. 16 is a schematic diagram of route information of destination network segment missing of ericsson SE series equipment provided in an embodiment of the present application;
fig. 17 is a schematic diagram of a route change information query page according to an embodiment of the present application;
fig. 18 is a schematic diagram of an instant route acquisition and comparison operation page provided in an embodiment of the present application;
fig. 19 is a schematic diagram of an instant route acquisition comparison result display page provided in an embodiment of the present application;
fig. 20 is a schematic diagram of a monitoring device for route information according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present application and their descriptions herein are for the purpose of explaining the present application, but are not to be construed as limiting the application.
In the description of the present specification, the terms "comprising," "including," "having," "containing," and the like are open-ended terms, meaning including, but not limited to. The description of the reference terms "one embodiment," "a particular embodiment," "some embodiments," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The order of steps involved in the embodiments is illustrative of the practice of the application, and is not limited and may be suitably modified as desired.
In the embodiment of the present application, a method for monitoring routing information is provided, and fig. 1 is a flowchart of a method for monitoring routing information provided in the embodiment of the present application, as shown in fig. 1, where the method may include the following steps:
s101, periodically collecting the route information of each route device in the data network and storing the route information as a corresponding route snapshot file.
It should be noted that, the data network in the embodiment of the present application may be, but is not limited to, a core network, a bearer network, and the like.
Optionally, the embodiment of the application can log in each routing device in the data network periodically in a command line mode, collect the routing information of each routing device and store the routing information as a corresponding routing snapshot file.
S102, comparing the next hop network addresses corresponding to the same destination network segment according to the route snapshot files of two adjacent periods.
Because the route information contains the destination IP address, when the route snapshot files of two periods are compared, only whether the network address of the next hop (namely, the next hop IP address) corresponding to the same destination network segment is changed or not is needed to be compared.
S103, determining the route change information of each routing device in the data network according to the comparison result.
In an alternative embodiment, the step S103 may determine the newly added, reduced or modified route change information in the data network according to the route information comparison result of all the routing devices in the adjacent two periods.
In another alternative embodiment, S103 may determine the route change information of the single routing device according to the route information comparison result of the single routing device in two adjacent periods.
S104, outputting the route change information of each route device in the data network.
It should be noted that, for different scene requirements, the route change information of each routing device in the data network may be output in multiple manners, for example, the route change information may be the total route change information of the data network, or the route change information of a single routing device in the data network.
As an alternative embodiment, the step S104 may include the following steps: receiving a routing query instruction, wherein the routing query instruction is used for specifying any one of the following query conditions: data network information, routing equipment information, routing change types, and comparison time; and outputting the route change information of each routing device in the data network according to the route inquiry command.
It can be seen from the foregoing that, by periodically collecting the routing information of each routing device in the data network and storing the routing information as the corresponding routing snapshot file, the monitoring method for the routing information provided by the embodiment of the present application can compare the next hop network addresses corresponding to the same destination network segment according to the routing snapshot files of two adjacent periods, so as to determine the routing change information of each routing device in the data network according to the comparison result, and finally output the routing change information of each routing device in the data network.
According to the route information monitoring method provided by the embodiment of the application, the route change information of each route device in the data network is monitored based on the periodically collected and stored route information snapshot file, and the route receiving device for collecting the route information is not required to be deployed, so that the equipment investment cost can be greatly reduced.
In an optional embodiment, the method for monitoring routing information provided by the embodiment of the present application may further include the following steps: collecting the route information of each route device at the current moment and storing the route information as a corresponding route snapshot file; obtaining a route snapshot file of each route device at the same time of history; comparing the destination network segment and the next hop network address corresponding to each routing device at the two moments according to the routing snapshot files of the same moment of the current moment and the history of each routing device; determining real-time route change information of each routing device in the data network according to the comparison result; and outputting the real-time route change information of each routing device in the data network. By the embodiment, the routing information of each routing device in the data network is monitored in real time.
The following describes embodiments of the present application in detail using a core network and a carrier network as examples.
Because many routing devices in the data network are provided, in the specific implementation process, the routing information concerned can be carded by taking the service as a unit for the core network (CMNET) and the carrier network, the routing information concerned is periodically collected (for example, in a unit of one hour), the routing information concerned is stored in a warehouse to be used as a routing snapshot, the latest routing snapshot is compared with the routing snapshot collected and stored in the earlier stage in the warehouse, whether the newly added, reduced or changed routing device exists is compared, and the relevant information of the specifically added, reduced or changed routing device can be output. Optionally, manual intervention may be supported for the critical monitoring route, requiring manual confirmation of the process and recording of the corresponding handler.
Traffic route combing logic:
(1) Core network:
(1) BR router (core router) collection logic: after the whole network route is collected, the eastern network letter game route and the Peng doctor game route and the group route are eliminated.
A. The collection command is as follows:
all routes are collected:
juniper：show route table inet.0；
hua is & Hua San:
display ip routing；
routing to be excluded:
oriental network letter game route
juniper：show route community 64510:56040table inet.0；
The process is as follows: display bgp routing-Table communication 64510:56040;
# Peng doctor game route
juniper：show route community 65050:56040table inet.0；
The process is as follows: display bgp routing-Table communication 65050:56040;
group # routing
juniper：show route aspath-regex".*9808.*"table inet.0；
The process is as follows: display bgp routing-table|include 9808.
B. Examples of routes are as follows:
in the above routing example, the bold portion is the destination route and the underlined portion is the next hop address. Exclusion routing:
in the routing example described above, the bolded portion is a route that needs to be excluded.
(2) CR router (ground outlet router) collection logic: the device full-scale route is directly collected, the route is collected without being excluded, and the next hop is taken as the attribute of the route.
A. The collection command is as follows:
collecting all routes
juniper: show route table inet.0 Hua is & Hua three: display ip routing.
B. Examples of routes are as follows:
the process is as follows:
in the above routing example, the bold portion is the destination route and the underlined portion is the next hop address.
(II) carrying network:
(1) cisco 76 series equipment
A. View vrf example:
operation command: show ip vrf;
inspection criteria: executing the command "show ip vrf" obtains all vrf information of the device, as shown in fig. 2, vrf information includes Name, default RD, interfaces, and only attention needs to be paid to Name, where Name includes all vrf instance names of the device.
B. Obtaining route table information of VPN and storing:
operation command: show ip route vrf ChinaMobile _GD_Gb;
inspection criteria: after acquiring vrf Name, the routing information can be acquired by inputting show ip route vrf +Name. As shown in fig. 3, after executing the command "show ip route vrf ChinaMobile _gd_gb", the routing table information of the child_gd_gb VPN can be acquired, and then the acquired VPN routing table is stored.
C. Collecting and storing a routing table of the public network:
Show ip route。
D. the routing table for each vrf instance is collected and stored.
E. Comparing the vrf routing table stored every day with the public network IP routing table to obtain the difference.
The comparison is made by daily stored routes, such as yesterday's route table and today's route table. When in comparison, only the information of the destination network segment and the next IP address in the routing table is required to be subjected to difference comparison.
First difference case: the route varies.
The next hop IP address of the destination network segment of the route table today (IP following the via field) is compared with the next hop IP address of the destination network segment of the route table yesterday, and if there is a change in the next hop exit (e.g., the number of next hop addresses of the same destination network segment is reduced or changed), the route is considered to be changed. FIG. 4 illustrates routing information for a reduced number of next hop addresses for the same destination network segment; fig. 5 shows the routing information for the next hop address change for the same destination network segment.
Second difference case: the route is lost.
Comparing the network segment of the route table of today with the network segment of the route table of yesterday, and finding that the network segment of the route table of today is missing, and considering that the route has change. Fig. 6 shows the missing routing information for the destination network segment.
A. Viewing a device VPN instance;
operation command: display ip vpn-instance;
inspection criteria: executing the command "display ip VPN-Instance" obtains all the VPN Instance information of the device, and as shown in fig. 7, the VPN Instance information includes VPN-Instance names, RD and Address-family, and only "VPN-Instance Name" needs to be concerned, and the VPN-Instance Name includes all the VPN Instance names of the device.
B. Obtaining and storing the route table information of VPN;
operation command: display ip routing-table vpn-instance ChinaMobile _GD_Gb;
inspection criteria: after acquiring the vpn Name, executing a command of display ip routing-table vpn-instance+name to acquire the routing information. As shown in fig. 8, executing the command "display ip routing-table VPN-instance ChinaMobile _gd_gb", the party may obtain the routing table information of the child_gd_gb VPN.
C. Collecting and storing a public network IP routing table:
Display ip routing-table。
D. collecting and storing a routing table of each VPN instance;
E. and comparing the VPN routing tables stored every day to obtain the routing difference.
The comparison is made by daily stored routes, such as yesterday's route table and today's route table. In contrast, only the information of Destination/Mask (e.g., 10.126.3.0/26) and NextHop (i.e., next hop address information) in the routing table need be subjected to differential comparison.
First difference case: the route varies.
The next IP address of the route table destination network segment of today is compared with the next IP address of the route table destination network segment of yesterday. The next hop of the today's routing table Destination/Mask is compared with the next hop of the yesterday's routing table Destination/Mask, and if there is a change in the next hop (the number of next hop addresses to the same Destination network segment is reduced or changed), the route is considered to be changed. Fig. 9 shows a case where the number of next hop addresses of the same destination network segment is reduced; fig. 10 shows a schematic diagram of routing information for a next hop address change of the same destination network segment.
Second difference case: the route is lost.
Comparing the today's route table Destination/Mask with the yesterday's route table Destination/Mask, and finding that the today's Destination/Mask network segment is missing, and considering that the route has a change. Fig. 11 shows the case of a destination network segment missing.
(3) Ericsson SE series device:
A. view vrf instance
Operation command: show context all;
inspection criteria: executing the command "show context all" obtains all context information of the device, as shown in fig. 12, the context information includes context name, context ID, VPN-Rd, and only the context name needs to be concerned, and the context name includes all context names of the device.
B. Entering a context corresponding to VPN:
operation command: context ChinaMobile _iups_media;
inspection criteria: after the Context Name is obtained according to the first step, inputting 'context+Context Name', and entering the corresponding Context. As shown in fig. 13, executing "context ChinaMobile _iups_media", the party may enter context of the child_iups_media.
C. Obtaining routing table information:
operation command: show ip route;
inspection criteria: after executing "show ip route", the routing table is shown in fig. 14, and the ericsson SE800 routing table contains routing types, networks, next Hop, dist, metric, uptime, interface, and then the whole routing table information needs to be stored.
D. And collecting and storing the routing table of each context.
E. The difference is obtained by comparing the context routing tables stored every day.
The comparison is made by daily stored routes, such as yesterday's route table and today's route table. In comparison, only the information of Network and Next Hop in the routing table is required to be subjected to difference comparison.
First difference case: route variation
The Next Hop of today's routing table network is compared with the Next Hop of yesterday's routing table network, and if there is a change in the Next Hop address, the route is considered to be changed. Fig. 15 shows a case where the next hop address of the same destination network segment is changed.
Second difference case: route loss
Comparing the network segment under the yesterday routing table network with the network segment of the today network, and finding that the network segment of the today network is missing, wherein the routing is considered to be changed. Fig. 16 shows the case of a destination segment missing.
Tables 1 to 3 show the relevant table structures, and table 1 shows a device full-scale routing table (DevRouteInfo table); table 2 shows a device route change table (DevRouteChangeH table) with hour granularity; table 3 shows the immediate acquisition device route change table (devroutectchange im table).
Table 1 device full routing table (DevRouteInfo table)
Table 2 hour granularity device route Change Table (DevRouteChange H Table)
For the comparison of routing snapshots at hour granularity, the acquisition processing logic is as follows:
for example, route collection is performed once on a device (a carrier network, CMNET) at intervals of one hour (time points are ordered to be one hour) (the output time is long, concurrent execution can be considered, and the number of concurrent events is according to actual conditions) and route comparison is performed in a unit of a single unit (the result of the previous hour is obtained from the DevRouteInfo table and the corresponding device value of the previous day is obtained), and if the comparison result finds that there is a new increase or decrease, data is inserted into the devroutecange table (state 1). And finally updating the DevRouteInfo table to the current result (the acquisition time is required to be regulated to the current hour).
Special case treatment:
(1) if the device in the previous hour has no data, the DevRouteInfo is directly updated without comparison.
(2) And the method supports multiple execution within one hour, the comparison is still carried out in the previous hour, and DevRouteInfo, devRouteChangeH all clears the data of the current hour and then enters the data.
(3) The full scale retains seven days of data at most, delete seven days of information before DevRouteInfo, change the table and retain one month of data
(4) The change types are newly increased, reduced and modified. The modification is that the route has not changed but has changed corresponding to the next hop (newly added next hop is reduced).
(4) And judging the professional and ground information according to the node where the equipment is located.
Table 3 instant acquisition device route Change Table (DevRouteChangeIM Table)
For instant route acquisition comparison, the acquisition processing logic is as follows:
collecting as required, and receiving scheduling parameters of a foreground: the device ID of the time (accurate to seconds) is collected, the device is logged in on the device in real time to collect the route information, and the route information is compared with the route information of the device at 22:00 yesterday. The comparison result information is input into a DevRouteHangeIM table, and the table has no state and can process the human information only by feeding back the comparison result. The acquisition time is entered into the foreground schedule. The acquisition logic is the same as the first requirement. The collected routing volume results also enter the DevRouteInfo table.
Fig. 17 shows a schematic diagram of a routing change information query page, the functions including but not limited to:
(1) the query function of the variable route is realized through condition screening;
(2) the network element can be manually input or can support equipment selection, and the equipment selection module is called and the equipment is singly selected when the selection is clicked.
Manual input supports fuzzy matching;
(3) the route change type drop-down supports ADD, DEL, MOD values of new ADD, decrease, modify, and correspond to the devroutechangehold table ChangeType. And may provide all types of choices (null or all, i.e., all types);
(4) the filtering of professions and places needs to provide screening according to the value actually existing in the DevRouteChangH table, and the screening is not provided when the corresponding field in the table has no value;
(5) the processing state pull-down provides 1, 2 and 0 values of the Status of the DevRouteChange H table for screening during unprocessed, processed and processed completion;
(6) the comparison time provides a screening to hour, defaulting to give the time of the current hour of the day
(7) Clicking and modifying editable processing state and remark information in the queried result, acquiring current processor ID if the processing state is modified to be processed, and inputting the current processor ID into a processor field
(8) Clicking export execl can export the results of the current query.
Fig. 18 is a schematic view of an instant routing acquisition comparison operation page provided in the embodiment of the present application, and fig. 19 is a schematic view of an instant routing acquisition comparison result display page provided in the embodiment of the present application, as shown in fig. 18 and fig. 19, including but not limited to the following functions:
(1) query function capable of realizing history instant acquisition and comparison result through condition screening
(2) The network element can be manually input or can support equipment selection, and the equipment selection module is called and the equipment is singly selected when the selection is clicked. Manual input supports fuzzy matching.
(3) The route change type drop-down supports ADD, DEL, MOD values of new ADD, decrease, modify, and correspond to the devroutectchange im table ChangeType. And may provide all types of choices (null or all, i.e., all types)
(4) The comparison time is accurate to the day, defaulting to the day. And inquiring all instant acquisition comparison results of the current day after selection.
(5) The instant acquisition and comparison of the click route are carried out, the scheduling background program triggers the instant route information acquisition of the equipment, and the parameter is the equipment id of the current time (accurate to seconds).
(6) And waiting for a background acquisition comparison result, if the background acquisition comparison result fails, returning to acquisition failure, and capturing the entry and exit of the background stdout as a failure reason to be presented. If the comparison result is successful, the comparison result is obtained from the DevRouteChangeIM table according to the acquisition time and is presented.
(7) Clicking on export execl may export the current query result.
According to the embodiment of the application, the route snapshot is stored in a timing mode by taking the equipment as a unit, the route is compared, the route is newly increased and reduced, the change history is generated and presented on the page according to the time granularity or the dimension of the equipment and the like, the route snapshot initiated actively by the page is stored and compared with the snapshot of the previous day, and the comparison condition is fed back in the form of the page. Therefore, the embodiment of the application periodically checks the route change condition in a simple mode, does not need to deploy route receiving equipment, and can greatly reduce the equipment investment cost. Manual intervention is provided for points where changing routes are at risk to prevent the failure of a route anomaly.
It should be noted that, in the embodiment of the present application, the routing device includes, but is not limited to, BR (core router), CR (city outlet router), and carrier CE (service router), and the embodiment of the present application can perform full quantization collection for all routes including BGP, IGP, static, etc. of all routing devices in the network, so as to perform periodic differential comparison.
Based on the same inventive concept, the embodiment of the application also provides a device for monitoring the route information, as described in the following embodiment. Because the principle of solving the problem of the embodiment of the device is similar to that of the monitoring method of the route information, the implementation of the embodiment of the device can refer to the implementation of the method, and the repetition is omitted.
Fig. 20 is a schematic diagram of a monitoring device for route information according to an embodiment of the present application, where, as shown in fig. 20, the device may include: the system comprises a route snapshot acquisition module 201, a route information comparison module 202, a route change information determination module 203 and a route change information output module 204.
The route snapshot acquisition module 201 is configured to periodically acquire route information of each routing device in the data network, and store the route information as a corresponding route snapshot file; the route information comparison module 202 is configured to compare, according to the route snapshot files of two adjacent periods, the next hop network addresses corresponding to the same destination network segment; the route change information determining module 203 is configured to determine route change information of each routing device in the data network according to the comparison result; and the route change information output module 204 is used for outputting route change information of each routing device in the data network.
As can be seen from the above, the monitoring device for routing information provided by the embodiment of the present application periodically collects the routing information of each routing device in the data network through the routing information collection module 201, and stores the routing information as a corresponding routing snapshot file; comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of two adjacent periods through the route information comparison module 202; and determining the route change information of each routing device in the data network according to the comparison result by the route change information determining module 203, and finally outputting the route change information of each routing device in the data network by the route change information outputting module 204.
According to the route information monitoring device provided by the embodiment of the application, the route change information of each route device in the data network is monitored based on the periodically collected and stored route information snapshot file, and the route receiving device for collecting the route information is not required to be deployed, so that the equipment investment cost can be greatly reduced.
In an alternative embodiment, in the routing information monitoring apparatus provided in the embodiment of the present application, the routing information collection module 201 may be configured to log in each routing device in the data network periodically in a command line manner, collect routing information of each routing device, and store the routing information as a corresponding routing snapshot file.
In an alternative embodiment, in the routing information monitoring apparatus provided in the embodiment of the present application, the routing change information determining module 203 may be configured to determine, according to a comparison result of routing information of all routing devices in two adjacent periods, newly added, reduced or modified routing change information in the data network.
In an alternative embodiment, in the routing information monitoring apparatus provided in the embodiment of the present application, the routing change information determining module 203 may be configured to determine routing change information of a single routing device according to a routing information comparison result of the single routing device in two adjacent periods.
In an optional embodiment, in the monitoring device for route information provided by the embodiment of the present application, the route snapshot acquisition module 201 is further configured to acquire route information of a current moment of each routing device, and store the route information as a corresponding route snapshot file; the route information comparison module 202 is further configured to obtain a route snapshot file of each routing device at the same time in history, and compare destination network segments and next hop network addresses corresponding to each routing device at the two times according to the route snapshot file of each routing device at the current time and the route snapshot file of each routing device at the same time in history; the route change information determining module 203 is further configured to determine real-time route change information of each routing device in the data network according to the comparison result; the route change information output module 204 is further configured to output real-time route change information of each routing device in the data network.
In an optional embodiment, in the monitoring device for routing information provided by the embodiment of the present application, the routing change information output module is further configured to receive a routing query instruction, and output, according to the routing query instruction, routing change information of each routing device in the data network, where the routing query instruction is configured to specify any one of the following query conditions: data network information, routing device information, routing change type, alignment time.
In the monitoring device for routing information provided in the embodiment of the present application, the data network may include, but is not limited to, at least one of the following: core network, bearer network.
The embodiment of the application also provides a computer device which is used for solving the technical problem that the prior route monitoring scheme needs to deploy route receiving equipment to receive route information, so that the equipment investment cost is high.
The embodiment of the application also provides a computer readable storage medium for solving the technical problem that the prior route monitoring scheme needs to deploy route receiving equipment to receive route information, which results in higher equipment investment cost.
In summary, the embodiments of the present application provide a method, an apparatus, a computer device, and a computer readable storage medium for monitoring routing information, which can achieve the following technical effects, but are not limited to: (1) simplifying route snapshot collection: by combing the concerned route of the professional content, the device is logged in periodically in a command line mode to collect the device route, and the device route is stored as a route snapshot, so that the cost is far lower than the cost of independently deploying a route receiver in a network; (2) routing snapshot full-vector comparison analysis: comparing the total routes with the collected route information in an hour period, and analyzing the new increase, decrease and change conditions of the routes and the routes with specific increase, decrease and change; (3) single device instant route comparison analysis: the method has the advantages that a single device is used as a dimension, instant route information acquisition can be triggered on a page, data of the previous day after the acquisition is compared, and the route change condition of the device is fed back.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the application, and is not meant to limit the scope of the application, but to limit the application to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the application are intended to be included within the scope of the application.
Claims (10)
1. A method for monitoring routing information, comprising:
periodically collecting the route information of each route device in the data network and storing the route information as a corresponding route snapshot file;
comparing the next hop network addresses corresponding to the same destination network segment according to the route snapshot files of the adjacent two periods;
determining route change information of each routing device in the data network according to the comparison result;
outputting route change information of each routing device in the data network;
outputting route change information of each routing device in the data network, including: outputting route change information of each routing device in the data network according to various modes aiming at different scene demands;
outputting route change information of each routing device in the data network according to various modes aiming at different scene demands, wherein the route change information comprises: full-scale route change information of the data network or route change information of single routing equipment in the data network;
periodically collecting the route information of each route device in the data network, storing the route information as corresponding route snapshot files, and comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of two adjacent periods, wherein the method comprises the following steps: and (3) regularly storing route snapshots by taking equipment as a unit, carrying out route comparison, generating a change history when the route is newly added, reduced and changed, presenting the route snapshots according to time granularity or equipment dimension on a page, storing the snapshots of the day before by the route snapshots actively initiated by the page for comparison, and feeding back the comparison condition in the form of the page.
2. The method of claim 1, wherein periodically collecting routing information for each routing device in the data network and storing the routing information as a corresponding routing snapshot file, comprises:
and periodically logging in each routing device in the data network in a command line mode, collecting the routing information of each routing device, and storing the routing information as a corresponding routing snapshot file.
3. The method of claim 1, wherein determining route change information for each routing device in the data network based on the comparison comprises:
and determining newly added, reduced or modified route change information in the data network according to the route information comparison results of all the route devices in two adjacent periods.
4. The method of claim 1, wherein determining route change information for each routing device in the data network based on the comparison comprises:
and determining the route change information of the single routing equipment according to the route information comparison result of the single routing equipment in two adjacent periods.
5. The method of claim 1, wherein the method further comprises:
collecting the route information of each route device at the current moment and storing the route information as a corresponding route snapshot file;
obtaining a route snapshot file of each route device at the same time of history;
comparing the destination network segment and the next hop network address corresponding to each routing device at the two moments according to the routing snapshot files of the same moment of the current moment and the history of each routing device;
determining real-time route change information of each routing device in the data network according to the comparison result;
and outputting the real-time route change information of each routing device in the data network.
6. The method of claim 1, wherein outputting route change information for each routing device within the data network comprises:
receiving a routing query instruction, wherein the routing query instruction is used for specifying any one of the following query conditions: data network information, routing equipment information, routing change types, and comparison time;
and outputting the route change information of each routing device in the data network according to the route inquiry instruction.
7. The method of any of claims 1 to 6, wherein the data network comprises at least one of: core network, bearer network.
8. A monitoring apparatus for routing information, comprising:
the route snapshot acquisition module is used for periodically acquiring the route information of each route device in the data network and storing the route information as a corresponding route snapshot file;
the route information comparison module is used for comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of the adjacent two periods;
the route change information determining module is used for determining route change information of each routing device in the data network according to the comparison result;
the route change information output module is used for outputting route change information of each routing device in the data network;
outputting route change information of each routing device in the data network, including: outputting route change information of each routing device in the data network according to various modes aiming at different scene demands;
outputting route change information of each routing device in the data network according to various modes aiming at different scene demands, wherein the route change information comprises: full-scale route change information of the data network or route change information of single routing equipment in the data network;
periodically collecting the route information of each route device in the data network, storing the route information as corresponding route snapshot files, and comparing the next hop network address corresponding to the same destination network segment according to the route snapshot files of two adjacent periods, wherein the method comprises the following steps: and (3) regularly storing route snapshots by taking equipment as a unit, carrying out route comparison, generating a change history when the route is newly added, reduced and changed, presenting the route snapshots according to time granularity or equipment dimension on a page, storing the snapshots of the day before by the route snapshots actively initiated by the page for comparison, and feeding back the comparison condition in the form of the page.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of monitoring routing information according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program that executes the monitoring method of route information according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911255643.XA CN112953740B (en) | 2019-12-10 | 2019-12-10 | Method and device for monitoring route information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911255643.XA CN112953740B (en) | 2019-12-10 | 2019-12-10 | Method and device for monitoring route information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112953740A CN112953740A (en) | 2021-06-11 |
| CN112953740B true CN112953740B (en) | 2023-11-03 |
Family
ID=76225387
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911255643.XA Active CN112953740B (en) | 2019-12-10 | 2019-12-10 | Method and device for monitoring route information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112953740B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124811B (en) * | 2021-10-21 | 2023-08-01 | 中盈优创资讯科技有限公司 | Route leakage real-time monitoring method |
| CN115426295A (en) * | 2022-03-03 | 2022-12-02 | 北京润通丰华科技有限公司 | Automatic monitoring method for IDC internetwork routing abnormity |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5412654A (en) * | 1994-01-10 | 1995-05-02 | International Business Machines Corporation | Highly dynamic destination-sequenced destination vector routing for mobile computers |
| CN1581821A (en) * | 2003-08-15 | 2005-02-16 | 华为技术有限公司 | Key route information monitoring method based on virtual router redundant protocol |
| CN101247278A (en) * | 2007-08-06 | 2008-08-20 | 北京高信达网络科技有限公司 | Routing monitoring apparatus |
| CN104348672A (en) * | 2013-07-29 | 2015-02-11 | 中国电信股份有限公司 | Large-scale IP network BGP routing entry detection method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6982966B2 (en) * | 2000-04-10 | 2006-01-03 | Viasat, Inc. | Satellite routing protocol with dynamic IP addressing |
-
2019
- 2019-12-10 CN CN201911255643.XA patent/CN112953740B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5412654A (en) * | 1994-01-10 | 1995-05-02 | International Business Machines Corporation | Highly dynamic destination-sequenced destination vector routing for mobile computers |
| CN1581821A (en) * | 2003-08-15 | 2005-02-16 | 华为技术有限公司 | Key route information monitoring method based on virtual router redundant protocol |
| CN101247278A (en) * | 2007-08-06 | 2008-08-20 | 北京高信达网络科技有限公司 | Routing monitoring apparatus |
| CN104348672A (en) * | 2013-07-29 | 2015-02-11 | 中国电信股份有限公司 | Large-scale IP network BGP routing entry detection method and device |
Non-Patent Citations (2)
| Title |
|---|
| 基于下一跳变化的细粒度路由事件识别方法;郑萌等;《华中科技大学学报(自然科学版)》;20161015;第196-197页 * |
| 路由监控分析系统的设计和实现;唐敏等;《计算机科学》;20080125(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112953740A (en) | 2021-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7529192B2 (en) | System and method for correlating traffic and routing information | |
| US20170317899A1 (en) | Using traffic data to determine network topology | |
| CN111064635B (en) | Abnormal traffic monitoring method and system | |
| JP5331123B2 (en) | Various route server systems and devices | |
| CN112953740B (en) | Method and device for monitoring route information | |
| US20140164595A1 (en) | Firewall event reduction for rule use counting | |
| EP3101841B1 (en) | Method, system and computer readable medium for network management automation | |
| EP3364627B1 (en) | Adaptive session intelligence extender | |
| EP2993824A2 (en) | Fault monitoring in multi-domain networks | |
| US10038609B2 (en) | Network traffic analysis | |
| WO2011036663A2 (en) | Method and system for reconstructing transactions in a communication network | |
| US8782092B2 (en) | Method and apparatus for streaming netflow data analysis | |
| CN112468365A (en) | Data quality detection method, system and medium for network mirror flow | |
| CN112491609A (en) | System application architecture discovery method and system based on business service | |
| CN111106970B (en) | Data monitoring method and device, electronic equipment and readable storage medium | |
| EP2517410B1 (en) | Tracing support in a router | |
| US20050099958A1 (en) | Methods and systems for automated analysis of signaling link utilization | |
| CN108108289A (en) | A kind of cluster resource statistical method, system, device and readable storage system | |
| CN116760834A (en) | Load balancing method, system, equipment and storage medium | |
| JP5221594B2 (en) | Network monitoring apparatus, network monitoring method, and network monitoring program | |
| CN112835934B (en) | Query information acquisition method and device, electronic equipment and storage medium | |
| CN112714008B (en) | Network topology analysis method, device and storage medium | |
| CN114448868A (en) | Path scheduling method, device and equipment based on segmented routing strategy | |
| JP4871775B2 (en) | Statistical information collection device | |
| CN114528266B (en) | Method, system, device and storage medium for realizing database and cache consistency |
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 |