E2T Comms Error - Calls Drop

[Volguy7]

Maintenance console shows E2T Comms error following a reboot. Additionally, any calls from IP to TDM connect to dead air and then are dropped. I'm sure the solution is to replace the E2T, but has anyone experienced this and is there something else I could try? The DHCP Static IP form shows the E2T with a static IP in the subnet og my switch.

System is 3300 LX, Rls. 7 (Yes, I know, outdated).


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[IrwinMFletcher]

Ah yes, correct. True, they are not technically a FRU, but they are physically replaceable (i.e not soldered to the mainboard). Any other LX can be scavenged for the board.

 

[Volguy7]

So what's the exact process and port to connect via PUTTY.



///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[LoopyLou]

You need to use a secure telnet program (SSH telnet)
once installed open it and type the following from the prompt

open ip address 2007

The ip address is the mxe RTC address and 2007 is the port number of the E2T card

Once you are in program a static IP address using the bootChange command

If you are familiar with the RTC then this is identical

Make sure that the host address is the RTC
and remember to set flags to static 0x0 (0x40 is default dhcp setting)

I think thats it any questions please ask

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.