OPTICAL CHASSIS MONITORING

• US 20090103916A1
• Filed: 10/18/2007
• Published: 04/23/2009
• Est. Priority Date: 10/18/2007
• Status: Abandoned Application

• Current Assignee: CSC Holdings LLC (Altice USA, Inc.)
• Original Assignee: CSC Holdings, Inc. (Expedia Group, Inc.)
• Inventors: Dolan, William E. III
• Application Number:
  US11/874,367
• Publication Number:
  US 20090103916A1
• Time in Patent Office: Days
• US Class Current: 398/9
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]

Abstract

Systems and methods for processing event data provided by a managed device which includes a plurality of components. One or more components are identified based on the event data, providing, for example, more accurate information for purposes of network management and equipment maintenance. Applications include the identification of one or more optical modules within an SNMP-managed optical chassis in a hybrid-fiber-coaxial cable-television network.

Claims

1. A method for processing event data provided by a managed device, the managed device comprising a plurality of components, the method comprising:

receiving the event data from the managed device;

obtaining a managed device identifier based on the event data;

obtaining a managed device model corresponding to the managed device identifier; and

identifying at least one component based on the event data and the managed device model, the at least one component being associated with the event.

2. The method of claim 1, wherein the managed device identifier is obtained by parsing the event data, and the at least one component is identified by parsing the event data according to the managed device model.

3. The method of claim 1, wherein the managed device model is obtained by querying a first database, and the at least one component is identified by querying a second database.

4. The method of claim 3, wherein the first database includes an object database, and the second database includes a relationship database.

5. The method of claim 3, further comprising:

obtaining a managed device identifier;

obtaining a managed device model from the managed device identifier;

storing an entry in the first database associating the managed device identifier with a managed device model;

obtaining component identifiers for each of the components; and

for each of the component identifiers, storing an entry in the second database associating the managed device identifier and at least one component identifier with at least one component.

6. The method of claim 5, wherein obtaining the managed device model from the managed device identifier includes requesting information from the managed device identifying the managed device type.

7. The method of claim 5, wherein obtaining the managed device model from the managed device identifier includes querying a third database based on the managed device identifier.

8. The method of claim 5, wherein obtaining component identifiers includes requesting component identifiers from the managed device.

9. The method of claim 5, wherein obtaining component identifiers includes querying a fourth database based on the managed device model.

10. The method of claim 1, wherein the managed device is an SNMP-managed device, and the event data includes an object identifier.

11. The method of claim 10, wherein

obtaining a managed device identifier includes extracting the network address of the managed device from the event data;

and

identifying at least one component includes extracting a component object identifier from the object identifier.

12. The method of claim 1, wherein the event data is received in response to a polling message sent from a network management station to the managed device.

13. The method of claim 1, wherein the event data is received as part of a trap message sent by the managed device to a network management station.

14. The method of claim 1, wherein:

the managed device includes an optical chassis;

the components include optical transmitter/receiver modules;

identifying the at least one component includes identifying a component that generated an alarm; and

event data include alarm data.

15. A method for handling event data in a network, the network including a managed device that comprises a plurality of components, the method comprising:

storing, in an object database, a managed device object;

storing, in the object database, one component object for each of the components;

storing, in a relationship database, one relationship for each of the component objects, each relationship associating a component object with the managed device object;

receiving event data from the managed device;

obtaining the managed device object from the event data and the object database;

identifying at least one component object from the event data, the managed device object, and the relationship database, the at least one component object corresponding to at least one component associated with the event.

16. The method of claim 15, wherein obtaining the managed device object includes:

parsing the event data to obtain a managed device identifier; and

querying the object database based on the managed object identifier.

17. The method of claim 15, wherein identifying at least one component object includes:

parsing the event data according to the managed device object to obtain a component identifier; and

querying the relationship database and the object database based on the component identifier.

18. The method of claim 17, wherein querying the relationship database and the object database includes:

querying the relationship database to obtain a set of component objects; and

querying the object database to obtain the at least one component object from the set of component objects and the at least one component identifier.

19. The method of claim 15, wherein:

the managed device includes an optical chassis;

the components include optical transmitter/receiver modules;

identifying the at least one component includes identifying a component that generated an alarm; and

event data include alarm data.

20. A system for processing event data provided by a managed device, the managed device including a plurality of components, the managed device being associated with a managed device identifier, each component being associated with a component identifier, the system comprising:

a first database associating the managed device identifier with a managed device model;

a second database associating the managed device identifier and at least one component identifier with at least one component; and

a computer system, responsive to the event data, programmed for identifying at least one component from the first database, the second database, and the event data.

21. The system of claim 20, wherein the computer system comprises:

a first running process for parsing the event data to obtain the managed device identifier; and

a second running process for parsing the event data according to the managed device model to obtain at least one component identifier.

22. The system of claim 20, wherein the computer system comprises:

a third running process for querying the first database to obtain the managed device model from the managed device identifier; and

a fourth running process for querying the second database to identify the at least one component from the managed device identifier and the at least one component identifier.

23. The system of claim 20, wherein:

the managed device includes an optical chassis;

the components include optical transmitter/receiver modules;

identifying the at least one component includes identifying a component that generated an alarm; and

event data include alarm data.

24. A computer-readable medium storing a program for processing event data provided by a managed device, the managed device comprising a plurality of components, the program comprising instructions for:

receiving the event data from the managed device;

obtaining a managed device identifier based on the event data;

obtaining a managed device model corresponding to the managed device identifier; and

identifying at least one component based on the event data and the managed device model, the at least one component being associated with the event.