Data model for automated server configuration

• US 20020082818A1
• Filed: 01/23/2001
• Published: 06/27/2002
• Est. Priority Date: 10/31/2000
• Status: Abandoned Application

• Current Assignee: Opsware, Inc. (HP Inc.)
• Original Assignee: Opsware, Inc. (HP Inc.)
• Inventors: Ferguson, Glenn, Dorsey, Christopher
• Application Number:
  US09/766,570
• Publication Number:
  US 20020082818A1
• Time in Patent Office: Days
• US Class Current: 703/22
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/105 Multiple levels of security

Abstract

The present invention is directed to a data model. The data model allows for modeling of all information relating to a computer network to be conveniently stored in a database in a manner which minimizes the effort associated with the addition of new devices to the network and maximizes software code reuse. The information relating to the network that may be modeled in the data model of the present invention include: software information, configuration information, monitoring information, hardware information, domain name server (DNS) information, network information, and information regarding queues that may be used by business logic, or intelligent agents in accessing and maintaining various portions of the network.

Claims

1. A monitoring data model for relating monitoring objects of a computer network to other monitoring objects, and for expressing the monitoring objects of a computer network in a form accessible to other network components, comprising:

device application configuration entities that represent the configuration of applications on specific devices connected to a network to be monitored;

device authorizations entities that represent various levels of authorization granted to devices connected to a network; and

virtual IP (VIP) groups entities that represent specific VIP groups on a network to be monitored.

2. The monitoring data model of claim 1, further comprising:

monitor access control lists (ACL) entities that represent various ACLs to be monitored, and for interrelating applications, represented by manager applications entities, device ACLs represented by device ACLs entities; and

VIP groups, represented by VIP groups entities.

3. The monitoring data model of claim 1, wherein said device authorizations entities is related to specific devices represented by device entities, and to said monitor ACLs entities by way of one or more device ACLs entities.

4. The monitoring data model of claim 2, wherein said device application configuration entities relate to devices represented by device entities, and to said monitor ACLs entities by way of manager application entities representing manager applications within the application configurations of each device connected to the network.

5. A monitoring data model for relating monitoring objects of a computer network to other monitoring objects, and for expressing the monitoring objects of a computer network in a form accessible by other network components, comprising:

device application configuration entities;

device authorizations entities; and

VIP groups entities;

wherein said device application configuration entities relate to configurations of applications on specific devices connected to the network;

wherein said VIP groups entities relate to various VIP groups of devices on the computer network; and

wherein said device authorizations entities relate devices on the network with access control lists represented by various access control list entities.

6. A computer readable set of instructions residing on a computer-readable medium that produces a monitoring data model comprising:

device entities;

device application configuration entities;

device authorizations entities; and

VIP groups entities;

wherein said device application configuration entities relate to one or more devices represented by said device entities;

wherein said device authorizations entities relate to one or more devices represented by said device entities, and to said device application configuration entities and said VIP groups entities by way of various device access control list entities; and

wherein said VIP groups entities relate to multiple VIP groups of devices represented by said device entities on the network.

7. A monitoring data model for characterizing the monitoring of all aspects of hardware devices connected to a computer network, and the configuration of that network, comprising:

a plurality of devices entities;

a plurality of device request classes entities;

a plurality of request class entities;

a plurality of request class variables entities;

a plurality of manager applications entities;

a plurality of monitor ACLs entities;

a plurality of device application configuration entities;

a plurality of device authorizations entities;

a plurality of device ACLs entities;

a plurality of SNMP variables entities;

a plurality of ACL entries entities; and

a plurality of VIP groups entities.

8. The data model of claim 7, further comprising a plurality of autonomous system map entities.

9. The data model of claim 7 wherein said device request classes entities relate said request class entities to hardware devices by way of a many-to-one relationship with said request class entities and a many-to-one relationship with said plurality of hardware entities.

10. The data model of claim 7 wherein said request class entities represent specific classes of requests that may be made, and wherein said request class entities relate to:

said device request classes entities by a one-to-many relationship; and

said request class variables entities by an optional one-to-many relationship.

11. The data model of claim 7 wherein said request class variables may be used to relate request classes associated with said request class entities with simple network management protocol (SNMP) variables associated with said SNMP variables entities by way of an optional many-to-one relationship with said request class entities, and optional many-to-one relationship with said SNMP variables entities.

12. The data model of claim 7 wherein said manager applications entities relate the monitor access control lists (ACLs) represented by the monitor ACLs entities with the device application configurations represented by the device application configuration entities by way of a one-to-many relationship with the monitor ACLs entities and a one-to-many relationship with the device application configuration entities.

13. The data model of claim 7 wherein said monitor ACLs entities represent the monitoring of the ACLs for various devices on the network, wherein said monitor ACLs entities relate to:

said manager applications entities by a many-to-one relationship;

said device ACLs entities by a one-to-many relationship; and

said ACL entries entities by a one-to-many relationship.

14. The data model of claim 7 wherein said device application configuration entities represent the configuration of applications contained on a device, and wherein said device application configuration entities relate to:

said manager applications entities by a many-to-one relationship; and

said plurality of hardware entities by a many-to-one relationship.

15. The data model of claim 7 wherein said device authorizations entities represent the authorization levels of particular devices, and wherein said device authorizations entities relate to:

said device ACLs entities by a one-to-many relationship; and

said plurality of devices entities by a many-to-one relationship.

16. The data model of claim 7 wherein said device ACLs entities represent device access control lists (ACLs) for specific devices on a network, wherein said device ACLs entities relate to:

said monitor ACLs entities by a many-to-one relationship; and

said device authorizations entities by a many-to-one relationship.

17. The data model of claim 7 wherein said SNMP variables entities represent specific variables associated with the simple network management protocol (SNMP) used by devices on the network, wherein said SNMP variable entities relate to said request class variables entities by an optional one-to-many relationship.

18. The data model of claim 7 wherein said ACL entries entities represent entries within an ACL, wherein said ACL entries entities relate to said monitor ACLs by a many-to-one relationship.

19. The data model of claim 7 wherein said virtual IP (VIP) groups entities represent particular groups sharing virtual IP addresses, wherein said VIP groups entities relate to:

a plurality of configuration entities by a many-to-one relationship; and

a plurality of hardware entities by a many-to-one relationship.