CN112565049A - Implementation method for intelligently maintaining vprn planning address based on collected data - Google Patents
Implementation method for intelligently maintaining vprn planning address based on collected data Download PDFInfo
- Publication number
- CN112565049A CN112565049A CN202011352612.9A CN202011352612A CN112565049A CN 112565049 A CN112565049 A CN 112565049A CN 202011352612 A CN202011352612 A CN 202011352612A CN 112565049 A CN112565049 A CN 112565049A
- Authority
- CN
- China
- Prior art keywords
- address
- vpn
- processing
- data
- collected 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5061—Pools of addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for realizing intelligent maintenance of a vprn planning address based on collected data, and relates to the technical field of intelligent communication. The method comprises the steps of VPN data processing and VPN address processing, wherein the VPN data processing step is to scan a VPN instance information table vpninstance at fixed time, associate an equipment table and a node table, and acquire relevant information of a local city where the equipment is located and a VPN instance to obtain an acquired data set A; comparing and matching the collected data in the processing set A one by one; and the VPN address processing step is to judge the VPN numbers in the set A, process the same VPN number address field together and group the same VPN number, and process the collected data of the same group one by one. The invention dynamically realizes the supplement and update of the vpn number and the vpn address information of the inventory data in the vpn service activation system by automatically comparing the actual three-layer vprn information on the existing network equipment, including the vpn number and the related address, with the inventory data managed in the system, thereby enhancing the vprn information management in various cities and improving the refinement degree of the vprn information.
Description
Technical Field
The invention belongs to the technical field of intelligent communication, and particularly relates to a method for realizing intelligent maintenance of a vprn planning address based on collected data.
Background
At present, a three-layer VPN (virtual private network) scheme is widely applied to a service provider to implement a virtual private network on a backbone network.
However, after three layers of vprn (Virtual Private Routed Networks) automatically open the work order service for a period of time, it is realized that the success rate of opening has a direct relationship with the management of the vpn number and the vpn address. Due to historical reasons, the problems that the data of the vpn service data is incomplete or not standardized exist in various cities and the like. It is difficult to collect complete and accurate business data from various cities. The user wants to automatically compare the data by automatically acquiring the configured service data on the online equipment. Finally, the purposes of completing the data of the whole province and dynamically managing the data and providing data support for the next network construction are achieved, and the purpose of fine management is achieved.
Disclosure of Invention
The invention aims to provide a method for realizing intelligent maintenance of a vprn planning address based on collected data, which can dynamically realize the supplement and update of vpn number and vpn address information of stock data in a vpn service activation system by automatically comparing the actual three-layer vprn information on the existing network equipment, including the vpn number and related addresses, with the stock data managed in the system and intelligently analyzing the three-layer vprn information, and solve the problems of insufficient management and refinement of the existing vprn information in various cities.
In order to solve the technical problems, the invention is realized by the following technical scheme:
the invention relates to a realizing method for intelligently maintaining a vprn planning address based on collected data, which comprises vpn data processing and vpn address processing;
the vpn data processing steps are as follows:
step S1: scanning a VPN (virtual private network) instance information table vpninstance at regular time, associating an equipment table and a node table, and acquiring relevant information of a city where equipment is located and a VPN instance to obtain an acquired data set A;
step S2: processing the collected data in the set A one by one, and comparing the rd value with the VPNNoInfo inventory data: vpninstance.rd vpnnoinfo.rd1 or vpnnoinforrd 2 were considered to match;
step S3: if a plurality of records are matched, skipping over and ending;
step S4: if a record is matched, and the state of the stock data is occupied: namely vpnnoinfo. status ═ 2, the record in set a is skipped and the next record is processed;
step S5: matching to a record, and the state of stock data is unoccupied: status 2, whether the acquired data and the stock data are matched or not is continuously judged;
if the cities are not matched, skipping the records in the set A, and ending;
if the local cities of the collected data and the stock data are matched: updating the stock data VPNNoInfo table by using the collected data;
step S6: if the records cannot be matched, adding a piece of vpn information into the stock table;
the vpn address processing comprises three vpn address processing types of processing an independent gateway address, processing a shared gateway address and processing a service address;
the processing step of processing the independent gateway address comprises the following steps:
step D11: scanning a Port ExtInfo table of a port expansion table at fixed time to acquire the collected vpn address information on the equipment, and associating an equipment table and a node table to acquire the name of a city to which the equipment belongs;
step D12: processing the collected data in the set A one by one, firstly judging the VPN number in the set A, and processing the VPN number address field together;
step D13: grouping the collected data set A according to the same vpn number, and processing the collected data of the same group one by one;
the processing step of processing the shared gateway address comprises the following steps:
step D21: scanning an address pool table at regular time to obtain an address and a gateway address mask, associating an equipment table and a node table, and obtaining a city name corresponding to equipment;
step D22: intercepting a digital part from a vpn example vpninstatnce field to obtain a vpn number;
step D23: obtaining a collected data set A by taking a record that the vpn number is not empty;
step D24: analyzing the acquisition state of each address segment under each address pool in the address pool;
step D25: processing the collected data in the set A, judging the VPN number in the set A, and processing the VPN number address field together;
step D26: comparing the collected data in the set A with the address of the shared gateway of the stock planning address of the same vpn number;
the processing step of processing the service address comprises the following steps:
step D31: scan static Address configuration Table the vpn instance vpninstance of the StaticRoute Table is not empty and IP! Associating the data of '0.0.0.0', and obtaining a city name corresponding to the equipment by the equipment table and the node table; intercepting a digital part from a vpninstance field to obtain a vpn number; obtaining an acquired data set A if the vpn number is not null;
step D32: processing the collected data in the set A one by one, firstly judging the vpn numbers in the set A, grouping the vpn numbers according to the same vpn number, and judging the same vpn number by the same method and the same unique gateway address;
step D33: and processing the collected data in the same vpn number one by one.
Preferably, in the step D11, the value of the vpn address information corresponding to the device is as follows: intercepting a digital part from a vpn example field of a PortExtInfo. vpninstance and port expansion table to obtain a vpn number; inquiring a device port address table DevPortAdddr according to the device iddeviceid and the port description portdescr to obtain a port address ipaddress and a mask address netmask; and (3) obtaining a collected data set A by taking the record that the vpn number is not empty, namely, only taking the address of which the port has the vpn and the standard vpn number to compare with the address of the storage volume vpn.
Preferably, in step D12, the method for determining the same VPN is to query the storage VPN information table vpnoninfo according to the VPN number;
if a record is inquired and the VPN opening area is not the urban area, calculating the same VPN by the same VPN number in different cities;
if one or more records are inquired and the VPN opening areas are all urban areas, calculating different VPNs by the same VPN number in different cities;
if the VPN opening area cannot be identified and the IP address cannot be compared and processed, recording the VPN opening area to an error log.
Preferably, in the step D13, the same group of collected data is processed item by item, and the start address and the end address of each collected address are calculated according to the address and the mask address; and comparing the address with the address which belongs to the same vpn number and is not the service address and is an independent gateway with planned inventory.
Preferably, in the step D24, a static address table is matched according to the device id and the address pool name to obtain a static occupied address, which is recorded as an occupied address; matching an address pool address field table according to the equipment id and the address pool name to obtain an available address and an address pool complete address field; the occupied address is subtracted from the available address, and the rest address segment is recorded as an idle address; the full address segment minus the available address, the remaining address, is marked as the lock address.
Preferably, in the step D26, the comparison result between the collected data in the set a and the inventory planning address sharing gateway address includes four types, which are respectively the collected planning address contained, the collected planning address partially intersected with the planning address, and no intersected address between the collected planning address and the collected planning address.
Preferably, in the step D33, the step of processing the collected data in the same vpn number one by one includes calculating the start address and the end address by using the static address and the mask; and (4) taking the service address in the storage planning address, and judging whether the acquisition address exists in the storage planning address.
The invention has the following beneficial effects:
the invention dynamically realizes the supplement and update of the vpn number and the vpn address information of the inventory data in the vpn service activation system by automatically comparing the actual three-layer vprn information including the vpn number and the related address on the existing network equipment with the inventory data managed in the system and intelligently analyzing, thereby enhancing the vprn information management of various cities and improving the refinement degree of the vprn information.
Of course, it is not necessary for any product in which the invention is practiced to achieve all of the above-described advantages at the same time.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of the vpn data processing of the present invention;
FIG. 2 is a flow diagram of independent gateway address processing and service address processing;
FIG. 3 is a flow diagram of shared gateway address processing;
FIG. 4 is a diagram illustrating comparison results of processing independent gateway addresses;
FIG. 5 is a diagram illustrating a comparison result of processing a shared gateway address;
fig. 6 is a diagram illustrating comparison results of processing service addresses.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-3, the present invention is a method for intelligently maintaining vprn planning address based on collected data, including vpn data processing and vpn address processing;
the steps of vpn data processing are as follows:
step S1: scanning a VPN (virtual private network) instance information table vpninlance at fixed time, associating an equipment table, a node table and the like, and acquiring relevant information of a city where equipment is located and a VPN instance to obtain an acquired data set A;
step S2: processing the collected data in the set A one by one, and comparing the rd value with the VPNNoInfo inventory data: vpninstance.rd vpnnoinfo.rd1 or vpnnoinforrd 2 were considered to match;
step S3: if a plurality of records are matched, skipping over and ending;
step S4: if a record is matched, and the state of the stock data is occupied: namely vpnnoinfo. status ═ 2, the record in set a is skipped and the next record is processed;
step S5: matching to a record, and the state of stock data is unoccupied: status 2, whether the acquired data and the stock data are matched or not is continuously judged;
if the cities are not matched, skipping the records in the set A, and ending;
if the local cities of the collected data and the stock data are matched: updating the stock data VPNNoInfo table by using the collected data;
step S6: if the records cannot be matched, adding a piece of vpn information into the stock table;
the vpn address processing comprises three vpn address processing types of processing an independent gateway address, processing a shared gateway address and processing a service address;
the processing step of processing the independent gateway address comprises the following steps:
step D11: scanning a Port ExtInfo table of a port expansion table at fixed time to acquire acquired vpn address information on equipment, and associating an equipment table, a node table and the like to acquire a city name of the equipment;
step D12: processing the collected data in the set A one by one, firstly judging the VPN number in the set A, and processing the VPN number address field together;
step D13: grouping the collected data set A according to the same vpn number, and processing the collected data of the same group one by one;
the processing step of processing the shared gateway address comprises the following steps:
step D21: scanning an address pool DevColIPPool table at fixed time to obtain addresses (startip and endip) and a gateway address (gateway) mask, associating a device table and a node table, and obtaining a city name corresponding to a device;
step D22: intercepting a digital part from a vpn example vpninstatnce field to obtain a vpn number;
step D23: obtaining a collected data set A by taking a record that the vpn number is not empty;
step D24: analyzing the acquisition state of each address segment under each address pool in the address pool;
step D25: processing the collected data in the set A, judging the VPN number in the set A, and processing the VPN number address field together;
description of the drawings: judging the same VPN number, sharing the gateway separately, and grouping according to the (VPN number) in case 1 and case 2, in case 1; case 2, grouping according to { local city + VPN number };
step D26: comparing the collected data in the set A with the address of the shared gateway of the stock planning address of the same vpn number;
1. taking the start (devcolpotol. startip) and end (devcolpipool. end) addresses of the collected data in set a;
2. an address of a shared gateway (IsGWShared ═ Y ') and (IPPrefixType ═ 0') in the inventory planning address and belonging to [ the same vpn number ], and a start-end address is calculated using the address field and the prefix;
3. comparing according to the starting address and the ending address;
processing the service address:
step D31: scan static Address configuration Table the vpn instance vpninstance of the StaticRoute Table is not empty and IP! Associating the data of '0.0.0.0', and obtaining a city name corresponding to the equipment by the equipment table and the node table; intercepting a digital part from a vpninstance field to obtain a vpn number; obtaining an acquired data set A if the vpn number is not null;
step D32: processing the collected data in the set A one by one, firstly judging the vpn numbers in the set A, grouping the vpn numbers according to the same vpn number, and judging the same vpn number by the same method and the same unique gateway address;
step D33: and processing the collected data in the same vpn number one by one.
In step D11, the value of the vpn address information corresponding to the device is as follows: intercepting a digital part from a vpn example field of a PortExtInfo. vpninstance and port expansion table to obtain a vpn number; inquiring a device port address table DevPortAdddr according to the device iddeviceid and the port description portdescr to obtain a port address ipaddress and a mask address netmask; and (3) obtaining a collected data set A by taking the record that the vpn number is not empty, namely, only taking the address of which the port has the vpn and the standard vpn number to compare with the address of the storage volume vpn.
In step D12, the same VPN is determined by querying the storage VPN information table VPNoInfo based on the VPN number;
if a record is inquired and the VPN opening area is not a City area (VPNNoInfo. OpenArea < > City), calculating the same VPN by the same VPN number in different cities, and marking as the condition 1;
if one or more records are inquired and the VPN open areas are City areas (vpnnoinfo. openarea ═ City), the same VPN number in different cities calculates different VPNs and is recorded as the condition 2;
otherwise, an error is reported: if the VPN opening area cannot be identified and the IP address cannot be compared and processed by inquiry, recording the VPN opening area to an error log;
for the case 1, address data is used as the same VPN number for searching and comparing;
for the case 2, the address data is used as the same VPN number to search and compare according to the city and the VPN number of the local city.
In step D13, the same group of collected data is processed item by item, and the start and end addresses of each collected address are calculated according to the address and the mask address; and compares with the independent gateway (IsGWShared ═ N ') and the non-business address (IPPrefixType ═ 0') belonging to the same vpn number.
As shown in fig. 4, the comparison results have four possibilities:
(A) the planning address is contained by the acquisition address;
(B) the acquisition address is contained by the planning address;
(C) collecting partial intersection addresses of the addresses and the planning addresses;
(D) the acquisition address and the planning address do not have any intersecting address;
for the case (A), firstly, judging the address pool range corresponding to the original stock planning address: ipprefix, if the address pool range contains the acquisition address, it indicates that the address pool range is correct
If the stock planning address state of the intersection part is not idle: VPNIPPoolDetail, status < >0, the state of the data storage cannot be modified, the intersection part is separated from the acquisition address, the rest part is newly added and recorded in a VPNIPPoolDetail table, the status is 2 (occupied),
if the stock planning address state of the intersection part is idle: status 0 in vpnippooldetail,
1. the original stock plan address is deleted,
2. recording VPNIPPoolDetail table with new memory of collection address, status 2 (occupied)
Ipprefix, if the address pool range vpnippoolinfo corresponding to the original planning address cannot completely contain the acquisition address, which indicates that the address pool range of the original planning address is wrong, then
1. Update the VPNIPPoolInfo table ipprefix, modify the pool range:
2. judging whether the planning address state is idle, if not, splitting an intersection part from the acquisition address, and newly recording the rest part into a VPNIPPoolDetail table; if the VPNIPPoolDetail table is idle, deleting the original programming address of the VPNIPPoolDetail table, and additionally recording the new programming address into the VPNIPPoolDetail table by using the acquisition address;
for case (B), if the stock address state of the intersection portion is not free: VPNIPPoolDetail & gt 0, the state of the stock data cannot be modified at the moment, and skipping is carried out;
if the intersection part address state is idle: status of vpnippooldetail 0, then
1. Splitting an intersection part, and updating and storing residual data: the address state is not changed, and the initial and final addresses, the number of addresses and the address field are recalculated
2. Splitting an intersection part, namely an acquisition address, newly adding and recording the acquired intersection part into a vpn address pool detailed table VPNIPPoolDetail, wherein the state is occupied;
for the case (C), if the address pool corresponding to the original stock planning address is defined as
Ipprefix, comprising an acquisition address;
if the address state of the intersection part is idle: vpnippooldetail. status ═ 0, then:
1. splitting an intersection part from VPNIPPoolDetail stock data, updating a database, keeping the state of the remaining addresses unchanged, and recalculating the starting address, the ending address, the number of the addresses and the address section;
2. inputting the collected address information into a VPNIPPoolDetail table, wherein the state is occupied;
if the address state of the intersection part is not idle, VPNIPPoolDetail.status < >0 (not idle), splitting the intersection part from the acquisition address, and putting the rest of the acquisition address into a VPNIPPoolDetail table;
if the address pool range vpnippoolinfo, ipprefix corresponding to the original planning address cannot completely contain the acquisition address, which indicates that the address pool range originally planned has errors, then:
1. modifying the address pool range: updating VPNIPPoolInfo. ipprefix table
2. Judging whether the address state of the intersection part is idle, and processing the steps as follows: if not, splitting the intersection part from the acquisition address, and newly recording the rest part into a VPNIPPoolDetail table; if the storage data is idle, splitting an intersection part from the storage data, keeping the state of the rest storage addresses unchanged, and updating address information; and newly adding and recording the acquisition address into a VPNIPPoolDetail table, wherein the state is occupied.
For the case (D), the acquisition address does not exist in the inventory planning data completely, and then data is added in the inventory vpn address pool and the vpnippoollnfo and VPNIPPoolDetail table. The address state is occupied;
in step D24, matching the static address table according to the device id and the address pool name to obtain a static occupied address, and recording the static occupied address as an occupied address; matching an address pool address field table according to the equipment id and the address pool name to obtain an available address and an address pool complete address field; the occupied address is subtracted from the available address, and the rest address segment is recorded as an idle address; the full address segment minus the available address, the remaining address, is marked as the lock address.
As shown in fig. 5, in step D26, the comparison result of the collected data and the stock planning address in the set a includes four types, which are (a) the planning address is included in the collected address, (B) the collection address is included in the planning address, (C) the collection address and the planning address have a partial intersection address, and (D) the collection address and the planning address do not have any intersection address.
And (4) deleting the planning address of the original stock in the stock if intersection exists in the conditions of (A), (B) and (C), and warehousing the planning address again by using the acquisition address.
1. Deleting VPNIPPoolDetail and VPNIPPoolInfo table related inventory planning data;
2. adding new storage according to the acquisition address;
when entering the warehouse, the address state is combined with the stock planning address state in the original warehouse, and the address state is processed according to the following logic rules:
if the collected and analyzed address state is an occupied address or a locked address, the address state is the same as the collected and analyzed address state when the address is newly put into the library;
if the address state of the acquisition and analysis is an idle address, the address state is the same as the address state of the stock data in the original library when the address is newly put into the library.
And (D) if the acquisition address does not exist in the inventory planning data, adding data in the inventory vpn address pool and the vpnippoollnfo detailed table and the VPNIPPoolDetail table. The address state is put in storage according to the address state analyzed in front of the collected address (idle address, occupied address, locked address).
In step D33, the step of processing the collected data in the same vpn number one by one includes calculating the start and end addresses by using the static address and the mask; and (4) taking the service address in the storage planning address, and judging whether the acquisition address exists in the storage planning address.
As shown in FIG. 6, in step D33, the processing for each case is with the exclusive gateway address processing
(A) The planning address is contained by the acquisition address;
(B) the acquisition address is contained by the planning address;
(C) collecting partial intersection addresses of the addresses and the planning addresses;
(D) the acquisition address and the planning address do not have any intersecting address;
for the case (A), firstly, judging the address pool range corresponding to the original stock planning address: ipprefix, if the address pool range contains the acquisition address, the address pool range is correct; if the stock planning address state of the intersection part is not idle: VPNIPPoolDetail, status < >0, can not modify stock data state, splits out the intersection part from gathering the address, and the rest adds the record and enters VPNIPPoolDetail table newly, and status is 2 (occupy), if the stock planning address state of intersection part is idle: deleting the original stock planning address if the status is 0, and recording the new stock planning address into a VPNIPPoolDetail table by adding the acquisition address, wherein the status is 2 (occupied);
if the address pool range VPNIPPoolInfo, ipprefix corresponding to the original programming address cannot completely contain the acquisition address, which indicates that the address pool range originally programmed is wrong, updating the VPNIPPoolInfo table ipprefix, and modifying the address pool range: judging whether the planning address state is idle, if not, splitting an intersection part from the acquisition address, and newly recording the rest part into a VPNIPPoolDetail table; if the VPNIPPoolDetail table is idle, deleting the original programming address of the VPNIPPoolDetail table, and additionally recording the new programming address into the VPNIPPoolDetail table by using the acquisition address;
for case (B), from the VPNIPPoolDetail associated address field, if the stock address state of the intersection portion is non-free: VPNIPPoolDetail & gt 0, the state of the stock data cannot be modified at the moment, and skipping is carried out;
if the intersection part address state is idle: vpnippooldetail. status is 0, then the intersection part is split, and the remaining data is updated and put in storage: the address state is unchanged, the split intersection part, namely the acquisition address, of the starting address, the ending address, the address number and the address field is recalculated, and is newly recorded into the vpn address pool detail table VPNIPPoolDetail, and the state is occupied
For the case (C), if the range of the address pool corresponding to the original storage planning address
Ipprefix, comprising an acquisition address; if the address state of the intersection part is idle: if VPNIPPoolDetail is 0, splitting an intersection part from VPNIPPoolDetail stock data, updating a database, keeping the state of the rest addresses unchanged, and recalculating the starting address, the ending address, the number of the addresses and the address field; inputting the collected address information into a VPNIPPoolDetail table, wherein the state is occupied; if the address state of the intersection part is not idle, VPNIPPoolDetail.status < >0 (not idle), splitting the intersection part from the acquisition address, and putting the rest of the acquisition address into a VPNIPPoolDetail table;
if the address pool range VPNIPPoolInfo. ipPrefix corresponding to the original planning address cannot completely contain the acquisition address, which indicates that the address pool range of the original planning address is wrong, modifying the address pool range: update vpnippoolinfo.
Judging whether the address state of the intersection part is idle, and processing the steps as follows: if not, splitting the intersection part from the acquisition address, and newly recording the rest part into a VPNIPPoolDetail table; if the storage data is idle, splitting an intersection part from the storage data, keeping the state of the rest storage addresses unchanged, and updating address information; newly adding and recording the acquisition address into a VPNIPPoolDetail table, wherein the state is occupied;
for the case (D), the acquisition address does not exist in the inventory planning data completely, and then data is added in the inventory vpn address pool and the vpnippoollnfo and VPNIPPoolDetail table. The address state is occupied.
The description of the table names and fields above is illustrated as follows:
vpninstance table-VPN instance collection information table;
VPNNoInfo table — stock data VPN number information maintenance table;
rd1 or VPNNoInfoRD2 — VPN number information maintains two RD values in the table;
VPNNoInfo. Status- -VPN number information maintenance table VPN use state 0-idle, 1-pre-occupation, 2-occupation;
PortExtInfo table- -Port collection expansion information table;
vpninstatnce field-vpn instance name;
StaticRoute table-static address collection information table;
deviceid field — device identification ID;
portdescr field — device port description;
DevPortAddr table — device port address collection information table;
ipaddress field — port address;
netmask field-mask address.
It should be noted that, in the above system embodiment, each included unit is only divided according to functional logic, but is not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
In addition, it is understood by those skilled in the art that all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing associated hardware, and the corresponding program may be stored in a computer-readable storage medium.
The preferred embodiments of the invention disclosed above are intended to be illustrative only. The preferred embodiments are not intended to be exhaustive or to limit the invention to the precise embodiments disclosed. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, to thereby enable others skilled in the art to best utilize the invention. The invention is limited only by the claims and their full scope and equivalents.
Claims (7)
1. An implementation method for intelligently maintaining a vprn planning address based on collected data comprises vpn data processing and vpn address processing, and is characterized in that:
the vpn data processing steps are as follows:
step S1: scanning a VPN (virtual private network) instance information table vpninstance at regular time, associating an equipment table and a node table, and acquiring relevant information of a city where equipment is located and a VPN instance to obtain an acquired data set A;
step S2: processing the collected data in the set A one by one, and comparing the rd value with the VPNNoInfo inventory data: vpninstance.rd vpnnoinfo.rd1 or vpnnoinforrd 2 were considered to match;
step S3: if a plurality of records are matched, skipping over and ending;
step S4: if a record is matched, and the state of the stock data is occupied: namely vpnnoinfo. status ═ 2, the record in set a is skipped and the next record is processed;
step S5: matching to a record, and the state of stock data is unoccupied: status 2, whether the acquired data and the stock data are matched or not is continuously judged;
if the cities are not matched, skipping the records in the set A, and ending;
if the local cities of the collected data and the stock data are matched: updating the stock data VPNNoInfo table by using the collected data;
step S6: if the records cannot be matched, adding a piece of vpn information into the stock table;
the vpn address processing comprises three vpn address processing types of processing an independent gateway address, processing a shared gateway address and processing a service address;
the processing step of processing the independent gateway address comprises the following steps:
step D11: scanning a Port ExtInfo table of a port expansion table at fixed time to acquire the collected vpn address information on the equipment, and associating an equipment table and a node table to acquire the name of a city to which the equipment belongs;
step D12: processing the collected data in the set A one by one, firstly judging the VPN number in the set A, and processing the VPN number address field together;
step D13: grouping the collected data set A according to the same vpn number, and processing the collected data of the same group one by one;
the processing step of processing the shared gateway address comprises the following steps:
step D21: scanning an address pool table at regular time to obtain an address and a gateway address mask, associating an equipment table and a node table, and obtaining a city name corresponding to equipment;
step D22: intercepting a digital part from a vpn example vpninstatnce field to obtain a vpn number;
step D23: obtaining a collected data set A by taking a record that the vpn number is not empty;
step D24: analyzing the acquisition state of each address segment under each address pool in the address pool;
step D25: processing the collected data in the set A, judging the VPN number in the set A, and processing the VPN number address field together;
step D26: comparing the collected data in the set A with the address of the shared gateway of the stock planning address of the same vpn number;
the processing step of processing the service address comprises the following steps:
step D31: scan static Address configuration Table the vpn instance vpninstance of the StaticRoute Table is not empty and IP! Associating the data of '0.0.0.0', and obtaining a city name corresponding to the equipment by the equipment table and the node table; intercepting a digital part from a vpninstance field to obtain a vpn number; obtaining an acquired data set A if the vpn number is not null;
step D32: processing the collected data in the set A one by one, firstly judging the vpn numbers in the set A, grouping the vpn numbers according to the same vpn number, and judging the same vpn number by the same method and the same unique gateway address;
step D33: and processing the collected data in the same vpn number one by one.
2. The method according to claim 1, wherein in step D11, the value of the vpn address information corresponding to the device is as follows: intercepting a digital part from a vpn example field of a PortExtInfo. vpninstance and port expansion table to obtain a vpn number; inquiring a device port address table DevPortAdddr according to the device iddeviceid and the port description portdescr to obtain a port address ipaddress and a mask address netmask; and (3) obtaining a collected data set A by taking the record that the vpn number is not empty, namely, only taking the address of which the port has the vpn and the standard vpn number to compare with the address of the storage volume vpn.
3. The method as claimed in claim 1, wherein in step D12, the same VPN is determined by querying the VPN number for the VPN information table VPNoInfo of the stock;
if a record is inquired and the VPN opening area is not the urban area, calculating the same VPN by the same VPN number in different cities;
if one or more records are inquired and the VPN opening areas are all urban areas, calculating different VPNs by the same VPN number in different cities;
if the VPN opening area cannot be identified and the IP address cannot be compared and processed, recording the VPN opening area to an error log.
4. The method according to claim 1, wherein in step D13, the same group of collected data is processed item by item, and the start and end addresses of each collected address are calculated according to the address and the mask address; and comparing the address with the address which belongs to the same vpn number and is not the service address and is an independent gateway with planned inventory.
5. The method according to claim 1, wherein in step D24, a static address table is matched according to a device id and an address pool name to obtain a static occupied address, which is recorded as an occupied address; matching an address pool address field table according to the equipment id and the address pool name to obtain an available address and an address pool complete address field; the occupied address is subtracted from the available address, and the rest address segment is recorded as an idle address; the full address segment minus the available address, the remaining address, is marked as the lock address.
6. The method according to claim 1, wherein in step D26, the comparison result between the collected data in set a and the addresses of the shared gateways for planning storage in set a includes four types, which are respectively included in the collected addresses of the planning addresses, included in the planned addresses of the collection addresses, partially intersected addresses between the collected addresses and the planning addresses, and none intersected addresses between the collected addresses and the planning addresses.
7. The method as claimed in claim 1, wherein in step D33, the step of processing the collected data in the same vpn number one by one includes calculating the start and end addresses with static addresses and masks; and (4) taking the service address in the storage planning address, and judging whether the acquisition address exists in the storage planning address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011352612.9A CN112565049B (en) | 2020-11-27 | 2020-11-27 | Implementation method for intelligently maintaining vprn planning address based on collected data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011352612.9A CN112565049B (en) | 2020-11-27 | 2020-11-27 | Implementation method for intelligently maintaining vprn planning address based on collected data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112565049A true CN112565049A (en) | 2021-03-26 |
| CN112565049B CN112565049B (en) | 2022-05-17 |
Family
ID=75045974
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011352612.9A Active CN112565049B (en) | 2020-11-27 | 2020-11-27 | Implementation method for intelligently maintaining vprn planning address based on collected data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112565049B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103684958A (en) * | 2012-09-14 | 2014-03-26 | 中国电信股份有限公司 | Method and system for providing flexible VPN (virtual private network) service and VPN service center |
| US20190238457A1 (en) * | 2016-07-25 | 2019-08-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Efficient vpn route refresh mechanism for bgp based vpn technologies |
-
2020
- 2020-11-27 CN CN202011352612.9A patent/CN112565049B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103684958A (en) * | 2012-09-14 | 2014-03-26 | 中国电信股份有限公司 | Method and system for providing flexible VPN (virtual private network) service and VPN service center |
| US20190238457A1 (en) * | 2016-07-25 | 2019-08-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Efficient vpn route refresh mechanism for bgp based vpn technologies |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112565049B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8510338B2 (en) | Indexing information about entities with respect to hierarchies | |
| US20060112133A1 (en) | System and method for creating and maintaining data records to improve accuracy thereof | |
| CN101901242A (en) | Federated configuration data management | |
| CN109995650B (en) | SDN network-based path calculation method and device under multidimensional constraint | |
| CN112565095B (en) | Automatic discovery and analysis method and device for internet special line | |
| CN104182435B (en) | The information retrieval system and method marked based on shortage of data | |
| JP2004518226A (en) | Database system and query optimizer | |
| US20100174712A1 (en) | Expertise ranking using social distance | |
| US7480662B2 (en) | Fact table storage in a decision support system environment | |
| JP2002504248A (en) | System and method for indexing entity information from different sources | |
| JP2009259284A (en) | Method of querying structure of compressed data | |
| JP2011509472A (en) | Data clustering method, system, apparatus, and computer program for applying the method | |
| US4792921A (en) | Network event identifiers | |
| CN105913656A (en) | Distributed statistics based method and system for frequently passing vehicles | |
| CN112565049B (en) | Implementation method for intelligently maintaining vprn planning address based on collected data | |
| US7167545B2 (en) | Method and device for automatically issuing information using a search engine | |
| US20080120623A1 (en) | Work-flow apparatus, work-flow process, and computer-readable medium storing work-flow program | |
| CN109257457B (en) | IDC information security system state monitoring method based on data analysis | |
| US6678675B1 (en) | Techniques for searching for best matches in tables of information | |
| CN113742344A (en) | Method and device for indexing power system data | |
| KR20050076401A (en) | Apparatus and method of customer information managing for high-speed internet service | |
| CN103067203B (en) | policy consistency auditing method, device and equipment | |
| US20100172269A1 (en) | Method for representing nodes in network | |
| KR100500837B1 (en) | Method for managing common database in network operating systems | |
| CN110569362B (en) | Ontology instantiation method and device |
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 | ||
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: 200000 room 702-2, No. 4811 Cao'an Road, Jiading District, Shanghai Patentee after: CHINA UNITECHS Address before: Room 1004-4, 10 / F, 1112 Hanggui Road, Anting Town, Jiading District, Shanghai Patentee before: CHINA UNITECHS |