CA2493525A1 - Method and apparatus for outage measurement - Google Patents
Method and apparatus for outage measurement Download PDFInfo
- Publication number
- CA2493525A1 CA2493525A1 CA002493525A CA2493525A CA2493525A1 CA 2493525 A1 CA2493525 A1 CA 2493525A1 CA 002493525 A CA002493525 A CA 002493525A CA 2493525 A CA2493525 A CA 2493525A CA 2493525 A1 CA2493525 A1 CA 2493525A1
- Authority
- CA
- Canada
- Prior art keywords
- outage
- processing device
- outages
- network processing
- network
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/064—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
Abstract
An Outage Measurement System (OMS) monitors and measures outage data at a network processing device. The outage data can be stored in the device and transferred to a Network Management System (NMS) or other correlation tool for deriving outage information. The OMS automates the outage measurement process and is more accurate, efficient and cost effective than pervious outage measurement systems.
Claims (69)
1. A method for detecting outages, comprising:
automatically measuring outages using an outage measurement system located locally in a network processing device.
automatically measuring outages using an outage measurement system located locally in a network processing device.
2. A method according to claim 1 including measuring outages for devices directly attached to the network processing device using the outage measurement system.
3. A method according to claim 1 including measuring outages for local objects in the network processing device.
4. A method according to claim 1 including storing outage data locally in the network processing device.
5. A method according to claim 4 including using a persistent memory device for storing the outage data.
6. A method according to claim 4 including storing the outage data in a Management Information Base (MIB).
7. A method according to claim 6 including using a Simple Network Management Protocol (SNMP) to transfer the outage data in the MIB.
8. A method according to claim 1 including transferring the outage data to a network management system or upper level tool for correlating.
9. A method according to claim 1 including polling for layer-2 outages with the outage measurement system.
10. A method according to claim 1 including polling for layer-3 outages with the outage measurement system.
11. A method according to claim 1 including automatically discovering devices connect to the local network processing device and automatically polling for outages associated with the discovered devices.
12. A method according to claim 1 including:
receiving configuration data from a network management system at the network processing device; and automatically monitoring for outages with the outage measurement system according to the received configuration data.
receiving configuration data from a network management system at the network processing device; and automatically monitoring for outages with the outage measurement system according to the received configuration data.
13. A method according to claim 12 including retaining the configuration data in a configuration table located in the network processing device.
14. A method according to claim 1 including filtering the local outage data with the outage measurement system.
15. A method for measuring outages in a network, comprising:
identifying single point of failure devices in the network;
selectively locating outage measurement systems in the identified single point of failure devices; and automatically testing for outages locally in the selected single point of failure devices using the outage measurement systems.
identifying single point of failure devices in the network;
selectively locating outage measurement systems in the identified single point of failure devices; and automatically testing for outages locally in the selected single point of failure devices using the outage measurement systems.
16. A method according to claim 15 including:
storing outage data for the outages in the identified devices;
correlating the outage data with one or more correlation systems; and identifying outage statistics according to the correlated outage data.
storing outage data for the outages in the identified devices;
correlating the outage data with one or more correlation systems; and identifying outage statistics according to the correlated outage data.
17. A method according to claim 16 wherein one or more of the correlation systems are located on a network management system remote from the identified devices.
18. A method according to claim 15 including polling for layer-2 outages using the outage measurement systems and polling for layer-3 outages according to results of the layer-2 polling.
19. A method according to claim 18 including using a combination of the polled layer-2 and layer-3 outages to distinguish between local outages local to the identified devices and remote outages associated with links or devices connected to the identified devices.
20. A method for identifying outages, comprising:
monitoring traffic statistics locally at a network processing device for objects associated with the network processing device; and using the traffic statistics to identify outages for the objects.
monitoring traffic statistics locally at a network processing device for objects associated with the network processing device; and using the traffic statistics to identify outages for the objects.
21. A method according to claim 20 including monitoring link status of objects associated with the network processing device and detecting outages according to the monitored traffic statistics and monitored link status.
22. A method according to claim 21 including;
pinging remote devices connected to the network processing device;
monitoring the results of the pinging; and detecting outages according to the monitored traffic statistics, monitored link status and monitored pinging.
pinging remote devices connected to the network processing device;
monitoring the results of the pinging; and detecting outages according to the monitored traffic statistics, monitored link status and monitored pinging.
23. A method according to claim 20 including monitoring utilization of a processor in the network processing device and using the monitored utilization to identifying Denial Of Service (DOS) conditions in the network processing device.
24. A method for identifying outages, comprising:
polling for local outages of local objects at the network processing device;
polling for remote outages of remote objects connected to the network processing device; and comparing the local outages with the remote outages to distinguish between outages caused by the local objects and outages caused by the remote objects.
polling for local outages of local objects at the network processing device;
polling for remote outages of remote objects connected to the network processing device; and comparing the local outages with the remote outages to distinguish between outages caused by the local objects and outages caused by the remote objects.
25. A method according to claim 24 including polling for the remote outages by pinging the remote objects with test packets.
26. A method according to claim 24 including:
deriving an Accumulated Outage Time (AOT) for the local objects;
deriving an Accumulated Outage Time (AOT) for the remote objects; and distinguishing local object outages from remote object outages by comparing the AOT for the local objects with the AOT for the remote objects.
deriving an Accumulated Outage Time (AOT) for the local objects;
deriving an Accumulated Outage Time (AOT) for the remote objects; and distinguishing local object outages from remote object outages by comparing the AOT for the local objects with the AOT for the remote objects.
27. A method according to claim 24 wherein the local objects include local physical and logical interfaces, a local line card, or a local router processor.
28. A method according to claim 24 wherein the remote objects include a remote peer router or remote customer equipment.
29. A method for identifying outages, comprising:
identifying outage events locally at a network processing device; and providing the outage events to a Network Management Server (NMS) or a correlation tool for outage analysis.
identifying outage events locally at a network processing device; and providing the outage events to a Network Management Server (NMS) or a correlation tool for outage analysis.
30. A method according to claim 29 including storing outage data for the outage events locally in the network processing device at least until the outage data is provided to the NMS or correlation tool.
31. A method according to claim 30 including storing the outage data in an outage Management Information Base (MIB).
32 32. A method according to claim 29 including polling for the outage events according to a configuration file sent from the NMS.
33. A method according to claim 32 including modifying which outage events are monitored in the network processing device according to commands sent from the NMS.
34. A method according to claim 29 including storing an object outage table in the network processing device that identifies which objects to poll for outages.
35. A method according to claim 34 including:
automatically discovering remote devices connected to the network processing device; and automatically updating the object outage table with the discovered remote devices.
automatically discovering remote devices connected to the network processing device; and automatically updating the object outage table with the discovered remote devices.
36. A method according to claim 29 including:
filtering the outage events identified at the network processing device; and sending the filtered events to the network management system or correlation tool.
filtering the outage events identified at the network processing device; and sending the filtered events to the network management system or correlation tool.
37. A method for network outage monitoring, comprising:
monitoring for outages associated with a configuration of devices connected to a network processing device;
automatically discovering a new configuration of devices connected to the network processing device; and dynamically updating outage monitoring according to the new configuration of devices.
monitoring for outages associated with a configuration of devices connected to a network processing device;
automatically discovering a new configuration of devices connected to the network processing device; and dynamically updating outage monitoring according to the new configuration of devices.
38. A method according to claim 37 including using a Cisco Discovery Protocol (CDP), Address Resolution Protocol (ARP) protocol, or Internet Control Message Protocol (ICMP) for automatically discovering the new configuration of devices.
39. A method according to claim 37 including:
storing a configuration table identify devices connected to the network processing device; and automatically updating the configuration table with the new configuration of devices.
storing a configuration table identify devices connected to the network processing device; and automatically updating the configuration table with the new configuration of devices.
40. A network processing device, comprising:
a processor configured to manage outage monitoring for objects associated with the network processing device.
a processor configured to manage outage monitoring for objects associated with the network processing device.
41. A network processing device according to claim 40 including memory for storing outage data for the monitored objects.
42. A network processing device according to claim 41 wherein the memory comprises a persistent storage of outage monitoring data when the network processing device loses power.
43. A network processing device according to claim 40 wherein the outage data is stored in a Management Information Base (MIB).
44. A network processing device according to claim 41 wherein the processor monitors for outages by monitoring local objects within the network processing devices.
45. A network processing device according to claim 44 wherein the local objects are associated with a muter processor, line card, or software program within the network processing device.
46. A network processor according to claim 40 wherein the processor initiates pinging of test packets to neighboring devices connected to the network processing device according to outage monitoring results.
47. A network processing device according to claim 40 wherein the processor automatically discovers objects coupled to the network processing device and automatically polls for outages of the discovered objects.
48. A network processing device according to claim 40 wherein the processor determines Accumulated Outage Time (AOT) or Number of Accumulate Failures (NAF) for the monitored objects.
49. A network processing device according to claim 40 including a backup processor and an associated backup memory, the processor storing data from outage monitoring in both the backup memory.
50. A method for measuring outages, comprising:
locally monitoring for outages at a network processing device;
filtering the monitored outages with the local network processing device; and sending the filtered outages to an outage correlation system.
locally monitoring for outages at a network processing device;
filtering the monitored outages with the local network processing device; and sending the filtered outages to an outage correlation system.
51. A method according to claim 50 including calculating an Accumulated Outage Time (AOT) outage parameter or a Number of Accumulated Failures (NAF) outage parameter from the monitored outages and sending the AOT or NAF to the correlation system.
52. A method according to claim 51 including deriving a Mean Time Between Failures or a Mean Time To Repair value from the AOT or NAF parameters with the correlation system.
53. A method according to claim 50 including:
identifying different outages associated with a same line card;
filtering the different line card outages into a single line card outage indication; and sending the single line card outage indication to the outage correlation system.
identifying different outages associated with a same line card;
filtering the different line card outages into a single line card outage indication; and sending the single line card outage indication to the outage correlation system.
54. A method according to claim 50 including filtering the monitored outages from a system log file.
55. A method for measuring an outage for a network processor device, comprising:
generating a time stamp for the network processing device;
storing the time stamp locally in the network processing device;
periodically updating the stored time stamp with a most recent time stamp for the network processing device;
retaining the most recent stored time stamp during a network processing device outage; and using the retained most recent stored time stamp to determine an outage time for the network processing device.
generating a time stamp for the network processing device;
storing the time stamp locally in the network processing device;
periodically updating the stored time stamp with a most recent time stamp for the network processing device;
retaining the most recent stored time stamp during a network processing device outage; and using the retained most recent stored time stamp to determine an outage time for the network processing device.
56. A method according to claim 55 including;
identifying a system up time when the network processing device has recovered from the outage; and comparing the stored time stamp with the system up time to determine the outage time.
identifying a system up time when the network processing device has recovered from the outage; and comparing the stored time stamp with the system up time to determine the outage time.
57. A method according to claim 55 including periodically storing the most recent time stamp in a persistent memory.
58. A method according to claim 55 wherein the outage comprises a power loss to the network processing device.
59. A method according to claim 55 wherein the time stamp stored in the network processing device is updated about once every minute.
60. An electronic storage medium for storing computer executable code for detecting outages, the computer executable code comprising:
code for automatically measuring outages using an outage measurement system located locally in a network processing device.
code for automatically measuring outages using an outage measurement system located locally in a network processing device.
61. An electronic storage medium according to claim 60 including code for storing outage data locally in the network processing device.
62. An electronic storage medium according to claim 60 including code for transferring the outage data to a network management system or upper level tool for correlating.
63. An electronic storage medium according to claim 60 including code for automatically discovering devices connect to the local network processing device and automatically polling for outages associated with the discovered devices.
64. An electronic storage medium according to claim 60 including:
code for receiving configuration data from a network management system at the network processing device; and code for automatically monitoring for outages with the outage measurement system according to the received configuration data.
code for receiving configuration data from a network management system at the network processing device; and code for automatically monitoring for outages with the outage measurement system according to the received configuration data.
65. A system for detecting outages, comprising:
means for automatically measuring outages using an outage measurement system located locally in a network processing device.
means for automatically measuring outages using an outage measurement system located locally in a network processing device.
66. A system according to claim 65 including means for storing outage data locally in the network processing device.
67. A system according to claim 65 including means for transferring the outage data to a network management system or upper level tool for correlating.
68. A system according to claim 65 including means for automatically discovering devices connected to the local network processing device and automatically polling for outages associated with the discovered devices.
69. A system according to claim 65 including:
means for receiving configuration data from a network management system at the network processing device; and means for automatically monitoring for outages with the outage measurement system according to the received configuration data.
means for receiving configuration data from a network management system at the network processing device; and means for automatically monitoring for outages with the outage measurement system according to the received configuration data.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2783206A CA2783206C (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/209,845 | 2002-07-30 | ||
US10/209,845 US7149917B2 (en) | 2002-07-30 | 2002-07-30 | Method and apparatus for outage measurement |
PCT/US2003/023878 WO2004012395A2 (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2783206A Division CA2783206C (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2493525A1 true CA2493525A1 (en) | 2004-02-05 |
CA2493525C CA2493525C (en) | 2012-10-02 |
Family
ID=31187156
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2493525A Expired - Lifetime CA2493525C (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
CA2783206A Expired - Lifetime CA2783206C (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2783206A Expired - Lifetime CA2783206C (en) | 2002-07-30 | 2003-07-30 | Method and apparatus for outage measurement |
Country Status (6)
Country | Link |
---|---|
US (2) | US7149917B2 (en) |
EP (1) | EP1525713B1 (en) |
CN (1) | CN1672362B (en) |
AU (1) | AU2003257943B2 (en) |
CA (2) | CA2493525C (en) |
WO (1) | WO2004012395A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10691516B2 (en) | 2017-04-05 | 2020-06-23 | International Business Machines Corporation | Measurement and visualization of resiliency in a hybrid IT infrastructure environment |
Families Citing this family (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040163007A1 (en) * | 2003-02-19 | 2004-08-19 | Kazem Mirkhani | Determining a quantity of lost units resulting from a downtime of a software application or other computer-implemented system |
US9451422B2 (en) * | 2003-03-17 | 2016-09-20 | Nokia Technologies Oy | Method, system and network device for routing a message to a temporarily unavailable network user |
US20040215781A1 (en) * | 2003-03-27 | 2004-10-28 | Pulsipher Eric A. | Techniques for determining device connectivity in a network using protocol-specific connectivity information |
US7882213B2 (en) * | 2003-06-03 | 2011-02-01 | Bmc Software, Inc. | Network management system to monitor managed elements |
US20050096953A1 (en) * | 2003-11-01 | 2005-05-05 | Ge Medical Systems Global Technology Co., Llc | Methods and apparatus for predictive service for information technology resource outages |
US7409604B2 (en) * | 2003-12-19 | 2008-08-05 | Microsoft Corporation | Determination of related failure events in a multi-node system |
US7606894B2 (en) * | 2004-01-27 | 2009-10-20 | Ricoh Company, Ltd. | Method and system for determining the type of status information to extract from networked devices in a multi-protocol remote monitoring system |
US8055755B2 (en) * | 2004-02-05 | 2011-11-08 | At&T Intellectual Property Ii, L.P. | Method for determining VoIP gateway performance and SLAs based upon path measurements |
US8107363B1 (en) | 2004-05-21 | 2012-01-31 | Rockstar Bidco, LP | Method and apparatus for accelerating failover of VPN traffic in an MPLS provider network |
US7688723B1 (en) | 2004-09-16 | 2010-03-30 | Avaya Inc. | Procedural XML-based telephony traffic flow analysis and configuration tool |
US7830813B1 (en) * | 2004-09-30 | 2010-11-09 | Avaya Inc. | Traffic based availability analysis |
JP4454516B2 (en) * | 2005-02-16 | 2010-04-21 | 富士通株式会社 | Fault detection device |
US8868717B2 (en) * | 2005-03-15 | 2014-10-21 | Mformation Software Technologies Llc | System and method for trap management and monitoring on wireless terminals |
US7685469B2 (en) * | 2005-04-22 | 2010-03-23 | Microsoft Corporation | Method and apparatus of analyzing computer system interruptions |
US7636315B2 (en) * | 2005-06-21 | 2009-12-22 | Hewlett-Packard Development Company, L.P. | Broadcast traceroute |
US7500150B2 (en) * | 2005-12-30 | 2009-03-03 | Microsoft Corporation | Determining the level of availability of a computing resource |
JP4758259B2 (en) * | 2006-01-31 | 2011-08-24 | 株式会社クラウド・スコープ・テクノロジーズ | Network monitoring apparatus and method |
US7936694B2 (en) * | 2006-04-03 | 2011-05-03 | Hewlett-Packard Development Company, L.P. | Sniffing-based network monitoring |
CN101114994B (en) * | 2006-07-28 | 2010-05-12 | 中兴通讯股份有限公司 | Method for detecting connectivity of multi-protocol label switching virtual private network |
US9088554B1 (en) | 2006-12-29 | 2015-07-21 | At&T Intellectual Property Ii, L.P. | System and method for data modeling |
US7853417B2 (en) * | 2007-01-30 | 2010-12-14 | Silver Spring Networks, Inc. | Methods and system for utility network outage detection |
CN100563179C (en) * | 2007-03-09 | 2009-11-25 | 杭州中导科技开发有限公司 | Ethernet Private Line method of real-time and monitoring equipment thereof |
US8181071B2 (en) * | 2007-06-29 | 2012-05-15 | Microsoft Corporation | Automatically managing system downtime in a computer network |
US7779300B2 (en) * | 2007-07-24 | 2010-08-17 | Microsoft Corporation | Server outage data management |
US20090049167A1 (en) * | 2007-08-16 | 2009-02-19 | Fox David N | Port monitoring |
US7788520B2 (en) * | 2007-09-14 | 2010-08-31 | International Business Machines Corporation | Administering a system dump on a redundant node controller in a computer system |
US8880724B2 (en) | 2008-01-31 | 2014-11-04 | Cisco Technology, Inc. | Event triggered traceroute for optimized routing in a computer network |
JP5349816B2 (en) * | 2008-03-18 | 2013-11-20 | 富士通株式会社 | Line monitoring apparatus and line monitoring method |
US8169921B2 (en) * | 2008-09-30 | 2012-05-01 | At&T Intellectual Property I, Lp | Methods and apparatus to monitor border gateway protocol sessions |
US7975187B2 (en) * | 2008-11-18 | 2011-07-05 | At&T Intellectual Property I, L.P. | Method and apparatus for measuring customer impacting failure rate in communication networks |
US8767587B1 (en) | 2009-01-21 | 2014-07-01 | Cisco Technology, Inc. | Exploratory linktrace operations in a computer network |
US20110072442A1 (en) * | 2009-09-22 | 2011-03-24 | International Business Machines Corporation | Event-handler for selecting responsive actions |
FR2954037B1 (en) * | 2009-12-14 | 2012-01-20 | Legrand France | SYSTEM FOR DISTRIBUTING AT LEAST LOCAL COMPUTER NETWORK SIGNALS AND SIGNALS OF ANOTHER NATURE |
US20110202554A1 (en) * | 2010-02-18 | 2011-08-18 | Hand Held Products, Inc. | Remote device management system and method |
CN102215141A (en) * | 2010-04-02 | 2011-10-12 | 华为技术有限公司 | Method and system for interruption measurement and monitoring equipment |
CN102215139A (en) * | 2010-04-02 | 2011-10-12 | 华为技术有限公司 | Interruption measuring method, device and system |
US8935571B2 (en) * | 2010-12-07 | 2015-01-13 | At&T Intellectual Property I, L.P. | Visual outage management wizard plug-in |
US8949676B2 (en) | 2012-05-11 | 2015-02-03 | International Business Machines Corporation | Real-time event storm detection in a cloud environment |
CN102710449B (en) * | 2012-06-14 | 2016-03-02 | 华为技术有限公司 | The maintaining method of network element device and system, mobile device and network manager service equipment |
TWI462526B (en) * | 2012-11-22 | 2014-11-21 | Accton Technology Corp | The processing method of network device and its power failure signal |
US11528195B2 (en) | 2013-03-15 | 2022-12-13 | NetBrain Technologies, Inc. | System for creating network troubleshooting procedure |
US9438481B2 (en) * | 2013-03-15 | 2016-09-06 | NETBRAIN Technologies, Inc | Sample driven visual programming system for network management |
CN103440174B (en) * | 2013-08-02 | 2016-05-25 | 杭州华为数字技术有限公司 | A kind of error message processing method, device and apply the electronic equipment of this device |
CN103412806A (en) * | 2013-08-12 | 2013-11-27 | 浪潮电子信息产业股份有限公司 | Evaluation method for comprehensive performance of multi-category applications used on super computer |
US9372734B2 (en) | 2013-08-27 | 2016-06-21 | Bank Of America Corporation | Outage window scheduler tool |
US20160197809A1 (en) * | 2013-09-30 | 2016-07-07 | Hewlett Packard Enterprise Development Lp | Server downtime metering |
CN105940637B (en) * | 2014-02-27 | 2020-03-31 | 英特尔公司 | Method and apparatus for workload optimization, scheduling and placement for rack-level architecture computing systems |
CN103873300A (en) * | 2014-03-19 | 2014-06-18 | 辽宁科技大学 | Network equipment energy saving and automatic fault recovery method and device |
US9876674B1 (en) * | 2014-05-03 | 2018-01-23 | Google Llc | Systems and methods for detecting service outages based on aggregate device signals |
CN104219091A (en) * | 2014-08-27 | 2014-12-17 | 中国科学院计算技术研究所 | System and method for network operation fault detection |
CN104461867B (en) * | 2014-11-08 | 2018-04-03 | 南通大学 | A kind of software evolution process failure analysis methods |
JP6444174B2 (en) * | 2015-01-08 | 2018-12-26 | キヤノン株式会社 | Image forming apparatus, image forming apparatus control method, and program |
US11736365B2 (en) | 2015-06-02 | 2023-08-22 | NetBrain Technologies, Inc. | System and method for network management automation |
CN105721197B (en) * | 2016-01-19 | 2019-01-29 | 烽火通信科技股份有限公司 | Improve the method and device of overall information collection accuracy of communication system |
CN110703817B (en) * | 2016-03-29 | 2022-04-05 | 华为技术有限公司 | Control method, device and system for statistical flow |
DE102016206707A1 (en) * | 2016-04-20 | 2017-10-26 | Siemens Aktiengesellschaft | Diagnostic procedure and diagnostic device for a network |
US10785124B2 (en) * | 2017-08-17 | 2020-09-22 | Facebook, Inc. | Network planning with availability guarantees |
US11349727B1 (en) * | 2021-05-11 | 2022-05-31 | At&T Intellectual Property I, L.P. | Service level agreement management service |
GB2616887A (en) * | 2022-03-24 | 2023-09-27 | British Telecomm | Monitoring optical access networks |
CN115209394A (en) * | 2022-05-31 | 2022-10-18 | 深圳市广和通无线股份有限公司 | Log capture method, device, equipment and storage medium |
Family Cites Families (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5822578A (en) | 1987-12-22 | 1998-10-13 | Sun Microsystems, Inc. | System for inserting instructions into processor instruction stream in order to perform interrupt processing |
GB9303640D0 (en) * | 1993-02-23 | 1993-04-07 | British Telecomm | Object-oriented correlation |
US5452287A (en) | 1993-09-20 | 1995-09-19 | Motorola, Inc. | Method of negotiation of protocols, classes, and options in computer and communication networks providing mixed packet, frame, cell, and circuit services |
GB2286508A (en) | 1994-02-08 | 1995-08-16 | Ibm | Performance and status monitoring in a computer network |
EP0799541A1 (en) * | 1994-12-23 | 1997-10-08 | BRITISH TELECOMMUNICATIONS public limited company | Fault monitoring |
US5802286A (en) | 1995-05-22 | 1998-09-01 | Bay Networks, Inc. | Method and apparatus for configuring a virtual network |
US5790431A (en) | 1995-11-20 | 1998-08-04 | International Business Machines Corporation | Method and system for measuring availability in a distributed network |
US5710885A (en) | 1995-11-28 | 1998-01-20 | Ncr Corporation | Network management system with improved node discovery and monitoring |
US5761502A (en) * | 1995-12-29 | 1998-06-02 | Mci Corporation | System and method for managing a telecommunications network by associating and correlating network events |
US5727142A (en) * | 1996-05-03 | 1998-03-10 | International Business Machines Corporation | Method for a non-disruptive host connection switch after detection of an error condition or during a host outage or failure |
US5768501A (en) * | 1996-05-28 | 1998-06-16 | Cabletron Systems | Method and apparatus for inter-domain alarm correlation |
US5832196A (en) * | 1996-06-28 | 1998-11-03 | Mci Communications Corporation | Dynamic restoration process for a telecommunications network |
US5864662A (en) * | 1996-06-28 | 1999-01-26 | Mci Communication Corporation | System and method for reported root cause analysis |
US5845081A (en) | 1996-09-03 | 1998-12-01 | Sun Microsystems, Inc. | Using objects to discover network information about a remote network having a different network protocol |
US5909549A (en) | 1996-11-12 | 1999-06-01 | International Business Machines Corporation | Network management system wherein the managed device reestablishes a connection to a management station after detecting a broken connection |
US5892753A (en) | 1996-12-02 | 1999-04-06 | International Business Machines Corporation | System and method for dynamically refining PMTU estimates in a multimedia datastream internet system |
US5968126A (en) | 1997-04-02 | 1999-10-19 | Switchsoft Systems, Inc. | User-based binding of network stations to broadcast domains |
JPH10308751A (en) | 1997-05-09 | 1998-11-17 | Fujitsu Ltd | Communication terminal for information provision system, network device and terminal identification information setting method, information provision system and fixed length cell transmitter/receiver for information communication system |
US6134671A (en) * | 1997-07-31 | 2000-10-17 | Mci Communications Corporation | System and method for dynamically generating restoration routes within a communications network |
IL121898A0 (en) * | 1997-10-07 | 1998-03-10 | Cidon Israel | A method and apparatus for active testing and fault allocation of communication networks |
US6212171B1 (en) | 1998-06-22 | 2001-04-03 | Intel Corporation | Method and apparatus for gap count determination |
US6269099B1 (en) | 1998-07-01 | 2001-07-31 | 3Com Corporation | Protocol and method for peer network device discovery |
DE19836347C2 (en) * | 1998-08-11 | 2001-11-15 | Ericsson Telefon Ab L M | Fault-tolerant computer system |
US6253339B1 (en) * | 1998-10-28 | 2001-06-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Alarm correlation in a large communications network |
US6337861B1 (en) | 1999-02-02 | 2002-01-08 | Cisco Technology, Inc. | Method and apparatus to properly route ICMP messages in a tag-switching network |
US7020697B1 (en) * | 1999-10-01 | 2006-03-28 | Accenture Llp | Architectures for netcentric computing systems |
US6510203B1 (en) * | 1999-10-20 | 2003-01-21 | Qwest Communications International Inc. | Central office technician notification and information system |
US6594786B1 (en) * | 2000-01-31 | 2003-07-15 | Hewlett-Packard Development Company, Lp | Fault tolerant high availability meter |
AU2001257374A1 (en) | 2000-04-28 | 2001-11-12 | Sheer Networks, Inc. | Network management method and system |
US6747957B1 (en) * | 2000-04-28 | 2004-06-08 | Cisco Technology, Inc. | Network availability monitor |
US6941362B2 (en) | 2000-04-28 | 2005-09-06 | Sheer Networks Inc. | Root cause analysis in a distributed network management architecture |
US7237138B2 (en) * | 2000-05-05 | 2007-06-26 | Computer Associates Think, Inc. | Systems and methods for diagnosing faults in computer networks |
US6966015B2 (en) * | 2001-03-22 | 2005-11-15 | Micromuse, Ltd. | Method and system for reducing false alarms in network fault management systems |
US20020143920A1 (en) | 2001-03-30 | 2002-10-03 | Opticom, Inc. | Service monitoring and reporting system |
US6738933B2 (en) * | 2001-05-09 | 2004-05-18 | Mercury Interactive Corporation | Root cause analysis of server system performance degradations |
CA2365430A1 (en) * | 2001-12-19 | 2003-06-19 | Alcatel Canada Inc. | System and method for collecting statistics for a communication network |
US7360121B2 (en) * | 2002-02-22 | 2008-04-15 | Bea Systems, Inc. | System for monitoring a subsystem health |
US8549133B2 (en) | 2002-03-11 | 2013-10-01 | Qwest Communications International Inc. | Systems and methods for tracking the reliability of communications networks |
US8260907B2 (en) * | 2002-04-04 | 2012-09-04 | Ca, Inc. | Methods, systems and computer program products for triggered data collection and correlation of status and/or state in distributed data processing systems |
US7139925B2 (en) * | 2002-04-29 | 2006-11-21 | Sun Microsystems, Inc. | System and method for dynamic cluster adjustment to node failures in a distributed data system |
US7124328B2 (en) | 2002-05-14 | 2006-10-17 | Sun Microsystems, Inc. | Capturing system error messages |
US20040015619A1 (en) * | 2002-07-18 | 2004-01-22 | International Business Machines Corporation | Method and system for monitoring the status and operation of devices from a central location |
US7213179B2 (en) * | 2002-07-30 | 2007-05-01 | Cisco Technology, Inc. | Automated and embedded software reliability measurement and classification in network elements |
US6830515B2 (en) | 2002-09-10 | 2004-12-14 | Igt | Method and apparatus for supporting wide area gaming network |
US6816813B2 (en) * | 2002-10-15 | 2004-11-09 | The Procter & Gamble Company | Process for determining competing cause event probability and/or system availability during the simultaneous occurrence of multiple events |
US7231182B2 (en) * | 2002-12-23 | 2007-06-12 | Cingular Wireless Ii, Llc | Tracking network problems in a wireless telecommunication system |
US7185231B2 (en) | 2003-05-14 | 2007-02-27 | Microsoft Corporation | Methods and systems for collecting, analyzing, and reporting software reliability and availability |
DE10326427A1 (en) * | 2003-06-10 | 2004-12-30 | Siemens Ag | Method and device for determining the causes of disturbances in industrial processes |
JP4445300B2 (en) * | 2004-03-18 | 2010-04-07 | 富士通株式会社 | Network failure estimation method and network failure estimation device |
US7325170B2 (en) * | 2004-03-19 | 2008-01-29 | Hewlett-Packard Development Company, L.P. | Method and system for providing information for remote device support |
JP4442410B2 (en) * | 2004-12-15 | 2010-03-31 | セイコーエプソン株式会社 | Abnormality diagnosis system |
US20060242453A1 (en) * | 2005-04-25 | 2006-10-26 | Dell Products L.P. | System and method for managing hung cluster nodes |
US7487407B2 (en) * | 2005-07-12 | 2009-02-03 | International Business Machines Corporation | Identification of root cause for a transaction response time problem in a distributed environment |
US20070140133A1 (en) * | 2005-12-15 | 2007-06-21 | Bellsouth Intellectual Property Corporation | Methods and systems for providing outage notification for private networks |
-
2002
- 2002-07-30 US US10/209,845 patent/US7149917B2/en not_active Expired - Lifetime
-
2003
- 2003-07-30 EP EP03772127.1A patent/EP1525713B1/en not_active Expired - Lifetime
- 2003-07-30 CA CA2493525A patent/CA2493525C/en not_active Expired - Lifetime
- 2003-07-30 WO PCT/US2003/023878 patent/WO2004012395A2/en not_active Application Discontinuation
- 2003-07-30 CN CN03818320.XA patent/CN1672362B/en not_active Expired - Fee Related
- 2003-07-30 AU AU2003257943A patent/AU2003257943B2/en not_active Ceased
- 2003-07-30 CA CA2783206A patent/CA2783206C/en not_active Expired - Lifetime
-
2006
- 2006-09-25 US US11/534,908 patent/US7523355B2/en not_active Expired - Lifetime
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10691516B2 (en) | 2017-04-05 | 2020-06-23 | International Business Machines Corporation | Measurement and visualization of resiliency in a hybrid IT infrastructure environment |
Also Published As
Publication number | Publication date |
---|---|
US7149917B2 (en) | 2006-12-12 |
CA2783206A1 (en) | 2004-02-05 |
WO2004012395A3 (en) | 2004-09-02 |
US20040024865A1 (en) | 2004-02-05 |
AU2003257943A1 (en) | 2004-02-16 |
CA2783206C (en) | 2015-07-14 |
WO2004012395A2 (en) | 2004-02-05 |
EP1525713A2 (en) | 2005-04-27 |
EP1525713B1 (en) | 2013-05-01 |
US20070028147A1 (en) | 2007-02-01 |
CN1672362A (en) | 2005-09-21 |
CA2493525C (en) | 2012-10-02 |
US7523355B2 (en) | 2009-04-21 |
AU2003257943B2 (en) | 2009-07-23 |
CN1672362B (en) | 2010-05-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2493525A1 (en) | Method and apparatus for outage measurement | |
US7213179B2 (en) | Automated and embedded software reliability measurement and classification in network elements | |
CN100536403C (en) | Method and equipment of intelligent patrol detection for communication network | |
CN110661669B (en) | Network topology automatic discovery method of network equipment based on ICMP, TCP and UDP protocols | |
US6625648B1 (en) | Methods, systems and computer program products for network performance testing through active endpoint pair based testing and passive application monitoring | |
CN101035037B (en) | Method, system and related device for detecting the network communication quality | |
CN105450472A (en) | Method and device for automatically acquiring states of physical components of servers | |
US20080181134A1 (en) | System and method for monitoring large-scale distribution networks by data sampling | |
CN112714013B (en) | Application fault positioning method in cloud environment | |
US6931356B2 (en) | System for dynamically adjusting performance measurements according to provided service level | |
US7421493B1 (en) | Orphaned network resource recovery through targeted audit and reconciliation | |
JP3293719B2 (en) | Network management system | |
KR100500836B1 (en) | Fault management system of metro ethernet network and method thereof | |
CN112884176B (en) | Management system and method | |
CN115242686A (en) | Power secondary equipment network communication fault detection system and method | |
CN104796294A (en) | Cloud acceleration network monitoring system and method | |
KR100534620B1 (en) | apparatus and method of information management in Network Device | |
WO2001076194A1 (en) | Apparatus and method of determining network address usage and allocation | |
CN117376204A (en) | Method for detecting network server connection | |
JP2007233858A (en) | Failure monitoring system and failure monitoring method | |
JP3280838B2 (en) | Fault information management device and fault information management system | |
Allen | Network maintenance and troubleshooting guide | |
CN115913903A (en) | Method and system for automatically repairing network fault of wave recording master station networking equipment | |
JP2010204850A (en) | Failure monitoring system | |
CN109039785A (en) | Trap alarm clearing method and apparatus based on SNMP |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |