Installing the Interface Module
Ethernet LAN Interface
3Verify connectivity with an echo request.
In most network environments, an echo request is accomplished using the ping utility. For the exact syntax for the ping or other echo request utility, refer to your network documentation. A normal response to multiple echo requests is 9, 10, or possibly 11 packets transmitted for every 10 echo requests.
If there is no response to the echo request, first check the command line. If an IP address is used in the echo request command line, then the IP address typed in the command line should match the IP address stored in the
HP 16500B Ethernet Configuration menu. If a hostname was used in the command line, then check the node names database to see that the IP address and the hostname for the HP 16500B were correctly entered.
After verifying the command line, check to make sure the hardware is connected and operating properly. To verify operation of the interface module, refer to "To verify the interface module performance" in Chapter 3.
An intermittent response to the echo request indicates a problem with the LAN itself. Use a LAN analyzer or LAN management software to monitor activity and determine where bottlenecks or other problems are occurring.
4Mount the HP 16500B system with an NFS mount.
An NFS mount of the 16500B system depends on the network environment the system is being mounted to. For UNIX, the mount command with the computer name and mount point are required. In
The normal response to an NFS mount in most cases is the command line prompt reappears. If the system includes a utility to view the mount table (for example, in UNIX, the mount command alone displays /etc/mnttab), then the 16500B remote file server should appear in the table of mounted devices.
If error messages appear, then check the command line syntax. If the syntax is correct, then resolve the error message directly using your network documentation. Note that an error message appears if you try to mount too soon after
