Completing the Installation

This module discusses how to verify link connectivity and how to install a Service Control application.

Examining the LEDs

The GBE Link LED must be green in order to verify that an active connection exists.

The GBE Rx and Tx LEDs (if flashing green) indicate that traffic is being received or transmitted by the SCE 2000 platform, respectively.

Note that in an inline topology, the Rx and Tx LEDs indicate that packets are being received/transmitted by the SCE 2000 platform.

In optical splitter topologies, the Rx LEDs are the sole indicators. The Tx LEDs do not "blink", since the Tx is not connected to the port in this topology.

Final Tests

The procedures for performing the final tests to verify that the SCE 2000 is functioning properly are explained in the following sections.

Verifying Operational Status

After all the ports are connected, verify that the SCE 2000 is not in a Warning state.

To verify that the SCE 2000 is not in a warning state, complete the following steps:

Step 1

On the SCE 2000 Front panel, examine that the Status LED is flashing green.

Step 1

To display the operation status of the system, at the SCE 2000# prompt, type show system operation-status and press Enter.

A message displaying the operation status of the system appears. If the system is operating in order, the following message appears:

Example:

The following example displays a sample output where the LEDs appear red/orange:

SCE 2000#show system operation-statusSystem Operation status is Operational

Viewing the User Log Counters

Step 1

At the SCE 2000# prompt, type show logger device User-File-Log counters and press Enter.

EXAMPLE:

SCE 2000#show logger device user-file-log countersLogger device User-File-Log counters: 
Total info messages: 1 
Total warning messages: 0 
Total error messages: 0 
Total fatal messages: 0

If there are "Total error messages" or "Total fatal messages", use the show logger device User-File-Log command to display details about the errors.

Viewing Configuration

When you enter configuration commands, it immediately effects 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 as saved by the user, into the running-config.

After configuring the SCE platform, you may query for the running configuration using the command show running-config. This command displays the non-default running configuration. To view all SCE platform running configuration, whether it is the default or not, you may use the option all-data in the show running-config command.

SCE 2000#show running-config#This is a general configuration file (running-config). 
#Created on 15:50:56  CET  MON  December  11  2005 
#cli-type 1 
#version 1 
clock timezone CET 1 
snmp-server community "public" ro 
snmp-server host 10.1.1.253 traps version 1 "public" 
interface LineCard 0 
connection-mode active 
no silent 
no shutdown 
flow-aging default-timeout UDP 60 
interface FastEthernet 0/0 
ip address 10.1.5.109 255.255.0.0 
interface FastEthernet 0/1 
interface FastEthernet 0/2 
exit 
line vty 0 4 
no timeout 
exit 
SCE 2000#

Saving the Configuration Settings

When you make changes to the current running configuration and you want those changes to continue to be valid when the system restarts, you must save the changes before leaving the management session, that is, you must save 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.

SUMMARY STEPS

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

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

DETAILED STEPS

Step 1

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

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.

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.txt located in the directory: tffs0:system.

Examples

EXAMPLE 1:

SCE 2000#show running-config#This is a general configuration file (running-config). 
#Created on 15:50:56  CET  MON  February  11  2006 
#cli-type 1 
#version 1 
clock timezone CET 1 
snmp-server community "public" ro 
snmp-server host 10.1.1.253 traps version 1 "public" 
interface LineCard 0 
connection-mode active 
no silent 
no shutdown 
flow-aging default-timeout UDP 60 
interface FastEthernet 0/0 
ip address 10.1.5.109 255.255.0.0 
interface FastEthernet 0/1 
interface FastEthernet 0/2 
exit 
line vty 0 4 
no timeout 
exit 
SCE 2000#      
SCE 2000#copy running-config startup-config 
Writing general configuration file to temporary location... 
Backing-up general configuration file... 
Copy temporary file to final location... 
SCE 2000#

For backup purposes, the old startup-config file is saved under the directory: tffs0:system/prevconf.

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

EXAMPLE 2:

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

Table Of Contents