Cisco 8832 Onderhoudshandleiding - Pagina 8

Blader online of download pdf Onderhoudshandleiding voor {categorie_naam} Cisco 8832. Cisco 8832 9 pagina's. Masergy ip conference phone
Ook voor Cisco 8832: Masterhandleiding voor firmwaremigratie (31 pagina's), Gebruikershandleiding (20 pagina's), Snelstarthandleiding (2 pagina's), Handmatig (30 pagina's), Installatiehandleiding (39 pagina's), Snelstarthandleiding (16 pagina's), Snel aan de slag (2 pagina's), Instellingen (14 pagina's), Snelstarthandleiding (2 pagina's), Herconfiguratiehandleiding (2 pagina's), Snel aan de slag (2 pagina's), Handmatig (30 pagina's)

Reboot History on the Phone Web User Interface

You can view the reboot history as follows:

• From the phone web user interface

• From the IP phone screen

• From the phone Status Dump file (http://phoneIP/status.xml or http://phoneIP/admin/status.xml)

Reboot History on the Phone Web User Interface

On the Info > System Status page, the Reboot History section 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 that indicates when the reboot took place.

For example:

Reboot Reason 1: [08/13/14 06:12:38] User Triggered

Reboot Reason 2: [08/10/14 10:30:10] Provisioning

Reboot Reason 3: [08/10/14 10:28:20] Upgrade

The reboot history displays in reverse chronological order; the reason for the most recent reboot displays in

Reboot Reason 1.

Reboot History is located under Apps > Admin Settings > Status menu. In the Reboot History window, the

reboot entries displays in reverse chronological order, similar to the sequence that displays on the phone web

user interface.

The reboot history is stored in the Status Dump file (http://<phone_IP_address>/admin/status.xml).

In this file, tags Reboot_Reason_1 to Reboot_Reason_3 store the reboot history, as shown in this example:

<Reboot_History>

<Reboot_Reason_1>[08/10/14 14:03:43]Provisioning</Reboot_Reason_1>

<Reboot_Reason_2>[08/10/14 13:58:15]Provisioning</Reboot_Reason_2>

<Reboot_Reason_3>[08/10/14 12:08:58]Provisioning</Reboot_Reason_3>

<Reboot_Reason_4>

<Reboot_Reason_5>

<Reboot_History/>

Maintenance