CLI Commands to Verify a Successful Installation
Revised: August 23, 2010, OL-19897-02
Introduction
When you have completed the installation of your Cisco SCE8000 GBE platform, we recommend that you run a number of CLI commands to verify that the proper components have been successfully installed and are operational.
Basic Post-Installation Checklist
The following table provides a basic post-installation checklist with the related CLI commands. Further verification of the system configuration would depend on the specific topology and configuration of the installation, but this list will verify that the basic installation is operational.
Refer to the descriptions of the individual commands for samples of the command output. Relevant information in the output is in bold.
|
|
|
version |
show version |
Check the following: • firmware version • application version • management agent status • management agent version |
optics |
show inventory |
In the physical inventory of the SCE platform, verify that the installed optics are supported by the interfaces. |
port configuration |
show interface |
Run this command for each port to get a listing of the status and configuration of all ports. |
operational status |
show system operational status |
Status should be operational. This command will give you an indication of problems such as a power problem or external bypass not configured properly. |
linecard status |
show interface linecard |
It should not be shutdown or silent. |
connection mode |
show interface linecard connection-mode |
Make sure that both the connection mode and the failure mode are configured correctly. |
link mode |
show interface linecard link mode |
When connection-mode is inline, link mode should be configured to forwarding. |
external bypass configuration |
show interface linecard external-bypass |
Only if external bypass modules are installed: Check the following: • Configuration should be activated on failure • The number of devices should match the number of links |
RDR formatter |
show RDR-formatter |
Verify the following: • The RDR formatter has established a connection with the configured destinations • The redundancy status is configured correctly in case of more then one destination. |
connection to Subscriber Manager |
show interface linecard subscriber sm-connection-failure |
If using SM: Verify that the connection with the SM is established. |
connection to Quota Manager |
show ip rpc-adapter sessions |
If using QM: Verify that the connection with the QM is established. |
Complete command sequence for a fully-populated SCE8000 GBE platform using both the SM and the QM
SCE>enable 5
Password:<cisco>
SCE>show version
SCE>show inventory
SCE>show interface GigabitEthernet 3/0/0
SCE>show interface GigabitEthernet 3/0/1
SCE>show interface GigabitEthernet 3/0/2
SCE>show interface GigabitEthernet 3/03
SCE>show interface GigabitEthernet 3/0/4
SCE>show interface GigabitEthernet 3/0/5
SCE>show interface GigabitEthernet 3/0/6
SCE>show interface GigabitEthernet 3/0/7
SCE>show interface GigabitEthernet 3/1/0
SCE>show interface GigabitEthernet 3/1/1
SCE>show interface GigabitEthernet 3/1/2
SCE>show interface GigabitEthernet 3/1/3
SCE>show interface GigabitEthernet 3/1/4
SCE>show interface GigabitEthernet 3/1/5
SCE>show interface GigabitEthernet 3/1/6
SCE>show interface GigabitEthernet 3/1/7
SCE>show system operation-status
SCE>show interface linecard 0
SCE>show interface linecard 0 connection-mode
SCE>show interface linecard 0 link mode
SCE>show interface linecard 0 external-bypass
SCE>show rdr-formatter
SCE>show interface linecard 0 subscriber sm-connection-failure
SCE>show ip rpc-adapter sessions
CLI Command Output Samples
The text in bold in the following output samples indicates the lines you should check when doing a post-installation check. For some commands, the output is short and the entire output is relevant. In these cases, nothing is in bold.
show version
Look for the following lines:
•
System version
•
Application file
•
Management agent interface version
System version: Version 3.5.5 Build 252
Build time: May 31 2009, 15:50:44 (Change-list 483168)
Software version is: Version 3.5.5 Build 252
kernel : [kernel] 2.3.0/1 (inactive: [kernel] 2.3.0/1)
u-boot : [uboot] 2.1.0/1 (field: [uboot] 0.8.1/13)
select : [ubs-cf0] 2.3.0/1 (secondary: [ubs-cf0] 2.3.0/1)
part-num : 73-10598-01 36
cpu (eeprom): 2.1, 1000MHz
cf : Model=SMART CF, S/N=20080213025D41EC41EC, FwRev=0x20060811, Size=4062240KB
cpu (eeprom): 2.1, 1500MHz
cpu (eeprom): 2.1, 1500MHz
part-num : 73-10947-01 22
Part number : 73-10598-01 36
LineCard S/N : CAT1151G012
SML Application information is:
Application file: /apps/data/scos/app/en355262.sli
Application name: Engage SML Version 3.5.5 build 74
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'.
Management agent interface version: SCE Agent 3.5.5 Build 121
Software package file: ftp://ftpserver/D:\pcube\Os\3.5.5\252\simba_03550252_K9.pkg
SCE8000 uptime is 4 days, 21 hours, 40 minutes, 37 seconds
show inventory
Look for the following lines:
•
All lines containing the text `NAME: "SCE8000 optic'. There should be one line for each installed optic.
NAME: "SCE8000 Chassis", DESCR: "SCE8000"
PID: SCE8000 , VID: V01, SN: FOX1235GP98
NAME: "SCE8000 Service Control Module (SCM) in slot 1", DESCR: """"
PID: "" , VID: "" , SN: CAT1151G012
NAME: "SCE8000 SPA Interface Processor (SIP) in slot 3", DESCR: """"
PID: "" , VID: "" , SN: CAT1150G075
NAME: "SCE8000 SPA module 3/0", DESCR: "SPA-8X1GE-V2"
PID: SPA-8X1GE-V2 , VID: V02, SN: JAE13020GQ5
NAME: "SCE8000 SPA module 3/1", DESCR: "SPA-8X1GE-V2"
PID: SPA-8X1GE-V2 , VID: V02, SN: JAE13020GN3
NAME: "SCE8000 SPA module 3/2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE114967LE
NAME: "SCE8000 SPA module 3/3", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11485LCX
NAME: "SCE8000 FAN 1", DESCR: "SCE8000-FAN"
PID: SCE8000-FAN , VID: V01, SN: DCH12130763
NAME: "SCE8000 AC power supply 1", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V02, SN: APS1216006R
NAME: "SCE8000 AC power supply 2", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V02, SN: APS12160070
NAME: "SCE8000 optic 3/0/0", DESCR: "N/A "
PID: N/A , VID: "" , SN: FNS0853G1T5
NAME: "SCE8000 optic 3/0/1", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WHD
NAME: "SCE8000 optic 3/0/2", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WF5
NAME: "SCE8000 optic 3/0/3", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WF9
NAME: "SCE8000 optic 3/0/4", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WDT
NAME: "SCE8000 optic 3/0/5", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WE7
NAME: "SCE8000 optic 3/0/6", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WDY
NAME: "SCE8000 optic 3/0/7", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12320WF1
NAME: "SCE8000 optic 3/1/0", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12330A8J
NAME: "SCE8000 optic 3/1/1", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12330A80
NAME: "SCE8000 optic 3/1/2", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12330A7R
NAME: "SCE8000 optic 3/1/3", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS12330A92
NAME: "SCE8000 optic 3/1/4", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS124615JN
NAME: "SCE8000 optic 3/1/5", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS124615K9
NAME: "SCE8000 optic 3/1/6", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS124702V5
NAME: "SCE8000 optic 3/1/7", DESCR: "SFP-GE-S "
PID: SFP-GE-S , VID: V01, SN: FNS1247026J
NAME: "SCE8000 optic 3/2/0", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: ONT1102108E
NAME: "SCE8000 optic 3/3/0", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: ECL11030105
show interface
Run this command for each interface. The command syntax is:
show interface GigabitEthernet 3/bay-number/port-number
sce>show interface GigabitEthernet 3/0/0
Auto negotiation configured: Disabled
Auto negotiation: Disabled
Bandwidth (L1): 10000000 Kbps, Burst-size: 50000 bytes
Pseudo IP Address: Not Configured
show system operational status
sce>show system operation-status
System Operation status is Operational
show interface linecard
sce>show interface LineCard 0
The application assigned to slot 0 is /apps/data/scos/app/en355262.sli
Configured shutdown is off
Shutdown due to sm-connection-failure is off
Resulting current shutdown state is off
show interface linecard connection-mode
sce>show interface linecard 0 connection-mode
Connection mode is inline
slot failure mode is external-bypass
Redundancy status is standalone
show interface linecard link mode
sce>show interface linecard 0 link mode
Current link mode is : crosspath-bypass
Actual link mode on active is : forwarding
Actual link mode on failure is: crosspath-bypass
show interface linecard external-bypass
sce1>show interface linecard 0 external-bypass
External bypass current state is 'not activated'.
External bypass failure state is 'activated'.
Amount of expected external bypass devices: 4 (automatically configured).
Amount of detected external bypass devices: 4
show RDR-formatter
Look for:
•
Forwarding mode
•
Status (in Status column in the Connection Table)
Forwarding mode: redundancy
--------------------------------------------------------------------------------
| Collector | Port |Status| Priority per Category: |
| IP-Address / | | |------------------------------------------------|
| Host-Name | | | Category1 | Category2 | Category3 | Category4 |
|---------------|-------|------|-----------|------------|-----------|-----------|
| 10.240.59.39 | 33000 | up |100 primary| --- | --- | --- |
| 10.240.59.44 | 33000 | up | --- |100 primary | --- | --- |
---------------------------------------------------------------------------------
RDR: queued: 0 ,sent:60108106, thrown: 0, format-mismatch: 0
UM: queued: 0 ,sent: 0, thrown: 0
Logger: queued: 0 ,sent: 0, thrown: 0
Last time these counters were cleared: 07:36:52 EDT TUE April 28 2009
show interface linecard subscriber sm-connection-failure
If working with the Subscriber Manager, use this command to make sure the connection with the SM is established
SCE>show interface linecard 0 subscriber sm-connection-failure
Current SM link state: up.
Configured action to take when SM link is down: No action.
Changing of system operational-status to 'warning' when SM link is down: enabled.
show ip rpc-adapter sessions
If working with the Quota Manager, use this command to make sure the connection with the QM is established
sce>show ip rpc-adapter sessions
client-name=usr.SM
client-address=/10.240.59.36
started=Mon Apr 06 12:43:01 GMT-04:00 2009
received-message-num=408790
dropped-notifications-num=0
client-address=/10.240.59.36
started=Mon Apr 06 12:43:02 GMT-04:00 2009
received-message-num=5715112
sent-notifications-num=386768
dropped-notifications-num=0
client-name=mcn.QuotaManager-10.248.64.119_10.240.59.36_SCE.J.API.PRPC
client-address=/10.240.59.36
started=Mon Apr 06 12:43:03 GMT-04:00 2009
received-message-num=404194
dropped-notifications-num=0