Cisco Router 860, 880 Series User Manual

							 
C-9
Book Title
OL-xxxxx-xx
Appendix C      ROM Monitor
  Debug Commands
The following are ROM monitor debugging commands:
 stack or k—Produces a stack trace; for example:
rommon 6> stack
Stack trace:
PC = 0x801111b0Frame 00: FP = 0x80005ea8    PC = 0x801111b0
Frame 01: FP = 0x80005eb4    PC = 0x80113694
Frame 02: FP = 0x80005f74    PC = 0x8010eb44Frame 03: FP = 0x80005f9c    PC = 0x80008118
Frame 04: FP = 0x80005fac    PC = 0x80008064
Frame 05: FP = 0x80005fc4    PC = 0xfff03d70
 context—Displays processor context; for example:
rommon 7> context
CPU context of the most recent exception:
PC  = 0x801111b0  MSR = 0x00009032  CR  = 0x53000035  LR    = 0x80113694CTR = 0x801065e4  XER = 0xa0006d36  DAR = 0xffffffff  DSISR = 0xffffffff
DEC = 0xffffffff  TBU = 0xffffffff  TBL = 0xffffffff  IMMR  = 0xffffffff
R0  = 0x00000000  R1  = 0x80005ea8  R2  = 0xffffffff  R3    = 0x00000000R4  = 0x8fab0d76  R5  = 0x80657d00  R6  = 0x80570000  R7    = 0x80570000
R8  = 0x00000000  R9  = 0x80570000  R10 = 0x0000954c  R11   = 0x00000000
R12 = 0x00000080  R13 = 0xffffffff  R14 = 0xffffffff  R15   = 0xffffffffR16 = 0xffffffff  R17 = 0xffffffff  R18 = 0xffffffff  R19   = 0xffffffff
R20 = 0xffffffff  R21 = 0xffffffff  R22 = 0xffffffff  R23   = 0xffffffff
R24 = 0xffffffff  R25 = 0xffffffff  R26 = 0xffffffff  R27   = 0xffffffff
R28 = 0xffffffff  R29 = 0xffffffff  R30 = 0xffffffff  R31   = 0xffffffff
 frame—Displays an individual stack frame. 
 sysret—Displays return information from the last booted system image. This information includes 
the reason for terminating the image, a stack dump of up to eight frames, and, if an exception is 
involved, the address where the exception occurred; for example:
rommon 8> sysretSystem Return Info:
count: 19,  reason: user break
pc:0x801111b0,  error address: 0x801111b0Stack Trace:
FP: 0x80005ea8, PC: 0x801111b0
FP: 0x80005eb4, PC: 0x80113694FP: 0x80005f74, PC: 0x8010eb44
FP: 0x80005f9c, PC: 0x80008118
FP: 0x80005fac, PC: 0x80008064FP: 0x80005fc4, PC: 0xfff03d70
FP: 0x80005ffc, PC: 0x00000000
FP: 0x00000000, PC: 0x00000000
 meminfo—Displays size in bytes, starting address, available range of main memory, the starting 
point and size of packet memory, and size of NVRAM; for example:
rommon 9> meminfo
Main memory size: 40 MB.
Available main memory starts at 0x10000, size 40896KBIO (packet) memory size: 5 percent of main memory.
NVRAM size: 32KB 
						

							 
C-10
Book Title
OL-xxxxx-xx
Appendix C      ROM Monitor
  Exiting the ROM Monitor
Exiting the ROM Monitor
You must set the configuration register to a value from 0x2 to 0xF for the router to boot a Cisco IOS 
image from flash memory upon startup or reloading. 
The following example shows how to reset the configuration register and cause the router to boot a 
Cisco
 IOS image stored in flash memory:
rommon 1 > confreg 0x2101
You must reset or power cycle for new config to take effect:
rommon 2 > boot
The router will boot the Cisco IOS image in flash memory. The configuration register will change to 
0x2101 the next time the router is reset or power cycled. 
						

							 
D-1
Book Title
OL-xxxxx-xx
APPENDIXD
Common Port Assignments
Ta b l e D-1 lists currently assigned Transmission Control Protocol (TCP) port numbers. To the extent 
possible, the User Datagram Protocol (UDP) uses the same numbers.
Ta b l e D-1 Currently Assigned TCP and UDP Port Numbers 
PortKeywordDescription
0—Reserved
1–4—Unassigned
5RJERemote job entry
7ECHOEcho
9DISCARDDiscard
11USERSActive users
13DAYTIMEDaytime
15NETSTATWho is up or NETSTAT
17QUOTEQuote of the day
19CHARGENCharacter generator
20FTP-DATAFile Transfer Protocol (data)
21FTPFile Transfer Protocol
23TELNETTerminal connection
25SMTPSimple Mail Transport Protocol
37TIMETime
39RLPResource Location Protocol
42NAMESERVERHostname server
43NICNAMEWho is
49LOGINLogin Host Protocol 
53DOMAINDomain name server
67BOOTPSBootstrap Protocol Server
68BOOTPCBootstrap Protocol Client
69TFTPTrivial File Transfer Protocol
75—Any private dial-out service 
						

							 
D-2
Book Title
OL-xxxxx-xx
Appendix D      Common Port Assignments
  
77—Any private RJE service
79FINGERFinger
95SUPDUPSUPDUP Protocol
101HOST NAMENetwork interface card (NIC) 
hostname server
102ISO-TSAPISO-Transport Service Access Point 
(
TSAP)
103X400X400
104X400-SNDX400-SND
111SUNRPCSun Microsystems Remote 
Procedure Call 
113AUT HAuthentication service
117UUCP-PATHUNIX-to-UNIX Copy Protocol 
(UUCP) Path Service
119NNTPUsenet Network News Transfer 
Protocol
123NTPNetwork Time Protocol
126SNMPSimple Network Management 
Protocol
137NETBIOS-NSNetBIOS name service
138NETBIOS-DGMNetBIOS datagram service
139NETBIOS-SSNNetBIOS session service
161SNMPSimple Network Management 
Protocol
162SNMP-TRAPSimple Network Management 
Protocol traps
512rexecUNIX remote execution (control)
513TCP—rlogin 
UDP—rwho
TCP—UNIX remote login
UDP—UNIX broadcast name 
service
514TCP—rsh 
UDP—syslog
TCP—UNIX remote shell
UDP—system log
515PrinterUNIX line printer remote spooling
520RIPRouting Information Protocol 
525TimedTime server 
Table D-1 Currently Assigned TCP and UDP Port Numbers (continued)
Port Keyword Description 
						

							Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2008 Cisco Systems, Inc. All rights reserved.
System Message Logging
This chapter describes how to configure system message logging on your wireless device.
This chapter consists of these sections:
 Understanding System Message Logging, page 1
 Configuring System Message Logging, page 2
 Displaying the Logging Configuration, page 11
NoteFor complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS 
Configuration Fundamentals Command Reference for Release 12.4.
Understanding System Message Logging
By default, access points send the output from system messages and debug privileged EXEC commands 
to a logging process. The logging process controls the distribution of logging messages to various 
destinations, such as the logging buffer, terminal lines, or a UNIX syslog server, depending on your 
configuration. The process also sends messages to the console. 
NoteThe syslog format is compatible with 4.3 BSD UNIX.
When the logging process is disabled, messages are sent only to the console. The messages are sent as 
they are generated, so message and debug output are interspersed with prompts or output from other 
commands. Messages are displayed on the console after the process that generated them has finished.
You can set the severity level of the messages to control the type of messages displayed on the console 
and each of the destinations. You can timestamp log messages or set the syslog source address to enhance 
real-time debugging and management.
You can access logged system messages by using the access point command-line interface (CLI) or by 
saving them to a properly configured syslog server. The access point software saves syslog messages in 
an internal buffer. You can remotely monitor system messages by accessing the access point through 
Telnet or by viewing the logs on a syslog server. 
						

							      System Message Logging
Configuring System Message Logging
2
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
Configuring System Message Logging
This section describes how to configure system message logging. It contains this configuration 
information:
 System Log Message Format, page 2
 Default System Message Logging Configuration, page 3
 Disabling and Enabling Message Logging, page 4
 Setting the Message Display Destination Device, page 4
 Enabling and Disabling Time Stamps on Log Messages, page 5
 Enabling and Disabling Sequence Numbers in Log Messages, page 6
 Defining the Message Severity Level, page 6
 Limiting Syslog Messages Sent to the History Table and to SNMP, page 8
 Setting a Logging Rate Limit, page 9
 Configuring UNIX Syslog Servers, page 9
System Log Message Format
System log messages can contain up to 80 characters and a percent sign (%), which follows the optional 
sequence number or timestamp information, if configured. Messages are displayed in this format:
seq no:timestamp: %facility-severity-MNEMONIC:description
The part of the message preceding the percent sign depends on the setting of the service 
sequence-numbers, service timestamps log datetime, service timestamps log datetime [localtime] 
[msec] [show-timezone], or service timestamps log uptime global configuration command.
Ta b l e 1 describes the elements of syslog messages.
Ta b l e 1 System Log Message Elements 
ElementDescription
seq no:Stamps log messages with a sequence number only if the service sequence-numbers global 
configuration command is configured. 
For more information, see the “Enabling and Disabling Sequence Numbers in Log Messages” 
section on page 6.
timestamp formats:
mm/dd hh:mm:ss
or
hh:mm:ss (short uptime)
or
d h (long uptime)
Date and time of the message or event. This information appears only if the service timestamps 
log [datetime | log] global configuration command is configured.
For more information, see the “Enabling and Disabling Time Stamps on Log Messages” section 
on page 5.
facilityThe facility to which the message refers (for example, SNMP, SYS, and so forth). A facility can 
be a hardware device, a protocol, or a module of the system software. It denotes the source or the 
cause of the system message. 
						

							      System Message Logging
Configuring System Message Logging
3
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
The following example shows a partial access point system message:
00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed 
state to down 2
*Mar  1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)18:47:02: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
*Mar  1 18:48:50.483 UTC: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36) 
Default System Message Logging Configuration
Ta b l e 2 shows the default system message logging configuration.
severitySingle-digit code from 0 to 7 that is the severity of the message. For a description of the severity 
levels, see 
Ta b l e 3 on page 7.
MNEMONICText string that uniquely describes the message.
descriptionText string containing detailed information about the event being reported.
Table 1 System Log Message Elements (continued)
Element Description
Ta b l e 2 Default System Message Logging Configuration 
FeatureDefault Setting
System message logging to the consoleEnabled
Console severityDebugging (and numerically lower levels; 
see 
Ta b l e 3 on page 7)
Logging buffer size4096 bytes
Logging history size1 message
Time stampsDisabled
Synchronous loggingDisabled
Logging serverDisabled
Syslog server IP addressNone configured
Server facilityLocal7 (see Ta b l e 4 on page 10)
Server severityInformational (and numerically lower 
levels; see 
Ta b l e 3 on page 7) 
						

							      System Message Logging
Configuring System Message Logging
4
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
Disabling and Enabling Message Logging
Message logging is enabled by default. It must be enabled to send messages to any destination other than 
the console. When enabled, log messages are sent to a logging process, which logs messages to 
designated locations asynchronously to the processes that generated the messages.
To disable message logging, follow these steps, beginning in privileged EXEC mode:
Disabling the logging process can slow down the access point because a process must wait until the 
messages are written to the console before continuing. When the logging process is disabled, messages 
are displayed on the console as soon as they are produced, often appearing in the middle of command 
output.
The logging synchronous global configuration command also affects the display of messages to the 
console. When this command is enabled, messages appear only after you press Return. For more 
information, see the 
“Enabling and Disabling Time Stamps on Log Messages” section on page 5.
To reenable message logging after it has been disabled, use the logging on global configuration 
command.
Setting the Message Display Destination Device
If message logging is enabled, you can send messages to specific locations in addition to the console. To 
specify the locations that receive messages, use one or more of the following commands, beginning in 
privileged EXEC mode:
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2no logging onDisables message logging.
Step 3endReturns to privileged EXEC mode.
Step 4show running-config 
or 
show logging
Verifies your entries.
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2logging buffered [size] [level]Logs messages to an internal buffer. The default buffer size is 4096. The 
range is 4096 to 2147483647 bytes. Levels include emergencies 0, alerts 
1, critical 2, errors 3, warnings 4, notifications 5, informational 6, and 
debugging 7.
NoteDo not make the buffer size too large because the access point 
could run out of memory for other tasks. Use the show memory 
command in privileged EXEC mode to view the free processor 
memory on the access point; however, this processor memory 
value is the maximum available, and you should not set the buffer 
size to this amount. 
						

							      System Message Logging
Configuring System Message Logging
5
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
The logging buffered global configuration command copies logging messages to an internal buffer. The 
buffer is circular, so newer messages overwrite older messages after the buffer is full. To display the 
messages that are logged in the buffer, use the show logging command, in privileged EXEC mode. The 
first message displayed is the oldest message in the buffer. To clear the contents of the buffer, use the 
clear logging command, in privileged EXEC mode.
To disable logging to the console, use the no logging console command in global configuration mode. 
To disable logging to a file, use the no logging file [severity-level-number | type] command in global 
configuration mode.
Enabling and Disabling Time Stamps on Log Messages
By default, log messages are not time stamped. 
To enable timestamping of log messages, follow these steps, beginning in privileged EXEC mode:
To disable timestamps for both debug and log messages, use the no service timestamps command in 
mode global configuration.
Step 3logging hostLogs messages to a UNIX syslog server host.
For host, specify the name or IP address of the host to be used as the 
syslog server.
To build a list of syslog servers that receive logging messages, enter this 
command more than once.
For complete syslog server configuration steps, see the “Configuring 
UNIX Syslog Servers” section on page 9.
Step 4endReturns to privileged EXEC mode.
Step 5terminal monitorLogs messages to a non-console terminal during the current session.
Terminal parameter-setting commands are set locally and do not remain 
in effect after the session has ended. You must perform this step for each 
session to see the debugging messages.
Command Purpose
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2service timestamps log uptime
or
service timestamps log datetime [msec] [localtime] 
[show-timezone]
Enables log timestamps.
The first command enables timestamps on log messages, 
showing the time since the system was rebooted.
The second command enables timestamps on log messages. 
Depending on the options selected, the timestamp can 
include the date, time in milliseconds relative to the local 
time zone, and the time zone name.
Step 3endReturns to privileged EXEC mode. 
						

							      System Message Logging
Configuring System Message Logging
6
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
The following example shows part of a logging display with the service timestamps log datetime 
command enabled:
*Mar  1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
The follwoing example shows part of a logging display with the service timestamps log uptime 
command enabled:
00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Enabling and Disabling Sequence Numbers in Log Messages
Because there is a chance that more than one log message can have the same timestamp, you can display 
messages with sequence numbers so that you can unambiguously refer to a single message. By default, 
sequence numbers in log messages are not displayed. 
To enable sequence numbers in log messages, follow these steps, beginning in privileged EXEC mode:
To disable sequence numbers, use the no service sequence-numbers global configuration command.
The follwoing example shows part of a logging display with sequence numbers enabled:
000019: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
Defining the Message Severity Level
You can limit messages that are displayed to the selected device by specifying the severity level of the 
message. 
Ta b l e 3 describes the severity level.
To define the message severity level, follow these steps, beginning in privileged EXEC mode:
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2service sequence-numbersEnables sequence numbers.
Step 3endReturns to privileged EXEC mode.
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2logging console levelLimits messages logged to the console.
By default, the console receives debugging messages and numerically 
lower levels (see 
Ta b l e 3 on page 7).
Step 3logging monitor levelLimits messages logged to the terminal lines.
By default, the terminal receives debugging messages and numerically 
lower levels (see 
Ta b l e 3 on page 7).