US20090019139A1 - Repository-Independent System and Method for Asset Management and Reconciliation - Google Patents
Repository-Independent System and Method for Asset Management and Reconciliation Download PDFInfo
- Publication number
- US20090019139A1 US20090019139A1 US12/236,609 US23660908A US2009019139A1 US 20090019139 A1 US20090019139 A1 US 20090019139A1 US 23660908 A US23660908 A US 23660908A US 2009019139 A1 US2009019139 A1 US 2009019139A1
- Authority
- US
- United States
- Prior art keywords
- configuration
- network
- knowledge
- instances
- configuration data
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
- H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
Definitions
- the present invention relates to network device management.
- the present invention relates to systems and methods for maintaining network device configurations and/or generating network device configurations.
- Network devices such as routers, switches and optical devices are becoming increasingly more complicated.
- Typical network devices now require thousands of lines of specialized configuration instructions to operate properly.
- the instructions that operate network devices can be changed on a frequent basis, and the nature of network devices often requires that each version of a device's configuration be stored.
- sizable repositories of old configurations are generated for each device.
- sizable repositories are accumulated across the thousands of network devices that frequently make up a network, cumbersome, inefficient repositories are created. In some cases, these repositories are so large that they are not useful.
- configuration knowledge generally requires that configuration instructions and the capabilities of a network device (referred to as “configuration knowledge”) be stored together as an atomic unit. This single-data-model approach has proven difficult to maintain for sophisticated networks. When network administrators, for example, archive only the configuration data—the actual configuration instructions or some indication thereof—the configuration knowledge that was used to generate those configuration instructions is lost. When the network administrators attempt to archive both the configuration instructions and the configuration knowledge for each configuration change, the size of the archived file becomes too large because the knowledge used to generate the configuration is many times the size of the actual configuration.
- the configuration knowledge is generally invariant, e.g., the operating system and hardware for the network device do not change. Thus, repeatedly archiving the configuration knowledge is wasteful.
- Network administrators have also found that the single-data-model implementation makes reverting to previous configurations difficult.
- the configuration data and the configuration knowledge are bundled together as an atomic unit, network administrators have significant difficulty in reverting to a previous device configuration when both the configuration instructions and the configuration knowledge change. For example, when a network device is upgraded to run a new version of its operating system, both the configuration knowledge and the configuration data are changed. If the upgrade fails, rolling back the changes to a known state for the previous operating system.
- Present network technology suffers from yet another drawback in that it lacks a common information model that can be used to derive each of the application-specific configurations. This lack results in network applications having difficulty in retrieving and sharing network information from different network devices. Even more problematic is the fact that the lack of the common information model results in network applications sharing network data infrequently. For example, each application might implement its own procedure for discovery of network devices because it cannot understand information generated by another network application.
- the configuration of a network device is separated into two portions: configuration knowledge and configuration data.
- Configuration knowledge for a particular network device is referred to as a configuration knowledge instance.
- configuration data for a particular network device is referred to as a configuration data instance.
- Configuration knowledge abstractly represents the capabilities of a network device, but not necessarily the actual configuration of that device.
- the configuration knowledge for a router might indicate the types of traffic conditioning, chip organization, and routing protocols that are available to that router.
- Configuration knowledge can be comprised of individual configuration schemata, which define the individual portions that make up the complete configuration knowledge.
- configuration knowledge for a device can be constructed from a set of individual schemata, when the capabilities of that network device are changed, the relevant portion of the configuration knowledge instance can be changed without otherwise rebuilding the entire configuration knowledge instance. For example, if a new card is added to a router, then the schemata for that new card is added to the configuration knowledge instance. The remaining portion of the configuration knowledge instance, however, may remain unchanged.
- the configuration data for a particular network device can be derived from the configuration knowledge instance for that device. Moreover, each configuration data instance can be associated with a particular version of the configuration knowledge instance. For example, if a router is updated with a new operating system (OS), a new version of the configuration knowledge instance that reflects the new OS is created. Subsequent sets of configuration data can be associated with the new version of the configuration knowledge instance.
- OS operating system
- FIG. 1 illustrates one organization of a configuration knowledge instance for a network device
- FIG. 2 is a block diagram of one embodiment of the present invention.
- FIG. 3 illustrates versioned KDMs and configuration instructions
- FIG. 4 is a block diagram of a network including network management applications and configuration knowledge and data storage devices
- FIG. 5 is a flowchart of one method for implementing a roll-back.
- FIG. 6 is a flowchart of one method for implementing a business policy in a network.
- Configuration knowledge abstractly represents the capabilities—both logical and physical—of a network device, and the configuration data includes information about the actual configuration of the network device. Put simply, configuration knowledge describes the features of a network device, and the configuration data indicates which features are being used and how they are being used.
- Typical configuration knowledge can include separate abstractions for each feature of the network device. For example, the configuration knowledge for a particular router could list the physical properties of the router such as processor type and available cards. Similarly, the configuration knowledge could list the logical capabilities of the router such as available protocols, security features and services. The actual configuration information for these physical and logical properties would be stored with the configuration data instance for that router. Note that the configuration of most network resources, including routers, router components, switches, switch components, fabrics, optical devices, and optical components can be divided into configuration knowledge and configuration data.
- FIG. 1 it illustrates one possible organization 10 of configuration knowledge.
- This abstraction includes a device family layer 12 for devices that all share common features and/or other characteristics.
- a typical device family could be “router” or “CISCO router.”
- the device family layer 12 is refined by the device layer 14 , which represents a software abstraction of a specific device.
- a typical device for the “router” family could be “CISCO,” and a device for the “CISCO router” family could be a particular model of CISCO router.
- the device family layer 12 can then further refined into its physical and logical aspects, which are represented by the physical and logical abstraction layers 16 and 18 .
- the physical and logical layers 16 and 18 can be refined according to the features of the family of devices being represented.
- the logical abstraction for a router can include: address management, services, security, protocols, and traffic conditioning.
- the physical abstraction can include: cabling, processors, cards, and chassis. These refinements are not inclusive, but rather exemplary for one type of device. Note that the logical and physical layers represent the capabilities of the class of network devices and not the actual configuration of any particular device.
- configuration knowledge can support applications that require access to only physical or logical information.
- configuration knowledge can be used to support a physical inventory application that has no need of logical information.
- the configuration knowledge can support a capacity planning application that has need for both physical and logical information. In either case, the application seeking information need only query the configuration knowledge and not the actual configuration as stored in the configuration data.
- Configuration knowledge can be organized using object classes, directories, and inheritance properties.
- the template for a new instance of configuration knowledge for a CISCO router could be formed by creating an instance that inherits the properties of a “CISCO router” class, which inherits the properties of the generic “router” class. The template would then be populated with the specific information, such as available cards and operating systems, pertaining to the particular CISCO router being modeled.
- configuration knowledge can be stored together in a central storage device or distributed across multiple storage devices.
- the configuration knowledge instances for each router on a network could be stored together in a central facility.
- the configuration knowledge instances can be stored in a variety of formats, including XML.
- FIG. 2 it is a block diagram of one embodiment of the present invention.
- instances of configuration knowledge and configuration data are stored in a configuration storage device 20 .
- the configuration storage device 20 is represented as a single device for simplicity only. It could be arranged in any fashion, including distributed, centralized, or some combination thereof. Additionally, a particular configuration knowledge instance and configuration data instance could also be stored at the network device 24 to which they correspond.
- the configuration storage device 20 is connected to a management application 22 that can be implemented in software or hardware. Additionally, the management application 22 can consist of several individual applications, including applications distributed over a network. The management application can be responsible for several functions, including:
- the management application 22 can search the individual configuration knowledge instances for particular capabilities. For example, the management application 22 can search for device capabilities such as hardware and software features of a network device that are no longer being used and are otherwise available. For example, consider the creation of a VPN. This requires dedicating either an interface or a sub-interface of a Physical Port of a network device to host the VPN traffic, along with dedicating logical resources that correspond to creating the instance of the VPN. This enables the network device to forward traffic on the VPN if the traffic is intended for that VPN.
- One example of a search is to identify components of a VPN. Similarly, if the VPN is subsequently removed, then it is important to reclaim these allocated resources. Thus, a second example of a search is to ensure that the components have been removed.
- a third example of a search is to ensure that adequate resources for creating the VPN exist before the commands are issued to the device.
- the management application 22 could also search the configuration knowledge instances for stranded services such as a virtual private network (VPN) that is no longer being used.
- the management application 22 could search for software capabilities, physical ports, physical assets, and physical containers. In effect, the management application 22 can provide an accurate inventory of the capabilities of a network. Such information can be used for network management, provisioning, and identification of stranded assets.
- the management application 22 can also support versioning of both configuration knowledge and configuration data. For example, multiple versions of configuration data could be associated with a single instance of configuration knowledge. Such versioning is particularly useful for creating different instances of configuration data that can be associated with different customer demands. Versioning is described in more detail with relation to FIG. 3 .
- the management application 22 can also enable different users to work on different parts of the configuration knowledge and configuration data simultaneously.
- the management application 22 can also track which individual features of a network device are changed and how those changes impact the configuration data. For example, if an updated card was added to a particular router, then the management application could change only the portion of the configuration knowledge corresponding to the updated card. Similarly, only the portion of the configuration instructions corresponding to the changed portion of the configuration knowledge need be changed.
- FIG. 3 it illustrates a versioned configuration knowledge instance and corresponding versions of configuration data.
- the configuration knowledge instance is associated with a particular network device and includes versions 1 through 4.
- the configuration data also corresponds to the network device and includes versions 1.1 through 4.3.
- Each version of the configuration data instance is associated with at least one of the versions of the configuration knowledge.
- configuration data V1.1 and V1.2 correspond to configuration knowledge instance V1.
- configuration data instance V2.1 corresponds to configuration knowledge instance V2.
- FIG. 4 it is a block diagram of a system that includes network management applications 40 connected to a centralized configuration knowledge storage device 42 and configuration data storage device 44 .
- a plurality of network management applications 40 are connected to the storage device through a network 46 .
- the storage devices 42 and 44 are also connected to network devices 48 ( a ) and ( b ) such as router through the network.
- the network management application 40 can access the network device 48 directly and read the relevant information. This process, however, generally requires the network management applications 40 to understand the particular syntax of the network device's configuration. In one embodiment of the present invention, however, the network management application 40 can access the storage device 42 or 44 and retrieve the relevant configuration knowledge instances or portions thereof.
- the network management applications 40 generally are not required to understand the device-specific syntax of a particular network device. For example, a physical inventory application could access the configuration knowledge instances for the relevant network devices and determine the cards that are used by each device without regard to the syntax of the actual configuration instructions.
- FIG. 5 it is a flowchart of one method for implementing a roll-back using configuration knowledge instances and versioned configuration data.
- Roll-backs are often useful for network administrators after network attacks or after unsuccessful network device updates—although they are useful in several other cases.
- new hardware is often added to existing routers in a network. This new hardware can introduce new capabilities to the router that are reflected in a new version of the router's configuration knowledge instance.
- the configuration data for the router is usually modified to engage the new hardware.
- both the configuration knowledge instance and the configuration data instance for the router are modified.
- the assembler or some other device can identify the device [step 50 ] and a version of the configuration knowledge instance that does not reflect the card's presence [step 52 ]. The configuration data associated with that version of the configuration knowledge instance can then be identified [step 54 ] and pushed to the network device [step 56 ].
- FIG. 6 it is a flowchart of one method for generating a business object model (BOM) for implementing a specific purpose in a network.
- a user or application requests a device configuration to perform a certain function [step 60 ].
- a certain function For example, assume that it is desired to create a VPN.
- the actual list of commands required to accomplish this task vary by vendor and also by version of the operating system that the network device is running. Therefore, in order to provide a single high-level ability to create a VPN, detailed knowledge of the differences in command syntax and semantics must be provided. In various embodiments of this invention, this is done through the use of a BOM, which correlates and assembles the individual knowledge instances.
- BOMs there will be many such BOMs, with a BOM for each type of function.
- the function can be small or large, a command change or a VPN creation being examples of each.
- VPN creation there will be a set of BOMs that are aggregated into a higher-level BOM. This request is handled by a BOM assembler.
- the BOM assembler determines which network resources are required to carry out the request [step 62 ].
- the BOM assembler next gathers information from the configuration knowledge instances associated with the identified network resources [step 66 ].
- the BOM derives the device configuration from the gathered configuration knowledge instances and generates the actual configuration commands [step 70 ].
- the BOM assembler will select appropriate BOMs, aggregate them together, and use the aggregated BOM to derive the appropriate device configuration commands for each device. This enables the device to be programmed at a high functional level, and to have these high-level functions translated to a low-level device-specific implementation. Examples of systems for generating commands are described in commonly owned and assigned U.S. patent application Ser. Nos.
- the device configuration is derived by binding the variable information within the configuration knowledge instances to the business purpose of the customer. For example, a QoS business purpose could be bound to the various traffic conditioning settings.
- the present invention provides, among other things, a system and method for managing and utilizing network device configurations.
- Those skilled in the art can readily recognize that numerous variations and substitutions may be made in the invention, its use and its configuration to achieve substantially the same results as achieved by the embodiments described herein. Accordingly, there is no intention to limit the invention to the disclosed exemplary forms. Many variations, modifications and alternative constructions fall within the scope and spirit of the disclosed invention as expressed in the claims.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- This application is a continuation application of U.S. application Ser. No. 10/617,420, filed Jul. 10, 2003, entitled Repository-Independent System and Method for Asset Management and Reconciliation, which claims the benefit of U.S. provisional patent Application No. 60/395,698, filed Jul. 11, 2002, entitled Repository-Independent System and Method for Asset Management and Reconciliation, which are both incorporated herein by reference in their entirety.
- The present invention relates to network device management. In particular, but not by way of limitation, the present invention relates to systems and methods for maintaining network device configurations and/or generating network device configurations.
- Network devices such as routers, switches and optical devices are becoming increasingly more complicated. Typical network devices now require thousands of lines of specialized configuration instructions to operate properly. Unlike most software applications, the instructions that operate network devices can be changed on a frequent basis, and the nature of network devices often requires that each version of a device's configuration be stored. Because changes are so frequent, sizable repositories of old configurations are generated for each device. When these sizable repositories are accumulated across the thousands of network devices that frequently make up a network, cumbersome, inefficient repositories are created. In some cases, these repositories are so large that they are not useful.
- Present network architecture generally requires that configuration instructions and the capabilities of a network device (referred to as “configuration knowledge”) be stored together as an atomic unit. This single-data-model approach has proven difficult to maintain for sophisticated networks. When network administrators, for example, archive only the configuration data—the actual configuration instructions or some indication thereof—the configuration knowledge that was used to generate those configuration instructions is lost. When the network administrators attempt to archive both the configuration instructions and the configuration knowledge for each configuration change, the size of the archived file becomes too large because the knowledge used to generate the configuration is many times the size of the actual configuration.
- For a given version of a network device, the configuration knowledge is generally invariant, e.g., the operating system and hardware for the network device do not change. Thus, repeatedly archiving the configuration knowledge is wasteful.
- Network administrators have also found that the single-data-model implementation makes reverting to previous configurations difficult. When the configuration data and the configuration knowledge are bundled together as an atomic unit, network administrators have significant difficulty in reverting to a previous device configuration when both the configuration instructions and the configuration knowledge change. For example, when a network device is upgraded to run a new version of its operating system, both the configuration knowledge and the configuration data are changed. If the upgrade fails, rolling back the changes to a known state for the previous operating system.
- Present network technology suffers from yet another drawback in that it lacks a common information model that can be used to derive each of the application-specific configurations. This lack results in network applications having difficulty in retrieving and sharing network information from different network devices. Even more problematic is the fact that the lack of the common information model results in network applications sharing network data infrequently. For example, each application might implement its own procedure for discovery of network devices because it cannot understand information generated by another network application.
- 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 of the present invention, the configuration of a network device—also referred to as network resources—is separated into two portions: configuration knowledge and configuration data. Configuration knowledge for a particular network device is referred to as a configuration knowledge instance. Similarly, configuration data for a particular network device is referred to as a configuration data instance.
- Configuration knowledge abstractly represents the capabilities of a network device, but not necessarily the actual configuration of that device. For example, the configuration knowledge for a router might indicate the types of traffic conditioning, chip organization, and routing protocols that are available to that router. Configuration knowledge can be comprised of individual configuration schemata, which define the individual portions that make up the complete configuration knowledge.
- Because configuration knowledge for a device can be constructed from a set of individual schemata, when the capabilities of that network device are changed, the relevant portion of the configuration knowledge instance can be changed without otherwise rebuilding the entire configuration knowledge instance. For example, if a new card is added to a router, then the schemata for that new card is added to the configuration knowledge instance. The remaining portion of the configuration knowledge instance, however, may remain unchanged.
- The configuration data for a particular network device can be derived from the configuration knowledge instance for that device. Moreover, each configuration data instance can be associated with a particular version of the configuration knowledge instance. For example, if a router is updated with a new operating system (OS), a new version of the configuration knowledge instance that reflects the new OS is created. Subsequent sets of configuration data can be associated with the new version of the configuration knowledge instance.
- 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 illustrates one organization of a configuration knowledge instance for a network device; -
FIG. 2 is a block diagram of one embodiment of the present invention; -
FIG. 3 illustrates versioned KDMs and configuration instructions; -
FIG. 4 is a block diagram of a network including network management applications and configuration knowledge and data storage devices; -
FIG. 5 is a flowchart of one method for implementing a roll-back; and -
FIG. 6 is a flowchart of one method for implementing a business policy in a network. - Individual network devices are typically associated with a device configuration that controls the operation of that network device. In one embodiment of the present invention, the device configuration for network device is separated into two portions: configuration knowledge and configuration data. Configuration knowledge abstractly represents the capabilities—both logical and physical—of a network device, and the configuration data includes information about the actual configuration of the network device. Put simply, configuration knowledge describes the features of a network device, and the configuration data indicates which features are being used and how they are being used.
- Typical configuration knowledge can include separate abstractions for each feature of the network device. For example, the configuration knowledge for a particular router could list the physical properties of the router such as processor type and available cards. Similarly, the configuration knowledge could list the logical capabilities of the router such as available protocols, security features and services. The actual configuration information for these physical and logical properties would be stored with the configuration data instance for that router. Note that the configuration of most network resources, including routers, router components, switches, switch components, fabrics, optical devices, and optical components can be divided into configuration knowledge and configuration data.
- Referring now to
FIG. 1 , it illustrates onepossible organization 10 of configuration knowledge. This abstraction includes adevice family layer 12 for devices that all share common features and/or other characteristics. A typical device family could be “router” or “CISCO router.” Thedevice family layer 12 is refined by thedevice layer 14, which represents a software abstraction of a specific device. A typical device for the “router” family could be “CISCO,” and a device for the “CISCO router” family could be a particular model of CISCO router. Thedevice family layer 12 can then further refined into its physical and logical aspects, which are represented by the physical and logical abstraction layers 16 and 18. - The physical and
logical layers - By defining the device according to its physical and logical capabilities, configuration knowledge can support applications that require access to only physical or logical information. For example, configuration knowledge can be used to support a physical inventory application that has no need of logical information. Likewise, the configuration knowledge can support a capacity planning application that has need for both physical and logical information. In either case, the application seeking information need only query the configuration knowledge and not the actual configuration as stored in the configuration data.
- Configuration knowledge can be organized using object classes, directories, and inheritance properties. For example, the template for a new instance of configuration knowledge for a CISCO router could be formed by creating an instance that inherits the properties of a “CISCO router” class, which inherits the properties of the generic “router” class. The template would then be populated with the specific information, such as available cards and operating systems, pertaining to the particular CISCO router being modeled.
- Once created, individual instances of configuration knowledge can be stored together in a central storage device or distributed across multiple storage devices. For example, the configuration knowledge instances for each router on a network could be stored together in a central facility. The configuration knowledge instances can be stored in a variety of formats, including XML.
- Referring now to
FIG. 2 , it is a block diagram of one embodiment of the present invention. In this embodiment, instances of configuration knowledge and configuration data are stored in aconfiguration storage device 20. Theconfiguration storage device 20 is represented as a single device for simplicity only. It could be arranged in any fashion, including distributed, centralized, or some combination thereof. Additionally, a particular configuration knowledge instance and configuration data instance could also be stored at thenetwork device 24 to which they correspond. - The
configuration storage device 20 is connected to amanagement application 22 that can be implemented in software or hardware. Additionally, themanagement application 22 can consist of several individual applications, including applications distributed over a network. The management application can be responsible for several functions, including: - Facilitation of Search and Accounting of Assets
- The
management application 22 can search the individual configuration knowledge instances for particular capabilities. For example, themanagement application 22 can search for device capabilities such as hardware and software features of a network device that are no longer being used and are otherwise available. For example, consider the creation of a VPN. This requires dedicating either an interface or a sub-interface of a Physical Port of a network device to host the VPN traffic, along with dedicating logical resources that correspond to creating the instance of the VPN. This enables the network device to forward traffic on the VPN if the traffic is intended for that VPN. One example of a search is to identify components of a VPN. Similarly, if the VPN is subsequently removed, then it is important to reclaim these allocated resources. Thus, a second example of a search is to ensure that the components have been removed. A third example of a search is to ensure that adequate resources for creating the VPN exist before the commands are issued to the device. Themanagement application 22 could also search the configuration knowledge instances for stranded services such as a virtual private network (VPN) that is no longer being used. Similarly, themanagement application 22 could search for software capabilities, physical ports, physical assets, and physical containers. In effect, themanagement application 22 can provide an accurate inventory of the capabilities of a network. Such information can be used for network management, provisioning, and identification of stranded assets. - Support for Versioning of Asset Information
- The
management application 22 can also support versioning of both configuration knowledge and configuration data. For example, multiple versions of configuration data could be associated with a single instance of configuration knowledge. Such versioning is particularly useful for creating different instances of configuration data that can be associated with different customer demands. Versioning is described in more detail with relation toFIG. 3 . - Support for Concurrent Editing of Asset Information
- The
management application 22 can also enable different users to work on different parts of the configuration knowledge and configuration data simultaneously. - Support for Incremental Update to Versioned Asset Information
- The
management application 22 can also track which individual features of a network device are changed and how those changes impact the configuration data. For example, if an updated card was added to a particular router, then the management application could change only the portion of the configuration knowledge corresponding to the updated card. Similarly, only the portion of the configuration instructions corresponding to the changed portion of the configuration knowledge need be changed. - Referring now to
FIG. 3 , it illustrates a versioned configuration knowledge instance and corresponding versions of configuration data. In this embodiment, the configuration knowledge instance is associated with a particular network device and includes versions 1 through 4. The configuration data also corresponds to the network device and includes versions 1.1 through 4.3. Each version of the configuration data instance is associated with at least one of the versions of the configuration knowledge. For example, configuration data V1.1 and V1.2 correspond to configuration knowledge instance V1. Similarly, configuration data instance V2.1 corresponds to configuration knowledge instance V2. - Referring now to
FIG. 4 , it is a block diagram of a system that includesnetwork management applications 40 connected to a centralized configurationknowledge storage device 42 and configurationdata storage device 44. In this embodiment, a plurality ofnetwork management applications 40 are connected to the storage device through anetwork 46. Thestorage devices - When a
network management application 40 needs configuration data about a particular network device or group of network devices, thenetwork management application 40 can access thenetwork device 48 directly and read the relevant information. This process, however, generally requires thenetwork management applications 40 to understand the particular syntax of the network device's configuration. In one embodiment of the present invention, however, thenetwork management application 40 can access thestorage device - Because the configuration knowledge instances are abstractions of the capabilities of the device, the
network management applications 40 generally are not required to understand the device-specific syntax of a particular network device. For example, a physical inventory application could access the configuration knowledge instances for the relevant network devices and determine the cards that are used by each device without regard to the syntax of the actual configuration instructions. - Referring now to
FIG. 5 , it is a flowchart of one method for implementing a roll-back using configuration knowledge instances and versioned configuration data. Roll-backs are often useful for network administrators after network attacks or after unsuccessful network device updates—although they are useful in several other cases. For example, new hardware is often added to existing routers in a network. This new hardware can introduce new capabilities to the router that are reflected in a new version of the router's configuration knowledge instance. Additionally, the configuration data for the router is usually modified to engage the new hardware. Thus, in this type of system upgrade, both the configuration knowledge instance and the configuration data instance for the router are modified. - Assuming that a system upgrade is unsuccessful for some reason, network administrators often wish to roll-back the configuration to a previous, known configuration. For example, if the added card was defective, the network administrator might want to remove the defective card and roll-back the configuration to a configuration based on router that does not include the card. To roll-back the configuration, the assembler or some other device can identify the device [step 50] and a version of the configuration knowledge instance that does not reflect the card's presence [step 52]. The configuration data associated with that version of the configuration knowledge instance can then be identified [step 54] and pushed to the network device [step 56].
- Referring now to
FIG. 6 , it is a flowchart of one method for generating a business object model (BOM) for implementing a specific purpose in a network. In this embodiment, a user or application requests a device configuration to perform a certain function [step 60]. For example, assume that it is desired to create a VPN. The actual list of commands required to accomplish this task vary by vendor and also by version of the operating system that the network device is running. Therefore, in order to provide a single high-level ability to create a VPN, detailed knowledge of the differences in command syntax and semantics must be provided. In various embodiments of this invention, this is done through the use of a BOM, which correlates and assembles the individual knowledge instances. In a preferred embodiment of this invention, there will be many such BOMs, with a BOM for each type of function. Note that the function can be small or large, a command change or a VPN creation being examples of each. For the VPN creation, there will be a set of BOMs that are aggregated into a higher-level BOM. This request is handled by a BOM assembler. The BOM assembler determines which network resources are required to carry out the request [step 62]. The BOM assembler next gathers information from the configuration knowledge instances associated with the identified network resources [step 66]. - Finally, the BOM derives the device configuration from the gathered configuration knowledge instances and generates the actual configuration commands [step 70]. For example, in the configuration of a VPN, the BOM assembler will select appropriate BOMs, aggregate them together, and use the aggregated BOM to derive the appropriate device configuration commands for each device. This enables the device to be programmed at a high functional level, and to have these high-level functions translated to a low-level device-specific implementation. Examples of systems for generating commands are described in commonly owned and assigned U.S. patent application Ser. Nos. 09/730,671, entitled “Dynamic Configuration of Network Devices to Enable Data Transfers,” and 09/730,864, entitled “System and Method for Configuration, Management, and Monitoring of Network Resources,” both of which are incorporated herein by reference. In one embodiment, the device configuration is derived by binding the variable information within the configuration knowledge instances to the business purpose of the customer. For example, a QoS business purpose could be bound to the various traffic conditioning settings.
- In conclusion, the present invention provides, among other things, a system and method for managing and utilizing network device configurations. Those skilled in the art can readily recognize that numerous variations and substitutions may be made in the invention, its use and its configuration to achieve substantially the same results as achieved by the embodiments described herein. Accordingly, there is no intention to limit the invention to the disclosed exemplary forms. Many variations, modifications and alternative constructions fall within the scope and spirit of the disclosed invention as expressed in the claims.
Claims (5)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/236,609 US20090019139A1 (en) | 2002-07-11 | 2008-09-24 | Repository-Independent System and Method for Asset Management and Reconciliation |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US39569802P | 2002-07-11 | 2002-07-11 | |
US10/617,420 US7464145B2 (en) | 2002-07-11 | 2003-07-10 | Repository-independent system and method for asset management and reconciliation |
US12/236,609 US20090019139A1 (en) | 2002-07-11 | 2008-09-24 | Repository-Independent System and Method for Asset Management and Reconciliation |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/617,420 Continuation US7464145B2 (en) | 2002-07-11 | 2003-07-10 | Repository-independent system and method for asset management and reconciliation |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090019139A1 true US20090019139A1 (en) | 2009-01-15 |
Family
ID=30115916
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/617,420 Expired - Fee Related US7464145B2 (en) | 2002-07-11 | 2003-07-10 | Repository-independent system and method for asset management and reconciliation |
US12/236,605 Abandoned US20090019138A1 (en) | 2002-07-11 | 2008-09-24 | Repository-Independent System and Method for Asset Management and Reconciliation |
US12/236,609 Abandoned US20090019139A1 (en) | 2002-07-11 | 2008-09-24 | Repository-Independent System and Method for Asset Management and Reconciliation |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/617,420 Expired - Fee Related US7464145B2 (en) | 2002-07-11 | 2003-07-10 | Repository-independent system and method for asset management and reconciliation |
US12/236,605 Abandoned US20090019138A1 (en) | 2002-07-11 | 2008-09-24 | Repository-Independent System and Method for Asset Management and Reconciliation |
Country Status (3)
Country | Link |
---|---|
US (3) | US7464145B2 (en) |
AU (1) | AU2003251881A1 (en) |
WO (1) | WO2004008283A2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050144610A1 (en) * | 2003-12-30 | 2005-06-30 | Ingo Zenz | Configuration manager in enterprise computing system |
US20050188021A1 (en) * | 2003-12-30 | 2005-08-25 | Hans-Christoph Rohland | Cluster architecture having a star topology with centralized services |
US20090019138A1 (en) * | 2002-07-11 | 2009-01-15 | John Strassner | Repository-Independent System and Method for Asset Management and Reconciliation |
US20140047085A1 (en) * | 2011-08-16 | 2014-02-13 | Edgecast Networks, Inc. | Configuration Management Repository for a Distributed Platform |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7307979B2 (en) * | 2002-07-31 | 2007-12-11 | Jeremy Benjamin As Receiver For Chiaro Networks Ltd | Configuration rollback |
US8601099B1 (en) | 2003-12-30 | 2013-12-03 | Sap Ag | System and method for managing multiple sever node clusters using a hierarchical configuration data structure |
US7533163B1 (en) | 2003-12-30 | 2009-05-12 | Sap Ag | Startup framework and method for enterprise computing systems |
US8312045B2 (en) * | 2003-12-30 | 2012-11-13 | Sap Ag | Configuration data content for a clustered system having multiple instances |
US7519600B1 (en) | 2003-12-30 | 2009-04-14 | Sap Aktiengesellschaft | System and method for managing multiple application server clusters using a hierarchical data object and a multi-parameter representation for each configuration property |
FI20040978A0 (en) * | 2004-07-13 | 2004-07-13 | Nokia Corp | System, Method, Web Objects, and Computer Programs to Manage Dynamic Host Configuration Policy Frame Configuration |
US20070064603A1 (en) * | 2005-09-19 | 2007-03-22 | Sean Chen | Method of provisioning network elements to perform a service |
GB2431067B (en) | 2005-10-07 | 2008-05-07 | Cramer Systems Ltd | Telecommunications service management |
GB2432992B (en) * | 2005-11-18 | 2008-09-10 | Cramer Systems Ltd | Network planning |
WO2007057685A2 (en) * | 2005-11-18 | 2007-05-24 | Cramer Systems Limited | Architecture for operational support system |
GB2433675B (en) | 2005-12-22 | 2008-05-07 | Cramer Systems Ltd | Communications circuit design |
GB2435362B (en) | 2006-02-20 | 2008-11-26 | Cramer Systems Ltd | Method of configuring devices in a telecommunications network |
US20070288467A1 (en) * | 2006-06-07 | 2007-12-13 | Motorola, Inc. | Method and apparatus for harmonizing the gathering of data and issuing of commands in an autonomic computing system using model-based translation |
US8086701B2 (en) * | 2008-04-28 | 2011-12-27 | Microsoft Corporation | Platform for managing and configuring network state |
US8606925B2 (en) | 2011-04-04 | 2013-12-10 | International Business Machines Corporation | Automatic generation of reusable network configuration objects |
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 |
US9558454B2 (en) | 2013-03-14 | 2017-01-31 | Futurewei Technologies, Inc. | System and method for model-based inventory management of a communications system |
US9602380B2 (en) | 2014-03-28 | 2017-03-21 | Futurewei Technologies, Inc. | Context-aware dynamic policy selection for load balancing behavior |
US9450895B2 (en) | 2014-03-28 | 2016-09-20 | Futurewei Technologies, Inc. | Context-aware dynamic policy selection for messaging behavior |
US10013414B2 (en) | 2014-08-20 | 2018-07-03 | Futurewei Technologies, Inc. | System and method for metadata enhanced inventory management of a communications system |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6170009B1 (en) * | 1998-07-17 | 2001-01-02 | Kallol Mandal | Controlling devices on a network through policies |
US6226788B1 (en) * | 1998-07-22 | 2001-05-01 | Cisco Technology, Inc. | Extensible network management system |
US6243747B1 (en) * | 1995-02-24 | 2001-06-05 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US20020049749A1 (en) * | 2000-01-14 | 2002-04-25 | Chris Helgeson | Method and apparatus for a business applications server management system platform |
US6463470B1 (en) * | 1998-10-26 | 2002-10-08 | Cisco Technology, Inc. | Method and apparatus of storing policies for policy-based management of quality of service treatments of network data traffic flows |
US6505244B1 (en) * | 1999-06-29 | 2003-01-07 | Cisco Technology Inc. | Policy engine which supports application specific plug-ins for enforcing policies in a feedback-based, adaptive data network |
US6539425B1 (en) * | 1999-07-07 | 2003-03-25 | Avaya Technology Corp. | Policy-enabled communications networks |
US20030074430A1 (en) * | 2001-10-05 | 2003-04-17 | Gieseke Eric James | Object oriented provisioning server object model |
US20030195921A1 (en) * | 2002-03-19 | 2003-10-16 | Becker Brian Eric | System and method for configurable software provisioning |
US6760761B1 (en) * | 2000-03-27 | 2004-07-06 | Genuity Inc. | Systems and methods for standardizing network devices |
US6799208B1 (en) * | 2000-05-02 | 2004-09-28 | Microsoft Corporation | Resource manager architecture |
US6832247B1 (en) * | 1998-06-15 | 2004-12-14 | Hewlett-Packard Development Company, L.P. | Method and apparatus for automatic monitoring of simple network management protocol manageable devices |
US6983317B1 (en) * | 2000-02-28 | 2006-01-03 | Microsoft Corporation | Enterprise management system |
US7630877B2 (en) * | 2003-03-06 | 2009-12-08 | Microsoft Corporation | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
Family Cites Families (166)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US147186A (en) * | 1874-02-03 | Improvement in morse telegraph-registers | ||
US147185A (en) * | 1874-02-03 | Improvement in devices for loading lumber, iron bars | ||
US810755A (en) * | 1905-06-15 | 1906-01-23 | Nels Hegg | Horseshoe-calk. |
US993725A (en) * | 1909-12-07 | 1911-05-30 | Union Typewriter Co | Type-writing machine. |
US1026867A (en) * | 1911-06-05 | 1912-05-21 | John W Staub | Lubricator. |
US1091526A (en) * | 1912-05-23 | 1914-03-31 | Henry A Vreeland | Grease-proof paper vessel. |
US1090492A (en) * | 1913-05-12 | 1914-03-17 | Oscar Onsrud | Core-drum. |
US2313164A (en) * | 1939-11-13 | 1943-03-09 | Walfred A Nelson | Self-retaining surgical retractor |
US2368692A (en) * | 1943-01-22 | 1945-02-06 | Donald A Wallance | Tent pole |
US3035477A (en) * | 1950-02-01 | 1962-05-22 | United Aircraft Corp | Apparatus for stabilizing optical sighting systems |
US3378326A (en) * | 1963-09-12 | 1968-04-16 | Bell & Howell Co | Gyroscopically controlled accidental motion compensator for optical instruments |
FR1439999A (en) * | 1965-04-08 | 1966-05-27 | Device ensuring the stabilization and control of a line of sight, by means of two mirrors or two prisms associated with a free gyroscope, or an equivalent system | |
US3437397A (en) * | 1966-09-14 | 1969-04-08 | Optical Res & Dev Corp | Double-mirror system for optical stabilization |
US3504957A (en) * | 1967-08-08 | 1970-04-07 | Trw Inc | Optical stabilized telescope arrangement |
FR1549505A (en) * | 1967-10-31 | 1968-12-13 | ||
US4256279A (en) * | 1978-11-03 | 1981-03-17 | Motorola, Inc. | Powered gimbal system |
US4573448A (en) * | 1983-10-05 | 1986-03-04 | Pilling Co. | Method for decompressing herniated intervertebral discs |
CA1261653A (en) * | 1986-10-23 | 1989-09-26 | John N. Leavitt | Steerable windowed enclosures |
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 |
US4989466A (en) * | 1989-08-02 | 1991-02-05 | Goodman Ronald C | Gyroscopically stabilized sensor positioning system |
US5159685A (en) | 1989-12-06 | 1992-10-27 | Racal Data Communications Inc. | Expert system for communications network |
DE69132279T2 (en) * | 1990-09-17 | 2001-01-18 | Cabletron Systems Inc | Procedure for isolating a network fault |
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 |
US5395317A (en) * | 1991-10-30 | 1995-03-07 | Smith & Nephew Dyonics, Inc. | Unilateral biportal percutaneous surgical procedure |
JP3130609B2 (en) * | 1991-12-17 | 2001-01-31 | 日本電気株式会社 | Online information processing equipment |
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 |
US5329619A (en) | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
US5535335A (en) | 1992-12-22 | 1996-07-09 | International Business Machines Corporation | Method and system for reporting the status of an aggregate resource residing in a network of interconnected real resources |
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 |
IL111154A0 (en) | 1993-10-21 | 1994-12-29 | Martino Ii John A | Systems and methods for electronic messaging |
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 |
DE69325398T2 (en) * | 1993-12-24 | 2000-01-20 | Ibm | FORWARDING BANDWIDTH-RESERVED CONNECTIONS IN INFORMATION NETWORKS |
US5519704A (en) * | 1994-04-21 | 1996-05-21 | Cisco Systems, Inc. | Reliable transport protocol for internetwork routing |
US5631536A (en) * | 1994-05-16 | 1997-05-20 | Tseng; Ling-Yuan | Rechargeable battery vending apparatus |
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 |
AU3965595A (en) * | 1994-10-25 | 1996-05-15 | Cabletron Systems, Inc. | Method and apparatus for automatically populating a network simulator tool |
US5491820A (en) | 1994-11-10 | 1996-02-13 | At&T Corporation | Distributed, intermittently connected, object-oriented database and management system |
US6365495B2 (en) * | 1994-11-14 | 2002-04-02 | Applied Materials, Inc. | Method for performing metallo-organic chemical vapor deposition of titanium nitride at reduced temperature |
US6699530B2 (en) * | 1995-07-06 | 2004-03-02 | Applied Materials, Inc. | Method for constructing a film on a semiconductor wafer |
US20020033533A1 (en) * | 1994-11-14 | 2002-03-21 | Marvin Liao | Interconnect structure for use in an integrated circuit |
US5659746A (en) | 1994-12-30 | 1997-08-19 | Aegis Star Corporation | Method for storing and retrieving digital data transmissions |
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 |
US5868031A (en) * | 1995-02-07 | 1999-02-09 | Anatoliy Kokush | Triaxial gyroscopic stabilizer for movie or television camera |
US5832503A (en) | 1995-02-24 | 1998-11-03 | Cabletron Systems, Inc. | Method and apparatus for configuration management in communications networks |
US5594318A (en) * | 1995-04-10 | 1997-01-14 | Norvik Traction Inc. | Traction battery charging with inductive coupling |
US5889953A (en) * | 1995-05-25 | 1999-03-30 | Cabletron Systems, Inc. | Policy management and conflict resolution in computer networks |
US5751150A (en) * | 1995-08-11 | 1998-05-12 | Aerovironment | Bidirectional load and source cycler |
US5889943A (en) * | 1995-09-26 | 1999-03-30 | Trend Micro Incorporated | Apparatus and method for electronic mail virus detection and elimination |
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 |
US5819042A (en) | 1996-02-20 | 1998-10-06 | Compaq Computer Corporation | Method and apparatus for guided configuration of unconfigured network and internetwork devices |
US5751965A (en) * | 1996-03-21 | 1998-05-12 | Cabletron System, Inc. | Network connection status monitor and display |
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 |
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 |
US5923850A (en) | 1996-06-28 | 1999-07-13 | Sun Microsystems, Inc. | Historical asset information data storage schema |
US5802530A (en) * | 1996-07-01 | 1998-09-01 | Sun Microsystems, Inc. | Web document based graphical user interface |
JP3224745B2 (en) * | 1996-07-09 | 2001-11-05 | 株式会社日立製作所 | High reliability network system and server switching method |
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 |
US5878432A (en) * | 1996-10-29 | 1999-03-02 | International Business Machines Corporation | Object oriented framework mechanism for a source code repository |
US5871249A (en) * | 1996-11-12 | 1999-02-16 | Williams; John H. | Stable positioning system for suspended loads |
JP3409983B2 (en) * | 1996-11-29 | 2003-05-26 | 富士通株式会社 | Communications system |
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 |
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 |
GB9707550D0 (en) | 1997-04-15 | 1997-06-04 | British Telecomm | Design of computer networks |
US6243815B1 (en) | 1997-04-25 | 2001-06-05 | Anand K. Antur | Method and apparatus for reconfiguring and managing firewalls and security devices |
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 |
US6571290B2 (en) * | 1997-06-19 | 2003-05-27 | Mymail, Inc. | Method and apparatus for providing fungible intercourse over a network |
CN1117462C (en) * | 1997-06-25 | 2003-08-06 | 三星电子株式会社 | Method and apparatus for home network auto-tree builder |
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 |
US6175758B1 (en) * | 1997-07-15 | 2001-01-16 | Parviz Kambin | Method for percutaneous arthroscopic disc removal, bone biopsy and fixation of the vertebrae |
US6101508A (en) | 1997-08-01 | 2000-08-08 | Hewlett-Packard Company | Clustered file management for network resources |
US6085253A (en) | 1997-08-01 | 2000-07-04 | United Video Properties, Inc. | System and method for transmitting and receiving data |
US20020007411A1 (en) * | 1998-08-10 | 2002-01-17 | Shvat Shaked | Automatic network user identification |
US6104700A (en) | 1997-08-29 | 2000-08-15 | Extreme Networks | Policy based quality of service |
US5999948A (en) | 1997-09-03 | 1999-12-07 | 3Com Corporation | Dynamic configuration forms in network management software |
US6028846A (en) | 1997-09-11 | 2000-02-22 | U S West, Inc. | Method and system for testing real-time delivery of packets of data |
JPH1196892A (en) * | 1997-09-17 | 1999-04-09 | Nec Corp | Field emitter |
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 |
US6253240B1 (en) | 1997-10-31 | 2001-06-26 | International Business Machines Corporation | Method for producing a coherent view of storage network by a storage network manager using data storage device configuration obtained from data storage devices |
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 |
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 |
US6088804A (en) | 1998-01-12 | 2000-07-11 | Motorola, Inc. | Adaptive system and method for responding to computer network security attacks |
US6426959B1 (en) | 1998-01-20 | 2002-07-30 | Innovative Communications Technologies, Inc. | System and method for facilitating component management in a multiple vendor satellite communications network |
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 |
US6363421B2 (en) * | 1998-05-31 | 2002-03-26 | Lucent Technologies, Inc. | Method for computer internet remote management of a telecommunication network element |
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 |
US6097697A (en) | 1998-07-17 | 2000-08-01 | Sitara Networks, Inc. | Congestion control |
US6211877B1 (en) * | 1998-07-20 | 2001-04-03 | Hewlett-Packard Co | Method for communicating between programming language controlled frames and CGI/HTML controlled frames within the same browser window |
US6338149B1 (en) * | 1998-07-31 | 2002-01-08 | Westinghouse Electric Company Llc | Change monitoring system for a computer system |
US6286038B1 (en) | 1998-08-03 | 2001-09-04 | Nortel Networks Limited | Method and apparatus for remotely configuring a network device |
US6530926B1 (en) * | 2000-08-01 | 2003-03-11 | Endius Incorporated | Method of securing vertebrae |
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 |
US6546416B1 (en) * | 1998-12-09 | 2003-04-08 | Infoseek Corporation | Method and system for selectively blocking delivery of bulk electronic mail |
US6615257B2 (en) * | 1998-12-18 | 2003-09-02 | Cisco Technology, Inc. | Secure multi-user cable modem configuration editor and viewer |
US6240458B1 (en) * | 1998-12-22 | 2001-05-29 | Unisys Corporation | System and method for programmably controlling data transfer request rates between data sources and destinations in a data processing system |
US6272526B1 (en) | 1999-01-07 | 2001-08-07 | Iq Netsolutions, Inc. | Distributed processing systems having self-advertising cells |
US6024697A (en) * | 1999-01-11 | 2000-02-15 | Pisarik; Paul | Multi-bladed speculum for dilating a body cavity |
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 |
US6381631B1 (en) * | 1999-06-03 | 2002-04-30 | Marimba, Inc. | Method and apparatus for controlling client computer systems |
US6564056B1 (en) * | 1999-08-03 | 2003-05-13 | Avaya Technology Corp. | Intelligent device controller |
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 |
US6678370B1 (en) * | 1999-09-21 | 2004-01-13 | Verizon Laboratories Inc. | Data extraction process |
US6684241B1 (en) * | 1999-09-29 | 2004-01-27 | Nortel Networks Limited | Apparatus and method of configuring a network device |
US7003560B1 (en) * | 1999-11-03 | 2006-02-21 | Accenture Llp | Data warehouse computing system |
US6990591B1 (en) * | 1999-11-18 | 2006-01-24 | Secureworks, Inc. | Method and system for remotely configuring and monitoring a communication device |
JP3436906B2 (en) * | 1999-12-10 | 2003-08-18 | パナソニック コミュニケーションズ株式会社 | Error notification device and error notification method |
US6571285B1 (en) * | 1999-12-23 | 2003-05-27 | Accenture Llp | Providing an integrated service assurance environment for a network |
US6361488B1 (en) * | 2000-01-28 | 2002-03-26 | Endius Incorporated | Support apparatus for endoscopic surgery |
US6725264B1 (en) * | 2000-02-17 | 2004-04-20 | Cisco Technology, Inc. | Apparatus and method for redirection of network management messages in a cluster of network devices |
US6865673B1 (en) * | 2000-03-21 | 2005-03-08 | 3Com Corporation | Method for secure installation of device in packet based communication network |
US6732175B1 (en) * | 2000-04-13 | 2004-05-04 | Intel Corporation | Network apparatus for switching based on content of application data |
US6725262B1 (en) * | 2000-04-27 | 2004-04-20 | Microsoft Corporation | Methods and systems for synchronizing multiple computing devices |
US7034864B2 (en) * | 2000-05-19 | 2006-04-25 | Canon Kabushiki Kaisha | Image display apparatus, image display system, and image display method |
US7056321B2 (en) * | 2000-08-01 | 2006-06-06 | Endius, Incorporated | Method of securing vertebrae |
DE20013399U1 (en) * | 2000-08-03 | 2000-11-02 | Chai Wellmon | Charging station for electrically powered vehicles |
US20020032775A1 (en) * | 2000-08-28 | 2002-03-14 | Ramesh Venkataramaiah | System and method for transmitting and retrieving data via a distributed persistence framework |
JP2002065629A (en) * | 2000-09-01 | 2002-03-05 | Tanita Corp | Living body impedance measuring device |
US20020032871A1 (en) * | 2000-09-08 | 2002-03-14 | The Regents Of The University Of Michigan | Method and system for detecting, tracking and blocking denial of service attacks over a computer network |
US6938079B1 (en) * | 2000-09-19 | 2005-08-30 | 3Com Corporation | System and method for automatically configuring a client device |
WO2002027438A2 (en) * | 2000-09-28 | 2002-04-04 | Vigilos, Inc. | Method and process for configuring a premises for monitoring |
US7254641B2 (en) * | 2001-01-30 | 2007-08-07 | Intervoice, Inc. | Digital multimedia contact center with tier escalation and deescalation in response to changed criteria |
GB2372672B (en) * | 2001-02-27 | 2003-04-30 | 3Com Corp | Network management apparatus and method for processing events associated with device reboot |
US6530880B2 (en) * | 2001-03-29 | 2003-03-11 | Endius Incorporated | Apparatus for supporting an endoscope |
JP3905714B2 (en) * | 2001-04-02 | 2007-04-18 | 矢崎総業株式会社 | Waterproof connector holder and method of manufacturing the same |
US20030065919A1 (en) * | 2001-04-18 | 2003-04-03 | Albert Roy David | Method and system for identifying a replay attack by an access device to a computer system |
US7278143B2 (en) * | 2001-06-28 | 2007-10-02 | Microsoft Corporation | System and related methods for accessing management functionality through a command line utility |
US7170900B2 (en) * | 2001-07-13 | 2007-01-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for scheduling message processing |
US20030061312A1 (en) * | 2001-09-26 | 2003-03-27 | Bodner James T. | Reduction of configuration time upon deployment of a configurable device in a shared resource environment |
US7275048B2 (en) * | 2001-10-30 | 2007-09-25 | International Business Machines Corporation | Product support of computer-related products using intelligent agents |
CA2476865A1 (en) * | 2002-02-22 | 2003-09-04 | Iplocks, Inc. | Method and apparatus for monitoring a database system |
US7272144B2 (en) * | 2002-06-26 | 2007-09-18 | Arris International, Inc. | Method and apparatus for queuing data flows |
US20040003067A1 (en) * | 2002-06-27 | 2004-01-01 | Daniel Ferrin | System and method for enabling a user interface with GUI meta data |
US7464145B2 (en) * | 2002-07-11 | 2008-12-09 | Intelliden, Inc. | Repository-independent system and method for asset management and reconciliation |
-
2003
- 2003-07-10 US US10/617,420 patent/US7464145B2/en not_active Expired - Fee Related
- 2003-07-11 AU AU2003251881A patent/AU2003251881A1/en not_active Abandoned
- 2003-07-11 WO PCT/US2003/021846 patent/WO2004008283A2/en not_active Application Discontinuation
-
2008
- 2008-09-24 US US12/236,605 patent/US20090019138A1/en not_active Abandoned
- 2008-09-24 US US12/236,609 patent/US20090019139A1/en not_active Abandoned
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6243747B1 (en) * | 1995-02-24 | 2001-06-05 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US6832247B1 (en) * | 1998-06-15 | 2004-12-14 | Hewlett-Packard Development Company, L.P. | Method and apparatus for automatic monitoring of simple network management protocol manageable devices |
US6170009B1 (en) * | 1998-07-17 | 2001-01-02 | Kallol Mandal | Controlling devices on a network through policies |
US6226788B1 (en) * | 1998-07-22 | 2001-05-01 | Cisco Technology, Inc. | Extensible network management system |
US6463470B1 (en) * | 1998-10-26 | 2002-10-08 | Cisco Technology, Inc. | Method and apparatus of storing policies for policy-based management of quality of service treatments of network data traffic flows |
US6505244B1 (en) * | 1999-06-29 | 2003-01-07 | Cisco Technology Inc. | Policy engine which supports application specific plug-ins for enforcing policies in a feedback-based, adaptive data network |
US6539425B1 (en) * | 1999-07-07 | 2003-03-25 | Avaya Technology Corp. | Policy-enabled communications networks |
US20020049749A1 (en) * | 2000-01-14 | 2002-04-25 | Chris Helgeson | Method and apparatus for a business applications server management system platform |
US6983317B1 (en) * | 2000-02-28 | 2006-01-03 | Microsoft Corporation | Enterprise management system |
US6760761B1 (en) * | 2000-03-27 | 2004-07-06 | Genuity Inc. | Systems and methods for standardizing network devices |
US6799208B1 (en) * | 2000-05-02 | 2004-09-28 | Microsoft Corporation | Resource manager architecture |
US20030074430A1 (en) * | 2001-10-05 | 2003-04-17 | Gieseke Eric James | Object oriented provisioning server object model |
US20030195921A1 (en) * | 2002-03-19 | 2003-10-16 | Becker Brian Eric | System and method for configurable software provisioning |
US7630877B2 (en) * | 2003-03-06 | 2009-12-08 | Microsoft Corporation | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090019138A1 (en) * | 2002-07-11 | 2009-01-15 | John Strassner | Repository-Independent System and Method for Asset Management and Reconciliation |
US20050144610A1 (en) * | 2003-12-30 | 2005-06-30 | Ingo Zenz | Configuration manager in enterprise computing system |
US20050188021A1 (en) * | 2003-12-30 | 2005-08-25 | Hans-Christoph Rohland | Cluster architecture having a star topology with centralized services |
US7526479B2 (en) * | 2003-12-30 | 2009-04-28 | Sap Ag | Configuration manager in enterprise computing system |
US8190780B2 (en) | 2003-12-30 | 2012-05-29 | Sap Ag | Cluster architecture having a star topology with centralized services |
US20140047085A1 (en) * | 2011-08-16 | 2014-02-13 | Edgecast Networks, Inc. | Configuration Management Repository for a Distributed Platform |
US9009277B2 (en) * | 2011-08-16 | 2015-04-14 | Edgecast Networks, Inc. | Configuration management repository for a distributed platform |
Also Published As
Publication number | Publication date |
---|---|
WO2004008283A2 (en) | 2004-01-22 |
AU2003251881A1 (en) | 2004-02-02 |
US7464145B2 (en) | 2008-12-09 |
AU2003251881A8 (en) | 2004-02-02 |
US20040148369A1 (en) | 2004-07-29 |
WO2004008283A3 (en) | 2004-04-08 |
US20090019138A1 (en) | 2009-01-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20090019139A1 (en) | Repository-Independent System and Method for Asset Management and Reconciliation | |
US20080059613A1 (en) | System and Method for Enabling Directory-Enabled Networking | |
US6714949B1 (en) | Dynamic file system configurations | |
JP4416821B2 (en) | A distributed file system that maintains a fileset namespace accessible to clients over the network | |
US6408434B1 (en) | System and method for using a substitute directory to automatically install an update program | |
CN101836186B (en) | A method and system for communicating between isolation environments | |
US7171459B2 (en) | Method and apparatus for handling policies in an enterprise | |
US6782389B1 (en) | Distributing files across multiple, permissibly heterogeneous, storage devices | |
US6886017B1 (en) | System and method for managing distribution of content to a device | |
US6289375B1 (en) | Method and apparatus for invoking network agent functions using a hash table | |
EP1589691B1 (en) | Method, system and apparatus for managing computer identity | |
US20070078914A1 (en) | Method, apparatus and program storage device for providing a centralized policy based preallocation in a distributed file system | |
US20020087665A1 (en) | Method and system for integrated resource management | |
US20130297902A1 (en) | Virtual data center | |
US20020019864A1 (en) | System and method for managing the configuration of hierarchically networked data processing devices | |
EP1039380A2 (en) | Method and data format for exchanging data between a java system database entry and an ldap directory | |
US7921419B2 (en) | Method and mechanism for managing incompatible changes in a distributed system | |
US20040059813A1 (en) | Methods and apparatus for configuration change management in communications networks | |
US7325017B2 (en) | Method of implementation of data storage quota | |
US7216184B2 (en) | System and method for identification of devices associated with input/output paths | |
CN111684437B (en) | Staggered update key-value storage system ordered by time sequence | |
US8719768B2 (en) | Accretion of inter-namespace instances in multi-tenant CIMOM environment | |
CN100468405C (en) | Methods, systems, and computer programs for storing device information | |
US20080208797A1 (en) | Automated record attribute value merging from multiple directory servers | |
US7610584B2 (en) | Method, system, and product for defining and managing provisioning states for resources in provisioning data processing systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTELLIDEN, INC., COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STRASSNER, JOHN;REEL/FRAME:021578/0040 Effective date: 20040308 |
|
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: GAFFNEY, ROBERT P., COLORADO 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: SNOWS HILL, LLC, 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: WESTON & CO. VI, LLC, MASSACHUSETTS 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: KOOKABURRA LLC, NEW YORK 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: 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: VOS, REMKO, CALIFORNIA 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 Owner name: GERDELMAN, SUE & JOHN, VIRGINIA 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 PARTNERS VI, L.P., 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: GRANITE GLOBAL VENTURES II L.P., CALIFORNIA 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 |
|
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 |
|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLIDEN, INC.;REEL/FRAME:024906/0572 Effective date: 20100727 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |