IMPORTANT: DHCP options 128-135
used to configure Mitel IP endpoints have been reclassified as public
options by the Internet Engineering Task Force (see RFC 2133 and RFC 3925).
To comply with the change, Mitel recommends using either option 43 or
125, depending on the server's ability to support them and on administrator
preference. The embedded server supports both options; 125 is the factory-programmed
default. The old options can still be used to provide backward compatibility
with IP sets that have yet to be upgraded with firmware that supports
the new options. After the upgrade, the old options may be removed to
prevent future conflicts with standard use or other vendors' use of these
options. The following procedure applies to new installations only. For
upgrade procedures, see the Technician's Handbook.
If you intend to rely on LLDP Link Layer Discovery Protocol. An An IEEE standard (801.1AB) that provides
a vendor-neutral method for Ethernet network devices such as switches,
routers and wireless LAN access points to advertise information about
themselves to other nodes on the network and store the information they
discover. Advertised nformation includes: device type description, boot
and main revision, phone IP address, phone MAC address , duplex setting,
power consumption, phone DN, attached devices, etc. The information is
stored in a SNMP MIB that provides network management systems with accurate
network mapping, inventory data and network troubleshooting information.
VLAN Discovery in the network, you must first upgrade the firmware in
LLDP-compliant IP Phones to version 2.0.0.18 or later. For upgrade procedures,
see the 3300 ICP Technician's Handbook.
Note: Programming the DHCP Server is not applicable to MCD for Mitel Communications Suite (MCS).
When you program the internal DHCP server of the 3300 ICP, the following conditions apply:
You must populate the DHCP Subnet form with the subnets that you want the the DHCP server to respond to. By default, this form is assigned with the subnet 192.168.1.0. If different subnets will be used in your installation, then delete this default subnet.
In the DHCP Options form, configure the options that you want applied to the subnets. Apply each option to the defined subnets at one of the following scopes: Global, Subnet, or Range. The DHCP server responds with option information to DHCP requests based on the priority of the scope setting. The highest priority is Range, followed by Subnet, and lastly Global. Note that the scopes only apply to subnets that you have defined in the DHCP Subnet form. A request from a subnet, or scope, that is not defined in the DHCP Subnet form will not elicit a DHCP response.
If you deleted the default subnet of 192.168.1.0 from the DHCP Subnet form, the associated DHCP option information for this subnet is ignored. However, you should delete any DHCP options assigned to this subnet from the DCHP Options form as a precautionary measure.
The MXe Server does not include an internal DHCP server, so it must be programmed via an external DHCP server or the DHCP server on another ICP in the network.
To program the DHCP server of the 3300 ICP:
Issue the DBMS STAT maintenance command and ensure that the DBMS_Initialized Flag is ON (look for the line DBMS info: DBMS_Initialized is ON). Before the DHCP server will allocate leases, the DBMS_Initialized Flag must be ON. See Using Maintenance Commands for instructions on how to enter a maintenance command.
If the DBMS_Initialized Flag is OFF, enter the DBMS SAVE command to turn it on.
DHCP Server form
Disable the DHCP server.
DHCP
Subnet form
Enter Name, IP Address, and Bit Mask information.
DHCP
Static IP Address form (Optional)
Assign IP addresses to specific devices by using the MAC address of
the device.
We recommend you assign a static IP address to the E2T (skip this step
for the CX, CXi, CX II, CXi II, MX, MXe,
MXe Server and 100-user controllers).
DHCP
IP Address Range form. Complete the IP Address range.
The following IP addresses are reserved for the Analog Main Board (AMB)
and the CIMs on the ASUs and ASU IIs:
169.254.10.0 to 169.254.10.15
169.254.11.0 to 169.254.11.15
169.254.12.0 to 169.254.12.15
169.254.13.0 to 169.254.13.15
169.254.14.0 to 169.254.14.15
169.254.15.0 to 169.254.15.15
169.254.16.0 to 169.254.16.15
169.254.17.0 to 169.254.17.15
169.254.18.0 to 169.254.18.15
169.254.19.0 to 169.254.19.15
169.254.20.0 to 169.254.20.15
169.254.21.0 to 169.254.21.15
169.254.22.0 to 169.254.22.15
169.254.23.0 to 169.254.23.15
169.254.24.0 to 169.254.24.15
169.254.25.0 to 169.254.25.15
169.254.26.0 to 169.254.26.15
169.254.27.0 to 169.254.27.15
169.254.28.0 to 169.254.28.15
169.254.29.0 to 169.254.29.15
169.254.30.0 to 169.254.30.15
The addresses are assigned on a first-come, first served basis. Under
normal conditions, AMB gets the first address assigned and after that,
each CIM is assigned an address as the CIM is used.
DHCP
Options form
Create options as required and apply to the required
scope: Global, Subnet, or Range.
Always create the following options:
3 Router, IP address
43 Vendor Specific Information, string
value
or
125 Vendor-Identifying Vendor-Specific Information, string value
66 TFTP Server, IP address format
67 Boot file, string value (always /sysro/E2T8260)
If there are 5230 IP Phones on the system, create the following DHCP options:
6 DNS Server, IP address format
44 NetBIOS Name Server, IP address format
If there are IP-DECT Wireless telephones on the system, create the following DHCP options:
140 OMM, IP address of the primary Open Mobility Manager (IP-DECT resiliency)
150 OMM, IP address of the secondary Open Mobility Manager (IP-DECT resiliency)
224 DHCP Server, string value "Open Mobility" (IP-DECT resiliency)
254 Upgrades booter version of IP-DECT RFPs, format is "ASCII string", value is "ASCII UPDATE"
If there are IP Phones not yet upgraded to the Release 7.0 DHCP options (60/43 or 124/125), create the following DHCP options:
128 TFTP, IP address format (typically the controller)
129 RTC, IP address format (typically the controller)
130 MITEL IP PHONE, string value
131 MITEL IP PHONE, IP address
132 VLAN ID (required if a voice VLAN is in use)
133 Priority, integer value of 1-6 (required if a voice VLAN is in use; for external server use Hex LONG; for internal server use decimal)
134 Diffserv Code Point, integer value )
Note: After the phones are upgraded, options 128-135 may be removed to avoid future conflicts with standard use or other vendors' use of these options.
DHCP
Options form (in a cluster environment)
Any IP Console in a cluster must be programmed with a static IP Address.
If a different router is need for the IP Console, repeat step 6 for Option 3 and set the Value to the IP address of the router.
DHCP
Lease Viewer form
Ensure that there is no DHCP IP Address Lease for the IP Console MAC
Addresses. If there is, delete it and then power off and power on the
device.
DHCP
Server form
Enable the DHCP server.
To use an external DHCP server:
DHCP
Server form
Disable the internal DHCP server.
Ensure that your DHCP server is programmed with options 60/43 or 124/125. See the Technician's Handbook for further instructions and the DHCP Options form for the required option format and values.
Note: IP sets require a firmware upgrade to support the new DHCP options introduced in Release 7.0; otherwise, the sets will fail to boot. Such failures can occur, for example, in a resilient cluster of mixed software releases or when sets with old firmware are added to a controller after it was upgraded to Release 7.0. For the sets to boot, DHCP options 128-135 must be present in the DHCP server. After the sets have booted, options 128-135 may be removed to avoid future conflicts with standard use or other vendors' use of these options.
To delete the lease of an IP address:
DHCP
Lease Viewer form (optional)
Select the IP address that should have the lease removed.
Click Delete.