CN104168192A - Rerouting method and device in fault network - Google Patents
Rerouting method and device in fault network Download PDFInfo
- Publication number
- CN104168192A CN104168192A CN201410390657.3A CN201410390657A CN104168192A CN 104168192 A CN104168192 A CN 104168192A CN 201410390657 A CN201410390657 A CN 201410390657A CN 104168192 A CN104168192 A CN 104168192A
- Authority
- CN
- China
- Prior art keywords
- faulty link
- path
- protection
- information
- bar
- 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.)
- Pending
Links
Abstract
The invention discloses a rerouting method in a fault network. The rerouting method comprises the steps of acquiring fault link information, acquiring target autonomous system (AS) information and fault link initial point AS information of an affected data packet on the fault link, rebuilding a connection relation mathematic model of every two ASs in the same administrative domain according to the fault link information, determining N protection paths from a fault line initial point AS to a target AS, and selecting a practical path from the N protection paths to serve as a protection tunnel, wherein N is a positive integer. The invention further discloses a rerouting device in the fault network.
Description
Technical field
The present invention relates to the routing management field in network, relate in particular to heavy route method and device in a kind of fault network.
Background technology
At present, the Internet has developed into the important communications infrastructure, is carrying many business-critical traffics; Meanwhile, along with the multimedias such as Online Video, game on line, tele-medicine and e-bank being widely used of application in real time, people are more and more higher to the requirement of network performance.
In network, unpredictable accident and abiogenous fault may occur at any time, and a large amount of measurement results shows that link in network fault is ubiquitous phenomenon.The convergence process that needs to depend on Routing Protocol after fault occurs realize fault keep away around, again to recover data forwarding paths end to end.But the problem such as instantaneity because Border Gateway Protocol (BGP) convergence time is long, during convergence is unreachable is serious, reduce the performance of network, be difficult to support crucial interactive service and application in real time.
For this problem, the current two large class solutions that mainly comprise: the one, fast route convergence technology, the one, fast reroute techniques.Wherein, fast route convergence technology, to reduce time of routing convergence as object, although these class methods obtain broad research, due to some design defect and complexity, causes these technology to be difficult to be deployed in actual network.The object that provides backup path to reach quick route recovery is mainly provided fast reroute techniques, but these class methods need extra human configuration to realize effective route protection, the variation that can not automatically conform.In addition, these two class methods are mainly applicable to the situation of single fault, can not effectively process the scene of multiple faults; And multiple faults situation in the main processing domain of technical scheme of existing solution multiple faults scene can not be applicable to again the processing of multiple faults scene between territory.
Summary of the invention
For solving the technical problem of existing existence, the embodiment of the present invention expects to provide heavy route method and device in a kind of fault network, can be between territory ensures the normal forwarding of packet when multilink fault.
The technical scheme of the embodiment of the present invention is achieved in that
The embodiment of the present invention provides the heavy route method in a kind of fault network, and the method comprises:
Obtain faulty link information;
According to described faulty link information, obtain object Autonomous Domain (AS, Autonomous System) information and the faulty link initial point AS information of influenced packet on described faulty link;
According to described faulty link information, re-establish each AS annexation Mathematical Modeling between any two in same management domain, determine that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, described N is positive integer;
From described N bar Protection path, filter out feasible path, as protection tunnel.
In such scheme, described in obtain faulty link information and comprise:
In the time getting Article 1 faulty link information, wait for the default time, obtain other faulty link informations in Preset Time; And/or,
In the time that the faulty link getting affects the normal use in the protection tunnel of having set up, remove described protection tunnel, and obtain the original corresponding faulty link information in described tunnel.
In such scheme, described according to described faulty link information, re-establish each AS annexation Mathematical Modeling between any two in same management domain, determine that the Protection path that N bar arrives described object AS from faulty link initial point AS comprises:
According to the AS information before fault, structure represents each AS two-dimensional matrix of annexation between any two in described same management domain;
According to described faulty link information, delete the annexation between faulty link ends A S;
Use depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determine N bar and arrive from described faulty link initial point AS the AS level Protection path of described object AS.
In such scheme, the described feasible path that filters out from described N bar Protection path comprises as protection tunnel:
Convert one by one described N bar AS level Protection path to corresponding with it N bar router level path;
According to the routing policy information configuring in management domain, delete the path that does not meet described routing policy in described N bar router level path, obtain M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.
In such scheme, after obtaining described protection tunnel, described method also comprises:
By checking that bgp routing table is that described influenced packet is selected nearest described protection tunnel exit.
The embodiment of the present invention also provides the device of the heavy-route in a kind of fault network, and this device comprises: fault acquisition module, Target Acquisition module, Protection path determination module and protection tunnel acquisition module; Wherein,
Described fault acquisition module, for obtaining faulty link information;
Described Target Acquisition module, for according to described faulty link information, obtains object AS information and the faulty link initial point AS information of influenced packet on described faulty link;
Described Protection path determination module, for according to described faulty link information, re-establishes each AS annexation Mathematical Modeling between any two in same management domain, determines that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, described N is positive integer;
Described protection tunnel acquisition module, for filtering out feasible path from described N bar Protection path, as protection tunnel.
In such scheme, described fault acquisition module comprises:
Concurrent fault acquiring unit, in the time getting Article 1 faulty link information, waits for the default time, obtains other faulty link informations in Preset Time; And/or,
Continuous fault acquiring unit, in the time that the faulty link getting affects the normal use in the protection tunnel of having set up, removes described protection tunnel, and obtains the original corresponding faulty link information in described tunnel.
In such scheme, described Protection path determination module comprises:
Modeling unit, for according to the AS information before fault, constructs and represents each AS two-dimensional matrix of annexation between any two in described same management domain;
Updating block, for according to described faulty link information, deletes the annexation between faulty link ends A S;
Routing unit, for using depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determines N bar and arrives from described faulty link initial point AS the AS level Protection path of described object AS.
In such scheme, described protection tunnel acquisition module comprises:
Refinement routing unit, for converting described N bar AS level Protection path one by one to corresponding with it N bar router level path;
Screening unit, for the routing policy information configuring according to management domain, deletes the path that does not meet described routing policy in described N bar router level path, obtains M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.
In such scheme, described device also comprises:
Optimize module: for after obtaining described protection tunnel, by checking that bgp routing table is that described influenced packet is selected nearest described protection tunnel exit.
Heavy route method in the fault network that the embodiment of the present invention provides and device, utilize the information of each AS in same management domain to all visible this features of network controller (Network Controller), for the scene of multiple spot concurrent fault and/or continuous fault, make full use of retrievable information, heavy-route calculating is carried out in classification; In the time that between territory, multilink breaks down, can fast, correctly calculate the Protection path that meets intra domain routing policy, set up protection tunnel; So, under many AS of raising multiple faults environment, in troubleshooting correctness and validity, accelerate heavy-route calculation procedure, improved availability and the reliability of network, and then also ensured that affected packet can normally be forwarded to destination.
Brief description of the drawings
Fig. 1 is the topological structure schematic diagram that has the example network of four AS under same management domain.
The realization flow schematic diagram of heavy route method in the fault network that Fig. 2 provides for the embodiment of the present invention;
The realization flow schematic diagram of heavy route method under an application scenarios in the fault network that Fig. 3 provides for the embodiment of the present invention;
The composition structural representation of heavy-route device in the fault network that Fig. 4 provides for the embodiment of the present invention.
Embodiment
In order to be illustrated more clearly in the embodiment of the present invention and technical scheme, below in conjunction with drawings and Examples, technical scheme of the present invention is described in detail, obviously, described embodiment is a part of embodiment of the present invention, instead of whole embodiment.Basic inventive embodiment, the every other embodiment that those of ordinary skill in the art obtain under the prerequisite of not paying creative work, belongs to the scope of protection of the invention.
In embodiments of the present invention, in network, there is a central controlled network controller, this network controller is connected with each router in network by control link (Control link), and in actual applications, the function of control link is realized by webmaster net.Here, network controller has information function, triggers heavy-route function, result receiving function and order and issue function etc.In this network, each AS belongs to same management domain, the information of each AS comprises configuration information, routing iinformation and policy information etc., these information are all visible concerning network controller, and these information can be collected and be saved in database by the information module in network controller.
Fig. 1 is the topological structure schematic diagram that has the example network of four AS under same management domain, and in Fig. 1, chain-dotted line represents control link, and heavy line represents domain-to-domain link (EBGP link), link (IBGP link) in fine line representative domain; AS1～AS4 represents four Autonomous Domains under same management domain.When the embodiment of the present invention especially multilink fault occurs for multiple AS in the network in same management domain, need to again find transmission path to affected packet, i.e. the situation of heavy-route; Wherein, affected packet refers to the packet that should transmit on faulty link.
In embodiments of the present invention, Protection path refers to the transmission path for transmitting (as: AS level) on the router rank that affected packet calculates; Protection tunnel refers to other transmission path of router level calculating for transmitting affected packet; The outlet in protection tunnel refers to last router in protection tunnel.
The realization flow schematic diagram of heavy route method in the fault network that Fig. 2 provides for the embodiment of the present invention, as shown in Figure 2, this heavy route method comprises:
Step 101, obtains faulty link information;
Concrete, in the time breaking down in network, faulty link information collected by trigger network controller by faulty link, and the type of failure judgement, and multilink fault can be divided into multiple spot concurrent fault and continuous fault two classes conventionally.
After multiple spot concurrent fault occurs in network, owing to there is unfixed time delay, network controller does not likely get whole faulty links at synchronization; Therefore,, if processed at once receiving after Article 1 fault message, will make the Protection path calculating not is for the whole concurrent faults in network, thereby likely causes Protection path unavailable.
Thereby further, in the time getting Article 1 faulty link information, wait for the default time, obtain other faulty link informations in Preset Time.The set of frequency that the described default time is occurred according to network failure by network manager, generally can be set to 1 to 3 second.
Concrete, for ensureing to collect whole multiple spot concurrent fault information, a default stand-by period, in the time that network controller gets Article 1 faulty link information, within the stand-by period, continue to collect faulty link information, until the stand-by period finishes.
For continuous fault, key is to judge whether consequent malfunction has influence on the protection tunnel of having set up; Therefore further, in the time that the faulty link getting affects the normal use in the protection tunnel of having set up, remove described protection tunnel, and obtain the original corresponding faulty link information in described tunnel.
Concrete, in the time judging whether consequent malfunction affects existing protection tunnel, there are two kinds of situations to need to consider: the first situation is that consequent malfunction occurs on the protection tunnel of having set up; The second situation is that consequent malfunction does not occur on protection tunnel, but after occurring in the outlet in protection tunnel, this situation is also by the normal use in impact protection tunnel.In the time that consequent malfunction is above one of two things, just the existing protection tunnel that is subject to consequent malfunction impact need to be removed, and obtain the formerly faulty link information corresponding with this protection tunnel, and consequent malfunction link information is together by following step process; In the time that consequent malfunction does not affect existing protection tunnel, only need, for consequent malfunction, carry out heavy-route calculating.
Step 102, according to described faulty link information, obtains object AS information and the faulty link initial point AS information of influenced packet on described faulty link;
Concrete, in the time getting faulty link information, network controller first wants on failure judgement link, whether there is affected packet; The method of judgement is: checking the routing table of the initial point router of faulty link, if the end-to-end router that the down hop of the network prefix of packet is faulty link is influenced packet, otherwise is unaffected packet.If there is no affected packet, do not need to carry out heavy-route; In the time defining affected packet, obtain the AS information at this place, packet rs destination ground and have influence on the AS information at the faulty link initial point place of this packet.
Especially; for example, because network controller can will be kept at after AS informations all in network in specific memory space (: database); therefore network controller can be judged according to the AS annexation in the faulty link information having got and network: except faulty link; whether faulty link initial point AS also there are other domain-to-domain links around; in the time not there are not other domain-to-domain links; show can not have protection tunnel in current network, thereby needn't carry out follow-up heavy-route and calculate.
Step 103, according to described faulty link information, re-establishes each AS annexation Mathematical Modeling between any two in same management domain, determines that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, N is positive integer.
Concrete, step 103 comprises the following steps:
Step a: according to the AS information before fault, structure represents each AS two-dimensional matrix of annexation between any two in described same management domain;
Step b: according to described faulty link information, delete the annexation between faulty link ends A S;
Step c: use depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determine N bar and arrive from described faulty link initial point AS the AS level Protection path of described object AS.
Concrete, network controller can be from preserving the memory space of all AS information, gets the information of each AS in the front management domain of fault generation; According to the AS information obtaining, can construct a two-dimensional matrix, to represent each AS annexation between any two; Also can represent each AS annexation between any two by other Mathematical Modelings such as bivariate tables herein.
In this step, all carry out for every the faulty link getting: according to the current faulty link information getting, the annexation between the AS at these faulty link two ends is deleted in two-dimensional matrix; Finally obtain the two-dimensional matrix after upgrading;
Here the two-dimensional matrix after the renewal obtaining, represents that each AS annexation between any two in rear management domain occurs fault.
In this step, use depth-first traversal algorithm, in the described two-dimensional matrix after renewal, calculate N bar and arrive from faulty link initial point AS the Protection path of described object AS, obviously, these Protection paths are AS levels.
Especially; in order to ensure to solve the computational process energy Fast Convergent of Protection path; can set the Protection path that only calculates AS_PATH<=H; it is the Protection path that the jumping figure of AS is less than or equal to H; wherein; H is configurable variable, and this variable can be configured according to the situation of concrete network.In the time that network size is large, H can be configured to larger value; When network size hour, H can be configured to less value; Concrete, H is positive integer, does not limit concrete span.For example, having in the management domain of 11 AS, the value of H can be set to 2～6.
Step 104 filters out feasible path from described N bar Protection path, as protection tunnel;
Concrete, through after step 103, obtain N bar Protection path, whether this N bar Protection path calculates in the ideal case, pratical and feasible need to screening according to the routing policy in network.For example, having in the management domain of 11 AS, use said method to obtain Protection path: AS1-AS3-AS5-AS7 and AS1-AS2-AS5-AS7; But AS5 uses the order of AS path list to forbid passing through from the packet of AS3, therefore AS1-AS3-AS5-AS7 has violated the routing policy of AS5 use path list command configuration, is infeasible; After screening, obtain feasible path AS1-AS2-AS5-AS7 and can be used as the basis of protecting tunnel.
Further, obtain after the Protection path of N bar AS level via step 103, step 104 can comprise:
Convert one by one described N bar AS level Protection path to corresponding with it N bar router level path;
According to the routing policy information configuring in management domain, delete the path that does not meet described routing policy in described N bar router level path, obtain M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.Described routing policy refers to the information that orders such as using prefix list, AS path list, group's list and route mapping generates, to reach the object of controlling network route.
Concrete, inter-domain routing system allows each AS to configure different routing policies, to meet the needs of self.For the strategy of routing configuration between compliant domain, network controller, according to AS information and the route-map preserved in database, first converts described N bar AS level Protection path to corresponding with it N bar router level path one by one; Again according to the routing policy information configuring in each AS in network; the all Protection paths that calculate are carried out to policy filtering; run counter to the path of routing policy to delete, thereby obtain the feasible path that M bar meets routing policy, built the reasonability in protection tunnel to ensure.
Further, after obtaining described protection tunnel, the method also comprises: by checking that Border Gateway Protocol (BGP) routing table is that described influenced packet is selected nearest described protection tunnel exit.
Concrete, after obtaining one or more protection tunnel, for the packet that is affected is selected nearest protection tunnel exit, that is: select the shortest transmission path for influenced packet and transmit, to improve the efficiency of transmission of packet.
Especially, in the time there is the above nearest described protection tunnel exit, that is:, while there is one or more the shortest transmission path, can be that influenced packet is selected protection tunnel exit according to the size of Router Distinguisher (RID).
Heavy route method in the fault network that the embodiment of the present invention provides, utilize the information of each AS in same management domain to all visible this features of network controller, for the scene of multiple spot concurrent fault and/or continuous fault, make full use of retrievable information, heavy-route calculating is carried out in classification; In the time that between territory, multilink breaks down, can fast, correctly calculate the Protection path that meets intra domain routing policy, set up protection tunnel; So, under many AS of raising multiple faults environment, in troubleshooting correctness and validity, accelerate heavy-route calculation procedure, improved availability and the reliability of network, and then also ensured that affected packet can normally be forwarded to destination.
The realization flow schematic diagram of heavy route method under an application scenarios in the fault network that Fig. 3 provides for the embodiment of the present invention.In this embodiment, as shown in Figure 1, Autonomous Domain AS1, AS2, AS3 and AS4 belong to same management domain to network topology structure; In network, have a central controlled network controller, network controller is connected with each router in network by control link; In actual applications, the function of control link is realized by webmaster net.
Here, network controller has information function, triggers tunnel computing function, result receiving function and order and issue function etc.; In this network, the information of these four AS comprises configuration information, routing iinformation and policy information etc., the information of these AS is all visible concerning network manager, and the information of these AS can be collected and be saved in database by the information module in network controller.
In the time there is link failure in network, the fault scenes identification module of network controller can failure judgement type, and carries out heavy-route calculating, and as shown in Figure 3, this heavy route method comprises the following steps:
Step 301, judges whether to start timer, if do not start, turns to step 302, if start, turns to step 303;
Step 302, starts timer;
Step 303, judges that whether timer is overtime, if do not have overtimely, judges, until when overtime, turn to step 304 always;
Step 304, judges in network whether have the protection tunnel of having set up, and if so, turns to step 305, otherwise, turn to step 307;
Step 305, whether failure judgement has influence on the normal use in existing protection tunnel, if so, turns to step 306, otherwise, turn to step 307;
Step 306, removes affected protection tunnel, and the input that the faulty link of former faulty link corresponding protection tunnel and this generation is together calculated as heavy-route, to calculate more accurately Protection path;
Step 307, the sequencing occurring according to fault is selected the faulty link of this processing;
Step 308, judges on the faulty link of processing whether have affected packet, if so, turns to step 311, otherwise, turn to step 309;
Step 309, does not have affected prefix on this faulty link, need to not set up protection tunnel from this end;
Step 310, checks and whether also has other untreated faulty link, if so, turn to step 307, otherwise, turn to step 320;
Step 311, the AS information of preserving according to database, judges whether other domain-to-domain link in addition, if so, turns to step 313, otherwise, turn to step 312;
Step 312, without other EBGP links, calculates Protection path failure, waits for that next fault triggers, and finishes this handling process;
Step 313, according to the AS information of preserving in database, structure represents the two-dimensional matrix of annexation between AS, and deletes the annexation between faulty link ends A S;
Step 314, is used depth-first traversal algorithm, is related in two-dimensional matrix at AS, obtains the N bar AS level path of the object AS that arrives all influenced packets;
Step 315, according to the AS preserving in database and route-map, the AS level path that step 314 is obtained changes into corresponding router level path;
Step 316, according to the routing policy information configuring in network, policy filtering is carried out in the router level path that step 315 is obtained, and deletes the path that does not meet routing policy, obtains meeting the feasible path of routing policy;
Step 317, for need influenced packet to be processed, the feasible path obtaining, takes out set of routers corresponding on path in turn from step 316;
Step 318, by checking bgp routing table, for influenced packet is selected nearest feasible path outlet, as protection tunnel exit; If exist more than one, select the outlet in protection tunnel according to the size of RID; And protection tunnel and outlet thereof are saved in database;
Step 319, judges whether to also have untreated faulty link, if so, turns to step 307, otherwise, turn to step 320;
Step 320, this batch of error protection path computing is complete, waits for that next fault triggers.
Heavy route method in the fault network that the embodiment of the present invention provides, utilize the information of each AS in same management domain to all visible this features of network controller, for multiple spot concurrent fault and this two classes fault scenes of continuous fault, make full use of retrievable information, heavy-route calculating is carried out in classification; In the time of multilink generation concurrent fault between territory or continuous fault, can fast, correctly calculate the Protection path that meets intra domain routing policy, set up protection tunnel; So, in improving the correctness and validity of troubleshooting under many AS multiple faults environment, accelerate heavy-route calculation procedure, improved availability and the reliability of network, and then also ensured that affected packet can normally be forwarded to destination.
Fig. 4 is the composition structural representation of heavy-route device in the fault network that provides of the embodiment of the present invention, as shown in Figure 4, this heavy-route device comprises: fault acquisition module 41, Target Acquisition module 42, Protection path determination module 43 and protection tunnel acquisition module 44; Wherein,
Fault acquisition module 41, for obtaining faulty link information;
Target Acquisition module 42, for according to described faulty link information, obtains object AS information and the faulty link initial point AS information of influenced packet on described faulty link;
Protection path determination module 43, for according to described faulty link information, re-establishes each AS annexation Mathematical Modeling between any two in same management domain, determines that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, N is positive integer;
Protection tunnel acquisition module 44, for filtering out feasible path from described N bar Protection path, as protection tunnel.
Further, described fault acquisition module 41 comprises:
Concurrent fault acquiring unit, in the time getting Article 1 faulty link information, waits for the default time, obtains other faulty link informations in Preset Time; And/or,
Continuous fault acquiring unit, in the time that the faulty link getting affects the normal use in the protection tunnel of having set up, removes described protection tunnel, and obtains the original corresponding faulty link information in described tunnel.
Further, described Protection path determination module 43 comprises:
Modeling unit, for according to the AS information before fault, constructs and represents each AS two-dimensional matrix of annexation between any two in described same management domain;
Updating block, for according to described faulty link information, deletes the annexation between faulty link ends A S;
Routing unit, for using depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determines N bar and arrives from described faulty link initial point AS the AS level Protection path of described object AS.
Further, described protection tunnel acquisition module 44 comprises:
Refinement routing unit, for converting described N bar AS level Protection path one by one to corresponding with it N bar router level path;
Screening unit, for the routing policy information configuring according to management domain, deletes the path that does not meet described routing policy in described N bar router level path, obtains M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.
Further, described heavy-route device also can comprise:
Optimize module: for after obtaining described protection tunnel, by checking that bgp routing table is that described influenced packet is selected nearest described protection tunnel exit.
In actual applications, described fault acquisition module 41, Target Acquisition module 42, Protection path determination module 43, protection tunnel acquisition module 44, optimization module and concurrent fault acquiring unit, continuous fault acquiring unit, modeling unit, updating block, routing unit, refinement routing unit, screening unit can be realized by the central processing unit (CPU), microprocessor (MPU), digital signal processor (DSP) or the field programmable gate array (FPGA) that are positioned at described network controller.
Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt hardware implementation example, implement software example or the form in conjunction with the embodiment of software and hardware aspect.And the present invention can adopt the form at one or more upper computer programs of implementing of computer-usable storage medium (including but not limited to magnetic disc store and optical memory etc.) that wherein include computer usable program code.
The present invention is with reference to describing according to flow chart and/or the block diagram of the method for the embodiment of the present invention, equipment (system) and computer program.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or the combination of square frame.Can provide these computer program instructions to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, the instruction that makes to carry out by the processor of computer or other programmable data processing device produces the device for realizing the function of specifying at flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.
These computer program instructions also can be stored in energy vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work, the instruction that makes to be stored in this computer-readable memory produces the manufacture that comprises command device, and this command device is realized the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, make to carry out sequence of operations step to produce computer implemented processing on computer or other programmable devices, thereby the instruction of carrying out is provided for realizing the step of the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame on computer or other programmable devices.
The above, be only preferred embodiment of the present invention, is not intended to limit protection scope of the present invention.
Claims (10)
1. the heavy route method in fault network, is characterized in that, described method comprises:
Obtain faulty link information;
According to described faulty link information, obtain object Autonomous Domain AS information and the faulty link initial point AS information of influenced packet on described faulty link;
According to described faulty link information, re-establish each AS annexation Mathematical Modeling between any two in same management domain, determine that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, described N is positive integer;
From described N bar Protection path, filter out feasible path, as protection tunnel.
2. heavy route method according to claim 1, is characterized in that, described in obtain faulty link information and comprise:
In the time getting Article 1 faulty link information, wait for the default time, obtain other faulty link informations in Preset Time; And/or,
In the time that the faulty link getting affects the normal use in the protection tunnel of having set up, remove described protection tunnel, and obtain the original corresponding faulty link information in described tunnel.
3. heavy route method according to claim 1; it is characterized in that; described according to described faulty link information, re-establish each AS annexation Mathematical Modeling between any two in same management domain, determine that the Protection path that N bar arrives described object AS from faulty link initial point AS comprises:
According to the AS information before fault, structure represents each AS two-dimensional matrix of annexation between any two in described same management domain;
According to described faulty link information, delete the annexation between faulty link ends A S;
Use depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determine N bar and arrive from described faulty link initial point AS the AS level Protection path of described object AS.
4. heavy route method according to claim 3, is characterized in that, the described feasible path that filters out from described N bar Protection path comprises as protection tunnel:
Convert one by one described N bar AS level Protection path to corresponding with it N bar router level path;
According to the routing policy information configuring in management domain, delete the path that does not meet described routing policy in described N bar router level path, obtain M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.
5. heavy route method according to claim 1, is characterized in that, after obtaining described protection tunnel, described method also comprises:
By checking that Border Gateway Protocol (BGP) routing table is that described influenced packet is selected nearest described protection tunnel exit.
6. the heavy-route device in fault network, is characterized in that, described device comprises: fault acquisition module, Target Acquisition module, Protection path determination module and protection tunnel acquisition module; Wherein,
Described fault acquisition module, for obtaining faulty link information;
Described Target Acquisition module, for according to described faulty link information, obtains object AS information and the faulty link initial point AS information of influenced packet on described faulty link;
Described Protection path determination module, for according to described faulty link information, re-establishes each AS annexation Mathematical Modeling between any two in same management domain, determines that N bar arrives the Protection path of described object AS from described faulty link initial point AS; Wherein, described N is positive integer;
Described protection tunnel acquisition module, for filtering out feasible path from described N bar Protection path, as protection tunnel.
7. heavy-route device according to claim 6, is characterized in that, described fault acquisition module comprises:
Concurrent fault acquiring unit, in the time getting Article 1 faulty link information, waits for the default time, obtains other faulty link informations in Preset Time; And/or,
Continuous fault acquiring unit, in the time that the faulty link getting affects the normal use in the protection tunnel of having set up, removes described protection tunnel, and obtains the original corresponding faulty link information in described tunnel.
8. heavy-route device according to claim 6, is characterized in that, described Protection path determination module comprises:
Modeling unit, for according to the AS information before fault, constructs and represents each AS two-dimensional matrix of annexation between any two in described same management domain;
Updating block, for according to described faulty link information, deletes the annexation between faulty link ends A S;
Routing unit, for using depth-first traversal algorithm, in the described two-dimensional matrix after renewal, determines N bar and arrives from described faulty link initial point AS the AS level Protection path of described object AS.
9. heavy-route device according to claim 8, is characterized in that, described protection tunnel acquisition module comprises:
Refinement routing unit, for converting described N bar AS level Protection path one by one to corresponding with it N bar router level path;
Screening unit, for the routing policy information configuring according to management domain, deletes the path that does not meet described routing policy in described N bar router level path, obtains M bar feasible path, as protection tunnel; Wherein, described 1≤M≤N, M is positive integer.
10. heavy-route device according to claim 6, is characterized in that, described device also comprises:
Optimize module: for after obtaining described protection tunnel, by checking that Border Gateway Protocol (BGP) routing table is that described influenced packet is selected nearest described protection tunnel exit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410390657.3A CN104168192A (en) | 2014-08-08 | 2014-08-08 | Rerouting method and device in fault network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410390657.3A CN104168192A (en) | 2014-08-08 | 2014-08-08 | Rerouting method and device in fault network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104168192A true CN104168192A (en) | 2014-11-26 |
Family
ID=51911833
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410390657.3A Pending CN104168192A (en) | 2014-08-08 | 2014-08-08 | Rerouting method and device in fault network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104168192A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104980351A (en) * | 2014-12-26 | 2015-10-14 | 深圳市新格林耐特通信技术有限公司 | Fast reroute method based on SDN network |
| WO2016202194A1 (en) * | 2015-06-19 | 2016-12-22 | 中兴通讯股份有限公司 | Method and apparatus for implementing service immigration |
| CN107659424A (en) * | 2016-07-26 | 2018-02-02 | 中兴通讯股份有限公司 | A kind of service tunnel robs circulation method and network management platform |
| CN110943759A (en) * | 2019-11-12 | 2020-03-31 | 国家电网有限公司信息通信分公司 | Electric power communication link data checking method based on depth-first search algorithm |
| CN116436844A (en) * | 2023-06-13 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Routing oscillation positioning method and device, storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1879356A (en) * | 2003-11-21 | 2006-12-13 | 思科技术公司 | Method and apparatus for determining network routing information based on shared risk link group information |
| US20090225652A1 (en) * | 2008-03-07 | 2009-09-10 | Jean-Philippe Vasseur | Locating tunnel failure based on next-next hop connectivity in a computer network |
| US20110063985A1 (en) * | 2009-09-17 | 2011-03-17 | Heng Wang | Methods, apparatus and articles of manufacture to monitor tunnels within traffic engineering/fast reroute enabled networks |
| CN102158397A (en) * | 2011-02-17 | 2011-08-17 | 中兴通讯股份有限公司 | Re-route method and point local repair (PLR) node |
| CN102932255A (en) * | 2012-09-06 | 2013-02-13 | 华为技术有限公司 | Method and device for selecting tunnel path |
-
2014
- 2014-08-08 CN CN201410390657.3A patent/CN104168192A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1879356A (en) * | 2003-11-21 | 2006-12-13 | 思科技术公司 | Method and apparatus for determining network routing information based on shared risk link group information |
| US20090225652A1 (en) * | 2008-03-07 | 2009-09-10 | Jean-Philippe Vasseur | Locating tunnel failure based on next-next hop connectivity in a computer network |
| US20110063985A1 (en) * | 2009-09-17 | 2011-03-17 | Heng Wang | Methods, apparatus and articles of manufacture to monitor tunnels within traffic engineering/fast reroute enabled networks |
| CN102158397A (en) * | 2011-02-17 | 2011-08-17 | 中兴通讯股份有限公司 | Re-route method and point local repair (PLR) node |
| CN102932255A (en) * | 2012-09-06 | 2013-02-13 | 华为技术有限公司 | Method and device for selecting tunnel path |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104980351A (en) * | 2014-12-26 | 2015-10-14 | 深圳市新格林耐特通信技术有限公司 | Fast reroute method based on SDN network |
| WO2016202194A1 (en) * | 2015-06-19 | 2016-12-22 | 中兴通讯股份有限公司 | Method and apparatus for implementing service immigration |
| CN107659424A (en) * | 2016-07-26 | 2018-02-02 | 中兴通讯股份有限公司 | A kind of service tunnel robs circulation method and network management platform |
| CN107659424B (en) * | 2016-07-26 | 2022-07-05 | 中兴通讯股份有限公司 | Service tunnel emergency-in method and network management platform |
| CN110943759A (en) * | 2019-11-12 | 2020-03-31 | 国家电网有限公司信息通信分公司 | Electric power communication link data checking method based on depth-first search algorithm |
| CN116436844A (en) * | 2023-06-13 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Routing oscillation positioning method and device, storage medium and electronic equipment |
| CN116436844B (en) * | 2023-06-13 | 2023-09-08 | 苏州浪潮智能科技有限公司 | Routing oscillation positioning method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10742556B2 (en) | Tactical traffic engineering based on segment routing policies | |
| US10855575B2 (en) | Adaptive traffic routing in a software-defined wide area network | |
| US9647944B2 (en) | Segment routing based wide area network orchestration in a network environment | |
| KR102002189B1 (en) | Method and apparatus for resilient routing of control traffic in a split-architecture system | |
| CN106464589B (en) | Method and apparatus for partial software defined network switch replacement in IP networks | |
| WO2011155510A1 (en) | Communication system, control apparatus, packet capture method and program | |
| CN104168192A (en) | Rerouting method and device in fault network | |
| CN110891018B (en) | Network traffic recovery method and device, SDN controller and storage medium | |
| CN104158739A (en) | IP (Internet Protocol) traffic engineering (TE) management method and device | |
| CN103152261A (en) | Method and equipment for generating and distributing link state protocol data unit fragment messages | |
| CN109889444A (en) | A kind of methods, devices and systems of planning path | |
| Al Mtawa et al. | Migrating from legacy to software defined networks: A network reliability perspective | |
| CN113347059B (en) | In-band network telemetering optimal detection path planning method based on fixed probe position | |
| CN106470165B (en) | Load sharing method, system and related equipment | |
| CN114448868B (en) | Path scheduling method, device and equipment based on segmented routing strategy | |
| JP5102804B2 (en) | Congestion impact evaluation apparatus, link traffic calculation method and program thereof | |
| US10924382B1 (en) | Rapid and verifiable network configuration repair | |
| CN110247845B (en) | Method for generating protection route in communication network | |
| JP5576837B2 (en) | Route information update system and route information update method | |
| Kumar et al. | Validating resiliency in software defined networks for smart grids | |
| EP3076610A1 (en) | Cross-domain path processing method and device | |
| Schneider et al. | Taming the transient while reconfiguring BGP | |
| JP6777615B2 (en) | Coping device, coping method and program | |
| CN109155756B (en) | Method and system for adding electrical layer resources | |
| Gokarslan et al. | Carbide: Highly Reliable Networks Through Real-Time Multiple Control Plane Composition |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20141126 |