
8712ET/ES and 8714ET/ES Troubleshooting and Block Diagrams
RF Network Analyzers Category 4 Failures: Peripheral Device Problems
Service Guide 4-41
3.
Make sure the LAN is enabled by pressing
. If the state was previously off, then it is necessary to cycle the
power again before the LAN will function.
4. Find and note the IP address of another working LAN device on the same network.
Make sure this device is turned on, connected, and is functioning properly.
5. Press
. Enter the IP address of the other LAN device.
6. Press .
7. The analyzer will attempt 4 cycles of communications with the indicated LAN device. It
will display the time it took to complete each cycle. Each cycle will time-out in one
second if no communication is established and the message
Timeout waiting for
reply will be displayed. It is common for the first of the four cycles to time-out even
though subsequent cycles pass. See below for an example output of a successful ping.
Resolving 15.4.43.255.
Pinging 15.4.43.255.
64 bytes from 15.4.43.255: time=60 ms
64 bytes from 15.4.43.255: time=50 ms
64 bytes from 15.4.43.255: time=60 ms
64 bytes from 15.4.43.255: time=50 ms
Finished PING test.
This establishes one way communication from the analyzer to the network. Reverse
communication should also be verified. Determining this, though, is dependent upon your
network setup and software. Generally, you will need to issue a ping command using the IP
address of the analyzer to be tested. For example, using Windows 95 and while at a DOS
prompt, type in
ping xxx.xxx.xxx.xxx, then press (the letters x represent the
IP address of the analyzer). If full communication can be established, then the computer
display will show the cycle time for each of four cycle attempts (similar to that in step 7).
Other software may behave slightly differently, but all should function basically the same.
If the analyzer will talk to the network, but the network will not talk to the analyzer, then
the computer or device used from the network may have a subnet mask that excludes
communication with the IP address chosen for the analyzer. Any subnet mask other than
0.0.0.0 will exclude operation from some addresses. Changing the subnet mask of a
computer or other device should only be attempted by a qualified network administrator.
Failure to communicate due to a subnet mask incompatibility does not indicate any failure
of the analyzer.
If the analyzer fails to ping in either direction, and assuming the subnet masks are okay,
then the fault must be isolated to the analyzer or to the network. Contact a qualified
network administrator or refer to the Agilent Technologies 8712ET/ES and 8714ET/ES
LAN Interface User’s Guide Supplement for more troubleshooting information. You may
also substitute a known working analyzer to help isolate the fault.
SYSTEM OPTIONS
SYSTEM OPTIONS
ENTER
Commenti su questo manuale