
Getting Started
Viewing Phone Information
Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide
29
1
You can view the reboot history from the phone web user interface, the IP phone
screen, and the phone SPA Status Dump file (http://
phoneIP
/status.xml or http://
phoneIP
/admin/status.xml).
Viewing the Reboot History on the Phone Web User Interface
The
Info
>
System Information
>
Reboot History
page displays the device
reboot history, the five most recent reboot dates and times and a reason for the
reboot. Each field displays the reason for the reboot and a time stamp indicating
when the reboot took place. For example:
Reboot Reason 1: Provisioning(06/22/2011 13:29:33)
Reboot Reason 2: Upgrade(06/22/2011 13:01:43)
Reboot Reason 3: Provisioning(06/22/2011 10:40:12)
The reboot history is displayed in reverse chronological order; the reason for the
most recent reboot is displayed in
Reboot Reason 1
.
Viewing the Reboot History on the IP Phone Screen
Reboot History
is located under the
Setup menu
. On the
Reboot History
Page,
the reboot entries are displayed in reverse chronological order, similar to the
sequence displayed on the phone web user interface.
Viewing the Reboot History in the SPA Status Dump File
The reboot history is stored in the SPA Status Dump file
(http://
<phone_IP_address>
/admin/status.xml). In this file, tags
Reboot_Reason_1
to
Reboot_Reason_5
store the reboot history, as shown in this example:
<Reboot_History><Reboot_String/>
<
Reboot_Reason_1
>Provisioning(06/13/2011 14:03:43)</Reboot_Reason_1>
<
Reboot_Reason_2
>Provisioning(06/13/2011 13:58:15)</Reboot_Reason_2>
<
Reboot_Reason_3
>Provisioning(06/13/2011 12:08:58)</Reboot_Reason_3>
<
Reboot_Reason_4
>Provisioning(05/26/2011 15:26:49)</Reboot_Reason_4>
<
Reboot_Reason_5
>System 4(05/24/2011 10:20:06)</Reboot_Reason_5>
User Triggered
The user manually triggered a warm reboot.
Software Req
The warm reboot was triggered by a remote server.
System
n
The reboot was triggered by system events (for
example, running out of resources).
IP Changed
The reboot was triggered after the phone IP address
was changed.
Reason
Description