User`s guide

188 CPU32 Emulation
Chapter 11: Troubleshooting the Emulator
Problems with the Emulation Probe
then try to set them to correct values. If you are unable to set them to
correct values, their is a failure in the FLASH ROM which requires
service from HP.
Test 3: 10BaseT Feedback Test failed here
R>pv -t3 -v2 1
Testing: HPE3499B Series Emulation System
Test # 3: LAN 10BaseT Feedback Test failed!
FAILED Number of tests: 1 Number of failures: 1
In addition to the internal checks performed in Test 2, this test also
checks for shorts on the cable connected to the network. If this test
fails, disconnect the cable and run the test again. If it then passes, the
cable is faulty. If it still fails, it requires service from HP.
If the emulator passes this “pv” test, additional testing can be
performed through exercising the connection to the network. To run
this test, set configuration switch 1 and switch 5 to OPEN, all other
configuration switches CLOSED (this enables LAN using 10BaseT).
Cycle power and wait for 15 to 30 seconds. Then “ping” the emulator
from your host computer or PC. See the LAN documentation for your
host computer for the location and action of the “ping” utility. If the
emulator fails to respond to the “ping” request, verify that the LAN
parameters (IP address and gateway address) are set correctly and
that your host computer recognizes the IP address of the emulator. If
all else is good, then failure to respond to ping indicates a faulty
emulator.
Test 4: Break In and Trigger Out BNC Feedback Test
R>pv -t4 -v2 1
Testing: HPE3499B Series Emulation System
Test # 4: Break In and Trigger Out BNC Feedback Test failed!
Break In not receiving Break Out HIGH
FAILED Number of tests: 1 Number of failures: 1
Before returning to HP, check to ensure that you have connected a
good coaxial cable between the two BNCs. If the cable is good, the
emulator is bad.