US 7,650,396 B2Grant

System and method for defining a policy enabled network

Issue Date:2010-01-19

•18 Claims

•10 Drawing Sheets

Abstract

A system and method for communicating with network devices without regard to the device type and/or manufacturer is described. In one embodiment, the present invention provides a global graphical user interface (GUI) for communicating with various network devices. The global GUI includes an intuitive interface driven by a template library. For each device type and each device manufacturer, this template library can store both the attribute fields required for device configuration and the format for communicating those attribute fields. When a network administrator wants to communicate with a particular network device, the template associated with that device can be retrieved from the template library. The network administrator can then populate the attribute fields of that template with the appropriate data. This attribute data can be formatted and provided to the network device.

Metadata

Assignee

Intelliden, Inc.

Inventor

Glen D. Tindal

Application Information

Application Number:US 11/763,937

Filing Date:2007-06-15

Priority Date:2000-12-06

Art Unit:2455

Classifications

IPC:

G06F15/177G06F15/173

Patent Drawings (10 sheets)

Description

Priority

[0001] The present application is a continuation application of commonly owned and assigned application Ser. No. 11/216,482, entitled SYSTEM AND METHOD FOR CONFIGURING A NETWORK DEVICE, filed on Aug. 31, 2005, now Pat. No. 7,246,163, which is incorporated herein by reference; which is a continuation application of application Ser. No. 09/799,579, entitled SYSTEM AND METHOD FOR CONFIGURING A NETWORK DEVICE, filed Mar. 6, 2001, now U.S. Pat. No. 6,978,301; which is a continuation-in-part application of the following commonly owned and assigned patent applications: application Ser. No. 09/730,864, entitled SYSTEM AND METHOD FOR CONFIGURATION, MANAGEMENT AND MONITORING OF NETWORK RESOURCES, filed on Dec. 6, 2000, now U.S. Pat. No. 7,249,170; application Ser. No. 09/730,680, entitled SYSTEM AND METHOD FOR REDIRECTING DATA GENERATED BY NETWORK DEVICES, filed on Dec. 6, 2000; application Ser. No. 09/730,863, entitled EVENT MANAGER FOR NETWORK OPERATING SYSTEM, filed Dec 6, 2000; patent application Ser. No. 09/730,671, entitled DYNAMIC CONFIGURATION OF NETWORK DEVICES TO ENABLE DATA TRANSFERS, filed on Dec. 6, 2000, now U.S. Pat. No. 7,054,946; and patent application Ser. No. 09/730,682, entitled NETWORK OPERATING SYSTEM DATA DIRECTORY, filed on Dec. 6, 2000.

Related Applications

[0002] The following commonly owned and assigned patent applications are hereby incorporated by reference in their entirety:

[0003] patent application Ser. No. 09/730,864, entitled System and Method for Configuration, Management and Monitoring of Network Resources, filed on Dec. 6, 2000;
[0004] patent application Ser. No. 09/730,680, entitled System and Method for Redirecting Data Generated by Network Devices, filed on Dec. 6, 2000;
[0005] patent application Ser. No. 09/730,863, entitled Event Manager for Network Operating System, filed on Dec. 6, 2000;
[0006] patent application Ser. No. 09/730,671, entitled Dynamic Configuration of Network Devices to Enable Data Transfers, filed on Dec. 6, 2000; and
[0007] patent application Ser. No. 09/730,682, entitled Network Operating System Data Directory, filed on Dec. 6, 2000.
[0008] patent application Ser. No. 11/763,934, entitled SYSTEM AND METHOD FOR CONFIGURING A NETWORK DEVICE, filed herewith, which is incorporated herein by reference.

Field of the Invention

[0009] The present invention relates generally to network systems. More particularly, but not by way of limitation, the present invention relates to systems and methods for configuring, managing and monitoring network resources such as routers, optical devices and storage devices.

Background of the Invention

[0010] With the ever-increasing reliance upon electronic data, businesses are becoming more and more reliant upon those networks responsible for distributing that data. Unfortunately, the rapid growth in the amount of data consumed by businesses has outpaced the development and growth of certain necessary network infrastructure components. One reason that the development and growth of the network infrastructure has lagged behind centers on the present difficulty in expanding, configuring, and reconfiguring existing networks. Even the most routine network expansions and reconfigurations, for example, require significant, highly technical, manual intervention by trained network administrators. Unfortunately, these highly trained network administrators are in extremely short supply. Thus, many needed network expansions and reconfigurations are delayed or even completely avoided because of the inability to find the needed administrators to perform the required laborious, technical tasks.

[0011] The present difficulty in configuring and reconfiguring networks is best illustrated by an example directed toward installing a single new router on an existing network. To install a new router (such as router 100 or 105 in FIG. 1), an administrator 110 first would need to choose a particular router with the best attributes for the network. The basic configuration of the new router generally will be defined by its manufacturer and its model. Although it would seem that the router should be chosen based upon its attributes, administrators 110 often choose a router based upon the identity of its manufacturer and the administrators' ability to configure devices from that manufacturer. Administrators 110, for example, may only know how to configure and operate devices manufactured by Cisco Systems, Inc. and may overlook equal or even superior devices from other manufacturers merely because they cannot or have not been trained to configure them.

[0012] After the administrator 110 has chosen the desired router (router 105, for example), the administrator 110 generally will order the router 105 from the manufacturer and have it shipped, not necessarily to the installation site, but rather to the administrator's site where a basic configuration can be installed. The administrator 110 then ships the router 105 to the installation site where it can be physically installed. After the router 105 has been physically installed, the administrator 110 typically is manually notified, e.g., by telephone, that the router 105 is connected to the network. The administrator must then create a set of device-specific commands required to fully configure the router 105 and transfer those commands to the router's memory 115. After the administrator 110 verifies that the device-specific commands were installed correctly, the router 105 can be brought online.

[0013] Obviously, the steps required for an administrator to configure a single router are quite cumbersome and require significant technical skill. The problem, however, is even more severe when the administrator desires to simultaneously configure or reconfigure several network devices. First, the administrator, for example, would need to manually identify the network devices that need to be configured or reconfigured. For example, if the administrator desired to turn up service between two points, the administrator would need to identify the routers along the path between the two points. The administrator would then need to verify that the policies and rules established for the network permit the contemplated reconfiguration for those devices. Assuming that the reconfiguration is within the network's policies and rules, the administrator would need to create the device-specific code required to reconfigure each of the identified devices. In many instances, the same device-specific code cannot be used on all of the devices. For example, the device-specific commands required to reconfigure a Cisco™ router differ significantly from the device-specific commands required to reconfigure a Juniper™ router. Thus, if the identified network devices include both Cisco™ and Juniper™ routers, the administrator would be required to create different versions of the device-specific commands, thereby significantly increasing the chance for error in the reconfiguration process.

[0014] Once the device-specific commands have been created for each of the identified network devices, the commands must be manually transmitted to each device. That is, a connection, e.g., a telnet connection, must be established to each device and the particular commands transferred thereto. After each device has received its commands, the network administrator must manually reconnect to each device and verify that the device received the proper commands and that it is operating properly.

[0015] Although some tools have been developed to help administrators perform certain ones of the laborious tasks of network management, these tools are extremely limited in their application. For example, CiscoWorks™ is a group of unrelated tools that can aid administrators in some enterprise level tasks. CiscoWorks™ and similar tools provide singularly focused, unrelated tools to perform activities such as quality of service (QOS) provisioning and network policy management. These tools do not provide a way to interrelate the various happenings in a network. In essence, these present network tools lack a holistic approach to network administration.

[0016] Moreover, tools like CiscoWorks™ are generally dedicated to the management of one type of network device, e.g., router or optical device, and one brand of network device. For example, CiscoWorks™ does not help an administrator configure a Juniper™ router, and it does not help an administrator configure optical devices. Thus, if the network has both Cisco™ and Juniper™ devices, multiple unrelated tools must be utilized to perform basic network management tasks. Unfortunately, because these multiple unrelated tools are so difficult to manage, network administrators are prone to select routers based upon manufacturer identity rather than upon device features.

[0017] In addition to several other drawbacks, these singularly focused network tools result in substandard fault detection and recovery. For example, in present systems, once a configuration is changed, there is no easy way to “back out” of that configuration if a problem arises. Presently, if a new configuration for a target device fails, the network administrator would be forced to recreate the device-specific commands of the target device's previous configuration, manually connect to the device and then transmit the recreated device-specific commands to the device. As can be appreciated, this process can be extremely time consuming and error prone.

[0018] Another drawback to existing network technology centers on the multitude of different interfaces that a network administrator must navigate to configure various network devices. Presently, each network device manufacturer uses its own distinct interface for communicating with its network devices. For example, a network administrator would use a first interface for communicating with a Ciena Corporation (hereinafter “Ciena”) optical device and a second interface for communicating with a Nortel™ optical device. Because, these interfaces may have very little in common, the network administrator would be required to spend a great deal of time learning both interfaces.

[0019] The burden on a network administrator increases dramatically when he needs to communicate with different types of devices manufactured by different companies. In many networks, an administrator could be required to communicate with routers, optical devices, and storage devices—all manufactured by different companies. Thus, a network administrator faces the daunting task of learning and using the distinct interfaces created by each of these manufacturers.

[0020] To date, each network device manufacture unfortunately has focused on building its own interface and making its own product easier to use. In other words, network device manufactures have focused on developing their own software platforms to operate their own network devices. Device manufactures, as would be expected, have not focused on an integrated software platform that will operate devices of different types and/or from different manufactures. There is no motivation for a company like Nortel™ to aid a network administrator in configuring a device from its competitor, Ciena.

[0021] The lack of an integrated software platform for communicating with, operating and/or configuring various network devices has led to the slowed expansion of existing networks. Because network administrators shy away from purchasing network devices that require them to undergo additional training, the lack of such an integrated software platform prevents new device manufactures from entering the market. Moreover, lack of such an integrated software platform prevents new network providers from entering the market because they cannot find trained personnel that can operate the distinct interfaces developed by the various network device manufactures. Accordingly, an integrated network software platform is needed. In particular, a system and method are needed for communicating with network devices without regard to the device type and/or manufacturer.

Summary of the Invention

[0022] In one innovative aspect, a system and method for communicating with network devices without regard to the device type and/or manufacturer is disclosed. In one embodiment, the present invention provides a global graphical user interface (GUI) for communicating with various network devices. Thus, instead of being forced to learn different interfaces for different network devices, a network administrator, using the present invention, can learn a single global GUI and communicate with the various types and brands of network devices.

[0023] Although the global GUI can be constructed in a variety of ways, good results have been achieved by using an intuitive interface driven by a template library. For each device type and each device manufacturer, this template library can store both the attribute fields required for device configuration and the format for communicating those attribute fields. For example, one template could be designed for Cisco™ routers, another for Juniper™ routers, and another for EMC™ storage devices. Moreover, different templates could even be designed for different models of, for example, a particular manufacturer's device.

[0024] When a network administrator wants to communicate with a particular network device, the template associated with that device can be retrieved from the template library. The network administrator can then populate the attribute fields of that template with the appropriate data. Because the global GUI can automatically format the data received from the network administrator, the network administrator can use the same format for the attribute fields across different network devices. In other words, through the present invention, network administrators will not be forced to learn the syntax for different network devices. Rather, the network administrator only needs to learn the syntax for the global GUI, which can “translate” instructions into the proper form and provide those “translated” instructions to the appropriate network device.

[0025] Although the global GUI can be operated independently, good results have been achieved by integrating the global GUI with a directory-enabled network system. For example, the global GUI can be integrated with a network manager unit that is disposed between the network administrator and the various network devices. The network manger unit can include, among other things, a central repository for storing configuration records for each of the attached network devices. In this type of system, the global GUI can be used to configure or reconfigure a configuration record associated with any type or brand of network device. The data in the configuration record can then be used to populate the attribute fields in the template, and the populated fields can be formatted and provided to the appropriate network device. In yet other embodiments, the configuration records and templates can be combined to form a single data structure.

[0026] As can be appreciated by those skilled in the art, the present invention addresses significant shortfalls in present network technology. In particular, the present invention, provides a way to configure, manage and view an entire network system. These and other advantages of the present invention are described more fully herein.

Brief Description of the Drawings

[0027] 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:

[0028] FIG. 1 illustrates a present system for configuring network routers:

[0029] FIG. 2 illustrates a system for configuring network devices in accordance with the principles of the present invention;

[0030] FIG. 3 illustrates in more detail the network manager unit shown in FIG. 2;

[0031] FIG. 4 illustrates in more detail the directory element shown in FIG. 3;

[0032] FIG. 5 illustrates a configuration record for a typical network device in accordance with the present invention;

[0033] FIG. 6 illustrates in more detail the event bus shown in FIG. 3;

[0034] FIG. 7 is a flow chart of a method for configuring a network device in accordance with the present invention;

[0035] FIG. 8 illustrates a network system with an integrated global graphical user interface; and

[0036] FIG. 9 illustrates a directory tree for managing network device templates.

Detailed Description

[0037] Although the present invention is open to various modifications and alternative constructions, a preferred exemplary embodiment that is shown in the drawings is described herein in detail. It is to be understood, however, that there is no intention to limit the invention to the particular forms disclosed. 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.

[0038] Referring now to FIG. 2, there is illustrated a system 120 for configuring network devices 100, 105, 125, 130 (collectively 135) in accordance with the principles of the present invention. This embodiment includes a network manager unit 140 disposed between the administrator 110 and the network devices 135, which can include routers, optical devices, etc. The network manager unit 140 also is connected to remote storage 145 (connected by network 150) and a network manager support 155.

[0039] To alter the configuration of a network device 135 or to add a network device to an existing network, the administrator 110 can access the network manager unit 140, search for and retrieve the configuration record corresponding to a target network device, and through a series of interactive, wizard-like screens, change the configuration record for the target network device. This altered configuration record is stored in a central repository in the network manager unit 140 and can be checked against network policies accessible by the network manager unit 140. Next, the network manager unit 140 can generate device-specific commands from the new configuration record and push those device-specific commands to the target network device or have the target network device pull the commands. Finally, the network manager unit 140 can verify that the new configuration was installed correctly at the target network device.

[0040] To generate the necessary device-specific commands, the network manager unit 140 may access the remote storage device 145 that can contain the various templates needed to generate device-specific commands for different types, brands, and/or models of network devices. Each of these templates can contain variable fields corresponding to either information stored in the configuration records or information input directly by the administrator. The network manager unit 140 generates the device-specific commands by retrieving the appropriate template and filling in the variable fields with the data from the configuration records and/or data input directly by the administrator 110. Once generated, these device-specific commands can be stored in the configuration record and/or they can be stored in the remote storage device 145 with an appropriate pointer stored in the configuration record.

[0041] As can be appreciated by those skilled in the art, the network manager unit 140 can be implemented on virtually any hardware system. Good results, however, have been achieved using components running the Red Hat™ LINUX Operating System and the Sun Solaris™ UNIX Operating System. In embodiments running either of these operating systems, the network manager unit 140 preferably is configured to utilize the common services provided by that particular operating system.

[0042] Referring now to FIG. 3, there is illustrated in more detail the network manager unit 140 shown in FIG. 2. This embodiment of the network manager unit 140 includes six basic modules: an interface 160, a directory 165, a policy manager 170, an event bus 175, a health manager 180 and an action manager 185. The illustrated connections between the various components are exemplary only. The components can be connected in a variety of ways without changing the basic operation of the system. Although the division of the network manager unit 140 into the six components is the presently preferred embodiment, the functions of these components could be subdivided, grouped together, deleted and/or supplemented so that more or less components can be utilized in any particular implementation. Thus, the network manager unit 140 can be embodied in several forms other than the one illustrated in FIG. 3.

[0043] Referring first to the interface module 160, it is designed to exchange data with the administrator 110 (shown in FIG. 2) and, in some embodiments, with the network devices 135 (also shown in FIG. 2). Although the interface 160 could implement virtually any type of interface, good results have been achieved using a graphical, web interface. Other interfaces can be based upon wireless protocols such as WAP (wireless application protocol).

[0044] The second component of the network manager unit 140 is the event bus 175. The event bus 175 includes a central posting location for receiving messages relating to network events. For example, when a configuration for a network device 135 is to be changed, an appropriate message can be published (or otherwise made available) to the event bus 175. Similarly, if a network condition such as an error occurs, an appropriate message can be published to the event bus 175. Notably, any message published to the event bus 175 can also be sent to the administrator 110 by way of the interface 160. The administrator 110, however, does not necessarily need to respond to a received message for the event to be addressed by the network manager unit 140.

[0045] To determine the proper response for a message posted to the event bus 175, the received message can be compared against the policies stored in the policy manager 170, which is a repository for the business and network policies and rules used to manage the network. By using these rules and policies, an administrator 110 (shown in FIG. 2) can define a response for any event published to the event bus 175. The defined response can be virtually anything including reconfiguring a network device, shutting down a network device and notifying an administrator.

[0046] In operation, the policy manager 170 can read a message posted to the event bus 175. Alternatively, the event bus 175 can automatically push the message to the policy manager 170. Either way, however, the policy manager 170 uses the message to access policy records that can be stored, for example, in a look-up table and to correlate the message to the appropriate response. Once the policy manager 170 has determined the appropriate response, that response is published to the event bus 175 as a work order that can be read by the action manager 185 and subsequently executed. That is, the action manager 185 can read the work order from the event bus 175 and perform the necessary tasks to complete that work order. In other embodiments, the work order can be sent directly to the action manager 185. For example, assume that the action manager 185 reads a work order from the event bus 175 that indicates two routers—one a Cisco™ router and one a Juniper™ router—need to be enabled. The action manager 185 can locate each of these routers and determine the device-specific code needed to enable them. The code required to enable the Cisco™ router, for example, might be “enable_router” and the code required to enable the Juniper™ router might be “router_enable.” Because the action manager 185 determines the appropriate device-specific code, however, the administrator 110 (shown in FIG. 2) only needs to generically indicate that both devices are to be enabled. The administrator 110 does not need to know the actual device-specific code required by each router. This feature is described in greater detail with relation to FIG. 8.

[0047] In other embodiments, the action manager 185 can verify that the administrator 110 (shown in FIG. 2) has authority to make changes to network devices without authorization from additional parties. If additional authorization is required, the action manager 185 can post an appropriate message to the event bus 175.

[0048] Still referring to FIG. 3, the directory 165 of the network manager unit 140 includes a central repository for storing the configuration records of each of the network devices connected to the network manager unit 140. For example, the directory 165 could store a separate configuration record for each of network devices 100, 105, 125 and 130 shown in FIG. 2. In certain embodiments, several interconnected directories may be utilized, and in such systems, each directory can store a certain subset of the configuration records or a complete copy of all of the configuration records. Generally, such embodiments would employ multiple linked network manager units 140, and in the embodiment where complete copies of the configuration records are stored in different directories, synchronization techniques can be used to guarantee data integrity.

[0049] The configuration records stored in the directory 165 are searchable by way of the interface 160. That is, the administrator 110 or a component within the network manager 140 (shown in FIG. 2) can initiate a search through the interface 160 and the results of that search can be made available to the administrator 110 through the interface 160. Moreover, the configuration records can be searched in any of a variety of ways. For example, the configuration records can be searched according to equipment type (e.g., routers, optical devices, etc.), device type (edge router, core router, etc.), device location, device manufacturer, device model, device name, operational status, etc. The directory 165 can be used to enable directory-based networking.

[0050] Referring now to the health manager 180, it can be configured to monitor the overall health of the network and/or the health of individual network devices 135 (shown in FIG. 2) within the network. The health manager 180 can operate in an active mode and/or a passive mode. In the active mode, the health manager actively polls at least some of the network devices 135 about their status, utilization, congestion, etc. In the passive mode, the various network devices 135 automatically report to the health manager 180. In either embodiment, however, the health manager 180 can collect individual device information and model overall network health. Additionally, the health manager 180 can publish messages regarding network device problems, projected network device problems, network problems, and/or projected network problems. The policy manager 170 can then determine the appropriate course of action to take for the particular message and the action manager 185 can implement that response.

[0051] In further embodiments, the health manager can monitor the health of the network manager components. For example, the health manager can monitor the operation of the event bus, the action manager and/or the directory. Moreover, the health manager can monitor the flow of data between the various components of the network manager.

[0052] Referring now to FIG. 4, there is illustrated in more detail the directory 165 shown in FIG. 3. This embodiment of the directory 165 consists of four interconnected modules: configuration storage 187, configuration comparator 190, configuration reader 195 and interface 200. The directory 165, however, does not need all of the modules to function in accordance with the principles of the present invention.

[0053] The configuration reader module 195 of the directory 165 is designed to initiate communication with (or directly communicate with) a target network device and retrieve that device's actual configuration. For example, the configuration reader can retrieve the actual configuration from the memory 115 of router 105 (shown in FIG. 2). This retrieved actual configuration can then be passed to the configuration comparator 190. The configuration reader 195 can also retrieve the intended configuration of the target device from the configuration storage 187 and pass that intended configuration to the configuration comparator 190. The configuration comparator 190 can then compare the actual configuration and the intended configuration and present the differences to the administrator 110 (shown in FIG. 2). In one embodiment, the differences in the configurations are not only presented literally, but also in a natural language summary form. Once the differences have been identified, they can be used to identify a failed configuration installation and/or to aid the administrator in creating the proper configuration for a device.

[0054] As previously discussed, the configuration storage 187 is designed to store configuration records corresponding to network devices such as network devices 135 shown in FIG. 2. In one embodiment the configuration storage 187 is designed not only to store the present configuration record for a network device, but also to store previous configuration records for that device. By storing these previous configurations, fault recovery and correction are vastly improved over present systems because prior, successful configurations can be quickly retrieved and used to replace new, faulty configurations. For example, a prior configuration of a previously known good state can be retrieved and installed on the associated network device. This prior configuration could be days old or even weeks old. Prior configuration records can be distinguished by version numbers and/or a time stamp. Additionally, each configuration record can include a searchable summary that includes notes on the configuration and why that configuration was modified.

[0055] Referring now to FIG. 5, there is illustrated a configuration record 205 for a typical network device. This configuration record 205 is divided into four portions: a common information model (“CIM”) data portion 210, a vendor data portion 215, proprietary data portion 220 and a data pointer 225. The CIM data portion 210 contains data relating to the physical attributes of a particular network device such as name, device type, number of interfaces, capacity, etc. The CIM data items are defined in the CIM Specification v2.2 and the CIM Schema v2.4, both of which are well known in the art and incorporated herein by reference.

[0056] The vendor data portion 215 of the configuration record contains standard vendor-specific data regarding the particular network device. For example, the vendor data portion 215 could indicate which version of an operating system that the network device is running or which features of the device are enabled. Generally, the data in the vendor data portion 215 is specific to each manufacturer and even to each model of network device.

[0057] The proprietary data portion 220 of the configuration record can contain data used by the network manager unit in configuring and managing the network devices. In one embodiment, for example, the proprietary data portion 220 includes a pointer to an address at which a core dump for a network device is stored. That is, if a router initiates a core dump, the location of that core dump could be recorded in the proprietary data portion 220 of the configuration record for that router. In other embodiments, the proprietary data portion 220 can store version numbers, time stamps, health records for a particular configuration, configuration summary data, configuration notes, etc.

[0058] The pointer portion 225 of the configuration record 205 can be used to point to a storage location where the actual device-specific commands for the associated network device are stored. Similarly, the pointer 225 could be configured to point to a storage location for a device-specific template for configuring a newly installed network device. In other embodiments, the pointer portion 225 of the configuration record can be supplemented or replaced with a storage location for actual device-specific code.

[0059] Referring now to FIG. 6, there is illustrated in more detail the event bus 175 shown in FIG. 3. As previously described, the event bus 175 is a posting location for messages relating to network events. Network devices as well as the other components of the network manager unit 140 (shown in FIG. 2) can address and post events to the event bus 175.

[0060] The particular embodiment of the event bus 175 shown in FIG. 6 is comprised of four basic modules: an interface 230, a status storage 235, an event queue 240, and an event queue manager 245. In operation, a message indicating the occurrence of a network event is posted to the event queue 240 by way of the interface 230. The messages stored at the event queue 240 are then made available to the policy manager 170 (shown in FIG. 3), so that a proper response can be determined. If the posted message is a work order from the policy manager 170, the work order is made available to the action manager 185 (shown in FIG. 3) for subsequent implementation.

[0061] In one embodiment of the event bus 175, an event message is stored in status storage 235 along with a status field and an age field. Thus, for any message posted to the event bus 175, its status and age can be continuously monitored. (The event bus can also get messages from client devices.) For example, status storage 235 could indicate that the status for a particular event is pending in the action manager 185 (shown in FIG. 3), awaiting proper authorization completed, stalled, etc. As the status changes from one status to another, appropriate messages can be generated and posted at the event queue 240. For example, if the status of an event changes from pending to stalled, an appropriate message can be posted to the event queue 240 so that the policy manager 170 can determine how to respond. Similarly, if the age field in the status storage 235 indicates that a particular network event has not been addressed within a predetermined amount of time, that event can be requeued, deleted from the event queue 240, or a new event notification indicating the delay can be generated and placed on the event queue 240.

[0062] Referring now to FIG. 7, there is a flow chart of one method for configuring or reconfiguring a network device in accordance with the principles of the present invention. In this embodiment, the administrator 110 (shown in FIG. 2) initially logs in to the network manager unit 140 (Step 250). Through a series of a graphical interfaces (such as the global GUI in FIG. 8), the administrator 110 can select a network device that needs to be configured or reconfigured. The configuration record associated with the selected device can then be retrieved from the directory 165 (shown in FIG. 3) and presented to the administrator (Step 255). If no configuration record is available for a selected device, the administrator 110 will be guided through a series of steps to build the configuration for that device. Otherwise, the administrator 110 can change parameters within the configuration record of the selected device and save those altered configuration records within the directory 165 (Step 260). Notably, even though the configuration record for the selected network device has been changed, the actual configuration of the device has not been changed. Before the configuration of the device can be changed, an event message indicating that a configuration record has been altered should be published to the event bus 175 (shown in FIG. 3) (Step 265). The policy manager 170 (shown in FIG. 3) then receives the event message, either by reading it from the event bus 175 or by receiving it from the event bus 175, and determines if the configuration change is authorized (Step 270). If the configuration change is within the network rules and the administrator 110 (shown in FIG. 2) is authorized to make the change, a work order is published to the event bus (Step 280). The action manager 185 (shown in FIG. 3) can then read the work order from the event bus 175 and carry out the necessary steps to implement the work order (Step 280).

[0063] In one embodiment, the action manager 185 (shown in FIG. 3) carries out the work order by locating the target network device, retrieving the appropriate configuration record from the directory 165 (shown in FIG. 3), generating the device-specific code corresponding to the altered configuration (Step 290), and pushing the device-specific code to the target network device (Step 295). The action manger 185 can also store the device-specific code in a remote storage device, such as remote storage device 145 shown in FIG. 2, and a pointer to the remote storage device can be recorded in the configuration record. Finally, the action manager 185 can verify that the device-specific code was properly transferred to the selected network device and that the network device is behaving accordingly (Step 300). Assuming that the device-specific codes were installed correctly and that the network device is operating properly, a completion message is published to the event bus 175 (shown in FIG. 3) (Step 305).

[0064] Referring now to FIG. 8, there is illustrated a network system with an integrated global graphical user interface (GUI 310). In this embodiment, a global GUI 310 is disposed between the network administrator 110 and various network devices (collectively 315). These network devices include storage devices 320a and 320b, routers 325a and 325b, and DWDM (dense wave division multiplexing) switches 330a and 330b connected to optical servers 335a and 335b. Notably, the network devices of the same type can be manufactured by different manufacturers. For example, router 325a can be manufactured by Cisco™ and router 325b can be manufactured by Juniper™.

[0065] As previously discussed, in present network systems, a network administrator 110 could be required to navigate different communication interfaces for each of the network devices 315. Thus, for network system x, a network administrator 110 without the benefit of the present invention could be forced to learn six distinct interfaces. Through the present invention, however, the network administrator 110 can communicate with any of the network devices 315 by navigating the global GUI 310, which presents the network administrator 110 with a familiar graphical interface that has a similar look and feel for all network devices 315, regardless of device type or manufacturer.

[0066] Configuration and reconfiguration of a network device requires that certain attributes be provided to the network device. For different types and manufacturers of devices, these attributes and their formats can vary. DWDM switches, for example, require a wavelength attribute that routers do not. Moreover, one DWDM manufacturer may require the wavelength in a first format, and a second manufacturer may require the same information in a second format. Thus, the global GUI 310 can include both attributes and formatting instructions associated with each of the network devices 315. Good results have been achieved by arranging these attributes and/or formatting instructions in a directory tree 340 such as the one shown in FIG. 9. In this directory tree 340, the attributes and/or formatting instructions for a model A, Cisco™ router can be located by traversing the tree from the root to the router node to the Cisco™ node to the Model A leaf. The appropriate attributes and/or formatting instructions can be located from the Model A leaf.

[0067] To populate the attribute fields, the global GUI 310 could prompt the network administrator 110 for the necessary information. Once the global GUI 310 has acquired the necessary information, the information can be properly formatted—in accordance with the formatting instructions—and passed to the appropriate network device. In the presently preferred embodiment, the global GUI 310 formats the attribute data for a particular network device into a frame that includes a header portion and a payload portion. The header portion can include routing instructions in various formats including HTTP, and the payload portion can include the attribute data in various formats including XML. Additionally, the attribute data can be ordered within the payload according to the formatting instructions. When a network device receives a frame from the global GUI, it can extract the attribute data from the payload and use that data as if it had been received through the network device's own interface. Notably, the frame can be stored on virtually any computer media and/or can exist as an electronically altered signal—collectively referred to as a “computer program product.” (A “computer program product” refers to any media that may be used to provide programming instructions or data to an electronic system. A computer program product includes, but is not limited to, any memory device (whether fixed or removable), any storage medium, and/or any electronically altered signals that carry data.)

[0068] By using the present invention, a network administrator 110 need only learn to navigate the global GUI 310 and not the individual GUIs for the various network devices. Because the present invention allows network devices 315 to be configured and reconfigured without regard to their type or manufacturer, network administrators 110 will be able to add network devices to their network even when they are otherwise unfamiliar with the means for communicating with that type/brand of device. Additionally, the present invention will increase competition in the network device market because new device manufactures will be able to enter the market without first training network administrators to use their products. Moreover, the present invention will reduce network provider costs because fewer specialized administrators will be needed to communicate with the various types of devices.

[0069] Although the global GUI 310 can be operated independently of the network manager unit 140 (shown in FIG. 2), good results are expected when the two components are integrated. For example, the global GUI 310 could be used to alter the centrally stored configuration record for a network device. In fact, the templates used by the global GUI 310 can be associated with or even integrated with the configuration records stored in the directory 165 (shown in FIG. 3) of the network manager unit. For example, the data pointer 225 (shown in FIG. 5) could point to a corresponding template in the global GUI 310.

[0070] The information stored in a configuration record 205 can be used to populate the attribute fields for a network device's template. In other words, the network manager unit 140 (shown in FIG. 5) could retrieve the template for a particular network device, populate the attribute fields of that retrieved template with information from the device's configuration record, format the attribute fields into a frame and pass that frame to the network device. This frame, in some embodiments, constitutes the device-specific commands required to configure the network device.

[0071] In conclusion, the present system provides, among other things, a method and apparatus to configure, monitor and manage network devices without regard for device type and/or manufacturer. Those skilled in the art, however, 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 defining a policy enabled network, the method comprising:

creating a network policy which corresponds to a predetermined network configuration state;

creating a business rule which corresponds to a predetermined series of steps required in response to the network policy;

associating the network policy to the business rule such that the network policy, when implemented in the network, adheres to the predetermined series of steps and results in the predetermined network configuration state;

storing the business rule in a data repository;

storing the network policy in the data repository;

storing the predetermined network configuration state in the data repository;

retrieving from a template library, in response to commands being needed to properly configure a particular one of a plurality of network devices in the network to operate in accordance with the predetermined network configuration state, a command-format template for the particular one of the plurality of network devices; and

generating, using the retrieved command-format template, device-specific commands for the particular one of the plurality of network devices.

2. The method of claim 1, further comprising:

applying the device-specific commands to the particular one of the plurality of network devices.

3. The method of claim 1, wherein creating the business rule comprises:

creating a computer programmable object, which reflects a predefined series of steps for implementing the business rule.

4. The method of claim 1, wherein creating the business rule comprises:

creating an XML Document, which reflects a predefined series of steps for implementing the business rule.

5. The method of claim 1, wherein creating the business rule comprises:

creating an XML Schema, which reflects a predefined series of steps for implementing the business rule.

6. The method of claim 2, wherein creating the business rule comprises:

creating a text document, which reflects a predefined series of steps for implementing the business rule.

7. The method of claim 1, wherein creating the network policy comprises:

creating a computer programmable object, which reflects the predefined network configuration state required for correctly implementing the network policy.

8. The method of claim 1, wherein creating the network policy comprises:

creating an XML document, which reflects the predefined network configuration state for correctly implementing the network policy.

9. The method of claim 1, wherein creating the network policy comprises:

creating an XML schema, which reflects the predefined network configuration state for correctly implementing the network policy.

10. The method of claim 1, wherein creating the network policy comprises:

creating a text document which reflects the predefined network configuration state for correctly implementing a network policy.

11. The method of claim 1, wherein associating the business rule to the network policy comprises:

creating a computer programmable object which defines the association of the business rule to network policy.

12. The method of claim 1, wherein associating the business rule to the network policy comprises:

creating an XML document which defines the association of the business rule to the network policy.

13. The method of claim 1, wherein associating the business rule to the network policy comprises:

creating an XML schema which defines options for associating the business rule and the network policy.

14. The method of claim 1, wherein associating the business rule to the network policy comprises:

creating a text document which defines steps for associating the business rule and network policy.

15. A process for implementing a policy enabled network comprising:

receiving a request to implement a desired network policy;

querying a data repository used to store required business rules;

querying a data repository used to store predefined network configurations;

determining a plurality of network devices to which to apply the predefined network configurations to implement the desired network policy; and

applying the predefined network configurations to the plurality of network devices in an order and as defined in the business rules, wherein applying the predefined network configurations further comprises:

retrieving from a template library, in response to commands being needed to properly configure a particular one of the plurality of network devices to operate in accordance with the predetermined network configuration, a command-format template for the particular one of the plurality of network devices; and

generating, using the retrieved command-format template, device-specific commands for the particular one of the plurality of network devices.

16. The process of claim 15 including:

receiving a network notification from a network device when applying the predefined network configurations;

checking the status of a current network policy by consulting a network policy server, retrieving a policy associated with the network notification and, as required, implementing the desired network policy.

17. The process of claim 16 including:

notifying a selected one of a network administrator, a system, and a customer upon completion of implementing the desired network policy.

18. The process of claim 15, wherein the request originates from a selected one of a network administrator, a system, and a customer.

Patent Citations (250)

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
US5506966(A)	1996-04-01	Ban	Applicant
US5519704(A)	1996-05-01	Farinacci et al.	Applicant
US5535335(A)	1996-07-01	Cox	Applicant
US5557748(A)	1996-09-01	Norris	Applicant
US5581764(A)	1996-12-01	Fitzgerald et al.	Applicant
US5659746(A)	1997-08-01	Bankert	Applicant
US5680551(A)	1997-10-01	Martin	Applicant
US5724509(A)	1998-03-01	Starkweather et al.	Applicant
US5726883(A)	1998-03-01	Levine et al.	Applicant
US5751965(A)	1998-05-01	Mayo	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
US5812768(A)	1998-09-01	Page	Applicant
US5819028(A)	1998-10-01	Manghirmalani et al.	Applicant
US5819042(A)	1998-10-01	Hansen	Applicant
US5832503(A)	1998-11-01	Malik et al.	Examiner
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
US5878432(A)	1999-03-01	Misheski	Applicant
US5884028(A)	1999-03-01	Kindell et al.	Applicant
US5889943(A)	1999-03-01	Ji	Applicant
US5889953(A)	1999-03-01	Thebaut et al.	Applicant
US5901320(A)	1999-05-01	Takahashi	Applicant
US5920701(A)	1999-07-01	Miller et al.	Applicant
US5923850(A)	1999-07-01	Barroux	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
US5999948(A)	1999-12-01	Nelson	Applicant
US6006035(A)	1999-12-01	Nabahi	Applicant
US6014697(A)	2000-01-01	Lewis	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
US6085253(A)	2000-07-01	Blackwell	Applicant
US6088804(A)	2000-07-01	Hill	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
US6173312(B1)	2001-01-01	Atarashi	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
US6211877(B1)	2001-04-01	Steele	Applicant
US6226654(B1)	2001-05-01	Van Hoff	Applicant
US6240458(B1)	2001-05-01	Gilbertson	Applicant
US6243747(B1)	2001-06-01	Lewis et al.	Applicant
US6243815(B1)	2001-06-01	Antur	Applicant
US6247049(B1)	2001-06-01	Scott	Applicant
US6253240(B1)	2001-06-01	Axberg	Applicant
US6260072(B1)	2001-07-01	Rodriguez-Moral	Applicant
US6269398(B1)	2001-07-01	Leong et al.	Applicant
US6272526(B1)	2001-08-01	Robinson	Applicant
US6286038(B1)	2001-09-01	Reichmeyer	Applicant
US6292889(B1)	2001-09-01	Fitzgerald et al.	Applicant
US6338149(B1)	2002-01-01	Ciccone	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
US6363421(B2)	2002-03-01	Barker	Applicant
US6370119(B1)	2002-04-01	Basso et al.	Applicant
US6374293(B1)	2002-04-01	Dev	Applicant
US6381631(B1)	2002-04-01	Van Hoff	Applicant
US6393425(B1)	2002-05-01	Kelly	Applicant
US7065946(B2)	2002-06-01	Tindal et al.	Applicant
US6418468(B1)	2002-07-01	Ahlstrom et al.	Applicant
US6426959(B1)	2002-07-01	Jacobson	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
US6449646(B1)	2002-09-01	Sikora	Applicant
US6453255(B1)	2002-09-01	Smorodinsky	Applicant
US6463470(B1)	2002-10-01	Mohaban et al.	Examiner
US6463583(B1)	2002-10-01	Hammond	Applicant
US6466580(B1)	2002-10-01	Leung	Applicant
US6470453(B1)	2002-10-01	Vilhuber	Applicant
US6473775(B1)	2002-10-01	Kusters	Applicant
US6487594(B1)	2002-11-01	Bahlmann	Examiner
US6496843(B1)	2002-12-01	Getchius et al.	Applicant
US6496858(B1)	2002-12-01	Frailong	Applicant
US6502131(B1)	2002-12-01	Vaid et al.	Examiner
US6539425(B1)	2003-03-01	Stevens et al.	Applicant
US6546416(B1)	2003-04-01	Kirsch	Applicant
US6550060(B1)	2003-04-01	Hammond	Applicant
US6564056(B1)	2003-05-01	Fitzgerald	Applicant
US6567406(B1)	2003-05-01	Skemer	Applicant
US6571285(B1)	2003-05-01	Groath	Applicant
US6598177(B1)	2003-07-01	Jones	Applicant
US6609108(B1)	2003-08-01	Pulliam et al.	Examiner
US6615166(B1)	2003-09-01	Guheen et al.	Applicant
US6615218(B2)	2003-09-01	Mandal	Applicant
US6625590(B1)	2003-09-01	Chen et al.	Applicant
US6628304(B2)	2003-09-01	Mitchell	Applicant
US6636877(B1)	2003-10-01	Doleac et al.	Applicant
US6643289(B1)	2003-11-01	Natanson	Applicant
US6643640(B1)	2003-11-01	Getchius et al.	Applicant
US6651191(B1)	2003-11-01	Vacante et al.	Examiner
US6654799(B1)	2003-11-01	Tanaka	Applicant
US6658526(B2)	2003-12-01	Nguyen et al.	Applicant
US6678370(B1)	2004-01-01	Freebersyser	Applicant
US6678827(B1)	2004-01-01	Rothermel et al.	Applicant
US6684241(B1)	2004-01-01	Sandick	Applicant
US6684244(B1)	2004-01-01	Goldman et al.	Applicant
US6697967(B1)	2004-02-01	Robertson	Applicant
US6725233(B2)	2004-04-01	Froyd et al.	Applicant
US6725262(B1)	2004-04-01	Choquier	Applicant
US6725264(B1)	2004-04-01	Christy	Applicant
US6732175(B1)	2004-05-01	Abjanic	Applicant
US6738910(B1)	2004-05-01	Genty	Applicant
US6760761(B1)	2004-07-01	Sciacca	Applicant
US6760767(B1)	2004-07-01	Miesbauer	Applicant
US6766369(B1)	2004-07-01	Haitsuka	Applicant
US6769116(B1)	2004-07-01	Sexton	Applicant
US6772206(B1)	2004-08-01	Lowry	Applicant
US6775698(B1)	2004-08-01	Simone	Applicant
US6782474(B1)	2004-08-01	Ylonen	Applicant
US6810427(B1)	2004-10-01	Cain	Applicant
US6816897(B2)	2004-11-01	McGuire	Applicant
US6826597(B1)	2004-11-01	Lonnroth et al.	Applicant
US6832247(B1)	2004-12-01	Cochran	Applicant
US6834298(B1)	2004-12-01	Singer	Applicant
US6847994(B1)	2005-01-01	Akimoto	Applicant
US6865673(B1)	2005-03-01	Nessett et al.	Applicant
US6895431(B1)	2005-05-01	Bero	Applicant
US6895588(B1)	2005-05-01	Ruberg	Applicant
US6907572(B2)	2005-06-01	Little	Applicant
US6931016(B1)	2005-08-01	Andersson	Applicant
US6931444(B2)	2005-08-01	Schweitzer	Applicant
US6938079(B1)	2005-08-01	Anderson	Applicant
US6959332(B1)	2005-10-01	Zavalkovsky	Applicant
US6978301(B2)	2005-12-01	Tindal	Examiner
US6990591(B1)	2006-01-01	Pearson	Applicant
US7003560(B1)	2006-02-01	Mullen	Applicant
US7016955(B2)	2006-03-01	Martin	Applicant
US7072934(B2)	2006-07-01	Helgeson et al.	Examiner
US7127526(B1)	2006-10-01	Duncan	Applicant
US7145871(B2)	2006-12-01	Levy	Applicant
US7200548(B2)	2007-04-01	Courtney	Applicant
US7246162(B2)	2007-07-01	Tindal	Applicant
US7246163(B2)	2007-07-01	Tindal	Applicant
US7249170(B2)	2007-07-01	Tindal et al.	Applicant
US7284042(B2)	2007-10-01	Beadles et al.	Examiner
US2001/0034771(A1)	2001-10-01	Hutsch	Applicant
US2001/0053991(A1)	2001-12-01	Bonabeau	Applicant
US2002/0007411(A1)	2002-01-01	Shaked	Applicant
US2002/0032769(A1)	2002-03-01	Barkai et al.	Applicant
US2002/0032775(A1)	2002-03-01	Venkataramaiah	Applicant
US2002/0032871(A1)	2002-03-01	Malan	Applicant
US2002/0038320(A1)	2002-03-01	Brook	Applicant
US2002/0051080(A1)	2002-05-01	Tanaka	Applicant
US2002/0052719(A1)	2002-05-01	Alexander	Applicant
US2002/0069143(A1)	2002-06-01	Cepeda	Applicant
US2002/0069271(A1)	2002-06-01	Tindal et al.	Applicant
US2002/0069340(A1)	2002-06-01	Tindal et al.	Applicant
US2002/0069367(A1)	2002-06-01	Tindal et al.	Applicant
US2002/0072956(A1)	2002-06-01	Willems	Applicant
US2002/0078068(A1)	2002-06-01	Krishnaprasad	Applicant
US2002/0078382(A1)	2002-06-01	Sheikh	Applicant
US2002/0143927(A1)	2002-10-01	Maltz	Applicant
US2002/0161863(A1)	2002-10-01	McGuire	Applicant
US2002/0169858(A1)	2002-11-01	Bellinger	Applicant
US2002/0171762(A1)	2002-11-01	Maxson et al.	Applicant
US2002/0173997(A1)	2002-11-01	Menard	Applicant
US2002/0174091(A1)	2002-11-01	Froyd et al.	Applicant
US2002/0191619(A1)	2002-12-01	Shafer	Applicant
US2002/0194289(A1)	2002-12-01	Engel	Applicant
US2002/0198974(A1)	2002-12-01	Shafer	Applicant
US2003/0016685(A1)	2003-01-01	Berggreen	Applicant
US2003/0018702(A1)	2003-01-01	Broughton	Applicant
US2003/0018765(A1)	2003-01-01	Muhlestein	Applicant
US2003/0033589(A1)	2003-02-01	Reyna et al.	Applicant
US2003/0037040(A1)	2003-02-01	Beadles et al.	Applicant
US2003/0048287(A1)	2003-03-01	Little et al.	Applicant
US2003/0051008(A1)	2003-03-01	Gorthy	Applicant
US2003/0061312(A1)	2003-03-01	Bodner	Applicant
US2003/0065919(A1)	2003-04-01	Albert	Applicant
US2003/0084009(A1)	2003-05-01	Bigus	Applicant
US2003/0135508(A1)	2003-07-01	Chorafakis et al.	Applicant
US2003/0135547(A1)	2003-07-01	Kent	Applicant
US2003/0158894(A1)	2003-08-01	Ziserman	Applicant
US2003/0187964(A1)	2003-10-01	Sage	Applicant
US2003/0200459(A1)	2003-10-01	Seeman	Applicant
US2004/0001493(A1)	2004-01-01	Cloonan	Applicant
US2004/0015592(A1)	2004-01-01	Selgas	Applicant
US2004/0024736(A1)	2004-02-01	Sakamoto	Applicant
US2004/0078695(A1)	2004-04-01	Bowers et al.	Applicant
US2004/0225865(A1)	2004-11-01	Cox et al.	Applicant
EP384339(A2)	1990-08-01		Applicant
EP745929(A1)	1996-12-01		Applicant
EP810755(A2)	1997-12-01		Applicant
EP762281(A3)	1999-03-01		Applicant
EP952521(A2)	1999-10-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
JP8139757(A)	1996-05-01		Applicant
WO95/08794	1995-03-01		Applicant
WO95/24802(A)	1995-09-01		Applicant
WO97/49214	1997-12-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 (59)

Managing Managed Network Services: The Service Provider Blink 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 Profling; 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
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
Torrent 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 Commamication Networks” IEEE Network, IEEE Inc. New York, US, vol. 9, No. 4, Jul. 1, 1995 (Jul. 1, 1995), pp. 46-55, XP000525591, 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
Wolfson, 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
Lonvick, C. The BSD syslog Protocol. RFC 3164 [online], Aug. 2001 (retrieved on Mar. 25, 2002). Retrieved from the Internet, <ietf.org/rfc/rfc3164.txt>.Applicant
Case, J., A Simple Network Management Protocol (SNMP). RFC 1098 [online], Apr. 1989 [retrieved on Mar. 26, 2002]. Retrieved from the internet <ietf.org/rfc/rfc1098.txt?number=1098>.Applicant
Postel, J.B. Simple Mail Transfer Protocol, RFC 821 [online], Aug. 1982 [retrieved on Mar. 26, 2002]. Retrieved from the Internet <ietf.org/rfc/rfc0821.xtx?number<821>.Applicant
Finseth, C. An Access Control Protocol, Sometimes called TACACS. RFC 1492 [online], Jul. 1993 [retrieved on Mar. 25, 2002]. Retrieved from the Internet <cis.ohio-state.edu/egi/bin/rfc/rfc1492.html>.Applicant
Anderson, B.A. TACACS User Identification Telnet Option. RFC 927 [online], Dec. 1984 [retrieved on Mar. 25, 2002]. Retrieved from the Internet<ieft.org/rfc/rfc0927.txt>.Applicant
Rigney, C., et al. Remote Authentication Dial in User Service (RADIUS). RFC 2138 [online], Apr. 1997 {retrieved on Mar. 25, 2002}. Retrieved from the Internet <ietf.org/rfc/rfc2138.txl>.Applicant
Rigney, C., RADIUS Accounting. RFC 2139 [online], Apr. 1997 [retrieved on Mar. 25, 2002]. Retrieved from the Internet <ietf.org/rfc/rfc2139.txt>.Applicant
Postel, J., and Reynolds, J. Telnet Protocol Specification. RFC 854 [online], May 1983 [retrieved on Mar. 25, 2002]. Retrieved from the Internet <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,” simple-times.org./pub/simple-times/issues/8-1.html., pp. 7-27.Applicant
Waldbusser, ST., et al., “Policy Based Management MIB,” ietf.org/internet/drafts/draft-ietf/snmpconf-pm-05.txt, pp. 1-102.Applicant
Strassner, J., A New Paradigm for Network Management: Business Deriven Device Management,[online], 2002, ssgrr.it/en/ssgrr2002s/papers.htm, http://www.ssgrr.it/en/ssgrr2002s/papers/t62/pdf.Applicant
NOMS, IEEE 1992 Network Operations and Management Symposium, 1992, vol. 1, IEEE Communications Society, NewYork, USA.Applicant
HP OpenView for Windows Workgroup Node Manager User Guide, 3COM, Jan. 1997, Part No. 09-1114-000, Hewlett-Packard Co., Santa Clara, CA USA.Applicant
Adminstrator's Guide, Formulator 3.0, 2000-2002, Gold Wire Technology Inc.Applicant
User Guide Formulator 1.0, 2000-2001, Gold Wire Technology Inc.Applicant
Superstack II Hub TR Network Management Module Installation Guide, 3COM Jan 1997, Hewlett-Packard Co., Santa Clara, CA USA.Applicant
Initially Configuring the ATM Switch Router, Cisco, Oct. 19, 2000, pp. 1-42.Applicant
Common Information Model—A Developer's Perspecti ve, IEEE, 1998, p. 1.Applicant
Liu, Stephen, Cisco IOS Command Line Interface Tutorial, 1997, Small/Medium Business Solutions, .com/warp/cpropub/45/tutorial.htm.Applicant
Yeong et al., Lightweight Directory Access Protocol, RFC 1487, Jul. 1993.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
Strassner, John; Technology Series—Directory Enabled Networks, 1999; MacMillan Technical Publishing USA.Applicant
Lonvick, C. The BSD syslog Protocol. RFC 3164 [online], Aug. 2001 [retrieved on Mar. 25, 2002]. Retrieved from the Internet, ://www.ietf.org/rfc/rfc3164.txt>.Applicant
Case, J., A Simple Network Management Protocol (SNMP). RFC 1098 [online], Apr. 1989 [retrieved on Mar. 26, 2002]. Retrieved from the internet <.ietf.org/rfc/rfc1098.txt?number=1098>.Applicant
Postel, J.B. Simple Mail Transfer Protocol. RFC 821 [online], Aug. 1982 [retrieved on Mar. 26, 2002]. Retrieved from the Internet .ietf.org/rfc/rfc0821.txt?number=821>.Applicant
Finseth, C. An Access Control Protocol, Sometimes caleld TACACS. RFC 1492 [online], Jul. 1993 [retrieved on Mar. 25, 2002]. Retrieved from the Internet .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 Mar. 25, 2002]. Retreived from the Internet <.ietf.org/rfc/rfc0927.txt>.Applicant
Rigney, C., et al. Remote Authentication Dial In User Service (RADIUS). RFC 2138 [online], Apr. 1997 {retrieved on Mar. 25, 2002]. Retrieved from the Internet <.ietf.org/rfc/rfc2138.txt>.Applicant
Rigney, C., RADIUS Accounting. RFC 2139 [online], Apr. 1997 [retrieved on Mar. 25, 2002]. Retrieved from the Internet <.ietf.org/rfc/rfc2139.txt>.Applicant
Postel, J., and Reynolds, J. Telnet Protocol Specification. RFC 854 [online], May 1983 [retrieved on Mar. 25, 2002]. Retrieved from the Internet <.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,” .simple-times.org./pub/simple-times/issues/8-1.html., pp. 7-27.Applicant
Waldbusser, ST., et al., “Policy Based Management MIB,” .ietf.org/internet-drafts/draft-ietf-snmpconf-pm-05.txt, pp. 1-102.Applicant
Strassner, J., A New Paradigm for Network Management: Business Deriven Device Management, [online], 2002, .ssgrr.it/en/ssgrr2002s/papers.htm, http://www.ssgrr.it/en/ssgrr2002s/papers/162.pdf.Applicant

Abstract

Description

Priority

Related Applications

[0002] The following commonly owned and assigned patent applications are hereby incorporated by reference in their entirety:

[0003] patent application Ser. No. 09/730,864, entitled System and Method for Configuration, Management and Monitoring of Network Resources, filed on Dec. 6, 2000;
[0004] patent application Ser. No. 09/730,680, entitled System and Method for Redirecting Data Generated by Network Devices, filed on Dec. 6, 2000;
[0005] patent application Ser. No. 09/730,863, entitled Event Manager for Network Operating System, filed on Dec. 6, 2000;
[0006] patent application Ser. No. 09/730,671, entitled Dynamic Configuration of Network Devices to Enable Data Transfers, filed on Dec. 6, 2000; and
[0007] patent application Ser. No. 09/730,682, entitled Network Operating System Data Directory, filed on Dec. 6, 2000.
[0008] patent application Ser. No. 11/763,934, entitled SYSTEM AND METHOD FOR CONFIGURING A NETWORK DEVICE, filed herewith, which is incorporated herein by reference.