cc/td/doc/product/rtrmgmt/cwm/9_2_06
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Saving and Restoring Node Configurations

Saving and Restoring Node Configurations

Each MGX 8800, BPX® 8600, or IGX 8400 node on the network stores network configuration information in BRAM of controller card (BCC/NPC/NPM). The node configuration includes information about trunks, lines, ports, connections etc. The network configuration can be stored on a Cisco WAN Manager (CWM) workstation and can be restored on the network at any time when it is required.

Saving Node Configurations

This section describes how to save and restore node configurations. To save or restore a node's configuration, the Configuration Save/Restore option should be enabled on the node.

Step 1 To enable or verify whether the Configuration Save/Restore option is enabled for a node, invoke the cnfswfunc command on the node CLI (Command Line Interface). The output of this command on a BPX 8600 is shown in Figure 15-1.


Figure 15-1: cnfswfunc Command Output


Option 1 in the above display is for Configuration Save and Restore. When this option is not enabled you can not save or restore the configuration from the node.


Note Note the output of cnfswfunc is different on an IGX 8400 series switch.

Step 2 Check whether a firmware image is loaded on the node. The savecnf command uses the same buffers used by a loaded firmware image. Therefore, when a firmware image is loaded on the node, savecnf displays an error. To check whether a firmware image is loaded on the node, invoke the dspcnf command. When the dspcnf output says "Reserved for firmware image" it means a firmware image is loaded on the node, as shown in Figure 15-2.


Figure 15-2: dspcnf Command Output


Loaded firmware images must be cleaned up before invoking savecnf. To remove the loaded firmware image, invoke the getfwrev command on the node and specify 0.0 as the firmware revision level, as in the following:

getfwrev <card_type> 0.0 <node>

Step 3 Save the node's configuration using the savecnf command. The syntax for the savecnf command is given below:

savecnf <backup_id|clear> <node_name|*> <dest_CWM_node> [<dest_CWM_ip>]

A typical savecnf command invocation is shown below with its output shown in Figure 15-3:

savecnf C051598 nmsbpx14 nmsbpx14 172.29.23.25


Figure 15-3: savecnf Command Output


When you specify an "*" (asterisk) as the third parameter to the savecnf command on a routing node, configuration of all the routing nodes in the network are saved. A directory with the name <backup_id>_Cfgdir is created in the home directory (/usr/users/svplus) of CWM and all the configuration files are saved in that directory.

When more than two CWM workstations are connected to the network, when you specify the last parameter (<dest_SV_ip>) you can identify to which CWM workstation the configuration save is to be done. In the above example, the configuration save is done on the CWM workstation with IP address 172.29.23.25.

Note, the value for dest_SV_node is dependent on the configuration in config.sv file of CWM.

When the last field in a /usr/users/svplus/config.sv file entry is set to nwip_on, the dest_CWM_node should be the same node on which the savecnf command is being executed. This case is shown in the typical invocation of the command, as shown above, where dest_CWM_node is specified as nmsbpx14 and the node on which savecnf is being run is also nmsbpx14.


Note You cannot invoke a save configuration of all nodes by specifying an "*" (asterisk) as the third parameter to the saveconf command when nwip_on is configured in the /usr/users/svplus/config.sv file.

When the last field in a /usr/users/svplus/config.sv file entry is set to nwip_off, the dest_CWM_node should be the gateway node name. Gateway node name is specified as the third field in a /usr/users/svplus/config.sv file entry of CWM. For example, the following command saves the configuration of node nmsbpx14 on the CWM workstation, whose IP address is 172.29.23.25, and is connected to the gateway node nmsbpx13.

savecnf C051598 nmsbpx14 nmsbpx13 172.29.23.25

To save the configuration of all routing nodes when nwip_off is configured in the /usr/users/svplus/config.sv file, a typical command invocation is:

savecnf C051598 * nmsbpx13 172.29.23.25

The above command saves the configuration of all routing nodes on the CWM workstation with the 172.29.23.25 IP address, and CWM gateway node specified as nmsbpx13. The configuration is saved in the /usr/users/svplus/C051598_Cfgdir directory.

Restoring Node Configurations

To restore a node's configuration, invoke the restorecnf command. For the syntax of the savecnf, restorecnf, and other related commands, see Appendix A "Save and Restore Configuration Commands".

Saving MGX 8220, MGX 8800, and ESP Node Configurations

To save the configuration of MGX 8220, MGX 8800, and ESP nodes, use the CWM Configuration Save/Restore application.

Step 1 Invoke this application by selecting the CWM Network Topology window's Software Management menu's Config Save option, or by selecting the HP OpenView's Cisco_SV menu's Configuration Save option. The Configuration Save window, shown in Figure 15-4, is displayed.


Figure 15-4: Configuration Save Window


Step 2 Click on the Save button to save the node's configuration in the /usr/users/svplus/ConfigData directory. The format of the file name is: <config_data_name>_<nodename>, where <config_data_name> is the name you specified in the Config Data Name text field and <nodename> is the name of the node(s) in the Selected Node List pane. A separate file is created for each node listed in the Selected Node List pane.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Nov 4 21:22:40 PST 1999
Copyright 1989-1999©Cisco Systems Inc.