Agilent Technologies 8714ET, 8714ES, 8712ET User Manual

LAN Interface User’s Guide Supplement

Agilent Technologies 8712ET/ES and 8714ET/ES

RF Network Analyzers

Part No. 08714-90013

Printed in USA

Print Date: June 2000

Supersedes October 1999

Notice

Softkey

The information contained in this document is subject to change without notice. Agilent Technologies makes no warranty of any kind with regard to this material, including but not limited to, the implied warranties of merchantability and ﬁtness for a particular purpose. Agilent Technologies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Key Conventions

This manual uses the following conventions:

FRONT PANEL KEY

analyzer (a “hardkey”).

: This indicates a “softkey”— a key whose label is determined by the instrument’s ﬁrmware, and is displayed on the right side of the instrument’s screen next to the eight unlabeled keys.

: This represents a key physically located on the

Firmware Revision

This manual documents analyzers with ﬁrmware revisions E.06.00 and later.

ii LAN Interface Supplement

Acknowledgments

Excel™ is a product of Microsoft® Corporation. Lotus® 1-2-3®, and Lotus Amipro are U.S. registered trademarks of Lotus

Development Corporation. Microsoft Excel® and Microsoft Word are U.S. registered trademarks of

Microsoft Corporation. QuickBasic™ is a product of Microsoft Corporation. Windows® is a registered trademark of Microsoft Corporation. Portions of the TCP/IP software are copyright Phil Karn, KA9Q. GIF output routines are by John Silva (derived from Jef Poskanzer’s

PBMplus package). Java™ is a U.S. trademark of Sun Microsystems, Incorporated. Lotus® 1-2-3® are U.S. registered trademarks of Lotus Development

Corporation. Microsoft® is a U.S. registered trademark of Microsoft Corporation. MS® and MS-DOS® are U.S. registered trademarks of Microsoft

Corporation. MS Windows®, Windows®, Windows 95®, and Windows NT® are U.S.

registered trademarks of Microsoft Corporation. Netscape® is a U.S. registered trademark of Netscape Communications

Corporation. Pentium® is a U.S. registered trademark of Intel Corporation. Postscript™ is a trademark of Adobe Systems Incorporated which may

be registered in certain jurisdictions. Reﬂection™ is a U.S. trademark of Walker, Richer & Quinn, Incorporated. UNIX® is a registered trademark in the United States and other

countries, licensed exclusively through X/Open Company Limited. Portions of the software include source code from the Info–ZIP group. This code is

freely available on the Internet by anonymous ftp asftp.uu.net:/pub/archiving/zip/unzip51/.tar.Z, and from CompuServe asunz51.zip in the IBMPRO forum, library 10 (data compression).

LAN Interface Supplement iii

Documentation Outline

This User’s Guide Supplement describes how to connect, use and troubleshoot the LAN interface on your analyzer. This supplement contains the following chapters:

1. Connecting and Conﬁguring the Analyzer

2. Accessing the Analyzer’s Web Pages

3. Printing Describes how to conﬁgure and print to a network

4. Accessing the Analyzer’s File System

5. Accessing the Analyzer’s Dynamic Data Disk

6. Controlling the Analyzer via the LAN

7. Using Network File System (NFS)

8. General Troubleshooting Describes what to do if you have a problem using the

Describes how to connect the analyzer to the LAN, and how to conﬁgure the analyzer for use on the LAN. Basic user account and ﬁle administration is also described. To effectively use this chapter, you should be familiar with your network setup and operation.

Describes how to use a Web browser to access built-in Web pages.

printer. Describes how to access the analyzer’s ﬁle system

using ﬁle transfer protocol (FTP). The directory structure of the analyzer is described here.

Describes the analyzer’s ‘data’ directory, the dynamic data disk. Includes an example program.

Shows you methods for programming the analyzer via the network connection.

Describes how to conﬁgure and use NFS.

analyzer on your network.

9. Quick Reference Provides useful information in summary form. Glossary Deﬁnitions for networking and other terms used in

this book.

iv LAN Interface Supplement

Agilent Technologies 8712ET/ES and 8714ET/ES Network Analyzer Documentation Map

The CDROM provides the contents of all of the documents listed below.

The User’s Guide shows how to make measurements, explains commonly-used features, and tells you how to get the most performance from the analyzer.

The LAN Interface User’s Guide Supplement shows how to use a local area network (LAN) for programming and remote operation of the analyzer.

The Automating Measurements User’s Guide Supplement provides information on how to conﬁgure and control test systems for automation of test processes.

The Programmer’s Guide provides programming information including GPIB and SCPI command references, as well as short programming examples.

LAN Interface Supplement v

The Example Programs Guide provides a tutorial introduction using BASIC programming examples to demonstrate the remote operation of the analyzer.

The Service Guide provides the information needed to adjust, troubleshoot, repair, and verify analyzer conformance to published speciﬁcations.

The HP Instrument BASIC User’s Handbook describes programming and interfacing techniques using HP Instrument BASIC, and includes a language reference.

The HP Instrument BASIC User’s Handbook Supplement shows how to use HP Instrument BASIC to program the analyzer.

The Option 100 Fault Location and Structural Return Loss Measurements User’s Guide Supplement provides theory and measurement examples for making fault location and SRL measurements. (Shipped only with Option 100 analyzers.)

The CATV Quick Start Guide provides abbreviated instructions for testing the quality of coaxial cables. (Shipped only with Option 100 analyzers.)

The Cellular Antenna Quick Start Guide provides abbreviated instructions for verifying the performance of cellular antenna systems. (Shipped only with Option 100 analyzers.)

vi LAN Interface Supplement

Contents

1. Connecting and Conﬁguring the Analyzer

About This Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Intoducing the LAN Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

LAN Client/Server Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Connecting the Analyzer to the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Setting Up a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Point-to-Point Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Conﬁguring the Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

The Analyzer's IP Address and Hostname . . . . . . . . . . . . . . . . . . . . . 1-8

The Gateway Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

The Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

The Ethernet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

To Conﬁgure the Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Testing the LAN Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Running Ping under Windows 95. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Running Ping under UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Managing User Names and Passwords . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Constructing Valid User Names and Passwords . . . . . . . . . . . . . . . 1-13

Adding New User Names and Passwords. . . . . . . . . . . . . . . . . . . . . 1-13

Removing a User from the Access List . . . . . . . . . . . . . . . . . . . . . . . 1-14

Displaying the Access List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Using BOOTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

BOOTP Fundamentals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Setting Up the BOOTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Setting Up the BOOTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Testing BOOTP . . . . . . . . . . . . . . . . . . . .1-18

Setting Up LAN Features with Wizards . . . . . . . . . . . . . . . . . . . . . . . 1-21

IBasic LAN Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

vii

Contents

Windows LAN Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-21

2. Accessing the Analyzer's Web Pages

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

Accessing the Analyzer with Your Web Browser . . . . . . . . . . . . . . . . . .2-4

Screen Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Control the Analyzer with SCPI Commands. . . . . . . . . . . . . . . . . . . .2-8

Analyzer Conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11

Other Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11

3. Printing

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

Compatible Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

Conﬁguring the Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Conﬁguring the Analyzer for Printing to a LAN Printer. . . . . . . . . . . .3-4

If You Have Trouble Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

4. Accessing the Analyzer's File System Using FTP

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Using FTP to Access the Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

Example 1: Copying a File to the Analyzer. . . . . . . . . . . . . . . . . . . . .4-5

Example 2: Retrieving a File from the Analyzer. . . . . . . . . . . . . . . . .4-6

Commonly Used FTP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8

Using GUI FTP Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10

Example: Transferring Files between the Analyzer and Your PC . .4-10

viii

Contents

5. Accessing the Analyzer's Dynamic Data Disk

The Dynamic Data Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Saving and Recalling Analyzer States . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Copying Programs to and from the Analyzer. . . . . . . . . . . . . . . . . . . . . 5-7

Copying an IBASIC Program to or from the Analyzer. . . . . . . . . . . . 5-7

Copying and Running a Program with One Command . . . . . . . . . . . 5-9

Copying a Screen Image to a Local File . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Copying Instrument Parameters in ASCII Text Format. . . . . . . . . . . 5-13

Retrieving Measurement Data in ASCII Format. . . . . . . . . . . . . . . . . 5-14

Importing Graphics or Data into PC Applications . . . . . . . . . . . . . . . 5-15

Importing a Screen Snapshot into a Word Processor Program . . . . 5-15

Importing Trace Data into a Spreadsheet Program. . . . . . . . . . . . . 5-16

6. Controlling the Analyzer via the LAN

About This Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Using Socket Programming to Control Your Analyzer . . . . . . . . . . . . . 6-3

Setting Up Your Analyzer for Socket Programming. . . . . . . . . . . . . . 6-3

Controlling the Analyzer via the Dynamic Data Disk. . . . . . . . . . . . . . 6-4

Entering Commands Directly with Telnet . . . . . . . . . 6-5

Telnet Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Controlling the Analyzer with a C Program . . . . . . . . . . . . . . . . . . . . . 6-9

IBASIC Communication across the LAN. . . . . . . . . . . . . . . . . . . . . . . 6-24

Controlling Multiple Analyzers using a Perl Script . . . . . . . . . . . . . . 6-28

Controlling the Analyzer using HP VEE . . . . . . . . . . . . . . . . . . . . . . . 6-31

Controlling the Analyzer with a Java™ Applet. . . . . . . . . . . . . . . . . . 6-33

Controlling the Analyzer using SICL LAN . . . . . . . . . . . . . . . . . . . . . 6-42

Contents

Collecting SICL LAN Setup Information. . . . . . . . . . . . . . . . . . . . . .6-43

Conﬁguring Your Analyzer as a SICL LAN Server. . . . . . . . . . . . . .6-44

Conﬁguring Your PC as a SICL LAN Client . . . . . . . . . . . . . . . . . . .6-44

Controlling Your Analyzer with SICL LAN and HP VEE . . . . . . . .6-45

Controlling Your Analyzer with SICL LAN and HP BASIC for

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-49

Controlling Your Analyzer with SICL LAN and HP BASIC for UNIX

(Rocky Mountain BASIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-50

7. Using the Network File System (NFS)

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

Introduction to NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

NFS Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

Setting Up NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Conﬁguring the Analyzer as an NFS Client . . . . . . . . . . . . . . . . . . . .7-5

Using a Local HOSTS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11

Using NFS Automount—Connecting to Network Resources

Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13

Using Save/Recall with NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15

8. General Troubleshooting

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

Troubleshooting the Initial Connection . . . . . . . . . . . . . . . . . . . . . . . . .8-3

Assess the Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

Ping the Analyzer from Your Computer or Workstation. . . . . . . . . . .8-5

Ping Your Computer or Other Device from Your Analyzer. . . . . . . . .8-7

Capturing Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-10

Subnets and Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-15

Troubleshooting Subnet Problems. . . . . . . . . . . . . . . . . . . . . . . . . . .8-17

Solutions to Common Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18

Contents

If you cannot connect to the analyzer . . . . . . . . . . . . . . . . . . . . . . . . 8-18

If you cannot access the ﬁle system via ftp. . . . . . . . . . . . . . . . . . . . 8-18

If you cannot telnet to the command parser port. . . . . . . . . . . . . . . 8-19

If you get an "operation timed-out" message . . . . . . . . . . . . . . . . . . 8-19

If you cannot access internal web pages or import graphic images when

using a point-to-point connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

If all else fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

9. Quick Reference

EIA/TIA 568B Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

The TELNET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Options and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

The FTP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Options and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

The PING Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Options and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Dynamic Data Disk Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Agilent Technologies Sales and Service Ofﬁces. . . . . . . . . . . . . . . . . . 9-11

Glossary

1 Connecting and Conﬁguring the

Analyzer

1-1

Connecting and Conﬁguring the Analyzer

About This Chapter

This chapter describes how to

• connect your analyzer to your network

• set up a network

• conﬁgure your analyzer

• verify connectivity

• manage user names and passwords

• conﬁgure your analyzer automatically using BOOTP

• run programs automatically using BOOTP

In order to complete the steps in this chapter, you'll need ❏ A computer with a LAN interface, running an operating system that

supports TCP/IP, like UNIX® or Microsoft Windows 95®. A typical computer would be an IBM-compatible Pentium®-based PC with a 10Base-T LAN card, or an HP J210 PA-RISC workstation.

❏ A computer program that communicates over the LAN using TCP/IP.

This might be an FTP or telnet program, or a program that you write. This will be covered in detail in the following chapters.

❏ LAN cabling, and typically a LAN hub.

If you only wish to print to a LaserJet printer via the LAN, you'll need

❏ an HP LaserJet printer with an HP JetDirect LAN interface card ❏ LAN cabling, and typically, a LAN hub

NOTE Older versions of Novell Netware used IPX networking protocol

exclusively. IPX protocol is not compatible with TCP/IP protocol. Newer versions of Novell Netware, such as version 3.1x and 4.xx

accommodate add-on products which provide a gateway to a TCP/IP network. Consult your Novell network administrator for the latest information on using Novell Netware with TCP/IP protocol.

1-2 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Intoducing the LAN Interface

With the LAN interface you can

• transfer IBASIC programs between your computer and your

analyzer

• transfer ﬁles between your computer and your analyzer using ﬁle

transfer protocol (FTP)

• save ﬁles from your analyzer to a computer using network ﬁle system

(NFS)

• connect many analyzers to one computer

• automate the control of your analyzer

• program the analyzer using SCPI commands

• print hardcopy directly to an HP LaserJet printer

• use your analyzer’s Web links to ﬁnd

✓ general information about the Agilent 87xx family of analyzers ✓ online documentation such as SCPI command references ✓ speciﬁc information about your analyzer such as your current

ﬁrmware revision, installed options, even the analyzer’s current screen image

✓ general information about Agilent Technologies , and how to obtain

assistance if you need it

LAN Interface Supplement 1-3

Connecting and Conﬁguring the Analyzer

Intoducing the LAN Interface

LAN Client/Server Functions

Your analyzer acts as either a client or server when you use the client/server features of the analyzer. For example, if you use Network File System (NFS), your analyzer acts as an NFS client (see Chapter 7,

“Using the Network File System (NFS),” on page 7-1). The table below

lists the client/server features of the analyzer, and the function performed by the analyzer when you use each feature:

Client/Server Feature Analyzer Function

BOOTP client FTP server NFS client SICL LAN server

1-4 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Connecting the Analyzer to the LAN

Your analyzer has an RJ-45 connector (see Figure 1-1) and connects to your network using 10Base-T unshielded twisted pair (UTP) cabling, also called Ethertwist. Ethertwist cables resemble standard modular phone cables.

NOTE If your network uses ThinLAN (10Base-2), you will need to purchase an

adapter which converts the ThinLAN BNC connector to 10Base-T Ethertwist.

To connect the analyzer to your network:

1.Turn off the analyzer.

2.Connect the Ethertwist cable from your network to the LAN

ETHERTWIST port on the rear of your analyzer.

3.Turn on the analyzer.

Figure 1-1 The LAN ETHERTWIST Port

LAN Interface Supplement 1-5

Connecting and Conﬁguring the Analyzer

Setting Up a Network

If you do not already have a network, you will need to create one. A simple network consists of a central LAN hub with multiple Ethertwist cables, one connected to the LAN port of each network device. This is often called a star topology, with the LAN hub at the center.

• Typical 8-port hub HP J2610B AdvanceStack 10Base-T Hub-8U

• Typical 16-port hub HP J2611B AdvanceStack 10Base-T Hub-16U

• Typical Ethertwist cables 92268A twisted-pair “straight-through” cable, 4 meters 92268B twisted-pair “straight-through” cable, 8 meters 92268C twisted-pair “straight-through” cable, 16 meters 92268D twisted-pair “straight-through” cable, 32 meters 92268N twisted-pair “straight-through” cable, 300 meters

To order cables , contact the nearest Agilent T ec hnologies sales or service ofﬁce. See Table 9-5 on page 9-11 for a list of sales and service ofﬁces.

Figure 1-2 Example of LAN Star Topology

1-6 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Setting Up a Network

Point-to-Point Connections

It is possible to connect a single computer to a single analyzer, and avoid using a LAN hub. T o do this, you must use a special “cross-over” cable or adapter, which acts like a LAN hub. See “EIA/TIA 568B Wiring” on page

9-2 for wiring details. If you try to create a point-to-point connection

using a standard “straight-through” cable, it will not work. For most applications, the use of a LAN hub is simpler, and additional devices can be added easily.

NOTE Some commercially-available cross-over cables do not implement the

cross-over wiring required for your analyzer. Please refer to “EIA/TIA

568B Wiring” on page 9-2 and verify all connections before using cables

not made by Agilent Technologies.

NOTE Point-to-point connections may not work when connecting to older laser

printers. Older printers typically require a boot server for network use. For a point-to-point connection with a printer, use an HP LaserJet 4 or newer.

NOTE Point-to-point connections do not require the use of proxy servers, since

no server is present in a point-to-point network connection. To use a point-to-point connection, ﬁrst disable the use of a proxy server in your LAN software. Refer to your software documentation for instructions how to do this.

LAN Interface Supplement 1-7

Connecting and Conﬁguring the Analyzer

Conﬁguring the Analyzer

Before you conﬁgure your analyzer, you will need to contact your network administrator to obtain the following information:

❏ an IP address for the analyzer ❏ a host name for the analyzer ❏ a gateway IP address ❏ a subnet mask

The Analyzer's IP Address and Hostname

Each device on your network must have a unique address so that all devices can communicate simultaneously over the same network. These unique addresses are called IP addresses, and are assigned by your network administrator. An IP address is a set of four decimal numbers, separated by periods, like 192.170.128.21. In this document, the term “LAN address” refers to the IP address.

CAUTION It is important that no two devices are assigned the same IP address.

Both devices may fail to communicate on the network. You may also receive (or request) from your network administrator a

hostname for your analyzer, like my8712. The hostname is not required, but can be used on your computer so that

you don't have to remember the IP address. Typically, the hostname is found in the /etc/hosts or control panel/network ﬁle on your computer or is returned by a name server.

Your network administrator will apply for a range of IP addresses from the Internet Network Information Center (InterNIC). InterNIC is responsible for registering domain names and assigning TCP/IP network numbers to networks that connect to the Internet. You may contact InterNIC via e-mail at hostmaster@internic.net, or by accessing their Web site at http://www.networksolutions.com.

1-8 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Conﬁguring the Analyzer

The Gateway Address

If your analyzer will be communicating with devices on different physical networks, you may need to have your network administrator assign a gateway IP address for you. The gateway IP address is the address of a routing device that connects your analyzer's LAN with other LANs. Set the gateway address to 0.0.0.0 if a gateway is not required. See “To

Conﬁgure the Analyzer” on page 1-10 to set this.

See “Subnets and Gateways” on page 8-15 for more information on gateway addresses.

The Subnet Mask

If your analyzer will be communicating with devices on different physical networks, you may need to have your network administrator assign a subnet mask number for you. The subnet mask tells your analyzer whether a remote device is on the same LAN as your analyzer. If your analyzer is attempting to communicate with another device, the subnet mask deﬁnes whether your analyzer needs to route communications through the gateway. Set the subnet mask to 0.0.0.0 if a subnet mask is not required. See “Conﬁguring the Analyzer” on page 1-8to set this.

See “Subnets and Gateways” on page 8-15 for more information on subnet masks.

The Ethernet Address

Y our analyzer has a unique built-in Ethernet address associated with the LAN hardware inside it. The Ethernet address is a 48-bit number assigned at the factory. You don’t have to know the Ethernet address to conﬁgure and use the analyzer, unless you are using the BOOTP feature (see “Using BOOTP” on page 1-15 for details).

LAN Interface Supplement 1-9

Connecting and Conﬁguring the Analyzer

LAN

LAN Port Setup

HP 871xxx IP Address

Gateway IP Address

Subnet Mask

Conﬁguring the Analyzer

To Conﬁgure the Analyzer

1. Press to access the LAN menu.

NOTE After each of the following steps, the analyzer will prompt you to cycle

power for the new setting to take effect. It is not necessary to cycle the power after each step. It only needs to be done once—when you are ﬁnished entering all of the settings.

2. Press , and enter the

IP address that your network administrator assigned to your analyzer. You may have also received a hostname (for example: my8712). You cannot enter the hostname into your analyzer, just the IP address. The hostname can be used on your computer so that you don't have to remember the IP address.

3. Press , and enter the numbers assigned to

you by your network administrator. If you were not assigned a gateway IP address, leave the setting at 0.0.0.0 (default value) to disable gateway routing.

4. Press , and enter the numbers assigned to you by

your network administrator. If you were not assigned a subnet mask, leave the setting at 0.0.0.0 (default value) to disable subnet masking.

5. Once you have entered these settings, cycle the power on your

analyzer to initialize the LAN interface with these new values.

SYSTEM OPTIONS

1-10 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Testing the LAN Communication

You should now test communication between your computer and your analyzer.

The ping utility is typically used to test LAN communication.

Running Ping under Windows 95

Enter the following at the command prompt of a DOS window on your computer or workstation:

ping <IP address>

ping <hostname>

<IP address> is the number that was assigned by your network

administrator and was entered into your analyzer in “To Conﬁgure the

Analyzer” on page 1-10. The <hostname> is the hostname assigned to

your IP address. For example, type:

ping my8712

where my8712 is the <hostname>.

The ping utility has three common responses. If there is a valid working connection, you should see a response similar to this:

Pinging my8712 [15.4.43.5] with 32 bytes of data: Reply from 15.4.43.5: bytes=32 time=37ms TTL=252

Reply from 15.4.43.5: bytes=32 time=30ms TTL=252 Reply from 15.4.43.5: bytes=32 time=30ms TTL=252 Reply from 15.4.43.5: bytes=32 time=31ms TTL=252

If you see a response similar to the following, your connection may have a problem. Refer to “Troubleshooting the Initial Connection” on page 8-3 for troubleshooting help and information.

Request timed out. Request timed out. Request timed out. Request timed out.

LAN Interface Supplement 1-11

Connecting and Conﬁguring the Analyzer

Testing the LAN Communication

The following response is generally caused by an incorrect subnet mask or IP address. It usually points to a software setting conﬂict, and does not signify a hardware problem.

Host Unreachable. Host Unreachable. Host Unreachable. Host Unreachable.

Running Ping under UNIX

The ping program is typically found in the /etc or/usr/etc directory, so you must add the appropriate directory to your path, or type the full path:

/etc/ping <IP address> 64 5

/etc/ping <hostname> 64 5

This command tells ping to send 5 packets of 64 bytes each. The output should look similar to this:

PING hostname: 64 byte packets 64 bytes from 15.4.43.5: icmp_seq=0. time=8. ms 64 bytes from 15.4.43.5: icmp_seq=1. time=4. ms 64 bytes from 15.4.43.5: icmp_seq=2. time=4. ms 64 bytes from 15.4.43.5: icmp_seq=3. time=3. ms 64 bytes from 15.4.43.5: icmp_seq=4. time=3. ms

hostname PING Statistics 5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 3/4/8

If you do not see any output after about 20 seconds, interrupt the ping command using ^c (hold down the “Ctrl” key, and press “c”). Once you do this, the ping program should provide some statistics on how many packets were sent and received. If the statistics look like

hostname PING Statistics 4 packets transmitted, 0 packets received, 100% packet loss

there is a communications problem. Refer to “Troubleshooting the Initial

Connection” on page 8-3 for troubleshooting help and information.

1-12 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

LAN

Add Login User

Enter

Managing User Names and Passwords

Your analyzer implements a limited form of network security using user name and password pairs. Any remote access of the analyzer, including Telnet or FTP access, requires a valid user name and associated password.

A default user name and password pair is set for you prior to shipment: User Name network Password analyzer

NOTE You should change this user name and password if you want to use the

security features of the analyzer, since the default user name and password is the same for all new analyzers, and is therefore public.

Constructing Valid User Names and Passwords

A valid user name must have 1 to 40 characters. A valid password must have 8 to 40 characters.

Adding New User Names and Passwords

NOTE You can add up to seven user name/password pairs to the analyzer’s

access list. Perform the following steps to add a new user name and password to the

access list:

1. Press .

2. Press .

3. Type the user name in the displayed dialog box.

4. Press when you are done.

5. Type the password in the displayed dialog box.

6. Press when you are done.

LAN Interface Supplement 1-13

SYSTEM OPTIONS

Connecting and Conﬁguring the Analyzer

Enter

LAN

Delete Login User

Enter

LAN

Delete All Users

LAN

Display User List

Managing User Names and Passwords

7. Type the password again (to conﬁrm the password) in the displayed dialog box.

8. Press when you are done.

If the entries are valid, the new user name and password will be conﬁrmed with the following message:

User ... has been added to the list

Removing a User from the Access List

Perform the following steps to remove a user from the access list:

1. Press .

2. Press .

3. Type the user name in the dialog box that is displayed.

4. Press to conﬁrm your entry.

5. Type the user password in the dialog box.

6. Press to conﬁrm your entry.

If the entries are valid you should see a conﬁrmation message displayed on the screen:

User ... has been deleted from the list

NOTE If you forget any of the user passwords, you will have to delete all users

by pressing

SYSTEM OPTIONS

and re-enter all user names and passwords.

Displaying the Access List

1. Press .

2. Press .

A table of the login user names will be displayed on the screen.

SYSTEM OPTIONS

1-14 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Using BOOTP

BOOTP Fundamentals

The Bootstrap Protocol (BOOTP) is a simple and elegant method of automatically distributing network information and software via the LAN. BOOTP is built on the client-server model. The BOOTP client conﬁgures itself using conﬁguration information obtained from a BOOTP

server. Your analyzer has a built-in BOOTP client. The analyzer can use BOOTP to conﬁgure itself automatically, obtaining its network

conﬁguration information (IP address, gateway address, and subnet mask) from a central BOOTP server over the network. On power up, the analyzer broadcasts a request to boot from a remote server. If a BOOTP server is available on the LAN listening for BOOTP client requests, it transmits conﬁguration parameters to the analyzer over the network. The analyzer uses those parameters automatically.

BOOTP can also be used to automatically retrieve and execute an IBASIC program at boot time. The boot ﬁle is transferred to the analyzer from the BOOTP server using FTP or trivial ﬁle transfer protocol (TFTP). If the transfer is successful, the ﬁle will be loaded into the analyzer’s memory and executed. The boot ﬁle can be any valid IBASIC program.

Setting Up the BOOTP Server

To use the BOOTP client in your analyzer, you need a BOOTP server application running on a remote UNIX system or a PC. A BOOTP server, bootpd (BOOTP daemon), is an integral part of most UNIX operating systems. You will need to obtain a separate BOOTP server application for your PC. Consult your network administrator for obtaining a BOOTP server application for your PC, and for assistance setting up a BOOTP server.

The following steps are required to use BOOTP:

1. Assure that the analyzer and BOOTP server are not separated by a gateway. Consult your network administrator if you are not sure.

2. Set up a BOOTP server application on a remote host (UNIX system or PC). You will need the following information:

LAN Interface Supplement 1-15

Connecting and Conﬁguring the Analyzer

LAN

LAN Port Setup

Ethernet Address

LAN

BOOTP Setup

BOOTP ON off

FTP

FTP User Name

FTP Password

Timeout

Using BOOTP

❏ The Ethernet address of the analyzer. To ﬁnd out the Ethernet

address of your analyzer, press

SYSTEM OPTIONS

❏ An IP address for the analyzer. This address is usually assigned

by your network administrator.

❏ An optional BOOTP host name and IP address. ❏ An optional absolute (fully qualiﬁed) path to the boot ﬁle, which

includes all the directories leading to it. If you want to retrieve an IBASIC boot program from your BOOTP server at boot time and execute it, you must know the absolute path to the boot ﬁle. The boot ﬁle must be accessible using FTP or TFTP.

❏ The LAN gateway address and the subnet mask.

Setting Up the BOOTP Client

Perform the following steps to set up the BOOTP client in your analyzer:

1. Press .

2. Toggle [BOOTP] to ON if needed to enable BOOTP. The softkey label will change to .

3. Press or to select either FTP or TFTP ﬁle transfer method. If your remote system requires a user name and password, you must use FTP, since TFTP does not implement any user validation.

If you select a. Press and enter a valid user name for your

b. Press and enter a valid password for your

4. Press and enter a timeout time, in seconds, for BOOTP requests. This value is typically between one and ﬁve seconds. The

spend transmitting BOOTP requests at boot time. If there is no response to the ﬁrst BOOTP request, then the analyzer will retransmit

SYSTEM OPTIONS

remote BOOTP host.

value is the number of seconds that your analyzer will

1-16 LAN Interface Supplement

Connecting and Conﬁguring the Analyzer

Timeout

Optional Boot Host

Clear Entry

Enter

Optional Boot Host

Optional File Name

Using BOOTP

a request. The analyzer will continue to retransmit requests at exponentially increasing time intervals until it receives a response or the value has expired.

5. Press and enter a hostname or a host IP address if you want BOOTP requests sent to a speciﬁc remote host only. Otherwise, the analyzer will broadcast a BOOTP request at boot time, and will accept a response from any BOOTP server.

If you do not want to use , make sure that it contains a null or empty string by pressing

NOTE If you use , you are also required to set up your

analyzer’s IP address. Refer to“To Conﬁgure the Analyzer” on page 1-10 for details on how to set up your analyzer’s IP address.

NOTE A local HOSTS ﬁle is required to specify a boot host by name. A local

HOSTS ﬁle is not required to specify a boot host by IP address. “Using a

Local HOSTS File” on page 7-11 for details about creating and using a

local HOSTS ﬁle.

NOTE You must use the UNIX-style forward slash (/) to separate names when

6. Press and enter an absolute (fully qualiﬁed) path to the ﬁle to be loaded and executed when the analyzer boots. For example , if your ﬁle name istest23.bas, and the path to the ﬁle is /server5/users/testeng/prodtests, enter the following for the absolute (fully-qualiﬁed) path name:

/server5/users/testeng/prodtests/test23.bas

you enter path names in the analyzer (the BOOTP client). You may need to use some other character to separate names when you enter path names in your particular BOOTP server.

LAN Interface Supplement 1-17

Connecting and Conﬁguring the Analyzer

Optional File Name

Clear Entry

Enter

LAN

BOOTP Setup

Parameters Received

Using BOOTP

Normally, your analyzer will obtain this ﬁle name from the BOOTP server, but you can override this using . If you do not want to use , make sure that it contains a null string. To do that, press

NOTE You can set up your BOOTP server to select the ﬁle to download when the

analyzer boots. Consult your BOOTP server documentation or your system administrator about setting up a BOOTPTAB ﬁle on the BOOTP server.

Testing BOOTP

After your analyzer has been set up correctly as a BOOTP client, make sure that the BOOTP server is also set up correctly and is running. Consult your network administrator if you need help doing this.

Perform the steps below to verify that BOOTP works correctly:

1. Press

The following dialog box will appear:

SYSTEM OPTIONS

1-18 LAN Interface Supplement

Figure 1-3 BOOTP Setup Dialog Box

Connecting and Conﬁguring the Analyzer

Using BOOTP

The dialog box shown above displays the following information: Host Addr the host address of the BOOTP server IP Addr the analyzer IP address set by BOOTP process Gateway the analyzer gateway IP address set by the BOOTP

process

Subnet Mask the subnet mask set for the analyzer by the BOOTP

process

File Path the absolute (fully-qualiﬁed) path name received

from the BOOTP server, or the [Optional File Path] if set

Step one shows the network parameters received from the BOOTP server. To verify that your IBASIC boot ﬁle is working correctly, perform steps two through four.

LAN Interface Supplement 1-19

+ 155 hidden pages