Hard-code E2T without Debug (TAPI) cable

[Lundah]

In reference to thread1329-1252983, it looks like (at least on the LX chassis i'm working on) they moved the E2T console port to 2002, just like the RTC. I've got a controller that won't load the DHCP config (working with support on that issue), so I need to hard-code my E2T until we get that resolved, hoping this is the fix so I don't have to wait for a TAPI cable to get shipped to me. Can anyone confirm this?

 

[Lundah]

Found the answer to my own question: on rel. 5.0 and above, you can connect to the E2T via puTTY (RAW mode) or Secure Telnet at port 2002 of the E2T IP address using the ESM System-level login/password.

If you don't know the current E2T address, it's found in the System Hardware Profile form, and will be the 2nd entry.

From here you will be at a vxWorks console session, similar to connecting to the RTC, and can run shell commands to do what you need. Particularly helpful is the "bootChange" command, which lets you change the IP address configuration for the E2T. But be careful! if you mess it up on a 250/700/LX controller, you'll have to dig up or make a debug cable to fix the settings.

 

[Mitel100]

Just to also let you know that on the MXE you will need to use port 2007