US 7,065,562 B2Grant

System and method for generating a representation of a configuration schema

Issue Date:2006-06-20

•12 Claims

•11 Drawing Sheets

Abstract

A system and method for managing and modeling a network device using a representation of a configuration schema is disclosed. One implementation includes a configuration hash key storage module; a configuration hash object storage module; and a configuration manager.

Metadata

Assignee

Intelliden, Inc.

Inventor

Mike Courtney

Application Information

Application Number:US 09/991,764

Filing Date:2001-11-26

Priority Date:2001-11-26

Art Unit:2154

Classifications

IPC:

G06F15/177

Patent Drawings (11 sheets)

Description

FIELD OF THE INVENTION

[0001] The present application is related to commonly owned and assigned application Nos.:

- [0002] Ser. No. 09/730,864, entitled System and Method for Configuration, Management and Monitoring of Network Resources, filed Dec. 6, 2000;
- [0003] Ser. No. 09/730,680, entitled System and Method for Redirecting Data Generated by Network Devices, filed Dec. 6, 2000;
- [0004] Ser. No. 09/730,863, entitled Event Manger for Network Operating System, filed Dec. 6, 2000;
- [0005] Ser. No. 09/730,671, entitled Dynamic Configuration of Network Devices to Enable Data Transfers, filed Dec. 6, 2000;
- [0006] Ser. No. 09/730,682, entitled Network Operating System Data Directory, filed Dec. 6, 2000;
- [0007] Ser. No. 09/799,579, entitled Global GUI interface for Network OS, filed Mar. 6, 2001;
- [0008] Ser. No. 09/942,834, entitled System and Method for Generating a Configuration Schema, filed Aug. 29, 2001; and
- [0009] Ser. No. 09/942,833, entitled System and Method for Modeling a Network Device's Configuration, filed Aug. 29, 2001.
  all of which are incorporated herein by reference.

[0010] The present invention relates to network device interrogation and configuration. In particular, but not by way of limitation, the present invention relates to systems and methods for interrogating and configuring routers, switches, hubs, and/or optical components.

BACKGROUND OF THE INVENTION

[0011] Networks, and in particular, the Internet, have revolutionized communications. Data vital to the continued prosperity of the world economy is constantly being exchanged between end-users over these networks. Unfortunately, the expansion and maintenance of these networks is outpaced by the demand for additional bandwidth. Network equipment is often difficult to configure, and qualified network technicians are in extremely short supply. Thus, many needed network expansions and upgrades must be delayed until these technicians are available. While these upgrades and expansions are pending, end-users continue to suffer poor network performance.

[0012] For example, Cisco™ routers are notoriously difficult to configure—especially in light of the new XML-based interfaces introduced by competitors such as Juniper Networks™. Instead of a user-friendly XML-based interface, Cisco uses a cumbersome command line interface (CLI) for its routers. Cisco's CLI interface is the result of many years of semi-controlled modifications to its router operating systems and has resulted in a tangled mess of commands and subcommands.

[0013] If Cisco attempted to abandon its CLI in favor of the new user-friendly XML-based interface, many years of development and expertise could be lost. Moreover, even if it could develop an XML-based interface, there is presently no economical way to integrate it into the thousands of existing routers. Despite the difficulties in implementing a more user-friendly interface, to remain competitive, Cisco and similarly situated companies need to move away from the CLI. However, present technology does not provide these companies with an acceptable option that allows continued use of its extensive CLI knowledge base while simultaneously providing system administrators with a user-friendly interface, e.g., XML-based interface. Moreover, present technologies do not provide an acceptable way to provide backward compatibility with existing devices.

[0014] Cisco is not the only manufacturer to face this interface-upgrade problem. Many manufacturers would like to continue using their existing interface knowledge base while providing system administrators a friendly, consistent interface. Accordingly, a system and method are needed that will allow manufacturers, like Cisco, to create user-friendly interfaces for both next-generation and existing devices.

SUMMARY OF THE INVENTION

[0015] Exemplary embodiments of the present invention that are shown in the drawings are summarized below. These and other embodiments are more fully described in the Detailed Description section. It is to be understood, however, that there is no intention to limit the invention to the forms described in this Summary of the Invention or in the Detailed Description. One skilled in the art can recognize that there are numerous modifications, equivalents and alternative constructions that fall within the spirit and scope of the invention as expressed in the claims.

[0016] Embodiments of the present invention can provide a system and method for generating a configuration schema and/or a representation thereof for network devices. Other embodiments can provide a system and method for configuring network devices using a configuration schema and/or a representation of the schema. These and other embodiments are discussed more fully below.

[0017] Although schema are generally used to validate commands, in one implementation of the present invention, the configuration schema can be used to generate commands. For example, a configuration command can be retrieved from a Cisco router. This configuration command is generally expressed in terms of a CLI-based command structure. Using the XML configuration schema, however, the CLI-based commands can be converted to an XML format, which is significantly more manageable than a CLI-based format. Once the CLI-based command has been converted to an XML format, the XML version of the command can be easily passed between various computers and system administrators in a highly readable, standardized format.

[0018] In another implementation, the schema can be used to generate CLI commands from, for example, XML-based commands. As previously described, the configuration schema contains the commands, command hierarchy and bounds of the various configuration commands. When given a command in XML format, the command information in the configuration schema can be used to reformat the XML-based command into a proper CLI format. Once reformatted into a CLI format, the command can be pushed out to the appropriate router. Thus, a system administrator could configure such a router without knowing the specifics of the CLI.

[0019] In another embodiment of the present invention, a representation of the schema is substituted for the schema or used in conjunction with the schema. This representation can be used anywhere that the schema can be used, but can provide significant “runtime” advantages versus the original schema. For example, the representation of the schema can be used to validate commands, generate commands, drive a graphical user interface, etc.

[0020] The representation of the schema can be generated by traversing the schema and creating, for example, a hash table or hash map with entries linked to corresponding container objects. These container objects can include information from the schema and other data, e.g., metadata, which may not be included in the schema, such as device manufacturer, device type, device model, device operating system, etc.

[0021] Advantages of the representation of the schema can include a smaller memory footprint than the complete schema, decreased traversal time when generating or converting commands, and ease-of-use relative to the original schema. As previously stated, however, the above-described embodiments, implementations, and advantages are for illustration purposes only. Numerous other embodiments, implementations, and details of the invention are easily recognized by those of skill in the art from the following descriptions and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Various objects and advantages and a more complete understanding of the present invention are apparent and more readily appreciated by reference to the following Detailed Description and to the appended claims when taken in conjunction with the accompanying Drawings wherein:

[0023] FIG. 1 is a block diagram of a conventional network;

[0024] FIG. 2 is a block diagram of a conventional router;

[0025] FIG. 3 is a flowchart of a method for generating a configuration schema in accordance with one embodiment of the present invention;

[0026] FIG. 4 is a representation of one storage model for storing configuration schema across different device types, manufacturers, models and operating system versions;

[0027] FIG. 5 is a block diagram of a router constructed in accordance with one embodiment of the present invention;

[0028] FIG. 6 is a block diagram of one embodiment of the present invention;

[0029] FIG. 7 is a block diagram of another embodiment of the present invention;

[0030] FIG. 8 is a flowchart of one method for configuring a router using a configuration schema;

[0031] FIG. 9 is a flowchart of one method for generating a representation of a configuration schema; and

[0032] FIG. 10 is a block diagram of one embodiment of the present invention incorporating a representation of the configuration schema.

DETAILED DESCRIPTION

[0033] Referring now to the drawings, where like or similar elements are designated with identical reference numerals throughout the several views, and referring in particular to FIG. 1, it illustrates a block diagram of a conventional network system 100. In this network system 100, end-users 105 are connected to servers 110, which are connected to networking equipment such as hubs, (not shown) optical components 115, and routers 120. Using the networking equipment, end-users 105 associated with different servers 110 can exchange data.

[0034] As new servers 110 and end-users 105 are added to the overall system 100, or as new software becomes available, the routers 120 and/or optical components 115 of the network system 100 may need reconfiguring. To reconfigure these components, a system administrator 125—with the proper authorization—could access the router 120 and/or optical component 115 by, for example, establishing a telnet connection to the component and transferring configuration instructions thereto.

[0035] Referring now to FIG. 2, it is a block diagram of a conventional router. In this representation, a processor 125 is connected to a configuration interface 130, an operating system (OS) storage module 135, a command storage module 140, a configuration storage module 145, and a routing module 150. The illustrated arrangement of these components is logical and not meant to be an actual hardware diagram. Thus, the components can be combined or further separated in an actual implementation. Moreover, the construction of each individual component is well-known to those of skill in the art.

[0036] When a system administrator 125 wishes to reconfigure a router 120, he accesses the router 120 through the configuration interface 130 and retrieves the present configuration for the router 120 from the configuration storage module 145. The system administrator 125 can review available configuration commands and bounds—usually in a CLI format—by accessing and reviewing the commands stored in the command storage module 140. In essence, the command storage module 140 provides the knowledge base for a “help” screen. The commands stored in the command storage module 140 are generally unique to the particular OS version stored in the OS module 135.

[0037] After the system administrator 125 has constructed the new configuration instructions, these instructions are pushed through the configuration interface 130 and stored in the configuration storage module 145. For Cisco routers, interaction is generally through a CLI. In other words, the command storage module 140 is queried through the CLI; available commands are returned through the CLI; and new configuration commands are provided to the router 120 through the CLI. Unfortunately, the CLI is difficult to manage and requires highly skilled technicians for even simple tasks.

[0038] Referring now to FIG. 3, it is a flowchart of one method for generating a configuration schema in accordance with the principles of the present invention. The illustrated method can be used, for example, to generate an XML schema from the CLI commands associated with a Cisco router. In accordance with the principles of the present invention, one method for constructing a configuration schema involves a system administrator 125 (in conjunction with an automated system) connecting to a router 120 through, for example, a telnet connection. Next, the system administrator 125 logs into the router 120 and activates a command extraction mode (steps 160 and 165). With regard to a Cisco router, the command extraction mode is activated by entering a “?”at the prompt. Next, the system administrator 125 retrieves the primary commands, subcommands and bounds (steps 170, 175 and 180). This retrieval can be done through an automated, recursive search. For a Cisco router, the following search could be executed and the following results returned where “>”is the CLI prompt:

- [0039] >?
- [0040] router
- [0041] admin
- [0042] global
- [0043] >router?
- [0044] bgp
- [0045] ospf
- [0046] >
  This process could be repeated until termination for each command and subcommand.

[0047] Once the commands, subcommands, and bounds are collected, they can then be recorded and cleansed (steps 185 and 190). Duplicate commands, for example, could be identified. When these duplicate commands include different subcommands and/or bounds, a single, cleansed command can be constructed to replace the duplicate commands. The cleansed commands, assuming that cleansing was necessary, can then be used to build a configuration schema, which in essence is a modeling of the router's command structure (step 195). An example snippet of such a modeling in an XML schema is represented by:

[0048]


	<xsd:element name=“vlan”>
	<xsd:complexType>
	<xsd:choice>
	<xsd:sequence>
	<xsd:element name=“mapping”>
	<xsd:complexType/>
	</xsd:element>
	<xsd:element name=“dot1q” fixed=“dot1q”>
	<xsd:complexType/>
	<xsd:element>
	<xsd:element name=“ARG.001”.
	<xsd:simpleType>
	.
	.
	.
	</xsd:choice>
	</xsd:complexType>
	</xsd:element>

[0049] In one embodiment, the conversion between the text file and the XML configuration schema is performed by a Visual Basic program. This program identifies arrays of related commands in the text file. Individual arrays can be identified, for example, because they are generally separated by termination characters or by logical termination indicators. Additionally, when an input indicator is encountered in the text file, the program can insert a placeholder into the configuration schema to represent the input indicator. This placeholder can then be associated with the bounds for that particular input. For example, if the input corresponding to the input indicator should be between 1 and 10, a bound of 1 to 10 can be associated with the placeholder.

[0050] After the configuration schema has been generated, it is associated with characteristics of the router and stored accordingly (steps 200 and 205). For example, the configuration schema might be associated with a Cisco router, model 7500, OS version 12.0. A representation of a storage model 210 for storing configuration schema according to manufacturer, device type, device model, and OS version is shown in FIG. 4. The first data block 215 is dedicated to Cisco routers as indicated in the upper left-hand corner. Each row represents a different model of Cisco device, and each column represents a different OS version. Similarly, the second data block is for Juniper™ routers 220 and the third is for Ciena™ devices 225.

[0051] Referring now to FIG. 5, it is a block diagram of a router 230 constructed in accordance with one embodiment of the present invention. In this embodiment, a converter 235 and schema storage module 240 are added to the router of FIG. 2. The router 230 is generally configured to interface with the system administrator 125 through the configuration interface. Even though the router 230 operates through a CLI configuration interface, a system administrator 125 can reconfigure such a router using XML-based commands—assuming the configuration schema stored in the schema storage module 240 is an XML schema. For example, a system administrator 125 can send an XML-based command to the configuration interface 130. That XML-based command can be passed to the converter 235 which converts the XML-based command to a CLI-based command using the XML schema. A CLI-based command, not the XML command, can then be passed to the configuration storage module 145 where it is integrated into the configuration of the router.

[0052] Referring now to FIG. 6, it is a block diagram 245 of an embodiment of the present invention in which the converter and schema storage 245 are localized within the system administrator 125. Rather than components within the router 120 converting an XML-based command to a CLI-based command, the localized converter 235′ and schema storage module 240′ convert the XML-based command to a CLI-based command and then transmit the CLI-based command through the network 250 to the router 120.

[0053] Referring now to FIG. 7, it shows a block diagram 255 of yet another embodiment of the present invention. In this embodiment, the converter 235″ and schema storage module 240″ are distributed relative to both the router 120 and the system administrator 125. Thus, any XML-based configuration commands generated by the system administrator 125 are sent through the network 250 to the converter 235.″ Using the configuration schema stored in the schema storage module 240″, the converter 235″ can convert the XML-based command to a CLI-based command and send that command through the network 250 to the router 120.

[0054] FIG. 8 illustrates one method of operating the system of FIG. 7. In this method, the converter 235″ initially receives an XML-based configuration command (step 260). The converter 235″ then determines the manufacturer, model and/or OS version for the router 120 to which the command is directed and accesses the appropriate configuration schema for that router 120. The (steps 265 and 270) converter 235″ then generates a CLI-based command from the XML-based command, verifies the correctness and validity of that command, and provides it to the router 120 (steps 275 and 280).

[0055] Referring now to FIG. 9, it is a flowchart of one method for generating a representation of a configuration schema. In this embodiment, a representation is generated for each schema. For example, if a first schema was associated with a particular class of Cisco routers and a second schema was associated with a particular class of Juniper routers, then each schema could have a corresponding, unique representation.

[0056] To generate a representation of a particular configuration schema, one embodiment of the present invention retrieves a command from the previously assembled configuration schema (step 290). Additionally, any related commands, e.g., parent commands, child commands, sibling commands, root commands, etc., in the configuration schema can be identified and retrieved. The retrieved command and the retrieved parent commands can then be used to generate a unique hash key for the retrieved command (step 295). An example of such a hash key is:
configuration|interface|FastEthernet.
This type of key can be generated by concatenating indicators of different commands. For example, a hash key can be created by concatenating a parent command, such as “configuration,” with a sibling command, such as “interface.”

[0057] After the unique hash key is generated, a corresponding hash object can also be generated. This hash object can include basic information related to the generated hash key. To generate the schema hash object, information such as data type, sibling commands, and application specific information can be retrieved and assembled into the schema object (steps 300, 305, 310 and 315). The data type information, for example, can indicate whether the data associated with a particular command is a string, an integer, etc. and the sibling information can identify commands at the same hierarchical level as the initially retrieved command that have the same parent command as the initially retrieved command. Additionally, in certain embodiments, specialized application information can also be retrieved from the schema or another source. This application information, for example, can define special processing requirements for a schema. Certain embodiments of the schema hash object also include metadata such as device name, device type, device manufacturer, operating version, etc.

[0058] An exemplary hash object is shown in Example 1. The hash object in Example 1 is associated with the key “configuration|interface|FastEthernet.”

EXAMPLE 1

Hash Object

- [0059] name=FastEthernet
- [0060] parent=interface
- [0061] hierarchy=configuraiton|interface
- [0062] type=null
- [0063] container=choice
- [0064] isContianterOptional=false
- [0065] containerlist=[choice]
- [0066] childContainer=complextype
- [0067] isBounded=false
- [0068] isOptional=false
- [0069] isBoolean=false
- [0070] childElements=[ARG.001, no, arp, random-detect, bandwidth, cdp, description, ip, encapsulaiton, fair-queue, hold-queue, keepalive, logging, priority-group, standby, shutdown]
- [0071] siblingElements=[ ]
- [0072] documentation—Fast Ethernet Interface
- [0073] appInfo=[VALUE_CONCATENATED]
- [0074] isUseRestOfLine=false
- [0075] isValueConcatenated=true
- [0076] restriction base=null
- [0077] minLength=null
- [0078] minInclusive=null
- [0079] maxInclusive=null

[0080] This use of key-based objects has several significant advantages. First, because each schema node of interest is represented in the hash by a key and an associated object, getting to an object via the key is very quick compared to having to traverse through the original schema. Since a direct lookup is possible with the key approach, this significantly reduces the runtime processing required to get schema node information. Second, the object generally contains only the information of interest about the schema node. Thus, extraneous node layers and node data do not have to be decoded and then ignored during the runtime processing. This also reduces processing time. Third, the fact that the schema nodes are manifested as generic programming objects provides ease-of-use for “consumers” of the schema. These consumers, which are other processes, do not have to have built-in redundant knowledge of how to properly traverse and decode the schema objects. This also makes debugging and maintenance much easier since this more difficult code only exists in one place. Fourth, a schema node object can be retrieved from the hash and passed to other programs without having to pass the entire schema or a disjointed part thereof.

[0081] Hash objects can be divided into groups of hash objects, referred to as hashlets. Hashlets can be organized in a variety of ways. For example, hashlets can be formed by grouping hash objects related to a certain level of configuration commands, such as all sibling commands to the “interface” command. In other embodiments, hashlets can be formed by grouping hash objects related to certain tasks. For example, a hashlet can be formed of hash objects related to Quality of Service (QOS) commands.

[0082] Once a hash object has been assembled, the unique key can be stored in a hash map in association with the hash object. If there are any more commands in the schema that need to be modeled (decision 325), branch 330 is followed and the next command can be retrieved (step 290). If all of the commands have been modeled, then branch 335 can be followed and the various hash objects can be stored as a completed hash table (step 340).

[0083] Referring now to FIG. 10, it is a block diagram of one embodiment of the present invention incorporating a representation of the configuration schema. In this embodiment, a schema hash generator 345, which is one implementation of a system for generating a representation, is connected with a schema storage module 240, a schema hash key storage module 350, and a schema hash object storage 355. The schema hash storage module 350 and the schema hash object storage module 355 can be a single memory device or multiple memory devices.

[0084] Data from the schema hash key storage module 350 and/or the schema hash object storage module 355 can be used in various network management applications. For example, the hash keys and the hash objects can be used by a device-neutral command generator, such as an XML command generator 360, to generate device-neutral commands from device-native commands. In other embodiments, the hash keys and the hash objects can be used by a device-native command generator, such as a CLI command generator 365, to generate device-native commands from device-neutral commands. In yet another embodiment, the hash keys and the hash objects can be used by a graphical user interface (GUI) to provide a system administrator with a simplified, device-neutral interface for managing a series of network devices.

[0085] Referring now to FIG. 11, it is a block diagram of one implementation of a representation of the configuration schema. In this implementation, a schema hash key storage module 350 and a schema hash object storage module 355 are connected to a configuration manager 360. The configuration manager 360 can use data from the hash key storage module 250 and the schema hash object storage module 355 to interface with the network device 365.

[0086] Although the embodiments of the present invention are generally described with regard to a router and in particular with regard to Cisco routers, one skilled in the art can understand that the embodiments of the present invention can incorporate routers from most router manufacturers and many other types of network components such as hubs, switches, and optical components. Thus, those skilled in the art can readily recognize that numerous variations and substitutions may be made in the invention, its use and its configuration to achieve substantially the same results as achieved by the embodiments described herein. Accordingly, there is no intention to limit the invention to the disclosed exemplary forms. Many variations, modifications and alternative constructions fall within the scope and spirit of the disclosed invention as expressed in the claims.

Claims

What is claimed is:

1. A method for modeling a command structure of a particular network component, the method comprising:

accessing the particular a network component, wherein the particular network component is capable of facilitating communications in a network, wherein the network includes a plurality of network components;

retrieving a command set from the network component, the command set includes commands for configuring the particular network component, and wherein the commands for configuring the particular network components differ from other commands utilized for configuring other network components;

generating a representation of the retrieved command set, wherein the generated representation corresponds to the network component, and wherein the generating the representation includes:

generating a hash key corresponding to at least a portion of the retrieved command set; and

generating a hash object corresponding to the generated hash key, wherein the generated hash object includes metadata, the metadata including information that identifies the network component from among a plurality of network components; and

storing the generated representation, wherein the step of generating a hash key comprises:

identifying a first level configuration command in the retrieved command set;

identifying a second level configuration command in the retrieved command set; and

concatenating at least an indication of the first level command and at least an indication of the second level command.

2. The method of claim 1, further comprising:

generating a configuration schema from the retrieved command set;

wherein the representation is generated from the configuration schema.

3. The method of claim 2, wherein the generated hash object includes data from the configuration schema.

4. The method of claim 1, wherein retrieving the command set comprises:

retrieving a set of primary commands;

retrieving a set of subcommands for each of the primary commands in the set of primary commands; and

retrieving a set of bounds for a plurality of the set of subcommands for a first of the primary commands.

5. The method of claim 4, wherein generating the hash key comprises:

combining at least an indication of the first of the primary commands with at least an indication of the first of the set of subcommands corresponding to the first of the primary commands.

6. A system for modeling command structures of network components comprising:

a configuration hash key storage module;

a configuration hash object storage module in communication with the configuration hash key storage module;

a configuration hash generator in communication with the configuration hash object storage module, wherein the configuration hash generator is configured to generate hash objects, which include metadata that identifies the network component from among a plurality of network components;

a configuration schema storage module in communication with the configuration hash generator; and

a configuration manager in communication with the configuration hash object storage module,

wherein the configuration manager includes:

a device-neutral configuration command generator,

a device-native configuration command generator; and

a hash object-driven graphical user interface.

7. A computer readable medium, which tangibly embodies a sequence of instructions executable by a machine, comprising:

a plurality of configuration command hash keys, each of the plurality of configuration command hash keys corresponding to at least one of a plurality of configuration commands;

a plurality of configuration command hash objects, wherein each of the plurality of configuration command hash objects corresponds to at least one of the plurality of configuration command hash keys;

wherein each of the plurality of configuration command hash objects comprises both schema data corresponding to at least one of the plurality of configuration commands and metadata that identifies a network component from among a plurality of network components,

wherein the configuration command hash objects are accessible by a configuration manager, wherein the configuration manager includes:

a device-neutral configuration command generator;

a device-native configuration command generator; and

a hash object-driven graphical user interface.

8. An apparatus for modeling a command structure of a particular network component comprising:

means for accessing the particular network component, wherein the particular network component is capable of facilitating communications in a network, wherein the network includes a plurality of network components;

means for retrieving a command set from the network component, the command set includes commands for configuring the particular network component, and wherein the commands for configuring the particular network components differ from other commands utilized for configuring other network components;

means for generating a representation of the retrieved command set, wherein the generated representation corresponds to the network component, and wherein the means for generating the representation includes:

means for generating a hash key corresponding to at least a portion of the retrieved command set; and

means for generating a hash object corresponding to the generated hash key, wherein the generated hash object includes metadata, the metadata including information that identifies the network component from among a plurality of network components; and

means for storing the generated representation,

wherein the means for generating a hash key comprises:

means for identifying a first level configuration command in the retrieved command set;

means for identifying a second level configuration command in the retrieved command set; and

means for concatenating at least an indication of the first level command and at least an indication of the second level command.

9. The apparatus of claim 8, further comprising:

means for generating a configuration schema from the retrieved command set;

wherein the representation is generated from the configuration schema.

10. The apparatus of claim 9, wherein the generated hash object includes data from the configuration schema.

11. The apparatus of claim 8, wherein the means for retrieving the command set comprises:

means for retrieving a set of primary commands;

means for retrieving a set of subcommands for each of the primary commands in the set of primary commands; and

means for retrieving a set of bounds for a plurality of the set of subcommands for a first of the primary commands.

12. The apparatus of claim 11, wherein the means for generating the hash key comprises:

means for combining at least an indication of the first of the primary commands with at least an indication of the first of the set of sub commands corresponding to the first of the primary commands.

Patent Citations (134)

Patent	Date	Inventor	Cited By
US4991089(A)	1991-02-01	Shorter	Applicant
US5109486(A)	1992-04-01	Seymour	Applicant
US5159685(A)	1992-10-01	Kung	Applicant
US5442791(A)	1995-08-01	Wrabetz et al.	Applicant
US5475819(A)	1995-12-01	Miller et al.	Applicant
US5491820(A)	1996-02-01	Belove et al.	Applicant
US5519704(A)	1996-05-01	Farinacci et al.	Applicant
US5557748(A)	1996-09-01	Noris	Applicant
US5581764(A)	1996-12-01	Fitzgerald et al.	Applicant
US5724509(A)	1998-03-01	Starkweather et al.	Applicant
US5726883(A)	1998-03-01	Levine et al.	Applicant
US5751967(A)	1998-05-01	Raab et al.	Applicant
US5764955(A)	1998-06-01	Doolan	Applicant
US5784702(A)	1998-07-01	Greenstein et al.	Applicant
US5787246(A)	1998-07-01	Lichtman et al.	Applicant
US5796732(A)	1998-08-01	Mazzola et al.	Applicant
US5819028(A)	1998-10-01	Manghirmalani et al.	Applicant
US5832503(A)	1998-11-01	Malik et al.	Applicant
US5838918(A)	1998-11-01	Prager et al.	Applicant
US5842040(A)	1998-11-01	Hughes et al.	Applicant
US5852740(A)	1998-12-01	Estes	Applicant
US5872928(A)	1999-02-01	Lewis et al.	Applicant
US5884028(A)	1999-03-01	Kindell et al.	Applicant
US5889953(A)	1999-03-01	Thebaut et al.	Applicant
US5920701(A)	1999-07-01	Miller et al.	Applicant
US5944782(A)	1999-08-01	Noble et al.	Applicant
US5948065(A)	1999-09-01	Eilert et al.	Applicant
US5956341(A)	1999-09-01	Galand et al.	Applicant
US5961594(A)	1999-10-01	Bouvier et al.	Applicant
US5968122(A)	1999-10-01	Schlosser et al.	Applicant
US5968176(A)	1999-10-01	Nessett et al.	Applicant
US5974236(A)	1999-10-01	Sherman	Applicant
US5980078(A)	1999-11-01	Krivoshein et al.	Applicant
US6006035(A)	1999-12-01	Nabahi	Applicant
US6016306(A)	2000-01-01	Le Boudec et al.	Applicant
US6023586(A)	2000-02-01	Gaisford et al.	Applicant
US6028846(A)	2000-02-01	Cain	Applicant
US6041347(A)	2000-03-01	Harsham et al.	Applicant
US6049828(A)	2000-04-01	Dev et al.	Applicant
US6055568(A)	2000-04-01	Adams	Applicant
US6097697(A)	2000-08-01	Yao et al.	Applicant
US6098094(A)	2000-08-01	Barnhouse et al.	Applicant
US6098101(A)	2000-08-01	Sears	Applicant
US6098108(A)	2000-08-01	Sridhar et al.	Applicant
US6101508(A)	2000-08-01	Wolff	Applicant
US6104700(A)	2000-08-01	Haddock et al.	Applicant
US6105069(A)	2000-08-01	Franklin et al.	Applicant
US6108699(A)	2000-08-01	Moiin	Applicant
US6108703(A)	2000-08-01	Leighton et al.	Applicant
US6122664(A)	2000-09-01	Boukobza et al.	Applicant
US6128729(A)	2000-10-01	Kimball et al.	Applicant
US6131118(A)	2000-10-01	Stupek, Jr. et al.	Applicant
US6131119(A)	2000-10-01	Fukui	Applicant
US6154776(A)	2000-11-01	Martin	Applicant
US6167445(A)	2000-12-01	Gai et al.	Applicant
US6170009(B1)	2001-01-01	Mandal et al.	Applicant
US6170011(B1)	2001-01-01	Macleod Beck et al.	Applicant
US6182094(B1)	2001-01-01	Humpleman et al.	Applicant
US6198479(B1)	2001-03-01	Humpleman et al.	Applicant
US6202090(B1)	2001-03-01	Simone	Applicant
US6243747(B1)	2001-06-01	Lewis et al.	Applicant
US6260072(B1)	2001-07-01	Rodriguez-Moral	Applicant
US6269398(B1)	2001-07-01	Leong et al.	Applicant
US6292889(B1)	2001-09-01	Fitzgerald et al.	Applicant
US6349306(B1)	2002-02-01	Malik et al.	Applicant
US6356955(B1)	2002-03-01	Hollberg et al.	Applicant
US6363411(B1)	2002-03-01	Dugan et al.	Applicant
US6370119(B1)	2002-04-01	Basso et al.	Applicant
US6381631(B1)	2002-04-01	Van Hoff	Applicant
US6393425(B1)	2002-05-01	Kelly	Applicant
US6418468(B1)	2002-07-01	Ahlstrom et al.	Applicant
US6438594(B1)	2002-08-01	Bowman-Amuah	Applicant
US6442608(B1)	2002-08-01	Knight et al.	Applicant
US6449638(B1)	2002-09-01	Wecker et al.	Applicant
US6463583(B1)	2002-10-01	Hammond	Applicant
US6496843(B1)	2002-12-01	Getchius et al.	Examiner
US6539425(B1)	2003-03-01	Stevens et al.	Applicant
US6550060(B1)	2003-04-01	Hammond	Applicant
US6567406(B1)	2003-05-01	Skemer	Applicant
US6609108(B1)	2003-08-01	Pulliam et al.	Applicant
US6615166(B1)	2003-09-01	Guheen et al.	Applicant
US6625590(B1)	2003-09-01	Chen et al.	Applicant
US6636877(B1)	2003-10-01	Doleac et al.	Examiner
US6643640(B1)	2003-11-01	Getchius et al.	Examiner
US6654799(B1)	2003-11-01	Tanaka	Applicant
US6658526(B1)	2003-12-01	Nguyen et al.	Applicant
US6678827(B1)	2004-01-01	Rothermel et al.	Applicant
US6684241(B1)	2004-01-01	Sandick et al.	Examiner
US6684244(B1)	2004-01-01	Goldman et al.	Applicant
US6697967(B1)	2004-02-01	Robertson	Examiner
US6725233(B1)	2004-04-01	Froyd et al.	Applicant
US6769116(B1)	2004-07-01	Sexton	Applicant
US6775698(B1)	2004-08-01	Simone	Applicant
US6826597(B1)	2004-11-01	Lonnroth et al.	Applicant
US2002/0032769(A1)	2002-03-01	Barkai et al.	Applicant
US2002/0038320(A1)	2002-03-01	Brook	Applicant
US2002/0051080(A1)	2002-05-01	Tanaka	Applicant
US2002/0171762(A1)	2002-11-01	Maxson et al.	Applicant
US2002/0174091(A1)	2002-11-01	Froyd et al.	Applicant
US2002/0191619(A1)	2002-12-01	Shafer	Applicant
US2002/0198974(A1)	2002-12-01	Shafer	Applicant
US2003/0033589(A1)	2003-02-01	Reyna et al.	Applicant
US2003/0037040(A1)	2003-02-01	Beadles et al.	Examiner
US2003/0048287(A1)	2003-03-01	Little et al.	Examiner
US2003/0084135(A1)	2003-05-01	Narain	Examiner
US2003/0135508(A1)	2003-07-01	Chorafakis et al.	Examiner
US2004/0078695(A1)	2004-04-01	Bowers et al.	Applicant
US2004/0225865(A1)	2004-11-01	Cox et al.	Examiner
EP384339(A2)	1990-08-01		Applicant
EP810755(A2)	1997-12-01		Applicant
EP762281(A3)	1999-03-01		Applicant
EP973296(A2)	2000-01-01		Applicant
EP993725(A1)	2000-04-01		Applicant
EP1011230(A2)	2000-06-01		Applicant
EP1012726(A1)	2000-06-01		Applicant
EP1026867(A2)	2000-08-01		Applicant
EP1047226(A2)	2000-10-01		Applicant
EP1090492(A1)	2001-04-01		Applicant
EP1091526(A2)	2001-04-01		Applicant
GB2368692(A)	2002-05-01		Applicant
WO95/08794	1995-03-01		Applicant
WO95/24802(A)	1995-09-01		Applicant
WO98/18235(A)	1998-04-01		Applicant
WO98/24208	1998-06-01		Applicant
WO99/01968	1999-01-01		Applicant
WO99/11003	1999-03-01		Applicant
WO99/67931	1999-12-01		Applicant
WO/04665	2000-01-01		Applicant
WO/41091	2000-07-01		Applicant
WO1/01293(A2)	2001-01-01		Applicant
WO1/19031(A1)	2001-03-01		Applicant
WO1/47185(A2)	2001-06-01		Applicant
WO1/47186(A2)	2001-06-01		Applicant
WO2/47332(A2)	2002-06-01		Applicant

Non-Patent Literature (31)

Strassner, John; Technology Series—Directory Enabled Networks, 1999; MacMillan Technical Publishing USA.Applicant
“FFST/2 Generic Alert Router for LAN and SNA Transports,” IBM Technical Disclosure Bulletin, IBM Corp. New York, US, vol. 34, No. 11, Apr. 1, 1992, pp. 467-468, XP000303331, ISSN: 0018-8689.Applicant
Torrente S et al: “Implementation of the ANSI T1M1.5 GBM-T1.214 within an ODBMS framework” Networking: Foundation for the Future, San Francisco, Mar. 28-Apr. 1, 1993, Proceedings of the Annual Joint Conference of the Computer and Communications Societies (INFOCOM), Los Alamitos, IEE Comp. Soc. Press, US, vol. 2 CONF. 12, Mar. 28, 1993, pp. 875-884, XP010032227, ISBN: 0-8186-3580-0.Applicant
Kennedy T W: “Network Operations & Management Tool Requirements for the 90s” Proceedings of the Network Operations and Management Symposium (NOMS). Memphis, Apr. 6-9, 1992, New York, IEEE, U.S. Vo. 1, 1992, pp. 122-132.Applicant
Lee, W.C. et al: “Routing Subject to Quality of Service Constraints in Integrated Communication Networks” IEEE Network, IEEE Inc. New York, US, vol. 9, No. 4, Jul. 1, 1995, pp. 46-55, XP000526591, ISSN: 0890-8044 the whole document.Applicant
Williams R: “Web Based Enterprise Management W101” DMTF 1999 Annual Conference, Online! Jun. 15-16, 1999, pp. 1-21.Applicant
Wolf{overscore (s)}on, Ouri et al.: “Managing Communication Networks by Monitoring Databases”, IEEE Transactions on Software Engineering, IEEE Inc. New York, US, vol. 17, No. 9 Sep. 1, 1991, pp. 944-953.Applicant
PCT/US 01/45668—International Search Report dated Oct. 16, 2002.Applicant
PCT/US 01/45669—International Search Report dated Oct. 16, 2002.Applicant
PCT/US 01/45671—International Search Report dated Oct. 16, 2002.Applicant
PCT/US 01/45670—International Search Report dated Dec. 20, 2002.Applicant
PCT/US 01/45672—International Search Report dated Apr. 14, 2003.Applicant
PCT/US 01/45671—Written Opinion dated Dec. 13, 2002.Applicant
Managing Managed Network Services: The Service Provider Blind Spot; Infonetics Research, The Networking Information Source; Jun. 2000 (18 pages).Applicant
ISM Customer—Aware™ Query; CoManage Corporation; As of Dec. 5, 2000 (2 pages).Applicant
ISM Customer—Aware™ Provisioning; CoManage Corporation; As of Dec. 5, 2000 (2 pages).Applicant
ISM Customer—Aware™ Deep Discovery™; CoManage Corporation; As of Dec. 5, 2000 (2 pages).Applicant
ISM Customer—Aware™ Service Profiling; CoManage Corporation; As of Dec. 5, 2000 (2 pages).Applicant
ISM Customer—Aware™ Fault and Performance Management; CoManage Corporation; As of Dec. 5, 2000 (2 pages).Applicant
Lonvick, C. The BSD syslog Protocol. RFC 3164 [online], Aug. 2001 [retrieved on 2002-03-25]. Retrieved from the Internet,<url: HTTP://www.ietf.org/rfc/rfc3164.txt>.Applicant
Case, J., A Simple Network Management Protocol (SNMP). RFC 1098 [online], Apr. 1989 [retrieved on 2002-03-26]. Retrieved from the internet<URL: http;//www.ietf.org/rfc/rfc1098.txt?number=1098>.Applicant
Postel, J.B. Simple Mail Transfer Protocol. RFC 821 [online], Aug. 1982 [retrieved on 2002-03-26]. Retrieved from the Internet<URL: http:///www.ietf.org/rfc/rfc0821.txt?number=821>.Applicant
Finseth, C. An Access Control Protocol, Sometimes called TACACS. RFC 1492 [online], Jul. 1993 [retrieved on 2002-03-25]. Retrieved from the Internet <URL: http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1492.html>.Applicant
Anderson, B.A. TACACS User Identification Telnet Option. RFC 927 [online], Dec. 1984 [retrieved on 2002-03-25]. Retrieved from the Internet<URL: http://www.ietf.org/rfc/rfc0927.txt>.Applicant
Rigney, C., et al. Remote Authentication Dial In User Service (RADIUS). RFC 2138 [online], Apr. 1997 [retrieved on 2002-03-25]. Retrieved from the Internet <URL: http://www.ietf.org/rfc/rfc2138.txt>.Applicant
Rigney, C., Radius Accounting. RFC 2139 [online], Apr. 1997 [retrieved on 2002-03-25]. Retrieved from the Internet <URL: http://www.ietf.org/rfc/rfc2139.txt>.Applicant
Postel, J., and Reynolds, J. Telnet Protocol Specification. RFC 854 [online], May 1983 [retrieved on 2002-03-25]. Retrieved from the Internet<URL: http://www.ietf.org/rfc/rfc0854.txt>.Applicant
Gold Wire Technology, “Tracking Changes.” In Formulator 1.0 User Guide , pp. 211-224.Applicant
Lewis, L., “Policy-Based Configuration Management: A Perspective from a Network Management Vendor,” http://www.simple-times.org./pub/simple-times/issues/8-1.html., pp. 7-27.Applicant
Waldbusser, ST., et al., “Policy Based Management MIB,” http://www.ietf.org/internet-drafts/draft-ietf-snmpconf-pm-05.txt. pp. 1-1102.Applicant
Strassner, J., A New Paradigm for Network Management: Business Deriven Device Management ,[online], 2002, http://www.ssgrr.it/en/ssgrr2002s/papers.htm,http://www.ssgrr.it/en/ssgrr2002s/papers/162.pdf.Applicant

Abstract

Description

FIELD OF THE INVENTION

[0001] The present application is related to commonly owned and assigned application Nos.:

- [0002] Ser. No. 09/730,864, entitled System and Method for Configuration, Management and Monitoring of Network Resources, filed Dec. 6, 2000;
- [0003] Ser. No. 09/730,680, entitled System and Method for Redirecting Data Generated by Network Devices, filed Dec. 6, 2000;
- [0004] Ser. No. 09/730,863, entitled Event Manger for Network Operating System, filed Dec. 6, 2000;
- [0005] Ser. No. 09/730,671, entitled Dynamic Configuration of Network Devices to Enable Data Transfers, filed Dec. 6, 2000;
- [0006] Ser. No. 09/730,682, entitled Network Operating System Data Directory, filed Dec. 6, 2000;
- [0007] Ser. No. 09/799,579, entitled Global GUI interface for Network OS, filed Mar. 6, 2001;
- [0008] Ser. No. 09/942,834, entitled System and Method for Generating a Configuration Schema, filed Aug. 29, 2001; and
- [0009] Ser. No. 09/942,833, entitled System and Method for Modeling a Network Device's Configuration, filed Aug. 29, 2001.
  all of which are incorporated herein by reference.