CA2404191A1 - Methods and apparatus for configuration change management in communications networks - Google Patents
Methods and apparatus for configuration change management in communications networks Download PDFInfo
- Publication number
- CA2404191A1 CA2404191A1 CA002404191A CA2404191A CA2404191A1 CA 2404191 A1 CA2404191 A1 CA 2404191A1 CA 002404191 A CA002404191 A CA 002404191A CA 2404191 A CA2404191 A CA 2404191A CA 2404191 A1 CA2404191 A1 CA 2404191A1
- Authority
- CA
- Canada
- Prior art keywords
- configuration
- communications network
- command
- network entity
- repository
- 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
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
-
- 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
Abstract
A configuration change management system is provided. The configuration change management system includes a configuration information repository and a human-machine interface for interacting with field-installed communications network entities and versions of communications network entity specific configuration information stored in repository entries.
Methods of managing configuration changes include: retrieving configuration information from communications network entities; storing thereof under version control in repository entries; comparing at least one retrieved repository entry from the configuration change management repository; and retrieved configuration information from field-installed communications network entities; and submitting, for reconfiguration, of at least one field installed communications network entity selected configuration information held in a selected repository entry. Advantages are derived from: a centralized tracking and storage of configuration information under version control, and the ability to compare versions of communications network entity configurations, reducing equipment downtime at reduced communications network management overheads. Further advantages are derived from an efficient method of debugging communications network entity configuration problems.
The methods and system further enable easy migration of communications network entities to newer software/firmware releases, and provisioning a replacement communications network equipment.
Methods of managing configuration changes include: retrieving configuration information from communications network entities; storing thereof under version control in repository entries; comparing at least one retrieved repository entry from the configuration change management repository; and retrieved configuration information from field-installed communications network entities; and submitting, for reconfiguration, of at least one field installed communications network entity selected configuration information held in a selected repository entry. Advantages are derived from: a centralized tracking and storage of configuration information under version control, and the ability to compare versions of communications network entity configurations, reducing equipment downtime at reduced communications network management overheads. Further advantages are derived from an efficient method of debugging communications network entity configuration problems.
The methods and system further enable easy migration of communications network entities to newer software/firmware releases, and provisioning a replacement communications network equipment.
Description
Methods and Apparatus for Configuration Change Management in Communications Networks Field of the invention The invention relates to communications network management, and in particular to methods and apparatus for managing configuration changes.
Background of the invention With regards to communications network equipment, for example data switching nodes schematically shown in FIG.1, a communications equipment vendor may chose to implement an integral communications network node device 122X having a data switching processor operable to switch data packets between a group of ports 102, while another communications equipment vendor may chose a customizable implementation of a switching node 112Y
including: a switching fabric, an equipment rack divided into shelves 122, each shelf 122 having slot connectors for connection with interface cards 124, each interface card 124 having at least one port 102. Physical transport links 108 are connected between ports 102.
Although conceptually the two the switching nodes 112X and 112Y provide a similar switching function, each communications equipment implementation is adapted for a different environment: the former switching node 112X is more adapted to enterprise solutions as a private communications network node, perhaps further adapted to be connected to carrier communications networks 100; while the latter switching node 112Y is better adapted for high data throughput in the core of public communications networks 100. Typically the former 112X implements a small number of data transport protocols while for the latter 112Y, data transport protocols are implemented on interface cards and/or ports 102 - providing fox a flexible/configurable deployment thereof.
Communications network nodes 112 which are data switching nodes (122X/122Y) may provide routing of the traffic conveyed. The integral switching node 112X as mentioned above is operable as a routing device 106, while the switching node 112Y may have at least one virtual muter 106 associated therewith. Other data network nodes 1122 may be distinct from an associated router 106. The latter configuration is typically found customer owned Local Area Network (LAN) segments.
It is understood that the interconnected physical communications network equipment alluded to above is part of larger body of managed communications network entities enabling the provision of communications services. The data network entities also include, but are not limited to: logical ports, logical interfaces, etc.
Connectivity information, configuration information, service support information, etc. regardless of its origin is held by communications network entities in the realm of management of a network management solution.
Suffice it to say that, the modification of: the connectivity information, configuration information, service support information, etc. leads to an optimization of the operation of a communications network; and incorrect modifications thereof leads to communications network failures.
The connectivity information, configuration information, service support information, etc. is provided to communications network entities using element management techniques and tools typically including the use of Command Line Interface (CLI) commands. A command line interface is a command driven text based user interface to a communications network entity.
Think configuration command snapshot!
Background of the invention With regards to communications network equipment, for example data switching nodes schematically shown in FIG.1, a communications equipment vendor may chose to implement an integral communications network node device 122X having a data switching processor operable to switch data packets between a group of ports 102, while another communications equipment vendor may chose a customizable implementation of a switching node 112Y
including: a switching fabric, an equipment rack divided into shelves 122, each shelf 122 having slot connectors for connection with interface cards 124, each interface card 124 having at least one port 102. Physical transport links 108 are connected between ports 102.
Although conceptually the two the switching nodes 112X and 112Y provide a similar switching function, each communications equipment implementation is adapted for a different environment: the former switching node 112X is more adapted to enterprise solutions as a private communications network node, perhaps further adapted to be connected to carrier communications networks 100; while the latter switching node 112Y is better adapted for high data throughput in the core of public communications networks 100. Typically the former 112X implements a small number of data transport protocols while for the latter 112Y, data transport protocols are implemented on interface cards and/or ports 102 - providing fox a flexible/configurable deployment thereof.
Communications network nodes 112 which are data switching nodes (122X/122Y) may provide routing of the traffic conveyed. The integral switching node 112X as mentioned above is operable as a routing device 106, while the switching node 112Y may have at least one virtual muter 106 associated therewith. Other data network nodes 1122 may be distinct from an associated router 106. The latter configuration is typically found customer owned Local Area Network (LAN) segments.
It is understood that the interconnected physical communications network equipment alluded to above is part of larger body of managed communications network entities enabling the provision of communications services. The data network entities also include, but are not limited to: logical ports, logical interfaces, etc.
Connectivity information, configuration information, service support information, etc. regardless of its origin is held by communications network entities in the realm of management of a network management solution.
Suffice it to say that, the modification of: the connectivity information, configuration information, service support information, etc. leads to an optimization of the operation of a communications network; and incorrect modifications thereof leads to communications network failures.
The connectivity information, configuration information, service support information, etc. is provided to communications network entities using element management techniques and tools typically including the use of Command Line Interface (CLI) commands. A command line interface is a command driven text based user interface to a communications network entity.
Think configuration command snapshot!
The invention addresses the ability to provide more visibility to a router's configuration, particularly because Different vendor equipment uses a different CLI command set, which makes it difficult for an operator obtain and manipulate configuration information in a multi-vendor deployment of a communications network. Configuration changes are usually made using scripts of CLI commands, while it is very common for configuration changes to be made manually by entering the CLI
commands via a console. Script-based and manual entry of CLI commands to change communications network entity configuration make it difficult to keep track of configuration changes.
The configuration of a communications network entity tends to change over time, for example due to software upgrades, firmware upgrades, hardware upgrades, new service/capacity provisioning, etc. It is often useful to track the changes made to the configuration of a communications network entity in case there is a need to return to a previous configuration, for example to remove a problem caused by a configuration change.
In the prior art it is known to perform "baselining" on a router's configuration:
a record is kept of the router's initial configuration. The initial configuration is then used as a template to which further changes are made. The Wide Area Network Design Laboratory (WANDL)Inc. providestool known as a the Internet ProtocolAnalysis Tool (IPAT)for performingbaselining on Cisco Systems routers.IPAT makes use of "configlets",which are router configuration scripts, to make configuration changes to a router.
It is also known in the prior art to store CLI command configuration scripts run on a router to effect configuration changes to it. Prior practice includes naming CLI command configuration scripts run on a router with descriptions specifying what changes were made. Communications network entities usually have at least one vendor specific CLI command or a specific CLI command sequence providing for retrieval of configuration information therefrom. This configuration information may be stored in a file. However, means to manage these retrieved configuration files are not known in the prior art.
Although descriptively naming "configlets" and CLI command configuration scripts of the prior art provide limited tracking of configuration changes made to a communications network entity, it does not provide any tracking of manual the configuration changes made thereto. Therefore, simply knowing the changes that were made to a communications network entity is not sufficient in tracking communications network entity configuration. The result is: an increased overhead in the management of communications networks, an over reliance of highly trained analysts, misuse of the capabilities of highly trained analysts in fixing configuration changes.
There therefore is a need to address the above mentioned issues in providing configuration change management solutions reducing network management operational overheads.
Summar3r of the invent~i on In accordance with an aspect of the invention, a configuration change management system is provided. The configuration change management system includes: means for receiving configuration information from at least one communications network entity; a configuration repository for storing version controlled snapshots of configuration information in configuration repository entries; and a comparator comparing at least two configuration snapshots. The configuration repository provides storage of configuration information of communications network entities in a realm of management of a network management solution. The comparator enables configuration change management to be effected.
In accordance with another aspect of the invention, the configuration change management system further includes a human-machine interface to enable an operator to interact with version controlled configuration information and in particular to perform operations on configuration command snapshots.
In accordance with a further of the invention a method of effecting configuration change management is provided. The method includes steps of:
retrieving at least two configurations command snapshots; selecting at least one Command Line Interface (CLI) command from one of the at least two configuration command snapshots; and issuing the at least one selected CLI
command to a selected communications network entity to effect a configuration change. The at least one selected CLI command is issued to the selected communications network entity to restore the configuration thereof to a previous configuration.
The advantages are derived from an efficient method of debugging communications network entity configuration problems. The methods and system further enable easy migration of communications network entities to newer software/firmware releases, and provisioning a replacement communications network equipment. Further advantages are derived from: a centralized tracking and storage of configuration information under version control, and the ability to compare versions of communications network entity configurations, reducing equipment downtime at reduced communications network management overheads.
commands via a console. Script-based and manual entry of CLI commands to change communications network entity configuration make it difficult to keep track of configuration changes.
The configuration of a communications network entity tends to change over time, for example due to software upgrades, firmware upgrades, hardware upgrades, new service/capacity provisioning, etc. It is often useful to track the changes made to the configuration of a communications network entity in case there is a need to return to a previous configuration, for example to remove a problem caused by a configuration change.
In the prior art it is known to perform "baselining" on a router's configuration:
a record is kept of the router's initial configuration. The initial configuration is then used as a template to which further changes are made. The Wide Area Network Design Laboratory (WANDL)Inc. providestool known as a the Internet ProtocolAnalysis Tool (IPAT)for performingbaselining on Cisco Systems routers.IPAT makes use of "configlets",which are router configuration scripts, to make configuration changes to a router.
It is also known in the prior art to store CLI command configuration scripts run on a router to effect configuration changes to it. Prior practice includes naming CLI command configuration scripts run on a router with descriptions specifying what changes were made. Communications network entities usually have at least one vendor specific CLI command or a specific CLI command sequence providing for retrieval of configuration information therefrom. This configuration information may be stored in a file. However, means to manage these retrieved configuration files are not known in the prior art.
Although descriptively naming "configlets" and CLI command configuration scripts of the prior art provide limited tracking of configuration changes made to a communications network entity, it does not provide any tracking of manual the configuration changes made thereto. Therefore, simply knowing the changes that were made to a communications network entity is not sufficient in tracking communications network entity configuration. The result is: an increased overhead in the management of communications networks, an over reliance of highly trained analysts, misuse of the capabilities of highly trained analysts in fixing configuration changes.
There therefore is a need to address the above mentioned issues in providing configuration change management solutions reducing network management operational overheads.
Summar3r of the invent~i on In accordance with an aspect of the invention, a configuration change management system is provided. The configuration change management system includes: means for receiving configuration information from at least one communications network entity; a configuration repository for storing version controlled snapshots of configuration information in configuration repository entries; and a comparator comparing at least two configuration snapshots. The configuration repository provides storage of configuration information of communications network entities in a realm of management of a network management solution. The comparator enables configuration change management to be effected.
In accordance with another aspect of the invention, the configuration change management system further includes a human-machine interface to enable an operator to interact with version controlled configuration information and in particular to perform operations on configuration command snapshots.
In accordance with a further of the invention a method of effecting configuration change management is provided. The method includes steps of:
retrieving at least two configurations command snapshots; selecting at least one Command Line Interface (CLI) command from one of the at least two configuration command snapshots; and issuing the at least one selected CLI
command to a selected communications network entity to effect a configuration change. The at least one selected CLI command is issued to the selected communications network entity to restore the configuration thereof to a previous configuration.
The advantages are derived from an efficient method of debugging communications network entity configuration problems. The methods and system further enable easy migration of communications network entities to newer software/firmware releases, and provisioning a replacement communications network equipment. Further advantages are derived from: a centralized tracking and storage of configuration information under version control, and the ability to compare versions of communications network entity configurations, reducing equipment downtime at reduced communications network management overheads.
Brief description of the drawings The features and advantages of the invention will become more apparent from the following detailed description of the preferred embodiments) with reference to the attached diagrams wherein:
FIG. 1 is a schematic diagram showing data network elements implementing a connected data transport infrastructure;
FIG. 2 is a schematic diagram of an configuration management system in accordance with an exemplary embodiment of the invention;
FIG. 3 is a schematic diagram showing a configuration repository roster specifying configuration command snapshot identification information in accordance with a generic exemplary implementation of the invention; and FIG. 4 is a schematic diagram showing an arrangement of widgets defining a generic human-machine interface for effecting configuration change management in accordance with an exemplary embodiment of the invention.
I5 It will be noted that in the attached diagrams like features bear similar labels.
Detailed description of the embodiments In accordance with a typical network provisioning scenario schematically shown in FIG.2, the communications network 100 includes router communications network entities 106 and a Network Management System (NMS) 240. Associated with the NMS 240 are various network management databases for storing network management information pertaining to communications network entities in a realm of management of the NMS 240.
In accordance with an exemplary embodiment of the invention, a record is kept for each managed vendor equipment type. The record specifies a Command Line Interface (CLI) command or a CLI command sequence to be used in requesting and obtaining a configuration command snapshot from a communications network entity. For certainty, the configuration command snapshot includes an exhaustive set of CLI commands otherwise needed to be input via a CLI interface to restore the configuration of the communications network entity to the same configuration as that present at the time the configuration command snapshot was obtained.
In accordance with an exemplary embodiment of the invention, a configuration repository 250 is also provided. The configuration repository 250 is associated with the NMS 240. It is understood that network management may be performed in a decentralized fashion in which multiple NMS 240 cooperate to effect network management without limiting the invention. It is also understood that the configuration repository may be implemented using central or distributed storage systems and techniques without limiting the thereto, the configuration repository 250 provides consolidated storage of configuration cornrnand snapshots for managed communications network entities in the realm of management of the NMS 240.
Typically the NMS 240 is adapted to display connectivity information regarding communications network entities in the realm of management thereof including what are know in the art as network maps. Network maps include schematic diagrams of interconnected iconical representations of communications network entities. Making reference to the connected manageable communications network entities schematically shown in FIG. 1, there are: Open Systems Interconnect (OSI) Layer 1 manageable communications network entities such as communications ports 108, interface cards 124, etc.; OSI layer 2 manageable communications network entities such as interface cards 124, switching nodes 112, etc.; and OSI Layer 3 manageable communications network entities such as (virtual) routers 106, bridges 106, etc.;
all of which may be displayed in corresponding network maps. The invention is not limited to the above mentioned communications network entities or the OSI layer associations thereof. The invention attempts to address configuration management issues for any manageable communications network entity whether physical or logical having a configuration retrievable as a configuration command snapshot. The network maps provided by the NMS
240 provide for the selection of communications network entities on which to effect configuration change management.
The current configuration information can be retrieved from communications network entities in configuration command snapshots and stored in the configuration repository 250 in corresponding configuration repository entries for backup, future reference, and furthermore to enable configuration comparisons. FIG. 3 is representative of a configuration command snapshot roster each row corresponding to a repository entry.
In accordance with the exemplary embodiment of the invention, each configuration command snapshot obtained from a field-installed manageable communications network entity is stored in a corresponding repository entry along with further identifying information. Preferably the identifying information includes configuration command snapshot version specifiers. A
variety of versions specifies formats may be used without limiting the invention, shown in FIG.3 are version specifies having a numbered major.minor format. Means to manage retrieved configuration command snapshots and provide versioning control thereof is not known in the prior art.
The version specifies is associated with other communications network entity identifiers between which a fully qualified name, a network address, a physical access address such as a Media Access Control (MAC) address, a vendor equipment identifier, etc. The version specifies may further have associated therewith a time stamp related to the data and time at which the configuration command snapshot was obtained, an operator identifier, a comment, etc.
In accordance with the exemplary embodiment of the invention the configuration management system generates the version specifies.
FIG. 1 is a schematic diagram showing data network elements implementing a connected data transport infrastructure;
FIG. 2 is a schematic diagram of an configuration management system in accordance with an exemplary embodiment of the invention;
FIG. 3 is a schematic diagram showing a configuration repository roster specifying configuration command snapshot identification information in accordance with a generic exemplary implementation of the invention; and FIG. 4 is a schematic diagram showing an arrangement of widgets defining a generic human-machine interface for effecting configuration change management in accordance with an exemplary embodiment of the invention.
I5 It will be noted that in the attached diagrams like features bear similar labels.
Detailed description of the embodiments In accordance with a typical network provisioning scenario schematically shown in FIG.2, the communications network 100 includes router communications network entities 106 and a Network Management System (NMS) 240. Associated with the NMS 240 are various network management databases for storing network management information pertaining to communications network entities in a realm of management of the NMS 240.
In accordance with an exemplary embodiment of the invention, a record is kept for each managed vendor equipment type. The record specifies a Command Line Interface (CLI) command or a CLI command sequence to be used in requesting and obtaining a configuration command snapshot from a communications network entity. For certainty, the configuration command snapshot includes an exhaustive set of CLI commands otherwise needed to be input via a CLI interface to restore the configuration of the communications network entity to the same configuration as that present at the time the configuration command snapshot was obtained.
In accordance with an exemplary embodiment of the invention, a configuration repository 250 is also provided. The configuration repository 250 is associated with the NMS 240. It is understood that network management may be performed in a decentralized fashion in which multiple NMS 240 cooperate to effect network management without limiting the invention. It is also understood that the configuration repository may be implemented using central or distributed storage systems and techniques without limiting the thereto, the configuration repository 250 provides consolidated storage of configuration cornrnand snapshots for managed communications network entities in the realm of management of the NMS 240.
Typically the NMS 240 is adapted to display connectivity information regarding communications network entities in the realm of management thereof including what are know in the art as network maps. Network maps include schematic diagrams of interconnected iconical representations of communications network entities. Making reference to the connected manageable communications network entities schematically shown in FIG. 1, there are: Open Systems Interconnect (OSI) Layer 1 manageable communications network entities such as communications ports 108, interface cards 124, etc.; OSI layer 2 manageable communications network entities such as interface cards 124, switching nodes 112, etc.; and OSI Layer 3 manageable communications network entities such as (virtual) routers 106, bridges 106, etc.;
all of which may be displayed in corresponding network maps. The invention is not limited to the above mentioned communications network entities or the OSI layer associations thereof. The invention attempts to address configuration management issues for any manageable communications network entity whether physical or logical having a configuration retrievable as a configuration command snapshot. The network maps provided by the NMS
240 provide for the selection of communications network entities on which to effect configuration change management.
The current configuration information can be retrieved from communications network entities in configuration command snapshots and stored in the configuration repository 250 in corresponding configuration repository entries for backup, future reference, and furthermore to enable configuration comparisons. FIG. 3 is representative of a configuration command snapshot roster each row corresponding to a repository entry.
In accordance with the exemplary embodiment of the invention, each configuration command snapshot obtained from a field-installed manageable communications network entity is stored in a corresponding repository entry along with further identifying information. Preferably the identifying information includes configuration command snapshot version specifiers. A
variety of versions specifies formats may be used without limiting the invention, shown in FIG.3 are version specifies having a numbered major.minor format. Means to manage retrieved configuration command snapshots and provide versioning control thereof is not known in the prior art.
The version specifies is associated with other communications network entity identifiers between which a fully qualified name, a network address, a physical access address such as a Media Access Control (MAC) address, a vendor equipment identifier, etc. The version specifies may further have associated therewith a time stamp related to the data and time at which the configuration command snapshot was obtained, an operator identifier, a comment, etc.
In accordance with the exemplary embodiment of the invention the configuration management system generates the version specifies.
The version specifier may be made dependent on the network address of the subject managed communications network entity. The network address includes an Internet Protocol (IP) address when the communications network is an IP network, but the invention is not limited thereto. Network addresses are ascribed to communications network equipment in provisioning thereof.
The benefits of including the IP address in the roster enables the selection of configuration command snapshots from the repository to enable the replacement of the managed communications network entities and reconfiguration of a new one thereof subject to the same vendor specific/equipment type being installed at the same network location.
The version specifier may be dependent on physical device identifiers of the subject managed data network entity. The physical device identifiers including MAC address but not limited thereto. Communications network entities having more than one physical access device such as a port 108 are typically associated with the lowest MAC address ascribed to ports 102 thereof. MAC
addresses are ascribed during manufacturing of the vendor equipment whether port 102, interface card 124, switch 112, router 106, etc.; and determined as described above at instantiadon of logical communications network entities such as virtual routers 106.
The benefits of including the MAC address enables the configuration to follow the corresponding communications network entity as the communications network entity moves in a realm of management. Such an example is a mobile communications network node.
Version dependencies on fully qualified names such as secure.access.router.corp.com, edgerouterl.corp.com, etc. benefits from the configuration information following a network function.
A configuration management scenario is presented in FIG. 3 wherein the first roster entry corresponds to obtaining an initial configuration command snapshot, the subsequent roster entry corresponds the configuration command snapshot of the same communications network entity having a newly defined link, the subsequent roster entry corresponds the configuration command snapshot of the same communications network entity obtained following a software upgrade.
Note that the version specifier is reset when the same communications network entity is moved to a new location and obtaining a different network address. A
newly installed communications network entity having the same vendor equipment identifier may be configured to replace the moved communications network entity.
The configuration management system also allows the operator to compare the current configuration of a communications network entity to a saved version thereof, and also to compare a saved version to another. This feature enables the determination of configuration problems from difference between configuration command snapshots.
FIG.4 is representative of a human-machine interface associated with the exemplary configuration management solution presented. The human machine interface provides facilities for displaying configuration information to an operator for interaction therewith.
The configuration management system consists of a client user interface and a server process. The server process controls the connection to the field-installed managed communications network entities and the configuration repository.
Various interactive elements known as widgets make up the human-machine interface displayed. As described above, a mode of specifying which communications network entity is to be made subject to configuration management includes an interactive network map from which the communications network entity may be selected. The human-machine interface provides an editable field for entering a communications network entity identifier. Having specified a communications network entity identifier, the operator may either interact with a "Get Configuration" button or a "Get Repository Entry" button.
Activating the Get Configuration button, the configuration management system performs the necessary steps to request and obtain a current configuration command snapshot from the specified configuration network entity.
An example of the steps performed in obtaining a current configuration command snapshot from a communications network entity include:
- the communications network entity is identified/selected via a network map or specifying identifying information regarding the selected communications network entity;
- the change management application makes use of necessary vendor dependent CLI commands) to request current configuration information from the selected communications network entity;
- the CLI commands) is/are sent to the selected/identified communications network entity;
- the communications network entity replies with the requested configuration command snapshot having a vendor dependent format;
- the configuration change management application displays the requested configuration command snapshot to the operator; and - the operator may decide to retain the configuration command snapshot, in which case the configuration change management system saves the information in the configuration repository with an appropriate version description identifier.
Activating the Get Repository Entry button, the configuration management system accesses the configuration repository and displays a configuration command snapshot roster (shown in FIG. 3) showing the configuration change history of the identified communications network entity. The operator may further interact with the roster to specify a configuration command snapshot.
Optionally if a version identifier field is populated, corresponding configuration command snapshot is retrieved.
The configuration management system is operable to perform one of the following tasks via the human-machine interface shown in FIG. 4:
- retrieve the current configuration command snapshot from the identified communications network entity;
- retrieve a saved configuration command snapshot version from the configuration repository;
- to display at least one configuration command snapshot to the operator;
- save the current configuration command snapshot retrieved from the field installed communications network entity in the configuration repository under a new version; and - save a displayed configuration command snapshot to an electronic file.
In accordance with the exemplary embodiment of the invention, the configuration management system is further operable to:
- perform a comparison between configuration command snapshots;
- display the configuration command differences to the operator; and - enable the operator to interact with displayed configuration command differences.
Performing a comparison between configuration command snapshots includes retrieving at least two configuration command snapshots and activating a "Compare" button.
In interacting with the displayed configuration command differences the human-machine interface provides for:
- identification of a next/previous configuration command difference;
- selecting configuration command differences;
- editing, copying, cutting, pasting configuration command differences;
- including/excluding command differences across the compared configuration command snapshots; and - issuing selected configuration command differences for execution to an identified field-installed communications network entity.
Iconical interactive elements are shown in FIG. 4 to effect the above mentioned interaction.
In summary the invention provides a configuration change management system which includes software and hardware components operable via a network management system. The configuration change management system provides display of and version controlled storage of configuration information of various vendor specific communications network entities interconnected in a mufti-vendor communications network deployment. The system further includes a change management application, which runs on the network manager system, the change management application provides intermediary and control functions between the configuration repository, human-machine interface, and optionally network maps to display of configuration information and effect the configuration management. The hardware components of the configuration change management system includes a configuration repository for storing configuration information in repository entries under version control. The configuration repository entries are populated with configuration command snapshots obtained from field-installed communications equipment.
The configuration change management system also includes a human-machine interface for interacting with configuration command snapshots to effect configuration management.
Other important operations are provided such as: displaying previously saved configuration command snapshot, comparing two previously saved configuration command snapshots, comparing a previous configuration command snapshot with a current configuration command snapshot, and configuring a communications network entity from a previously saved configuration. These operations can be useful in debugging configuration related network failures in managing a communications network, migrating a communications network entity to a new software release, and in replacing a communications network entity with a new communications network entity.
The invention enables management of communications network entity configurations, and detection of configuration changes, for mufti-vendor communications network entities. This capability is important to network providers because it enables management of a more diverse communications network infrastructure with less investment in network management equipment and less operator training, thereby reducing the associated capital and operating costs.
The embodiments presented are e~cemplary only and persons skilled in the art would appreciate that variations to the above described embodiments may be made without departing from the spirit of the invention. The scope of the invention is solely defined by the appended claims.
The benefits of including the IP address in the roster enables the selection of configuration command snapshots from the repository to enable the replacement of the managed communications network entities and reconfiguration of a new one thereof subject to the same vendor specific/equipment type being installed at the same network location.
The version specifier may be dependent on physical device identifiers of the subject managed data network entity. The physical device identifiers including MAC address but not limited thereto. Communications network entities having more than one physical access device such as a port 108 are typically associated with the lowest MAC address ascribed to ports 102 thereof. MAC
addresses are ascribed during manufacturing of the vendor equipment whether port 102, interface card 124, switch 112, router 106, etc.; and determined as described above at instantiadon of logical communications network entities such as virtual routers 106.
The benefits of including the MAC address enables the configuration to follow the corresponding communications network entity as the communications network entity moves in a realm of management. Such an example is a mobile communications network node.
Version dependencies on fully qualified names such as secure.access.router.corp.com, edgerouterl.corp.com, etc. benefits from the configuration information following a network function.
A configuration management scenario is presented in FIG. 3 wherein the first roster entry corresponds to obtaining an initial configuration command snapshot, the subsequent roster entry corresponds the configuration command snapshot of the same communications network entity having a newly defined link, the subsequent roster entry corresponds the configuration command snapshot of the same communications network entity obtained following a software upgrade.
Note that the version specifier is reset when the same communications network entity is moved to a new location and obtaining a different network address. A
newly installed communications network entity having the same vendor equipment identifier may be configured to replace the moved communications network entity.
The configuration management system also allows the operator to compare the current configuration of a communications network entity to a saved version thereof, and also to compare a saved version to another. This feature enables the determination of configuration problems from difference between configuration command snapshots.
FIG.4 is representative of a human-machine interface associated with the exemplary configuration management solution presented. The human machine interface provides facilities for displaying configuration information to an operator for interaction therewith.
The configuration management system consists of a client user interface and a server process. The server process controls the connection to the field-installed managed communications network entities and the configuration repository.
Various interactive elements known as widgets make up the human-machine interface displayed. As described above, a mode of specifying which communications network entity is to be made subject to configuration management includes an interactive network map from which the communications network entity may be selected. The human-machine interface provides an editable field for entering a communications network entity identifier. Having specified a communications network entity identifier, the operator may either interact with a "Get Configuration" button or a "Get Repository Entry" button.
Activating the Get Configuration button, the configuration management system performs the necessary steps to request and obtain a current configuration command snapshot from the specified configuration network entity.
An example of the steps performed in obtaining a current configuration command snapshot from a communications network entity include:
- the communications network entity is identified/selected via a network map or specifying identifying information regarding the selected communications network entity;
- the change management application makes use of necessary vendor dependent CLI commands) to request current configuration information from the selected communications network entity;
- the CLI commands) is/are sent to the selected/identified communications network entity;
- the communications network entity replies with the requested configuration command snapshot having a vendor dependent format;
- the configuration change management application displays the requested configuration command snapshot to the operator; and - the operator may decide to retain the configuration command snapshot, in which case the configuration change management system saves the information in the configuration repository with an appropriate version description identifier.
Activating the Get Repository Entry button, the configuration management system accesses the configuration repository and displays a configuration command snapshot roster (shown in FIG. 3) showing the configuration change history of the identified communications network entity. The operator may further interact with the roster to specify a configuration command snapshot.
Optionally if a version identifier field is populated, corresponding configuration command snapshot is retrieved.
The configuration management system is operable to perform one of the following tasks via the human-machine interface shown in FIG. 4:
- retrieve the current configuration command snapshot from the identified communications network entity;
- retrieve a saved configuration command snapshot version from the configuration repository;
- to display at least one configuration command snapshot to the operator;
- save the current configuration command snapshot retrieved from the field installed communications network entity in the configuration repository under a new version; and - save a displayed configuration command snapshot to an electronic file.
In accordance with the exemplary embodiment of the invention, the configuration management system is further operable to:
- perform a comparison between configuration command snapshots;
- display the configuration command differences to the operator; and - enable the operator to interact with displayed configuration command differences.
Performing a comparison between configuration command snapshots includes retrieving at least two configuration command snapshots and activating a "Compare" button.
In interacting with the displayed configuration command differences the human-machine interface provides for:
- identification of a next/previous configuration command difference;
- selecting configuration command differences;
- editing, copying, cutting, pasting configuration command differences;
- including/excluding command differences across the compared configuration command snapshots; and - issuing selected configuration command differences for execution to an identified field-installed communications network entity.
Iconical interactive elements are shown in FIG. 4 to effect the above mentioned interaction.
In summary the invention provides a configuration change management system which includes software and hardware components operable via a network management system. The configuration change management system provides display of and version controlled storage of configuration information of various vendor specific communications network entities interconnected in a mufti-vendor communications network deployment. The system further includes a change management application, which runs on the network manager system, the change management application provides intermediary and control functions between the configuration repository, human-machine interface, and optionally network maps to display of configuration information and effect the configuration management. The hardware components of the configuration change management system includes a configuration repository for storing configuration information in repository entries under version control. The configuration repository entries are populated with configuration command snapshots obtained from field-installed communications equipment.
The configuration change management system also includes a human-machine interface for interacting with configuration command snapshots to effect configuration management.
Other important operations are provided such as: displaying previously saved configuration command snapshot, comparing two previously saved configuration command snapshots, comparing a previous configuration command snapshot with a current configuration command snapshot, and configuring a communications network entity from a previously saved configuration. These operations can be useful in debugging configuration related network failures in managing a communications network, migrating a communications network entity to a new software release, and in replacing a communications network entity with a new communications network entity.
The invention enables management of communications network entity configurations, and detection of configuration changes, for mufti-vendor communications network entities. This capability is important to network providers because it enables management of a more diverse communications network infrastructure with less investment in network management equipment and less operator training, thereby reducing the associated capital and operating costs.
The embodiments presented are e~cemplary only and persons skilled in the art would appreciate that variations to the above described embodiments may be made without departing from the spirit of the invention. The scope of the invention is solely defined by the appended claims.
Claims (20)
1. A configuration management system comprising:
a. means for receiving configuration information from at least one communications network entity;
b. a configuration repository for storing version controlled snapshots of configuration information in configuration repository entries; and c. a comparator comparing at least two configuration snapshots the configuration repository providing storage of configuration information of communications network entities in a realm of management of a network management solution, the comparator enabling configuration change management to be effected.
a. means for receiving configuration information from at least one communications network entity;
b. a configuration repository for storing version controlled snapshots of configuration information in configuration repository entries; and c. a comparator comparing at least two configuration snapshots the configuration repository providing storage of configuration information of communications network entities in a realm of management of a network management solution, the comparator enabling configuration change management to be effected.
2. A configuration management system as claimed in claim 1, further comprising a store for retrievably storing at least one Command Line Interface (CLI) command specification for a CLI command sequence used in requesting a configuration snapshot from a corresponding vendor specific communications network entity.
3. A configuration management system as claimed in claim 1, wherein each repository entry holds a version controlled configuration command snapshot.
4. A configuration management system as claimed in claim 1, wherein each repository entry further specifies a configuration snapshot version identifier and at least one of: a communications network entity fully qualified name, a communications network entity network address, a communications network entity physical address, a vendor specific equipment identifier.
5. A configuration management system as claimed in claim 4, wherein each repository entry further specifies a time stamp holding a time specification representative of the time at which the configuration command snapshot was generated.
6. A configuration management system as claimed in claim 1, further comprising a human-machine interface enabling an operator to interact with the version controlled configuration information.
7. A configuration management system as claimed in claim 6, wherein the human-machine interface is further operable to display a representation of at least one portion of a communications network comprising at least one managed communications network entity.
8. A configuration management system as claimed in claim 7, wherein the human-machine interface is further operable to display Open Systems Interconnection (OSI) Layer 1 communications network entities.
9. A configuration management system as claimed in claim 7, wherein the human-machine interface is further operable to display Open Systems Interconnection (OSI) Layer 2 communications network entities.
10. A configuration management system as claimed in claim 7, wherein the human-machine interface is further operable to display Open Systems Interconnection (OSI) Layer 3 communications network entities.
11. A configuration management system as claimed in claim 7, the human-machine interface operable to select the at least one managed communications network entity creating a network management context in which to effect configuration change management.
12. A configuration management system as claimed in claim 6, wherein the human-machine interface further includes:
a. interactive elements for retrieving at least two configuration snapshots pertaining to at least one communications network entity;
b. interactive display elements operable to display differences between at least two configuration snapshots.
a. interactive elements for retrieving at least two configuration snapshots pertaining to at least one communications network entity;
b. interactive display elements operable to display differences between at least two configuration snapshots.
13. A configuration management system as claimed in claim 12, wherein the human-machine interface further includes interactive elements operable to perform at least one operation on displayed differences from: edit, copy, paste, include, exclude, delete, save to file, issue for execution on a selected communications network entity, select next difference, and select previous difference.
14. A method of effecting configuration change management comprising the steps of:
a. retrieving at least two configurations command snapshots;
b. selecting at least one Command Line Interface (CLI) command from one of the at least two configuration command snapshots; and c. issuing the at least one selected CLI command to a selected communications network entity to effect a configuration change the at least one selected CLI command being issued to the selected communications network entity to restore the configuration thereof to a previous configuration.
a. retrieving at least two configurations command snapshots;
b. selecting at least one Command Line Interface (CLI) command from one of the at least two configuration command snapshots; and c. issuing the at least one selected CLI command to a selected communications network entity to effect a configuration change the at least one selected CLI command being issued to the selected communications network entity to restore the configuration thereof to a previous configuration.
15. A method of effecting configuration change management as claimed in claim 14, wherein retrieving the at least two configuration snapshots, the method further comprises a step of retrieving a configuration command snapshot from a one of: a configuration repository entry of a configuration repository storing version controlled configuration information, and a field-installed communications network entity.
16. A method of effecting configuration change management as claimed in claim 15, wherein prior to retrieving the at least two configuration snapshots, the method further comprises steps of:
a. issuing at least one CLI command to a managed field-installed communications network entity requesting a configuration command snapshot; and b. storing the received configuration command snapshot in a configuration repository entity of a configuration repository subject to version control successive received configuration command snapshots, having successive corresponding version specifiers, are stored in the configuration repository.
a. issuing at least one CLI command to a managed field-installed communications network entity requesting a configuration command snapshot; and b. storing the received configuration command snapshot in a configuration repository entity of a configuration repository subject to version control successive received configuration command snapshots, having successive corresponding version specifiers, are stored in the configuration repository.
17. A method of effecting configuration change management as claimed in claim 15, wherein prior issuing at least one CLI command to a field-installed communications network entity requesting a configuration command snapshot, the method further comprises a step of: selecting the managed field-installed communications network entity from a network map representative of a realm of management of a network management solution.
18. A method of effecting configuration change management as claimed in claim 15, wherein prior issuing at least one CLI command to a field-installed communications network entity requesting a configuration command snapshot, the method further comprises a step of: specifying a communication network entity identifier corresponding to the managed field-installed communications network entity from: a communication network entity fully qualified name, a communications network entity network address, and a communications network entity physical address.
19. A method of effecting configuration change management as claimed in claim 14, wherein prior to selecting at least one Command Line Interface (CLI) command from one of the at least two configuration command snapshots, the method further comprises a step of: comparing the at least two configuration command snapshots to determine differences therebetween.
20. A method of effecting configuration change management as claimed in claim 19, the method further comprises a step of: interacting with determined configuration command differences to perform at least one operation on displayed differences from: editing, copying, pasting, including, excluding, deleting, saving to file, issuing for execution on a selected communications network entity, selecting a next difference, and selecting a previous difference.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002404191A CA2404191A1 (en) | 2002-09-19 | 2002-09-19 | Methods and apparatus for configuration change management in communications networks |
| US10/456,489 US20040059813A1 (en) | 2002-09-19 | 2003-06-09 | Methods and apparatus for configuration change management in communications networks |
| EP03300119A EP1443700A3 (en) | 2002-09-19 | 2003-09-18 | Methods and apparatus for configuration change management in communications networks |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002404191A CA2404191A1 (en) | 2002-09-19 | 2002-09-19 | Methods and apparatus for configuration change management in communications networks |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2404191A1 true CA2404191A1 (en) | 2004-03-19 |
Family
ID=31983634
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002404191A Abandoned CA2404191A1 (en) | 2002-09-19 | 2002-09-19 | Methods and apparatus for configuration change management in communications networks |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US20040059813A1 (en) |
| CA (1) | CA2404191A1 (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7361249B2 (en) * | 2002-12-05 | 2008-04-22 | Multimedia Games, Inc. | Apparatus for applying a removable cover to a ticket substrate |
| US7386629B2 (en) * | 2003-06-30 | 2008-06-10 | Intel Corporation | System and method for synchronous configuration of DHCP server and router interfaces |
| US20040267922A1 (en) * | 2003-06-30 | 2004-12-30 | Rover Jeremy L. | System and method for the design and description of networks |
| US7383340B2 (en) * | 2003-06-30 | 2008-06-03 | Intel Corporation | System and method for programmatically changing the network location of a network component |
| US20040267921A1 (en) * | 2003-06-30 | 2004-12-30 | Rover Jeremy L. | System and method for describing network components and their associations |
| US7483390B2 (en) * | 2003-06-30 | 2009-01-27 | Intel Corporation | System and method for dynamically configuring and transitioning wired and wireless networks |
| US7606888B2 (en) * | 2003-11-24 | 2009-10-20 | Cisco Technology, Inc. | Approach for managing network device configuration data |
| US7383271B2 (en) * | 2004-04-06 | 2008-06-03 | Microsoft Corporation | Centralized configuration data management for distributed clients |
| US7590669B2 (en) * | 2004-04-06 | 2009-09-15 | Microsoft Corporation | Managing client configuration data |
| US7403491B2 (en) * | 2004-04-15 | 2008-07-22 | Alcatel Lucent | Framework for template-based retrieval of information from managed entities in a communication network |
| US7779404B2 (en) | 2004-06-10 | 2010-08-17 | Cisco Technology, Inc. | Managing network device configuration using versioning and partitioning |
| CA2504030A1 (en) * | 2005-04-13 | 2006-10-13 | Canimex Inc. | Special quiet anchor for spring fitting in counterbalancing door, and door assembly including the same |
| US8539604B2 (en) * | 2005-08-03 | 2013-09-17 | International Business Machines Corporation | Method, system and program product for versioning access control settings |
| EP1797528A1 (en) * | 2005-08-16 | 2007-06-20 | Swiss Reinsurance Company | Computer-based data processing system and method of processing data objects |
| 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 |
| US10528705B2 (en) * | 2006-05-09 | 2020-01-07 | Apple Inc. | Determining validity of subscription to use digital content |
| US20080065680A1 (en) * | 2006-09-12 | 2008-03-13 | Microsoft Corporation | Change and release management system |
| US8341251B2 (en) * | 2008-01-03 | 2012-12-25 | International Business Machines Corporation | Enabling storage area network component migration |
| US8769675B2 (en) * | 2008-05-13 | 2014-07-01 | Apple Inc. | Clock roll forward detection |
| CN101788991B (en) * | 2009-06-23 | 2013-03-06 | 北京搜狗科技发展有限公司 | Updating reminding method and system |
| WO2012097015A2 (en) | 2011-01-11 | 2012-07-19 | A10 Networks Inc. | Virtual application delivery chassis system |
| US9154577B2 (en) | 2011-06-06 | 2015-10-06 | A10 Networks, Inc. | Sychronization of configuration file of virtual application distribution chassis |
| US10423509B2 (en) * | 2011-08-05 | 2019-09-24 | Entit Software Llc | System and method for managing environment configuration using snapshots |
| US8959425B2 (en) | 2011-12-09 | 2015-02-17 | Microsoft Corporation | Inference-based extension activation |
| US9679163B2 (en) | 2012-01-17 | 2017-06-13 | Microsoft Technology Licensing, Llc | Installation and management of client extensions |
| US9256445B2 (en) | 2012-01-30 | 2016-02-09 | Microsoft Technology Licensing, Llc | Dynamic extension view with multiple levels of expansion |
| US8843822B2 (en) | 2012-01-30 | 2014-09-23 | Microsoft Corporation | Intelligent prioritization of activated extensions |
| US9449112B2 (en) | 2012-01-30 | 2016-09-20 | Microsoft Technology Licensing, Llc | Extension activation for related documents |
| US20130219156A1 (en) * | 2012-02-22 | 2013-08-22 | Sungard Availability Services Lp | Compliance aware change control |
| DE102012106774A1 (en) * | 2012-07-25 | 2014-01-30 | Endress + Hauser Gmbh + Co. Kg | Method for maintaining the functionality of a field device |
| US20150026076A1 (en) * | 2013-07-18 | 2015-01-22 | Netapp, Inc. | System and Method for Providing Customer Guidance in Deploying a Computing System |
| US20150026077A1 (en) * | 2013-07-18 | 2015-01-22 | Netapp, Inc. | Centralized Method for Customer Assistance and System Verification |
| US9961130B2 (en) | 2014-04-24 | 2018-05-01 | A10 Networks, Inc. | Distributed high availability processing methods for service sessions |
| US10742559B2 (en) | 2014-04-24 | 2020-08-11 | A10 Networks, Inc. | Eliminating data traffic redirection in scalable clusters |
| EP2958291B1 (en) * | 2014-06-18 | 2021-04-14 | Swisscom AG | Method and system for authenticating network equipment |
| US10318288B2 (en) | 2016-01-13 | 2019-06-11 | A10 Networks, Inc. | System and method to process a chain of network applications |
| US20220398287A1 (en) * | 2021-06-10 | 2022-12-15 | Dirk Ockhardt | Map Based Internet Browsing |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5495607A (en) * | 1993-11-15 | 1996-02-27 | Conner Peripherals, Inc. | Network management system having virtual catalog overview of files distributively stored across network domain |
| US5923850A (en) * | 1996-06-28 | 1999-07-13 | Sun Microsystems, Inc. | Historical asset information data storage schema |
| US6282175B1 (en) * | 1998-04-23 | 2001-08-28 | Hewlett-Packard Company | Method for tracking configuration changes in networks of computer systems through historical monitoring of configuration status of devices on the network. |
| US6453346B1 (en) * | 1998-07-17 | 2002-09-17 | Proactivenet, Inc. | Method and apparatus for intelligent storage and reduction of network information |
| US7249170B2 (en) * | 2000-12-06 | 2007-07-24 | Intelliden | System and method for configuration, management and monitoring of network resources |
| GB2380004A (en) * | 2001-07-27 | 2003-03-26 | Virtual Access Ireland Ltd | A configuration and management development system for a netwok of devices |
| US6959329B2 (en) * | 2002-05-15 | 2005-10-25 | Intelliden | System and method for transforming configuration commands |
-
2002
- 2002-09-19 CA CA002404191A patent/CA2404191A1/en not_active Abandoned
-
2003
- 2003-06-09 US US10/456,489 patent/US20040059813A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| US20040059813A1 (en) | 2004-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2404191A1 (en) | Methods and apparatus for configuration change management in communications networks | |
| EP1443700A2 (en) | Methods and apparatus for configuration change management in communications networks | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator | |
| Cisco | Using the Configurator |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |