US20070150561A1 - System and method for verifying a network device's configuration - Google Patents

System and method for verifying a network device's configuration Download PDF

Info

Publication number
US20070150561A1
US20070150561A1 US11/675,727 US67572707A US2007150561A1 US 20070150561 A1 US20070150561 A1 US 20070150561A1 US 67572707 A US67572707 A US 67572707A US 2007150561 A1 US2007150561 A1 US 2007150561A1
Authority
US
United States
Prior art keywords
configuration
retrieved
network device
xml
vendor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/675,727
Inventor
Mike Courtney
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intelliden Inc
Original Assignee
Intelliden Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intelliden Inc filed Critical Intelliden Inc
Priority to US11/675,727 priority Critical patent/US20070150561A1/en
Assigned to INTELLIDEN, INC. reassignment INTELLIDEN, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COURTNEY, MIKE
Publication of US20070150561A1 publication Critical patent/US20070150561A1/en
Assigned to VOS, REMKO, LALUDE, AKINYEMI O., GRANITE GLOBAL VENTURES II L.P., KOOKABURRA LLC, MICHAEL J. ROWNY REVOCABLE TRUST UTA, WESTBURY EQUITY PARTNERS SBIC, L.P., GERDELMAN, SUE & JOHN, MATRIX VI PARALLEL PARTNERSHIP-B, L.P., BLACK FAMILY TRUST 2001 U/I DTD, GGV II ENTREPRENEURES FUND L.P., WESTON & CO. VI, LLC, GAFFNEY, ROBERT P., SCHNEIDER, JAMES M., MATRIX VI PARALLEL PARTNERSHIP-A, L.P., MATRIX PARTNERS VI, L.P., SNOWS HILL, LLC, SUE GERDELMAN & JOHN GERDELMAN TTEE REVOC. TRUST OF JOHN WILLIAM GERDELMAN, BOYNTON FAMILY TRUST BY CHARLES BOYNTON reassignment VOS, REMKO SECURITY AGREEMENT Assignors: INTELLIDEN, INC.
Assigned to INTELLIDEN, INC. reassignment INTELLIDEN, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: AKINYEMI O. LAIUDE, BLACK FAMILY TRUST 2001 U/I DTD NOVEMBER 26, 2001, BOYNTON FAMILY TRUST, DALE HECHT, GGV II ENTREPRENEURS FUND L.P., GRANITE GLOBAL VENTURES II L.P., JAMES M. SCHNEIDER, MATRIX PARTNERS VI, L.P., MATRIX VI PARALLEL PARTNERSHIP-A, L.P., MATRIX VI PARALLEL PARTNERSHIP-B, L.P., MICHAEL J. ROWNY REVOCABLE TRUST UTA 6/6/95, REMKO VOS, ROBERT GAFFNEY, SNOWS HILL, LLC, SUE GERDELMAN & JOHN GERDELMAN, SUE GERDELMAN & JOHN GERDELMAN TTEE REVOC. TRUST OF JOHN WILLIAM GERDELMAN, W CAPITAL PARTNERS II, L.P., WESTBURY EQUITY PARTNERS SBIC, L.P., WESTON & CO. VI, LLC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0246Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0266Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0866Checking the configuration
    • H04L41/0869Validating the configuration within one network element
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/328Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the presentation layer [OSI layer 6]

Definitions

  • the present invention relates to network device configuration.
  • the present invention relates to systems and methods for retrieving configurations from network devices and generating corresponding command models.
  • Networks and in particular, the Internet, have revolutionized communications. Data vital to the continued citizenship of the world economy is constantly being exchanged between end-users over these networks. Unfortunately, the expansion and maintenance of present networks is outpaced by the demand for additional bandwidth. Network equipment is often difficult to configure, and qualified network engineers are in extremely short supply. Thus, many needed network expansions and upgrades must be delayed until these engineers are available. While these upgrades and expansions are pending, end-users continue to suffer poor network performance.
  • CiscoTM routers are notoriously difficult to configure—especially in light of the new XML-based interfaces introduced by competitors such as Juniper NetworksTM. Instead of a user-friendly XML-based interface, CiscoTM uses a cumbersome command line interface (CLI) for its routers.
  • CLI command line interface
  • Cisco'sTM CLI 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. This cumbersome interface is one reason that CiscoTM requires that Cisco-certified engineers work on its routers.
  • CiscoTM could reduce the complexity of its routers and reduce the need for Cisco-certified engineers by producing a user-friendly interface. If CiscoTM attempted to abandon its CLI in favor of such a user-friendly interface, however, many years of development and expertise could be lost. Moreover, even if it could develop a user-friendly interface, there is presently no economical way to integrate it into the thousands of existing CiscoTM routers. Despite the difficulties in implementing a more user-friendly interface, to remain competitive, CiscoTM and similarly situated companies need to move away from their present interfaces. Present technology, however, does not provide these companies with an acceptable option that allows continued use of their extensive interface knowledge base while simultaneously providing system administrators and network engineers with a user-friendly interface. Moreover, present technologies do not provide an acceptable way to provide backward compatibility of new user-friendly interfaces with existing network devices.
  • CiscoTM of course, is not the only network device manufacturer to face this interface-upgrade problem. Many manufacturers would like to continue using their existing interface knowledge base while providing system administrators a user-friendly, consistent interface. Accordingly, a system and method are needed that will allow manufacturers, like CiscoTM, to create user-friendly interfaces for both next-generation and existing devices.
  • the present invention can provide a system and method for modeling the configuration of a network device.
  • a system could include a CLI-to-XML converter connected to a schema storage device or a CLI-to-XML converter in combination with a document object model (DOM) generator.
  • DOM document object model
  • Other embodiments could include, for example, a CLI-to-XML converter, a schema hash system, and a DOM generator.
  • one embodiment of the present invention can model a network device's configuration by retrieving a the network device's configuration, in a native format, from the network device—or an alternate location—and converting it into a standard-format configuration such as an XML document or a DOM.
  • This standard-format configuration provides system administrators with an easy-to-use, familiar device configuration format for different network devices. That is, instead of being forced to manipulate a difficult CLI-based configuration format, or other format system administrators can use the standard-format configuration to interact with the target network device.
  • one embodiment of the present invention can allow system administrators to use the same standard configuration format across multiple brands and models of network devices. Thus, in networks that employ multiple brands and models of network devices, system administrators can be presented with similar configuration formats for each device despite the fact that the native configuration formats for the different devices are significantly different.
  • the process for actually converting a native-format configuration for a network device into a standard-format configuration is generally a multi-step process.
  • one embodiment of the present invention initially determines the target network device's characteristics such as manufacturer, model, operating system version, etc.
  • an appropriate configuration schema can be retrieved from a schema storage device.
  • the schema can include a standard representation of the command structure for a particular type of network device.
  • one schema could contain a representation of the command structure for all model 7500 CiscoTM routers using OS version 12.1, and another schema could contain a representation of the command structure routers using OS version 12.2.
  • the schema, its creation, and its use are fully described in commonly owned and assigned U.S. patent application Ser. No. 09/942,834, Attorney Docket No. CNTW-007/US, entitled System and Method for Generating a Configuration Schema, which is incorporated herein by reference.
  • this schema can be directly used to generate an XML document that represents the configuration of the particular network device.
  • an intermediate representation e.g., a hash representation
  • the intermediate representation is used to more quickly generate the corresponding XML document.
  • one embodiment of the present invention generates an XML representation of each native-format command in the network device's configuration by associating each command with the schema, or its hash representation.
  • the XML document itself can be used to represent the standard-format configuration, or alternatively, the XML document can be converted into a DOM, and the DOM can represent the standard-format configuration.
  • the integrity of the generated DOM can be verified via the schema that was used to generate the XML document, thereby providing a “closed-loop” capability.
  • FIG. 1 is a block diagram of a conventional network
  • FIG. 2 is a block diagram of a conventional router
  • FIG. 3 is a block diagram of one embodiment of a system constructed in accordance with the principles of the present invention.
  • FIG. 4 is a block diagram of an alternate embodiment of a system constructed in accordance with the principles of the present invention.
  • FIG. 5 is a block diagram of one implementation of the DOM generator shown in FIG. 3 ;
  • FIG. 6 is a flowchart of one method for operating the DOM generator shown in FIG. 5 ;
  • FIG. 7 is a flowchart of one method for generating an intermediate representation described with relation to FIG. 6 .
  • FIG. 1 it illustrates a block diagram of a conventional 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 .
  • networking equipment such as hubs, not shown, optical components 115 , and routers 120 .
  • end-users 105 that are associated with different servers 110 can exchange data.
  • the routers 120 and/or optical components 115 of the network system 100 may need reconfiguring.
  • 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.
  • FIG. 2 it is a block diagram of one type of conventional router.
  • 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 .
  • OS operating system
  • 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.
  • 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 . If necessary, the system administrator 125 can review available configuration commands and associated bounds 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 often unique to the particular OS version stored in the OS module 135 .
  • the configuration interface 130 could be XML based.
  • the XML-based interface is easier to navigate than a CLI, each network device manufacturer that uses an XML-based interface generally structures its interface in a proprietary fashion. Thus, network engineers are still forced to learn many different interfaces and command structures even for XML-based network devices.
  • FIG. 3 it is a block diagram of one embodiment of a system constructed in accordance with the principles of the present invention.
  • a DOM generator 160 which is more fully described with relation to FIG. 5 , is connected to a network device 165 , a schema storage device 170 , a system administrator 175 , a DOM storage device 180 , and various DOM applications 185 , which will be discussed in more detail below.
  • the system administrator 175 initially notifies the DOM generator 160 to model the configuration for the network device 165 .
  • the DOM generator 160 is instructed to convert the active command format for the network device 165 into an XML and/or DOM format.
  • the DOM generator 160 either polls the network device 165 to discover the device's characteristics, e.g., manufacturer, model, operating system version, etc., or retrieves the information from a database (not shown).
  • the DOM generator 160 identifies and retrieves, from the schema storage device 170 , the schema corresponding to the device characteristics for the network device 165 .
  • the DOM generator 160 then retrieves the configuration from the network device 165 and, using the retrieved schema, converts the individual commands of the configuration into a DOM.
  • the resulting DOM can then be stored in the DOM storage device 180 in association with an identifier for the network device 165 .
  • storage devices 170 and 180 could, in fact, be integrated into a single device.
  • DOM format provides a standard format for most network device configurations.
  • applications that use or manipulate network device configurations must be customized for each manufacturer, each model, and each OS version. This type of customization often requires many different versions of the same application.
  • By converting each network device's configuration into a DOM format however, applications can be designed to utilize a single, standard configuration format and thereby limit the need for customizations.
  • GUI DOM-based graphical user interface
  • the hashed schema and/or the resulting DOM instance are used to drive the GUI used by the system administrator 175 .
  • the advantage of such a GUI 190 is that the system administrator 175 is presented with network device configurations in a standard, consistent format regardless of the characteristics of the particular network device.
  • the XML-XML converter 195 also called the standard XML-to-native XML converter.
  • some network devices include XML-based interfaces. However, these XML-based interfaces are generally based on proprietary (native) configuration instructions. Thus, the system administrator 175 may interface with one XML-based network device in a very different way than another XML-based network device.
  • the XML-XML converter converts a standard XML-based instruction into a native XML-based instruction. In other words, the XML-XML converter allows the system administrator 175 to use the same XML-based command format for most network devices even though each device may require its own native XML-based command format.
  • the XML-CLI converter 200 allows the system administrator 175 to interface with CLI-based network devices using a standard XML-based command format instead of a CLI-based command format.
  • Other DOM-based applications may include lightweight directory access protocol (LDAP) for storing and manipulating schema, hash representations, and device configuration commands.
  • LDAP lightweight directory access protocol
  • These converters convert XML-based configurations into a LDAP-based configuration and LDAP-based configurations into XML-based configurations.
  • Yet another possible DOM application is the comparator 210 , which is configurable to identify the differences between two DOMs. For example, if the configuration for a target network device were changed, the new configuration could be retrieved from the device and converted to a DOM. The comparator 210 could then compare the new DOM against the original DOM to thereby identify any changes, additions, and/or deletions. The comparator can then record these changes in a markup DOM using a configuration change markup language and make the markup DOM available to the system administrator for configuration and validation purposes.
  • the old DOM is compared against a draft DOM instead of a new DOM.
  • the system administrator 175 generates a draft configuration for a target network device 165 .
  • This draft configuration is converted into a DOM, and the comparator 210 compares it against the target network device's original DOM.
  • the system administrator 175 can use this embodiment of the comparator to view the configuration changes before the draft DOM is finalized and pushed to the target network device 165 .
  • the DOM applications can also include an (API) application programming interface 215 .
  • This API provides a mechanism whereby the DOM can be transferred to/from other software programs, which may reside on network devices. Accordingly, the DOM can be programmatically modified outside of the embodiment and resubmitted.
  • FIG. 4 it is a block diagram of an alternate embodiment of a system 220 constructed in accordance with the principles of the present invention.
  • the DOM generator 160 is connected through a network 225 to the network devices 165 , the system administrator 175 , the schema storage device 170 , and the DOM applications 180 .
  • This embodiment illustrates that the components described herein can be distributed in a number of ways and without impacting the basic operation of this system as described with regard to FIG. 3 .
  • the DOM generator 160 includes a schema hash system 230 , an XML converter 235 , and a DOM transformer 250 . These components can be connected to the schema storage device 170 , the target network device 165 , a DOM storage device 245 and an XML storage device 250 .
  • the XML converter 235 uses the appropriate schema, generates an XML document containing an XML representation of the network device's configuration. This XML document is then passed to the DOM transformer 240 , which converts the XML document into a DOM.
  • the output from the XML converter 235 and/or the DOM transformer 240 can be stored and passed to relevant software applications. For example, the output from the XML converter 235 can be stored in the XML storage device 250 and the output from the DOM transformer 240 can be stored in the DOM storage device 245 .
  • the XML converter 235 of this embodiment can convert the native configuration of the network device 165 into an XML document using an intermediate representation of the schema associated with the network device 165 , such as a hash table generated by the hash system 230 , instead of the schema itself.
  • an intermediate representation of the appropriate schema the XML converter 235 can reduce the time and processing requirements needed to convert a native configuration into a corresponding XML document. The creation and use of the intermediate representation is described more fully with regard to FIG. 6 .
  • the operation of the DOM generator 160 can be further illustrated by reference to the flowchart in FIG. 6 .
  • the DOM generator 160 determines the target network device's characteristics by polling the network device or accessing a database (not shown) containing such information (step 255 ).
  • the XML converter 235 identifies the appropriate intermediate representation for the target network device 165 (step 260 ). As previously described, this intermediate representation provides the necessary data to convert the native-format configuration of the target network device 165 into a standard format such as an XML format.
  • the XML converter 235 retrieves the configuration from the network device 165 and identifies each initial command within each configuration line (steps 265 and 270 ). For example, the XML converter 235 could locate command distinguishing tags embedded in the configuration such as “begin command” and/or “end command.” Alternatively, the XML converter 235 could use logical indicators within the configuration to distinguish the individual commands. Either way, using the identified initial command, the XML converter 235 generates a look-up key that is used to index the hash table, locate a hash map object that corresponds to the look-up key and retrieve that hash map object (steps 275 and 280 ).
  • the hash map object contains schema information regarding the command or value such as whether optional or required data type, etc.
  • the XML converter 235 can assemble the XML-based command and write it to the corresponding XML document (step 295 ).
  • this process should be repeated for each command in the network device's native-format configuration.
  • this process is represented by determining whether any more commands need to be converted (step 300 ). If so, branch 305 is followed to step 270 and a next native-format command is identified. The process for this command is then repeated. If, on the other hand, all native-format commands have been converted, branch 310 is followed and the XML converter 235 assembles all of the generated XML commands into an XML document that can be stored in the XML storage device and/or provided to the DOM transformer 240 (step 315 ).
  • the DOM transformer 240 can verify its transformation process against the appropriate schema stored in the schema storage device 170 (step 325 ).
  • each configuration command in the DOM should have a particular format, which are defined by the configuration schema corresponding to the target network device 165 .
  • the DOM transformer 240 can compare the generated DOM against the corresponding configuration schema to verify that the DOM was properly constructed.
  • a command is initially retrieved from the previously assembled configuration schema (step 328 ). Additionally, any related higher-level commands (called parent commands) in the configuration schema can be retrieved (step 330 ). The retrieved command and the retrieved parent commands can then be used to generate a unique hash key for the retrieved command (step 330 ).
  • a corresponding hash object can also be generated.
  • This hash object can include basic information related to the generated hash key.
  • information such as data type, sibling commands, and application specific information is retrieved and assembled into the schema object (steps 335 and 340 ).
  • the data type information 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.
  • specialized application information can also be retrieved (step 345 ). This application information, for example, can define special processing requirements for a schema.
  • the corresponding schema object can be assembled and the hash map assembled for the unique key and schema object (step 350 and 355 ). If there are any more commands in the schema that need to be modeled, branch 362 is followed and the next command can be retrieved (step 328 ). If all of the commands have been modeled, then branch 364 can be followed and the various hash objects can be stored as a completed hash table (step 365 ).

Abstract

A system and method for verifying the state of a device configuration corresponding to a network device is described. In one embodiment, the method includes determining a desired state of a device, retrieving a device configuration stored in a repository, retrieving another device configuration from the network device, and identifying differences between the device configuration retrieved from the network device with the device configuration retrieved from the repository. A record of the differences is then provided to a system administrator.

Description

    PRIORITY
  • The present application is a continuation application of commonly owned and assigned application Ser. No. 09/942,833, Attorney Docket No. CNTW-008/00US, entitled SYSTEM AND METHOD FOR MODELING A NETWORK DEVICE'S CONFIGURATION, filed on Aug. 29, 2001, which is incorporated herein by reference.
  • RELATED APPLICATIONS
  • The present application is related to commonly owned and assigned application Ser. Nos.:
      • Ser. No. 09/730,864 entitled System and Method for Configuration, Management and Monitoring of Network Resources, filed Dec. 6, 2000;
      • Ser. No. 09/730,680 entitled System and Method for Redirecting Data Generated by Network Devices, filed Dec. 6, 2000;
      • Ser. No. 09/730,863 entitled Event Manager for Network Operating System, filed Dec. 6, 2000;
      • Ser. No. 09/730,671 entitled Dynamic Configuration of Network Devices to Enable Data Transfers, filed Dec. 6, 2000;
      • Ser. No. 09/730,682 entitled Network Operating System Data Directory, filed Dec. 6, 2000; and
      • Ser. No. 09/799,579 entitled Global GUI Interface for Network OS, filed Mar. 6, 2001;
        all of which are incorporated herein by reference.
    FIELD OF THE INVENTION
  • The present invention relates to network device configuration. In particular, but not by way of limitation, the present invention relates to systems and methods for retrieving configurations from network devices and generating corresponding command models.
  • BACKGROUND OF THE INVENTION
  • 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 present networks is outpaced by the demand for additional bandwidth. Network equipment is often difficult to configure, and qualified network engineers are in extremely short supply. Thus, many needed network expansions and upgrades must be delayed until these engineers are available. While these upgrades and expansions are pending, end-users continue to suffer poor network performance.
  • Cisco™ routers, for example, 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 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. This cumbersome interface is one reason that Cisco™ requires that Cisco-certified engineers work on its routers.
  • Cisco™ could reduce the complexity of its routers and reduce the need for Cisco-certified engineers by producing a user-friendly interface. If Cisco™ attempted to abandon its CLI in favor of such a user-friendly interface, however, many years of development and expertise could be lost. Moreover, even if it could develop a user-friendly interface, there is presently no economical way to integrate it into the thousands of existing Cisco™ routers. Despite the difficulties in implementing a more user-friendly interface, to remain competitive, Cisco™ and similarly situated companies need to move away from their present interfaces. Present technology, however, does not provide these companies with an acceptable option that allows continued use of their extensive interface knowledge base while simultaneously providing system administrators and network engineers with a user-friendly interface. Moreover, present technologies do not provide an acceptable way to provide backward compatibility of new user-friendly interfaces with existing network devices.
  • Cisco™, of course, is not the only network device manufacturer to face this interface-upgrade problem. Many manufacturers would like to continue using their existing interface knowledge base while providing system administrators a user-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
  • 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.
  • In one embodiment, for example, the present invention can provide a system and method for modeling the configuration of a network device. Such a system could include a CLI-to-XML converter connected to a schema storage device or a CLI-to-XML converter in combination with a document object model (DOM) generator. Other embodiments could include, for example, a CLI-to-XML converter, a schema hash system, and a DOM generator.
  • In operation, one embodiment of the present invention can model a network device's configuration by retrieving a the network device's configuration, in a native format, from the network device—or an alternate location—and converting it into a standard-format configuration such as an XML document or a DOM. This standard-format configuration provides system administrators with an easy-to-use, familiar device configuration format for different network devices. That is, instead of being forced to manipulate a difficult CLI-based configuration format, or other format system administrators can use the standard-format configuration to interact with the target network device. Moreover, one embodiment of the present invention can allow system administrators to use the same standard configuration format across multiple brands and models of network devices. Thus, in networks that employ multiple brands and models of network devices, system administrators can be presented with similar configuration formats for each device despite the fact that the native configuration formats for the different devices are significantly different.
  • The process for actually converting a native-format configuration for a network device into a standard-format configuration is generally a multi-step process. For example, one embodiment of the present invention initially determines the target network device's characteristics such as manufacturer, model, operating system version, etc. Next, using some or all of this characteristic information, an appropriate configuration schema can be retrieved from a schema storage device. Briefly, the schema can include a standard representation of the command structure for a particular type of network device. For example, one schema could contain a representation of the command structure for all model 7500 Cisco™ routers using OS version 12.1, and another schema could contain a representation of the command structure routers using OS version 12.2. The schema, its creation, and its use are fully described in commonly owned and assigned U.S. patent application Ser. No. 09/942,834, Attorney Docket No. CNTW-007/US, entitled System and Method for Generating a Configuration Schema, which is incorporated herein by reference.
  • In certain embodiments, this schema can be directly used to generate an XML document that represents the configuration of the particular network device. In the presently preferred embodiment, however, an intermediate representation, e.g., a hash representation, of the schema is generated and the intermediate representation is used to more quickly generate the corresponding XML document. By using the intermediate representation, the number of instruction cycles needed to generate the XML document is reduced significantly when compared to generating the XML document directly.
  • To actually assemble an XML document, one embodiment of the present invention generates an XML representation of each native-format command in the network device's configuration by associating each command with the schema, or its hash representation. The XML document itself can be used to represent the standard-format configuration, or alternatively, the XML document can be converted into a DOM, and the DOM can represent the standard-format configuration. Notably, the integrity of the generated DOM can be verified via the schema that was used to generate the XML document, thereby providing a “closed-loop” capability.
  • As previously stated, the above-described embodiments and implementations 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
  • 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:
  • FIG. 1 is a block diagram of a conventional network;
  • FIG. 2 is a block diagram of a conventional router;
  • FIG. 3 is a block diagram of one embodiment of a system constructed in accordance with the principles of the present invention;
  • FIG. 4 is a block diagram of an alternate embodiment of a system constructed in accordance with the principles of the present invention;
  • FIG. 5 is a block diagram of one implementation of the DOM generator shown in FIG. 3;
  • FIG. 6 is a flowchart of one method for operating the DOM generator shown in FIG. 5; and
  • FIG. 7 is a flowchart of one method for generating an intermediate representation described with relation to FIG. 6.
  • DETAILED DESCRIPTION
  • 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 that are associated with different servers 110 can exchange data.
  • 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.
  • Referring now to FIG. 2, it is a block diagram of one type of 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.
  • Still referring to FIG. 2, 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. If necessary, the system administrator 125 can review available configuration commands and associated bounds 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 often unique to the particular OS version stored in the OS module 135.
  • After the system administrator 125 has assembled the new configuration instructions, these instructions are pushed through the configuration interface 130 and stored in the configuration storage module 145. As previously described, 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 engineers for even simple tasks.
  • For other routers, the configuration interface 130 could be XML based. Although the XML-based interface is easier to navigate than a CLI, each network device manufacturer that uses an XML-based interface generally structures its interface in a proprietary fashion. Thus, network engineers are still forced to learn many different interfaces and command structures even for XML-based network devices.
  • Referring now to FIG. 3, it is a block diagram of one embodiment of a system constructed in accordance with the principles of the present invention. In this embodiment, a DOM generator 160, which is more fully described with relation to FIG. 5, is connected to a network device 165, a schema storage device 170, a system administrator 175, a DOM storage device 180, and various DOM applications 185, which will be discussed in more detail below.
  • In one method of operation, the system administrator 175 initially notifies the DOM generator 160 to model the configuration for the network device 165. In other words, the DOM generator 160 is instructed to convert the active command format for the network device 165 into an XML and/or DOM format. In response, the DOM generator 160 either polls the network device 165 to discover the device's characteristics, e.g., manufacturer, model, operating system version, etc., or retrieves the information from a database (not shown). Next, the DOM generator 160 identifies and retrieves, from the schema storage device 170, the schema corresponding to the device characteristics for the network device 165. The DOM generator 160 then retrieves the configuration from the network device 165 and, using the retrieved schema, converts the individual commands of the configuration into a DOM. The resulting DOM can then be stored in the DOM storage device 180 in association with an identifier for the network device 165. Note that storage devices 170 and 180 could, in fact, be integrated into a single device.
  • One advantage of the DOM format is that it provides a standard format for most network device configurations. Generally, applications that use or manipulate network device configurations must be customized for each manufacturer, each model, and each OS version. This type of customization often requires many different versions of the same application. By converting each network device's configuration into a DOM format, however, applications can be designed to utilize a single, standard configuration format and thereby limit the need for customizations.
  • Although many different types of applications can utilize a DOM, a select few are represented in FIG. 3 as DOM applications. For example, one such application is a DOM-based graphical user interface (GUI) 190. In this application, the hashed schema and/or the resulting DOM instance are used to drive the GUI used by the system administrator 175. The advantage of such a GUI 190 is that the system administrator 175 is presented with network device configurations in a standard, consistent format regardless of the characteristics of the particular network device.
  • Another application that utilizes the DOM is the XML-XML converter 195, also called the standard XML-to-native XML converter. As previously described, some network devices include XML-based interfaces. However, these XML-based interfaces are generally based on proprietary (native) configuration instructions. Thus, the system administrator 175 may interface with one XML-based network device in a very different way than another XML-based network device. To standardize the interface between these various XML-based network devices, the XML-XML converter converts a standard XML-based instruction into a native XML-based instruction. In other words, the XML-XML converter allows the system administrator 175 to use the same XML-based command format for most network devices even though each device may require its own native XML-based command format.
  • Like the XML-XML converter 195, the XML-CLI converter 200 allows the system administrator 175 to interface with CLI-based network devices using a standard XML-based command format instead of a CLI-based command format. Other DOM-based applications may include lightweight directory access protocol (LDAP) for storing and manipulating schema, hash representations, and device configuration commands. These converters convert XML-based configurations into a LDAP-based configuration and LDAP-based configurations into XML-based configurations.
  • Yet another possible DOM application is the comparator 210, which is configurable to identify the differences between two DOMs. For example, if the configuration for a target network device were changed, the new configuration could be retrieved from the device and converted to a DOM. The comparator 210 could then compare the new DOM against the original DOM to thereby identify any changes, additions, and/or deletions. The comparator can then record these changes in a markup DOM using a configuration change markup language and make the markup DOM available to the system administrator for configuration and validation purposes.
  • In another embodiment of the comparator 210, the old DOM is compared against a draft DOM instead of a new DOM. In other words, the system administrator 175 generates a draft configuration for a target network device 165. This draft configuration is converted into a DOM, and the comparator 210 compares it against the target network device's original DOM. The system administrator 175 can use this embodiment of the comparator to view the configuration changes before the draft DOM is finalized and pushed to the target network device 165.
  • The DOM applications can also include an (API) application programming interface 215. This API provides a mechanism whereby the DOM can be transferred to/from other software programs, which may reside on network devices. Accordingly, the DOM can be programmatically modified outside of the embodiment and resubmitted.
  • Referring now to FIG. 4, it is a block diagram of an alternate embodiment of a system 220 constructed in accordance with the principles of the present invention. In this embodiment, the DOM generator 160 is connected through a network 225 to the network devices 165, the system administrator 175, the schema storage device 170, and the DOM applications 180. This embodiment illustrates that the components described herein can be distributed in a number of ways and without impacting the basic operation of this system as described with regard to FIG. 3.
  • Referring now to FIG. 5, it is a block diagram of one implementation of the DOM generator 160 shown in FIG. 3. In this embodiment, the DOM generator 160 includes a schema hash system 230, an XML converter 235, and a DOM transformer 250. These components can be connected to the schema storage device 170, the target network device 165, a DOM storage device 245 and an XML storage device 250.
  • In this embodiment, the XML converter 235, using the appropriate schema, generates an XML document containing an XML representation of the network device's configuration. This XML document is then passed to the DOM transformer 240, which converts the XML document into a DOM. The output from the XML converter 235 and/or the DOM transformer 240 can be stored and passed to relevant software applications. For example, the output from the XML converter 235 can be stored in the XML storage device 250 and the output from the DOM transformer 240 can be stored in the DOM storage device 245.
  • Notably, the XML converter 235 of this embodiment can convert the native configuration of the network device 165 into an XML document using an intermediate representation of the schema associated with the network device 165, such as a hash table generated by the hash system 230, instead of the schema itself. By using an intermediate representation of the appropriate schema, the XML converter 235 can reduce the time and processing requirements needed to convert a native configuration into a corresponding XML document. The creation and use of the intermediate representation is described more fully with regard to FIG. 6.
  • The operation of the DOM generator 160 can be further illustrated by reference to the flowchart in FIG. 6. As depicted, the DOM generator 160 determines the target network device's characteristics by polling the network device or accessing a database (not shown) containing such information (step 255). Next, the XML converter 235 identifies the appropriate intermediate representation for the target network device 165 (step 260). As previously described, this intermediate representation provides the necessary data to convert the native-format configuration of the target network device 165 into a standard format such as an XML format.
  • Possibly concurrently with the XML converter 235 identifying the corresponding intermediate representation, the XML converter 235 retrieves the configuration from the network device 165 and identifies each initial command within each configuration line (steps 265 and 270). For example, the XML converter 235 could locate command distinguishing tags embedded in the configuration such as “begin command” and/or “end command.” Alternatively, the XML converter 235 could use logical indicators within the configuration to distinguish the individual commands. Either way, using the identified initial command, the XML converter 235 generates a look-up key that is used to index the hash table, locate a hash map object that corresponds to the look-up key and retrieve that hash map object (steps 275 and 280). The hash map object contains schema information regarding the command or value such as whether optional or required data type, etc. Finally, using this hash map object, the XML converter 235 can assemble the XML-based command and write it to the corresponding XML document (step 295).
  • The above process should be repeated for each command in the network device's native-format configuration. With regard to FIG. 6, this process is represented by determining whether any more commands need to be converted (step 300). If so, branch 305 is followed to step 270 and a next native-format command is identified. The process for this command is then repeated. If, on the other hand, all native-format commands have been converted, branch 310 is followed and the XML converter 235 assembles all of the generated XML commands into an XML document that can be stored in the XML storage device and/or provided to the DOM transformer 240 (step 315).
  • Once the XML document has been assembled, it can be passed to the DOM transformer 240 where a DOM corresponding to the XML document can be generated (step 320). The process for converting an XML document to a DOM is well known in the art and, thus, not described here. Notably, the DOM transformer 240 can verify its transformation process against the appropriate schema stored in the schema storage device 170 (step 325). In other words, each configuration command in the DOM should have a particular format, which are defined by the configuration schema corresponding to the target network device 165. Thus, the DOM transformer 240 can compare the generated DOM against the corresponding configuration schema to verify that the DOM was properly constructed.
  • Referring now to FIG. 7, it is a flowchart of one method for generating an intermediate representation of a configuration schema. In this embodiment, a command is initially retrieved from the previously assembled configuration schema (step 328). Additionally, any related higher-level commands (called parent commands) in the configuration schema can be retrieved (step 330). The retrieved command and the retrieved parent commands can then be used to generate a unique hash key for the retrieved command (step 330).
  • 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 hash object, information such as data type, sibling commands, and application specific information is retrieved and assembled into the schema object (steps 335 and 340). 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 (step 345). This application information, for example, can define special processing requirements for a schema.
  • Once the relevant information has been collected, the corresponding schema object can be assembled and the hash map assembled for the unique key and schema object (step 350 and 355). If there are any more commands in the schema that need to be modeled, branch 362 is followed and the next command can be retrieved (step 328). If all of the commands have been modeled, then branch 364 can be followed and the various hash objects can be stored as a completed hash table (step 365).

Claims (17)

1. A method for verifying the state of a device configuration corresponding to a network device, wherein the device configuration includes a plurality of configuration commands, the method comprising:
determining a desired state of a device;
retrieving a device configuration stored in a repository, wherein the device configuration stored in the repository corresponds to the desired state of the device;
retrieving another device configuration from the network device;
identifying differences between the device configuration retrieved from the network device with the device configuration retrieved from the repository; and
providing a record of the differences to a system administrator.
2. The method of claim 1 including:
converting the device configuration retrieved from the repository into an XML-based format; and
converting the device configuration retrieved from the network device into the XML-based format.
3. The method of claim 2, wherein converting the device configuration retrieved from the network device includes converting the device configuration retrieved from the network device into an XML document or an XML document object model, and wherein converting the device configuration retrieved from the repository includes converting the device configuration retrieved from the repository into an XML document or an XML document object model.
4. The method of claim 1, including:
retrieving the device configuration stored in the repository as a software programmable object; and
converting the device configuration retrieved from the network device into an software programmable object.
5. The method of claim 1 including:
providing the record to an event bus
6. The method of claim 1 including:
providing the record to a policy server.
7. The method of claim 1, wherein providing the record includes providing the record via an application programmable interface.
8. The method of claim 1, wherein providing the record includes providing the record via a document.
9. A method for providing a vendor independent representation of device configurations wherein each of the device configurations include a plurality of configuration commands, the method comprising:
retrieving a device configuration stored in a data repository;
translating the retrieved configuration into a vendor-independent representation of the retrieved configuration;
making the vendor-independent representation of the retrieved configuration available via an applications programmable interface;
retrieving the vendor-independent representation of the retrieved configuration via the application programmable interface;
modifying the vendor-independent representation of the retrieved configuration;
resubmitting the modified vendor-independent representation of the retrieved configuration back to the application programmable interface;
applying a configuration corresponding to the modified vendor-independent representation of the retrieved configuration to a device; and
storing the modified vendor-independent representation of the retrieved configuration.
10. The method of claim 9, wherein the vendor independent representation of the retrieved configuration is an XML document object model.
11. The method of claim 9 wherein the vendor independent representation of the retrieved configuration is a software programmable object.
12. The method of claim 9, wherein the vendor independent representation of the retrieved configuration is an XML document.
13. The method of claim 9, wherein the vendor independent representation of the retrieved configuration is a document.
14. A method for verifying a configuration corresponding to a network device, wherein the configuration includes a plurality of configuration commands, the method comprising:
determining a required configuration of a device wherein the determining the required configuration of a network device comprises:
assessing the network device requirements;
choosing the vendor, type model and operating system needed to fulfill the required assessment;
choosing configuration commands to fulfill the required assessment by consulting a representation of a command structure for the network device;
generating required network device configuration commands;
submitting the required network configuration commands to the network device; and
storing the device configuration.
15. The method of claim 14, wherein the representation of a command structure for the network device is an XML schema.
16. The method of claim 14, wherein the representation of a command structure for the network device is a software programmable object.
17. The method of claim 14, wherein the representation of a command structure for the network device is a document.
US11/675,727 2001-08-29 2007-02-16 System and method for verifying a network device's configuration Abandoned US20070150561A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/675,727 US20070150561A1 (en) 2001-08-29 2007-02-16 System and method for verifying a network device's configuration

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/942,833 US7200548B2 (en) 2001-08-29 2001-08-29 System and method for modeling a network device's configuration
US11/675,727 US20070150561A1 (en) 2001-08-29 2007-02-16 System and method for verifying a network device's configuration

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/942,833 Continuation US7200548B2 (en) 2001-08-29 2001-08-29 System and method for modeling a network device's configuration

Publications (1)

Publication Number Publication Date
US20070150561A1 true US20070150561A1 (en) 2007-06-28

Family

ID=25478663

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/942,833 Expired - Lifetime US7200548B2 (en) 2001-08-29 2001-08-29 System and method for modeling a network device's configuration
US11/675,727 Abandoned US20070150561A1 (en) 2001-08-29 2007-02-16 System and method for verifying a network device's configuration

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/942,833 Expired - Lifetime US7200548B2 (en) 2001-08-29 2001-08-29 System and method for modeling a network device's configuration

Country Status (2)

Country Link
US (2) US7200548B2 (en)
WO (1) WO2003021415A1 (en)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060256813A1 (en) * 2005-05-12 2006-11-16 Verizon Services Corp. Automatic configuration of network devices for network services
US20090228649A1 (en) * 2008-03-10 2009-09-10 Porel Partha P Redundant array of inexpensive disks configuration using simple network management protocol
US20090271510A1 (en) * 2008-04-28 2009-10-29 Microsoft Corporation Network state platform
US20100024031A1 (en) * 2008-07-24 2010-01-28 Sap Portals Israel Ltd System and method for transforming hierarchical objects
US20110010383A1 (en) * 2009-07-07 2011-01-13 Thompson Peter C Systems and methods for streamlining over-the-air and over-the-wire device management
US11075805B1 (en) 2019-04-24 2021-07-27 Juniper Networks, Inc. Business policy management for self-driving network
US11088900B2 (en) 2016-05-24 2021-08-10 Apstra, Inc. Configuring system resources for different reference architectures
US11223512B2 (en) * 2014-11-14 2022-01-11 Apstra, Inc. Configuring a network
US11283691B1 (en) 2020-10-21 2022-03-22 Juniper Networks, Inc. Model driven intent policy conflict detection and resolution through graph analysis
US11323338B2 (en) 2015-12-23 2022-05-03 Apstra, Inc. Verifying service status
US11451451B2 (en) 2017-12-08 2022-09-20 Apstra, Inc. Intent-based analytics
US11567994B2 (en) 2017-01-24 2023-01-31 Apstra, Inc. Configuration, telemetry, and analytics of a computer infrastructure using a graph model
US11570055B2 (en) 2020-11-25 2023-01-31 Apstra, Inc. Connectivity templates
US11677619B2 (en) 2015-06-30 2023-06-13 Apstra, Inc. Selectable declarative requirement levels
US11805024B1 (en) 2019-03-21 2023-10-31 Apstra, Inc. Automatically generating an intent-based network model of an existing computer network

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6978301B2 (en) * 2000-12-06 2005-12-20 Intelliden System and method for configuring a network device
US7353248B1 (en) * 2001-07-30 2008-04-01 At&T Delaware Intellectual Property, Inc. Application server and method to perform hierarchical configurable data validation
US7191209B1 (en) * 2001-07-30 2007-03-13 Bellsouth Intellectual Property Corp. Application server and method to perform hierarchical configurable data manipulation
US7441007B1 (en) 2001-07-30 2008-10-21 At&T Intellectual Property I, L.P. System and method for allowing applications to retrieve properties and configuration information from a persistent store
US7065562B2 (en) * 2001-11-26 2006-06-20 Intelliden, Inc. System and method for generating a representation of a configuration schema
US7783733B1 (en) 2002-04-26 2010-08-24 Extreme Networks, Inc. Method and apparatus for dynamic configuration management
US7689678B2 (en) * 2002-04-26 2010-03-30 Extreme Networks Method and apparatus for restoring the configuration of a network device
US6959329B2 (en) * 2002-05-15 2005-10-25 Intelliden System and method for transforming configuration commands
US7716576B1 (en) * 2002-05-20 2010-05-11 Cisco Technology, Inc. Flexible XML parsing based on p-code
US7461158B2 (en) * 2002-08-07 2008-12-02 Intelliden, Inc. System and method for controlling access rights to network resources
ITTO20020742A1 (en) * 2002-08-23 2004-02-24 Telecom Italia Lab Spa PROCEDURE AND SYSTEM FOR THE CONTROL OF THE
US20040064803A1 (en) * 2002-09-27 2004-04-01 Graves David A. Validation system and method
WO2004034229A2 (en) 2002-10-10 2004-04-22 Rocksteady Networks, Inc. System and method for providing access control
AU2003301482A1 (en) * 2002-10-16 2004-05-04 Rocksteady Networks, Inc. System and method for dynamic bandwidth provisioning
US7290263B1 (en) * 2002-12-19 2007-10-30 Extreme, Networks, Inc. Method and system for a scriptable command line interface
JP2005056039A (en) * 2003-08-01 2005-03-03 Sony Corp Information processing system and method, program, and recording medium
US7624438B2 (en) 2003-08-20 2009-11-24 Eric White System and method for providing a secure connection between networked computers
US7392300B2 (en) * 2004-01-08 2008-06-24 Hewlett-Packard Development Company, L.P. Method and system for modelling a communications network
US20050204022A1 (en) * 2004-03-10 2005-09-15 Keith Johnston System and method for network management XML architectural abstraction
US7610621B2 (en) * 2004-03-10 2009-10-27 Eric White System and method for behavior-based firewall modeling
US8543710B2 (en) * 2004-03-10 2013-09-24 Rpx Corporation Method and system for controlling network access
US7590728B2 (en) * 2004-03-10 2009-09-15 Eric White System and method for detection of aberrant network behavior by clients of a network access gateway
US7665130B2 (en) * 2004-03-10 2010-02-16 Eric White System and method for double-capture/double-redirect to a different location
US20050229152A1 (en) * 2004-04-08 2005-10-13 Brian Connell Integrated modeling environment
US7657635B2 (en) * 2004-07-30 2010-02-02 Extreme Networks Method and apparatus for converting network management protocol to markup language
US20060025984A1 (en) * 2004-08-02 2006-02-02 Microsoft Corporation Automatic validation and calibration of transaction-based performance models
US7536448B2 (en) * 2004-09-02 2009-05-19 Cisco Technology, Inc. Auto-generation of configuration and topology models
EP1843520B1 (en) * 2004-12-28 2012-12-19 ZTE Corporation A method and device for controlling the configuration of configuration parameter set of the remote device
CN100429888C (en) * 2005-01-12 2008-10-29 乐金电子(中国)研究开发中心有限公司 Personalized mobile telephone configuration method and mobile telephone and website that can be personalized
US7860989B2 (en) 2005-02-02 2010-12-28 Microsoft Corporation Efficient transformation of interchange format messages
US7779398B2 (en) * 2005-06-08 2010-08-17 Cisco Technology, Inc. Methods and systems for extracting information from computer code
US7784036B2 (en) * 2005-06-08 2010-08-24 Cisco Technology, Inc. Methods and systems for transforming a parse graph into an and/or command tree
US7698694B2 (en) * 2005-06-08 2010-04-13 Cisco Technology, Inc. Methods and systems for transforming an AND/OR command tree into a command data model
US7685316B2 (en) * 2005-06-16 2010-03-23 Cisco Technology, Inc. System and method for coordinated network configuration
US7953886B2 (en) * 2005-07-08 2011-05-31 Cisco Technology, Inc. Method and system of receiving and translating CLI command data within a routing system
US7908594B2 (en) * 2005-07-29 2011-03-15 Cisco Technology, Inc. External programmatic interface for IOS CLI compliant routers
US20070244997A1 (en) * 2005-08-31 2007-10-18 Tindal Glen D System and method for configuring a network device
US8015270B2 (en) * 2005-09-06 2011-09-06 Reldata, Inc. Redundant appliance configuration repository in standard hierarchical format
GB2433675B (en) 2005-12-22 2008-05-07 Cramer Systems Ltd Communications circuit design
US7823069B1 (en) * 2006-03-23 2010-10-26 Cisco Technology, Inc. Method and application tool for dynamically navigating a user customizable representation of a network device configuration
US20080005344A1 (en) * 2006-06-29 2008-01-03 Ford Daniel E Method and system for configuring a network device using a template
US20090327301A1 (en) * 2008-06-26 2009-12-31 Microsoft Corporation Distributed Configuration Management Using Constitutional Documents
EP2211277A1 (en) 2009-01-19 2010-07-28 BRITISH TELECOMMUNICATIONS public limited company Method and apparatus for generating an integrated view of multiple databases
US10114666B1 (en) * 2009-09-30 2018-10-30 EMC IP Holding Company LLC Loading software components
US9571489B2 (en) * 2011-08-12 2017-02-14 Sony Corporation System and method for performing commands from a remote source
GB2497932A (en) 2011-12-21 2013-07-03 Ibm Network device modelling of configuration commands to predict the effect of the commands on the device.
US9280514B1 (en) * 2012-07-11 2016-03-08 Tellabs Operations, Inc. Optimizing testability of network devices using markup language based output
GB2505644A (en) 2012-09-05 2014-03-12 Ibm Managing network configurations
US9417892B2 (en) 2012-09-28 2016-08-16 International Business Machines Corporation Configuration command template creation assistant using cross-model analysis to identify common syntax and semantics
CN103546572B (en) * 2013-10-30 2017-04-05 北京荣之联科技股份有限公司 A kind of cloudy storing networking system and method
US9959106B2 (en) * 2013-11-14 2018-05-01 International Business Machines Corporation Sharing of portable initialized objects between computing platforms
US9607059B2 (en) * 2014-01-31 2017-03-28 Sap Se Intelligent data mining and processing of machine generated logs
US10545749B2 (en) * 2014-08-20 2020-01-28 Samsung Electronics Co., Ltd. System for cloud computing using web components
US11223530B2 (en) * 2019-09-06 2022-01-11 International Business Machines Corporation Natural language processing in modeling of network device configurations

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6198479B1 (en) * 1997-06-25 2001-03-06 Samsung Electronics Co., Ltd Home network, browser based, command and control
US20020069340A1 (en) * 2000-12-06 2002-06-06 Glen Tindal System and method for redirecting data generated by network devices
US20020069367A1 (en) * 2000-12-06 2002-06-06 Glen Tindal Network operating system data directory
US20020069271A1 (en) * 2000-12-06 2002-06-06 Glen Tindal Event manager for network operating system
US20030051008A1 (en) * 2001-08-29 2003-03-13 Gorthy Scott B. System and method for generating a configuration schema
US6978301B2 (en) * 2000-12-06 2005-12-20 Intelliden System and method for configuring a network device
US7054946B2 (en) * 2000-12-06 2006-05-30 Intelliden Dynamic configuration of network devices to enable data transfers
US7054924B1 (en) * 2000-09-29 2006-05-30 Cisco Technology, Inc. Method and apparatus for provisioning network devices using instructions in extensible markup language
US7249170B2 (en) * 2000-12-06 2007-07-24 Intelliden System and method for configuration, management and monitoring of network resources

Family Cites Families (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4991089A (en) * 1988-09-30 1991-02-05 Ibm Corp. Method for establishing current terminal addresses for system users processing distributed application programs in an SNA LU 6.2 network environment
US5109486A (en) * 1989-01-06 1992-04-28 Motorola, Inc. Distributed computer system with network and resource status monitoring
DE69030340T2 (en) 1989-02-24 1997-11-20 Digital Equipment Corp Broker for the selection of computer network servers
US5159685A (en) * 1989-12-06 1992-10-27 Racal Data Communications Inc. Expert system for communications network
DE69126666T2 (en) * 1990-09-17 1998-02-12 Cabletron Systems Inc NETWORK MANAGEMENT SYSTEM WITH MODEL-BASED INTELLIGENCE
CA2048306A1 (en) * 1990-10-02 1992-04-03 Steven P. Miller Distributed configuration profile for computing system
US5301284A (en) * 1991-01-16 1994-04-05 Walker-Estes Corporation Mixed-resolution, N-dimensional object space method and apparatus
US5974236A (en) * 1992-03-25 1999-10-26 Aes Corporation Dynamically reconfigurable communications network and method
WO1993020511A1 (en) * 1992-03-31 1993-10-14 Aggregate Computing, Inc. An integrated remote execution system for a heterogenous computer network environment
US5819028A (en) * 1992-06-10 1998-10-06 Bay Networks, Inc. Method and apparatus for determining the health of a network
CA2100540A1 (en) * 1992-10-19 1994-04-20 Jonel George System and method for performing resource reconfiguration in a computer system
WO1994025913A2 (en) * 1993-04-30 1994-11-10 Novadigm, Inc. Method and apparatus for enterprise desktop management
US6269398B1 (en) * 1993-08-20 2001-07-31 Nortel Networks Limited Method and system for monitoring remote routers in networks for available protocols and providing a graphical representation of information received from the routers
US5838918A (en) * 1993-12-13 1998-11-17 International Business Machines Corporation Distributing system configuration information from a manager machine to subscribed endpoint machines in a distrubuted computing environment
JP3084066B2 (en) * 1993-12-24 2000-09-04 インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン Routing bandwidth reservation connections in information networks
US5519704A (en) * 1994-04-21 1996-05-21 Cisco Systems, Inc. Reliable transport protocol for internetwork routing
US5787246A (en) * 1994-05-27 1998-07-28 Microsoft Corporation System for configuring devices for a computer system
US5751967A (en) * 1994-07-25 1998-05-12 Bay Networks Group, Inc. Method and apparatus for automatically configuring a network device to support a virtual network
US5884028A (en) * 1994-07-29 1999-03-16 International Business Machines Corporation System for the management of multiple time-critical data streams
US5491820A (en) * 1994-11-10 1996-02-13 At&T Corporation Distributed, intermittently connected, object-oriented database and management system
US5920701A (en) * 1995-01-19 1999-07-06 Starburst Communications Corporation Scheduling data transmission
US5557748A (en) * 1995-02-03 1996-09-17 Intel Corporation Dynamic network configuration
US5872928A (en) * 1995-02-24 1999-02-16 Cabletron Systems, Inc. Method and apparatus for defining and enforcing policies for configuration management in communications networks
US5832503A (en) * 1995-02-24 1998-11-03 Cabletron Systems, Inc. Method and apparatus for configuration management in communications networks
US5889953A (en) * 1995-05-25 1999-03-30 Cabletron Systems, Inc. Policy management and conflict resolution in computer networks
US5724516A (en) 1995-09-06 1998-03-03 International Business Machines Corporation System for dynamically creating and retrieving formatted dump data by setting value in dump object indicating that the dump agent is to generate formatted dump data
US5726883A (en) * 1995-10-10 1998-03-10 Xerox Corporation Method of customizing control interfaces for devices on a network
US5764955A (en) * 1995-10-19 1998-06-09 Oasys Group, Inc. Gateway for using legacy telecommunications network element equipment with a common management information protocol
US6356955B1 (en) * 1996-02-15 2002-03-12 International Business Machines Corporation Method of mapping GDMO templates and ASN.1 defined types into C++ classes using an object-oriented programming interface
US5796732A (en) * 1996-03-28 1998-08-18 Cisco Technology, Inc. Architecture for an expandable transaction-based switching bus
US5724509A (en) * 1996-04-22 1998-03-03 Motorola, Inc. Method and apparatus for synchronizing implementation of configuration information in a communication system
DE69720857T2 (en) 1996-05-31 2004-02-05 Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto Systems and methods for operating a network management station
US5842040A (en) * 1996-06-18 1998-11-24 Storage Technology Corporation Policy caching method and apparatus for use in a communication device based on contents of one data unit in a subset of related data units
FR2750517B1 (en) * 1996-06-27 1998-08-14 Bull Sa METHOD FOR MONITORING A PLURALITY OF OBJECT TYPES OF A PLURALITY OF NODES FROM A ADMINISTRATION NODE IN A COMPUTER SYSTEM
US5961594A (en) 1996-09-26 1999-10-05 International Business Machines Corporation Remote node maintenance and management method and system in communication networks using multiprotocol agents
US5944782A (en) * 1996-10-16 1999-08-31 Veritas Software Corporation Event management system for distributed computing environment
US5956341A (en) * 1996-12-13 1999-09-21 International Business Machines Corporation Method and system for optimizing data transmission line bandwidth occupation in a multipriority data traffic environment
US6055568A (en) * 1996-12-17 2000-04-25 Intel Corporation Method and apparatus for dynamically configuring a decentralized network of computers
US6105069A (en) * 1997-01-22 2000-08-15 Novell, Inc. Licensing controller using network directory services
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
US6658526B2 (en) * 1997-03-12 2003-12-02 Storage Technology Corporation Network attached virtual data storage subsystem
US5948065A (en) * 1997-03-28 1999-09-07 International Business Machines Corporation System for managing processor resources in a multisystem environment in order to provide smooth real-time data streams while enabling other types of applications to be processed concurrently
US5968122A (en) * 1997-03-31 1999-10-19 Alcatel Alsthom Compagnie Generale D'electricite Method for propagating between views of connection object status in network
US6131119A (en) * 1997-04-01 2000-10-10 Sony Corporation Automatic configuration system for mapping node addresses within a bus structure to their physical location
US5968176A (en) * 1997-05-29 1999-10-19 3Com Corporation Multilayer firewall system
US6260072B1 (en) * 1997-06-12 2001-07-10 Lucent Technologies Inc Method and apparatus for adaptive routing in packet networks
US6108699A (en) 1997-06-27 2000-08-22 Sun Microsystems, Inc. System and method for modifying membership in a clustered distributed computer system and updating system configuration
US6098108A (en) * 1997-07-02 2000-08-01 Sitara Networks, Inc. Distributed directory for enhanced network communication
US6101508A (en) * 1997-08-01 2000-08-08 Hewlett-Packard Company Clustered file management for network resources
US6104700A (en) * 1997-08-29 2000-08-15 Extreme Networks Policy based quality of service
US6028846A (en) * 1997-09-11 2000-02-22 U S West, Inc. Method and system for testing real-time delivery of packets of data
US6418461B1 (en) * 1997-10-06 2002-07-09 Mci Communications Corporation Intelligent call switching node in an intelligent distributed network architecture
US6363411B1 (en) * 1998-08-05 2002-03-26 Mci Worldcom, Inc. Intelligent network
US6041347A (en) * 1997-10-24 2000-03-21 Unified Access Communications Computer system and computer-implemented process for simultaneous configuration and monitoring of a computer network
US6202090B1 (en) * 1997-12-11 2001-03-13 Cisco Technology, Inc. Apparatus and method for downloading core file in a network device
US6098101A (en) * 1997-12-11 2000-08-01 Micron Electronics, Inc. Method and apparatus for generating shared modem usage reports in a networked computer system
US5931594A (en) * 1997-12-12 1999-08-03 Valois S.A. Cosmetic product distributors intended for make-up and corresponding gripping element
US6128729A (en) * 1997-12-16 2000-10-03 Hewlett-Packard Company Method and system for automatic configuration of network links to attached devices
US6006035A (en) * 1997-12-31 1999-12-21 Network Associates Method and system for custom computer software installation
US6449638B1 (en) * 1998-01-07 2002-09-10 Microsoft Corporation Channel definition architecture extension
US6023586A (en) * 1998-02-10 2000-02-08 Novell, Inc. Integrity verifying and correcting software
US6170011B1 (en) * 1998-09-11 2001-01-02 Genesys Telecommunications Laboratories, Inc. Method and apparatus for determining and initiating interaction directionality within a multimedia communication center
US6370119B1 (en) * 1998-02-27 2002-04-09 Cisco Technology, Inc. Computing the widest shortest path in high-speed networks
US6154776A (en) * 1998-03-20 2000-11-28 Sun Microsystems, Inc. Quality of service allocation on a network
JP3307329B2 (en) * 1998-05-27 2002-07-24 日本電気株式会社 Network configuration managed access system and method
US6131118A (en) * 1998-07-07 2000-10-10 Compaq Computer Corporation Flexible display of management data in a programmable event driven processing system
US6108703A (en) * 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
US6170009B1 (en) * 1998-07-17 2001-01-02 Kallol Mandal Controlling devices on a network through policies
US6097697A (en) * 1998-07-17 2000-08-01 Sitara Networks, Inc. Congestion control
US6167445A (en) * 1998-10-26 2000-12-26 Cisco Technology, Inc. Method and apparatus for defining and implementing high-level quality of service policies in computer networks
US6349306B1 (en) * 1998-10-30 2002-02-19 Aprisma Management Technologies, Inc. Method and apparatus for configuration management in communications networks
US6301613B1 (en) * 1998-12-03 2001-10-09 Cisco Technology, Inc. Verifying that a network management policy used by a computer system can be satisfied and is feasible for use
US6442608B1 (en) * 1999-01-14 2002-08-27 Cisco Technology, Inc. Distributed database system with authoritative node
US6826597B1 (en) * 1999-03-17 2004-11-30 Oracle International Corporation Providing clients with services that retrieve data from data sources that do not necessarily support the format required by the clients
US6496843B1 (en) * 1999-03-31 2002-12-17 Verizon Laboratories Inc. Generic object for rapid integration of data changes
US6393415B1 (en) * 1999-03-31 2002-05-21 Verizon Laboratories Inc. Adaptive partitioning techniques in performing query requests and request routing
US6463583B1 (en) * 1999-04-08 2002-10-08 Novadigm, Inc. Dynamic injection of execution logic into main dynamic link library function of the original kernel of a windowed operating system
US6550060B1 (en) * 1999-04-08 2003-04-15 Novadigm, Inc. Method and system for dynamic injection of dynamic link libraries into a windowed operating system
US6393425B1 (en) * 1999-05-05 2002-05-21 Microsoft Corporation Diagramming real-world models based on the integration of a database, such as models of a computer network
US6678827B1 (en) * 1999-05-06 2004-01-13 Watchguard Technologies, Inc. Managing multiple network security devices from a manager device
US6615166B1 (en) * 1999-05-27 2003-09-02 Accenture Llp Prioritizing components of a network framework required for implementation of technology
US6381631B1 (en) * 1999-06-03 2002-04-30 Marimba, Inc. Method and apparatus for controlling client computer systems
US6539425B1 (en) * 1999-07-07 2003-03-25 Avaya Technology Corp. Policy-enabled communications networks
US6625590B1 (en) * 1999-08-10 2003-09-23 International Business Machines Corporation Command line interface for reducing user input in a network management device
US6438594B1 (en) * 1999-08-31 2002-08-20 Accenture Llp Delivering service to a client via a locally addressable interface
US20040225865A1 (en) * 1999-09-03 2004-11-11 Cox Richard D. Integrated database indexing system
US6636877B1 (en) 1999-09-21 2003-10-21 Verizon Laboratories Inc. Method for analyzing the quality of telecommunications switch command tables
US6769116B1 (en) * 1999-10-21 2004-07-27 Oracle International Corporation Diagnostic technique for debugging memory corruption
US6609108B1 (en) * 1999-11-05 2003-08-19 Ford Motor Company Communication schema of online system and method of ordering consumer product having specific configurations
US6567406B1 (en) * 1999-12-10 2003-05-20 Tropic Networks Inc. Method of labeling data units with a domain field
DE19961893C2 (en) * 1999-12-21 2002-02-21 Sascha Manthey Device for locking swiveling door leaves in the closed position with an indirect locking system
US6684244B1 (en) * 2000-01-07 2004-01-27 Hewlett-Packard Development Company, Lp. Aggregated policy deployment and status propagation in network management systems
AU2001257374A1 (en) * 2000-04-28 2001-11-12 Sheer Networks, Inc. Network management method and system
US7034864B2 (en) * 2000-05-19 2006-04-25 Canon Kabushiki Kaisha Image display apparatus, image display system, and image display method
AUPQ849500A0 (en) * 2000-06-30 2000-07-27 Canon Kabushiki Kaisha Hash compact xml parser
US7207031B2 (en) * 2001-03-01 2007-04-17 Wind River Systems, Inc. System and method for utilization of a command structure representation
US6930730B2 (en) * 2001-05-03 2005-08-16 Mitsubishi Digital Electronics America, Inc. Control system and user interface for network of input devices
US6725233B2 (en) * 2001-05-15 2004-04-20 Occam Networks Generic interface for system and application management
US7054901B2 (en) * 2001-05-31 2006-05-30 Juniper Networks, Inc. Network management interface with selective rendering of output
US7072946B2 (en) * 2001-05-31 2006-07-04 Juniper Networks, Inc. Network router management interface with API invoked via login stream
US7278143B2 (en) * 2001-06-28 2007-10-02 Microsoft Corporation System and related methods for accessing management functionality through a command line utility
US6907572B2 (en) * 2001-08-10 2005-06-14 Occam Networks Command line interface abstraction engine
US7130854B2 (en) * 2001-08-14 2006-10-31 Endforce, Inc. Selection and storage of policies in network management
CA2467727A1 (en) * 2001-11-21 2003-05-30 Enterasys Networks, Inc. Translating configuration files among network devices
US7124328B2 (en) * 2002-05-14 2006-10-17 Sun Microsystems, Inc. Capturing system error messages

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6198479B1 (en) * 1997-06-25 2001-03-06 Samsung Electronics Co., Ltd Home network, browser based, command and control
US7054924B1 (en) * 2000-09-29 2006-05-30 Cisco Technology, Inc. Method and apparatus for provisioning network devices using instructions in extensible markup language
US20020069340A1 (en) * 2000-12-06 2002-06-06 Glen Tindal System and method for redirecting data generated by network devices
US20020069367A1 (en) * 2000-12-06 2002-06-06 Glen Tindal Network operating system data directory
US20020069271A1 (en) * 2000-12-06 2002-06-06 Glen Tindal Event manager for network operating system
US6978301B2 (en) * 2000-12-06 2005-12-20 Intelliden System and method for configuring a network device
US7054946B2 (en) * 2000-12-06 2006-05-30 Intelliden Dynamic configuration of network devices to enable data transfers
US7249170B2 (en) * 2000-12-06 2007-07-24 Intelliden System and method for configuration, management and monitoring of network resources
US20030051008A1 (en) * 2001-08-29 2003-03-13 Gorthy Scott B. System and method for generating a configuration schema

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060256813A1 (en) * 2005-05-12 2006-11-16 Verizon Services Corp. Automatic configuration of network devices for network services
US8085808B2 (en) * 2005-05-12 2011-12-27 Verizon Services Corp. Automatic configuration of network devices for network services
US8112582B2 (en) * 2008-03-10 2012-02-07 Lsi Corporation Redundant array of inexpensive disks configuration using simple network management protocol
US20090228649A1 (en) * 2008-03-10 2009-09-10 Porel Partha P Redundant array of inexpensive disks configuration using simple network management protocol
US8285934B2 (en) 2008-03-10 2012-10-09 Lsi Corporation Redundancy array of inexpensive disks configuration using simple network management protocol
US20090271510A1 (en) * 2008-04-28 2009-10-29 Microsoft Corporation Network state platform
US8086701B2 (en) * 2008-04-28 2011-12-27 Microsoft Corporation Platform for managing and configuring network state
US20100024031A1 (en) * 2008-07-24 2010-01-28 Sap Portals Israel Ltd System and method for transforming hierarchical objects
US20110010383A1 (en) * 2009-07-07 2011-01-13 Thompson Peter C Systems and methods for streamlining over-the-air and over-the-wire device management
US11695615B2 (en) 2014-11-14 2023-07-04 Apstra, Inc. Configuring a network
US11223512B2 (en) * 2014-11-14 2022-01-11 Apstra, Inc. Configuring a network
US11677619B2 (en) 2015-06-30 2023-06-13 Apstra, Inc. Selectable declarative requirement levels
US11876699B2 (en) 2015-12-23 2024-01-16 Apstra, Inc. Verifying service status
US11323338B2 (en) 2015-12-23 2022-05-03 Apstra, Inc. Verifying service status
US11088900B2 (en) 2016-05-24 2021-08-10 Apstra, Inc. Configuring system resources for different reference architectures
US11689413B2 (en) 2016-05-24 2023-06-27 Apstra, Inc. Configuring system resources for different reference architectures
US11567994B2 (en) 2017-01-24 2023-01-31 Apstra, Inc. Configuration, telemetry, and analytics of a computer infrastructure using a graph model
US11451451B2 (en) 2017-12-08 2022-09-20 Apstra, Inc. Intent-based analytics
US11805024B1 (en) 2019-03-21 2023-10-31 Apstra, Inc. Automatically generating an intent-based network model of an existing computer network
US11444833B1 (en) 2019-04-24 2022-09-13 Juniper Networks, Inc. Business policy management for self-driving network
US11658872B1 (en) 2019-04-24 2023-05-23 Juniper Networks, Inc. Business policy management for self-driving network
US11075805B1 (en) 2019-04-24 2021-07-27 Juniper Networks, Inc. Business policy management for self-driving network
US11283691B1 (en) 2020-10-21 2022-03-22 Juniper Networks, Inc. Model driven intent policy conflict detection and resolution through graph analysis
US11652704B2 (en) 2020-10-21 2023-05-16 Juniper Networks, Inc. Model driven intent policy conflict detection and resolution through graph analysis
US11929886B2 (en) 2020-10-21 2024-03-12 Juniper Networks, Inc. Model driven intent policy conflict detection and resolution through graph analysis
US11570055B2 (en) 2020-11-25 2023-01-31 Apstra, Inc. Connectivity templates

Also Published As

Publication number Publication date
US20030046370A1 (en) 2003-03-06
US7200548B2 (en) 2007-04-03
WO2003021415A1 (en) 2003-03-13

Similar Documents

Publication Publication Date Title
US7200548B2 (en) System and method for modeling a network device's configuration
US6959329B2 (en) System and method for transforming configuration commands
US7065562B2 (en) System and method for generating a representation of a configuration schema
US7246162B2 (en) System and method for configuring a network device
US20030051008A1 (en) System and method for generating a configuration schema
US7580936B2 (en) Extendable discovery of network device information
US5787252A (en) Filtering system and method for high performance network management map
US7249170B2 (en) System and method for configuration, management and monitoring of network resources
US8010952B2 (en) Method and apparatus for configuration syntax and semantic validation
EP1955479B1 (en) Network service configuration management
US9331902B2 (en) Apparatus and method providing unified network management
US20070244997A1 (en) System and method for configuring a network device
US20040003067A1 (en) System and method for enabling a user interface with GUI meta data
EP1782215B1 (en) A generic framework for deploying ems provisioning services
US20080301143A1 (en) Automatic Update System and Method for Using a Meta Mib
US20060242284A1 (en) Generating MIBs from WMI classes
US20090182880A1 (en) System and Method to Synthesize Custom Metric Attributes from Available MBean Attributes on an Application Server
JP2002368743A (en) Network design support system
WO2008064825A1 (en) Management method for server customer communication
WO2016107397A1 (en) System and method for model-based search and retrieval of networked data
US8880664B1 (en) Method and apparatus for generating a network profile and device profile
JP5181958B2 (en) Device management apparatus, device management system, device information acquisition program, and recording medium recording the program
WO2006051599A1 (en) Resource management program, resource management method, and resource management device
KR20030057921A (en) Method of Managing MIB Table Structure in the SNMP Network

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTELLIDEN, INC., COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COURTNEY, MIKE;REEL/FRAME:018896/0826

Effective date: 20010814

AS Assignment

Owner name: SCHNEIDER, JAMES M., TEXAS

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: GERDELMAN, SUE & JOHN, VIRGINIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: GAFFNEY, ROBERT P., COLORADO

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: BLACK FAMILY TRUST 2001 U/I DTD, CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: MATRIX VI PARALLEL PARTNERSHIP-A, L.P., MASSACHUSE

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: MATRIX VI PARALLEL PARTNERSHIP-B, L.P., MASSACHUSE

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: VOS, REMKO, CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: WESTON & CO. VI, LLC, MASSACHUSETTS

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: GRANITE GLOBAL VENTURES II L.P., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: GGV II ENTREPRENEURES FUND L.P., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: MICHAEL J. ROWNY REVOCABLE TRUST UTA, MARYLAND

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: MATRIX PARTNERS VI, L.P., MASSACHUSETTS

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: BOYNTON FAMILY TRUST BY CHARLES BOYNTON, CALIFORNI

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: SUE GERDELMAN & JOHN GERDELMAN TTEE REVOC. TRUST O

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: KOOKABURRA LLC, NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: SNOWS HILL, LLC, MASSACHUSETTS

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: WESTBURY EQUITY PARTNERS SBIC, L.P., NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

Owner name: LALUDE, AKINYEMI O., TEXAS

Free format text: SECURITY AGREEMENT;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:022552/0785

Effective date: 20090319

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: INTELLIDEN, INC.,COLORADO

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:MATRIX PARTNERS VI, L.P.;MATRIX VI PARALLEL PARTNERSHIP-B, L.P.;WESTON & CO. VI, LLC;AND OTHERS;REEL/FRAME:024053/0635

Effective date: 20100215

Owner name: INTELLIDEN, INC., COLORADO

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:MATRIX PARTNERS VI, L.P.;MATRIX VI PARALLEL PARTNERSHIP-B, L.P.;WESTON & CO. VI, LLC;AND OTHERS;REEL/FRAME:024053/0635

Effective date: 20100215