Mitel MiVoice Business Troubleshooting Manual page 214

Troubleshooting Guide
9. The set goes through the Discovery/Offer/ Request/Ack sequence
again.The packets sent are tagged to include VLAN and Priority
values supplied by the first DHCP server.
10. The TFTP server downloads the boot image and displays the set
IP address. If there is no boot image, the set jumps to Step 12.
Refer to Table 66 for a description of possible error messages.
11. The boot file is copied to flash if it is a different version than the
one in flash.
12. If the boot load is the same as in flash, it is not copied.
13. The set downloads a main image. A failure causes a phone reset,
and the process starts again at step 1.
14. The set resets and the main load executes.
The display changes to waiting for link.
The set requests registration with the ICP (the first time request
requires a PIN registration).
The set waits for the ICP to take control.
15. After the main boot load is downloaded, (and only when a phone
in a resilient network has homed to the wrong ICP) the phone
seeks out the IP address of its primary 3300 ICP from the DHCP
ICP Redirect list of 3300 ICPs in the network.
It is possible for the phone to be redirected and you may see this
display again.
16. Once communication is established, the idle display appears on
the set.
206
Table 63: IP Phone Boot Sequence(continued)
BOOT SEQUENCE PHONE DISPLAY
xx.xx.xx.xx
Downloading
Upgrading Flash
DO NOT POWER DOWN
xx.xx.xx.xx
Upgrade not required
xx.xx.xx.xx
Download failed
---------------------
xx.xx.xx.xx
Downloading
---------------------
xx.xx.xx.xx
Starting main
MAIN 08.04.01.01
BOOT 04.02.01.06
---------------------
Set xx.xx.xx.xx
ICP xx.xx.xx.xx
---------------------
Waiting for ACK...
ICP xx.xx.xx.xx
---------------------
Waiting for COMMS...
ICP xx.xx.xx.xx
Set xx.xx.xx.xx
ICP xx.xx.xx.xx
---------------------
Set xx.xx.xx.xx
ICP xx.xx.xx.xx
<idle in service UI>
<idle softkeys>
Page 2 of 2