Network topology management system

0001A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the xeroxographic reproduction by anyone of the patent document or the patent disclosure in exactly the form it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

0002The present invention relates to the field of computer systems and their management and control. More specifically, in one particular embodiment the invention provides a method and device for managing and visualizing the topology of a computer network.

0003As computer networks have developed and achieved wide acceptance, it has become necessary for managers of such networks to have access to software and hardware tools necessary to manage, monitor and control networks. As networks have increased in complexity, so have the tools needed for their management. Existing management packages for managing a network provide a wide range of functionality including network management application launchers, event request and filtering mechanisms, logging systems for storing network event and performance statistics, alarm correlation mechanisms, load balancing mechanisms, and other tools. Among the most advanced of such packages is SunSoft's Solstice Enterprise Manager 1.1. Other systems include Hewlett Packard's OpenView platform Network Node Manager, Operations Center and AdminCenter; and IBM's NetView.

0004The most advanced of such packages allow multiple operators to access management information simultaneously and support multiple computing environments. To facilitate this complex functionality advanced network management systems have used an object oriented network model. Network resources represented as objects are stored and manipulated by management applications and agents. The use of such object oriented approaches enables, <i>inter alia,</i> much easier scalability and other advantages. In addition, the support of multiple network management protocols is facilitated. In SunSoft's Solstice products for example, the management tools may be distributed over multiple workstations. The same information is made available to all applications and tools via MISs ("Management Information Servers").

0005Such systems have met with substantial success and are, in fact, considered to be pioneering in the industry. However, certain challenges remain. For example, while the object oriented approach to network database management has proven successful certain limitations remain. Such systems have, previously, maintained separate databases representing the logical and physical layouts of a network, respectively. Separate applications in the network management system then access and may modify the logical and physical topology databases. In some instances it has been found that two views of the same network can be found to be inconsistent as a result of this architecture.

0006According to one aspect of the invention, there is provided a computer network comprising a plurality of network nodes and interconnections; a network management system comprising a database of managed network resources, the database of managed network resources defining network nodes, associated node types and associated views of the nodes; and a plurality of network management users, the network management users being arranged to display views of the network using said network management database. In one embodiment, through user modification of node attributes, the views of the network are updated by the system through use of an object oriented database. In a preferred embodiment the views of the network are modified based on input or change of the attributes of the nodes. For example, parent relationships may be used to define a new view node when a new parent is added to an attribute of a node.

0007It is thus possible to provide improved tools for maintaining, viewing and managing the physical and logical topology of a network. The system can maintain databases for both logical and physical topology using an improved data model. Consistency can be maintained by placing a consistency application in a logical/physical database. In a preferred embodiment, users are able to access the data only through the physical topology database; both physical and logical topology resides in an MIS database.

0008Other aspects of the invention are exemplified by the attached claims.

0009For a better understanding of the invention, and to show how the same may be carried into effect, reference will now be made, by way of example, to the accompanying drawings, in which:- <ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 is an overall view of a hypothetical network, showing the relationship to the network management tools described herein;</li><li>Fig. 2 is a typical screen display provided by one embodiment of the invention;</li><li>Fig. 3 is an object relationship diagram according to one specific embodiment of the invention;</li><li>Figs. 4A to 4C illustrate a simple application of the invention;</li><li>Figs. 5A to 5D illustrate specific data structures used herein; and</li><li>Figs. 6A to 6C illustrate use of the invention in specific examples.</li></ul>

0010Fig. 1 illustrates a computer network along with its associated network management system. As shown, the computer network 100 will include hardware such as hosts 101a, 101b, 101c, 101d, and 101e, routers 103, and subnetworks 100a and 100b. Hosts 101 may be, for example, users, servers and other network elements. Attached to one or more of the hosts are network management elements 109. Management elements 109 will be connected to one or more of the network hosts for network managers to monitor and control the network.

0011The layout of the network is illustrated with regard to physical connectivity, but another set of relationships will also exist. That is, the various elements of the network will also be related by logical relationships. For example, a portion of the users connected to servers 101a and 101b may be in one logical group, while other portions of the network will be in other logical groups. Often it is desirable for network managers to be able to view the network in logical views other than the physical layout of the network. The embodiment now to be described includes an improved viewer mechanism for looking at and analyzing various portions of the network.

0012A management system or "nerve center" 111 is provided in the network to manage and control the network. While the management system 111 is illustrated as a single entity on the network, it may in many embodiments be distributed over multiple workstations and servers.

0013The management system includes an MIS or Management Information Server 113. The MIS is an object oriented network model that enables object definitions to be stored and manipulated by management applications 115, using object oriented tools such as classing, inheritance and scoping to represent complex resources and simplify complex operations. Management applications 115 interact through the network MIS rather than with each other.

0014System 111 will normally include a set of standard tools such as a relational database logging tool, alarm managers and other tools. The system is able to provide access to managed objects via a common management information protocol (CMIP) with management protocol adapter 119. Other system elements are supported directly through an interface such as a protocol driver manager (PDM) in the case of, for example, SunNet Manager Agent interactions.

0015As shown in Fig. 1, a particular user of the system will have applications 115 resident on his/her particular server or workstation. In addition, the use] may have various tools 121, a particular graphical user interface 123 and viewer 125. The various application utilize the resources of the nerve center to perform management tasks. A database 127 in the nerve center provides a single source of network objects in an object oriented relational database to service the various network applications for management of the network. The system illustrated in Fig. 1 will, in a preferred embodiment, be based on the Solstice Enterprise Manager 1.1, available from Sun Microsystems, Inc. The various software and data elements discussed herein are stored on a memory device 128 such DS one or more magnetic or optical disc drives.

0016Fig. 2 illustrates a typical screen display available to a user of the network management system disclosed herein. As shown, the system will display a viewer 201 in which the topology of the system (logical or physical) may be displayed. In addition, the system may display other items of interest such as an alarm report 203.

0017Both the logical and physical elements of the network model are stored in a common database 127. Fig. 3 illustrates the architecture of the network database 127 according to a preferred embodiment of the invention. The purpose of the topology database is to store topological information about the managed networked environments. Topological information is in the form of objects which represent topological nodes, views, viewnodes, and types. The topology database includes data of the following types: a topoTypeDB, a topoNodeDB, and a topoViewDB. These data are used by the system applications to manage the user's networks.

topoTypeDB

0018The topoTypeDB object class 301 contains the general relationship or rules between objects (which represent a topoType 303). In other words, topoTypeDB contains a list of object types. Examples of such object types would be servers, routers, hubs, and users.

0019The topoTypeDB is a managed object class that acts as a "container" for all topoType objects. The topoTypeDB object class is named under the system object and only one instance of a topoTypeDB object class can be created under a system. TopoType is an object class that is named under the topoTypeDB object class.

topoNodeDB

0020The topoNodeDB object class 305 contains a flat layout of the objects in the particular managed networked environment, that is, lists of all nodes 307 in the network and their attributes.

0021The topoNodeDB is a managed object class that acts as the "container" for all topoNode objects. This object class lists all nodes and their attributes. The topoNodeDB object class is named under the system object and only one instance of the topoNodeDB object class can be created under a system.

0022TopoNode is an object class that is named under the topoNodeDB object class. The topoNode object class has the following features. TopoNode can be positioned in multiple views. This attribute is allowed since the behaviour of "topoTypeLegalChildren" is checked for all parents specified by the attribute. The ASN1 syntax of topoNodeParents is a set of topoNodeId's. Special secondary index queries can be done with actions. TopoNode objects can be renamed. The topoNodeName attribute is unique across all topoNodes under the same topoNode DB. The reason that topoNodeName is not used as the naming attribute is to allow renaming of topoNode objects. If a topoNode object is renamed, it's new name cannot be the same as the name of an existing node.

0023A topoNodeChildren attribute is a reverse relationship attribute of a topoNodeParents attribute. It specifies all the topoNode children that are contained by this topoNode. Propagation severity of topoNode objects can be tracked and propagation can be controlled such that, for example, alarms are indicated in desired views.

0024Each node has an associated severity, derived from alarms posted for the corresponding resource. The tracking of the propagated severity is performed with a "topoNodePropagateSeverity" attribute. This attribute is the maximum value of the topoNodeSeverity of the topoNode and the topoNodePropagateSeverity of all its children.

0025To control propagation locally, a topoNode's "topoNodePropagateUp" attribute is used. To turn the propagation off for the entire topology database, the topoNodeDB's "topoStatePropagation" attribute is used. By default, the global propagation flag is set on. A topoNode propagates its current severity to its parents only if its topoNodePropagateUp flag is on and topoNodeDB's topoStatePropagation flag is on.

topoViewDB

0026The topoViewDB 309 object class contains views of the objects in the managed networked environment, that is, of all views 311. The various views contain logical groups of network resources or topology nodes that a user may wish to use for management purposes. For example, a view of various ethernet servers in a network may be desired to monitor the failure rate of such servers. Thus, a view of such servers will be formed.

0027TopoViewDB is a managed object class that acts as the container for all topoView objects. TopoViewDB lists all views; each of these views is called a topoView. The topoViewDB object class is named under the system object and only one instance of the topoViewDB object class can be created under a system. A view is a graphical representation of a set of related managed objects. For example, in a network that contains multiple subnetworks, the network might be one view that has subnetwork elements and each subnetwork within it might constitute or use separate views.

0028TopoView is an object class that lists views and is named under the topoViewDB object class. Each topoView object is called a topoViewNode. Each instance of the topoView class represents a view in an executable viewing program (em_viewer in the case of SunSoft) to display objects that are in the view and store attributes that are related to the view. TopoView objects show relationships and hierarchy between objects. Instances of the class are named under topoViewDB, but create/delete operations are not supported by the name binding.

0029The topoViewNode objects 313 represent topoNode objects in different views (different logical views). Each topoViewNode object is associated with a topoNode object. There is a many-to-one relationship between topoViewNode and topoNode objects. If the information is available in the topoViewNode's associated topoNode object, the information is not duplicated in the topViewHode object. The exception is that the topoNodeId attribute is used as the naming attribute to create topoViewNode objects.

0030Since instances of the class are named under topoView, create/delete operations are not supported by the name binding. All topoViewNode objects are created/deleted as side effects of creating/deleting topoNodes and adding/removing parents to form a "topoNodeParents" attribute of topoNode objects. The MIS is responsible for maintaining the referential integrity between topoViewNode and topoNode objects (for example, a topoNode can contain other topoNodes).

0031TopoViewNode objects are automatically updated. When a new parent is added to the topoNodeParents attribute, the MIS creates a topoViewNode object associating to the topoNode under a topoView object which associates to the new parent. When an old parent is removed from topoNodeParents, the MIS deletes the topviewNode object associating to the topoNode from the topoView object which associates to the old parent. If the user wants to move or place a topoNode in a different or another view, it will be necessary to change the topoNode's topoNodeParents attribute.

0032Data integrity between topoNode, topoView, and topoViewNode is maintained by the system. Data integrity is maintained by the behaviour, in the system herein, of the class. Once a new topoNode is created, if the type of the topoNode can contain other topoNodes, the MIS will create a topoView object associated to the topoNode. If a topoNode is deleted, all topoView and topoViewNode objects associated with the topoNode are automatically removed by the MIS.

0033Fig. 3 includes a description of the containment of the various objects in the database. Specifically, TopoViewDB, topoNodeDB, and topoTypeDB are contained within the "system." A topoView is contained within the topoViewDB. A topoViewNode is contained within a topoView. A topoNode is contained within the topoNodeDB. A topoType is contained within the topoTypeDB.

0034The reference rules for the database are as follows. A topoView must reference a topoNode. Only one topoView can reference a single topoNode. A topoViewNode must reference a topoNode. One or more topoView Nodes can reference a single topoNode. A topoNode can reference other topoNodes as topoNodeParents or topoNodeChildren. A topoNode must reference one topoType. A topoType can be referenced by multiple topoNodes.

0035Table 1 provides general descriptions of topology types. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1</title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="78.75mm" /><colspec colnum="2" colname="col2" colwidth="78.75mm" /><thead valign="top"><row rowsep="1"><entry namest="col1" nameend="col1" align="left">Topology Type</entry><entry namest="col2" nameend="col2" align="left">Description</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Container</entry><entry namest="col2" nameend="col2" align="left">A generic view representation.</entry></row><row><entry namest="col1" nameend="col1" align="left">Universe</entry><entry namest="col2" nameend="col2" align="left">A generic view, generally used at the top level.</entry></row><row><entry namest="col1" nameend="col1" align="left">Internet</entry><entry namest="col2" nameend="col2" align="left">Any combination of IP networks.</entry></row><row><entry namest="col1" nameend="col1" align="left">Subnetwork</entry><entry namest="col2" nameend="col2" align="left">Containers specific to the Internet.</entry></row><row><entry namest="col1" nameend="col1" align="left">Host</entry><entry namest="col2" nameend="col2" align="left">An IP device on a network.</entry></row><row><entry namest="col1" nameend="col1" align="left">Device</entry><entry namest="col2" nameend="col2" align="left">A general representation of a network element.</entry></row><row><entry namest="col1" nameend="col1" align="left">Link</entry><entry namest="col2" nameend="col2" align="left">A physical connection between two network elements.</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">Router, Bridge Hub</entry><entry namest="col2" nameend="col2" align="left">Multiple interface devices capable of transferring packets between networks.</entry></row></tbody></tgroup></table></tables>

0036Figs. 4A to 4C illustrate various views of a network using the system herein, Fig. 4A illustrates a view of several routers 401 in a network. Fig. 4B illustrates a new view that has been created including only two of the routers that a particular user desired to monitor. Fig. 4C illustrates the display after using the system to add another router to the view. Of course, the layout of networks is most often quite complex and Fig. 4 shows only a simple illustration.

0037Figs. 5A to 5D illustrate the data formats and contents of a particular topoType (Fig. 5A), topoNode (Fig. 5B), topoView (Fig. 5C), topoViewNode (Fig. 5D). Of interest, in topoNode, the topoNodeChildren entry (and, not shown, parents) is changed upon change or deletion of, e.g., a parent or other relevant attribute.

0038Fig. 5A illustrates the data structure for a topoType. Fig. 5B illustrates a topoNode entry. Fig. 5C illustrates a particular topoView entry. Fig. 5D illustrates the topoViewNode entry for node 13 in Fig. 5B.

0039The definition of all objects is preferably in GDMO (Guidelines for Definition of Managed Objects) format. The definitions according to one embodiment are shown in the file "topo.gdmo" below. The syntax for GDMO objects is defined in ASN.1. The file "topo.asnl", set out later, provides object syntax according to one specific embodiment of the invention.

Example

0040Figs. 6A to 6C illustrate typical use of the present embodiment. A user typically identifies objects such as routers, hubs, bridges, print servers, NFS servers, and WAN links that have an impact on the greatest number of users on the network. The typical user will then monitor only those devices, reducing the number of managed objects to create and monitor.

0041In the system herein a view of the network can include part (or all) of a network topology or it can simply be an arbitrary collection of managed objects, not part of the topology. In a small scale network, one might wish to place all the critical nodes into a single view of the network, as shown in Fig. 6A. In this example, a network includes two subnets (A and B), which are connected by a router.

0042For most network configurations it will be useful to have multiple views of the network to represent functional groupings of network devices and to represent the network topology. Using the database model discussed above, one might want, for example, to depict devices in particular buildings, or a view that consists only of routers. Taking the example in Fig. 6A one might want to create a separate view for each subnet as well as separate views by type of device (routers, NFS servers, and print servers). A user would create these views one element at a time using a graphical user interface, which would then build the database elements discussed above. As an example, views grouping elements by function (software servers, routers, and print servers) and subnetwork(s) might be formed as shown in Fig. 6B. A high level view is shown in Fig 6C. As shown therein, cloud icons represent the separate views that have been created. By double clicking on the clouds, one would then see the elements within these views of the network. Of course, the same element may appear in multiple views. For example, a particular server could occur in both a "servers" view as well as the Net_B view, which shows all of the nodes in that subnetwork.

0043The above description is illustrative and not restrictive. Many variations of the invention will become apparent to those of skill in the art upon review of this disclosure. Merely by way of example specific database relationships have been used for illustration, but the invention is not so limited.<img file="EP0773649A2_D0001.tif" /><img file="EP0773649A2_D0002.tif" /><img file="EP0773649A2_D0003.tif" /><img file="EP0773649A2_D0004.tif" /><img file="EP0773649A2_D0005.tif" /><img file="EP0773649A2_D0006.tif" /><img file="EP0773649A2_D0007.tif" /><img file="EP0773649A2_D0008.tif" /><img file="EP0773649A2_D0009.tif" /><img file="EP0773649A2_D0010.tif" /><img file="EP0773649A2_D0011.tif" /><img file="EP0773649A2_D0012.tif" /><img file="EP0773649A2_D0013.tif" /><img file="EP0773649A2_D0014.tif" /><img file="EP0773649A2_D0015.tif" /><img file="EP0773649A2_D0016.tif" />