Mitel MiVoice Business Troubleshooting Manual page 77

ERROR MESSAGE
ON DISPLAY
Invalid VLAN ID
Duplicated IP address
DHCP discovery OR
DHCP OFFER X REJ
Table 17: IP Phone Registration Troubleshooting
POSSIBLE CAUSE
DHCP Option 43 or 125 on 3300
Release 7.0 or later systems or
132 and/or 133 for earlier
releases not set correctly.
Existing data device owns the IP
address.
Corrupted DHCP server.
DHCP option 43 or 125 on 3300
Release 7.0 or later systems or
option 130 (MITEL IP PHONE)
for earlier Releases is not
programmed.
DHCP server does not have
enough IP addresses.
DHCP server cannot assign IP
addresses for the corresponding
subnet, even though there are
enough IP addresses.
L2 switch port is shut down or not
configured properly.
Your installation is using the
controller's internal DHCP
server, but DBMS Save is not on.
CORRECTIVE ACTION
1. Identify the location of DHCP server and
which DHCP server is assigned the IP
address for the corresponding subnet (see
"Network Configuration Examples" in the
"Typical Network Configurations" chapter of
the Technician's Handbook for examples).
2. For an external Microsoft DHCP server (NT
server, etc.), make sure that the option type
is set to LONG.
®
3. For a Cisco Router DHCP server, make
sure that the option type is set to hex, and
padded with 0s (for example, 0x00000002
for VLAN 2).
4. For the controller internal DHCP server, set
the option type to numeric.
1. Check the IP address on the phone display.
2. Disconnect the IP Phone.
3. From a PC on the same subnet, ping the
suspected IP Phone. If there is a response,
identify the data device, and resolve the
conflict.
1. On the suspected DHCP server, disable
then recreate the scope.
2. If this is a Microsoft DHCP server, reboot the
server.
Identify the location of DHCP server and set to
Option 130 as String type with value of "MITEL
IP PHONE".
Create a larger scope with more IP addresses
on the DHCP server.
1. For a Microsoft DHCP server, reboot the
server.
2. For the controller internal DHCP server,
disable DHCP and rebuild the scope.
1. Check the L2 switch, and ensure that the
port is not shut down.
2. Ensure that this port can access the DHCP
server subnet (that is, access the port for the
same VLAN, etc.).
Enter the DBMS Save command through the
Maintenance Commands form.
Hardware
Page 1 of 6
69