CN111935015B

CN111935015B - MPLS VPN analysis method, device, computer equipment and storage medium

Info

Publication number: CN111935015B
Application number: CN202010747275.7A
Authority: CN
Inventors: 晏平
Original assignee: Yunnan Nuoxunke Technology Co ltd
Current assignee: Yunnan Nuoxunke Technology Co ltd
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2022-07-26
Anticipated expiration: 2040-07-29
Also published as: CN111935015A

Abstract

The invention relates to MPLS VPN analysis method, device, computer equipment and storage medium, the method includes constructing the neighbor relation with MP-BGP reflector, and collecting the update message of MP-BGP reflector; analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN; analyzing the current reachable and cancelled routing information of the MPLS VPN according to the related information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN; and feeding back the current route state of the MPLS VPN to the terminal so as to display the current route state of the MPLS VPN at the terminal. The invention realizes real-time analysis of MPLS VPN routing attribute information, thereby obtaining the real-time state of MPLS VPN routing, and having high efficiency and accuracy.

Description

MPLS VPN analysis method, device, computer equipment and storage medium

Technical Field

The present invention relates to network management, and more particularly, to a method, an apparatus, a computer device, and a storage medium for analyzing MPLS VPNs.

Background

The existing network management systems are realized by training devices in a network in turn based on SNMP (simple network management protocol), and the devices cannot acquire real-time running conditions and historical data of route running of any MP-BGP (MP-Border gateway protocol), namely backward compatible and multiprotocol label switching virtual private network technology MPLS VPN (Multi-protocol Label switching) route. Conventional BGP-4 can only manage IPV4 routing information, and is somewhat limited for applications using other network layer protocols when propagating across autonomous systems. In order to provide support for a variety of network layer protocols, the IETF has extended BGP-4 to form MP-BGP, which is RFC4760 (Multiprotocol Extensions to BGP-4 for BGP-4). To support the MPLS VPN network layer protocol, MP-BGP needs to reflect the Information of the network layer protocol to NLRI (network layer Reachability Information) and the IP address of the router to the destination route next-hop autonomous system. Two new path attributes, MP _ REACH _ NLRI (Multiprotocol Reachable route) and MP _ unread _ NLRI (Multiprotocol Unreachable NLRI), are introduced into MP-BGP. MP _ REACH _ NLRI is used to publish reachable routes and next hop information. MP _ unread _ NLRI is used to withdraw unreachable routes. Both attributes are optional and non-transitive, so a BGP (Border gateway protocol) speaker that does not provide multiprotocol capability will ignore the information of both attributes and not pass them on to other neighbors. In addition to the above-mentioned MP _ read _ NLRI and MP _ unread _ NLRI attributes, EXT _ communites (Extended communites, Extended community attribute information) also contains relevant information of the MPLS VPN, mainly RT (Route Target) attributes.

SNMP is a traditional network management technique that does not have the ability of analyzing dynamic routes of MP-BGP and MPLS VPNs in real time that is of interest to network managers. The SNMP-based network management system is a device-level monitoring and management system based on periodic polling. Events occurring in the network between polling intervals are missed, and increasing the polling density increases the load of the network, and unfortunately the SNMP protocol itself has no knowledge about problems inside the MP-BGP routing protocol, for example, some user feedbacks cannot access some networks, but from the view of the network management system, the states of all routers and links are normal, so it is difficult to determine where the problem is and how to remove the failure. Secondly, because part of RT values of the MP-BGP are changed, routes matching the RT values are inhibited from entering corresponding VPNs (Virtual Private networks), which results in that some networks are unreachable, but current Network management tools do not have the capability of analyzing real-time states of MP-BGP and MPLS VPN routes, and fault location has no effect.

Therefore, it is necessary to design a new method for analyzing the MPLS VPN routing attribute information in real time so as to know the real-time status of the MPLS VPN routing.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provides an MPLS VPN analysis method, a device, computer equipment and a storage medium.

In order to realize the purpose, the invention adopts the following technical scheme: the MPLS VPN analysis method comprises the following steps:

constructing a neighbor relation with the MP-BGP reflector, and collecting an update message of the MP-BGP reflector;

analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN;

analyzing the current reachable and cancelled routing information of the MPLS VPN according to the related information of the MPLS VPN to obtain the current routing state of the MPLS VPN;

and feeding back the current route state of the MPLS VPN to the terminal so as to display the current route state of the MPLS VPN at the terminal.

The further technical scheme is as follows: the feeding back the current route state of the MPLS VPN to the terminal so that after the terminal displays the current route state of the MPLS VPN, the method further includes:

and storing the current routing state of the MPLS VPN, and inquiring and analyzing the historical routing time condition of the MPLS VPN.

The further technical scheme is as follows: the related information of the MPLS VPN comprises multi-protocol reachable routing information, multi-protocol unreachable routing information and extended community attribute information;

the analyzing the related information of the MPLS VPN to the update message to obtain the related information of the MPLS VPN includes:

offsetting the withdrawn route length of the MP-BGP reflector according to the updating message;

searching the attribute with the type code of 14 in the updating message to obtain the multi-protocol reachable routing information;

searching the attribute with the type code of 15 in the updating message to obtain the multi-protocol unreachable routing information;

searching the attribute with the type code of 16 in the updating information to obtain the attribute information of the extended community;

storing the multi-protocol reachable route information, and updating the multi-protocol reachable route to a system memory cache;

analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into a database;

storing the multi-protocol unreachable route information, and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route;

analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries, and writing all the multi-protocol unreachable routing entries into a database;

storing the extended community attribute information, and updating the extended community attribute information into a system memory cache;

and analyzing the extended community attribute information to obtain extended community attribute information items, and writing all the extended community attribute information items into a database.

The further technical scheme is as follows: the analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into a database includes:

judging whether the address family information in the multi-protocol reachable routing information is legal or not;

if the address family information in the multi-protocol reachable routing information is legal, judging whether the next hop information is analyzed;

if the next hop information is not analyzed, analyzing the field value of the next hop information according to the length of the next hop, and updating the field value into a memory for caching;

judging whether the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed;

if the subnet access point attribute field in the multi-protocol reachable routing information is not analyzed, analyzing each subnet access point attribute field according to the number of the subnet access points;

judging whether the length of the reachable routing list field in the multi-protocol reachable routing information is legal or not;

if the length of the reachable route list field in the multi-protocol reachable route information is legal, judging whether the reachable route list field in the multi-protocol reachable route information is analyzed;

if the reachable route list field in the multi-protocol reachable route information is not analyzed, analyzing the label attribute, the RD attribute and the IP prefix attribute in the reachable route list field to obtain a multi-protocol reachable route entry;

the multi-protocol reachable route entries are updated into the memory cache and the database.

The further technical scheme is as follows: the parsing the multi-protocol unreachable route information to obtain multi-protocol unreachable route entries and writing all the multi-protocol unreachable route entries into a database includes:

judging whether the address family information in the multi-protocol unreachable routing information is legal or not;

if the address family information in the multi-protocol unreachable routing information is legal, judging whether the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal or not;

if the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal, analyzing a label attribute, an RD attribute and an IP prefix attribute in the withdrawn routing information field to obtain a multi-protocol unreachable routing entry;

and updating the memory cache and the database according to the multi-protocol unreachable route entry.

The further technical scheme is as follows: the analyzing the extended community attribute information to obtain extended community attribute information entries, and writing all the extended community attribute information entries into a database, including:

judging whether the byte length of the extended community attribute information is legal or not;

if the byte length of the extended community attribute information is legal, judging whether the extended community attribute information is analyzed;

if the extended community attribute information is not analyzed, judging whether the RT attribute in the extended community attribute information is of a type of 0x 0002;

if the RT attribute in the extended community attribute information is of a type 0x0002, analyzing the RT attribute of the type 0x0002 to obtain an extended community attribute information item;

updating the extended community attribute information items to a memory cache and a database;

if the RT attribute in the extended community attribute information is not 0x0002 type, judging whether the RT attribute in the extended community attribute information is 0x0102 type;

if the RT attribute in the extended community attribute information is of a 0x0102 type, analyzing the RT attribute of the 0x01022 type to obtain an extended community attribute information item, and updating the extended community attribute information item to a memory cache and a database;

if the RT attribute in the extended community attribute information is not of the type 0x0102, judging whether the RT attribute in the extended community attribute information is of the type 0x 0202;

and if the RT attribute in the extended community attribute information is of a 0x0202 type, analyzing the 0x0202 type RT attribute to obtain an extended community attribute information item, and updating the extended community attribute information item to a memory cache and a database.

The further technical scheme is as follows: the analyzing the current reachable and withdrawn route information of the MPLS VPN for the related information of the MPLS VPN to obtain the current route state of the MPLS VPN comprises the following steps:

judging whether the memory cache has related information of the MPLS VPN or not;

if the related information of the MPLS VPN exists in the memory cache, judging whether the current query request queries the reachable routing information of the MPLSVPN;

if the current query request is to query the reachable route information of the MPLS VPN, summarizing a reachable route result of the MPLS VPN according to the reachable route items of the multiprotocol so as to obtain the current route state of the MPLS VPN;

if the current query request does not query the reachable route information of the MPLS VPN, judging whether the current query request queries the route revocation information of the MPLS VPN;

if the current query request is to query MPLS VPN withdrawal routing information, summarizing an MPLS VPN reachable routing result according to the multiprotocol unreachable routing entry so as to obtain the current routing state of the MPLS VPN;

if the current query request does not query the MPLS VPN withdrawal routing information, returning error information to obtain the current routing state of the MPLS VPN.

The invention also provides an MPLS VPN analysis apparatus, including:

the neighbor building unit is used for building a neighbor relation with the MP-BGP reflector and collecting the update message of the MP-BGP reflector;

the analysis unit is used for analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN;

the analysis unit is used for analyzing the current reachable and withdrawn routing information of the MPLS VPN for the related information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN;

and the feedback unit is used for feeding back the current route state of the MPLS VPN to the terminal so as to display the current route state of the MPLS VPN at the terminal.

The invention also provides computer equipment which comprises a memory and a processor, wherein the memory is stored with a computer program, and the processor realizes the method when executing the computer program.

The invention also provides a storage medium storing a computer program which, when executed by a processor, is operable to carry out the method as described above.

Compared with the prior art, the invention has the beneficial effects that: the invention establishes neighbors with the MP-BGP reflector to collect the updated information of the MP-BGP reflector, analyzes the updated information to obtain MPLSVPN related information such as multi-protocol reachable route information, multi-protocol unreachable route information and extended group attribute information, updates the memory cache and the database by analyzing the MPLS VPN related information, can fetch the information in the corresponding memory cache when inquiring the MPLS VPN state, realizes real-time analysis of the MPLSVPN route attribute information, and thus obtains the real-time state of the MPLS VPN route, and has high efficiency and accuracy.

The invention is further described below with reference to the accompanying drawings and specific embodiments.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a schematic view of an application scenario of an MPLS VPN analysis method according to an embodiment of the present invention;

fig. 2 is a schematic flowchart of an MPLS VPN analysis method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating an MPLS VPN analysis method according to another embodiment of the present invention;

fig. 4 is a schematic block diagram of an MPLS VPN analysis apparatus according to an embodiment of the present invention;

fig. 5 is a schematic block diagram of an MPLS VPN analysis apparatus according to another embodiment of the present invention;

FIG. 6 is a schematic block diagram of a computer device provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.

Referring to fig. 1 and fig. 2, fig. 1 is a schematic view of an application scenario of an MPLS VPN analysis method according to an embodiment of the present invention. Fig. 2 is a schematic flowchart of an MPLS VPN analysis method according to an embodiment of the present invention. The MPLS VPN analysis method is applied to a server. The server carries out data interaction with the MP-BGP reflector, carries out data interaction with the terminal, acquires the update message of the MP-BGP reflector through the neighbor relation established with the MP-BGP reflector, analyzes the related information of the MPLS VPN from the update message, further analyzes the related information of the MPLS VPN, obtains the real-time state of the MPLS VPN, and feeds the state back to the terminal.

Fig. 2 is a flowchart illustrating an MPLS VPN analysis method according to an embodiment of the present invention. As shown in fig. 2, the method includes the following steps S110 to S140.

S110, constructing a neighbor relation with the MP-BGP reflector, and collecting an update message of the MP-BGP reflector.

In this embodiment, the neighbor relation is a connection relation of an internal BGP protocol, and provides more information to an internal router, and routers corresponding to IBGP neighbors are connected in a full mesh structure.

Specifically, the server establishes an IBGP neighbor with an MP-BGP reflector in a certain autonomous system, and the neighbor establishment state is a connection established state, that is, the acquisition and analysis server and the MP-BGP reflector can exchange three messages, namely, a keep-alive message, an update message, and an error message. And the real-time analysis of the MP-BGP protocol state information and the MPLS VPN route is completed by analyzing the information attributes of the MP _ REACH _ NLRI and the MP _ UNREACH _ NLRI in the update message. The function of historical route analysis of MP-BGP and MPLS VPN is provided by storing the real-time MP-BGP attribute and MPLS VPN route information.

In this embodiment, each autonomous system has MP-BGP routes, and the MP-BGP reflectors are connected to a number of MP-BGP routes through a BGP network. And establishing connection with a server through the MP-BGP reflector to realize real-time acquisition of MP-BGP routing information.

The whole process of establishing the neighbor is as follows: establishing TCP connection with an MP-BGP reflector in an autonomous system in a collection network route, and monitoring the corresponding TCP initialization condition; acquiring an opening message from an MP-BGP reflector, and driving the MP-BGP reflector to enter a state that the opening message is sent; sending an opening message to the MP-BGP reflector for verification by the MP-BGP reflector and sending a keep-alive message by the MP-BGP reflector; and responding the keep-alive message and driving the MP-BGP reflector to transition to the state that the connection is established. Specifically, after the TCP connection is established, the MP-BGP reflector sends an opening message to the acquisition server, enters a state that the opening message is sent, and waits until the acquisition server responds; the acquisition server sends an opening message to the routing equipment; the MP-BGP reflector checks the opening message, and sends a keep-alive message after the check is successful; the acquisition server responds to the keep-alive message of the MP-BGP reflector, and the state of the MP-BGP reflector is transited to the connection established state to complete the neighbor establishment.

S120, analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN.

In this embodiment, the MPLS VPN related information includes multi-protocol reachable routing information, multi-protocol unreachable routing information, and extended community attribute information, and the MPLS VPN related information refers to an attribute that can represent a real-time state of an MPLS VPN route.

Specifically, the multi-protocol reachable routing information includes address family information, next hop information, subnet access point information, and prefix information; wherein the address family information includes AFI and SAFI. Wherein the AFI carries a network layer protocol identifier related to a network address; the SAFI carries additional information of network layer reachable information in the relevant attributes; corresponding to MPLS VPN, AFI and SAFI address family information are 1 and 128, respectively. The next hop information includes a network address length and a next hop network address. In the BGP IPv4 definition, the next hop is passed as an attribute of the address, with the attribute type being 3. After BGP performs address extension, the next hop address also needs to be extended, and therefore, the next hop address is transferred in the MP _ REACH _ NLRI attribute. The subnet access point information is used for storing SNPA subnet access points, and the Number of the SNPA subnet access points is controlled by Number of SNPAs. Prefix information is put in the NLRI field of the attribute and is transmitted, and different address family formats are different. The reachable route list includes a label attribute, an RD attribute, and an IP prefix attribute, where the label attribute is the same as an MPLS label, but there is no TTL.

The unreachable route is announced by the unreachable attribute of the extended address, and an update message containing MP _ UNREACH _ NLRI does not need to carry any other path attribute except the MP _ UNREACH _ NLRI attribute; the multi-protocol unreachable routing information comprises address family information and withdrawn routing information; the address family information includes AFI and SAFI. Wherein the AFI carries a network layer protocol identifier related to a network address; the SAFI carries additional information of network layer reachable information in the relevant attributes; corresponding to MPLS VPN, AFI and SAFI address family information are 1 and 128, respectively. The withdrawn routing information comprises a label attribute, an RD attribute and an IP prefix attribute, wherein the label attribute is the same as the MPLS label but has no TTL.

For the extended community attribute information, the extended community attribute contains a plurality of RT attributes, and for the RTs of different types, the represented meanings of the RT values are also different; the specific correspondence is as follows: route Target Type (0x0002), Route Target AS (2octets), Route Target AN (4 octets); route Target Type (0x0102), Route Target IP address (4octets), and Route Target AN (2 octets); route Target Type (0x0202), Route Target AN (4octets), and Route Target Local (2 octets).

In an embodiment, the step S120 may include steps S121 to S1210.

S121, offsetting the withdrawn route length of the MP-BGP reflector according to the updating message.

In this embodiment, the server offsets the Length of the MP-BGP revoked route, and the total Length of the MP-BGP revoked route information is the value of the unreachable Routes Length field, that is, the Length of the identification unreachable route field; the format of the withdrawn routing information is in the form of mask bit number + prefix. The Length of the offset unfeasable Routes Length field value is the header of the Path Attribute Length field, and the total Length of the route Attribute information is the value of the Path Attribute Length field. Each route attribute information is composed of an attribute header and an attribute body, the attribute header is composed of flag information of 1 byte, an attribute type code of 1 byte and an attribute length of 1 byte, and the attribute body is the content of the attribute corresponding to the attribute type code.

S122, searching the attribute with the type code of 14 in the updating message to obtain the multi-protocol reachable routing information.

In this embodiment, the multiprotocol reachable route information refers to MP _ REACH _ NLRI information in the MP-BGP path attribute, that is, an attribute whose type code of the update message is 14, and is used to issue reachable route and next hop information, specifically, the server parses the MP-BGP path attribute MP _ REACH _ NLRI information, and by searching for the type code, the attribute whose type code is 14 is an MP _ REACH _ NLRI attribute.

S123, searching the attribute with the type code of 15 in the updating message to obtain the multi-protocol unreachable routing information.

In this embodiment, the multiprotocol unreachable route information refers to MP _ unread _ NLRI information in the MP-BGP path attribute, that is, an attribute with a type code of 15 of the update message, and is used to withdraw an unreachable route. Specifically, the server parses MP-BGP path attribute MP _ unread _ NLRI information, and searches for a type code, where an attribute with the type code of 15 is an MP _ unread _ NLRI attribute.

S124, searching the attribute with the type code being 16 in the updated information to obtain the extended community attribute information.

In this embodiment, the extended COMMUNITY attribute information refers to EXT _ notification information in the MP-BGP path attribute, that is, an attribute whose type code of the update message is 16, and includes the RT attribute, so as to take into account a change in the RT value, and implement more accurate real-time analysis of the state of the MPLS VPN. Specifically, the server parses the MP-BGP path attribute EXT _ COMMUNITY information, and finds a type code, where the attribute with the type code of 16 is the EXT _ COMMUNITY attribute.

S125, storing the multi-protocol reachable route information, and updating the multi-protocol reachable route into a system memory cache.

In this embodiment, the three attributes in the update message are divided and stored in the corresponding memory cache, so as to be used for the history query.

S126, analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into the database.

In this embodiment, the multi-protocol reachable route entry refers to a label attribute, an RD attribute, and an IP prefix attribute in a reachable route list field, that is, information related to a reachable route list, so as to show a reachable state of the MPLS VPN route.

In an embodiment, the step S126 may include steps S1261 to S1269.

S1261, judging whether the address family information in the multi-protocol reachable routing information is legal or not;

and if the address family information in the multi-protocol reachable routing information is illegal, entering an ending step.

In this embodiment, the address family information in the multi-protocol reachable routing information is checked, where the address family information includes AFI and SAFI, where AFI is 2 bytes and SAFI is 1 byte. For MPLS VPN, AFI value is 1, SAFI value is 128; when the length of the byte occupied by the address family information meets the requirement, the address family information is legal, otherwise, the address family information is illegal.

S1262, if the address family information in the multi-protocol reachable routing information is legal, determining whether the next hop information is analyzed;

if the next hop information analysis is completed, step S1254 is executed.

S1263, if the next hop information is not parsed, parsing a field value of the next hop information according to the length of the next hop, and updating the field value to the memory for caching.

Specifically, the field value of the next hop information is circularly analyzed according to the length of the next hop, and the field value is updated to a memory cache;

s1264, judging whether the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed;

if the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed, S1266 is executed;

s1265, if the subnet access point attribute field in the multi-protocol reachable routing information is not analyzed, analyzing the attribute field of each subnet access point according to the number of the subnet access points.

Specifically, the attribute field of each subnet access point is circularly analyzed according to the number of the subnet access points.

S1266, judging whether the reachable route list field length in the multi-protocol reachable route information is legal.

Specifically, whether the length of the reachable route list field in the multi-protocol reachable route information is legal or not is judged, one reachable route list field is composed of Reserved (1octet) + Label (3octet) + RD (8octet) + IP prefix (4octet), namely, one reachable route list field is 16 bytes. The length of the reachable route list field in the multi-protocol reachable route information can be divided by 16, if the length of the reachable route list field cannot be divided by 16, the method is illegal, and ending processing is carried out; if it can be divided by 16, it is legal.

If the length of the reachable route list field in the multi-protocol reachable route information is illegal, entering an ending step;

s1267, if the reachable route list field in the multi-protocol reachable route information is valid in length, determining whether resolution of the reachable route list field in the multi-protocol reachable route information is complete;

if the analysis of the reachable route list field in the multi-protocol reachable route information is completed, the step S1269 is performed.

S1268, if the reachable route list field in the multi-protocol reachable route information is not analyzed, analyzing the tag attribute, the RD attribute and the IP prefix attribute in the reachable route list field to obtain a multi-protocol reachable route entry.

Specifically, the Label attribute, the RD attribute, and the IP prefix attribute in the reachable routing list field are circularly resolved.

S1269, the multi-protocol reachable route entry is updated to the memory cache and the database.

Specifically, the analyzed reachable route list attribute is added into a vector cache for storing NLRI, the cache is vpnv4_ route, whether routes with the same prefix mask exist in the unreachable route cache withathdrawn _ vpnv4_ route with the same structure or not is searched, and the route is deleted from withdrawn _ vpnv4_ route; after all the multi-protocol reachable routes are analyzed, all the analyzed reachable route lists are written into the database, and the attribute corresponding to each reachable route list is recorded as a record entry.

S127, storing the multi-protocol unreachable route information, and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route.

S128, the multi-protocol unreachable route information is analyzed to obtain multi-protocol unreachable route entries, and all the multi-protocol unreachable route entries are written into a database.

In this embodiment, the multi-protocol unreachable route entry refers to attributes such as Label attribute, RD attribute, and IP prefix in the withdrawn route information field, and is used to characterize relevant information of the unreachable route.

In an embodiment, the step S128 may include steps S1281 to S1284.

S1281, judging whether the address family information in the multi-protocol unreachable routing information is legal or not;

and if the address family information in the multi-protocol unreachable routing information is illegal, entering an ending step.

In this embodiment, the address family information in the multiprotocol unreachable routing information includes AFI and SAFI, where AFI is 2 bytes and SAFI is 1 byte. For MPLS VPN, the AFI value is 1 and the SAFI value is 128; when the length of the byte occupied by the address family information meets the requirement, the address family information is legal, otherwise, the address family information is illegal.

S1282, if the address family information in the multi-protocol unreachable routing information is legal, determining whether the length of the withdrawn routing information field in the multi-protocol unreachable routing information is legal.

In this embodiment, it is determined whether the length of the withdrawn routing information field in the multi-protocol unreachable routing information is legal, where one withdrawn routing information field is composed of Reserved (1octet) + Label (3octet) + RD (8octet) + IP prefix (4octet), that is, the total number of bytes of one withdrawn routing information field is 16. The length of a withdrawn routing information field in the multi-protocol unreachable routing information field can be divided by 16, if the length of the withdrawn routing information field cannot be divided by 16, the current length is illegal, and ending processing is carried out; if it is divisible by 16, it indicates that the current length is legal.

If the length of the withdrawn routing information field in the multi-protocol unreachable routing information is illegal, entering an ending step;

s1283, if the length of the withdrawn routing information field in the multi-protocol unreachable routing information is legal, analyzing the label attribute, the RD attribute and the IP prefix attribute in the withdrawn routing information field to obtain the multi-protocol unreachable routing entry.

Specifically, attributes such as Label attribute, RD attribute, IP prefix and the like in a route information field are circularly analyzed and withdrawn;

s1284, updating the memory cache and the database according to the multi-protocol unreachable route entry.

Specifically, the analyzed attributes of the withdrawn route information are added to a vector cache for storing NLRI, the cache is a worthwraw _ vpnv4_ route, and meanwhile, whether routes with the same prefix mask exist in reachable route caches vpnv4_ route with the same structure is searched, and the routes are deleted from vpnv4_ route;

and after all the withdrawn routes are analyzed, all the analyzed withdrawn route information is written into the database, and the attribute of each withdrawn route information is recorded as a record entry.

S129, storing the extended community attribute information, and updating the extended community attribute information into a system memory cache;

s1210, analyzing the extended community attribute information to obtain extended community attribute information items, and writing all the extended community attribute information items into a database.

In this embodiment, the extensible community attribute information entry refers to an extensible community attribute, and includes a type and a structure corresponding to the RT.

In one embodiment, the step S1210 may include steps S12101 to S12109.

S12101 judges whether the byte length of the extended community attribute information is valid.

And if the byte length of the extended community attribute information is illegal, entering an ending step.

In this embodiment, it is determined whether the byte length of the extended community attribute information is legal, and one extended community attribute is 2 byte RT type +6 byte RT attribute value, that is, one extended community attribute is 8 bytes. The byte length of the extended community attribute should be divisible by 8, if the byte length of the extended community attribute cannot be divisible by 8, the byte length of the extended community attribute information is illegal, ending processing is performed, and if the byte length of the extended community attribute information can be divisible by 8, the byte length of the extended community attribute information is legal.

S12102, if the byte length of the extended community attribute information is legal, judging whether the extended community attribute information is analyzed.

Specifically, the extended team attribute information is processed in a circulating manner, and whether the analysis of the extended team attribute is completed is judged.

S12103, if the extended community attribute information is not analyzed, judging whether the RT attribute in the extended community attribute information is 0x0002 type;

s12104, if the RT attribute in the extended community attribute information is 0x0002 type, parsing the RT attribute of 0x0002 type to obtain the extended community attribute information entry.

It is determined whether the current attribute RT attribute is of type 0x 0002. If so, analyzing the corresponding format RT; if not, judging another RT type, analyzing the RT attribute with the RT type of 0x0002, wherein the attribute structure is AS: AN; and skipping to the next extended community attribute analysis after the analysis is finished.

And S12105, updating the extended community attribute information item to a memory cache and a database.

Specifically, updating a memory cache, and adding the analyzed extended community attribute into a vector cache for storing the RT, wherein the cache is the RT; and after all the extended community attributes are analyzed, all the analyzed extended community attributes are written into a database, and each extended community attribute is a record entry.

S12106, if the RT attribute in the extended community attribute information is not 0x0002 type, determining whether the RT attribute in the extended community attribute information is 0x0102 type;

s12107, if the RT attribute in the extended community attribute information is of type 0x0102, parse the RT attribute of type 0x01022 to obtain an extended community attribute information entry, and execute S12105.

Specifically, it is determined whether the current RT attribute is of the 0x0102 type. If yes, analyzing the corresponding format RT; if not, judging another RT type; analyzing the RT attribute with the RT type of 0x0102, wherein the attribute structure is IP: and the AN jumps to the next extended community attribute analysis after the analysis is finished.

S12108, if the RT attribute in the extended community attribute information is not of the 0x0102 type, determining whether the RT attribute in the extended community attribute information is of the 0x0202 type;

s12109, if the RT attribute in the extended community attribute information is 0x0202 type, parsing the 0x0202 type RT attribute to obtain an extended community attribute information entry, and executing the S12105.

And if the RT attribute in the extended community attribute information is not the 0x0202 type, entering an ending step.

In this embodiment, it is determined whether the current RT attribute is of the 0x0202 type. If so, analyzing the corresponding format RT; if not, ending the processing; analyzing the RT attribute with the RT type of 0x0202, wherein the attribute structure is AN: and Local, skipping to the next extended community attribute analysis after the analysis is completed.

MP _ REACH _ NLRI, MP _ UNREACH _ NLRI and EXT _ COMMUNITY attribute information contained in the MP-BGP update message are analyzed, so that MPLSVPN routing attribute information can be analyzed in real time; the current reachable routing condition of the MP-BGP MPLS VPN can be analyzed in real time by analyzing MP _ REACH _ NLRI reachable routing information contained in the UPDATE message of the MP-BGP; the current withdrawn routing condition of the MP-BGP MPLS VPN can be analyzed in real time by analyzing the MP _ REACH _ NLRI withdrawn routing information contained in the UPDATE message of the MP-BGP.

S130, analyzing the current reachable and withdrawn routing information of the MPLS VPN according to the related information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN.

In this embodiment, the current routing state of the MPLS VPN refers to the currently reachable and revoked routing information of the MPLS VPN.

In one embodiment, the step S130 may include steps S131 to S136.

S131, judging whether the related information of the MPLS VPN exists in the memory cache.

In this embodiment, it is first determined whether there is routing information of the MP-BGP MPLS VPN in the current system memory cache, that is, it is checked whether there is information of the MP-BGP MPLS VPN reachable route and withdrawn route in the memory cache, and if not, it is prompted to inquire and analyze an error.

S132, if the related information of the MPLS VPN exists in the memory cache, whether the current query request queries the reachable routing information of the MPLS VPN is judged.

In this embodiment, the type of the current query analysis request is determined, and different types of routing information requests are processed in a branch manner. And judging whether the current query request is an MP-BGP MPLS VPN reachable route information query analysis request, if so, querying a reachable route, and if not, judging whether the current query request is a query request for canceling the route information.

S133, if the current query request is to query the accessible MPLS VPN routing information, summarizing the accessible MPLS VPN routing results according to the accessible multi-protocol routing entries to obtain the current routing state of the MPLS VPN.

Specifically, the routing information is summarized from the memory cache of the reachable route of the MP-BGP MPLS VPN system; the corresponding reachable route lists are stored in both the memory cache and the database, so that the current route state of the MPLSVPN is formed.

And S134, if the current query request does not query the accessible routing information of the MPLS VPN, judging whether the current query request queries the withdrawn routing information of the MPLS VPN.

In this embodiment, the type of the current query analysis request is determined, whether the current request is an MP-BGP pmpls VPN withdrawal routing information query analysis request is determined, if so, a query of MP-BGP MPLS VPN withdrawal routing is performed, and if not, error information is returned.

And S135, if the current query request is to query the MPLS VPN to withdraw the routing information, summarizing the MPLS VPN reachable routing result according to the multiprotocol unreachable routing entry so as to obtain the current routing state of the MPLS VPN.

And summarizing the routing information from the memory cache of the withdrawn routing of the MP-BGP MPLS VPN system, wherein the memory cache corresponding to the withdrawn routing has a corresponding withdrawn routing information field, and summarizing the inquired routing information from the memory cache of the MP-BGP MPLS VPN system and returning the detailed information after the reachable routing information and the withdrawn routing information are obtained.

S136, if the current query request does not query the MPLS VPN withdrawal routing information, returning error information to obtain the current routing state of the MPLS VPN.

And S140, feeding back the current route state of the MPLS VPN to the terminal so as to display the current route state of the MPLSVPN at the terminal.

And feeding the inquired current routing state back to the terminal, and displaying the state at the terminal for corresponding personnel to look up.

The method can analyze the current protocol configuration of the MP-BGP protocol in real time, and covers all MP-BGP attributes related to the MPLSVPN; the MPLS VPN routing information and the change situation can be analyzed in real time.

According to the MPLS VPN analysis method, the neighbor is established with the MP-BGP reflector to collect the update information of the MP-BGP reflector, the update information is analyzed to obtain MPLS VPN related information such as multi-protocol reachable routing information, multi-protocol unreachable routing information and extended community attribute information, the memory cache and the database are updated through analyzing the MPLS VPN related information, information in the corresponding memory cache can be obtained when the MPLS VPN state is inquired, the MPLS VPN routing attribute information is analyzed in real time, and therefore the real-time state of the MPLS VPN routing is obtained, efficiency and accuracy are high.

Fig. 3 is a flowchart illustrating an MPLS VPN analysis method according to another embodiment of the present invention. As shown in fig. 3, the MPLS VPN analysis method of the present embodiment includes steps S210 to S250. Steps S210 to S240 are similar to steps S110 to S140 in the above embodiment, and are not described herein again. The added step S250 in the present embodiment is explained in detail below.

And S250, storing the current routing state of the MPLS VPN, and inquiring and analyzing the historical MPLSVPN routing time condition.

The embodiment can analyze the historical data, thereby analyzing and summarizing the MPLS VPN routing condition in a specified certain historical time period.

In one embodiment, the step S250 may include steps S251 to S254.

S251, storing the current route state of the MPLS VPN, and judging whether the inquired historical time period is legal or not;

and if the queried historical time period is illegal, entering an ending step.

In this embodiment, it is first determined whether the queried historical time period is legal, and if so, the next operation is performed, and S252 is executed; if not, an error is returned directly.

And S252, if the inquired historical time period is legal, constructing an inquiry statement of the MP-BGP historical routing event, and inquiring in the database to obtain an inquiry result.

In this embodiment, the query result includes MPLS VPN reachable route information, MPLS VPN withdrawn route information, RD, RT attribute, and the like.

Constructing query statements of MP-BGP historical routing events, taking the queried historical time period as a query condition, and executing related database query operation to obtain a database query result, wherein the query result comprises MPLS VPN reachable routing information, MPLS VPN withdrawn routing information, RD (reverse routing) attributes, RT (reverse traffic channel) attributes and the like;

s253, judging whether the query result is empty or not;

and if the query result is empty, entering an end step.

In this embodiment, it is determined whether the database query result is empty, and if the database query result is empty, the database query result returns to the default state and does not execute the next operation; if not, go to step S254.

And S254, if the query result is not empty, formatting the query result into a JSON format, and feeding back the formatted query result to the terminal for displaying at the terminal.

Specifically, the result of querying the database is formatted, the related data is converted into a JSON format, and then the data is displayed.

By saving the contents of MP _ REACH _ NLRI, MP _ UNREACH _ NLRI and EXT _ COMMUNITY in the update message of MP-BGP, MP-BGP event situations and MPLS VPN route change situations in a specified historical time period can be queried and analyzed.

Fig. 4 is a schematic block diagram of an MPLS VPN analysis apparatus 300 according to an embodiment of the present invention. As shown in fig. 4, the present invention also provides an MPLS VPN analysis device 300 corresponding to the above MPLS VPN analysis method. The MPLS VPN analysis apparatus 300 includes a unit for performing the above-described MPLS VPN analysis method, and may be configured in a server. Specifically, referring to fig. 4, the MPLS VPN analysis apparatus 300 includes a neighbor constructing unit 301, an analyzing unit 302, an analyzing unit 303, and a feedback unit 304.

A neighbor construction unit 301, configured to construct a neighbor relationship with the MP-BGP reflector, and collect update messages of the MP-BGP reflector; an analyzing unit 302, configured to analyze the relevant MPLS VPN information of the update message to obtain relevant MPLS VPN information; an analyzing unit 303, configured to analyze currently reachable and revoked routing information of the MPLS VPN for the MPLS VPN related information, so as to obtain a current routing state of the MPLS VPN; a feedback unit 304, configured to feed back the current routing state of the MPLS VPN to the terminal, so as to display the current routing state of the MPLS VPN at the terminal.

In an embodiment, the parsing unit 302 includes a length shifting subunit, a reachable information searching subunit, an unreachable information searching subunit, an extended community searching subunit, a first saving subunit, a first parsing subunit, a second saving subunit, a second parsing subunit, a third saving subunit, and a third parsing subunit.

A length offset subunit, configured to offset, according to the update message, a route length revoked by the MP-BGP reflector; the reachable information searching subunit is used for searching for the attribute with the type code of 14 in the update message to obtain the multi-protocol reachable routing information; an unreachable information searching subunit, configured to search for an attribute with a type code of 15 in the update message, so as to obtain multi-protocol unreachable routing information; the extended group searching subunit is used for searching the attribute with the type code of 16 in the updated information to obtain extended group attribute information; the first storage subunit is used for storing the multi-protocol reachable route information and updating the multi-protocol reachable route to a system memory cache; the first analysis subunit is used for analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries and writing all the multi-protocol reachable routing entries into a database; the second storage subunit is used for storing the multi-protocol unreachable route information and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route; the second analysis subunit is used for analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries and writing all the multi-protocol unreachable routing entries into the database; the third storage subunit is used for storing the extended group attribute information and updating the extended group attribute information into a system memory cache; and the third analysis subunit is used for analyzing the extended group attribute information to obtain extended group attribute information items and writing all the extended group attribute information items into the database.

In an embodiment, the first parsing subunit includes a first determining module, a second determining module, a next hop parsing module, a third determining module, an access point parsing module, a fourth determining module, a fifth determining module, a list parsing module, and a first updating module.

The first judging module is used for judging whether the address family information in the multi-protocol reachable routing information is legal or not; a second judging module, configured to judge whether the next hop information is resolved if address family information in the multi-protocol reachable routing information is legal; the next hop analyzing module is used for analyzing the field value of the next hop information according to the length of the next hop and updating the field value into the memory for caching if the next hop information is not analyzed; a third judging module, configured to judge whether resolution of a subnet access point attribute field in the multi-protocol reachable routing information is completed; an access point analyzing module, configured to analyze, if the subnet access point attribute fields in the multi-protocol reachable routing information are not analyzed, the subnet access point attribute fields according to the number of subnet access points; a fourth judging module, configured to judge whether a reachable route list field length in the multi-protocol reachable route information is legal; a fifth judging module, configured to judge whether resolution of a reachable route list field in the multi-protocol reachable route information is completed if the reachable route list field in the multi-protocol reachable route information is legal; the list analysis module is used for analyzing the label attribute, the RD attribute and the IP prefix attribute in the reachable route list field to obtain a multiprotocol reachable route item if the reachable route list field in the multiprotocol reachable route information is not analyzed; the first updating module is used for updating the multi-protocol reachable route entry into the memory cache and the database.

In an embodiment, the second parsing subunit includes a sixth determining module, a seventh determining module, an information parsing module, and a second updating module.

A sixth judging module, configured to judge whether address family information in the multiprotocol unreachable routing information is legal; a seventh determining module, configured to determine whether a length of a withdrawn routing information field in the multiprotocol unreachable routing information is legal if the address family information in the multiprotocol unreachable routing information is legal; the information analysis module is used for analyzing the label attribute, the RD attribute and the IP prefix attribute in the withdrawn routing information field to obtain a multi-protocol unreachable routing item if the length of the withdrawn routing information field in the multi-protocol unreachable routing information is legal; and the second updating module is used for updating the memory cache and the database according to the multi-protocol unreachable route entry.

In an embodiment, the third parsing subunit includes an eighth determining module, a ninth determining module, a tenth determining module, a first type parsing module, a third saving module, an eleventh determining module, a second type parsing module, a twelfth determining module, and a third type parsing module.

An eighth judging module, configured to judge whether the byte length of the extended group attribute information is legal; a ninth judging module, configured to judge whether the extended group attribute information is parsed or not if the byte length of the extended group attribute information is legal; a tenth determining module, configured to determine whether an RT attribute in the extended group attribute information is of a type 0x0002 if the extended group attribute information is not parsed; a first type parsing module, configured to parse a 0x0002 type RT attribute to obtain an extended community attribute information entry if the RT attribute in the extended community attribute information is a 0x0002 type; the third storage module is used for updating the extended group attribute information items to a memory cache and a database; an eleventh determining module, configured to determine whether the RT attribute in the extended community attribute information is a 0x0102 type if the RT attribute in the extended community attribute information is not a 0x0002 type; a second type parsing module, configured to parse a 0x01022 type RT attribute to obtain an extended group attribute information entry if the RT attribute in the extended group attribute information is a 0x0102 type, and execute updating the extended group attribute information entry to the memory cache and the database; a twelfth judging module, configured to judge whether the RT attribute in the extended community attribute information is of a 0x0202 type if the RT attribute in the extended community attribute information is not of a 0x0102 type; and the third type analysis module is used for analyzing the 0x0202 type RT attribute to obtain an extended community attribute information item and updating the extended community attribute information item to a memory cache and a database if the RT attribute in the extended community attribute information is the 0x0202 type.

In one embodiment, the analyzing unit 303 includes a memory determining subunit, a first request determining subunit, a first summarizing subunit, a second request determining subunit, a second summarizing subunit, and an information returning subunit.

The memory judgment subunit is used for judging whether the memory cache has related information of the MPLS VPN or not; a first request judging subunit, configured to judge whether the current query request queries the reachable routing information of the MPLS VPN if the memory cache has MPLS VPN related information; the first summarizing subunit is used for summarizing the reachable routing result of the MPLS VPN according to the reachable routing entry of the multiprotocol if the current query request is to query the reachable routing information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN; a second request judging subunit, configured to judge whether the current query request queries MPLS VPN revocation route information if the current query request does not query MPLS VPN reachable route information; a second summarizing subunit, configured to summarize, according to the multiprotocol unreachable route entry, a MPLS VPN reachable route result if the current query request is to query MPLS VPN withdrawal routing information, so as to obtain a current routing state of MPLS VPN; and the information returning subunit is used for returning error information to obtain the current routing state of the MPLS VPN if the current query request does not query the MPLS VPN to withdraw the routing information.

Fig. 5 is a schematic block diagram of an MPLS VPN analysis apparatus 300 according to another embodiment of the present invention. As shown in fig. 5, MPLS VPN analyzing apparatus 300 according to the present embodiment is the above-described embodiment, and history analyzing section 305 is added.

A history analysis unit 305, configured to save the current routing state of the MPLS VPN, and query and analyze a history of the MPLS VPN routing time.

In one embodiment, the history analysis unit 305 includes a time period determination subunit, a sentence construction subunit, a result determination subunit, and a result processing subunit.

A time period judging subunit, configured to store the current routing state of the MPLS VPN, and judge whether the queried historical time period is legal; and if the inquired historical time period is illegal, entering an end step. And the statement constructing subunit is used for constructing the query statement of the MP-BGP historical routing event if the queried historical time period is legal, and querying in the database to obtain a query result. A result judging subunit, configured to judge whether the query result is null; and if the query result is empty, entering an end step. And the result processing subunit is used for formatting the query result into a JSON format if the query result is not empty, and feeding back the formatted query result to the terminal for display at the terminal.

It should be noted that, as can be clearly understood by those skilled in the art, the specific implementation process of the MPLS VPN analysis device 300 and each unit may refer to the corresponding description in the foregoing method embodiment, and for convenience and simplicity of description, details are not repeated herein.

The MPLS VPN analysis apparatus 300 may be implemented as a computer program that can be run on a computer device as shown in fig. 6.

Referring to fig. 6, fig. 6 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 is a server, wherein the server may be an independent server or a server cluster composed of a plurality of servers.

Referring to fig. 6, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.

The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer programs 5032 include program instructions that, when executed, cause the processor 502 to perform an MPLS VPN analysis method.

The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.

The internal memory 504 provides an environment for the execution of the computer program 5032 in the non-volatile storage medium 503, and when executed by the processor 502, the computer program 5032 causes the processor 502 to perform an MPLS VPN analysis method.

The network interface 505 is used for network communication with other devices. Those skilled in the art will appreciate that the configuration shown in fig. 6 is a block diagram of only a portion of the configuration associated with aspects of the present application, and is not intended to limit the computing device 500 to which aspects of the present application may be applied, and that a particular computing device 500 may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

Wherein the processor 502 is configured to run the computer program 5032 stored in the memory to implement the following steps:

constructing a neighbor relation with the MP-BGP reflector, and collecting an update message of the MP-BGP reflector; analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN; analyzing the current reachable and cancelled routing information of the MPLS VPN according to the related information of the MPLS VPN to obtain the current routing state of the MPLS VPN; and feeding back the current routing state of the MPLS VPN to the terminal so as to display the current routing state of the MPLS VPN at the terminal.

The MPLS VPN related information comprises multi-protocol reachable routing information, multi-protocol unreachable routing information and extended community attribute information.

In an embodiment, after the step of feeding back the current route state of the MPLS VPN to the terminal to display the current route state of the MPLS VPN at the terminal, the processor 502 further performs the following steps:

and storing the current route state of the MPLS VPN, and inquiring and analyzing the historical route time condition of the MPLS VPN.

In an embodiment, when the processor 502 implements the step of analyzing the MPLS VPN related information of the update message to obtain MPLS VPN related information, the following steps are specifically implemented:

offsetting the withdrawn route length of the MP-BGP reflector according to the updating message; searching the attribute with the type code of 14 in the updating message to obtain multi-protocol reachable routing information; searching the attribute with the type code of 15 in the updating message to obtain the multi-protocol unreachable routing information; searching the attribute with the type code of 16 in the updated information to obtain the attribute information of the extended community; storing the multi-protocol reachable route information, and updating the multi-protocol reachable route into a system memory cache; analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into a database; storing the multi-protocol unreachable route information, and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route; analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries, and writing all the multi-protocol unreachable routing entries into a database; storing the extended community attribute information, and updating the extended community attribute information into a system memory cache; and analyzing the extended community attribute information to obtain extended community attribute information items, and writing all the extended community attribute information items into a database.

In an embodiment, when the processor 502 implements the steps of analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into the database, the following steps are specifically implemented:

judging whether the address family information in the multi-protocol reachable routing information is legal or not; if the address family information in the multi-protocol reachable routing information is legal, judging whether the next hop information is analyzed; if the next hop information is not analyzed, analyzing the field value of the next hop information according to the length of the next hop, and updating the field value to a memory for caching; judging whether the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed; if the subnet access point attribute fields in the multi-protocol reachable routing information are not analyzed, analyzing each subnet access point attribute field according to the number of the subnet access points; judging whether the length of the reachable route list field in the multi-protocol reachable route information is legal or not; if the length of the reachable route list field in the multi-protocol reachable route information is legal, judging whether the reachable route list field in the multi-protocol reachable route information is analyzed; if the reachable route list field in the multi-protocol reachable route information is not analyzed, analyzing the label attribute, the RD attribute and the IP prefix attribute in the reachable route list field to obtain a multi-protocol reachable route entry; and updating the multi-protocol reachable route entries into the memory cache and the database.

In an embodiment, when the processor 502 implements the steps of analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries and writing all the multi-protocol unreachable routing entries into the database, the following steps are specifically implemented:

judging whether the address family information in the multi-protocol unreachable routing information is legal or not; if the address family information in the multi-protocol unreachable routing information is legal, judging whether the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal or not; if the length of the withdrawn routing information field in the multi-protocol unreachable routing information is legal, analyzing the label attribute, the RD attribute and the IP prefix attribute in the withdrawn routing information field to obtain a multi-protocol unreachable routing entry; and updating the memory cache and the database according to the multi-protocol unreachable route entry.

In an embodiment, when the processor 502 implements the steps of parsing the extended community attribute information to obtain extended community attribute information entries, and writing all the extended community attribute information entries into the database, the following steps are specifically implemented:

judging whether the byte length of the extended community attribute information is legal or not; if the byte length of the extended community attribute information is legal, judging whether the extended community attribute information is analyzed; if the extended community attribute information is not analyzed, judging whether the RT attribute in the extended community attribute information is of a type of 0x 0002; if the RT attribute in the extended community attribute information is of a type 0x0002, analyzing the RT attribute of the type 0x0002 to obtain an extended community attribute information item; updating the extended community attribute information items to a memory cache and a database; if the RT attribute in the extended community attribute information is not of a type 0x0002, judging whether the RT attribute in the extended community attribute information is of a type 0x 0102; if the RT attribute in the extended group attribute information is of a 0x0102 type, analyzing the 0x01022 type RT attribute to obtain an extended group attribute information entry, and updating the extended group attribute information entry into a memory cache and a database; if the RT attribute in the extended community attribute information is not of the type 0x0102, judging whether the RT attribute in the extended community attribute information is of the type 0x 0202; and if the RT attribute in the extended community attribute information is of a 0x0202 type, analyzing the 0x0202 type RT attribute to obtain an extended community attribute information item, and updating the extended community attribute information item to a memory cache and a database.

In an embodiment, when the processor 502 implements the step of analyzing currently reachable and revoked routing information of the MPLS VPN for the MPLS VPN related information to obtain the current routing state of the MPLS VPN, the following steps are specifically implemented:

judging whether the memory cache has related information of MPLS VPN; if the related information of the MPLS VPN exists in the memory cache, judging whether the current query request queries the reachable routing information of the MPLS VPN; if the current query request is to query the reachable route information of the MPLS VPN, summarizing a reachable route result of the MPLS VPN according to the reachable route items of the multiprotocol so as to obtain the current route state of the MPLS VPN; if the current query request does not query the reachable route information of the MPLS VPN, judging whether the current query request queries the route revocation information of the MPLS VPN; if the current query request is to query MPLS VPN withdrawal routing information, summarizing MPLS VPN reachable routing results according to the multiprotocol unreachable routing entries to obtain the current routing state of MPLS VPN; if the current query request does not query the MPLS VPN withdrawal routing information, returning error information to obtain the current routing state of the MPLS VPN.

It should be understood that in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program includes program instructions, and the computer program may be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program, when executed by a processor, causes the processor to perform the steps of:

constructing a neighbor relation with the MP-BGP reflector, and collecting an update message of the MP-BGP reflector; analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN; analyzing the current reachable and cancelled routing information of the MPLS VPN according to the related information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN; and feeding back the current routing state of the MPLS VPN to the terminal so as to display the current routing state of the MPLS VPN at the terminal.

The related information of the MPLS VPN comprises multi-protocol reachable routing information, multi-protocol unreachable routing information and extended community attribute information.

In an embodiment, after the step of feeding back the current routing status of the MPLS VPN to the terminal to display the current routing status of the MPLS VPN by the terminal, the processor further performs the following steps:

In an embodiment, when the processor executes the computer program to implement the step of analyzing the MPLS VPN related information of the update message to obtain MPLS VPN related information, the following steps are specifically implemented:

In an embodiment, when the processor executes the computer program to implement the steps of analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into the database, the following steps are specifically implemented:

judging whether the address family information in the multi-protocol reachable routing information is legal or not; if the address family information in the multi-protocol reachable routing information is legal, judging whether the next hop information is analyzed; if the next hop information is not analyzed, analyzing the field value of the next hop information according to the length of the next hop, and updating the field value to a memory for caching; judging whether the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed; if the subnet access point attribute fields in the multi-protocol reachable routing information are not analyzed, analyzing each subnet access point attribute field according to the number of the subnet access points; judging whether the length of the reachable routing list field in the multi-protocol reachable routing information is legal or not; if the length of the reachable route list field in the multi-protocol reachable route information is legal, judging whether the reachable route list field in the multi-protocol reachable route information is analyzed; if the reachable route list field in the multi-protocol reachable route information is not analyzed, analyzing the label attribute, the RD attribute and the IP prefix attribute in the reachable route list field to obtain a multi-protocol reachable route entry; the multi-protocol reachable route entries are updated into the memory cache and the database.

In an embodiment, when the processor executes the computer program to implement the steps of parsing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries, and writing all the multi-protocol unreachable routing entries into the database, the following steps are specifically implemented:

judging whether the address family information in the multi-protocol unreachable routing information is legal or not; if the address family information in the multi-protocol unreachable routing information is legal, judging whether the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal or not; if the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal, analyzing a label attribute, an RD attribute and an IP prefix attribute in the withdrawn routing information field to obtain a multi-protocol unreachable routing entry; and updating the memory cache and the database according to the multi-protocol unreachable route entry.

In an embodiment, the processor, when executing the computer program to implement the steps of parsing the extended community attribute information to obtain extended community attribute information entries, and writing all the extended community attribute information entries into the database, specifically implements the steps of:

judging whether the byte length of the extended community attribute information is legal or not; if the byte length of the extended group attribute information is legal, judging whether the extended group attribute information is analyzed; if the extended community attribute information is not analyzed, judging whether the RT attribute in the extended community attribute information is of a type of 0x 0002; if the RT attribute in the extended community attribute information is of a type 0x0002, analyzing the RT attribute of the type 0x0002 to obtain an extended community attribute information item; updating the extended community attribute information items to a memory cache and a database; if the RT attribute in the extended community attribute information is not of a type 0x0002, judging whether the RT attribute in the extended community attribute information is of a type 0x 0102; if the RT attribute in the extended group attribute information is of a 0x0102 type, analyzing the 0x01022 type RT attribute to obtain an extended group attribute information entry, and updating the extended group attribute information entry into a memory cache and a database; if the RT attribute in the extended community attribute information is not of the 0x0102 type, judging whether the RT attribute in the extended community attribute information is of the 0x0202 type or not; if the RT attribute in the extended community attribute information is of the 0x0202 type, parsing the 0x0202 type RT attribute to obtain an extended community attribute information entry, and updating the extended community attribute information entry into a memory cache and a database.

In an embodiment, when the processor executes the computer program to implement the step of analyzing currently reachable and revoked routing information of the MPLS VPN for the MPLS VPN related information to obtain a current routing state of the MPLS VPN, the following steps are specifically implemented:

judging whether the memory cache has related information of the MPLS VPN or not; if the related information of the MPLS VPN exists in the memory cache, judging whether the current query request queries the reachable routing information of the MPLS VPN; if the current query request is to query the accessible route information of the MPLS VPN, summarizing the accessible route result of the MPLS VPN according to the accessible route entries of the multiprotocol so as to obtain the current route state of the MPLS VPN; if the current query request does not query the accessible routing information of the MPLS VPN, judging whether the current query request queries the withdrawn routing information of the MPLS VPN; if the current query request is to query MPLS VPN withdrawal routing information, summarizing an MPLS VPN reachable routing result according to the multiprotocol unreachable routing entry so as to obtain the current routing state of the MPLS VPN; if the current query request does not query the MPLS VPN withdrawal routing information, returning error information to obtain the current routing state of the MPLS VPN.

The storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, which can store various computer readable storage media of program codes.

Those of ordinary skill in the art will appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.

The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partly contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

An MPLS VPN analysis method, comprising:

constructing a neighbor relation with the MP-BGP reflector, and collecting an update message of the MP-BGP reflector;

analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN;

analyzing the current reachable and cancelled routing information of the MPLS VPN according to the related information of the MPLS VPN to obtain the current routing state of the MPLS VPN;

feeding back the current route state of the MPLS VPN to a terminal so as to display the current route state of the MPLS VPN at the terminal;

the related information of the MPLS VPN comprises multiprotocol reachable routing information, multiprotocol unreachable routing information and extended group attribute information;

the analyzing the related information of the MPLS VPN to the update message to obtain the related information of the MPLS VPN comprises the following steps:

offsetting the withdrawn route length of the MP-BGP reflector according to the updating message;

searching the attribute with the type code of 14 in the updating message to obtain multi-protocol reachable routing information;

searching the attribute with the type code of 15 in the updating message to obtain the multi-protocol unreachable routing information;

searching the attribute with the type code of 16 in the updating message to obtain the attribute information of the extended community;

storing the multi-protocol reachable route information, and updating the multi-protocol reachable route to a system memory cache;

analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into a database;

storing the multi-protocol unreachable route information, and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route;

analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries, and writing all the multi-protocol unreachable routing entries into a database;

storing the extended community attribute information, and updating the extended community attribute information into a system memory cache;

the extended community attribute information is parsed to obtain extended community attribute information entries and all the extended community attribute information entries are written into the database.
2. The MPLS VPN analysis method according to claim 1, wherein the feeding back the current routing status of MPLS VPN to the terminal further comprises, after the terminal displays the current routing status of MPLS VPN:

and storing the current routing state of the MPLS VPN, and inquiring and analyzing the historical routing time condition of the MPLS VPN.
3. The MPLS VPN analysis method according to claim 1, wherein said parsing the multi-protocol reachable route information to obtain multi-protocol reachable route entries and writing all multi-protocol reachable route entries to a database comprises:

judging whether the address family information in the multi-protocol reachable routing information is legal or not;

if the address family information in the multi-protocol reachable routing information is legal, judging whether the next hop information is analyzed;

if the next hop information is not analyzed, analyzing the field value of the next hop information according to the length of the next hop, and updating the field value into a memory for caching;

judging whether the analysis of the subnet access point attribute field in the multi-protocol reachable routing information is completed;

if the subnet access point attribute fields in the multi-protocol reachable routing information are not analyzed, analyzing each subnet access point attribute field according to the number of the subnet access points;

judging whether the length of the reachable route list field in the multi-protocol reachable route information is legal or not;

if the length of the reachable route list field in the multi-protocol reachable route information is legal, judging whether the reachable route list field in the multi-protocol reachable route information is analyzed;

if the reachable route list field in the multi-protocol reachable route information is not analyzed, analyzing the label attribute, RD attribute and IP prefix attribute in the reachable route list field to obtain a multi-protocol reachable route entry;

and updating the multi-protocol reachable route entries into the memory cache and the database.
4. The MPLS VPN analysis method according to claim 1, wherein said parsing the multi-protocol unreachable route information to obtain multi-protocol unreachable route entries and writing all the multi-protocol unreachable route entries to the database comprises:

judging whether the address family information in the multi-protocol unreachable routing information is legal or not;

if the address family information in the multi-protocol unreachable routing information is legal, judging whether the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal or not;

if the length of a withdrawn routing information field in the multi-protocol unreachable routing information is legal, analyzing a label attribute, an RD attribute and an IP prefix attribute in the withdrawn routing information field to obtain a multi-protocol unreachable routing entry;

and updating the memory cache and the database according to the multi-protocol unreachable route entry.
5. The MPLS VPN analysis method according to claim 1, wherein said parsing the extended community attribute information to obtain extended community attribute information entries and writing all extended community attribute information entries to the database comprises:

judging whether the byte length of the extended community attribute information is legal or not;

if the byte length of the extended group attribute information is legal, judging whether the extended group attribute information is analyzed;

if the extended community attribute information is not analyzed, judging whether the RT attribute in the extended community attribute information is of a type of 0x 0002;

if the RT attribute in the extended community attribute information is 0x0002 type, analyzing the 0x0002 type RT attribute to obtain an extended community attribute information item;

updating the extended community attribute information items to a memory cache and a database;

if the RT attribute in the extended community attribute information is not 0x0002 type, judging whether the RT attribute in the extended community attribute information is 0x0102 type;

if the RT attribute in the extended community attribute information is of a 0x0102 type, analyzing the RT attribute of the 0x01022 type to obtain an extended community attribute information item, and updating the extended community attribute information item to a memory cache and a database;

if the RT attribute in the extended community attribute information is not of the type 0x0102, judging whether the RT attribute in the extended community attribute information is of the type 0x 0202;

if the RT attribute in the extended community attribute information is of the 0x0202 type, parsing the 0x0202 type RT attribute to obtain an extended community attribute information entry, and updating the extended community attribute information entry into a memory cache and a database.
6. The MPLS VPN analysis method according to claim 1, wherein the analyzing the currently reachable and withdrawn routing information of MPLS VPN for the MPLS VPN related information to obtain the current routing status of MPLS VPN comprises:

judging whether the memory cache has related information of the MPLS VPN or not;

if the related information of the MPLS VPN exists in the memory cache, judging whether the current query request queries the reachable routing information of the MPLS VPN;

if the current query request is to query the accessible route information of the MPLS VPN, summarizing the accessible route result of the MPLS VPN according to the accessible route entries of the multiprotocol so as to obtain the current route state of the MPLS VPN;

if the current query request does not query the reachable route information of the MPLS VPN, judging whether the current query request queries the route revocation information of the MPLS VPN;

if the current query request is to query MPLS VPN withdrawal routing information, summarizing an MPLS VPN reachable routing result according to the multiprotocol unreachable routing entry so as to obtain the current routing state of the MPLS VPN;

if the current query request does not query the MPLS VPN withdrawal routing information, returning error information to obtain the current routing state of the MPLS VPN.
An MPLS VPN analysis apparatus, comprising:

the neighbor building unit is used for building a neighbor relation with the MP-BGP reflector and collecting the update message of the MP-BGP reflector;

the analysis unit is used for analyzing the related information of the MPLS VPN to obtain the related information of the MPLS VPN;

the analysis unit is used for analyzing the current reachable and cancelled routing information of the MPLS VPN for the related information of the MPLS VPN so as to obtain the current routing state of the MPLS VPN;

a feedback unit, configured to feed back a current routing state of the MPLS VPN to a terminal, so as to display the current routing state of the MPLS VPN at the terminal;

the related information of the MPLS VPN comprises multiprotocol reachable routing information, multiprotocol unreachable routing information and extended group attribute information;

the analyzing the related information of the MPLS VPN to the update message to obtain the related information of the MPLS VPN includes:

offsetting the withdrawn route length of the MP-BGP reflector according to the updating message;

searching the attribute with the type code of 14 in the updating message to obtain multi-protocol reachable routing information;

searching the attribute with the type code of 15 in the updating message to obtain the multi-protocol unreachable routing information;

searching the attribute with the type code of 16 in the updating message to obtain the attribute information of the extended community;

storing the multi-protocol reachable route information, and updating the multi-protocol reachable route to a system memory cache;

analyzing the multi-protocol reachable routing information to obtain multi-protocol reachable routing entries, and writing all the multi-protocol reachable routing entries into a database;

storing the multi-protocol unreachable route information, and deleting the corresponding multi-protocol reachable information in the system memory cache according to the multi-protocol unreachable route;

analyzing the multi-protocol unreachable routing information to obtain multi-protocol unreachable routing entries, and writing all the multi-protocol unreachable routing entries into a database;

storing the extended community attribute information, and updating the extended community attribute information into a system memory cache;

and analyzing the extended community attribute information to obtain extended community attribute information items, and writing all the extended community attribute information items into a database.
8. A computer device, characterized in that the computer device comprises a memory, on which a computer program is stored, and a processor, which when executing the computer program implements the method according to any of claims 1 to 6.
9. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.