US 6,349,306 B1Grant
Method and apparatus for configuration management in communications networks
Issue Date:2002-02-19
•21 Claims
•6 Drawing Sheets
Abstract
Apparatus and method for monitoring parameters that govern the operational characteristics of a network device, including the use of templates for generating configuration records of network devices of a selected model type. A database of models is provided, each model representing an associated network device and including attribute values for the parameters of the associated network device. Templates are used to screen a model in order to retrieve values for each of the attributes and create a configuration record. The configuration records may be stored in the configuration manager or other storage device, and/or transferred to the pre-existing model database for use by a network management system in reconfiguring the associated network devices. This system for configuration management is less time consuming, expensive, and error prone than prior systems.
Metadata
Assignee
- Aprisma Management Technologies, Inc.
Inventors
- Rajiv Malik
- Steve Sycamore
- Bill Tracy
Application Information
Application Number:US 09/183,701
Filing Date:1998-10-30
Priority Date:1998-10-30
Art Unit:7
Classifications
IPC:
G06F 1700
Field of Search:
707 10707200707 1707102707203707 8707104709223709203709222713324713187713200
Patent Drawings (6 sheets)
Description
FIELD OF THE INVENTION
[0002] The present invention is directed to configuration management of communications networks, and more specifically to an apparatus and method for processing and storing model-based configuration data and which utilizes templates for configuring a plurality of network devices in order to make such configuration management less time-consuming, expensive and error prone.
BACKGROUND OF THE INVENTION
[0003] Configuration management in communications networks is the task of keeping an inventory of network devices, knowing the configuration of each device, resetting or updating configurations as the need arises, and scheduling configuration changes. In the past, many of these tasks were done manually or by software packages built specifically for a particular device.
[0004] A “configuration” is defined as a particular setting of device parameters that govern the operational characteristics of a network device. In communications networks, the devices that are routinely configured are routers, bridges and hubs, and examples of device parameters include port thresholds, on/off switches, access security, etc.
[0005] In the prior art, one method of network configuration is to manually configure a network device. In this case, a user physically attaches a dumb terminal to the network device and issues configuration commands through the terminal's keyboard. A disadvantage of this method is that one cannot retrieve or store information regarding the configuration of a device.
[0006] A second known method is to make configuration changes with a software package built specially for a network device type. A disadvantage of this method is that one cannot configure different device types simultaneously. Examples of commercially available tools that allow one to configure a single type of device include the following: (1) Site Manager, Wellfleet Communications, Inc., 8 Federal Street, Billerica, Mass. 01821; and (2) Cisco Works, 1525 O'Brien Drive, Menlo Park, Calif. 94025.
[0007] Thus, the primary disadvantages of the prior art include:
[0008] a user can manually configure only one device at a time;
[0009] a user must know the desired configuration before making a change;
[0010] a user must manually check to see if in fact the desired change took place;
[0011] existing tools utilize only one network management protocol (e.g., the simple network management protocol—SNMP) to manage the device; and
[0012] existing tools are specialized for one particular type of device (e.g., Cisco routers).
[0013] In general, the prior art methods are time-consuming, expensive, error prone, and limited in terms of the operations that can be performed.
SUMMARY OF THE INVENTION
[0014] The present invention is directed to a method and apparatus for configuration management of a communications network, and which performs one or more of the following functions:
[0015] enables configuration of several network devices at the same time;
[0016] enables retrieval of a configuration from a device, storage of a configuration, and downloading of the configuration to other devices;
[0017] verifies that configurations have taken place and generates reports and/or alarms when configuration operations are unsuccessful;
[0018] enables automatic scheduling of configuration retrieval, loading and/or verification;
[0019] enables configuration of a wide variety of different network devices.
[0020] The present invention utilizes a database of models, each “model” representing an associated network device and including attribute values for the parameters of that device. A configuration manager accesses a set of model types, each “model type” having an associated set of attributes. The configuration manager creates a template by selecting a model type and one or more attributes from the associated set of attributes, and then screens a selected model with the template to retrieve the values for each of the attributes in the template from the attribute values in the database, to create a configuration record for the model. The configuration record may then be stored, modified, transferred to a model, and/or displayed to a user on a user interface. Also, multiple templates can be used to create a composite configuration record. Multiple configuration records may be transferred to multiple models in the database, for reconfiguring multiple network devices. In one alternative embodiment, a template may be created from a pre-existing configuration record by extracting the attributes of that record. Other features include the generation of alarms to indicate whether or not a transfer or reconfiguration has been successful, and maintaining a scheduler for automatic capture, load or verification of configuration records.
[0021] The terms “model” and “model type” will be more specifically described in regard to the following detailed description. Generally, a model type is analogous to a “class” in object-oriented terminology. Note that a reference to “model type name” is meant to be the same as “model type”.
[0022] The term “model” is analogous to an “instance of a class” or an “object” in object-oriented terminology. So, a model is an instance of a model type. Again, a reference to “model name” means the same as just “model”.
[0023] These and other advantages of the present invention are both particularly described in the following detailed description and drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0024] FIG. 1 is a schematic illustration of one embodiment of an apparatus for configuration management according to this invention.
[0025] FIG. 2 is a main window display from a user interface illustrating the configuration data and options which may be selected according to one embodiment of this invention.
[0026] FIG. 3 illustrates a representative template and a corresponding configuration according to the present invention.
[0027] FIG. 4 is a components window display outlining the components of a main network device (e.g., hub), showing model name and model type according to one embodiment of this invention.
[0028] FIG. 5 is a flow chart of the basic configuration operations according to this invention.
[0029] FIG. 6 is a configuration window display for managing configurations according to this invention.
DETAILED DESCRIPTION
[0030] In accordance with a specific embodiment of the present invention, configuration management may include identifying, controlling and monitoring the “managed devices” that make up a communications network. A managed device is any device that is modeled in a network management system, such as the Spectrum™ Network Management System available from Cabletron Systems, Inc., 35 Industrial Way, Rochester, N.H. 03867. The managed devices include not only hardware devices such as personal computers (PCs), workstations, hubs and routers, but also software applications.
[0031] As illustrated in FIG. 1, a network management system 14, such as Spectrum™, continually monitors the network and maintains a database of information about every managed device in the network. In accordance with this invention, a configuration manager 18 obtains the values of certain attributes (i.e., data which define the characteristics of the network device being modeled) in a desired configuration by interrogating the Spectrum™ model of the managed device. The configuration manager then enables a system administrator, via a user interface (see FIG. 2), to use this information to manage the device. For example, the administrator may create new configurations, load these configurations to devices anywhere on the network, and then verify whether the configurations have changed.
[0032] More specifically, the configuration manager enables a user to create configurations with a template. A template is a list of attributes for a device of a certain model type. When creating a template, the configuration manager provides the user with a list of all readable/writable and non-shared attributes for a model type (which includes the specific device). The user then selects the attributes needed for the template, which depending on the purpose of the template, might include a single attribute (port status, for example) or dozens of attributes.
[0033] The configuration manager then captures the values of the attributes listed in the template, by retrieving the values from the Spectrum™ model. The template functions like a filter, blocking out unwanted attributes (IP address, for example) and capturing the values of those attributes found in the template.
[0034] The resulting configuration created with the template contains the attributes from the template and the values collected from the model. The configuration may be stored in the configuration manager, in another storage device, or the Spectrum™ database.
[0035] FIG. 3 illustrates the difference between a template and a configuration. Item 40 is a template for “new_config template” which includes the list of attributes set forth below the heading “Attribute”. Item 42 is the corresponding configuration for “new_config”, which includes a list of attributes on the left and corresponding values on the right.
[0036] The following glossary of terms is helpful to an understanding of the present invention:
[0037] capture: An operation on a model that stores all attribute/value pairs, obtained by interrogating the selected models through a template. That is, the value of only those attributes that can be found within the template are obtained by interrogating the model.
[0038] configuration: A record of all attribute/value pairs which are obtained by interrogating the selected models through the template. The record may be stored in a compressed form in the configuration manager.
[0039] load: An operation on a model which places the values of the attributes listed in the selected configuration into selected models.
[0040] template: A record which contains a list of attributes for which the configurations will provide values.
[0041] verify: An operation on a model which involves comparing the model's actual attributes/values with the attribute/ value pairs of a configuration.
[0042] attribute: A configurable parameter within a model. The development of the model type creates an attribute by publishing the attribute name and range of possible values.
[0043] An understanding of the present invention is furthered by an understanding of a model-based network management system such as Spectrum™, which is described in U.S. Pat. No. 5,261,044, issued Nov. 9, 1993 to R. Dev et al., and hereby incorporated by reference in its entitety. The Spectrum™ network management system is commercially available and also described in various user manuals and literature available from Cabletron Systems, Inc., Rochester, N.H.
[0044] In summary, Spectrum™ is a system for maintaining and processing information pertaining to the condition of the computer network and providing the same to a user, the network including a plurality of network entities such as computer devices and software applications being executed on such devices. The system includes a virtual network machine, comprising a programmed digital computer, wherein a program is implemented using an object-oriented programming language such as C++, Eiffel, SmallTalk, and Ada. The virtual network consists of interrelated intelligent models of network entities and relations between network entities, including means for acquiring network data pertaining to the condition of a network entity from the corresponding network entity. The virtual network further includes means for maintaining objects which include network data relating to the corresponding network entity and one or more inference handlers for processing the network data, the inference handlers being responsive to changes occurring in the same and/or a different object. The network data can then be transferred to a user interface coupled to the virtual network machine, for supplying the network data to a user.
[0045] Thus, the models are implemented as software “objects” containing both “data” (attributes) relating to the corresponding network entity and one or more “inference handlers” (functions) for processing the data. See Grady Booch, “Object-Oriented Analysis And Design, With Applications,” 2nd Edition, Benjamin/Cummings Publishing Co., Redwood City, Calif., Chapter 2, 1994. The inference handlers are initiated by predetermined virtual network events, such as a change in specified network data in the same model, a change in specified network data in a different model, and predefined events or changes in models or model relations. Information pertaining to the condition of the network entity can be obtained from the network entity by polling the same, can be automatically received from the network entity (without polling), or can be inferred from data contained in other models. An alarm condition may be generated when the network data meets a predetermined criteria. Events, alarms and statistical information from the virtual network are stored in a database and are selectively displayed for the user.
[0046] The data in the Spectrum™ database may be used for generating topological displays of the network, showing hierarchial relationships between network devices, isolating a network fault, and reviewing statistical information.
[0047] Spectrum™ allows for collective management of autonomous local area networks (LANs), with equipment from different vendors. It complies with the current simple network management protocol (SNMP) standards, and can also accommodate other standard and proprietary protocols. The virtual network machine preprocesses the raw information coming from the network devices in order to construct a model of the network's current status and performance characteristics. Network elements that cannot be directly communicated with (e.g., cables and buildings) can infer their status from the status of the devices connected to (or contained within) them. The virtual network machine provides a consistent interface for management applications to access any of the information in the model and thereby provides these applications with a unified view of the network.
[0048] Spectrum's™ associated SpectroGRAPH™ user interface provides a highly graphical multi-perspective view into the network model. SpectroGRAPH™ enables the user to navigate through a landscape in which cables, networks, local area networks and even rooms show up as icons, and which icons indicate the health and performance characteristics of those elements. These icons can be further queried for additional information. SpectroGRAPH™ main function is to visually present to the user the model within the virtual network machine. It allows the user to navigate freely within the network model, only limited by the access rights assigned by the network administrator. The information can be accessed at varying degrees of detail, from a macro overview, to the devices and cables which connect them. In addition to its navigation functions, SpectroGRAPH™ provides an alarm management facility, an event log window, a reporting facility, a find facility, and other features.
[0049] The above description of the Spectrum™ system provides a context for an understanding of the present invention. As described in greater detail below, the configuration manager of the present invention utilizes certain aspects of the Spectrum™ system to provide a configuration management system which is less time-consuming, expensive and error prone.
[0050] FIG. 1 is a block diagram illustrating generally the method and apparatus of the present invention. A network management system 14 monitors a live network 10 via communication link 12. In this example, the network management system is Spectrum™, which includes a database of models and model types relating to corresponding network entities. A configuration management system 18 is connected via communication link 16 to the network management system 14. In this embodiment, the configuration management system 18 is software implemented in an object-oriented programming language such as C++, and developed on a Sun OS platform. The configuration management system may be envoked from an icon subview menu within the SpectroGRAPH™ user interface, which forms part of networking management system 14.
[0051] The configuration management system 18 according to the present invention includes the following features/ functions:
[0052] create and edit templates 20;
[0053] create and edit configurations 22;
[0054] capture configurations 24;
[0055] load configurations 26;
[0056] verify configurations 28;
[0057] status and history reporting 30;
[0058] event-triggered configuration 32;
[0059] configuration scheduling 34; and
[0060] storage 36. These features/functions will be described in greater detail below.
[0061] FIG. 2 illustrates the main display screen for the configuration management system as displayed on SpectroGRAPH™. The display 50 includes a configuration section 52 which lists the available configurations by name and information about the selected configuration in other fields. These configurations all relate to the model by the user, as indicated on the display. The configurations listed in section 52 can be loaded to the selected model or to other models of the same model type, and further to schedule automatic loads as described below. The load and schedule operations are initiated by selecting the icons 58 and 62, respectively. The verify operation, designated by icon 60, enables the user to verify the configuration of the selected model or models, and also to schedule automatic verifications as described below.
[0062] The “Configuration Name” field 55 contains the names of configurations that have previously been created for models of the same model type as the model selected by the user (as shown in line 53). The “Model Specific” field 57 shows whether the configuration is specific to this model or whether it will be included in the configuration list of other models of the same type. The “Loaded” field 59 shows the most recent load status of the configuration, for example: y=successful, n=not loaded, p=partially loaded, and r=rolled back. These will be further defined below.
[0063] The status section 54 includes a “Source” field 61 containing the name of the model from which the configuration was captured. The “Time Loaded” field 63 indicates the last date and time the configuration was loaded. The “Loaded By” field 65 designates the log-in name of the person who loaded the configuration.
[0064] The detail section 56 displays information about the attributes that are in the selected configuration. This enables the user to view the attributes in the configuration before the user elects to load the configuration to a model. The “Attribute” field 64 contains a list of attributes in the configuration and their instance IDs, if any. The “Value” field 67 contains the values of the attributes, which can be numbers or text strings.
[0065] The “Host Configuration” button 66 at the bottom of the window provides the user with the additional options of viewing, editing, printing and loading a host configuration, as opposed to a Spectrum™ configuration. For example, the host configuration file on a Cisco router contains the setup commands used to configure that router. When a user captures or creates a Cisco router configuration, the host configuration button appears at the bottom of the display. This enables a user to perform all of the configuration management operations on the Cisco host configuration. Cisco router is a trademark of Cisco Systems, Inc., Menlo Park, Calif.
[0066] The display screen illustrated in FIG. 4 is a components display 70. This screen is under the “Options” menu 68 on the main display screen (FIG. 2). In FIG. 4, a user has selected the components for “HubEmme—1” and display 70 lists all components according to their relationship to the main device. The main device (HubCSIEMME—a hub sold by Cabletron Systems, Inc.) appears at the top of the right-hand list under the heading “Model Type” 71, and all components of this main device, for example, boards, interface, and applications, appear below the main device. All subcomponents appear indented under the component. On the left-hand side, under the column heading “Model Name” 72, are the specific instances of these components. For example, FIG. 4 illustrates that the main device has an Emme board in slot 1, a TPRMIM22 board in slot 2, and then lists all of the ports on slot 2. Following all of the boards, there are listed the interfaces on the hub and then the applications on the hub.
[0067] The operation of the configuration management system will now be described in greater detail, with reference to the general flow chart of FIG. 5. A summary of FIG. 5 is outlined below, followed by a more detailed discussion:
[0068] Select Model (80)
[0069] Connect to model database
[0070] Display available model/modeltype pairs
[0071] Highlight/check model of interest
[0072] Create template by selecting model type attributes (81)
[0073] Retrieve all attributes from the related modeltype
[0074] Highlight/check attributes of interest
[0075] Save collection of attributes as a template
[0076] Select configuration record (82)
[0077] Connect to configuration record database
[0078] Display available configurations
[0079] Highlight/check configuration of interest
[0080] Create template by selecting configuration attributes (83)
[0081] Retrieve all attributes in configuration record
[0082] Save collection of attributes as a template
[0083] Select template (84)
[0084] Connect to template database
[0085] Display available templates
[0086] Highlight/check template of interest
[0087] Create configuration record (85)
[0088] Connect to model database
[0089] Use template as an index to retrieve attribute values
[0090] Save collection of attribute/value pairs to configuration record database
[0091] Load configuration record (86)
[0092] Connect to model database
[0093] Display available models
[0094] Highlight/check models of interest
[0095] Place parameter values from configuration record into the model
[0096] Verify model(s) against configuration record (87)
[0097] Connect to model database
[0098] Connect to configuration data base
[0099] Display available models
[0100] Display available configurations
[0101] Highlight/check models of interest
[0102] Highlight/check configuration of interest
[0103] Report discrepancies between attribute/value pairs after comparison
[0104] Schedule future load or verification (88)
[0105] Connect to configuration record database
[0106] Display available configurations
[0107] Highlight/check configuration of interest
[0108] Schedule loads or verifications
[0109] Schedule future capture (89)
[0110] Connect to template database
[0111] Display available templates
[0112] Highlight/check templates of interest
[0113] Schedule captures
[0114] The configuration manager allows the user to create configurations in two ways—either with templates or manually without templates. During both processes, the configuration manager captures attribute values and instance IDs, if any, from the selected model. The capture process provides an efficient way to “populate” a configuration, reducing the chances of human error. The user can then modify attribute values and instance IDs when necessary.
[0115] The configuration manager allows the user to create the following types of configurations:
[0116] configurations that can be loaded to the model selected by the user, or to other models of that model type.
[0117] model-specific configurations that are restricted to one device and cannot be loaded to other devices. When the model specific option 57 (FIG. 2) is selected for a configuration, the configuration manager displays the configuration only in the configuration listing of the specified device.
[0118] multiple configurations that can be loaded sequentially to a single device. For example, a user may create multiple configurations when it is necessary to configure certain attributes before configuring others, or when configurations are very large.
[0119] Once a configuration is created, the user can use the load and verify options. The load option enables the user to load the configuration to the model from which it was captured or to one or more models of the same type. This is how one configures new models or reconfigures existing ones. The verify option enables the user to verify whether models' attribute values match that of the configuration created.
Managing Templates
[0120] Templates are useful to create configurations quickly. A library of templates provides administrators with an efficient way to create configurations.
[0121] A template is created by selecting a model (step 80) and then selecting one or more attributes of the model type of the selected model (step 81). The template can later be edited by adding to or deleting selected attributes.
[0122] An alternative method (steps 82-83) of creating a template is from a configuration that has been created manually, or captured with the template and then modified. In this case, the configuration manager takes the attributes listed in the configuration, creates a template from them, and gives the template the same name as the configuration.
Managing Configurations
[0123] A user first selects the desired template (step 84). The configuration manager then uses the template to capture the values of those attributes specified in the template and lists the captured attribute/value pairs in a new configuration (step 85). The configuration manager captures all instances of an attribute, where applicable. The template thus functions as a filter, blocking out unwanted attributes and capturing the values of those attributes specified in the template. Some attributes—IP address, for example, should not be captured in a configuration that will be applied to multiple devices. Therefore, the template used to capture this configuration should not include the IP address attribute.
[0124] When creating a configuration with a template, the configuration manager only includes in the configuration those attributes that can be retrieved from the model. If the configuration manager cannot capture attributes specified in the template, it shows the user the attributes that were not captured. The user can then insert those attributes and values by editing the configuration later, if necessary.
Loading a Configuration
[0125] Once a configuration is created either manually or with the template, the user can load the configuration to one or more models (step 86). As a first alternative, the configuration manager will apply a configuration to the selected model; as a second alternative, the configuration manager will apply a configuration to any number of models of the same model type as the selected model.
[0126] A “safe load” option helps administrators control the load process. When the safe load option is activated, the configuration manager captures the model's configuration before loading a new configuration to it. If the load fails, the configuration manager tries to restore (i.e., roll back) the original configuration to the model.
[0127] The configuration section 52 in the main window 50 (FIG. 2) shows the load status of the configurations which have been created. Successfully loaded configurations (Y) appear first, then partially loaded configurations P, then rolled-back configurations (R). Within these three subcategories, configurations are sorted according to the time of the load, the most recent load appearing first. Configurations that have not been loaded (N) are sorted according to the time they were created—the most recently created appearing first. Configurations that have not been loaded (N) are sorted according to the time they were created —the most recently created appearing first.
[0128] Once a configuration record is loaded to the model, the network management system 14 will modify the parameters of the network device to conform to the configuration data in the model.
Verifying a Configuration
[0129] To perform a verification (step 87), the configuration manager first captures the actual configuration of the model and compares each attribute/value pair in the configuration with the current model's actual configuration. The configuration manager may then display the results to a user via the user interface.
[0130] In addition, the configuration manager enables the user to verify the configurations of other models of the same model type as a selected model, by creating a sublist of the models in for example, a particular network or area.
Scheduling Tasks
[0131] The configuration manager enables administrators to schedule (steps 88 and 89) the time and frequency of automatic captures, loads and verifications. More specifically, this feature may be used to:
[0132] schedule loads, captures and verifications during low-traffic hours.
[0133] maintain more stable configurations by scheduling automatic loads at regular intervals.
[0134] check the integrity of the network with periodic, automatic captures and verifications of configurations.
[0135] The configuration manager sends information about the scheduled operations to the Spectrum™ event log and/or to other storage devices. A user can then view the results of any operation performed by the scheduler.
[0136] For example, to schedule a capture, the user will specify the template to be used and the name of the configuration that is created. Then, the user selects a frequency option (hourly, daily, once, weekly, monthly). The scheduled entry is then sent to a scheduling queue.
[0137] The event log, which is accessed in SpectroGRAPH™, contains the basic information about each configuration operation. An event log entry shows the time the operation was performed, whether it was successful, and the names of the devices, configurations, and templates when applicable.
[0138] The following example is illustrative of the above-described methods.
EXAMPLE
Configuring Ports
[0139] The procedures in this example show how the configuration manager may be used to configure ports (i.e., turn on or off) on an “MRXiRptr” repeater. The example assumes that the MRXiRptr is located in slot 2 of a hub and that the ports are all on.
[0140] 1. In SpectroGRAPH™, select an icon of a hub that contains an MRXiRptr and invoke the configuration manager from it.
[0141] 2. Navigate to the specific component that you want to work with—in this case, an MRXiRptr. Follow these steps:
[0142] a. In the Main window 50 (FIG. 2), click on Navigate Components in the Options menu 68. This opens a Components dialog box (FIG. 4).
[0143] b. Scroll down through the list of components in the Components dialog box, select the MRXiRptr, and click on Apply.
[0144] c. Close the Components window. The Main window 50 now displays all the configurations that are available to the MRXiRptr.
[0145] d. Open a Configurations window 90 (FIG. 6).
[0146] 3. In the Configurations window (FIG. 6), manually create a configuration called “Ports1_2_OFF.” When completed, the configuration should have the following attributes, instance IDs, and values:
| Attribute | Value | |
|---|---|---|
| rptrPortMgmtAdminState 2.1 | 1 | |
| rptrPortMgmtAdminState 2.2 | 1 | |
| rptrPortMgmtAdminState 2.3 | 2 | |
| rptrPortMqmtAdminState 2.4 | 2 | |
| . | . | |
| . | . | |
| . | . | |
[0147] The instance IDs (2.1,2.2, 2.3, 2.4. . .) indicate that this board is located in slot 2 and that there are 4+ ports on the board.
[0148] For this particular attribute, a value of 1 means OFF, a value of 2 means ON. Therefore, this configuration will turn ports 1 and 2 off and ports 3 and 4 on.
[0149] 4. In the Main window 50 (FIG. 2), select the configuration “Ports1_2_OFF” (in section 52), and click on Load 58.
[0150] The configuration manager loads the configuration to the MRXiRptr. If a user keeps the Spectrum™ Device View open, he/she can see the ports 1 and 2 turn blue (off) when the configuration is downloaded.
[0151] Having thus described various embodiments of the present invention, additional modifications and improvements will readily occur to those skilled in the art. Accordingly, the foregoing description is by way of example only, and is not intended to be limiting.
Claims
What is claimed is:
1. A method for monitoring device parameters that govern the operational characteristics of a network device, the method including the steps of:
accessing a database of models, each model representing an associated network device and including attribute values for the parameters of the associated network device;
accessing a set of model types, each model type having an associated set of attributes;
creating a template by selecting a model type and one or more attributes from the associated set of attributes;
screening a model of the selected model type with the template to retrieve values for each of the attributes in the template, from the attribute values in the database, to create a configuration record for the model; and
storing the configuration record.
2. The method of claim 1, further including the steps of transferring the configuration record to a user interface and displaying the configuration record on the user interface.
3. The method of claim 1, wherein the screening is performed using multiple templates simultaneously to create a composite configuration record.
4. The method of claim 1, further including the step of modifying the configuration record.
5. The method of claim 1, further including the step of transferring the configuration record to the associated model.
6. The method of claim 5, further including the step of generating an alarm when the transferring step is unsuccessful.
7. The method of claim 5, wherein the transferring step includes transferring multiple configuration records to multiple models simultaneously.
8. The method of claim 1, further including the step of verifying the configuration of a device by comparing the model and the configuration record.
9. The method of claim 8, further including the step of generating an alarm when the verifying step is unsuccessful.
10. The method of claim 1, further including the step of modifying the parameters of the associated network device.
11. The method of claim 10, further including the step of generating an alarm when the modifying step is unsuccessful.
12. The method of claim 1, further including the step of maintaining a schedule for initiating one or more of the screening, transferring, verifying and modifying steps.
13. The method of claim 1, further including the step of maintaining the database of models, including:
acquiring parameter data from the associated network device;
maintaining a virtual network of interrelated intelligent models comprising objects representing the network devices, each of the objects including the parameter data as attributes and one or more inference handlers for processing the parameter data, the inference handlers being initiated by changes occurring in one or more objects.
14. The method of claim 1, wherein the creating step includes selecting the model type and associated set of attributes from a pre-existing configuration record.
15. A system for monitoring parameters that govern the operational characteristics of the network device, the system comprising:
a database of models, each model representing an associated network device and including attribute values for the parameters of the associated network device;
a database of model types, each model type having an associated set of attributes;
a configuration manager for creating and storing configuration records comprising:
means for creating a template by selecting a model type and one or more attributes from the associated set of attributes;
means for screening a model of the selected type with the template to retrieve values for each of the attributes in the template, for the attribute values in the database, to create a configuration record for the model; and
means for storing the configuration record.
16. The system of claim 15, further including:
a user interface for displaying the configuration record.
17. The system of claim 15, further including:
means for transferring the configuration record to the associated model.
18. The system of claim 15, further including:
means for verifying the configuration of a device by comparing the configuration record and the associated model.
19. The system of claim 15, further including:
means for modifying the parameters of the associated network device.
20. The system of claim 1, further including:
means for generating an alarm when any one of the transferring, verifying and modifying is unsuccessful.
21. The system of claim 1, further including:
means for scheduling one or more of the means for screening, the means for transferring, the means for verifying and the means for modifying.
Patent Citations (30)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5049873(A) | 1991-09-01 | Robins et al. | Examiner |
| US5175800(A) | 1992-12-01 | Galis et al. | Examiner |
| US5193152(A) | 1993-03-01 | Smith | Applicant |
| US5202985(A) | 1993-04-01 | Goyal | Examiner |
| US5226120(A) | 1993-07-01 | Brown et al. | Examiner |
| US5261044(A) | 1993-11-01 | Dev et al. | Examiner |
| US5285494(A) | 1994-02-01 | Sprecher et al. | Examiner |
| US5295244(A) | 1994-03-01 | Dev et al. | Examiner |
| US5333252(A) | 1994-07-01 | Brewer, III et al. | Examiner |
| US5384697(A) | 1995-01-01 | Pascucci | Examiner |
| US5436909(A) | 1995-07-01 | Dev et al. | Examiner |
| US5444851(A) | 1995-08-01 | Woest | Examiner |
| US5452415(A) | 1995-09-01 | Hotka | Examiner |
| US5455938(A) | 1995-10-01 | Ahmed | Examiner |
| US5471399(A) | 1995-11-01 | Tanaka et al. | Examiner |
| US5483631(A) | 1996-01-01 | Nagai et al. | Examiner |
| US5485455(A) | 1996-01-01 | Dobbins et al. | Examiner |
| US5500934(A) | 1996-03-01 | Austin et al. | Examiner |
| US5535335(A) | 1996-07-01 | Cox et al. | Examiner |
| US5535403(A) | 1996-07-01 | Li et al. | Examiner |
| US5539870(A) | 1996-07-01 | Conrad et al. | Examiner |
| US5559955(A) | 1996-09-01 | Dev et al. | Examiner |
| US5568605(A) | 1996-10-01 | Clouston et al. | Examiner |
| US5572652(A) | 1996-11-01 | Robusto et al. | Examiner |
| US5832503(A) | 1998-11-01 | Malik et al. | Examiner |
| US5872928(A) | 1999-02-01 | Lewis et al. | Examiner |
| US5884072(A) | 1999-03-01 | Rasmussen | Examiner |
| US6094654(A) | 2000-07-01 | Van Huben et al. | Examiner |
| US6115713(A) | 2000-09-01 | Pascucci et al. | Examiner |
| EP609990 | 1994-08-01 | Applicant |
Non-Patent Literature (7)
- Terplan, Communications Networks Management, “Fault Management,” (Chapter 8, pp. 263-366), Second edition, Prentice Hall, Englewood Cliffs, New Jersey 07632 (1992).Applicant
- Sloman, Network and Distributed Systems Management, Addison-Wesley Publishing Company, Wokingham, England (1994) “Domains: A Framework For Structuring Management Policy”(Chapter 16, pp. 433-453) Moffett, “Specification of Management Policies and Discretionary Access Control,” (Chapter 17, pp. 455-480).Applicant
- Ericson et al., Expert Systems Applications In Integrated Network Management, “Fault Management Applications,” (Chapter 5, pp. 235-273), Artech House, 685 Canton Street, Norwood, MA 02062 (1989).Applicant
- Weis, Journal of Network and Systems Management, Plenum Publishing Corp., “Policies In Network And Systems Management—Formal Definition And Architecture,” Plenum Publishing Corp., (1994).Applicant
- Roos et al., Integrated Network Management III, “Modelling Management Policy Using Enriched Managed Objects,” Elsevier Science Publishers, North holland, pp. 207-215 (1993).Applicant
- Cheriton et al., “Host Groups: A Multicast Extension For Datagram Internetworks,” Data Communications Symposium, Sep. 1985, pp. 172-179 (USA).Applicant
- “Method For Assigning Network Applications To Users and Groups,” IBM Technical Disclosure Bulletin, vol. 37, No. 4b, Apr. 1994 (New York, USA).Applicant