- About this Guide
- Cisco Service Control Overview
- Introduction to the Cisco SCE8000 GBE Platform
- Cisco SCE8000 GBE Topology and Topology-Related Parameters
- Installing the Cisco SCE8000 Chassis
- Connecting the Management Interfaces
- Cabling the GBE Line Ports and Completing the Installation
- Basic Cisco SCE8000 Platform Operations
- Troubleshooting
- Removal and Replacement Procedures
- CLI Commands to Verify a Successful Installation
Cisco SCE8000 GBE Installation and Configuration Guide, Release 3.5.5
Chapter: Basic Cisco SCE8000 Platform Operations
Basic Cisco SCE8000 GBE Platform Operations
Introduction
This chapter describes how to start up the Cisco SCE8000 GBE platform, reboot, and shutdown. It also describes how to manage configurations.
•
Starting the Cisco SCE8000 GBE Platform
•Managing Cisco SCE8000 GBE Configurations
•How to Display the SCE Platform Version Information
•How to Display the SCE Platform Inventory
•How to Display the System Uptime
•Rebooting and Shutting Down the SCE Platform
Starting the Cisco SCE8000 GBE Platform
The procedures for starting the Cisco SCE8000 GBE platform are explained in the following sections:
•Checking Conditions Prior to System Startup
•Performing Complex Configurations
•Starting the System and Observing Initial Conditions
Checking Conditions Prior to System Startup
Check the following conditions before you start your Cisco SCE8000 GBE platform:
•Both power supply units are installed and connected. (If only one power supply is connected it will put the box in warning state.)
•First-time startup at installation:
–Cisco SCE8000 GBE platform connected to local console (CON port)
–The console terminal is turned on and properly configured
•Subsequent startups
–Line interfaces are properly cabled (optional)
–Cisco SCE8000 GBE platform is connected to at least one of the following types of management stations:
–Direct connection to local console (CON port)
–Remote management station via the LAN (Mng port)
Performing Complex Configurations
After you have installed your Cisco SCE8000 GBE platform hardware, checked all external connections, turned on the system power, allowed the system to boot up, and performed the initial system configuration, you might need to perform more complex configurations, which are beyond the scope of this publication.
For further information on system and interface configuration, refer to the following documents:
•Cisco SCE8000 GBE Software Configuration Guide
•Cisco SCE8000 CLI Command Reference
Starting the System and Observing Initial Conditions
After installing your Cisco SCE8000 GBE platform and connecting cables, complete the following steps to start the Cisco SCE8000 GBE platform:
Step 1 Make sure the power cables are connected to the Cisco SCE8000 GBE platform.
Step 2 Plug the AC power supply cables into the AC power source, or make sure the circuit breakers at the DC panels are turned to the on position. Turn on the switches on both power supplies.
Step 3 Listen for the fans; you should immediately hear them operating.
Step 4 During the boot process, observe the following LEDs on the SCE8000-SCM-E:
•The Power LEDs should be green.
•Optical Bypass LED should be green while the Cisco SCE8000 GBE is in bypass and unlit when the optical bypass is turned off.
•The Status LED should be a constant amber while booting. After a successful boot, the Status LED is steady green.
Note It takes a several minutes for the Cisco SCE8000 GBE to boot and for the status LED to change from amber to green.
What to Do Next
If the system does not complete each of the steps in the startup procedure, proceed to Identifying Startup Problems for troubleshooting recommendations and procedures.
Final Tests
The procedures for performing the final tests to verify that the Cisco SCE8000 GBE is functioning properly are explained in the following sections:
•Viewing the User Log Counters
•Viewing the Gigabit Ethernet Port Status
•Viewing the Gigabit Ethernet Counters
Verifying Operational Status
After all the ports are connected, verify that the Cisco SCE8000 GBE is not in a Warning state.
Step 1 On the front panel of the Service Control module, examine the Status LED; it should be green.
Step 2 To display the operation status of the system, at the SCE# 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:
System Operation status is Operational.
If the Status LED is red or flashing amber, the following message appears:
System Operation status is Warning
Description:
1. Power Supply problem
2. Line feed problem
3. Amount of External bypass devices detected is lower than expected amount
Viewing the User Log Counters
View the user log for errors that occurred during the installation process.
Step 1 At the SCE# prompt, type show logger device user-file-log counters and press Enter.
Examples for Viewing the User Log Counters
The following example shows the current User-File-Log device counters.
SCE#show logger device user-file-log counters Logger 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 the Gigabit Ethernet Port Status
Step 1 At the SCE# prompt, type show interface GigabitEthernet 3/ baynumber /port-number.
This displays the port link status.
The following example displays a system response.
SCE#show interface GigabitEthernet 3/1/0 Actual Status: Link is on Bandwidth: 10000000Kbps Burst-size: 500000bytes
Viewing the Gigabit Ethernet Counters
In an inline topology, you can monitor traffic via the platform counters for both the Rx and Tx connections. The counters increase as packets flow through the Cisco SCE8000 GBE for both Rx and Tx.
However, in receive-only topologies, the counters for the Tx do not increment, as the SCE8000 GBE is only monitoring traffic, and not re-transmitting it
Step 1 At the SCE# prompt, type show interface GigabitEthernet 3/ baynumber /port-number counters.
This displays the GigabitEthernet counters. This command enables you to verify that there is traffic on the line. You can see that the counters increase, together with real-time packet flow through the Cisco SCE8000 GBE .
Remember, in bump-in-the-wire topology, both the Rx and Tx counters apply as traffic monitors. For receive-only topologies, using an external splitter, only the Rx counters apply.
The following example shows the counters of the first Gigabit Ethernet interface.
SCE#show interface GigabitEthernet 3/0/0 counters In total octets: 100 In good unicast packets: 90 In good multicast packets: 0 In good broadcast packets: 10 In packets discarded: 0 In packets with CRC/Alignment error: 0 In undersized packets: 0 In oversized packets: 0 Out total octets: 93*2^32+1022342538 Out unicast packets: 858086051 Out non unicast packets: 0 Out packets discarded: 0
Managing Cisco SCE8000 GBE Configurations
After you have installed your SCE8000 GBE platform hardware, checked all external connections, turned on the system power, and allowed the system to boot up, you are ready to install the Service Control application. However, before you install the application, you might need to configure the SCE platform. Instructions for configuring the SCE8000 GBE platform are beyond the scope of this publication.
For further information on system and interface configuration, refer to the following documents:
•Cisco SCE8000 GBE Software Configuration Guide
•Cisco SCE8000 CLI Command Reference
The procedures for managing Cisco SCE8000 GBE configurations are explained in the following sections:
•Saving or Changing the Configuration Settings
•Restoring a Previous Configuration
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.
Step 1 At the SCE# prompt, type show running-config.
The system shows the running configuration.
SCE#show running-config #This is a general configuration file (running-config). #Created on 17:17:59 UTC WED June 3 2009
#cli-type 1 #version 1
no management-agent notifications notification-list 1417,1418,804,815,1404,1405,1406,1407,1408,400 no management-agent notifications notification-list 402,421,440,441,444,445,446,450,437,457 no management-agent notifications notification-list 3593,3594,3595,10040
interface LineCard 0
connection-mode inline on-failure external-bypass no silent no shutdown replace spare-memory code bytes 3145728
interface GigabitEthernet 1/1 ip address 10.56.108.68 255.255.255.0
interface GigabitEthernet 3/0/0
interface GigabitEthernet 3/0/1
interface GigabitEthernet 3/0/2
interface GigabitEthernet 3/0/3
interface GigabitEthernet 3/0/4
interface GigabitEthernet 3/0/5
interface GigabitEthernet 3/0/6
interface GigabitEthernet 3/0/7
interface GigabitEthernet 3/1/0
interface GigabitEthernet 3/1/1
interface GigabitEthernet 3/1/2
interface GigabitEthernet 3/1/3
interface GigabitEthernet 3/1/4
interface GigabitEthernet 3/1/5
interface GigabitEthernet 3/1/6
interface GigabitEthernet 3/1/7
interface TenGigabitEthernet 3/2/0
interface TenGigabitEthernet 3/3/0
interface GigabitEthernet 1/3/0/0
interface GigabitEthernet 1/3/0/1
interface GigabitEthernet 1/3/0/2
interface GigabitEthernet 1/3/0/3
interface GigabitEthernet 1/3/0/4
interface GigabitEthernet 1/3/0/5
interface GigabitEthernet 1/3/0/6
interface GigabitEthernet 1/3/0/7
interface GigabitEthernet 1/3/1/0
interface GigabitEthernet 1/3/1/1
interface GigabitEthernet 1/3/1/2
interface GigabitEthernet 1/3/1/3
interface GigabitEthernet 1/3/1/4
interface GigabitEthernet 1/3/1/5
interface GigabitEthernet 1/3/1/6
interface GigabitEthernet 1/3/1/7
exit
line vty 0 4 exit subscriber LEG dhcp-lease-query servers 127.0.0.1 logger device SCE-agent-Statistics-Log max-file-size 204800 management-agent property "com.pcube.management.framework.install.activation.operation" "Install" management-agent property "com.pcube.management.framework.install.activated.version" "3.5.5 build 262" management-agent property "com.pcube.management.framework.install.activated.package" "SCA BB" management-agent property "com.pcube.management.framework.install.activation.date" "Wed Jun 03 17:01:09 GMT+00:00 2009" flow-filter partition name "ignore_filter" first-rule 4 num-rules 32
Saving or Changing 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).
SCE#show running-config #This is a general configuration file (running-config). #Created on 17:17:59 UTC WED June 3 2009
#cli-type 1 #version 1
no management-agent notifications notification-list 1417,1418,804,815,1404,1405,1406,1407,1408,400 no management-agent notifications notification-list 402,421,440,441,444,445,446,450,437,457 no management-agent notifications notification-list 3593,3594,3595,10040
interface LineCard 0
connection-mode inline on-failure external-bypass no silent no shutdown replace spare-memory code bytes 3145728
interface GigabitEthernet 1/1 ip address 10.56.108.68 255.255.255.0
interface GigabitEthernet 3/0/0
interface GigabitEthernet 3/0/1
interface GigabitEthernet 3/0/2
interface GigabitEthernet 3/0/3
interface GigabitEthernet 3/0/4
interface GigabitEthernet 3/0/5
interface GigabitEthernet 3/0/6
interface GigabitEthernet 3/0/7
interface GigabitEthernet 3/1/0
interface GigabitEthernet 3/1/1
interface GigabitEthernet 3/1/2
interface GigabitEthernet 3/1/3
interface GigabitEthernet 3/1/4
interface GigabitEthernet 3/1/5
interface GigabitEthernet 3/1/6
interface GigabitEthernet 3/1/7
interface TenGigabitEthernet 3/2/0
interface TenGigabitEthernet 3/3/0
interface GigabitEthernet 1/3/0/0
interface GigabitEthernet 1/3/0/1
interface GigabitEthernet 1/3/0/2
interface GigabitEthernet 1/3/0/3
interface GigabitEthernet 1/3/0/4
interface GigabitEthernet 1/3/0/5
interface GigabitEthernet 1/3/0/6
interface GigabitEthernet 1/3/0/7
interface GigabitEthernet 1/3/1/0
interface GigabitEthernet 1/3/1/1
interface GigabitEthernet 1/3/1/2
interface GigabitEthernet 1/3/1/3
interface GigabitEthernet 1/3/1/4
interface GigabitEthernet 1/3/1/5
interface GigabitEthernet 1/3/1/6
interface GigabitEthernet 1/3/1/7
exit
line vty 0 4 exit subscriber LEG dhcp-lease-query servers 127.0.0.1 logger device SCE-agent-Statistics-Log max-file-size 204800 management-agent property "com.pcube.management.framework.install.activation.operation" "Install" management-agent property "com.pcube.management.framework.install.activated.version" "3.5.5 build 262" management-agent property "com.pcube.management.framework.install.activated.package" "SCA BB" management-agent property "com.pcube.management.framework.install.activation.date" "Wed Jun 03 17:01:09 GMT+00:00 2009" flow-filter partition name "ignore_filter" first-rule 4 num-rules 32 SCE#copy running-config startup-config Writing general configuration file to temporary location... Backing-up general configuration file... Copy temporary file to final location... SCE#
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.
Restoring a previous startup configuration means renaming the file so it overwrites the startup configuration (config.txt) file.
Step 1 At the SCE# prompt, type more /system/prevconf/config.tx1 to view the configuration file.
The system displays the configuration information stored in the file.
Step 2 Read the configuration information to make sure it is the configuration you want to restore.
Note that you cannot undo the configuration restore command.
Step 3 Type copy /system/config.tx1 /system/config.txt.
The system sets the startup configuration to the configuration from config.tx1.
Example for Restoring a Previous Configuration
The following example displays a saved configuration file and then restores the file to overwrite the current configuration.
SCE#more /system/prevconf/config.tx1 #This is a general configuration file (running-config). #Created on 17:17:59 UTC WED June 3 2009
#cli-type 1 #version 1
no management-agent notifications notification-list 1417,1418,804,815,1404,1405,1406,1407,1408,400 no management-agent notifications notification-list 402,421,440,441,444,445,446,450,437,457 no management-agent notifications notification-list 3593,3594,3595,10040
interface LineCard 0
connection-mode inline on-failure external-bypass no silent no shutdown replace spare-memory code bytes 3145728
interface GigabitEthernet 1/1 ip address 10.56.108.68 255.255.255.0
interface GigabitEthernet 3/0/0
interface GigabitEthernet 3/0/1
interface GigabitEthernet 3/0/2
interface GigabitEthernet 3/0/3
interface GigabitEthernet 3/0/4
interface GigabitEthernet 3/0/5
interface GigabitEthernet 3/0/6
interface GigabitEthernet 3/0/7
interface GigabitEthernet 3/1/0
interface GigabitEthernet 3/1/1
interface GigabitEthernet 3/1/2
interface GigabitEthernet 3/1/3
interface GigabitEthernet 3/1/4
interface GigabitEthernet 3/1/5
interface GigabitEthernet 3/1/6
interface GigabitEthernet 3/1/7
interface TenGigabitEthernet 3/2/0
interface TenGigabitEthernet 3/3/0
interface GigabitEthernet 1/3/0/0
interface GigabitEthernet 1/3/0/1
interface GigabitEthernet 1/3/0/2
interface GigabitEthernet 1/3/0/3
interface GigabitEthernet 1/3/0/4
interface GigabitEthernet 1/3/0/5
interface GigabitEthernet 1/3/0/6
interface GigabitEthernet 1/3/0/7
interface GigabitEthernet 1/3/1/0
interface GigabitEthernet 1/3/1/1
interface GigabitEthernet 1/3/1/2
interface GigabitEthernet 1/3/1/3
interface GigabitEthernet 1/3/1/4
interface GigabitEthernet 1/3/1/5
interface GigabitEthernet 1/3/1/6
interface GigabitEthernet 1/3/1/7
exit
line vty 0 4 exit subscriber LEG dhcp-lease-query servers 127.0.0.1 logger device SCE-agent-Statistics-Log max-file-size 204800 management-agent property "com.pcube.management.framework.install.activation.operation" "Install" management-agent property "com.pcube.management.framework.install.activated.version" "3.5.5 build 262" management-agent property "com.pcube.management.framework.install.activated.package" "SCA BB" management-agent property "com.pcube.management.framework.install.activation.date" "Wed Jun 03 17:01:09 GMT+00:00 2009" flow-filter partition name "ignore_filter" first-rule 4 num-rules 32 SCE#copy /system/config.tx1 /system/config.txt
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.
SCE>show version System version: Version 3.5.5 Build 253 Build time: Jun 2 2009, 17:48:38 (Change-list 484251) Software version is: Version 3.5.5 Build 253 Cryptography class: K9 Hardware information is:
--------------------- Firmware --------------------- kernel : [kernel] 2.3.0/1 (inactive: [kernel] 2.3.0/1) u-boot : [uboot] 2.1.0/1 (field: [uboot] 0.8.1/18) select : [ubs-cf1] 2.3.0/1 (secondary: [ubs-cf1] 2.3.0/1)
--------------------- Slot 1: SCE8000-SCM-E --------------------- serial-num : CAT1231G03R part-num : 73-10598-01 cpld : 0x816c vtpld : 0xc003 summit-0 : 0xf2c1001 summit-1 : 0xf2c1101 dpt/tx : 0x4913 cls/ff : 0x2112 cls cam : 0x454120 cls flow cap: 33554432 ssa : 0x90
--------------------- TVR --------------------- #cpus : 1 cpu SVR : 0x80900121 cpu PVR : 0x80040202 cpu freq : 1000MHz cpu (eeprom): 2.1, 1000MHz cpld : 0xa1bb cpld-ufm : 0xa803 summit : 0xf2c1701 cf : Model=SILICONSYSTEMS INC 4GB-3213, S/N=B8243186VCK20914MX01, FwRev=0x242-0230, Size=4125744KB phy-0 : 0xcc2 phy-1 : 0xcc2 phy-2 : 0xcc2
--------------------- CFC-0 --------------------- board type : P2 #cpus : 3 cpu-0 SVR : 0x80900121 cpu-0 PVR : 0x80040202 cpu-0 freq : 1500MHz cpu-1 SVR : 0x80900121 cpu-1 PVR : 0x80040202 cpu-1 freq : 1500MHz cpu-2 SVR : 0x80900121 cpu-2 PVR : 0x80040202 cpu-2 freq : 1500MHz cpu (eeprom): 2.1, 1500MHz cpld-0 : 0xb217 cpld-1 : 0xb217 cpld-2 : 0xb217 cpld-0-ufm : 0xb803 cpld-1-ufm : 0xb803 cpld-2-ufm : 0xb803 summit-0 : 0xf2c1301 summit-1 : 0xf2c1401 fc : 0x1100
--------------------- CFC-1 --------------------- board type : P2 #cpus : 3 cpu-0 SVR : 0x80900121 cpu-0 PVR : 0x80040202 cpu-0 freq : 1500MHz cpu-1 SVR : 0x80900121 cpu-1 PVR : 0x80040202 cpu-1 freq : 1500MHz cpu-2 SVR : 0x80900121 cpu-2 PVR : 0x80040202 cpu-2 freq : 1500MHz cpu (eeprom): 2.1, 1500MHz cpld-0 : 0xb217 cpld-1 : 0xb217 cpld-2 : 0xb217 cpld-0-ufm : 0xb803 cpld-1-ufm : 0xb803 cpld-2-ufm : 0xb803 summit-0 : 0xf2c1301 summit-1 : 0xf2c1401 fc : 0x1100
--------------------- Slot 3: SCE8000-SIP --------------------- serial-num : CAT1217G01K part-num : 73-10947-01 cpld : 0x916c summit-0 : 0xf2c1501 summit-1 : 0xf2c1601 dpt-0 : 0x322f dpt-1 : 0x322f ssa-0 : 0x90 ssa-1 : 0x90 spa[0] : SPA-8X1GE spa[1] : SPA-8X1GE spa[2] : SPA-1X10GE-L-V2 spa[3] : SPA-1X10GE-L-V2
--------------------- SCE8000 Chassis --------------------- product-num : SCE8000 serial-num : FOX1229GYVS part-num : 73-11293-01 part-rev : A0 vid : V01
Part number : 73-10598-01 Revision : 1 Software revision : 1 LineCard S/N : CAT1231G03R Power Supply type : AC
SML Application information is: Application file: /apps/data/scos/app/en355262.sli Application name: Engage SML Version 3.5.5 build 74 Using Lib - PL_3.5.5_b74 Using Lib - Classifier_3.5.5_b74 Application help: Entry point of Engage Original source file: /auto/srbu-proj1/apps/users/atukh/autoBuild/App/SML/Engage/dev/src/com/pcube/AppTemplate/M ain/template_app_main.san Compilation date: Tue, May 19, 2009 at 19:51:58 Compiler version: SANc v3.20 Build 12 built on: Tue 02/01/2009 11:11:05.;SME plugin v1.1 Capacity option used: 'EngageDefaultSCE8000'.
Logger status: Enabled
Platform: SCE8000 Management agent interface version: SCE Agent 3.5.5 Build 121 Software package file: Not available
SCE8000 uptime is 26 minutes, 53 seconds
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:
•Entity MIB (see ENTITY-MIB in the "Cisco Service Control MIBs" appendix of the Cisco SCE8000 GBE Software Configuration Guide)
•CLI show inventory command
This command displays the UDIs only for field replaceable units (FRU).
•CLI show inventory raw command.
This command displays all UDIs on the Cisco SCE8000 GBE platform.
The show inventory CLI commands display the following information:
•Device name
•Description
•Product identifier
•Version identifier
•Serial number
Step 1 From the SCE> prompt, type show inventory [raw] and press Enter.
Examples for Displaying the SCE Platform Inventory
•Displaying the SCE Platform Inventory: FRUs Only
•Displaying the Complete SCE Platform Inventory
Displaying the SCE Platform Inventory: FRUs Only
The following example shows how to display the inventory (UDIs) for the FRUs only.
SCE>show inventory
NAME: "SCE8000 GBE Chassis", DESCR: "CISCO7604"
PID: CISCO7604 , VID: V0 , SN: FOX105108X5
NAME: "SCE8000 GBE Service Control Module (SCM) in slot 1", DESCR: "SCE8000-SCM-E"
PID: SCE8000-SCM-E , VID: V0 , SN: CAT1122584N
NAME: "SCE8000 GBE SPA Interface Processor (SIP) in slot 3", DESCR: "SCE8000-SIP"
PID: SCE8000-SIP , VID: V0 , SN: CAT1150G07F
NAME: "SCE8000 SPA module 3/0", DESCR: "SPA-8X1GE"
PID: SPA-8X1GE , VID: V01, SN: SAD12180111
NAME: "SCE8000 SPA module 3/1", DESCR: "SPA-8X1GE"
PID: SPA-8X1GE , VID: V01, SN: SAD1218013R
NAME: "SCE8000 SPA module 3/2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE1229PFRZ
NAME: "SCE8000 SPA module 3/3", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE1229PFTL
NAME: "SCE8000 GBE FAN 1", DESCR: "FAN-MOD-4HS"
PID: FAN-MOD-4HS , VID: V0 , SN: DCH11013744
NAME: "SCE8000 GBE AC or DC power supply 0", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105000MV
NAME: "SCE8000 GBE AC or DC power supply 1", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105000MV
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1142N4B7
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1142N4AL
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1141N43R
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1143N4JN
Displaying the Complete SCE Platform Inventory
The following example shows how to display the complete inventory (UDIs) of the SCE platform.
SCE>show inventory raw NAME: "SCE8000 Chassis", DESCR: "SCE8000" PID: SCE8000 , VID: V01, SN: FOX1229GYVS
NAME: "SCE8000 Physical Slot 1", DESCR: "Container SCE8000 Service Control Module (SCM) slot" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 2", DESCR: "Container SCE8000 Service Control Module (SCM) slot" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 3", DESCR: "Container SCE8000 SPA Interface Processor (SIP) slot" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 4", DESCR: "Container SCE8000 Optical Bypass slot" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Fan Module", DESCR: "Container SCE8000 Fan Module" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 AC and DC power supply", DESCR: "Container SCE8000 AC and DC power supply" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link", DESCR: "Container SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Backplane", DESCR: "Container SCE8000 Backplane " PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Service Control Module (SCM) in slot 1", DESCR: "SCE8000-SCM-E" PID: SCE8000-SCM-E , VID: V01, SN: CAT1231G03R
NAME: "SCE8000 SPA Interface Processor (SIP) in slot 3", DESCR: "SCE8000-SIP" PID: SCE8000-SIP , VID: V01, SN: CAT1217G01K
NAME: "SCE8000 Link 0", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 1", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 2", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 3", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 4", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 5", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 6", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 7", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 8", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 9", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 10", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 11", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 12", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 13", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 14", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 15", DESCR: "SCE8000 Link" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/0", DESCR: "SCE8000 SIP bay" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/1", DESCR: "SCE8000 SIP bay" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/2", DESCR: "SCE8000 SIP bay" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/3", DESCR: "SCE8000 SIP bay" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SPA module 3/0", DESCR: "SPA-8X1GE" PID: SPA-8X1GE , VID: V01, SN: SAD1218013N
NAME: "SCE8000 SPA module 3/1", DESCR: "SPA-8X1GE" PID: SPA-8X1GE , VID: V01, SN: SAD1213036U
NAME: "SCE8000 SPA module 3/2", DESCR: "SPA-1X10GE-L-V2" PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE12035KTT
NAME: "SCE8000 SPA module 3/3", DESCR: "SPA-1X10GE-L-V2" PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE1229P1F3
NAME: "SCE8000 Optical bypass", DESCR: "Container SCE8000 Optical bypass" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/1", DESCR: "SCE8000 Management port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/0", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/1", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/2", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/3", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/4", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/5", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/6", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/0/7", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/0", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/1", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/2", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/3", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/4", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/5", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/6", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet3/1/7", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "TenGigabitEthernet3/2/0", DESCR: "SCE8000 Cascade port" PID: "" , VID: "" , SN: ""
NAME: "TenGigabitEthernet3/3/0", DESCR: "SCE8000 Cascade port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/0", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/1", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/2", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/3", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/4", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/5", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/6", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/0/7", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/0", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/1", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/2", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/3", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/4", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/5", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/6", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "GigabitEthernet1/3/1/7", DESCR: "SCE8000 SPA Traffic port" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 FAN 1", DESCR: "SCE8000-FAN" PID: SCE8000-FAN , VID: V01, SN: DCH12281347
NAME: "SCE8000 AC power supply 1", DESCR: "PWR-2700-AC/4" PID: PWR-2700-AC/4 , VID: V02, SN: APS1216003E
NAME: "SCE8000 AC power supply 2", DESCR: "PWR-2700-AC/4" PID: PWR-2700-AC/4 , VID: V02, SN: APS1216003J
NAME: "SCE8000 optic 3/0/0", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS1223015K
NAME: "SCE8000 optic 3/0/1", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS122305UE
NAME: "SCE8000 optic 3/0/2", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12230165
NAME: "SCE8000 optic 3/0/3", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS122305TU
NAME: "SCE8000 optic 3/0/4", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DTX
NAME: "SCE8000 optic 3/0/5", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DUU
NAME: "SCE8000 optic 3/0/6", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DUM
NAME: "SCE8000 optic 3/0/7", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DU4
NAME: "SCE8000 optic 3/1/0", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12230158
NAME: "SCE8000 optic 3/1/1", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12230156
NAME: "SCE8000 optic 3/1/2", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS122305TS
NAME: "SCE8000 optic 3/1/3", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS1223014S
NAME: "SCE8000 optic 3/1/4", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DU0
NAME: "SCE8000 optic 3/1/5", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DUD
NAME: "SCE8000 optic 3/1/6", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DTV
NAME: "SCE8000 optic 3/1/7", DESCR: "SFP-GE-S " PID: SFP-GE-S , VID: V01, SN: FNS12330DU5
NAME: "SCE8000 optic 3/2/0", DESCR: "XFP-10GLR-OC192SR " PID: XFP-10GLR-OC192SR , VID: V02, SN: ECL122200J9
NAME: "SCE8000 optic 3/3/0", DESCR: "XFP-10GLR-OC192SR " PID: XFP-10GLR-OC192SR , VID: V02, SN: ONT11481008
NAME: "SCE8000 traffic processor 1", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 2", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 3", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 4", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 5", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 6", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 7", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 8", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 9", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 10", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 11", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 12", DESCR: "SCE8000 traffic processor" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device port 0", DESCR: "SCE8000 External bypass device" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device port 1", DESCR: "SCE8000 External bypass device" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device 0/0", DESCR: "This module isn't connected" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device 0/1", DESCR: "This module isn't connected" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device 1/0", DESCR: "This module isn't connected" PID: "" , VID: "" , SN: ""
NAME: "SCE8000 External bypass device 1/1", DESCR: "This module isn't connected" PID: "" , VID: "" , SN: ""
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 GBE uptime is 21 minutes, 37 seconds
Rebooting and Shutting Down the SCE Platform
•How to Shut 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 Saving or Changing the Configuration Settings.
Step 1 At the SCE# prompt, type reload and press Enter.
A confirmation message appears.
Step 2 Type y to confirm the reboot request and press Enter.
Examples for Rebooting the SCE Platform
The following example shows the commands for system reboot.
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 Saving or Changing 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.
Feedback