Guest

Cisco BPX/IGX/IPX WAN Software

Cisco WAN Manager (CWM) Field Defined in savecnf and loadcnf Commands

Cisco - Cisco WAN Manager (CWM) Field Defined in savecnf and loadcnf Commands

Document ID: 10788

Updated: Dec 07, 2006

   Print

Introduction

This document explains the Cisco WAN Manager (CWM) node_name field in the SuperUser savecnf and loadcnf commands.

caution Caution: Use of SuperUser commands needs to be limited to Cisco employees and other qualified users, such as system administrators. Improper use of some SuperUser commands can lead to system malfunction or complete failure.

Prerequisites

Requirements

Cisco recommends that you have knowledge of CWM maintenance and administration.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

The savecnf Command (Save Configuration)

The savecnf command saves a configuration image on a CWM workstation disk.

Attributes

Jobs: Yes Log: Yes Lock: Yes Node Type: IPX, IGX, BPX, IPX/AF

Associated Commands

  • loadcnf

  • runcnf

  • clrcnf

Syntax

savecnf backup_id| clear node_name dest_SV_node [dest_SV_ip]

Command Argument Description
backup_id Specifies the name of a configuration to be saved on CWM. The Backup ID must be 1 to 8 alphanumeric characters with the first character being alphabetic. Configuration names are case-sensitive.
clear Specifies that the buffer area should be cleared.
node_name Specifies the node name on which to save configuration. '*' can be specified to indicate all nodes.
dest_SV_node Specifies the node name where CWM is connected and receives the specified backup_id.
[dest_SV_ip] For IPX/AF interface shelves only, this optional specification is the IP address of the CWM that is to receive the configuration image.

Function

The savecnf command has two possible applications. It saves all the configurations for the nodes in a routing network, or it saves the configuration of one IPX/AF interface shelf to a specific CWM workstation. Once saved, the configuration can be restored to BRAM with the use of the loadcnf and runcnf commands. The savecnf command should be executed in these situations:

  • After you make any configuration changes in a network

  • Before you upgrade to a new system software release

The loadcnf Command (Load Configuration)

The loadcnf command loads a configuration image from CWM to a node.

Attributes

Jobs: Yes Log: Yes Lock: Yes Node Type: IPX, IGX, BPX, IPX/AF

Associated Commands

  • dspcnf

  • runcnf

  • savecnf

Syntax

loadcnf backup_id | clear node_name source_SV_node

Command Argument Description
backup_id Specifies the name of the backup configuration file to be loaded. Configuration names are case-sensitive.
clear Specifies that the control card buffer area used to load a configuration be cleared.
node_name Specifies the target node where the backup configuration file is to be loaded.
source_SV_node Specifies the node connected to the CWM where the configuration file backup_id resides.

Function

This command causes a saved network configuration file to be downloaded from CWM to one node or all nodes. Refer to the savecnf command. The configuration image downloaded is temporarily stored in a buffer area in a node controller card memory. The process runs in the background and can take several minutes if the configuration file is large. Although loaded, the configuration is not yet restored. The configuration is restored to the controller card BRAM memory with the runcnf command.

After you load and restore a network configuration, the control card buffer area used for this purpose should be cleared so it is available for other downloading processes, such as that of firmware. Execute loadcnf with the clear parameter specified instead of backup_id in order to clear the buffer area. Specify the buffer of an individual node with node_name or all nodes with *. For the purpose to clear the buffer area, do not specify the source_SV_node parameter.

Telnet to the shelf or use a control terminal attached to the shelf in order to execute this command on an IPX/AF interface shelf.

Explanation

In the past the CWM node used in the savecnf and loadcnf commands was the CWM Gateway node. But, this is no longer always the case. This can cause some confusion because CWM can use the network IP address to talk directly to the node when the network IP address is configured in the CWM config.sv file. That means that CWM no longer sends a message to a remote node through the CWM Gateway node. You can use the more /usr/users/svplus/config.sv UNIX command in order to view the config.sv file.

In other words, if the network IP address (nwip) is specified in CWM, the CWM node for the CWM is the node itself, instead of the CWM Gateway node. This is because the message does not go through the CWM Gateway node.

The best way to utilize the savecnf and loadcnf commands is to put the "*" in the CWM node field and specify the CWM IP address to indicate where the configurations are to be saved or from where they are to be restored. Then you do not have to worry about the identity of the CWM node.

An example is shown:

+--------------+       +-------+
     | node1        |       |       |
     | (CWM Gateway |-------| node2 |
     |  node)       |       |       |
     +--------------+       +-------+
          |
          |   +-----+
          +---| CWM | IP address: 133.8.3.8
              +-----+

In the previous example, when nwip is off for the CWM, a user logged in to node2 can use one of these forms to run the savecnf or the loadcnf command on the node2 configuration:

  • savecnf node2cnf node2 node1

  • savecnf node2cnf node2 * 133.8.3.8

When nwip is on for the CWM, a user logged in to node2 can use one of these forms to run the savecnf or the loadcnf command on the node2 configuration:

  • savecnf node2cnf node2 node2

  • savecnf node2cnf node2 * 133.8.3.8

Related Information

Updated: Dec 07, 2006
Document ID: 10788