Programming instructions

206
3300 ICP Technician’s Handbook
E2T
Table 23: LX E2T Troubleshooting
Symptoms 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.)
This change is made by changing
the flags (f) parameter in the
bootline of the E2T from 0x0
(hardcode) to 0x40 (DHCP).
When changing the flag from 0x0
to 0x40 on the E2T, make sure
that you blank out ALL IP
addresses in the bootline of E2T.
Table 24: MXe E2T Troubleshooting
Symptoms 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.)
1. Secure telnet to <RTC IP
Address> port 2007 (this is the
E2T serial port on the MXe)
2. Secure telnet to <RTC IP
Address> port 2002 (VxWorks
shell on the RTC)
3. At the VxWorks shell on the
RTC type: "ToggleCpu 1" to
reset the E2T card
4. Watch the port 2007 (E2T)
telnet session.
5. Hit 3 spaces to interrupt the
boot process.
6. Verify the bootline parameters
as described in Table 23, “LX
E2T Troubleshooting,” on
page 206.