Abstract: Prior to a first configuration change of a first resource, such as a network resource of a network, a processor determines a first performance metric of a second resource, such as a second network resource of the network. The first configuration change does not result in complete failure or fault of the second resource. Subsequent to the first configuration change of the first resource, the processor determines a second performance metric of the second resource and compares the second performance metric to at least one of the first performance metric and a service objective to yield comparison results. Based on the comparison results, the processor can cause a second configuration change of the first resource. The second configuration change of the first resource can revert a configuration of the first resource to its state prior to the first configuration change.

Abstract: Prior to a first configuration change of a first resource, such as a network resource of a network, a processor determines a first performance metric of a second resource, such as a second network resource of the network. The first configuration change does not result in complete failure or fault of the second resource. Subsequent to the first configuration change of the first resource, the processor determines a second performance metric of the second resource and compares the second performance metric to at least one of the first performance metric and a service objective to yield comparison results. Based on the comparison results, the processor can cause a second configuration change of the first resource. The second configuration change of the first resource can revert a configuration of the first resource to its state prior to the first configuration change.

Abstract: Prior to a first configuration change of a first resource, such as a network resource of a network, a processor determines a first performance metric of a second resource, such as a second network resource of the network. The first configuration change does not result in complete failure or fault of the second resource. Subsequent to the first configuration change of the first resource, the processor determines a second performance metric of the second resource and compares the second performance metric to at least one of the first performance metric and a service objective to yield comparison results. Based on the comparison results, the processor can cause a second configuration change of the first resource. The second configuration change of the first resource can revert a configuration of the first resource to its state prior to the first configuration change.

Abstract: Prior to a first configuration change of a first resource, such as a network resource of a network, a processor determines a first performance metric of a second resource, such as a second network resource of the network. The first configuration change does not result in complete failure or fault of the second resource. Subsequent to the first configuration change of the first resource, the processor determines a second performance metric of the second resource and compares the second performance metric to at least one of the first performance metric and a service objective to yield comparison results. Based on the comparison results, the processor can cause a second configuration change of the first resource. The second configuration change of the first resource can revert a configuration of the first resource to its state prior to the first configuration change.

Abstract: Mechanisms operable to configure, monitor and manage network devices without regard for device type and/or manufacturer are disclosed. One implementation includes a network manager unit disposed between the network administrator and the network devices. The network manager unit allows the administrator to holistically view, configure and manage an entire network without regard to device type and/or manufacturer. The administrator can implement this holistic approach with the use of a central repository for all configuration information and/or a central posting location for all network events. A device-specific command template database may be provided for providing device-specific command templates for various device types and/or manufacturers.

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

Abstract: A method and apparatus to initializing a network device is described. In one embodiment, the present invention includes the step of: retrieving an initial communications address from a local memory of the network device; transmitting a secure identifier to the initial communications address verifying the authenticity of the secure identifier; retrieving a configuration record from a configuration record repository, the retrieved configuration record being associated with the network device that corresponds to the secure identifier; receiving the configuration record at the network device; and installing the configuration record at the network device.

Abstract: A method and apparatus to configure, monitor and manage network devices without regard for device type and/or manufacturer is disclosed. One implementation of this embodiment includes a network manager unit disposed between the network administrator and the network devices. The network manager unit allows the administrator to holistically view, configure and manage an entire network without regard to device type and/or manufacturer. The administrator can implement this holistic approach with the use of a central repository for all configuration information and/or a central posting location for all network events.

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

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

Abstract: A system and method for optimizing the use of network resources is described. In one embodiment, an enterprise first requests provisioning of network resources for a particular transaction. Responsive to that request, network resources are dynamically configured to meet the enterprise's request. When the transaction is complete, the network resources are returned to a default state.

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

Abstract: A system and method for managing network-device configurations is described. In one exemplary embodiment, the present invention can include a central repository for storing configuration information about multiple network devices. This configuration information is organized for efficient searching and retrieval of relevant data. For example, network applications can search and retrieve relevant configuration information about particular network devices.

Abstract: An event bus for managing network event messages is described. In one embodiment, the event bus includes an interface for receiving an event message; a routing manager configured to determining whether an event message received at the interface should be routed to a destination device or whether it should be queued for retrieval by the destination device; a queue for storing the event message; and a network event storage device configured to store a copy of the event message.

Abstract: A method and apparatus to initializing a network device is described. In one embodiment, the present invention includes the step of: retrieving an initial communications address from a local memory of the network device; transmitting a secure identifier to the initial communications address verifying the authenticity of the secure identifier; retrieving a configuration record from a configuration record repository, the retrieved configuration record being associated with the network device that corresponds to the secure identifier; receiving the configuration record at the network device; and installing the configuration record at the network device.

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

Abstract: A method and apparatus to configure, monitor and manage network devices without regard for device type and/or manufacturer is disclosed. One implementation of this embodiment includes a network manager unit disposed between the network administrator and the network devices. The network manager unit allows the administrator to holistically view, configure and manage an entire network without regard to device type and/or manufacturer. The administrator can implement this holistic approach with the use of a central repository for all configuration information and/or a central posting location for all network events.