CN114143247A

CN114143247A - IP relay circuit flow emigration and emigration method and device

Info

Publication number: CN114143247A
Application number: CN202111293289.7A
Authority: CN
Inventors: 杨雁武
Original assignee: Unihub China Information Technology Co Ltd
Current assignee: Unihub China Information Technology Co Ltd
Priority date: 2021-11-03
Filing date: 2021-11-03
Publication date: 2022-03-04

Abstract

The invention discloses a method and a device for migrating IP relay circuit flow, wherein the method comprises the following steps: decomposing a circuit into two ends, and synchronously processing the two ends of the circuit; judging whether the circuit is a member circuit of the binding circuit, if so, unbinding the fault port of the circuit from the binding port of the binding circuit, successfully migrating the flow and recording original information; if not, draining through an ISIS protocol or a static routing protocol, successfully migrating the flow and recording original information; and restoring the configuration to the state before the flow emigration through the reverse processing of the flow emigration, wherein the flow emigration is successful. The method and the device adopt a unified strategy to realize the emigration and the emigration of the IP relay circuit bearing flow, and are beneficial to maintaining the stability of the IP network.

Description

IP relay circuit flow emigration and emigration method and device

Technical Field

The invention relates to the field of IP relay circuits, in particular to a method and a device for migrating IP relay circuit traffic out and back.

Background

An IP Relay Circuit (Relay Circuit) is a Circuit for connecting two routers in an IP network, and its core attributes include: the system comprises an A-end device, an A-end port, an A-end IP, a Z-end device, a Z-end port and a Z-end IP.

In an IP network, when one circuit fails, a backup circuit and a path may carry traffic in a corresponding direction, and generally, the network carrying capability does not affect the overall carrying of the network. But the failed circuit needs to be stripped from the IP network quickly to avoid that the traffic of the user is still directed to the circuit, resulting in loss or poor quality of the user traffic. Especially for circuits that are not completely interrupted. Therefore, when a circuit fault is found in the IP network, the circuit fault should be isolated, and then the traffic carried by the circuit fault should be migrated out, that is, the traffic is not passed through the fault circuit by methods such as configuration, so as to ensure the normal operation of the whole IP network. After the circuit fault is repaired, the flow which the circuit should bear needs to be migrated back, that is, the reverse operation of the flow migration, and the configuration is restored to the state before the flow migration.

Disclosure of Invention

In view of the above situation, the present invention provides a method and an apparatus for migrating IP relay circuit traffic, which implement migration of IP relay circuit bearer traffic by using a uniform policy, and are beneficial to maintaining the stability of an IP network.

In order to achieve the purpose, the invention adopts the following technical scheme:

in an embodiment of the present invention, a method for migrating IP relay circuit traffic is provided, where the method includes:

decomposing a circuit into two ends, and synchronously processing the two ends of the circuit;

judging whether the circuit is a member circuit of the binding circuit, if so, unbinding the fault port of the circuit from the binding port of the binding circuit, successfully migrating the flow and recording original information;

if not, draining through an ISIS protocol or a static routing protocol, successfully migrating the flow and recording original information;

and restoring the configuration to the state before the flow emigration through the reverse processing of the flow emigration, wherein the flow emigration is successful.

Further, draining via the ISIS protocol, comprises:

and checking whether the ISIS configuration exists, if so, adjusting the current metric or cost value to be ten times of the original value, and storing.

Further, draining via a static routing protocol, comprising:

and inquiring whether the static route configuration exists or not, and deleting and storing the static route if the static route configuration exists.

Further, the unified query rule of the static routing configuration is as follows:

IPv4 static routing: if the port address is/30 address, inquiring that the next hop is the opposite end address; otherwise, matching and inquiring according to the port name;

IPv6 static routing: if the port address is/127 address, inquiring that the next hop is opposite end address; otherwise, matching the query according to the port name.

Furthermore, the method is packaged into an external interface which is used as a capacity open interface for being called by an external system or used as an interface for calling flow migration and migration processing interfaces.

In an embodiment of the present invention, a device for migrating IP relay circuit traffic out and back is further provided, where the device includes:

the flow emigration module is used for decomposing a circuit into two ends and synchronously processing the two ends of the circuit; judging whether the circuit is a member circuit of the binding circuit, if so, unbinding the fault port of the circuit from the binding port of the binding circuit, successfully migrating the flow and recording original information; if not, draining through an ISIS protocol or a static routing protocol, successfully migrating the flow and recording original information;

and the flow migration module is used for restoring the configuration to the state before the flow migration through the reverse processing of the flow migration, and the flow migration is successful.

Further, draining via the ISIS protocol, comprises:

Further, draining via a static routing protocol, comprising:

In an embodiment of the present invention, a computer device is further provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the IP relay circuit traffic migratory/migratory method is implemented.

In an embodiment of the present invention, a computer-readable storage medium is further provided, where a computer program for executing the IP relay circuit traffic migration and relocation method is stored in the computer-readable storage medium.

Has the advantages that:

1. the IP relay circuit carries out the migration and the migration of the flow, and different methods are provided according to different conditions; the invention can cover common conditions, adopts a uniform strategy and is beneficial to maintaining the stability of the IP network.

2. The IP network has a plurality of routers, which relate to different manufacturers and models, and the same scheme commands are different; the invention can support mainstream equipment models and reduce the requirements on maintenance personnel.

3. The invention can be adopted to uniformly configure the standard and is beneficial to later maintenance.

4. The invention can automatically execute the operation, and is rapid, convenient and standard.

Drawings

FIG. 1 is a flow chart of the IP relay circuit traffic migration of the present invention;

FIG. 2 is a flow chart of the IP relay circuit flow migration of the present invention;

FIG. 3 is a schematic diagram of a processing interface for IP trunk circuit traffic migration and migration according to the present invention;

FIG. 4 is a schematic structural diagram of the IP relay circuit traffic migration and retrieval device according to the present invention;

FIG. 5 is a schematic diagram of the computer device structure of the present invention.

Detailed Description

The principles and spirit of the present invention will be described below with reference to several exemplary embodiments, which should be understood to be presented only to enable those skilled in the art to better understand and implement the present invention, and not to limit the scope of the present invention in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to the embodiment of the invention, the invention provides a method and a device for migrating IP relay circuit traffic, when traffic migrates, a member circuit of a binding circuit (a plurality of physical circuits are bound together through configuration to form the binding circuit, and a circuit interconnection IP is configured on the binding circuit) comprises the following steps: the circuit is unbound from the binding circuit, and then the flow can be migrated out; pure physical circuit: drainage by ISIS protocol: the value of the metric (cost) is increased to be 10 times of the original value, and the flow is guided to pass through other circuits and does not pass through the fault circuit; drainage by static routing protocol: and deleting the static route to prevent the incoming flow from passing through the fault circuit. When the flow moves back, the reverse operation is only needed. Note that the operations are performed simultaneously on both ends of the circuit, as simultaneously as possible.

The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the invention.

The IP relay circuit flow emigration and emigration method comprises the following steps:

a circuit is divided into two ends, one end is processed respectively, the operation of each end is the same, but the simultaneous operation of the two ends is ensured as much as possible.

And logging in the equipment, and performing corresponding processing according to different scenes of different equipment.

The flow migration is as shown in fig. 1, and whether the circuit is a member circuit of the binding circuit is judged, if yes, the fault port of the circuit is unbound from the binding port of the binding circuit, the flow migration is successful, and the original information is recorded;

if not, checking whether the ISIS configuration exists, if so, adjusting the current metric or cost value to ten times of the original value, storing the current metric or cost value, successfully migrating the flow and recording the original information; or inquiring whether the static route configuration exists, if so, deleting the static route, storing, and recording the original information when the flow is successfully migrated.

As shown in fig. 2, the flow relocation is performed to determine whether the circuit is a member circuit of the binding circuit, and if so, the fault recovery port of the circuit is rebundled into the binding port of the binding circuit, and the flow relocation is successful;

if not, checking whether the ISIS configuration exists, if so, restoring the current metric or cost value to the original value, storing the original value, and successfully transferring the flow back; or inquiring whether the static route configuration exists, if so, restoring the static route, storing the static route, and successfully migrating the flow.

The method is packaged into an external interface which is used as a capability open interface, an RESTFul interface is adopted for external system calling, and the following tables 1 and 2 show that:

TABLE 1 request information field Table

Name of field	Type of field	Description of the invention
			DeviceIP	String	Device loopback address
PortName	String	Port name
			WsId	String	Calling identification number

Table 2 return information field table

Name of field	Type of field	Description of the invention
			ResultCode	String	Call result 0_ success-1 _ failure
RetDetail	String	Reason for failure
			OpLog	String	Configuring an operation log

Besides providing the external capability, the method can also be directly invoked by the traffic migration and migration processing interface shown in fig. 3.

The page logic is as follows:

1. if the system has no record, the identification number indicates that the operation is the first operation, the IP of the A-end equipment, the name of the A-end port, the IP of the Z-end equipment and the name of the Z-end port are input, and only a flow emigration button is available.

2. If the system has records, the identification number indicates that the migration operation has been performed, the IP of the A-end equipment, the name of the A-end port, the IP of the Z-end equipment and the name of the Z-end port are brought in, and only the flow migration button is available.

It should be noted that although the operations of the method of the present invention have been described in the above embodiments and the accompanying drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the operations shown must be performed, to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

For a clearer explanation of the above method for rapidly generating a functional configuration based on a new metro network topology, a specific embodiment is described below, however, it should be noted that this embodiment is only for better explaining the present invention, and should not be construed as an undue limitation to the present invention.

Flow emigration general rule:

firstly, whether the circuit is a member circuit of the binding circuit or not is judged, if so, the fault port of the circuit is unbound from the binding port of the binding circuit, and the flow is moved away.

If not, checking whether the ISIS configuration exists, if so, adjusting the current metric or cost value to ten times of the original value, and migrating the incoming flow; or inquiring whether static route configuration exists or not, if so, deleting the static route, and migrating the backhaul flow.

Unified query rules for static routing configuration:

IPv 4: the port address is/30 address, find the next hop is the opposite end address (port address odd number plus one, even number minus one); otherwise, matching and inquiring according to the port name;

IPv 6: the port address is/127 address, find the next hop is the opposite end address (port address odd minus one, even plus one); otherwise, matching and inquiring according to the port name;

metric (cost) may have configuration on both IPv4 and IPv6, the same processing method.

Flow emigration example:

the method comprises the following steps:

1. judging whether to bind the members of the interface

interface GigabitEthernet2/2/0/3

set transfer-mode wan

description To SH-SH-WS-AS4812-MAN10G(S-64N2001IP)::bundle To Eth-Trunk 2

undo shutdown

eth-trunk 2 — judge as a binding port, the keywords include: eth-trunk, ip-trunk

return

Unbinding:

entering port, executing V8:

interface GigabitEthernet2/2/0/3

shutdown

commit

sleep 1s

unbio eth-trunk 2-unbinding

commit

no shutdown

commit

Other versions:

interface GigabitEthernet2/2/0/3

shutdown

sleep 1s

unbio eth-trunk 2-unbinding

no shutdown

V8 must have commit, otherwise direct confirmation, which is noted during processing, as follows.

2. Check if there is a cost configuration

-look at the current cost and adjust the cost;

entering an inlet:

interface GigabitEthernet2/1/0

viewing port:

Display this

carrier down-hold-time 60

description To JS-SQ-XDL-S-1.CN210GE(10GE9002CN2)

undo shutdown

mtu 9178

ip address 59.43.94.18255.255.255.252

isis enable 1

isis circuit-type p2p

isis circuit-level level-2

isis authentication-mode simple cipher@％@％DcrpW^@_@E38|O！ov_8@QG#v@％@％

isis cost 20 level-2

isis timer hello 3

isis small-hello

isis ldp-sync

isis timer ldp-sync hold-down 2

isis timer ldp-sync hold-max-cost 65535

pim sm

mpls

mpls ldp

mpls ldp timer keepalive-hold 30

mpls ldp timer igp-sync-delay 30

ip netstream inbound

undo dcn

control-flap

port-queue be wfq weight 1shaping shaping-percentage 80port-wred 1 outbound

port-queue af1 wfq weight 1shaping shaping-percentage 80port-wred 1 outbound

port-queue af2 wfq weight 1shaping shaping-percentage 80port-wred 1 outbound

port-queue af3 wfq weight 1shaping shaping-percentage 80port-wred 1 outbound

port-queue af4 wfq weight 1shaping shaping-percentage 80port-wred 1 outbound

port-queue ef pq shaping shaping-percentage 90 port-wred0 outbound

port-queue cs6 pq shaping shaping-percentage 10 port-wred0 outbound

port-queue cs7 pq shaping shaping-percentage 10 port-wred0 outbound

change cost value to 10 times original value:

isis cost xxx level-2

3. querying and deleting static routes

Searching for a static route according to a uniform query rule;

finding out all global static routes by using display current-configuration | in route-static, and filtering by using a program according to rules;

deleting the static route:

Undo ip route-static 115.168.128.198 255.255.255.255GigabitEthernet2/0/3115.168.160.198

juniper (Router manufacturer name)

1. Bundle judgment rule

And judging whether the interface is a bundle interface (hereinafter, shown as xe-15/0/1.0 interface bound under ae 0.0), wherein ae is Ethernet port aggregation, and as is pos interface aggregation. If the two ae or as are not displayed, the two ae or as are judged as non-aggregation binding openings)

GX-LZ-LC-D-2.163.RE0>show interfaces xe-15/0/1.0 terse

Interface Admin Link Proto Local Remote

xe-15/0/1.0up up aenet-->ae0.0

GX-LZ-LC-D-2.163.RE0>show interfaces terse so-1/0/0.0|match as

so-1/0/0.0up up soagg-->as0.0

2. Binding port

Removing the binding:

GX-LZ-LC-D-2.163.RE0>

show configuration interfaces xe-15/0/1 gigether-options|display set

set interfaces xe-15/0/1 gigether-options 802.3ad ae0

(original configuration recovery bundle) -the binding port can also be judged by ae here

-command of POS port, judged by as;

unbinding:

configure exclusive (enter configuration mode)

set interfaces xe-15/0/1disable (close port)

commit synchronize (save configuration and exit configuration mode)

sleep 10s

delete interfaces xe-15/0/1gigether-options 802.3ad ae0 (unbundle) commit synchronize (save configuration)

delete interfaces xe-15/0/1disable (open port)

commit synchronize and-quit (save configuration and exit configuration mode)

3. Physical port

View and adjust the current Metric:

BJ-BJ-JA-C-2.CN2-RE0>show configuration protocols isis|match so-0/0/1.0|display set|match metric

set protocols is interface so-0/0/1.0level 2metric1500 (original configuration recovery flow)

configure exclusive (enter configuration mode)

set protocols is interface so-0/0/1.0level 2metric15000 (traction volume)

commit synchronize and-quit (save configuration and exit configuration mode)

And querying and deleting the static route:

GX-LZ-LC-D-2.163.RE0>show configuration routing-options static|display set|match 180.140.104.26

set routing-optional static route 222.217.174.1/32next-hop 180.140.104.26 original configuration is stored;

set routing-optional static route 118.84.117.140/32next-hop 180.140.104.26 original configuration is stored;

entering a configuration mode:

configure exclusive (enter configuration mode, delete static route replace set to delete)

delete routing-options static route 222.217.174.1/32next-hop 180.140.104.26

delete routing-options static route 118.84.117.140/32next-hop 180.140.104.26

commit synchronize and-quit (save configuration and exit configuration mode)

Cisco IOX

1. Bundle member, unbinding:

interface POS0/11/1/0

description To GD-FS-SDNQ-AS64853-MAN10G(S-64N0056IPM)::To-Bundle-POS11

bundle id 11mode on-judgment is a bundle circuit

Unbinding:

interface POS0/11/1/0

shutdown

commit

sleep 1s

no bundle id 11

commit

no shutdown

commit

2. physical port (POS port, ethernet port):

check if there is Metric configuration, adjust Metric:

checking and recording ISIS interface configuration:

Sh run router isis

RP/0/RSP0/CPU0:SN-AK-LDL-S-1.CN2#show running-config router

router router-convergence

RP/0/RSP0/CPU0:SN-AK-LDL-S-1.CN2#show running-config router isis

Mon Jul 17 14:45:27.089GMT

router isis cn2

set-overload-bit on-startup wait-for-bgp

is-type level-2-only

net 86.4809.0029.0590.4300.2062.00

nsf cisco

this command is used by the show run roller is same interface POS 0/1/0/0-163;

this command is used by the show run route isis CN2 interface POS0/1/0/0- -CN 2;

modify ISIS interface metric value, original metric value 10:

router isis core

interface POS0/1/0/0

address-family ipv4 unicast

metric 115000level 2

！

address-family ipv6 unicast

metric 20000level 2

！

commit

3. checking whether static route configuration exists or not, and deleting the static route

And checking and recording static routes related to the interfaces:

show run router static

118.84.118.24/32POS0/15/1/0 183.58.10.46tag 64856description For-GDZSJ-MAN-AS65856-VNH

deleting the static route:

router static

address-family ipv4 unicast

no 118.84.118.24/32POS0/15/1/0183.58.10.46tag 64856description For-GDZSJ-MAN-AS65856-VNH

cisco IOS

1. Bundle member, unbinding:

show run interface TenGigE0/11/1/0

channel-group 11-circuit for judging bundle

Unbinding:

interface TenGigE0/11/1/0

shutdown

sleep 1s

no channel-group 11

sleep 1s

no shutdown

2. physical port (POS port, ethernet port):

check if there is Metric configuration, adjust Metric:

checking and recording ISIS interface configuration:

show run int pos0/0/0

modify ISIS interface metric value, original metric value 10:

interface POS0/0/0

isis metric 100000level-2

isis ipv6 metric 100000level-2

2. checking whether static route configuration exists or not, and deleting the static route

And checking and recording static routes related to the interfaces:

reference command:

show running-config|in ip route

finding corresponding static routes

Deleting the static route:

no ip route 192.168.0.0 255.255.255.0POS1/0/0172.16.1.113

alang

1. Judging whether the port is a conventional port or an aggregation port and a virtual next hop command

show port 1/1/1detail

Conventional port:

the corresponding port LAG/Bndl field value is-;

binding port members:

the corresponding value of the LAG/Bndl field is 1;

accordingly, whether the binding port member is judged.

2. Finding static routes

# admin display-config | match "59.43.35.198" - -port-to-port IP;

static-route 172.20.2.5/32next-hop 59.43.35.198

binding port members:

checking the corresponding relation between the port and the aggregation port lag;

command: a show lag port;

note that: viewing a port under a link aggregation port LAG;

closing the port;

command: # configure Port 1/1/4shutdown

Note that: closing the port;

Sleep 1s

removing the failed port from the link aggregation port LAG;

command: configure lag 61no port 1/1/4;

note that: deleting the failed port from the link aggregation port LAG;

intra-network interconnection relay conventional port:

checking whether the Metric configuration exists, and adjusting the Metric;

interface plus so-, ge-rule;

the POS port judges the type of a board card where the port is located, the type of the board card comprises '-oc', the number of the board card is the POS board card, and so is added; the board card type comprises "gb-", the number following is the Ethernet board card, add ge-; the board card type comprises 10gb- ", the number following is 10G Ethernet board card, add xe-;

adjusting the Metric value of the isis protocol corresponding to the interface;

command: # configuration router is interface-5/1/1 level 2metric 30000;

note that: the Metric value of the isis protocol corresponding to the interface is multiplied by 10;

3. with statically routed conventional ports

Deleting the relevant static route:

command: # configure Router no static-route 172.20.2.5/32next-hop x.x.x.x.

Note that: deleting static routing commands

#configure router no static-route 172.20.2.5/32next-hop59.43.35.198。

Flow relocation example:

Huawei

1. binding mouth

Binding port migration flow:

entering an port and recovering the original binding configuration;

V8：

interface GigabitEthernet5/0/3

eth-trunk 2- -binding instance, restore original configuration

commit

And others:

interface GigabitEthernet5/0/3

eth-trunk 2- -binding instance, restore original configuration

2. Physical port

(1) And (3) static route recovery:

adding a static route:

ip route-static 115.168.128.198 255.255.255.255GigabitEthernet2/0/3.2000115.168.160.198

(2) cost migration back flow:

entering an inlet:

interface GigabitEthernet2/1/0

and (3) recovering the configuration:

isis cost 20level-2

Juniper

binding the opening:

1. and (3) binding recovery:

configure exclusive (enter configuration mode)

set interfaces xe-15/0/1disable (close port)

set interfaces xe-15/0/1gigether-options 802.3ad ae0 (recovery bundles)

commit synthronize (save configuration)

delete interfaces xe-15/0/1disable (open port)

commit synchronize and-quit (save configuration and exit configuration mode)

Physical port:

2. recovering metric configuration

configure exclusive (enter configuration mode)

set protocols is interface so-0/0/1.0level 2metric1500 (recovery configuration)

commit synchronize and-quit (save configuration and exit configuration mode)

3. Static route restoration

And (3) recovering the configuration:

configure exclusive (enter configuration mode, keep the original configuration executed once);

commit synchronize and-quit (save configuration and exit configuration mode);

the IPv6 static routing principle is the same as above:

GX-LZ-LC-D-2.163.RE0>show configuration routing-options|display set|match 240e:9:3001:f002::3

set routing-options rib inet6.0 static route240e:9:3000::001/128next-hop 240e:9:3001:f002::3

set routing-options rib inet6.0 static route240e:0:0:0:d:92:3:1001/128next-hop 240e:9:3001:f002::3

cisco IOX

1. Binding member

Entering a port, and recovering the original bundle configuration:

interface POS0/11/1/0

bundle id 11mode on- -get the original configuration, have a relationship with the other party's negotiation

commit

2. Intra-network interconnection port

Recovery ISIS metric value:

router isis core--163

router isis cn2--CN2

interface POS0/1/0/0

address-family ipv4 unicast

metric 11500 level 2

！

address-family ipv6 unicast

metric 2000level 2

3. static route restoration

router static

address-family ipv4 unicast

118.84.118.24/32 POS 0/15/1/0183.58.10.46 tag 64856description For-GDZSJ-MAN-AS65856-VNH- -restore the original configuration.

Cisco IOS

1. Binding member

Entering a port, and recovering the original bundle configuration:

Interface TenGigE0/11/1/0

channel-group 11

2. intra-network interconnection port

Recovery ISIS metric value:

interface POS0/0/0

isis metric 10000 level-2

isis ipv6 metric 10000 level-2

3. static route restoration

ip route 192.168.0.0255.255.255.0 POS 1/0/0172.16.1.113- -restore the original configuration.

Alang

1. Adding normal port tested by loop-making test from link aggregation port LAG

Command: configure lag 61 port 1/1/4

Note that: adding looped port ports from a link aggregation port LAG;

2. recovering Metric value of isis protocol corresponding to interface

Command: # configure route is interface-5/1/1 level 2metric 3000- -original metric value;

3. restoring static routing

Command: # configure Router static-route 172.20.2.5/32next-hop x.x.x.x.

Note that: configuring a static routing command;

#configure router static-route 172.20.2.5/32 next-hop59.43.35.198

based on the same invention concept, the invention also provides an IP relay circuit flow emigration and emigration device. The implementation of the device can be referred to the implementation of the method, and repeated details are not repeated. The term "module," as used below, may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 4 is a schematic structural diagram of the IP relay circuit traffic migration and retrieval device of the present invention. As shown in fig. 4, the apparatus includes:

the flow emigration module 101 is used for decomposing a circuit into two ends and synchronously processing the two ends of the circuit; judging whether the circuit is a member circuit of the binding circuit, if so, unbinding the fault port of the circuit from the binding port of the binding circuit, successfully migrating the flow and recording original information; if not, checking whether the ISIS configuration exists, if so, adjusting the current metric or cost value to ten times of the original value, storing the current metric or cost value, successfully migrating the flow and recording the original information; or inquiring whether the static route configuration exists, if so, deleting the static route, storing, successfully migrating the flow and recording the original information;

the unified query rule for static routing configuration is as follows:

And the flow migration back module 102 is configured to restore the configuration to a state before the flow migration through a reverse process of the flow migration, so that the flow migration back is successful.

It should be noted that although several modules of IP trunk circuit traffic migration back device are mentioned in the above detailed description, such partitioning is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the modules described above may be embodied in one module according to embodiments of the invention. Conversely, the features and functions of one module described above may be further divided into embodiments by a plurality of modules.

Based on the aforementioned inventive concept, as shown in fig. 5, the present invention further provides a computer device 200, which includes a memory 210, a processor 220, and a computer program 230 stored on the memory 210 and operable on the processor 220, wherein the processor 220 implements the aforementioned IP relay circuit traffic migration method when executing the computer program 230.

Based on the foregoing inventive concept, the present invention further provides a computer-readable storage medium storing a computer program for executing the foregoing IP relay circuit traffic migration and relocation method.

The IP relay circuit flow emigration and emigration method and the device can cover common conditions, adopt a uniform strategy and are beneficial to maintaining the stability of an IP network; the device model of the mainstream can be supported, and the requirement on maintenance personnel is reduced; the invention can be adopted to uniformly configure the standard, which is beneficial to the later maintenance; the invention can automatically execute the operation, and is rapid, convenient and standard.

While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

The limitation of the protection scope of the present invention is understood by those skilled in the art, and various modifications or changes which can be made by those skilled in the art without inventive efforts based on the technical solution of the present invention are still within the protection scope of the present invention.

Claims

1. A method for migrating IP relay circuit traffic is characterized by comprising the following steps:

2. The IP trunk circuit traffic emigration and emigration method according to claim 1, wherein the routing by ISIS protocol comprises:

3. The IP relay circuit traffic migration and back-migration method according to claim 1, wherein the routing is performed by a static routing protocol, and comprises:

4. The IP relay circuit traffic migration and back-migration method according to claim 3, wherein the unified query rule of the static routing configuration is as follows:

5. The IP relay circuit traffic migration and relocation method according to claim 1, wherein the method is encapsulated into an external interface as a capability open interface for external system call, or as an interface for calling a traffic migration and relocation processing interface.

6. An IP relay circuit traffic migration and migration device, comprising:

7. The IP trunk circuit traffic migration and back-migration device according to claim 6, wherein the drainage via ISIS protocol comprises:

8. The IP trunk circuit traffic migration and back-out device according to claim 6, wherein the routing is performed by a static routing protocol, comprising:

9. The IP relay circuit traffic migration and back-migration device according to claim 8, wherein the unified query rule for the static routing configuration is as follows:

10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-5 when executing the computer program.

11. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1-5.