WO2013029393A1

WO2013029393A1 - Routing information notification method and device

Info

Publication number: WO2013029393A1
Application number: PCT/CN2012/075584
Authority: WO
Inventors: 成黎; 孙默
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-08-30
Filing date: 2012-05-16
Publication date: 2013-03-07
Also published as: CN102957606B; CN102957606A

Abstract

A routing information notification method and device. The method includes: when a tag router in a virtual aggregation network is publishing a normal routing update message, tagging the routing update message to be published according to the type of the routing prefix: for a VP routing in an autonomous domain to be published, adding an installation tag in the routing update message; and for a routing to be published which is covered within a VP range and a non-aggregation point routing device a prefix need not be loaded by a forwarding information base (FIB), adding a suppression tag in the routing update message. The method above enables an in-domain routing device to recognize a disabled visual prefix routing, thus routing search and recovery processing operations can be performed, data forwarding can be continued, reducing the effect on data forwarding due to virtual prefix routing disability.

Description

Routing information notification method and device

Technical field

The present invention relates to the field of mobile communications and the Internet, and in particular, to a routing information notification method and apparatus.

Background technique

As the primary node device in the network transmission, the routing device completes the addressing and forwarding of data by searching the routing table and matching the routing entries. The routing table includes a Routing Information Base (RIB) and a Forwarding Information Base (FIB). In recent years, the widespread deployment of multi-homed networks and traffic engineering has led to a rapid increase in the number of Internet routes. The warning of IPv4 addresses and the progressive deployment of IPv6 are also the reasons for the rapid increase in the DFZ (Default Free Zone) routing table. The impact of the rapid growth of routes in a communication network includes: On the one hand, it is necessary to increase the storage capacity of the routing table in the routing device, and the cost increases; on the other hand, the number of routes in the network is large, and the route convergence is slow, affecting the entire communication network. Work efficiency.

Different hardware devices are used in the routing device to store different routing tables. RIB tables are large in size and are not directly used for data forwarding. Rigabytes are often used in routing devices to store RIB information in high-capacity, low-cost, slow-speed hardware. In order to ensure the wire-speed forwarding of data, FIB tables are usually stored in hardware devices with high price, fast speed and small capacity. Therefore, from the perspective of cost, the solution to the FIB table capacity problem is more urgent.

To solve the problem of capacity expansion of the FIB table, a related scheme (Visual Aggregation, VA for short) is proposed in the related art, as shown in FIG. 1 . The specific process is to divide the routing information according to the prefix. The routing distributions of the different prefixes are stored in the FIBs of the Aggregation Point Router (APR). The aggregation point routing device aggregates the prefixes that are loaded into a Virtual Prefix (VP) route, and advertises the virtual prefix route as a common route through the BGP (Border Gateway Protocol) routing device. Each routing device in the network performs route calculation according to the existing BGP routing rules, and saves the calculated optimal BGP route in the RIB. When performing FIB loading, the aggregation point routing device loads the prefix (sub-prefix) route of its aggregated prefix block. In the FIB, the non-aggregation point routing device (non-APR) only needs to load the virtual prefix route into the FIB, and does not need to load the prefix route covered by the virtual prefix, thereby compressing the FIB and reducing the FIB storage capacity in the routing table.

In the related art, in order to implement automatic installation of routing information by the routing device in the domain, an automatic configuration scheme is proposed, as shown in FIG. 2, which specifically includes the following two aspects:

The first is the release of routing information. The selected Autonomous System Border Router (ASBR) is set as the tagging router. Configure the virtual prefix range (VP range) on the tag router to indicate the address segment in the address space that is aggregated as a virtual prefix. When the marking router advertises the routing update packet, the device adds the suppression flag to the routing update packet of the VP range that is over the prefix in the virtual prefix range to implement the FIB suppression installation of the routing device in the autonomous domain. The specific implementation manner includes: performing a FIB-loaded prefix route (such as a client prefix, a high-traffic prefix, etc.) for all routing devices in the domain, according to a network configuration policy that does not cover a route, a virtual prefix route, and a virtual prefix coverage in the VP range. When the update is issued, the flag is not marked; the route update text of the other prefix covered by the virtual prefix in the VP range is added by the FIB loading of the routing information. The routing device in the network selects the best BGP route to save in the RIB, and then based on the local policy, FIB loading is performed according to the marking of the routing information. For non-aggregation point routing devices, routing information with suppression flags does not need to be loaded into the FIB, and routes without suppression flags must be FIB loaded. For the aggregation point routing device, if the FIB is loaded with a route with no suppression flag, if the route prefix is the prefix route covered by the aggregated prefix block, even if the route is suppressed, it must be loaded into the FIB. Summary of the invention

At least the following problems exist in the related art: The marking router does not perform special marking when issuing the virtual prefix update packet, and the intra-domain routing device cannot distinguish the virtual prefix route when performing routing loading. If the routing information of the prefix prefixed by the virtual prefix is not loaded in the FIB of the routing device, the routing device cannot continue to perform data forwarding.

The technical problem to be solved by the present invention is to provide a routing information notification method and device, so that the intra-domain routing device can identify the invalid virtual prefix route, thereby performing route search and recovery. Processing operations.

To solve the above technical problem, the present invention provides a method for advertising routing information, including: when a marking router in a virtual aggregation network issues a normal routing update message, the routing update message to be advertised is performed according to the type of the routing prefix. Mark:

The route to the virtual prefix (VP) in the autonomous domain to be advertised is hereinafter referred to as a type of route, and an installation flag is added in the route update message;

For the route to be advertised, the non-aggregation point routing device does not need to forward the prefix loaded by the information base (FIB) in the virtual prefix range (VP range), which is hereinafter referred to as the three types of routes, and the routing update message is used in the routing update message. .

Preferably, the method further includes: a prefix route that does not cover the prefix route in the VP range, and the FIB installation is required for all routing devices in the autonomous domain according to the policy that is covered in the VP range, and is called a type 2 route, and is required according to the type of the route prefix. When the advertised route update message is marked, no mark is added to the second type of route.

Preferably, the routing device in the autonomous domain receives the route update message, and when the route updated in the route update message is the best route, determines whether to perform FIB loading of the route information according to the flag in the route update message:

If the label is not added to the routing update packet, or the installation flag is added to the routing update packet, the routing information is loaded into the FIB.

If the suppression flag is added to the routing update packet, it is determined whether the routing device is an aggregation point routing device of the route, and if yes, the routing information must be loaded into the FIB. Otherwise, the routing information does not need to be performed. FIB loading of routing information.

Preferably, the method further includes: when the marking router determines that the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation marking corresponding to the route, performing the following processing:

Record invalid virtual prefix information;

Find three types of routes in the routing information base (RIB) table that are covered in the expired virtual prefix, and load them into the FIB;

The specific routing update packet of the three types of routes is advertised. The specific routing update packet of the three types of routes is: the routing update packet of the three types of routes is advertised, and the routing update packet is not added. Force 4 can only show itself.

Preferably, the method further includes: when the non-marking router determines that the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation mark corresponding to the route, performing the following processing:

Look for the three types of routes in the RIB table that are covered in the expired virtual prefix and load them into the FIB. Preferably, the route failure refers to that the routing of the virtual prefix loaded by the FIB in the routing device is lost.

Preferably, if the marking router determines that there is a virtual prefix route that is invalid, when the normal routing update of the three types of routes is issued, the virtual prefix information in the invalidation record is matched to determine the route to be advertised. Whether the prefix of the update packet overwritten in the VP range is overwritten in the expired virtual prefix:

If yes, the specific route update message of the three types of routes is advertised; the specific route update message of the three types of routes is: the route update message of the three types of routes is advertised, and no mark is added in the route update message;

Otherwise, the normal route update packet of the three types of routes is advertised, that is, the suppression flag is added to the route update packet.

Preferably, the method further includes:

If the marking router determines that there is a virtual route prefix that is invalid, when the routing update message of the type of route is advertised, the virtual prefix information in the invalidation record is matched to determine a class of the routing update message to be advertised. Whether the virtual prefix corresponding to the route is a failed virtual prefix: If yes, the invalidation record of the invalid virtual prefix is deleted, and the normal routing update packet of the one type of route is advertised, that is, in the advertised route update packet. Adding the installation flag; at the same time, publishing the normal routing update message of the three types of routes that are covered in the expired virtual prefix, that is, adding the suppression flag to the advertised route update; otherwise, publishing the normal type of the route Route update message, that is, add an installation tag to the advertised route update message.

Preferably, the pair of routes adds an installation tag to the routing update message, and the boundary gateway protocol (BGP) extension attribute of the intra-domain transmission is registered by the Internet Digital Assignment Structure (IANA).

The invention also provides a routing information notification device, which is applied to a routing arrangement of a virtual convergence network The device includes: a classification marking module and a message sending module,

The classification marking module is configured to: classify the routes according to the type of the routing prefix as follows: The routing of the virtual prefix in the autonomous domain is called a type of routing; the routing of the device in the VP range and the non-aggregating point does not require FIB loading. The route of the prefix is called the three types of routes; and the normal route update message to be advertised is marked as follows according to the classification, and then sent to the message sending module: For a type of route, added in the route update message Install the tag; for the three types of routes, add a suppression flag to the route update message;

The packet sending module is configured to: send a routing update message.

Preferably, the device further includes a message receiving module,

The message receiving module is configured to: receive a routing update.

Preferably, the classification marking module is further configured to: perform a FIB installation prefix route for all routing devices in the autonomous domain, and a second type of routing according to a prefix route that does not cover the VP range and a policy that is covered in the VP range; When the type of the route prefix marks the route update message to be advertised, no tag is added to the type 2 route.

Preferably, the device further includes an FIB loading module, where the FIB loading module is configured to: determine whether the updated route in the received routing update message is an optimal route, and if yes, update the packet according to the routing The flag determines whether to perform the FIB loading of the routing information: If the marking is not added in the routing update message, or the routing update is added to the routing update, the routing information is loaded into the FIB; if the routing update message is added The suppression flag is used to determine whether the routing device is an aggregation point routing device of the route. If yes, the routing information must be loaded into the FIB. Otherwise, the FIB loading of the routing information is not required.

Preferably, the device further includes a failure processing module, wherein the failure processing module is respectively connected to the FIB loading module and the classification marking module, and the failure processing module is configured to: determine the autonomous domain according to the installation marking corresponding to the route If the route corresponding to the virtual prefix is invalid, determine whether the routing device is a tagged router: If the routing device is a tagged router, record the invalid virtual prefix information, and find the three types of routes in the RIB table that are covered in the invalid virtual prefix. Notifying the FIB loading module to load, and notifying the classification marking module to release the loaded three types of routes; if the routing device is a non-labeling router, searching for the RIB table is covered by the invalid virtual prefix The three types of routes, and notify the FIB load module to load.

Preferably, the routing failure means that the route of the virtual prefix loaded by the FIB in the routing device is out of preference, and the FIB loading module is further configured to: load the three types of routes found by the failure processing module into the FIB.

Preferably, the classification marking module is further configured to: advertise a specific routing update message of the three types of routes loaded by the invalidation processing module according to the notification of the failure processing module, that is, no adding any routing update message The flag is sent to the message sending module for transmission.

Preferably, the classification marking module is further configured to: if there is a virtual route prefix that is invalid, when the normal routing update of the three types of routes is issued, the virtual prefix information in the invalidation record is matched to determine Whether the prefix overwritten in the VP range of the route update message to be advertised is overwritten in the expired virtual prefix:

If yes, the specific routing update message of the three types of routes is advertised, that is, no label is added to the routing update message, and sent to the packet sending module for sending;

Otherwise, the normal route update message of the three types of routes is advertised, that is, the suppression flag is added to the route update message, and sent to the message sending module for transmission.

Preferably, the classification marking module is further configured to: if there is a virtual route prefix that is invalid, when the routing update message of the type of route is advertised, the virtual prefix information in the invalidation record is matched to determine the route to be advertised. Whether the virtual prefix corresponding to a type of route that updates the packet is a failed virtual prefix:

If yes, the invalidation record of the expired virtual prefix is deleted, and the normal routing update packet of the one type of route is advertised, that is, after the installation tag is added to the advertised route update packet, the packet is sent to the packet. The sending module sends the packet, and the normal routing update packet of the three types of routes that are in the expired virtual prefix is advertised, that is, after the suppression flag is added to the advertised routing update packet, the packet is sent to the packet sending module. Send

Otherwise, the normal routing update message of the type of route is advertised, that is, after the installation tag is added to the advertised route update message, the message is sent to the message sending module for sending.

Preferably, the classification marking module is further configured to: the pair of routes in the routing update message Adding an installation tag is implemented by registering a Border Gateway Protocol (BGP) extension attribute for intra-domain transport to the Internet Digital Assignment Structure (IANA).

In the method of the embodiment of the present invention, when the route is automatically installed in the virtual aggregation scheme, the marking router performs special identification on the virtual prefix route, so that in the case that the virtual prefix route in the domain fails, the intra-domain router can identify the failed route according to the identifier. Route the virtual prefix and install the corresponding detailed prefix route to continue data forwarding. This reduces the impact of virtual prefix routing failure on data forwarding. BRIEF abstract

The drawings are intended to provide a further understanding of the invention, and are intended to be illustrative of the invention. In the drawing:

Figure 1 is a schematic diagram of virtual aggregation network deployment;

Figure 2 is a schematic diagram of automatic route installation and deployment in an autonomous domain;

3 is a schematic diagram of a classification mark of a routing update message by a marking router according to an embodiment of the present invention; FIG. 4 is a schematic diagram of a processing flow of an update packet by a routing device in an autonomous domain according to an embodiment of the present invention;

5a is a schematic diagram of a processing flow of a non-marker routing device in an autonomous domain when a virtual prefix corresponding route fails in an embodiment of the present invention;

FIG. 5b is a schematic diagram of a processing flow of a tag routing device in an autonomous domain when a virtual prefix corresponding route fails;

6a is a schematic diagram of a processing flow for an in-domain marking router to issue a type of routing update message in the case that the virtual prefix routing fails in the embodiment of the present invention;

FIG. 6b is a schematic diagram of a processing flow of an update message of a type 3 route issued by a labeling router in a domain in the case of a virtual prefix routing failure according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a routing information notification apparatus according to an embodiment of the present invention. Preferred embodiment of the invention

The present embodiment provides a method for advertising routing information. When a route is automatically installed in a virtual aggregation scheme, the marking router performs special identification on the virtual prefix route. If the virtual prefix routing fails in the domain, the intra-domain router can identify the label according to the label. The invalid route is a virtual prefix route, and the route of the prefix covered by the virtual prefix is installed, and the data forwarding is continued to reduce the impact of the virtual prefix route failure on data forwarding.

Specifically, the routing information advertisement method provided in this embodiment uses the following technical solution: Before marking the update message, the marking router first performs type determination on the route to be advertised according to the type of the route prefix, and marks the route according to the route type. The route update packet includes: a route to a virtual prefix (VP) in the autonomous domain to be advertised, and an installation flag is added to the route update packet;

A suppression flag is added to the route update message for the route to be advertised that is over the virtual prefix range (VP range) and the non-aggregation point routing device does not need the FIB-loaded prefix.

Further, the marking router may determine that the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation flag corresponding to the route, and further perform subsequent processing operations such as searching and recovering the invalid route.

In order to make the objects, the technical solutions and the advantages of the present invention more clearly, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other.

Embodiment 1

This embodiment describes that the marking router distinguishes the normal distribution (which is different from the specific routing update message corresponding to the invalid virtual prefix below. In this paper, the marking router other than the specific routing update message is publishing the update message. Before, the type of the route is judged according to the type of the route prefix, and the update packet is marked according to the route type. In this embodiment, the route is classified into the following three types according to the type of the route prefix:

One type of route: virtual prefix route in the autonomous domain;

Type 2 route: Does not override the prefix route in the VP range and the basis of the coverage in the VP range. The policy requires prefix routing (such as client routing prefix, high traffic special prefix, etc.) for all routing devices in the autonomous domain to perform FIB installation.

The three types of routes are covered in the VP range. The non-aggregation point routing device in the autonomous domain does not need to perform FIB-loaded prefix routing.

When the update packet is issued, the tag router performs different tag processing on the update packets of different types of routes. As shown in Figure 3, the process flow is described as follows:

Step 301: The route type is determined to be a type of route, and when the marking router issues the corresponding update message, the installation mark is added (for example, the Internet Assigned Numbers Authority (IANA) can be registered with a border gateway protocol for intra-domain transmission ( Border Gateway Protocol, BGP) extended attributes to add this tag);

Step 302: The route type is determined to be a type 2 route, and when the labeling router issues the corresponding update message, it does not add any p;

Step 303: The route type is determined to be three types of routes. When the marking router issues the corresponding update message, the suppression flag is added (for example, the BGP extended attribute transmitted in a domain may be registered to add the tag).

Embodiment 2

This embodiment describes the processing flow of the update packet in the intra-domain routing device. The intra-domain routing devices here include tagged routers and untagged router devices within the domain. As shown in Figure 4, when the intra-domain routing device receives the update packet, the processing flow is as follows:

Step 401: The routing device receives the routing update packet.

Step 402: The routing device determines whether the updated route is the best route. If not, the process ends; if yes, go to step 403.

Step 403: The routing device identifies the packet type according to the tag added in the update packet. If the packet is a type 1 or a type 2 route, the route information is directly loaded in the FIB. If the message is a type 3 route, the process proceeds to step 404.

Step 404: The routing device determines whether it is an aggregation node of the routing prefix in the update packet. If yes, the corresponding three types of routes are loaded into the FIB; if not, the FIB loading of the route is not required. Embodiment 3

This embodiment describes the processing flow of the intra-domain routing device when the virtual prefix route fails. When a virtual prefix route fails, the processing flow of the untagged routing device in the autonomous domain and the processing flow of the tag routing device correspond to FIG. 5a and FIG. 5b, respectively.

As shown in Figure 5a, when the untagged routing device in the domain finds that the route corresponding to a virtual prefix is invalid, the process is as follows:

Step 501: According to the installation mark corresponding to the virtual prefix route, the non-marker routing device determines that the route corresponding to a virtual prefix in the domain is invalid. (The route is invalid, and the virtual prefix route loaded by the FIB in the routing device is invalid, and the route is not found after convergence. Other routing information corresponding to the virtual prefix) Step 502: The non-marking routing device searches for three types of routes in the RIB table according to the suppression flag, matches the invalid virtual prefix information, and searches for three types of routes that are covered in the virtual prefix, that is, virtual prefix coverage. Routing information for the prefix;

Step 503: The non-tagged routing device loads the three types of routes found in step 502 into the FIB.

As shown in Figure 5b, when the intra-domain tag routing device finds that the route corresponding to a virtual prefix is invalid, the process is as follows:

Step 504: According to the mark corresponding to the virtual prefix route, the marking routing device determines that the route corresponding to a virtual prefix in the domain is invalid (the route is invalid, and the virtual prefix route loaded by the FIB in the routing device is invalid, and the virtual channel is not found after the route is converged. Other routing information corresponding to the prefix);

Step 505: Mark the routing device to record the invalid virtual prefix information;

Step 506: The marking router searches for three types of routes that are covered under the invalid prefix according to the suppression flag, and loads the routes into the FIB table.

Step 507: The marking router issues a specific routing update of the three types of routes corresponding to the invalid prefix, and advertises the three types of routes loaded in the 506, and does not add any markings in the update (the same as the advertising mode of the second-class routing).

Embodiment 4

This example describes the process of marking an update packet in the intra-domain tagged router when the virtual prefix route fails. Tag routers divide routes into three types. Where the second type of route is not virtual The prefix invalidation effect is affected. Therefore, under the premise that the virtual prefix fails, the second-layer routing update message publishing process of the marking router does not change. The update message issuance flow of one type of route and three types of routes respectively corresponds to FIG. 6a and FIG. 6b.

As shown in Figure 6a, the process of publishing the three types of route update packets is as follows:

Step 601: The marking router classifies the routes that need to be updated, and determines that the routes that need to be updated are three types of routes.

Step 602: There is currently a failed virtual prefix, that is, the invalidation record is not empty. The marking router matches the virtual prefix information in the invalidation record, and determines whether the three types of routes to be advertised are overwritten in the invalid virtual prefix. If the three types of routes are in the invalid virtual prefix, step 603 is performed; if the three types of routes are not covered, the failure is invalid. In the virtual prefix, step 604 is performed.

Step 603: Publish a specific routing update packet that covers the three types of routes under the invalid prefix, that is, no label is added in the routing update packet.

Step 604: Publish the normal routing update ^艮, add the suppression flag.

As shown in Figure 6b, under the premise that the virtual prefix fails, the process of publishing a type of route update packet is as follows:

Step 605: The marking router determines that the route that needs to issue the update packet is a type of route. Step 606: Match the virtual prefix information in the invalid record to determine whether the virtual prefix corresponding to the one type of route is a virtual virtual prefix; if yes, execute Step 608; Otherwise, step 607 is performed; Step 607: If the invalid virtual prefix is not matched, the normal routing update message of the type of route with the expired prefix is issued, and the installation flag is added in the routing update message;

Step 608: If the invalid virtual prefix is matched, that is, the virtual virtual prefix in the domain is restored, the virtual prefix information in the invalidation record is deleted, and the process proceeds to step 609;

Step 609: Publish a normal routing update of a type of route of the invalid virtual prefix, and add an installation flag in the routing update.

Step 610: The normal routing update packet of the three types of routes covered by the invalid virtual prefix is advertised, that is, the suppression flag is added to the routing update packet. Embodiment 5

As shown in FIG. 7, the embodiment of the present invention provides a routing information notification apparatus, which is applied to a routing device of a virtual aggregation network, and the apparatus mainly includes:

The classification tag module is configured to: classify the route according to the type of the route prefix: The route to the virtual prefix in the autonomous domain is called a type of route; the route device that is covered in the VP range and the non-aggregation point does not need FIB loading. The route of the prefix is called the three types of routes; and the normal route update message to be advertised is marked as follows according to the classification, and then sent to the packet sending module for sending: For a type of route, the route update message is added. Install the tag; for the three types of routes, add a suppression flag in the route update message;

The message sending module is configured to send a route update message.

The adding a type of route to the routing update message adds an installation tag to the Internet Digital Distribution Structure (IANA) to register a Border Gateway Protocol (BGP) extended attribute transmitted within the domain.

The classification and marking module is further configured to: perform a FIB installation prefix route for the routing route that does not cover the VP range, and the routing policy that covers the VP range, and all the routing devices in the autonomous domain, and the second type of routing; When a type marks a route update message to be advertised, no tag is added to the type 2 route.

Further, the device in this embodiment further includes a message receiving module and a FIB loading module, where: the message receiving module is configured to receive a routing update message;

The FIB loading module is configured to determine whether the updated route in the received routing update message is the best route, and if yes, determine whether to perform FIB loading of the routing information according to the mark in the route update message:

Further, the device further includes a failure processing module, and the failure processing module is respectively connected to the FIB loading module and the classification marking module. The failure processing module is mainly used to determine whether the routing device is a tagged router when the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation flag corresponding to the route:

If the routing device is a tagged router, the invalid virtual prefix information is recorded, and the three types of routes that are covered in the invalid virtual prefix in the RIB table are searched, the FIB loading module is notified to load, and the classification tag module is notified. Three types of routes loaded;

If the routing device is a non-tagged router, it searches for three types of routes in the RIB table that are overwritten in the invalid virtual prefix, and notifies the FIB loading module to load.

The FIB loading module is used to load the three types of routes found by the failure processing module into the FIB. The classification marking module is further configured to: according to the notification of the failure processing module, issue a specific routing update message of the three types of routes loaded by the invalidation processing module, that is, no label is added in the routing update message, and is sent to the packet sending module. send.

In addition, the classification marking module is further configured to: if a virtual routing route that is invalid is currently present, when the normal routing update of the three types of routes is issued, by matching the virtual prefix information in the invalidation record, Determine whether the prefix overwritten in the VP range of the route update packet to be advertised is overwritten in the invalid virtual prefix:

In addition, the classification marking module is further configured to: if there is a virtual prefix route that is invalid, when the routing update of the type of route is issued, the virtual prefix information in the invalidation record is matched, and the desired Whether the virtual prefix corresponding to a type of route that advertises routing update packets is a virtual prefix that is invalid:

If yes, the invalidation record of the expired virtual prefix is deleted, and the normal routing update packet of the one type of route is advertised, that is, after the installation tag is added to the advertised route update packet, the packet is sent to the packet. The sending module sends the packet, and the normal routing update packet of the three types of routes that are in the expired virtual prefix is advertised, that is, after the suppression flag is added to the advertised routing update packet, the packet is sent to the packet sending module. send; Otherwise, the normal routing update message of the one type of route is advertised, that is, after the installation mark is added to the advertised route update message, the message is sent to the message sending module for sending.

In addition, it should be noted that the routing information advertising apparatus of this embodiment may be applied to any routing device of the virtual aggregation network, including a marking router and a non-marking router, that is, the marking router or the non-marking router in the network has the same at this time. The function.

However, in other embodiments of the present invention, the functions of the marking router and the non-marking router may also be set differently. For example, the above-mentioned classification marking module may be configured only in the marking router, and the non-marking router may not configure the functional module. Moreover, the processing mechanism of the invalidation module of the tag router and the non-label router may also be different, such as the tag router will record the invalid virtual prefix information, the non-marker router does not need to record, and so on.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention. The present invention may be embodied in various other embodiments without departing from the spirit and scope of the invention. Various changes and modifications may be made to the invention, and such changes and modifications are intended to be included within the scope of the appended claims.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

Industrial Applicability In the above method, when the route is automatically installed in the virtual aggregation scheme, the marking router performs special identification on the virtual prefix route. Therefore, in the case that the virtual prefix routing fails in the domain, the intra-domain router can identify the invalid route as virtual according to the identifier. Prefix routing, and install the corresponding detailed prefix route, continue data forwarding, and reduce the impact of virtual prefix routing failure on data forwarding.

Claims

Claim

1. A method for advertising routing information, including:

When a labeled router in a virtual aggregation network advertises a normal route update packet, it marks the route update packet to be advertised according to the type of the route prefix:

2. The method according to claim 1, further comprising:

For a prefix route that does not cover the VP range and a policy that is in the VP range, the prefix route of the FIB installation is required for all routing devices in the autonomous domain.

When the route update packet to be advertised is tagged according to the type of the route prefix, no tag is added to the class 2 route.

3. The method of claim 2, wherein

The routing device in the autonomous domain receives the routing update packet. When the route updated in the routing update packet is the best route, it determines whether to perform the FIB loading of the routing information according to the flag in the routing update packet:

4. The method of claim 1, wherein the method further comprises:

When the marking router determines that the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation flag corresponding to the route, the following processing is performed:

Record invalid virtual prefix information; Find three types of routes in the routing information base (RIB) table that are covered in the expired virtual prefix, and load them into the FIB;

The specific route update message of the three types of routes is advertised. The specific route update message of the three types of routes refers to: the route update message of the three types of routes is advertised, and the routing update message does not add a force port. Ίί^ί can show yourself.

5. The method of claim 1, wherein the method further comprises:

When the non-labeled router determines that the route corresponding to the virtual prefix in the autonomous domain is invalid according to the installation flag corresponding to the route, the following processing is performed:

Look for the three types of routes in the RIB table that are covered in the expired virtual prefix and load them into the FIB.

6. The method according to claim 4 or 5, wherein

The route is invalid. The route of the virtual prefix loaded by the FIB in the routing device is invalid, and the routing information is not found.

7. The method of claim 4, wherein

If the marking router determines that there is a virtual route prefix that is invalid, when the normal routing update message of the three types of routes is advertised, the virtual prefix information in the invalidation record is matched to determine the route update message to be advertised. Whether the prefix covering the VP range is overwritten in the expired virtual prefix:

8. The method of claim 4, wherein the method further comprises:

If the marking router determines that there is a virtual route prefix that is invalid, when the routing update message of the type of route is advertised, the virtual prefix information in the invalidation record is matched to determine a class of the routing update message to be advertised. Whether the virtual prefix corresponding to the route is a virtual prefix that is invalid: if yes, deleting the invalidation record of the invalid virtual prefix, and publishing the route of the one type of route A normal routing update message, that is, an installation tag is added to the advertised route update message. At the same time, the normal route update message of the three types of routes that are covered in the expired virtual prefix is advertised, that is, the advertised route is updated. Add a suppression marker;

Otherwise, the normal routing update message of the one type of route is advertised, that is, the installation flag is added in the published routing update message.

9. The method according to claim 1, wherein the pair of routes add an installation tag to the route update message, and register a border gateway protocol (BGP) extension for intra-domain transmission by the Internet Digital Assignment Structure (IANA). Property implementation.

A routing information notification device, which is applied to a routing device of a virtual aggregation network, the device includes: a classification marking module and a message sending module,

The packet sending module is configured to: send a routing update message.

The device of claim 10, wherein the device further comprises a message receiving module, wherein the message receiving module is configured to: receive a route update message.

The apparatus according to claim 10, wherein the classification marking module is further configured to: perform FIB installation on all routing devices in the autonomous domain for the prefix route that does not cover the VP range and the policy that is covered in the VP range. The prefix route is called the second type of route. When the route update packet to be advertised is marked according to the type of the route prefix, no mark is added to the type 2 route.

The device of claim 12, wherein the device further comprises a FIB loading module, the FIB loading module is configured to: determine whether the updated route in the received routing update message is an optimal route, if yes And determining, according to the marking in the routing update message, whether to perform FIB loading of the routing information: if the marking is not added in the routing update packet, or the installation marking is added in the routing update packet, the routing information is loaded to In FIB; if the routing update is added to the text If the flag is suppressed, it is determined whether the routing device is an aggregation point routing device of the route. If yes, the routing information must be loaded into the FIB. Otherwise, the FIB loading of the routing information is not required.

The device of claim 11, wherein the device further comprises a failure processing module, wherein the failure processing module is respectively connected to the FIB loading module and the classification marking module.

The failure processing module is configured to: determine, according to the installation flag corresponding to the route, that the routing device corresponding to the virtual prefix in the autonomous domain is invalid, determine whether the routing device is a marking router: if the routing device is a marking router, record the invalid virtual prefix. The information is used to find the three types of routes that are covered in the invalid virtual prefix in the RIB table, notify the FIB loading module to load, and notify the classification tag module to issue the three types of routes that are loaded; if the routing device is a non-tagged router, Then, the three types of routes that are covered in the invalid virtual prefix in the RIB table are searched, and the FIB loading module is notified to load.

15. The apparatus according to claim 14, wherein

16. The apparatus according to claim 14, wherein

The FIB loading module is further configured to: load the three types of routes found by the failure processing module into the FIB.

17. The apparatus according to claim 14, wherein

The classification marking module is further configured to: advertise a specific routing update message of the three types of routes loaded by the invalidation processing module according to the notification of the failure processing module, that is, no label is added in the routing update message, and the sending Send to the message sending module.

18. The apparatus according to any one of claims 13-17, wherein

The classification marking module is further configured to: if there is a virtual route prefix that is invalid, when the normal routing update of the three types of routes is issued, the virtual prefix information in the invalidation record is matched to determine the route to be advertised. Whether the prefix of the update packet overwritten in the VP range is overwritten in the expired virtual prefix:

If yes, the specific routing update packet of the three types of routes is advertised, that is, not in the routing update packet. Add any tag and send it to the message sending module for sending;

19. Apparatus according to any of claims 13-17, wherein

The classification tag module is further configured to: if there is a virtual route prefix that is invalid, when the route update message of the type of route is advertised, the virtual prefix information in the invalidation record is matched to determine the route update message to be advertised. Whether the virtual prefix corresponding to a type of route is a virtual prefix that is invalid:

20. The apparatus of claim 10, wherein the classification marking module is further configured to: add a mounting tag to a routing update message for a type of route, registering with an Internet Digital Distribution Structure (IANA) Implementation of the Border Gateway Protocol (BGP) extended attribute for intra-domain transport.