Troubleshooting guide

Hardware
39
Controllers
MXe Controller
Table 9: MXe Controller Troubleshooting
Symptom Probable Cause Corrective Action
E2T fails to initialize. Changing from a hard coded E2T
IP address to requesting one from
the DHCP server. (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.)
For information and guidance for
correcting this problem, refer to
"Programming E2T via 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 or the E2T VxWorks
shell, remove the vlan using the cv
command.
E2T card defective. Check the Hardware Compute Cards form
in the System Administration Tool. If the IP
Address for Slot 2 displays “Not
Responding”, replace the E2T card.
Unable to communicate with
MXe
You are attempting to use port 2 to
access the MXe controller but the
Layer 2 IP address is not
programmed.
Use port 1 to access the MXe controller.
Then launch the System Administration
Tool and program the Layer 2 IP address.
Soft fault reported
intermittently by RAID
controller.
Soft fault comes indirectly from
the hard drive itself.
Refer to Mitel Knowledge Base article
06-2806-00012.
Audio problems from IP to IP
or IP to TDM.
E2T is unable to communicate
with devices off its subnet.
If the problem is IP -> IP or IP -> TDM:
Check the default gateway on all
components involved in the call that is
having audio problems.
For example, you might see this issue
when the following pairs are on different
subnets:
• E2T to E2t
• E2t to IP phone
• IP phone to IP phone