Programming E2T Via Debug Cable Or Secure Telnet - Mitel 3300 Technician's Handbook

3300 ICP Technician's Handbook

Programming E2T via Debug Cable or Secure Telnet

Use the settings in Table 54 below to program the E2T using a debug
cable. The debug (Tapi) cable is an RS-232 serial cable with a PS2
connector at one end and a DB9 connector at the other.
For the MXe and MXe Server, connect to the controller through secure
telnet to port 2007.
Tip: Use this section only if you already have a debug cable, and only if you
are directed to do so by Mitel Technical Support.
Table 54: Debug Cable E2T VxWorks Settings
Prompt
boot device
processor number
host name
file name
inet on ethernet (e)
inet on backplane (b)
host inet (h)
gateway inet (g)
user (u)
ftp password (ftp)
flags (f)
target name (n)
282
Value
motfcc or qefcc
on the MXe III
0
bootHost
/sysro/E2T8260
ftp
@
0x0
Note
Boot device is Network.
Note: The MXe III accepts motfcc
but automatically converts it to
qefcc on the next system reboot.
Not used.
Boot location and file name.
IP address and subnet mask (hex)
for controller E2T (for example,
134.199.63.11:ffffff00). Obtain it
from your IT administrator.
IP address of controller RTC.
Note: System IP for MXe Server
IP address of the end user's default
gateway for the 3300 ICP (must be
outside the DHCP range).
Fixed IP address (0x40 used on
E2T for DHCP).
Page 1 of 2