Troubleshooting guide

Troubleshooting Guide
26
Unable to establish
communication with controller
via maintenance PC
Controller has not finished starting
up.
The controller can take up to 15 minutes to
start up.
PC communication application
(for example VT 100 emulator
program) serial port settings
incorrect.
See “Connect to PC” in the “Initial Setup”
chapter of the MCD Technician’s
Handbook for correct settings.
Crossover Ethernet cable used to
PC to controller.
Use a straight-through Ethernet cable.
PC Network Interface Card IP
address not programmed.
Program the PC’s NIC with the following
settings:
• IP Address: 192.168.1.n (where n is a
value between 30 and 254)
• Subnet Mask: 255.255.255.0
Maintenance PC on different
subnet.
Configure maintenance PC on same the
same subnet as controller.
IP address and subnet mask for
RTC entered incorrectly.
Enter IP addresses without leading zeros.
For example, 192.168.1.2; not
192.168.001.002
E2T does not come up even
though inet on ethernet is
programmed and the flag is set
to 0x40.
ET2 was hard coded with an IP
address and then later changed to
request an IP address from the
DHCP server. This change is
made by changing the flags (f)
parameter in the bootline of the
E2T from 0x0 (hardcode) to 0x40
(DHCP). If any IP addresses
remain on the E2T (at “inet on
ethernet”, “host inet” or “gateway
inet”), the E2T will use them and
will obtain the rest of its
parameters from the DHCP
server.
When changing the flag from 0x0 to 0x40
on E2T, ensure that you blank out ALL IP
addresses in the bootline of E2T.
Refer to “Programming the E2T via a
Debug Cable or Secure Telnet” in the MCD
Technician’s Handbook.
RTC is set up with a different
virtual LAN (vlan).
From the RTC shell, remove the vlan using
the cv command:
When adding subnets to the
internal DHCP server you
receive the error message “No
more room for records”.
Number of available subnets
exceeded.
Refer to Mitel Knowledge Base article
06-5157-00008 for details.
After a new install, the internal
DHCP server is not supplying
addresses to IP devices.
Internal DHCP server is not
activated.
The internal DHCP server is not activated
by default. If your system relies on the
internal DHCP server, you must turn the
flag on by issuing the DBMS SAVE
command.
Table 5: AX, MXe, CX, or CXi Controller Setup Troubleshooting
Symptom Possible Cause Corrective Action