Initial Setup Troubleshooting Tips; All Controllers; Ax, Mxe, Cx, Or Cxi Controller - Mitel MiVoice Business Troubleshooting Manual

INITIAL SETUP TROUBLESHOOTING TIPS

 Refer to the Technician's Handbook for instructions on how to install and set up a 3300
ICP controller.
 For hardware related issues, also see See "Controllers" on page 39.

ALL CONTROLLERS

SYMPTOM
Unable to access the console
screen.
E2T fails to initialize.

AX, MXE, CX, OR CXI CONTROLLER

SYMPTOM
Controller not powering up.
Table 4: General Controller Setup Troubleshooting
POSSIBLE CAUSE
You are replacing an existing 3300
ICP controller with another
controller, and trying to use the
same system IP address for the
new controller from a PC on a
different subnet.
An MXE Server is using the default
IP scheme. This causes the E2T of
the other controller—which looks to
192.168.1.8 for TFTP on initial
bootup—to grab and re-hardcode
the IP from the MXE Server.
POSSIBLE CAUSE
Power cable is not securely
plugged into the controller and/or
power source.
Both power switches on a
redundant power supply controller
are not on.
CORRECTIVE ACTION
Initially, you can only connect to the
controller from the local subnet.
Before you can connect to the new
controller from other subnets, you
must manually clear the router ARP
cache or wait until the router ARP
cache is automatically updated.
Refer to the latest 3300 ICP
Release Notes for instructions.
Do not let the MXE Server use the
factory-default IP scheme if there
are other controllers with an E2T
installed on the same network
subnet. At a minimum you need to
change the default System IP of
192.168.1.8 to something else that
falls within your IP scope.
CORRECTIVE ACTION
Ensure power cable connections are
secure.
Ensure that both power switches are
turned on.
Initial Setup
25