CN101350789A - Method and apparatus for clearing residual LSP banding - Google Patents
Method and apparatus for clearing residual LSP banding Download PDFInfo
- Publication number
- CN101350789A CN101350789A CNA200810222362XA CN200810222362A CN101350789A CN 101350789 A CN101350789 A CN 101350789A CN A200810222362X A CNA200810222362X A CN A200810222362XA CN 200810222362 A CN200810222362 A CN 200810222362A CN 101350789 A CN101350789 A CN 101350789A
- Authority
- CN
- China
- Prior art keywords
- lsp
- fragmentation
- fragment
- received
- locally
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 22
- 238000006062 fragmentation reaction Methods 0.000 claims abstract description 226
- 238000013467 fragmentation Methods 0.000 claims abstract description 225
- 239000012634 fragment Substances 0.000 claims description 172
- 238000004140 cleaning Methods 0.000 abstract 1
- 238000005516 engineering process Methods 0.000 description 7
- 230000032683 aging Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000003672 processing method Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000009792 diffusion process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for cleaning the residual LSP fragmentation and a device thereof. The method comprises: after receiving the LSP fragmentation, a router judges if the Source-ID carried by the LSP fragmentation matches with any of the initial system ID and the additional system ID configured locally; if the matched ID exists, the processing flow which corresponds to receiving the LSP fragmentation sent by the local system is carried out; if the matching fails, when LSP fragmentation received is the first LSP fragmentation, the Normal system-id carried on the first 0 LSP fragmentation is judged if the Normal system-id is equal to the initial system ID configured locally, if two ID are same, the LSP fragmentation received is defined as the residual LSP fragmentation, and the entire network is informed to clean the LSP fragmentation; otherwise, the processing flow which corresponds to receiving the LSP fragmentation sent by other systems is carried out. The invention can promptly clean the residual LSP fragmentation on the network, thereby preventing from generating the black hole router.
Description
Technical Field
The present invention relates to a routing technology in a communication network, and in particular, to a method and an apparatus for removing a Link State Protocol Data Unit (LSP) fragment from a network running from an Intermediate System to an Intermediate System intra-domain routing information exchange Protocol (IS-IS) in the Intermediate System domain.
Background
The IS-IS an interior gateway protocol based on the Shortest Path First (SPF) algorithm, which uses LSP diffusion link state information to ensure that the link state information of the whole network router IS synchronized. Since link state information can be very large, the protocol provides a fragmentation method to fragment LSPs. Each LSP fragment carries an LSP identification (LSP-ID) to uniquely identify the LSP fragment. Table 1 shows a composition structure of LSP-IDs including a system ID (source ID) of 6 bytes, a pseudo node Number (Pseudonode ID) of 1 byte, and an LSP fragment Number (LSP Number) of 1 byte. The length of 1 byte of the LSP fragmentation number determines that one IS-IS router can generate at most 256 LSP fragmentations.
TABLE 1
With the continuous emergence of new technologies and the continuous expansion of network scale, more and more link state information needs to be issued, and 256 LSP fragments have failed to meet the increasing demand. In order to break through the limitation that a single IS-IS router can only issue 256 LSP fragments, RFC3786 provides an LSP fragment extension technique, which generates more LSP fragments by configuring multiple Virtual systems (Virtual systems) under an initial System (organizing System). The initial System IS a router which actually runs an IS-IS protocol and IS identified by an initial System ID (Normal System-ID); the virtual System is attached to the initial System and is identified by an Additional System ID (Additional System-ID), one initial System can be configured with a plurality of virtual systems, and each virtual System can issue 256 expansion LSP fragments. The Source ID in the LSP-ID field of the initial LSP fragment issued by the initial system fills in the initial system ID, the Source ID in the LSP-ID field of the expanded LSP fragment issued by the virtual system fills in the additional system ID, and after receiving the LSP fragment, the carried LSP-ID can be used to judge which system the LSP fragment is issued by.
Fig. 1 shows a flow chart of a process for receiving LSP fragmentation in the prior art, which includes the following steps:
step 101: after receiving the LSP fragment, determining whether the LSP fragment is issued by the local system, if yes, executing step 102; otherwise, step 103 is performed.
For the router supporting the LSP fragmentation extension technique, the determination process is as follows: checking whether the Source-ID in the LSP-ID field of the received LSP fragmentation is matched with any one of the local system IDs, and if the matched ID exists, determining that the LSP fragmentation is issued by the local system; otherwise, determining that the LSP fragmentation is issued by other systems. The local system ID comprises an initial system ID and an additional system ID which are configured locally, and the initial system ID and the additional system ID which are configured locally are recorded on the router.
For the router which does not support the LSP fragmentation expansion technology, because the router does not have a virtual system and does not have an additional system ID, after receiving the LSP fragmentation, directly comparing the initial system ID with the Source-ID of the LSP fragmentation, and if the initial system ID and the Source-ID are the same, determining that the LSP fragmentation is issued by a local system; otherwise, determining that the LSP fragmentation is issued by other systems.
Step 102: executing a processing flow when receiving the LSP fragmentation issued by the local system, comparing the received LSP fragmentation with the LSP fragmentation stored in a link state information base, if the received LSP fragmentation is newer than the locally stored LSP fragmentation (the LSP fragmentation is newer and older through a time sequence number carried in the LSP fragmentation, and the LSP fragmentation is newer if the time sequence number is larger), considering the LSP fragmentation to be the LSP fragmentation issued before, and the local system reissues an updated LSP fragmentation and notifies the whole network router; if the LSP fragmentation does not exist locally, extracting the LSP fragmentation head, and notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the locally stored LSP fragmentation, directly discarding the received LSP fragmentation, and notifying the locally stored LSP fragmentation to achieve that the whole network router stores the latest LSP fragmentation.
Step 103: executing the processing flow when receiving LSP fragmentation issued by other systems, comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, and replacing the locally stored LSP fragmentation if the received LSP fragmentation is newer than locally stored LSP fragmentation; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the locally stored LSP fragmentation, directly discarding the received LSP fragmentation, and notifying the locally stored LSP fragmentation to achieve that the whole network router stores the latest LSP fragmentation.
The synchronization and update of LSP shards can be completed through the process shown in fig. 1, however, this processing method easily results in the generation of black hole routes. For example, referring to the network topology shown in fig. 2, the routers RTA, RTB, and RTC respectively run the IS-IS protocol, and each router supports LSP fragmentation extension technology, where an additional system ID1 IS configured on the RTA, a virtual system corresponding to the RTA publishes a prefix route ip-prefix1 in the extended LSP fragmentation, and after receiving the extended LSP fragmentation, the RTB and RTC calculate that the next hop of the route to reach ip-prefix1 IS the RTA and the RTB, respectively. When a link between the RTA and the RTB fails, the additional system ID1 configured on the RTA and the extended LSP slice corresponding to the additional system are all cleared locally, and the extended LSP slice corresponding to the additional system ID1 remains on other routers in the network. Then, when the RTA restarts to access the network again and the topology relationship among the RTA, the RTB, and the RTC recovers again, the extended LSP fragment issued by the additional system ID1 and remaining on the RTB and the RTC is still regarded as a valid LSP fragment during route calculation, so that both the RTB and the RTC calculate a black hole route with the destination IP-prefix 1. These black hole routes will disappear only when the residual LSP fragment corresponding to the additional system ID1 is left to age from the network, because according to the flow shown in fig. 1, when these residual LSP fragments are returned to the RTA local router, because the additional system ID1 configured on the RTA is not present at this time, the RTA may misunderstand that the residual LSP fragment is issued by other systems, and does not notify other routers on the network to delete the residual LSP fragment. Thus, these residual LSP fragments will remain on the network until its aging period (default configuration, LSP fragment aging period is usually 1200 seconds) comes, and these residual LSP fragments will not age out of the network automatically, and their corresponding black hole routes will not disappear.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for clearing residual LSP fragmentation, and a method and an apparatus for clearing residual LSP fragmentation on a network in time to avoid the generation of black hole routing.
In order to achieve the purpose, the technical scheme provided by the invention is as follows:
a method for clearing a residual link state protocol data unit (LSP) fragment comprises the following steps:
after receiving the LSP fragmentation, the router judges whether the Source-ID carried by the LSP fragmentation is matched with any one of the initial system ID and the additional system ID configured locally, if the matched ID exists, the LSP fragmentation is determined to be issued by the local system, and the processing flow when the LSP fragmentation issued by the local system is received is executed; if the matching fails, judging whether the Normal system-ID carried by the 0 th LSP fragment is the same as the initial system ID configured locally or not when the received LSP fragment is the 0 th LSP fragment, if so, determining that the received LSP fragment is a residual LSP fragment, and informing the whole network of clearing the LSP fragment; otherwise, determining that the received LSP fragmentation is issued by other systems, and executing the processing flow when the LSP fragmentation issued by other systems is received.
The process flow when executing receiving the LSP fragment issued by the local system specifically includes:
comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, if the received LSP fragmentation is newer than the LSP fragmentation stored locally, reissuing an updated LSP fragmentation, and notifying a whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
The process flow when executing receiving the LSP fragment issued by other systems specifically includes:
comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, and replacing the locally stored LSP fragmentation if the received LSP fragmentation is newer than locally stored LSP fragmentation; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
An apparatus for clearing residual LSP fragmentation, comprising: a first judging unit, a second judging unit, a local system fragment processing unit, other system fragment processing units and a clearing fragment notification unit, wherein,
the first judging unit is used for judging whether the Source-ID carried by the LSP fragment is matched with any one of the initial system ID and the additional system ID which are locally configured or not after the LSP fragment is received, if the matched ID exists, the LSP fragment is determined to be issued by the local system, the received LSP fragment is sent to the local system fragment processing unit, and the local system fragment processing unit executes the processing flow when the LSP fragment issued by the local system is received; if the matching fails, the received LSP fragmentation is sent to a second judgment unit;
a second judging unit, configured to, when the received LSP fragment is a 0 th LSP fragment, judge whether a Normal system-ID carried by the 0 th LSP fragment is the same as the locally configured initial system ID, and if so, determine that the received LSP fragment is a residual LSP fragment, send the received LSP fragment to the removal fragment notifying unit, and notify the whole network of removing the LSP fragment by the removal fragment notifying unit; otherwise, determining that the received LSP fragmentation is issued by other systems, sending the received LSP fragmentation to other system fragmentation processing units, and executing the processing flow when the LSP fragmentation issued by other systems is received by other system fragmentation processing units.
After receiving the LSP fragmentation, the local system fragmentation processing unit compares the received LSP fragmentation with LSP fragmentation stored in a link state information base, and if the received LSP fragmentation is newer than the LSP fragmentation stored locally, an updated LSP fragmentation is reissued to notify a whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
After receiving the LSP fragments, the other system fragment processing units compare the received LSP fragments with LSP fragments stored in a link state information base, and if the received LSP fragments are newer than locally stored LSP fragments, the other system fragment processing units replace the locally stored LSP fragments; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
The device is positioned in a router supporting the LSP fragmentation expansion technology.
Therefore, in the technical scheme provided by the invention, when the Source-ID of the received LSP fragment cannot be matched with the local system ID, the method does not directly judge that the LSP fragment is issued by other systems like the prior art, but further judges whether the Normalsystem-ID in the 0 th LSP fragment is matched with the local initial system ID, and if so, determines that the received LSP fragment is a residual LSP fragment and informs the whole network to clear the LSP fragment. Therefore, the situation that the residual LSP fragmentation issued by the deleted virtual system before is considered to be issued by other systems due to the fact that the locally configured virtual system is deleted can be avoided, the 0 th LSP fragmentation of the residual LSP fragmentation can be timely cleared in the whole network, and other LSP fragmentation issued by the same virtual system becomes invalid. Although these non-0 th LSP fragments still exist in its aging period, since the 0 th LSP fragment is already invalid, routers on the network do not calculate the IP prefix routes carried by these LSP fragments when calculating the routes, thereby avoiding the generation of black hole routes.
Drawings
Fig. 1 is a flow chart of processing for receiving LSP fragments in the prior art;
FIG. 2 is a diagram of a prior art network topology;
FIG. 3 is a schematic diagram of a link state information base formed by LSP fragmentation;
fig. 4 is a flowchart of processing for receiving an LSP fragment in the embodiment of the present invention;
fig. 5 is a schematic structural diagram of an apparatus for clearing residual LSP fragmentation in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings and examples.
As known from the LSP fragmentation extension technology specified in RFC3786 protocol, an intermediate system Alias identifier length type value (IS Alias ID TLV) field IS carried in the 0 th LSP fragment (LSP Number ═ 0) issued by the initial system and the virtual system. The format of the IS Alias ID TLV field IS shown in Table 2, and includes an initial system ID (Normal system-ID) of 6 bytes, a pseudo node number (Pseudonode number) of 1 byte, a Sub TLV length (Sub-TLVs length) of 1 byte, and Sub TLV values (Sub-TLVs) of 0-247 bytes.
TABLE 2
Fig. 3 shows a schematic diagram of a link state information base composed of LSP fragments. As can be seen from fig. 3, the Source ID in the LSP-ID field of the initial LSP fragment issued by the initial system fills in the initial system ID, and the Source ID in the LSP-ID field of the extended LSP fragment issued by the virtual system fills in the additional system ID; however, whether the initial LSP fragmentation IS issued by the initial system or the extended LSP fragmentation IS issued by the virtual system, the Normal system-ID in the IS Alias ID TLV field IS filled with the initial system ID. Routers in the network can determine which system the LSP fragment was issued by based on the Source ID in the LSP-ID field and find the initial system based on the Normalsystem-ID in the IS Alias ID TLV field.
The RFC3786 protocol also provides that when an IS-IS system processes LSP fragments issued by an initial system or a virtual system, only the 0 th LSP fragment IS valid, and other LSP fragments are valid. That is, other LSP fragments depend on the 0 th LSP fragment, and if a scheme can be found so that the remaining 0 th LSP fragment can be timely removed, the other LSP fragments also fail, and the black hole route can disappear.
In view of the above characteristics, the present invention provides a processing method after receiving an LSP fragment, which can remove the residual LSP fragment in time. Fig. 4 shows a flow chart of the method, comprising the steps of:
step 401: after receiving the LSP fragment, the router first determines whether the Source-ID in the LSP-ID field of the LSP fragment matches any of the locally configured initial system ID and the additional system ID, if there is a matching ID, it determines that the LSP fragment is issued by the local system, and performs step 402; if the matching fails, it is not directly determined that the LSP fragment is issued by other systems, but step 403 is further performed.
Step 402: executing a processing flow when receiving the LSP fragmentation issued by the local system, comparing the received LSP fragmentation with the LSP fragmentation stored in a link state information base, if the received LSP fragmentation is newer than the LSP fragmentation stored locally, issuing an updated LSP fragmentation again, and notifying a whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the locally stored LSP fragmentation, directly discarding the received LSP fragmentation, and notifying the locally stored LSP fragmentation to achieve that the whole network router stores the latest LSP fragmentation.
Step 403: checking whether the LSP-Number field of the received LSP fragmentation is 0, if not, executing step 405; if the number of the LSP fragments IS 0, that IS, the LSP fragment IS the 0 th LSP fragment, judging whether the Normal system-ID in the carried IS Alias ID TLV field IS the same as the initial system ID configured locally, if so, executing step 404; otherwise, step 405 is performed.
Step 404: and determining that the received LSP fragmentation is residual LSP fragmentation, and informing the whole network to clear the LSP fragmentation.
Step 405: determining that the received LSP fragmentation is issued by other systems, executing a processing flow when the LSP fragmentation issued by other systems is received, comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, and replacing the locally stored LSP fragmentation if the received LSP fragmentation is newer than locally stored LSP fragmentation; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the locally stored LSP fragmentation, directly discarding the received LSP fragmentation, and notifying the locally stored LSP fragmentation to achieve that the whole network router stores the latest LSP fragmentation.
In fig. 4, when the Source-ID of the received LSP fragment cannot be matched with the local system ID, it is not directly determined that the LSP fragment is issued by another system as in the prior art, but it is further determined whether the Normal system-ID in the 0 th LSP fragment matches with the local initial system ID, and if so, it is determined that the received LSP fragment is a residual LSP fragment, and the whole network is notified to clear the LSP fragment. Therefore, the situation that the residual LSP fragmentation issued by the deleted virtual system before is considered to be issued by other systems due to the fact that the locally configured virtual system is deleted can be avoided, the 0 th LSP fragmentation of the residual LSP fragmentation can be timely cleared in the whole network, and other LSP fragmentation issued by the same virtual system becomes invalid. Although these non-0 th LSP fragments still exist in its aging period, since the 0 th LSP fragment is already invalid, routers on the network do not calculate the IP prefix routes carried by these LSP fragments when calculating the routes, thereby avoiding the generation of black hole routes.
Correspondingly, the present invention further provides a device for clearing residual LSP fragmentation, which can be located in a router supporting LSP fragmentation extension technology, and its structure is shown in fig. 5, including: the system comprises a first judgment unit, a second judgment unit, a local system fragment processing unit, other system fragment processing units and a clearing fragment notification unit. Wherein,
the first judging unit is used for judging whether the Source-ID carried by the LSP fragment is matched with any one of the initial system ID and the additional system ID which are locally configured or not after the LSP fragment is received, if the matched ID exists, the LSP fragment is determined to be issued by the local system, the received LSP fragment is sent to the local system fragment processing unit, and the local system fragment processing unit executes the processing flow when the LSP fragment issued by the local system is received; if the matching fails, the received LSP fragmentation is sent to a second judgment unit;
a second judging unit, configured to, when the received LSP fragment is a 0 th LSP fragment, judge whether a Normal system-ID carried by the 0 th LSP fragment is the same as the locally configured initial system ID, and if so, determine that the received LSP fragment is a residual LSP fragment, send the received LSP fragment to the removal fragment notifying unit, and notify the whole network of removing the LSP fragment by the removal fragment notifying unit; otherwise, determining that the received LSP fragmentation is issued by other systems, sending the received LSP fragmentation to other system fragmentation processing units, and executing the processing flow when the LSP fragmentation issued by other systems is received by other system fragmentation processing units.
After receiving the LSP fragmentation, the local system fragmentation processing unit compares the received LSP fragmentation with LSP fragmentation stored in a link state information base, and if the received LSP fragmentation is newer than the LSP fragmentation stored locally, an updated LSP fragmentation is reissued to notify a whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
After receiving the LSP fragments, the other system fragment processing units compare the received LSP fragments with LSP fragments stored in a link state information base, and if the received LSP fragments are newer than locally stored LSP fragments, the other system fragment processing units replace the locally stored LSP fragments; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
The above-mentioned objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned is not intended to limit the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included within the scope of the present invention.
Claims (7)
1. A method for clearing LSP fragments of a residual link state protocol data unit, comprising:
after receiving the LSP fragmentation, the router judges whether the Source-ID carried by the LSP fragmentation is matched with any one of the initial system ID and the additional system ID configured locally, if the matched ID exists, the LSP fragmentation is determined to be issued by the local system, and the processing flow when the LSP fragmentation issued by the local system is received is executed; if the matching fails, judging whether the Normal system-ID carried by the 0 th LSP fragment is the same as the initial system ID configured locally or not when the received LSP fragment is the 0 th LSP fragment, if so, determining that the received LSP fragment is a residual LSP fragment, and informing the whole network of clearing the LSP fragment; otherwise, determining that the received LSP fragmentation is issued by other systems, and executing the processing flow when the LSP fragmentation issued by other systems is received.
2. The method according to claim 1, wherein the executing the processing flow when receiving the LSP fragment issued by the local system specifically includes:
comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, if the received LSP fragmentation is newer than the LSP fragmentation stored locally, reissuing an updated LSP fragmentation, and notifying a whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
3. The method according to claim 1, wherein the executing the processing flow when receiving the LSP fragment issued by the other system specifically includes:
comparing the received LSP fragmentation with LSP fragmentation stored in a link state information base, and replacing the locally stored LSP fragmentation if the received LSP fragmentation is newer than locally stored LSP fragmentation; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
4. An apparatus for clearing residual LSP fragments, comprising: a first judging unit, a second judging unit, a local system fragment processing unit, other system fragment processing units and a clearing fragment notification unit, wherein,
the first judging unit is used for judging whether the Source-ID carried by the LSP fragment is matched with any one of the initial system ID and the additional system ID which are locally configured or not after the LSP fragment is received, if the matched ID exists, the LSP fragment is determined to be issued by the local system, the received LSP fragment is sent to the local system fragment processing unit, and the local system fragment processing unit executes the processing flow when the LSP fragment issued by the local system is received; if the matching fails, the received LSP fragmentation is sent to a second judgment unit;
a second judging unit, configured to, when the received LSP fragment is a 0 th LSP fragment, judge whether a Normal system-ID carried by the 0 th LSP fragment is the same as the locally configured initial system ID, and if so, determine that the received LSP fragment is a residual LSP fragment, send the received LSP fragment to the removal fragment notifying unit, and notify the whole network of removing the LSP fragment by the removal fragment notifying unit; otherwise, determining that the received LSP fragmentation is issued by other systems, sending the received LSP fragmentation to other system fragmentation processing units, and executing the processing flow when the LSP fragmentation issued by other systems is received by other system fragmentation processing units.
5. The apparatus according to claim 4, wherein the local system fragment processing unit, after receiving the LSP fragment, compares the received LSP fragment with LSP fragments stored in a link state information base, and if the received LSP fragment is newer than the locally stored LSP fragment, reissues an updated LSP fragment to notify the whole network router; if the LSP fragmentation does not exist locally, notifying a whole network router to clear the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
6. The apparatus according to claim 4, wherein the other system fragment processing unit, after receiving the LSP fragment, compares the received LSP fragment with LSP fragments stored in the link state information base, and if the received LSP fragment is newer than locally stored LSP fragment, replaces locally stored LSP fragment; if the LSP fragmentation does not exist locally, locally storing the LSP fragmentation; if the received LSP fragmentation is older than the local storage, directly discarding the received LSP fragmentation, and notifying the local storage LSP fragmentation.
7. The apparatus according to any of claims 4 to 6, wherein the apparatus is located in a router supporting LSP fragmentation extension technique.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810222362XA CN101350789B (en) | 2008-09-17 | 2008-09-17 | Method and apparatus for clearing residual LSP banding |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810222362XA CN101350789B (en) | 2008-09-17 | 2008-09-17 | Method and apparatus for clearing residual LSP banding |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101350789A true CN101350789A (en) | 2009-01-21 |
| CN101350789B CN101350789B (en) | 2010-12-08 |
Family
ID=40269371
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810222362XA Expired - Fee Related CN101350789B (en) | 2008-09-17 | 2008-09-17 | Method and apparatus for clearing residual LSP banding |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101350789B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102143032A (en) * | 2010-02-02 | 2011-08-03 | 杭州华三通信技术有限公司 | Method for eliminating residual link state protocol data unit fragments and route equipment |
| CN101640819B (en) * | 2009-09-03 | 2013-01-16 | 杭州华三通信技术有限公司 | Port initialization control method and fiber channel over-Ethernet switch |
| CN103152263A (en) * | 2013-02-06 | 2013-06-12 | 杭州华三通信技术有限公司 | Link status protocol data unit fragmentation updating method and router |
| WO2014187398A1 (en) * | 2013-10-16 | 2014-11-27 | 中兴通讯股份有限公司 | Lsp data packet generating method and device |
| WO2015035570A1 (en) * | 2013-09-11 | 2015-03-19 | Telefonaktiebolaget L M Ericsson (Publ) | Inter-chassis peer and method used therein |
| CN105553856A (en) * | 2015-12-15 | 2016-05-04 | 瑞斯康达科技发展股份有限公司 | Method and device for realizing link-state packet updating |
| US9344504B2 (en) | 2012-11-23 | 2016-05-17 | Hangzhou H3C Technologies Co., Ltd. | Establishing neighbor connection |
| WO2017066971A1 (en) * | 2015-10-22 | 2017-04-27 | 华为技术有限公司 | Method and device for removing a residual label switching path (lsp) |
| CN110912819A (en) * | 2018-09-14 | 2020-03-24 | 迈普通信技术股份有限公司 | Method and device for route convergence |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103560953B (en) * | 2013-10-31 | 2017-03-15 | 杭州华三通信技术有限公司 | The method and device of route oscillation is prevented in the middle of in the middle of a kind of in Routing Protocol |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101517983B (en) * | 2006-10-05 | 2012-02-08 | 艾利森电话股份有限公司 | Equipment and method relative to routing of IP service in mobile wireless network |
| CN101207555B (en) * | 2006-12-18 | 2010-07-14 | 中兴通讯股份有限公司 | Method for automatically clearing over loading bit in the course of avoiding path black hole |
| CN101179515B (en) * | 2007-12-24 | 2010-06-02 | 杭州华三通信技术有限公司 | Method and device for inhibiting black hole routing |
-
2008
- 2008-09-17 CN CN200810222362XA patent/CN101350789B/en not_active Expired - Fee Related
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101640819B (en) * | 2009-09-03 | 2013-01-16 | 杭州华三通信技术有限公司 | Port initialization control method and fiber channel over-Ethernet switch |
| CN102143032A (en) * | 2010-02-02 | 2011-08-03 | 杭州华三通信技术有限公司 | Method for eliminating residual link state protocol data unit fragments and route equipment |
| CN102143032B (en) * | 2010-02-02 | 2014-05-07 | 杭州华三通信技术有限公司 | Method for eliminating residual link state protocol data unit fragments and route equipment |
| US9344504B2 (en) | 2012-11-23 | 2016-05-17 | Hangzhou H3C Technologies Co., Ltd. | Establishing neighbor connection |
| CN103152263B (en) * | 2013-02-06 | 2016-01-06 | 杭州华三通信技术有限公司 | Link State Protocol Data Unit burst update method and router |
| CN103152263A (en) * | 2013-02-06 | 2013-06-12 | 杭州华三通信技术有限公司 | Link status protocol data unit fragmentation updating method and router |
| WO2015035570A1 (en) * | 2013-09-11 | 2015-03-19 | Telefonaktiebolaget L M Ericsson (Publ) | Inter-chassis peer and method used therein |
| US10164863B2 (en) | 2013-09-11 | 2018-12-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Inter-chassis peer and method used therein |
| WO2014187398A1 (en) * | 2013-10-16 | 2014-11-27 | 中兴通讯股份有限公司 | Lsp data packet generating method and device |
| US10097672B2 (en) | 2013-10-16 | 2018-10-09 | Zte Corporation | Method and apparatus for generating link state protocol data packet |
| WO2017066971A1 (en) * | 2015-10-22 | 2017-04-27 | 华为技术有限公司 | Method and device for removing a residual label switching path (lsp) |
| CN105553856A (en) * | 2015-12-15 | 2016-05-04 | 瑞斯康达科技发展股份有限公司 | Method and device for realizing link-state packet updating |
| CN105553856B (en) * | 2015-12-15 | 2018-09-11 | 瑞斯康达科技发展股份有限公司 | A kind of newer method and device of realization link state data packet |
| CN110912819A (en) * | 2018-09-14 | 2020-03-24 | 迈普通信技术股份有限公司 | Method and device for route convergence |
| CN110912819B (en) * | 2018-09-14 | 2022-05-20 | 迈普通信技术股份有限公司 | Method and device for route convergence |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101350789B (en) | 2010-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101350789B (en) | Method and apparatus for clearing residual LSP banding | |
| JP5095823B2 (en) | Transport control server, network system, and transport control method | |
| US8873377B2 (en) | Method and apparatus for hitless failover in networking systems using single database | |
| EP3386156B1 (en) | Failure recovery method, device and storage medium | |
| CN101340369B (en) | Method and router for realizing virtual connection supported optimum restart | |
| EP2664105B1 (en) | Method for backing up link state advertisement | |
| CN102447587B (en) | Graceful restart method based on OSPF (Open Shortest Path First Interior Gateway Protocol) protocol and router thereof | |
| KR101463364B1 (en) | Lookahead computation of routing information | |
| EP3881504A1 (en) | Efficient method of computing backup routes | |
| CN102325080B (en) | Open shortest path first (OSPF) protocol graceful restarting method and device | |
| CN110233801B (en) | Route updating method and device | |
| CN113615132A (en) | Fast flooding topology protection | |
| CN102143032B (en) | Method for eliminating residual link state protocol data unit fragments and route equipment | |
| CN102739543B (en) | Processing method and device of maximum serial number flip of LSP (Link State Protocol) fragments | |
| CN101207555B (en) | Method for automatically clearing over loading bit in the course of avoiding path black hole | |
| CN103746828A (en) | Method and device for network node management | |
| CN111884827A (en) | Method for synchronizing topological information in SFC network and routing network element | |
| CN105024866A (en) | Detection system and method for routing configuration abnormity of IS-ISv6 network | |
| JP2005333383A (en) | Trouble relief processing method and program | |
| CN103152263A (en) | Link status protocol data unit fragmentation updating method and router | |
| US8514876B2 (en) | Method and apparatus for sequencing operations for an incoming interface check in data center ethernet | |
| CN102035906A (en) | IPv6 (Internet Protocol Version 6) protocol address conflict processing method and system based on VRRP (Virtual Router Redundancy Protocol) | |
| CN104301221A (en) | Message routing method and device | |
| CN102006240B (en) | Method, device and system for transferring message in MPLS (Multi-Protocol Label Switching) network | |
| US9143399B2 (en) | Minimizing the number of not-via addresses |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: NEW H3C TECHNOLOGIES Co.,Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: HANGZHOU H3C TECHNOLOGIES Co.,Ltd. |
|
| CP03 | Change of name, title or address | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20101208 |