Managing Configurations

Viewing Configurations

When you enter configuration commands, it immediately affects the SCE platform operation and configuration. This configuration, referred to as the running-config, is saved in the SCE platform volatile memory and is effective while the SCE platform is up. After reboot, the SCE platform loads the startup-config, which includes the non-default configuration that was saved by the user, into the running-config.

The SCE platform provides commands for:

•Viewing the running configuration with only user-configured (non-default) values: show running-config

•Viewing the running configuration with all the SCE platform running configuration values, whether default or not: show running-config all-data

•Viewing the startup configuration: show startup-config

After configuring the SCE platform, you may query for the running configuration using the command show running-config.

How to Save or Change the Configuration Settings

When you make changes to the current running configuration and you want those changes to continue to be in effect when the system restarts, you must save the changes before leaving the management session. You do that by saving the running configuration to the startup configuration file.

The SCE platform provides multiple interfaces for the purpose of configuration and management. All interfaces supply an API to the same database of the SCE platform and any configuration made through one interface is reflected through all interfaces. Furthermore, when saving the running configuration to the startup configuration from any management interface, all configuration settings are saved regardless of the management interface used to set the configuration.

For backup purposes, the old startup-config file is saved under the directory: /system/prevconf. Refer to Restoring a Previous Configuration for an explanation on how to restore a previous configuration.

To remove a configuration command from the running-config, use the no form of the command.

Step 1 At the SCE# prompt, type show running-config to view the running configuration.

The running configuration is displayed.

Step 2 Check the displayed configuration to make sure that it is set the way you want. If not, make the changes you want before saving.

Step 3 Type copy running-config startup-config.

The system saves all running configuration information to the configuration file, which is used when the system reboots.

The configuration file holds all information that is different from the system default in a file called config.tx1 located in the directory: /system.

Example for Saving or Changing the Configuration Settings

The following example shows how to save the running configuration file (first displaying the file to review the settings).

Tip To remove a configuration command from the running-config, use the no form of the command.

The following example illustrates how to remove all DNS settings from the running configuration.

SCE(config)#no ip name-server

Restoring a Previous Configuration

When you save a new configuration, the system automatically backs up the old configuration in the directory /system/prevconf/. Up to nine versions of the startup configuration file are saved, namely config.tx1-config.tx9, where config.tx1 is the most recently saved file.

You can view the old startup configuration files using the CLI command more.

How to Display the SCE Platform Version Information

Use this command to display global static information on the SCE platform, such as software and hardware version, image build time, system uptime, last open packages names and information on the SLI application assigned.

Step 1 From the SCE> prompt, type show version and press Enter.

Example for Displaying the SCE Platform Version Information

The following example shows how to display the SCE platform version information.

How to Display the SCE Platform Inventory

Unique Device Identification (UDI) is a Cisco baseline feature that is supported by all Cisco platforms. This feature allows network administrators to remotely manage the assets in their network by tracing specific devices through either CLI or SNMP. The user can display inventory information for a remote device via either:

How to Display the System Uptime

Use this command to see how long the system has been running since the last reboot.

Step 1 At the SCE> prompt, type show system-uptime and press Enter.

Example for Displaying the System Uptime

The following example shows how to display the system uptime of the SCE platform.

SCE#show system-uptime
Cisco SCE8000 uptime is 21 minutes, 37 seconds

Monitoring Control Processor CPU Utilization

You can monitor the CPU utilization of the control processor by displaying the actual load on the control processor. This feature provides visibility into the performance envelop of the Control processor under different management schemes.

Information regarding CPU utilization is available using any of the following methods:

•SNMP—The Cisco Process MIB shows the CPU utilization of both the control processor and the traffic processors. An SNMP walk on the cpmCPUTotalTable provides information regarding overall CPU statistics.

•CLI commands—The following admin level CLI commands can be used to monitor CPU utilization:

–show processes cpu

–show processes cpu sorted

–show snmp MIB cisco-process

•SCE support file—The entire measured CPU utilization of the control processor, as well as a number of specific internal tasks that were marked important to track, is written to the SCE log files , which are part of the SCE support file. This data can be used to monitor the CPU utilization trend of the control processor and the specific internal tasks over time or to view the CPU utilization required for a specific event.

CLI Commands for Monitoring Control Processor CPU Utilization

Use this command to display the CPU utilization of the control processor.

Tip To display the CPU history sorted by percentage of utilization, use the sorted keyword.

Example for Monitoring Control Processor CPU Utilization

The following example shows how to display the CPU utilization of the control processor.

SCE>show processes cpu

CPU utilization for five seconds: 24%/ 0%; one minute: 29%; five minutes: 20%

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

1 78790 6374 0 0.00% 0.00% 0.00% 0 (init)

2 10 1 0 0.00% 0.00% 0.00% 0 (kthreadd)

3 5010 501 0 0.00% 0.00% 0.00% 0 (migration/0)

4 90 9 0 0.00% 0.00% 0.00% 0 (ksoftirqd/0)

5 63130 6313 0 0.00% 0.00% 0.00% 0 (watchdog/0)

6 4940 494 0 0.00% 0.00% 0.00% 0 (migration/1)

7 0 0 0 0.00% 0.00% 0.00% 0 (ksoftirqd/1)

8 10530 1053 0 0.00% 0.00% 0.00% 0 (watchdog/1)

9 2606490 207337 0 0.00% 0.02% 0.03% 0 (events/0)

10 1246730 123793 0 0.00% 0.02% 0.02% 0 (events/1)

11 0 0 0 0.00% 0.00% 0.00% 0 (khelper)

12 177810 17781 0 0.00% 0.00% 0.00% 0 (kblockd/0)

13 8010 801 0 0.00% 0.00% 0.00% 0 (kblockd/1)

16 0 0 0 0.00% 0.00% 0.00% 0 (kswapd0)

17 0 0 0 0.00% 0.00% 0.00% 0 (aio/0)

18 0 0 0 0.00% 0.00% 0.00% 0 (aio/1)

19 0 0 0 0.00% 0.00% 0.00% 0 (nfsiod)

20 0 0 0 0.00% 0.00% 0.00% 0 (mtdblockd)

21 1198570 119326 0 0.00% 0.02% 0.02% 0 (skynet)

22 7413850 741207 0 0.00% 0.11% 0.10% 0 (hw-mon-regs)

23 556170 49614 0 0.00% 0.02% 0.01% 0 (scos-dump)

24 527310 52718 0 0.00% 0.00% 0.01% 0 (wdog-kernel)

The following table lists and describes the fields in the show processes cpu output.

Table 3-1 show processes cpu Output Fields

Field

Description

CPU utilization for five seconds

CPU utilization for the last five seconds. The first number indicates the total, the second number indicates the percent of CPU time spent at the interrupt level.

one minute

CPU utilization for the last minute

five minutes

CPU utilization for the last five minutes

PID

The process ID

Runtime (msecs)

CPU time the process has used, expressed in msecs

Invoked

The number of times the process has been invoked (progress once every 5sec)

uSecs

Microseconds of CPU time for each process invocation

5Sec

CPU utilization by task in the last five seconds

1Min

CPU utilization by task in the last minute

5Min

CPU utilization by task in the last five minutes

TTY

Currently not relevant in the Cisco Service Control system.

Process

Name of the process. For more information, refer to The Processes section of this document.

Note Linux tasks are also presented as processes.

Note When CPU utilization is higher than about 90%, the CPU utilization per task is not reliable and can sum to more than 100%. This is because high CPU utilization can influence the task that samples CPU utilization.

Rebooting and Shutting Down the SCE Platform

Rebooting the SCE Platform

Rebooting the SCE platform is required after installing a new package, in order for that package to take effect. There might be other occasions where rebooting the SCE platform is necessary.

Note When the SCE restarts, it loads the startup configuration, so all changes made in the running configuration will be lost. You are advised to save the running configuration before performing reload, as described in How to Save or Change the Configuration Settings.

Examples for Rebooting the SCE Platform

SCE# reload
Are you sure? Y.
the system is about to reboot, this will end your CLI session

How to Shut Down the SCE Platform

Shutting down the SCE platform is required before turning the power off. This helps to ensure that non-volatile memory devices in the SCE platform are properly flushed in an orderly manner.

Note When the SCE platform restarts, it loads the startup configuration, so all changes made in the running configuration will be lost. You are advised to save the running configuration before performing reload, as described in How to Save or Change the Configuration Settings.

Step 1 Connect to the serial console port (The CON connector on the front panel of the Service Control module in slot #1, 9600 baud).

The SCE# prompt appears.

Step 2 Type reload shutdown.

A confirmation message appears.

Step 3 Type y to confirm the shutdown request and press Enter.

Examples for Shutting Down the SCE Platform

The following example shows the commands for system shutdown.

SCE#reload shutdown
You are about to shut down the system.
The only way to resume system operation after this
is to cycle the power off, and then back on.
Continue?
y
IT IS NOW SAFE TO TURN THE POWER OFF.

Note Since the SCE platform can recover from the power-down state only by being physically turned off (or cycling the power), this command can only be executed from the serial CLI console. This limitation helps prevent situations in which a user issues this command from a Telnet session, and then realizes he or she has no physical access to the SCE platform.