Verifying and Saving Your Configuration

This chapter describes how to save your system configuration.

Verifying the Configuration

You can use a number of commands to verify the configuration of your feature, service, or system. Many are hierarchical in their implementation and some are specific to portions of or specific lines in the configuration file.

Feature Configuration

In many configurations, you have to set and verify specific features. An example includes IP address pool configuration. Using the example below, enter the listed commands to verify proper feature configuration.

Enter the show ip pool command to display the IP address pool configuration. The output from this command should look similar to the sample shown below. In this example, all IP pools were configured in the isp1 context. 

context : isp1:  
+-----Type:        (P) - Public        (R) - Private  
|                  (S) - Static        (E) - Resource  
| 
|+----State:       (G) - Good          (D) - Pending Delete      (R)-Resizing 
|| 
||++--Priority:    0..10 (Highest      (0) .. Lowest (10)) 
|||| 
||||+-Busyout:     (B) - Busyout configured  
|||||| 
vvvvvv  Pool Name           Start Address  Mask/End Address Used      Avail 
----- --------------------- -------------- ---------------  ---------------- 
PG00    ipsec               12.12.12.0       255.255.255.0   0        254 
PG00    pool1               10.10.0.0        255.255.0.0     0        65534 
SG00    vpnpool             192.168.1.250    92.168.1.254    0        5  
 
Total Pool Count: 5

Important

To configure features on the system, use the show commands specifically for these features. Refer to the Exec Mode show Commands chapter in the Command Line Interface Reference for complete information.

Service Configuration

Verify that your service was created and configured properly by entering the following command: 

show   service_type  service_name

The output is a concise listing of the service parameter settings similar to the sample displayed below. In this example, a P-GW service called pgw is configured. 

Service name                        : pgw1 
Service-Id                                  : 1 
Context                                     : test1 
Status                                      : STARTED 
Restart Counter                             : 8 
EGTP Service                                : egtp1  
LMA Service                                 : Not defined 
Session-Delete-Delay Timer                  : Enabled 
Session-Delete-Delay timeout                : 10000(msecs) 
PLMN ID List                                : MCC: 100, MNC: 99 
Newcall Policy                              : None

Context Configuration

Verify that your context was created and configured properly by entering the show context name name command.

The output shows the active context. Its ID is similar to the sample displayed below. In this example, a context named test1 is configured. 

Context Name     ContextID          State 
------------       ---------          -----  
test1              2                  Active

System Configuration

Verify that your entire configuration file was created and configured properly by entering the show configuration command.

This command displays the entire configuration including the context and service configurations defined above.

Finding Configuration Errors

Identify errors in your configuration file by entering the show configuration errors command.

This command displays errors it finds within the configuration. For example, if you have created a service named "service1", but entered it as "srv1" in another part of the configuration, the system displays this error.

You must refine this command to specify particular sections of the configuration. Add the section keyword and choose a section from the help menu as shown in the examples below. 

show configuration errors section ggsn-service

or 

show configuration errors section aaa-config

If the configuration contains no errors, an output similar to the following is displayed: 

############################################################################## 
Displaying Global
AAA-configuration errors ##############################################################################
Total 0 error(s) in this section !

Synchronizing File Systems

Whenever changes are made to a configuration or StarOS version boot order on the active CF, the file systems must be synchronized with the standby CF. This assures that the changes are identically maintained across the management cards.

Enter the following Exec mode command to synchronize the local file systems: 

[local]host_name# filesystem synchronize all

The filesystem command supports multiple keywords that allow you to check for and repair file system corruption, as well as synchronize a file system with a specific storage device. For additional information, see the Exec Mode Commands chapter in the Command Line Interface Reference.

Synchronizing Boot File for Service Function Cards

To synchronize the boot file for all the Service Function (SF) VPC-DI non-management cards, use the following CLI executable command:

[local]host_name# system synchronize boot

This assures that the changes in boot file are identically maintained across the SF cards.

Ensure that you execute this command before reload for version upgrade from any version less than mh14 to mh14 or later.

Saving the Configuration

These instructions assume that you are at the root prompt for the Exec mode: 

[local]host_name#

To save your current configuration, enter the following command: 

save configuration url [ obsolete-encryption | showsecrets | verbose ] [ -redundant ] [ -noconfirm ]

url specifies the location in which to store the configuration file. It may refer to a local or a remote file.


Important

Do not use the "/" (forward slash), ":" (colon) or "@" (at sign) characters when entering a string for the following URL fields: directory, filename, username, password, host or port#.


Important

The -redundant keyword saves a configuration file to the standby CF virtual machine. This command does not synchronize the local file system. If you have added, modified, or deleted other files or directories to or from a local device for the active CF VM, you must synchronize the local file system on both CF VMs. See Synchronizing File Systems.


Important

The obsolete-encryption and showsecrets keywords have been removed from the save configuration command in StarOS 19.2 and higher. If you run a script or configuration that contains the removed keyword, a warning message is generated.


Note

Although usb1 and usb2 keyword options are available in this command, this options are only available if the devices have been configured for the server via the hypervisor. This involves creating a virtual controller and specifying the available devices.

The recommended procedure is to save VPC configurations to an external network device.

For complete information about the above command, see the Exec Mode Commands chapter of the Command Line Interface Reference.

To save a configuration file called system.cfg to a directory that was previously created called cfgfiles, enter the following command: 

save configuration /flash/cfgfiles/system.cfg

To save a configuration file called simple_ip.cfg to a directory called host_name_configs, using an FTP server with an IP address of 192.168.34.156, on which you have an account with a username of administrator and a password of secure, use the following command: 

save configuration sftp://administrator:secure@192.168.34.156/host_name_configs/ simple_ip.cfg

To save a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command: 

save configuration tftp://config_server/init_config.cfg