User`s guide

CPU32 Emulation 187
Chapter 11: Troubleshooting the Emulator
Problems with the Emulation Probe
If a performance verification test fails
There are some things you can do if a failure is found on one of these
tests. Details of the failure can be obtained through using a -v value
(“verbose level”) of 2 or more.
TEST 2: LAN 10BASE2 Feedback Test failed
For LAN 10BASE2 test, the following is an example of a failure which is
not caused by a broken emulator.
R>pv -t2 -v2 1
Testing: HPE3499B Series Emulation System
Test # 2: LAN 10Base2 Feedback Test failed!
FAILED - no lan connection (LAN probably not terminated
FAILED Number of tests: 1 Number of failures: 1
Check to see that the port under test has a good cable connected to it
and that the cable is properly terminated with a 50 ohm terminator on
each end of the overall cable.
R>pv -t2 -v2 1
Testing: HPE3499B Series Emulation System
Test # 2: LAN 10Base2 Feedback Test failed!
FAILED due to excessive collisions
FAILED Number of tests: 1 Number of failures: 1
The most common cause of this problem is poor termination of the
cable or failure to remove the port under test from the LAN before
performing the test. Check to see that the terminators are good (50
ohms) and that you are isolated from any traffic on a system LAN.
R>pv -t2 -v2 1
Testing: HPE3499B Series Emulation System
Test # 2: LAN 10Base2 Feedback Test failed!
FAILED - invalid Ethernet address in EEPROM
FAILED Number of tests: 1 Number of failures: 1
First check to see that a correct link-level address and IP address have
been set in the virtual EEPROM through the “lan” command. If the
“lan” command shows bad information for the link-level address and IP,