CN1681254A - Maintaining method of Ethernet link state - Google Patents
Maintaining method of Ethernet link state Download PDFInfo
- Publication number
- CN1681254A CN1681254A CN 200410034427 CN200410034427A CN1681254A CN 1681254 A CN1681254 A CN 1681254A CN 200410034427 CN200410034427 CN 200410034427 CN 200410034427 A CN200410034427 A CN 200410034427A CN 1681254 A CN1681254 A CN 1681254A
- Authority
- CN
- China
- Prior art keywords
- link
- message
- terminal equipment
- network
- address
- 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
Images
Landscapes
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The method includes following steps: when two layer 3 equipments pass through Ethernet link connection, one of the layer 3 equipments periodically send link state detection message; after opposite terminal equipment receives the message, it will make response; when the present terminal equipment doesn't receive the response from opposite terminal equipment, this link is considered have a failure, meantime disenable the router whose next-hop address is the address of opposite terminal equipment. The invention can automatically switch the failure link to spare link, and when the network failure recovers, it can switch back.
Description
Technical field
The present invention relates to network technology, particularly the detection of network link failure and processing method.
Background technology
When connecting by the Ethernet net between router and the router or between any two three-layer network appliances, can directly connect, perhaps connect by one or more Layer 2 switch by ethernet line.Be illustrated in fig. 1 shown below; direct-connected by ethernet line; because line quality; perhaps contact badly, such phenomenon takes place through regular meeting, can operate as normal from RTA to RTB; but from RTB to RTA, but break down; RTA also can continue information is sent to RTB like this, but RTB can not return information, thereby causes network failure.When connecting by Layer 2 switch, problem is just more serious.During to the connection fault between RTB and the Layer 2 switch, RTA does not also know, causes network failure equally.After these faults took place, network can not switch on the reserve link automatically because it and do not known own fault.In order to address this is that, can only solve problem by configuration dynamic routing protocol on RTA and RTB at present.Because the agreement maintenance packet between the dynamic routing protocol all needs the other side to confirm, so, no matter be to break down in any point between RTA and the RTB, can detect by dynamic routing protocol and to break down, thereby network is switched on the backup network, thereby guarantee that whole network continues operate as normal.Do like this and bring some new problems:
1, the requirement to the network equipment increases.A lot of network equipments are not support dynamic routing protocol as three-tier switch etc.
2, increase the load of the network equipment.Start dynamic routing protocol and use static routing to compare, largely increase consumption equipment CPU and internal memory.
3, increase the complexity of network operation.At the edge of network, as the connection between three-tier switch and the router, generally all adopt static routing protocol, but, must all start dynamic routing protocol in order to guarantee the reliability of network, increased the complexity of network greatly.Especially in the MPLS network, what network will become is unusual complicated.
Summary of the invention
Based on above analysis, when two three-layer equipments connect by Ethernet link, need a kind of simple technology, detect Link State.
The present invention proposes a simple technique scheme and solve this problem, when two three-layer equipments connect by Ethernet link, one of them three-layer network appliance regularly sends the Link State detection messages, and opposite equip. is replied by opposite equip. after receiving this message.When local terminal equipment is not received replying of opposite equip. in the regular hour, just think this link fault, it is invalid with next hop address to be that the route of opposite equip. address is changed to simultaneously.
The present invention makes the network equipment can find the ethernet link fault by Ethernet link state-detection mechanism is provided, by with relevant static routing mating reaction, network is switched on the reserve link from faulty link automatically.Behind network disaster recovery, can switch back again.By using this technology, the network equipment is as long as support static routing just can realize the ethernet link backup, and is low for equipment requirements, and needs the extra resource of the equipment that takies hardly, greatly facilitates the construction and the maintenance of edge network.
Description of drawings
Fig. 1 is a network equipment networking schematic diagram;
Fig. 2 totally implements block diagram representation for the present invention;
Fig. 3 is a testing process schematic diagram of the present invention;
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with the drawings and specific embodiments.
As Fig. 1, be enforcement block diagram of the present invention, implement the present invention and mainly contain following steps;
Step 10: determine the next hop address that local terminal equipment will detect by configuration;
Step 11: check whether disposed the Static ARP of this next hop address, if there is not jump procedure 17;
Step 12: timed sending ARP request (can pass through broadcasting or clean culture);
Step 13: do not receive the back message using of arp request whether continuous three times, if, jump procedure 19;
Step 14: received response message, whether former interface link state is down, and whether relevant route is invalid, if do not receive jump procedure 12;
Step 15: Link State is set to effectively, and route is set to effectively
Step 16: after the route of main usefulness is effective, replace original route stand-by to have an effect automatically, jump procedure 12;
Step 17:, set up the dynamic ARP entry of this next jumping by the Dynamic ARP request
Step 18: whether set up this ARP list item, if do not set up jump procedure 12
Step 19: judge that then the opposite end is obstructed, the local terminal link is set to the down state, and it is invalid that the route entry of will being correlated with simultaneously is changed to
Step 20: after top route entry was invalid, the route of backup was had an effect automatically
As Fig. 2, get access to the MAC Address of opposite end three-layer network appliance when equipment after (no matter be or pass through static configuration) by the ARP dynamic learning, regular transmission probe messages is to opposite equip., for avoiding causing network burden, probe messages sends with the form of clean culture, the target MAC (Media Access Control) address of this message is the MAC Address of opposite end three-layer network appliance.The regular time is configurable, in order to find network failure as early as possible, reduces the unnecessary load of network simultaneously as far as possible, and recommended value is 1 second to 10 seconds.The content of probe messages can be various, can be special protocol massages, can use the prior protocols message, as clean culture ARP request message (target MAC (Media Access Control) address of ARP request message is known MAC Address), perhaps ICMP request message.Probe messages receives that with after sending together request message replying of opposite end is a detection process of finishing.
Behind the ARP list item of the IP address correspondence that the opposite end that disposes has been arranged in the ARP table, just the ARP that can be correlated with has surveyed.The form of probe messages is as follows:
Can use the ARP message request of broadcasting, message format is as follows:
Sender′s?MAC?Address | Sender′s?IP?Address | Target?MAC?Address | Target?IP?Address |
00-00-0c-94-36-aa (local terminal eth MAC Address) | (172.16.10.100 local terminal IP address) | 00-00-00-00-00-00 (broadcast address) | 172.16.20 200 (peer IP address) |
Can use the ARP message request of clean culture, message format is as follows:
Sender′s?MAC?Address | Sender′s?IP?Address | Target?MAC?Address | Target?IP?Address |
00-00-0c-94-36-aa (local terminal eth MAC Address) | (172.16.10.100 local terminal IP address) | 00-00-0e-95-45-55 (the mac address of arriving by static configuration or dynamic learning) | (172.16.20.200 peer IP address) |
If reciever does not respond, if response times does not surpass three times, then think and the other side down continue to send then, if response is arranged, then show up.
After continuous several times (as 3 times) is not received the response message of opposite end, just think that network breaks down, in this equipment, next jumping is the route of three-layer network appliance address, opposite end, all is changed to failure state.Like this, if when in the network backup link being arranged, route stand-by will come into force, thereby network is switched on the backup link, keeps whole network operate as normal.
As Fig. 1, RTA, RTB, RTC connect by ethernet link, the middle LanSwith that passes through two layers.Connect internal network under the RTA, the internal network address network segment is 50.0.0.0/24.RTA is first outlet of in-house network to RTB, and RTA is second outlet of enterprise to RTC.Under the normal condition, two default routes are arranged on RTA, divide to be clipped to RTB and RTC, will be higher than RTC's to the priority of the route of RTB.Like this, all uplink messages all are sent to RTB, deliver to external network then.Though RTB and RTC have issued the network segment of 50.0.0.0 to external network, the priority of RTB issue will be higher than RTC, so downlink message all is sent to RTB, delivers to internal network by RTA.
When RTB after the link occurs fault of LanSwitch, according to present processing method, RTA does not also know this link occurs fault, continues message is sent to 100.0.0.2, final LanSwitch is all packet loss, thereby causes network failure.
Adopt technical scheme of the present invention, specifying 100.0.0.2 and 100.0.0.3 on RTA is the three-layer network appliance address, and all specifying 100.0.0.1 on RTB and RTC is the three-layer network appliance address.Like this, all regularly whether (every 3 seconds) transmission probe messages is normal with the detecting link state for RTA, RTB and RTC.With RTA is example, can send destination address is 100.0.0.2, target MAC (Media Access Control) address is that the ARP request message of B.B.B (is determined because of target MAC (Media Access Control) address, so be unicast message), LanSwitch delivers to this message on the RTB, RTB receives after this ARP request message, can answer an arp reply message, returns to RTA.After the link occurs fault between RTB and the Lanswtich, the probe messages of RTA also just can't send to RTB, and natural RTA just can not receive the response message of RTB yet, continuous do not have response message three times after, then think this link failure.Search that next hop address is the route of 100.0.0.2 in the routing table, and this route was lost efficacy.Like this, article one default route that RTA comes into force in Central Plains, 0.0.0.0 0.0.0.0 100.0.0.2/24 10 had just lost efficacy, the second default route, 0.0.0.0 0.0.0.0 100.0.0.3/24 20 has just come into force.Like this, uplink message is just delivered to RTC by RTA.For RTB, the continuous too response message of not receiving RTA for three times, the route that can be 100.0.0.1/24 with next hop address forbids falling, being about to route 50.0.0.0255.255.255.0 100.0.0.1/24 10 forbids falling, like this, external network just can only be received from the route of the 50.0.0.0 network segment of RTC issue.So all downlink messages just are sent to RTC, deliver to internal network by RTA.Like this, realized that RTA from fault is to the backup link of link switchover to RTA to RTC of RTB.
After RTA was normal to the link-recovery of RTB, originally forbidden route can come into force again, and network returns to again and uses the link of RTA to RTB.
Claims (5)
1, a kind of ethernet link fault detect way, it is characterized by, local terminal Equipment Inspection configuration, local terminal equipment sends detection messages to detected link opposite equip., opposite equip. is received detection messages, reply response message, whether local terminal equipment basis receives response message is judged the state of link, and makes corresponding troubleshooting.
2, ethernet link fault detect way according to claim 1, it is characterized in that, the inspection of described local terminal equipment disposition comprises, if be checked through ARP is not quiesce protocol, then set up the dynamic address resolution agreement ARP list item of next jumping, if do not set up dynamic address resolution agreement ARP list item, then be switched to route stand-by.
3, ethernet link detection method according to claim 1 is characterized in that, described transmission message can be common dynamic address resolution agreement ARP request message clean culture ARP request message, or Internet Control Message Protocol ICMP request message.
4, ethernet link detection method according to claim 1 is characterized in that, described transmission message is the cycle transmission with 1 second to 10 seconds, does not receive corresponding message if send 3 messages continuously, then judges this link failure.
5, ethernet link detection method according to claim 1 is characterized in that, described troubleshooting comprises that the local terminal link is set to the down state, and it is invalid that the route of being correlated with is set to, and be transformed on the route stand-by.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB200410034427XA CN100499485C (en) | 2004-04-08 | 2004-04-08 | Maintaining method of Ethernet link state |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB200410034427XA CN100499485C (en) | 2004-04-08 | 2004-04-08 | Maintaining method of Ethernet link state |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1681254A true CN1681254A (en) | 2005-10-12 |
CN100499485C CN100499485C (en) | 2009-06-10 |
Family
ID=35067691
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB200410034427XA Expired - Fee Related CN100499485C (en) | 2004-04-08 | 2004-04-08 | Maintaining method of Ethernet link state |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100499485C (en) |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007045156A1 (en) * | 2005-10-17 | 2007-04-26 | Huawei Technologies Co., Ltd. | Method and system for controlling the continuity check of the ethernat links and the maintenance terminal thereof |
WO2008028385A1 (en) * | 2006-08-30 | 2008-03-13 | Huawei Technologies Co., Ltd. | Method and apparatus of ethernet device link fault detection |
CN100433660C (en) * | 2006-09-30 | 2008-11-12 | 杭州华三通信技术有限公司 | Method and equipment for realizing fast detection |
CN100446476C (en) * | 2006-08-02 | 2008-12-24 | 华为技术有限公司 | Method and apparatus for communicating network trouble dtecting result |
CN100446470C (en) * | 2006-01-19 | 2008-12-24 | 华为技术有限公司 | Method for realizing operation and maintenance of wind-band ethernet network |
CN100456697C (en) * | 2006-04-20 | 2009-01-28 | 华为技术有限公司 | Method and system for configuring two-way converting inspection automatically |
WO2009070943A1 (en) * | 2007-11-26 | 2009-06-11 | Supcon Group Co., Ltd. | Fault processing method, system and exchanging device based on industry ethernet network |
WO2009092257A1 (en) * | 2007-12-29 | 2009-07-30 | Huawei Technologies Co., Ltd. | Fault detection method and device for provider backbone transport network |
CN101155433B (en) * | 2006-09-30 | 2010-04-21 | 华为技术有限公司 | Service protection method and routing device |
CN101052037B (en) * | 2006-05-10 | 2010-08-18 | 华为技术有限公司 | Conversation management control method of IP bearing net |
CN101304346B (en) * | 2008-06-27 | 2010-12-15 | 北京星网锐捷网络技术有限公司 | Method and apparatus for monitoring link |
CN101159627B (en) * | 2007-11-07 | 2010-12-22 | 杭州华三通信技术有限公司 | Link state detecting method and apparatus |
CN102035695A (en) * | 2010-12-20 | 2011-04-27 | 中兴通讯股份有限公司 | Bidirectional forwarding detection method and device |
CN101340320B (en) * | 2008-08-27 | 2011-08-17 | 北京星网锐捷网络技术有限公司 | Link detection method, apparatus and system |
CN102624584A (en) * | 2012-03-01 | 2012-08-01 | 中兴通讯股份有限公司 | Link detection method and link detection device |
CN101772194B (en) * | 2008-12-26 | 2013-02-27 | 中兴通讯股份有限公司 | General packet radio service tunnel user plane path keep-alive method and system |
CN101075970B (en) * | 2007-07-19 | 2013-03-20 | 杭州华三通信技术有限公司 | Method and apparatus for selecting router |
CN103117930A (en) * | 2013-02-07 | 2013-05-22 | 华为技术有限公司 | Method and device for detecting static route configuration |
CN103457755A (en) * | 2012-06-05 | 2013-12-18 | 深圳市华力特电气股份有限公司 | IEC 61850 system communication fault detection method and system |
CN103532840A (en) * | 2013-10-11 | 2014-01-22 | 杭州华三通信技术有限公司 | Link switching method and link switching device |
CN105323080A (en) * | 2014-06-09 | 2016-02-10 | 中兴通讯股份有限公司 | Method, apparatus and system for backup of link and power supply |
CN107453849A (en) * | 2017-07-31 | 2017-12-08 | 中国南方电网有限责任公司电网技术研究中心 | Mutual-backup linkage method and system for wired link and wireless link of power distribution communication network and air-ground mutual-backup integrated device |
CN108471369A (en) * | 2018-06-27 | 2018-08-31 | 深圳创维数字技术有限公司 | A kind of network dialing method, device and storage medium |
CN110417761A (en) * | 2019-07-17 | 2019-11-05 | 上海东土远景工业科技有限公司 | Communication means and device based on dual-computer redundancy |
CN110838994A (en) * | 2019-11-14 | 2020-02-25 | 天津津航计算技术研究所 | Redundant Ethernet link state monitoring system based on broadcast protocol |
CN112511665A (en) * | 2020-12-14 | 2021-03-16 | 北京特立信电子技术股份有限公司 | Route detection method, route switching method, device, terminal and storage medium |
CN113133036A (en) * | 2019-12-31 | 2021-07-16 | 北京奇虎科技有限公司 | Interference detection method and device and router |
CN114500632A (en) * | 2022-01-24 | 2022-05-13 | 重庆奥普泰通信技术有限公司 | Communication method and communication device |
CN114826888A (en) * | 2022-04-27 | 2022-07-29 | 济南浪潮数据技术有限公司 | Message sending method, device, equipment and storage medium |
-
2004
- 2004-04-08 CN CNB200410034427XA patent/CN100499485C/en not_active Expired - Fee Related
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007045156A1 (en) * | 2005-10-17 | 2007-04-26 | Huawei Technologies Co., Ltd. | Method and system for controlling the continuity check of the ethernat links and the maintenance terminal thereof |
CN100446470C (en) * | 2006-01-19 | 2008-12-24 | 华为技术有限公司 | Method for realizing operation and maintenance of wind-band ethernet network |
CN100456697C (en) * | 2006-04-20 | 2009-01-28 | 华为技术有限公司 | Method and system for configuring two-way converting inspection automatically |
CN101052037B (en) * | 2006-05-10 | 2010-08-18 | 华为技术有限公司 | Conversation management control method of IP bearing net |
CN100446476C (en) * | 2006-08-02 | 2008-12-24 | 华为技术有限公司 | Method and apparatus for communicating network trouble dtecting result |
WO2008028385A1 (en) * | 2006-08-30 | 2008-03-13 | Huawei Technologies Co., Ltd. | Method and apparatus of ethernet device link fault detection |
CN100433660C (en) * | 2006-09-30 | 2008-11-12 | 杭州华三通信技术有限公司 | Method and equipment for realizing fast detection |
CN101155433B (en) * | 2006-09-30 | 2010-04-21 | 华为技术有限公司 | Service protection method and routing device |
CN101075970B (en) * | 2007-07-19 | 2013-03-20 | 杭州华三通信技术有限公司 | Method and apparatus for selecting router |
CN101159627B (en) * | 2007-11-07 | 2010-12-22 | 杭州华三通信技术有限公司 | Link state detecting method and apparatus |
US8488475B2 (en) | 2007-11-26 | 2013-07-16 | Supcon Group Co., Ltd. | Fault processing method, system and exchanging device based on industry ethernet network |
WO2009070943A1 (en) * | 2007-11-26 | 2009-06-11 | Supcon Group Co., Ltd. | Fault processing method, system and exchanging device based on industry ethernet network |
WO2009092257A1 (en) * | 2007-12-29 | 2009-07-30 | Huawei Technologies Co., Ltd. | Fault detection method and device for provider backbone transport network |
CN101304346B (en) * | 2008-06-27 | 2010-12-15 | 北京星网锐捷网络技术有限公司 | Method and apparatus for monitoring link |
CN101340320B (en) * | 2008-08-27 | 2011-08-17 | 北京星网锐捷网络技术有限公司 | Link detection method, apparatus and system |
CN101772194B (en) * | 2008-12-26 | 2013-02-27 | 中兴通讯股份有限公司 | General packet radio service tunnel user plane path keep-alive method and system |
CN102035695A (en) * | 2010-12-20 | 2011-04-27 | 中兴通讯股份有限公司 | Bidirectional forwarding detection method and device |
CN102624584A (en) * | 2012-03-01 | 2012-08-01 | 中兴通讯股份有限公司 | Link detection method and link detection device |
CN102624584B (en) * | 2012-03-01 | 2018-02-23 | 中兴通讯股份有限公司 | Chain circuit detecting method and device |
CN103457755B (en) * | 2012-06-05 | 2016-08-31 | 深圳市华力特电气股份有限公司 | A kind of method and system of IEC 61850 system communication failure detection |
CN103457755A (en) * | 2012-06-05 | 2013-12-18 | 深圳市华力特电气股份有限公司 | IEC 61850 system communication fault detection method and system |
CN103117930A (en) * | 2013-02-07 | 2013-05-22 | 华为技术有限公司 | Method and device for detecting static route configuration |
CN103117930B (en) * | 2013-02-07 | 2016-01-27 | 华为技术有限公司 | The detection method of static routing configuration and device |
CN103532840B (en) * | 2013-10-11 | 2017-01-25 | 杭州华三通信技术有限公司 | Link switching method and link switching device |
CN103532840A (en) * | 2013-10-11 | 2014-01-22 | 杭州华三通信技术有限公司 | Link switching method and link switching device |
CN105323080B (en) * | 2014-06-09 | 2019-08-16 | 中兴通讯股份有限公司 | A kind of link backup, power supply backup method, apparatus and system |
CN105323080A (en) * | 2014-06-09 | 2016-02-10 | 中兴通讯股份有限公司 | Method, apparatus and system for backup of link and power supply |
CN107453849A (en) * | 2017-07-31 | 2017-12-08 | 中国南方电网有限责任公司电网技术研究中心 | Mutual-backup linkage method and system for wired link and wireless link of power distribution communication network and air-ground mutual-backup integrated device |
CN108471369A (en) * | 2018-06-27 | 2018-08-31 | 深圳创维数字技术有限公司 | A kind of network dialing method, device and storage medium |
CN108471369B (en) * | 2018-06-27 | 2021-01-15 | 深圳创维数字技术有限公司 | Network dialing method, device and storage medium |
CN110417761B (en) * | 2019-07-17 | 2021-12-17 | 上海东土远景工业科技有限公司 | Communication method and device based on dual-computer redundancy |
CN110417761A (en) * | 2019-07-17 | 2019-11-05 | 上海东土远景工业科技有限公司 | Communication means and device based on dual-computer redundancy |
CN110838994A (en) * | 2019-11-14 | 2020-02-25 | 天津津航计算技术研究所 | Redundant Ethernet link state monitoring system based on broadcast protocol |
CN110838994B (en) * | 2019-11-14 | 2021-09-28 | 天津津航计算技术研究所 | Link state monitoring method of redundant Ethernet based on broadcast protocol |
CN113133036A (en) * | 2019-12-31 | 2021-07-16 | 北京奇虎科技有限公司 | Interference detection method and device and router |
CN112511665A (en) * | 2020-12-14 | 2021-03-16 | 北京特立信电子技术股份有限公司 | Route detection method, route switching method, device, terminal and storage medium |
CN114500632A (en) * | 2022-01-24 | 2022-05-13 | 重庆奥普泰通信技术有限公司 | Communication method and communication device |
CN114826888A (en) * | 2022-04-27 | 2022-07-29 | 济南浪潮数据技术有限公司 | Message sending method, device, equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN100499485C (en) | 2009-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN100499485C (en) | Maintaining method of Ethernet link state | |
US6581166B1 (en) | Network fault detection and recovery | |
CN102035676B (en) | ARP (Address Resolution Protocol) interaction based method and equipment for detecting and recovering link fault | |
CN1925496B (en) | System and method for load sharing of network layer with multiple network interface cards terminal equipment | |
US7522598B2 (en) | System and method of protecting an IGMP proxy | |
CN101729426B (en) | Method and system for quickly switching between master device and standby device of virtual router redundancy protocol (VRRP) | |
JP2006101471A (en) | Multicast redundant path router, multicast redundant method | |
EP2698948A1 (en) | Method and device for determining failure elimination based on oam protocol | |
CN101420381B (en) | Method and apparatus for enhancing forwarding reliability in VRRP load balance | |
CN108833149B (en) | Method and system for monitoring network availability and self-healing of express delivery cabinet | |
CN110650078B (en) | Coordinating pseudowire connection features and multi-homed provider edge device capabilities | |
CN1992707A (en) | Fast restoration method of multicast service and network apparatus | |
CN1889579A (en) | Method and apparatus for raising route information protocol route convergence rate | |
CN103607317A (en) | Two-layer loop detection method, two-layer loop detection device and communication system | |
CN101174975A (en) | Periodic line fault location method and system in Ethernet | |
CN110611590A (en) | Method and system for internet of things gateway communication backup | |
US7599368B2 (en) | Communication system | |
CN111030926B (en) | Method and device for improving high availability of network | |
CN101330496A (en) | Method and apparatus for detecting Ethernet multicast loop | |
CN110661705B (en) | Hardware network switching engine and network fault processing system and method | |
CN101741740B (en) | Method, system and equipment for balancing loads | |
CN101841424A (en) | EMS network management system and method based on SOCKS proxy connection | |
CN102064956B (en) | Method for regulating aging time, system and modulator-demodulator | |
JP4757719B2 (en) | Network system, IP telephone terminal, and network device switching method used therefor | |
CN108270593A (en) | A kind of two-node cluster hot backup method and system |
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 | ||
CF01 | Termination of patent right due to non-payment of annual fee | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090610 Termination date: 20180408 |