|
|
Table Of Contents
environment-monitor shutdown fan
environment-monitor shutdown temperature
environment-monitor temperature-threshold
show optical wavelength mapping
show upgrade-info functional-image
System Management Commands
Use the following commands to manage your Cisco ONS 15530.
clear facility-alarm
To clear the external indications for the facility alarms, use the clear facility-alarm command.
clear facility-alarm [critical | major | minor]
Syntax Description
Defaults
Clears all external alarm indications and LEDs.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
EV-Release
•
•
Usage Guidelines
Use this command to perform a one-time clear of the specified LEDS and external audible and visual alarm relays.
The facility alarm conditions and alarm threshold error conditions are still posted in the processor memory and can be seen by using the show facility-alarm status command. You can clear the alarm threshold error conditions in memory by disabling protocol monitoring using the no monitor enable command. Online removal of a component or disabling an interface with the shutdown command also clears an alarm from processor memory.
Examples
The following examples shows how to clear critical external facility alarm indications.
Switch# clear facility-alarm criticalRelated Commands
Enables signal monitoring for certain protocol encapsulations.
Shows the facility alarm status information.
Disables an interface.
environment-monitor shutdown fan
To enable the fan failure shutdown feature, use the environment-monitor shutdown fan command. To disable fan failure shutdown, use the no form of the command.
environment-monitor shutdown fan
no environment-monitor shutdown fan
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
If a single fan fails on the Cisco ONS 15530, a minor alarm is reported to the CPU switch module. However, the chassis will never reach a critical high temperature when only one fan fails.
If two or more fans fail, a major alarm is reported to the CPU switch module.
If all six fans in the fan tray fail, the chassis will reach critical temperature after 4 minutes.
To prevent damage to the cards and modules in the shelf when two or more fans fail, use the environment-monitor shutdown fan command to configure the system to automatically reset the following components:
•
•
•
•
•
In addition, the ITU lasers on the transponder line cards are powered off.
To recover from fan failure shutdown, you must power-cycle the shelf.
Caution
Caution
Examples
The following example shows how to enable fan failure shutdown.
Switch#configure terminalSwitch(config)#environment-monitor shutdown fanRelated Commands
environment-monitor shutdown temperature
To enable the automatic shutdown of the system if the operating temperature exceeds the critical threshold, use the environment-monitor shutdown temperature command. To disable this feature, use the no form of the command.
environment-monitor shutdown temperature slot /subslot/module
no environment-monitor shutdown temperature
Syntax Description
slot
Specifies a chassis slot.
subslot
Specifies a chassis sub slot.
module
Specifies a temperature sensor module.
Defaults
Enabled
Command Modes
Global configuration
Command History
This table includes the following release-specific history entry:
Usage Guidelines
The Cisco ONS 15530 system automatically resets the following cards if the operating temperature exceeds the critical threshold:
•
•
•
•
•
•
All the other cards will be shutdown if the operating temperature exceeds the critical threshold. In addition, the ITU lasers on the trunk cards will be powered off. Though possible, Cisco does not recommend that you disable this feature.
To recover from a shutdown, you must power-cycle the shelf.
Caution
Caution
Examples
The following example shows how to enable the automatic shutdown of the system if the operating temperature exceeds the critical threshold:
Switch#configure terminalSwitch(config)#environment-monitor shutdown temperature 6/0/0Related Commands
Displays the temperature sensor and fan status.
Changes the default threshold temperatures.
environment-monitor temperature-threshold
To change the default threshold temperatures, use the environment-monitor temperature-threshold command. To reset all the thresholds to the default values for all temperature sensor modules, use the no form of the command.
environment-monitor temperature-threshold {critical | major | minor | low} slot/subslot/module <threshold value>
no environment-monitor temperature-threshold
Syntax Description
Defaults
The following table provides the default threshold temperatures for the alarms:
Command Modes
Global configuration
Command History
This table includes the following release-specific history entry:
Usage Guidelines
If you do not specify the threshold temperature for an alarm (critical, major, minor, or low), the threshold will be reset to the default value. If you do not specify the temperature sensor module as well, the threshold temperature will be reset for all the temperature sensor modules.
Examples
The following example shows how to configure the critical threshold temperature:
Switch#configure terminalSwitch(config)#environment-monitor temperature-threshold critical 6/0/0 65Related Commands
Displays the temperature sensor and fan status.
Enables the automatic shutdown of the system if the operating temperature exceeds the critical threshold
reload
To reload the active CPU switch module, use the reload command.
reload [text | in [hh:]mm [text] | at hh:mm [month day | day month] [text] | cancel]
Syntax Description
Defaults
Immediate active CPU switch module reload
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command halts the active CPU switch module. If the CPU switch module is set to restart on error, it reboots itself.
Use this command after configuration information is entered into a file and saved to the startup configuration. You cannot reload from a virtual terminal if the CPU switch module is not set up for automatic booting. This prevents the CPU switch module from dropping to the ROM monitor and thereby taking the CPU switch module out of the remote user's control.
If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you enter yes in this situation, the CPU switch module goes to setup mode upon reload.
When you schedule a reload to occur at a later time, it must occur within approximately 24 days.
This command can be entered on either the active or standby CPU switch module console and only a reload of the CPU switch module on which the command was entered occurs.
When entered on the active CPU switch module, this command synchronizes the running-config to the standby CPU switch module just before the reload is executed, and causes a switchover to the standby CPU switch module only if the standby CPU switch module is in the hot-standby state.
By default the system is configured to reboot automatically, so the active CPU switch module reboots as the standby CPU switch module after the reload.
To display information about a scheduled reload, use the show reload command.
Examples
The following example shows how to reload the software on the CPU switch module.
Switch#reloadThe following example reloads the software on the CPU switch module in 10 minutes.
Switch#reload in 10Reload scheduled for 11:57:08 PDT Mon Feb 26 2001 (in 10 minutes)Proceed with reload? [confirm]Switch#The following example reloads the software on the CPU switch module at 1:00 p.m. today.
Switch#reload at 13:00Reload scheduled for 13:00:00 PPDT Mon Feb 26 2001 (in 1 hour and 2 minutes)Proceed with reload? [confirm]Switch#The following example reloads the software on the CPU switch module on 2/27 at 2:00 a.m.
Switch#reload at 02:00 feb 27Reload scheduled for 02:00:00 PDT Tues Feb 26 2001 (in 38 hours and 9 minutes)Proceed with reload? [confirm]Switch#The following example cancels a pending reload.
Switch#reload cancel%Reload cancelled.Related Commands
reprogram
To upgrade the FPGA or functional image on a selected card from a flash file, use the reprogram privileged EXEC command.
reprogram flash-file-name {slot [subcard] | rommon | sby-rommon}
Syntax Description
Defaults
None.
Command Modes
EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command the image to the controller you select. It also resets the selected controller, which causes active connections and configurations to be lost.
Caution
Examples
The following example shows how to reprogram the image on the ESCON aggregation card in slot 3.
Switch# reprogram bootflash:fi-ons15530-escon.A.2-36.exo 3Related Commands
show bootvar
To display boot and related environmental variables for both the active and standby CPU switch modules, use the show bootvar command.
show bootvar
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command shows boot and related information for the active and standby CPU switch modules.
Examples
The following example shows how to display boot information for the system. (See Table 9-1 for field descriptions.)
Switch# show bootvarBOOT variable = bootflash:<imagename>;CONFIG_FILE variable =BOOTLDR variable =Configuration register is 0x2Standby auto-sync startup config mode is onStandby auto-sync running config mode is onStandby is up.Standby BOOT variable = bootflash:<imagename>;Standby CONFIG_FILE variable =Standby BOOTLDR variable =Standby Configuration register is 0x2
Related Commands
show ciscoview package
To display Embedded CiscoView package information, use the show ciscoview package command.
show ciscoview package
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display Embedded CiscoView package file information or to troubleshoot.
Examples
The following example shows how to display Embedded CiscoView package information. (See Table 9-2 for field descriptions.)
Switch# show ciscoview packageFile source:slot1:CVFILE SIZE(in bytes)------------------------------------------------ONS15530-1.0.html 8861ONS15530-1.0.sgz 1183238ONS15530-1.0_ace.html 3704ONS15530-1.0_error.html 401ONS15530-1.0_jks.jar 17003ONS15530-1.0_nos.jar 17497applet.html 8861cisco.x509 529identitydb.obj 2523
Related Commands
show ciscoview version
To display Embedded CiscoView version information, use the show ciscoview version command.
show ciscoview version
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display Embedded CiscoView version information.
Examples
The following example shows how to display Embedded CiscoView version information. (See Table 9-3 for field descriptions.)
Switch# show ciscoview versionEngine Version: 5.3 ADP Device: ONS15530 ADP Version: 1.0 ADK: 39
Related Commands
show environment
To display the temperature sensor and fan status, use the show environment command.
show environment
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Examples
The following example shows how to display the fan tray failure shutdown feature configuration:
Switch# show environmentFan---Status: Total FailureLine card shutdown on fan failure:enabledSensor Temperature Thresholds(degree C) Minor Major Critcal Low-------------------- ----------- ------------------------------------Inlet Sensor 28 65 75 80 -15Outlet Sensor 28 75 85 90 -15Sensor AlarmsMinCritical-------------------- ------------------------Inlet Sensor 0 0 0Outlet Sensor 0 0 0Power Entry Module 0 type DC status: OKRelated Commands
show facility-alarm status
To display the facility alarm status, use the show facility-alarm status command.
show facility-alarm status [critical | info | major | minor]
Syntax Description
Defaults
Displays all facility alarm status information. This information includes external alarms and protocol monitoring alarms.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display the facility alarm and alarm threshold error status information.
Examples
The following example shows how to display the facility alarm status information. (See Table 9-4 for field descriptions.)
Switch# show facility-alarm statusSystem Totals Critical: 0 Major: 5 Minor: 1Source Severity Description [Index]------ -------- -------------------Chassis INFO Chassis power supply 1 missing [6]Giga2/0/4 INFO Keep-alive timeout event [12]WaveE4/0 MAJOR Loss of Lock event [0]WaveE4/0 MAJOR Loss of Sync event [2]PSC card 6 MINOR Unprotected. Peer not responding [10]TenGE7/0 MAJOR Loss of Lock event [0]TenGE7/0 MAJOR Loss of Sync event [2]Wave4/0/1 MAJOR Low alarm threshold exceeded forReceive Power (in dBm)Wave4/0/1 INFO Low warning threshold exceeded forReceive Power (in dBm)
Related Commands
Clears external facility alarm indications.
Enables signal monitoring for certain protocol encapsulations.
show hardware
To display hardware information, use the show hardware command.
show hardware [detail | linecard [slot]]
Syntax Description
detail
Shows detailed hardware information for the entire shelf.
linecard [slot]
Shows detailed hardware information for the motherboard or CPU switch module in a specific slot. The range is 0 to 10.
Defaults
Displays a summary of hardware information for the entire shelf.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display hardware information for debugging and tracking.
Examples
The following example shows how to display hardware information for the shelf. (See Table 9-5 for field descriptions.)
Switch# show hardware--------------------------------------------------------------------------------ONS 15530 Chassis, NEBS Version named Switch, Date: 08:44:06 UTC Wed Apr 27 2005----------------------------------------------------------------------------------------------------------------------------------------------------------------Back-Plane Information--------------------------------------------------------------------------------Orderable Product No. MAC-Address MAC-Size Serial No. Mfg. Date H/W Ver--------------------- ----------------- -------- ------------ ---------- -------15530-CHAS-N= 00-0e-83-44-b0-30 16 TBC07464403 2004/01/20 3.1--------------------------------------------------------------------------------Slot Orderable Product No. Part No. Rev Serial No. Mfg. Date H/W Ver.---- ------------------------- ---------- --- ------------ ---------- ----------1/* 15530-ITU2-2110= 800-24373- A0 CNH08060204 10/11/2004 8.12/* 15530-ITU2-1310= 800-24365- A0 CNH084300WR 11/01/2004 8.13/* 15530-ITU2-0520 800-24389- 04 CNH071900BZ 05/16/2003 8.05/* 15530-CPU=PROTO 73-7399-04 02 CAB0602M9XE 01/31/2002 4.66/* PROTO-HAMPTON-CPU 73-6572-04 06 CAB0602M9XV 01/29/2002 4.07/* 15530-ITU3-0120 68-1761-02 2 CAB06280T7Q 01/01/2000 3.010/* 15530-ITU2-0120= 800-19405- A0 CNH0711001J 03/28/2003 7.1Power Supply:Slot Part No. Rev Serial No. RMA No. Hw Vrs Power Consumption---- ---------------- ---- ----------- ----------- ------- -----------------0 34-1811-01 A0 SNI06090004 00-00-00-00 1.0 4900 cAPower Supply 0 :type : 600W ACstatus : OKPower Supply 1 Not present
The following example shows how to display detailed hardware information for a specific slot. (See Table 9-6 for field descriptions.)
Switch# show hardware linecard 1--------------------------------------------------------------------------------Slot Number : 1/*Controller Type : 0x1113On-Board Description : ONS 15530 Tunable Ch 21-24 10Gpbs ITU Line Card MU w/splitterOrderable Product Number: 15530-ITU2-2110=Board Part Number : 800-24373-02Board Revision : A0Serial Number : CNH08060204Manufacturing Date : 10/11/2004Hardware Version : 8.1RMA Number :RMA Failure Code :Functional Image Version: 2.38Function-ID : 0Version-ID (VID) : V01
show inventory
To display hardware inventory information, use the show inventory command.
show inventory [raw]
Syntax Description
Defaults
Displays summary hardware inventory information.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display hardware information for debugging and tracking.
Examples
The following example shows how to display hardware inventory information for the shelf. (See Table 9-7 for field descriptions.)
Switch# show inventoryNAME: "Cisco ONS 15530 Chassis, NEBS compliant", DESCR: "Cisco ONS 15530 Chassis, NEBS compliant"PID: 15530-CHAS-N= , VID: 3.1, SN: TBC07464403NAME: "ONS 15530 4-Channel Band F 10Gbps ITU Line Card MU with Splitter", DESCR:"ONS 15530 4-Channel Band F 10Gbps ITU Line Card MU with Splitter"PID: 15530-ITU2-2110= , VID: 8.1, SN: CNH08060204NAME: "ONS 15530 4-Channel Band D 10Gbps ITU Line Card MU with Splitter", DESCR:"ONS 15530 4-Channel Band D 10Gbps ITU Line Card MU with Splitter"PID: 15530-ITU2-1310= , VID: 8.1, SN: CNH084300WRNAME: "ONS 15530 Ch 05 10Gbps ITU Line Card MU without Splitter", DESCR: "ONS 15530 Ch 05 10Gbps ITU Line Card MU without Splitter"PID: 15530-ITU2-0520 , VID: 8.0, SN: CNH071900BZNAME: "Cisco ONS 15530 CPU and Switch Board", DESCR: "Cisco ONS 15530 CPU and Switch Board"PID: 15530-CPU=PROTO , VID: 4.6, SN: CAB0602M9XENAME: "Cisco ONS 15530 CPU and Switch Board", DESCR: "Cisco ONS 15530 CPU and Switch Board"PID: PROTO-HAMPTON-CPU , VID: 4.0, SN: CAB0602M9XVNAME: "ONS 15530 Ch 01/02 2.5Gbps ITU Line Card MU without Splitter", DESCR: "ONS 15530 Ch 01/02 2.5Gbps ITU Line Card MU without Splitter"PID: 15530-ITU3-0120 , VID: 3.0, SN: CAB06280T7QNAME: "ONS 15530 Ch 01 10Gbps ITU Line Card MU without Splitter", DESCR: "ONS 15530 Ch 01 10Gbps ITU Line Card MU without Splitter"PID: 15530-ITU2-0120= , VID: 7.1, SN: CNH0711001J
show optical wavelength mapping
To display the mapping of Cisco ONS 15530 channels to ITU grid frequencies and wavelengths, use the show optical wavelength mapping command.
show optical wavelength mapping
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display how the Cisco ONS 15530 channels map to the ITU G.692 grid wavelengths. Channel 0 is the OSC. Channels 1 through 32 are the client data channels. The last two digits of the frequency correspond to the ITU number (for example, the frequency for channel 1 is 192.1 so the ITU grid number is 21).
The frequencies ending in 0 and 5 are missing from the output because they are used as buffers between the 4-channel bands.
Examples
The following example shows how to display wavelength mapping information for the system. (See Table 9-8 for field descriptions.)
Switch# show optical wavelength mappingFrequency WavelengthChannel (THz) (nm)------- --------- ----------0 191.9 1562.231 192.1 1560.612 192.2 1559.793 192.3 1558.984 192.4 1558.175 192.6 1556.556 192.7 1555.757 192.8 1554.948 192.9 1554.139 193.1 1552.5210 193.2 1551.7211 193.3 1550.9212 193.4 1550.1213 193.6 1548.5114 193.7 1547.7215 193.8 1546.9216 193.9 1546.1217 194.1 1544.5318 194.2 1543.7319 194.3 1542.9420 194.4 1542.1421 194.6 1540.5622 194.7 1539.7723 194.8 1538.9824 194.9 1538.1925 195.1 1536.6126 195.2 1535.8227 195.3 1535.0428 195.4 1534.2529 195.6 1532.6830 195.7 1531.9031 195.8 1531.1232 195.9 1530.33
show temperature
To display shelf temperature information, use the show temperature command.
show temperature
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display the current shelf temperature and the alarm threshold temperatures.
Examples
The following example shows how to display internal redundancy software state information. (See Table 9-9 for field descriptions.)
Switch> show temperatureSensor Temperature Thresholds(degree C) Minor Major Critcal Low-------------------- ----------- ------------------------------------Sensor 27 65 75 80 -15Sensor AlarmsMinor Major Critical-------------------- ------------------------Sensor 0 0 0
Related Commands
show upgrade-info functional-image
To display ROMMON and functional image version diagnostics, use the show upgrade-info functional-image command.
show upgrade-info functional-image {all | latest-version [software-compatible]}
dat-file device:filename [detail]Syntax Description
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
12.2(18)SV
This command was introduced.
12.2(22)S
Usage Guidelines
Use this command to display the version diagnostics for ROMMON and functional images. The data file to use in conjunction with this command can be downloaded from the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/ons15530-fpga
The following example shows how to display detailed APS information for all APS groups. (See Table 9-10 for field descriptions.)
Switch# show upgrade-info functional-image all dat-file fi-ons15530-index.010.datValidating CRC...100%Generating Functional Image Upgrade Information for the currently running IOSusing DAT file fi-ons15530-index.010.dat, created on Thu Aug 21 00:23:10 PST 2003.Please ensure that you are using the latest DAT file fromCisco Connection Online (CCO) WebpageAbbr: Cur.FV = Functional Image Version of the Card.Lis.FV = List of Func. Image Versions found in the DAT-file for thecorresponding card.(U) = IOS Software upgrade is required, to upgrade tothe recommended functional image version.Slot Product No Cur.FV Lis.FV Listed Functional Image---- ------------------------- ------ ------ -------------------------------1/* 15530-TSP1-2912= 3.12 3.12 No Func. Image Upgrade Required1/0 Unknown 1.A2 1.A2 No Func. Image Upgrade Required2/* 15530-TSP1-3112 3.55 3.55 No Func. Image Upgrade Required2/0 Unknown 1.F2 1.F2 No Func. Image Upgrade Required3/* 15530-TSP1-2911 3.11 3.12 fi-ons15530-tpd.A.3-12.exo3/0 Unknown 1.9F 1.A0 fi-ons15540-tlcmdb.A.1-A0.exo4/* PROTO-HAMPTON-ESCON 2.33 2.36 fi-ons15530-escon.A.2-36.exo5/* PROTO-HAMPTON-CPU 1.43 1.43 No Func. Image Upgrade Required5/0 Active Rommon 1.1 1.1 No Func. Image Upgrade Required6/* PROTO-HAMPTON-CPU 1.43 1.43 No Func. Image Upgrade Required6/0 Standby Rommon 1.1 1.1 No Func. Image Upgrade Required8/* PROTO-HAMPTON-OSCMB 1.37 1.37 No Func. Image Upgrade Required8/0 15530-OSCM 0.58 0.58 No Func. Image Upgrade Required8/1 15530-OSCM 0.58 0.58 No Func. Image Upgrade Required
Related Commands
Updates the ROMMON or functional image on a card or module.
Displays information about the hardware on the shelf.
show version
To display the system hardware configuration, software version, and names and sources of configuration files and boot images, use the show version command.
show version
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display the system hardware configuration, software version, and names and sources of configuration files and boot images.
Note
Examples
The following example shows how to display version information for the system. Table 9-11 describes the output from the show version command.
Switch# show versionCisco IOS Software, ONS-15530 Software (ONS15530-I-M), Experimental Version 12.2(20050406:093210) [ksrinu-flo_ons_dev 100]Copyright (c) 1986-2005 by Cisco Systems, Inc.Compiled Wed 06-Apr-05 15:26 by ksrinuROM: System Bootstrap, Version 12.1(10r)EV, RELEASE SOFTWARE (fc1)switch uptime is 1 day, 7 hours, 35 minutesUptime for this control processor is 1 day, 6 hours, 37 minutesSystem returned to ROM by reload at 02:29:17 UTC Tue Apr 26 2005System image file is "bootflash:ons15530-i-mz-UT-APR6"Cisco ONS15530 (RM7000) processor with 49152K/16384K bytes of memory.R7000 CPU at 234Mhz, Implementation 39, Rev 2.1, 256KB L2, 2048KB L3 CacheLast reset from s/w nmi2 FastEthernet interfaces509K bytes of NVRAM.16384K bytes of Flash internal SIMM (Sector size 256K).Configuration register is 0x0
tl1 user
To add a new user for the TL1 command environment, use the tl1 user command. To remove a TL1 user, use the no form of the command.
tl1 user user-name {maint | prov | rtrv | super} [0 | 7] password
no tl1 user user-name
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use the tl1 user command to create user names for the TL1 command environment using the Cisco IOS CLI.
Examples
The following example shows how to create a TL1 user name and password.
Switch(config)# tl1 user admin super 0^x3T1traceroute
To trace the IP routes the packets actually take when traveling from the Cisco ONS 15530 NME (network management Ethernet) port to their destination, use the traceroute EXEC command.
EXEC Mode
traceroute protocol destination
Privileged EXEC Mode
traceroute [protocol] [destination]
Syntax Description
Defaults
The protocol argument is based on the format of the destination argument. For example, if the system finds a destination in IP format, the protocol defaults to ip.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The traceroute command works by taking advantage of the error messages generated by the system when a datagram exceeds its TTL (Time To Live) value. The traceroute command starts by sending probe datagrams with a TTL value of 1. This causes the first system to discard the probe datagram and send back an error message. The traceroute command sends several probes at each TTL level and displays the round-trip time for each.
The traceroute command sends out one probe at a time. Each outgoing packet may result in one or two error messages. A
time exceedederror message indicates that an intermediate system detected and discarded the probe. Adestination unreachableerror message indicates that the destination node received and discarded the probe because it could not deliver the packet. If the timer goes off before a response comes in, traceroute prints an asterisk(*).The traceroute command terminates when the destination responds, when the maximum TTL is exceeded, or when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, enter ^X.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and switches, the IP traceroute command may behave in unexpected ways.
Not all destinations respond correctly to a probe message by sending back an
ICMP port unreachablemessage. A long sequence of TTL levels with only asterisks, terminating only when the maximum TTL is reached, may indicate this problem.There is a known problem with the way some hosts handle an
ICMP TTL exceededmessage. Some hosts generate an ICMP message, but they reuse the TTL of the incoming packet. Because this is zero, the ICMP packets do not make it back. When you trace the path to such a host, you may see a set of TTL values with asterisks (*). Eventually, the TTL gets high enough that the ICMP message can get back. For example, if the host is 6 hops away, traceroute times out in responses 6 through 11.Examples
The following example displays sample IP traceroute output in EXEC mode when a destination host name is specified. (See Table 9-12 for field descriptions.)
Switch> traceroute ip ABA.NYC.milType escape sequence to abort.Tracing the route to ABA.NYC.mil (26.0.0.73)1 DEBRIS.CISCO.COM (131.108.1.6) 1000 msec 8 msec 4 msec2 BARRNET-GW.CISCO.COM (131.108.16.2) 8 msec 8 msec 8 msec3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec4 BB2.SU.BARRNET.NET (131.119.254.6) 8 msec 8 msec 8 msec5 SU.ARC.BARRNET.NET (131.119.3.8) 12 msec 12 msec 8 msec6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
Table 9-13 describes the characters that can appear in traceroute output.
The following example displays sample IP traceroute output in privileged EXEC mode when a destination IP address is specified. (See Table 9-14 for prompt descriptions and Table 9-12 for field descriptions.)
Switch# tracerouteProtocol [ip]:Target IP address: 10.0.0.1Source address:Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 10.0.0.11 10.0.0.2 msec 0 msec 4 msec2 10.0.1.9 0 msec 0 msec 0 msec3 10.0.0.1 0 msec 0 msec 4 msec
Posted: Mon Feb 27 03:18:27 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
