LanProbe Main Menu (HP-UX Workstation)

Installation/User’s Guide
Agilent J3911A Multiport
Token-Ring LanProbe
Consumer Warranty Statement
Consumer Warranty Statement
AGILENT TECHNOLOGIES, INC. LIMITED WARRANTY STATEMENT
AGILENT PRODUCT
DURATION OF LIMITED WARRANTY
Multiport Token-Ring LanProbe
1 year
Agilent warrants to you, the end-user customer, that Agilent hardware, accessories
and supplies will be free from defects in materials and workmanship after the date
of purchase, for the period specified above. If Agilent receives notice of such
defects during the warranty period, Agilent will, at its option, either repair or
replace products which prove to be defective. Replacement products may be
either new or like-new.
Agilent warrants to you that Agilent software will not fail to execute its
programming instructions after the date of purchase, for the period specified
above, due to defects in material and workmanship when properly installed and
used. If Agilent receives notice of such defects during the warranty period,
Agilent will replace software media which does not execute its programming
instructions due to such defects.
Agilent does not warrant that the operation of Agilent products will be
uninterrupted or error free. If Agilent is unable, within a reasonable time, to repair
or replace any product to a condition as warranted, you will be entitled to a refund
of the purchase price upon prompt return of the product.
Agilent products may contain remanufactured parts equivalent to new in
performance or may have been subject to incidental use.
Warranty does not apply to defects resulting from (a) improper or inadequate
maintenance or calibration, (b) software, interfacing, parts or supplies not
supplied by Agilent, (c) unauthorized modification or misuse, (d) operation
outside of the published environmental specifications for the product, or (e)
improper site preparation or maintenance.
ii
Consumer Warranty Statement
AGILENT MAKES NO OTHER EXPRESS WARRANTY OR CONDITION
WHETHER WRITTEN OR ORAL. TO THE EXTENT ALLOWED BY LOCAL
LAW, ANY IMPLIED WARRANTY OR CONDITION OF
MERCHANTABILITY, SATISFACTORY QUALITY, OR FITNESS FOR A
PARTICULAR PURPOSE IS LIMITED TO THE DURATION OF THE
EXPRESS WARRANTY SET FORTH ABOVE. Some countries, states or
provinces do not allow limitations on the duration of an implied warranty, so the
above limitation or exclusion might not apply to you. This warranty gives you
specific legal rights and you might also have other rights that vary from country to
country, state to state, or province to province.
TO THE EXTENT ALLOWED BY LOCAL LAW, THE REMEDIES IN THIS
WARRANTY STATEMENT ARE YOUR SOLE AND EXCLUSIVE
REMEDIES. EXCEPT AS INDICATED ABOVE, IN NO EVENT WILL
AGILENT OR ITS SUPPLIERS BE LIABLE FOR LOSS OF DATA OR FOR
DIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL (INCLUDING LOST
PROFIT OR DATA), OR OTHER DAMAGE, WHETHER BASED IN
CONTRACT, TORT, OR OTHERWISE. Some countries, States or provinces do
not allow the exclusion or limitation of incidental or consequential damages, so
the above limitation or exclusion may not apply to you.
FOR CONSUMER TRANSACTIONS IN AUSTRALIA AND NEW
ZEALAND: THE WARRANTY TERMS CONTAINED IN THIS STATEMENT,
EXCEPT TO THE EXTENT LAWFULLY PERMITTED, DO NOT EXCLUDE,
RESTRICT OR MODIFY AND ARE IN ADDITION TO THE MANDATORY
STATUTORY RIGHTS APPLICABLE TO THE SALE OF THIS PRODUCT TO
YOU.
iii
Operating Restrictions
The following warnings and operating information are shown in French followed
by the English translation.
MISE ENGARDE
Cet appareil répond aux normes
de la «Classe de sécurité I» et
est muni d'un fil de mise à la
terre pour votre protection.
MISE ENGARDE
Pour prévenir les risques de
choc électrique, la broche de
mise à la terre du cordon
d'alimentation ne doit pas être
désactivée.
WARNING
This product is a Safety Class I
instrument with a protective earth
terminal.
WARNING
For protection from electric shock
hazard, power cord ground must
not be defeated.
Restrictions d'utilisation
L'utilisateur se doit d'observer les mesures de précaution
énumérées ci-dessous pour toutes les phases d'utilisation,
de service et de réparation de cet appareil. Le fait de ne
pas s'y conformer équivaut à ne pas respecter les mises en
gardes spécifiques contenues dans ce manuel et constitue
une violation des normes de sécurité relatives à la
conception, la fabrication et l'utilisation prévue de cet
appareil. La société Agilent Technologies, Inc. n'assume
aucune responsabilité envers un client qui manquerait de
se conformer à ces exigences.
Operating Restrictions
The following general safety precatuions must be observed
during all phases of operation, service, and repair of this
instrument. Failure to comply with these precautions with
specific warnings in this manual violate safety standards of
design, manufacture, and intended use of this instrument.
Mise à la terre
Afin de minimiser les risques de choc électrique, le
chÀssis et le cabinet de l'appareil doivent être mis à la
terre. L'appareil est équipé d'un cordon d'alimentation
muni d'une fiche homoloquée à trois lames, compatible
c.a. La prise murale et la prise femelle de la rallonge
électrique doivent respecter les normes de sécurité de la
«Commision électrotechnique internationale» (IEC).
Grounding
To minimize shock hazard, the instrument chassis and
cabinet must be connected to an electrical ground. The
instrument is equipped with a three-conductor AC power
cable compatible with an approved three-contact electrical
outlet. The power jack and mating plug of the power cord
must meet International Electrotechnical Commission (IEC)
safety standards.
iv
Environnement
Ne faites pas fonctionner cet appareil en présence de gaz
inflammables ou de vapeurs dangereuses. L'utilisation de
n'importe quel appareil électrique dans ces conditions
constitue un risque élevé pour votre sécurité.
Service et ajustement
Des «tensions dangereuses» résident dans cet appareil. Par
conséquent, le service et l'ajustement doivent être effectués
uniquement par une personne qualifiée.
Environment
Do not operate the instrument in the presence of flammable
gases or fumes. Operation of any electrical instrument in
such an environment constitutes a definite safety hazard.
Service and Adjustment
Dangerous voltages exist within this instrument. Service
and adjustment of this instrument is to be performed only by
trained service personnel.
Ne remplacez pas de composantes lorsque le cordon
d'alimentation est sous tension. Il pourrait y avoir présence
de «tensions dangereuses» même lorsque l'appareil est
déconnecté.
Do not replace components with the power cable connected.
Dangerous voltages may be present even when the power
cable is disconnected.
Ne faites pas de service interne ou d'ajustement sauf en
présence d'une autre personne, capable de prodiguer les
premiers soins et de pratiquer la réanimation.
Do not perform internal servicing or adjustment unless
another person, capable of rendering first aid and
resuscitation is present.
Service non autorisé
L'installation de pièces étrangères, ou toute modification
apportée à l'appareil sans le consentement de Agilent
Technologies, Inc. est formellement interdit. Le fait de
procéder à de tels modifications sans autorisation pourrait
entraîner l'annulation de la garantie de l'appareil ou de tout
contrat de service.
Unauthorized Service
The installation of substitute parts or the installation of any
instrument modification not authorized by Agilent
Technologies, Inc. is specifically forbidden. The
performance of such unauthorized service can negate the
instrument warranty or any maintenance agreements.
Pour un service et des réparations autorisées, retournez
l'appareil à un point de vente et service Agilent
Technologies, Inc..
Return the instrument to a Agilent Technologies, Inc. Sales
and Service Office for authorized service and repair.
v
Notice
Notice
© Copyright Agilent Technologies, Inc.
All Rights Reserved
Reproduction, adaptation, or translation without prior written permission is
prohibited, except as allowed under the copyright laws.
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 fitness for a particular purpose. Agilent 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.
Agilent assumes no responsibility for the use or reliability of its software on
equipment that is not furnished by Agilent.
This document contains proprietary information that is protected by copyright. All
rights are reserved. No part of this document may be photocopied, reproduced, or
translated to another language without the prior written consent of Agilent
Technologies, Inc.
Agilent Technologies, Inc.
NetMetrix Division
5070 Centennial Boulevard
Colorado Springs, Colorado 80919-2497
vi
Safety Information
Safety Information
Before you use this instrument, be sure to pay special attention to the “Safety” and
“Warning” topics in this Manual. Failure to comply with the precautions or with
specific warnings in this book violates safety standards of design, manufacture,
and intended use of this instrument. Agilent assumes no liability for the
customer’s failure to comply with these requirements.
Electric Shock Hazard. Do not remove the system covers. To avoid electric
shock, use only the supplied power cords and connect only to properly grounded
(3-pin) wall outlets.
Explosion Hazard. Do not operate in the presence of flammable gases.
Fire Hazard. For continued protection against fire hazard replace only with fuse
of same type and rating.
Indoor Use. This instrument is designed for indoor use.
Cleaning. To clean the instrument, use a damp cloth moistened with a mild
solution of soap and water. Do not use harsh chemicals. Do not let water get into
the instrument.
Product Damage. Do not use this product when:




the product shows visible damage,
fails to perform,
has been stored in unfavorable conditions, or
has been subject to severe transport stresses.
Make the product inoperative and secure it against any unintended operation.
Contact your nearest Agilent office for assistance.
Defects and Abnormal Stresses. Whenever this instrument has been damaged or
wet, make the product inoperative and secure it against any unintended operation.
vii
Warning Symbols Used in This Book
Warning Symbols Used in This Book
Instruction book symbol: the product will be marked with this symbol when it is
necessary for the user to refer to the instruction book in order to protect against
damage.
Indicates potential for electrical shock.
WARNING
An operating procedure, practice, etc. which, if not correctly followed could result
in personal injury or loss of life.
CAUTION
An operating procedure, practice, etc. which, if not strictly observed, could result
in damage to, or destruction of, equipment or software.
viii
Conventions Used in this Book
Conventions Used in this Book
NOTE
An operating procedure, practice, or information of importance, is separated from
normal text as shown in this NOTE.
Terminology and conventions in this manual are handled with the following
methods:
z Keys on the keyboard such as PgDn (page down) or F1 (function key #1)
are printed in the characters you see here.
z Text that you should type is printed in characters such as:
Filename.ext
z In some cases, you must press two keys simultaneously. This is represented
as CTRL + Q.
ix
Trademarks
Trademarks
Agilent is a registered trademark and OpenView is a trademark of
Hewlett-Packard Company.
Microsoft, LAN Manager, MS-DOS, and Windows are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
UNIX is a registered trademark in the United States and other countries, licensed
exclusively through X/Open Company Limited.
Ethernet is a trademark of Xerox Corporation.
Hayes is a registered trademark of Hayes MicroComputer Products, Inc.
IBM and Token-Ring are trademarks of International Business Machines
Corporation.
Sun and Solaris are registered trademarks of Sun Microsystems, Inc.
SPARC is a registered trademark of SPARC International, Inc. Products bearing
the SPARC trademark are based on an architecture developed by Sun
Microsystems, Inc.
Novell and NetWare are registered trademarks of Novell Inc.
x
Printing History
Printing History
New editions are complete revisions of this book. Update packages may contain
new or additional material and be released between editions. See the date of the
current edition on the back cover of this book.
First Edition . . . . . . . . . . . . . . . . . . . . . . . July 1998 J3911-99501
Additional Help
You can obtain additional assistance in the U.S. by calling U.S. Response Center
at 888 699 7280, or Internationally by calling your local Agilent Sales Office.
xi
xii
Contents
Consumer Warranty Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Operating Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv
Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Warning Symbols Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Conventions Used in this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Printing History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Installation and Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . 5
Local Terminal Configuration and Installation . . . . . . . . . . . . . . . . . 5
Installation and Bootp Server Configuration . . . . . . . . . . . . . . . . . . 5
LanProbe Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Supported MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Management Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Status LEDs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
CONFIG Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Included Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Optional Accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 Local Terminal Configuration. . . . . . . . . . . . . . . . . . . 17
Probe Configuration Using a Local Terminal . . . . . . . . . . . . . . . . . .
Using a Local Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify/View Configuration Values . . . . . . . . . . . . . . . . . . . . . . . .
Modify/View Security Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify/View Interface Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Interface Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify/View Serial Port Settings . . . . . . . . . . . . . . . . . . . . . . . . .
19
20
22
24
25
28
30
xiii
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Selecting a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing the Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Rack or Cabinet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Wall Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Connecting the Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Connecting to the Network (Out-of-Band) . . . . . . . . . . . . . . . . . . . 41
Connecting to 10MB/s Ethernet Networks (Telemetry) . . . . . 42
Connecting to 10Base-T/100Base-TX Networks (Telemetry) 44
Connecting to Token-Ring Networks (Telemetry) . . . . . . . . . 45
Connecting to Token-Ring Networks . . . . . . . . . . . . . . . . . . . . . . . 45
Connecting Out-of-Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Modem Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Data Switch Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Starting the Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4 Bootp Server Configuration . . . . . . . . . . . . . . . . . . . . 59
Probe Configuration Using a Bootp Server
. . . . . . . . . . . . . . . . . . . 61
Bootp Server Setup on an HP or Sun System . . . . . . . . . . . . . . . . . . . . 63
Starting the Bootp Server on an HP or Sun System . . . . . . . . . . . . 65
Bootp Server Setup on a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Using Microsoft LAN Manager
. . . . . . . . . . . . . . . . . . . . . . . . . 68
Using Novell NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Starting the PC Bootp Server
. . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring the Bootptab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Example Bootptab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5 LanProbe Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Restarting the Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Warm Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Cycling Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Selecting the Warm Start Menu Item. . . . . . . . . . . . . . . . . . . . 81
Cold Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Pressing the CONFIG Button Twice . . . . . . . . . . . . . . . . . . . . 82
Selecting the Cold Start Menu Item. . . . . . . . . . . . . . . . . . . . . 83
xiv
6 Download New Firmware . . . . . . . . . . . . . . . . . . . . . . 85
Downloading Firmware using an HP-UX Workstation and a Terminal
Install New Download Firmware on an HP-UX Workstation . . . .
Download Firmware to LanProbe . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Firmware using a Networked PC and a Terminal . . . .
Setup TFTP Server for Downloading . . . . . . . . . . . . . . . . . . . . . . .
Download Firmware to LanProbe . . . . . . . . . . . . . . . . . . . . . . . . . .
Xmodem Download of Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Cables and Connectors
88
88
89
93
93
93
98
. . . . . . . . . . . . . . . . . . . . . 103
Token-Ring Cabling Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Interface Cables
..............................
Cable Connector Pin-Outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LanProbe’s RS-232 Port Pin-Out . . . . . . . . . . . . . . . . . . . . . .
LanProbe RS-232 Modem Cable Connectors . . . . . . . . . . . . .
25-pin Terminal/PC Cable Connectors . . . . . . . . . . . . . . . . . .
9-pin Terminal/PC Cable Connectors . . . . . . . . . . . . . . . . . . .
UTP Network Connector Pin-Out . . . . . . . . . . . . . . . . . . . . . .
STP Network Connector Pin-Out . . . . . . . . . . . . . . . . . . . . . .
105
106
107
107
108
109
109
110
111
B LanProbe Specifications . . . . . . . . . . . . . . . . . . . . . . 113
Probe Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
RMON-2 Protocol Directory . . . . . . . . . . . . . . . . . . . . . . . . . 118
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Index
Agilent Technologies, Inc. Offices
xv
xvi
Figures
Figure 1-1: LanProbe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 1-2: LanProbe System Example . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 1-3: Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 1-4: Back Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 2-1: LanProbe’s Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 2-2: LanProbe Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 2-3: Modify/View Configuration Values Menu . . . . . . . . . . . . 22
Figure 2-4: Modify/View Security Values Menu . . . . . . . . . . . . . . . . . 24
Figure 2-5: Modify/View Interface Values Menu . . . . . . . . . . . . . . . . 26
Figure 2-6: Display Interface Summary . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 2-7: Modify/View Serial Port Settings Menu . . . . . . . . . . . . . . 30
Figure 3-1: Install the Probe in a Rack or Cabinet . . . . . . . . . . . . . . . . . 38
Figure 3-2: Install LanProbe on a Wall . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 3-3: The Probe’s Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 3-4: Close-up of a Token-Ring Interface . . . . . . . . . . . . . . . . . 42
Figure 3-5: Connecting the Probe to a 10MB/s Ethernet Network . . . 43
Figure 3-6: Connecting the Probe to a 10Base-T/100Base-T Network 45
Figure 3-7: Connecting the Probe using RJ-45 Connectors . . . . . . . . . 46
Figure 3-8: Connecting the Probe using a Media Filter . . . . . . . . . . . . 47
Figure 3-9: Connecting the Probe using Data & DB-9 Connectors . . . 48
Figure 3-10: LanProbe Direct Connection . . . . . . . . . . . . . . . . . . . . . . 49
Figure 3-11: LanProbe Modem Connection . . . . . . . . . . . . . . . . . . . . . 49
Figure 3-12: LanProbe Data Switch Connection . . . . . . . . . . . . . . . . . 55
Figure 5-1: LanProbe’s Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 6-1: LanProbe Main Menu (HP-UX Workstation) . . . . . . . . . . . 90
Figure 6-2: LanProbe TFTP Download Menu (HP-UX Workstation) . 91
Figure 6-3: LanProbe Main Menu (Networked PC) . . . . . . . . . . . . . . . 95
Figure 6-4: LanProbe TFTP Download Menu (Networked PC) . . . . . 96
Figure 6-5: LanProbe Main Menu (XMODEM) . . . . . . . . . . . . . . . . . 99
Figure 6-6: LanProbe XMODEM Download Menu (Networked PC) . 99
Figure 1-1: Data Connector Color Coded Connection Points . . . . . . 111
xvii
xviii
Tables
Table 1-1: Private MIB Access Security Privileges . . . . . . . . . . . . . . . . 11
Table 4-1: Minimum Requirements for a Bootp Server
. . . . . . . . . . 62
Table 4-2: Bootp Server bootptab Files . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 4-3: Bootptab File Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 4-4: Bootp Process Verification
. . . . . . . . . . . . . . . . . . . . . . . 75
Table 5-1: Probe Data and Parameters Reset by Warm or Cold Start . . 80
Table A-1: Token-Ring Cable Type, Vp, and Impedance . . . . . . . . . . 105
Table A-2: Serial Port Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . 106
Table A-3: LanProbe’s RS-232 Port Pin-Out . . . . . . . . . . . . . . . . . . . 107
Table A-4: LanProbe to Modem Cable Min. Pin-Out
(25-Pin to 25-Pin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table A-5: LanProbe to 25-Pin Terminal Cable Min. Pin-Out . . . . . 109
Table A-6: LanProbe to 9-Pin Terminal Cable Min. Pin-Out . . . . . 109
Table A-7: UTP (Type 3) Network Connector Pin-Outs . . . . . . . . . . 110
Table A-8: STP (Type 1) Network Connector Pin-Outs . . . . . . . . . 111
Table B-1: LanProbe Memory Allocation . . . . . . . . . . . . . . . . . . . . . . 117
Table B-2: RMON-2 Protocol Directory . . . . . . . . . . . . . . . . . . . . . . 118
xix
xx
1
Introduction
Introduction
Introduction
This chapter introduces the Agilent 3911A Multiport Token-Ring LanProbe
(shown in Figure 1-1 on page 3), including its installation and configuration
options.
You can use your LanProbe with NetMetrix/UX, supported for HP-UX and
Solaris. The term “NetMetrix” is used in this manual to refer to Agilent
NetMetrix/UX.
The following sections are included in this chapter:
z “Installation and Configuration Overview” on page 5
z “LanProbe Overview” on page 6
The Agilent J3911A Multiport Token-Ring LanProbe is a MIPS-based,
SNMP-managed segment monitor for Token-Ring networks.
The base hardware configuration supports four Token-Ring interfaces, a
10Base-T/100Base-TX telemetry interface, and a SLIP connection. The Multiport
Token-Ring LanProbe can also be ordered with two additional Token-Ring
interfaces. The 10Base-T/100Base-TX telemetry interface or one of the
Token-Ring interfaces can be used as the telemetry interface. Probe data is
retrieved using SNMP via a LAN or SLIP connection.
The base hardware supports 10Base-T and 100Base-TX with an RJ-45 connector.
By default, this interface functions as the telemetry interface for the probe. The
LanProbe also has an AUI connector for connection to 10 MB/s Ethernet
telemetry networks. The telemetry port retrieves data associated with the other
interfaces on LanProbe, but does not maintain RMON or other network statistics
for its own network.
2
Introduction
Figure 1-1: LanProbe
The Multiport Token-Ring LanProbe has 64 MB of memory (optionally 128 MB),
and uses FLASH EPROM. Future upgrades to LanProbe’s firmware are easily
downloaded over the LAN to multiple probes simultaneously. You can also
download firmware using LanProbe’s serial port.
LanProbe maintains a variety of statistical measurements on network
performance, continuously keeping track of traffic levels, errors, and other
important trends. Alarm thresholds can be set on any of these parameters,
immediately alerting the network manager or initiating a packet trace to capture
the details of the event for later analysis. Traffic and error levels are also
monitored per node for each station on the segment.
Private MIB extensions give LanProbe additional capabilities beyond RMON.
Multiple SNMP trap addresses, or groups of addresses, can be defined for event
notification. The probe maps MAC addresses to IP addresses for node
identification, and provides duplicate IP address detection. A real time utilization
variable has been added, which provides the ability to alarm on instantaneous
peaks of network load. An additional Out-of-Band connection to the probe can be
established using Serial Link Internet Protocol (SLIP), either directly, using a
modem, or by using a data switch.
You can configure LanProbe to perform Echo Test Monitoring (tests to verify
communications) of network nodes from your network management station.
LanProbe allows the network manager to select one or several nodes to perform a
one-time test or specify an interval for periodic testing. You can view the results
of the Echo Test Monitoring from your NetMetrix management console. This can
be very useful for monitoring critical nodes to verify connectivity. This test can
3
Introduction
also be performed from several points on the network (using several LanProbes)
to verify connectivity from each point. When a node becomes unreachable an alert
can be sent from LanProbe to your management station. To provide testing of a
large range of nodes, Echo Test Monitoring supports ICMP, IEEE 802.2, and
IEEE 802.3 for Novell IPX. This extension is supported by the NetMetrix
software.
4
Introduction
Installation and Configuration Overview
Installation and Configuration Overview
To quickly install and configure your LanProbe, it is important for you to
understand the available configuration and installation options. Configuration
consists of setting the LanProbe parameters (IP address, for example). Installation
consists of physically installing the probe and connecting it to the network.
You will reference different chapters of this Installation/User’s Guide depending
on which of the following installation and configuration options you select:
z “Local Terminal Configuration and Installation” below
z “Installation and Bootp Server Configuration” below
Local Terminal Configuration and Installation
This method of installation and configuration requires that you configure the
probe first and then install the probe. These procedures are detailed in Chapter 2
“Local Terminal Configuration” and Chapter 3 “Installation”.
Installation and Bootp Server Configuration
This method of installation and configuration requires that you install the probe
first and then configure the probe. These procedures are detailed in Chapter 3
“Installation” and Chapter 4 “Bootp Server Configuration”.
5
Introduction
LanProbe Overview
LanProbe Overview
This section provides some general information on the
Agilent J3911A Multiport Token-Ring LanProbe.
Token-Ring LanProbe is a non-intrusive SNMP agent on the LAN that monitors
all frames and network performance. This includes current and historical traffic
statistics and snapshots of selected frames.
The following topics are covered:
z
z
z
z
z
z
z
“System Overview” below
“Supported MIBs” on page 8
“Management Stations” on page 9
“Access Security” on page 10
“Status LEDs” on page 12
“CONFIG Button” on page 14
“Included Parts” on page 14
System Overview
A typical LanProbe distributed monitoring system consists of the following:
z One or more LanProbes
z One or more NetMetrix management stations, using NetMetrix
Figure 1-2 on page 7 shows a LanProbe system example.
6
Introduction
LanProbe Overview
Figure 1-2: LanProbe System Example
7
Introduction
LanProbe Overview
Supported MIBs
LanProbe uses RMON-1 MIB standards together with private MIB extensions to
provide the following features:
MTR TR LanProbe uses the RMON MIB standard, the Token-Ring RMON
extensions, and the Agilent private MIB to provide the following features:
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
z
8
Statistics on Token-Ring Data Frames
Statistics on Token-Ring MAC Frames
History
Alarms
Host Table
Host Top N
Traffic Matrix
Filters
Frame Capture
Events
Log
Trap
Echo Test
Ring Stations
Ring Station Configuration
Source routing Statistics
Protocol Directory
Protocol Distribution
Address Map
Network Layer Host Table
Network Layer Traffic Matrix
Application Layer Host Table
Application Layer Traffic Matrix
User History
Probe Configuration
RMON Conformance
Introduction
LanProbe Overview
LanProbe implements groups 1 through 9 of RFC 1757, group 10 of RFC 1513,
and groups 11 through 20 of RFC 2021. Refer to RFC 1757 and RFC 1513 for
more information on the Remote Network Monitoring Management Information
Base (RMON-1 MIB), to RFC 2021 for information on the RMON-2 MIB, and to
RFC 2074 for information on Protocol Identifiers.
LanProbe also contains the Agilent Private MIB which allows for configuration
and administration of the probe. It provides enhanced authentication features,
specification of trap destinations, remote download of new firmware revisions,
serial line control, and other features. The Agilent Private MIB is available
electronically with NetMetrix.
You can refer to Table B-2 on page 118 for specific information on your probe’s
protocol directory.
Management Stations
Management stations gather network data collected by Agilent LanProbes. They
present this information in easy-to-use and easy-to-understand text and graphic
formats. You can use a management station to communicate with your LanProbe
after it has been installed and configured.
The LanProbe communicates with the NetMetrix software running on your
management station. NetMetrix management applications allow you to review
and reconfigure LanProbe parameters (such as IP address, trap destinations,
filters, and packet captures), to manage the information collected by LanProbe
(including statistics, historical studies, alarms, packet size distribution, and
captured packet traces), and to monitor local or remote networks (by gathering
network statistics from Agilent LanProbe agents as network monitors).
Refer to your NetMetrix documentation for more information.
9
Introduction
LanProbe Overview
Access Security
The LanProbe configuration menu allows network administrators to disable
standard RMON functions which could be considered a security risk. The security
menu allows network administrators to disable the RMON-1 packet capture
capabilities of LanProbe to prevent network users from viewing network traffic.
TFTP firmware downloads can be disabled to prevent users from downloading
earlier versions of the LanProbe firmware which did not support these new
security features. For more information, refer to “Modify/View Security Values”
on page 24 .
LanProbe’s private MIB uses a four-level access control scheme. An access level
is assigned for each community string to be used with LanProbe. The access level
is an integer value between one and four, with increasing degrees of authorization
granted for higher authorization numbers. Each higher level is granted the rights
of all lower levels in addition to the specific privileges of that level. Table 1-1
shows specific access privileges by level.
10
Introduction
LanProbe Overview
Table 1-1: Private MIB Access Security Privileges
Default
Community
Name
Level
Permissions
public
1
Read access to MIB-II objects.
rmon
2
Read access to MIB-II, RMON* MIB, and
LanProbe MIB objects, excluding the objects
in the accessControl group and in the
captureBuffer Table.
rmon_admin
3
Write access to RMON* MIB and LanProbe
MIB objects, excluding the objects in the
probeAdmin, interface, and accessControl
groups.
Read access to MIB-II, RMON* MIB
(including the captureBuffer Table), and
LanProbe MIB objects, excluding those in the
accessControl group.
agilent_admin
4
Read and write access to all MIB-II, RMON*
MIB, and LanProbe MIB objects.
* RMON implies RMON-1 and RMON-2.
11
Introduction
LanProbe Overview
Status LEDs
The status LEDs are visible on the front of LanProbe. Figure 1-3 on page 13
shows the orientation of the LEDs on the front of LanProbe.
On the back of LanProbe, there are LEDs associated specifically with each
interface and a Power LED. The 10Base-T/100Base-TX telemetry interface have
LEDs for Collision, Activity, and Link functions. The Token-Ring interfaces each
have an Activity LED. The following list describes the functions of these LEDs.
Refer to Figure 1-4 on page 13 for the orientation of the LEDs on the back of
LanProbe.
~ Line On or Power. This green LED is turned on when LanProbe is receiving
power.
Activity. This green LED is turned on when data is being received from the
network or transmitted by LanProbe. When flashing, the frequency shows the
amount of traffic. During periods of steady traffic, it may appear to stay on solid.
Fault. This yellow LED is turned on when LanProbe needs to be reset, repaired,
or replaced or when new firmware is downloaded. The Fault LED is normally on
during the power-on self-test, but turns off after a successful self-test or when a
cold or warm start is completed.
12
Introduction
LanProbe Overview
Figure 1-3: Front Panel LEDs
Figure 1-4: Back Panel LEDs
13
Introduction
LanProbe Overview
CONFIG Button
The CONFIG button is used to configure LanProbe from a terminal or to restart
the probe. The CONFIG button is recessed and located on the back of the probe
near the RS-232C connector. You will need to use a narrow, pointed object (like a
pen) to press the CONFIG button.
To configure LanProbe using a local terminal (or PC emulating a terminal),
connect a terminal to LanProbe using a null modem cable and push the CONFIG
button to display LanProbe’s Main Menu. This operation is described in Chapter 2
“Local Terminal Configuration”.
You can restart the probe (with a warm start or cold start) using the CONFIG
button. These functions are described in Chapter 5 “LanProbe Operation”.
Included Parts
The following items are included with your Agilent J3911A Multiport TokenRing LanProbe.
z Agilent J3911A Multiport Token-Ring LanProbe
z Bootp Software 3 1/2-inch Disk, for PCs
z Hardware Kit (5064-0339)
 Two Mounting Brackets for Agilent LanProbe
 Four 10-mm #M4 Mounting Screws
 Four 5/8-in #12-24 Mounting Screws
 Four Self-Adhesive rubber feet
14
Introduction
LanProbe Overview
z Power Cord, one of the following:
 Australian (8120-1369)
 Danish (8120-2957)
 European (8120-1689)
 Japanese (8120-4753)
 South Africa (8120-4600)
 Swiss (8120-2104)
 United Kingdom (8120-1351)
 United States/Canada 125 V (8120-1378)
 United States/Canada 250 V (8120-0698)
Optional Accessories
The following Agilent LanProbe accessories can be purchased from Agilent:
z Agilent J3911A Multiport Token-Ring LanProbe Installation/User’s
Guide—this manual (J3911-99501)
z Null Modem Cable—9 pin to 25 pin (24542G)
15
Introduction
LanProbe Overview
16
2
Local Terminal Configuration
Local Terminal Configuration
Local Terminal Configuration
This chapter describes how to use a local terminal to configure your Agilent
J3911A Multiport Token-Ring LanProbe so that it can communicate over a
network. You will need to configure an IP address for the 10Base-T/100Base-TX
telemetry interface port (unless you use one of the Token-Ring ports as the
telemetry port) and for all of the telemetry or Monitor/Transmit Token-Ring ports
on the probe. The default configurations are, as sent from the factory, Port 1 is the
Ethernet telemetry port and all of the Token-Ring ports are Monitor/Transmit
ports. If you plan to use the Bootp server method of configuration, then skip this
chapter and continue with Chapter 3 “Installation”.
The following sections are covered in this chapter:
z “Probe Configuration Using a Local Terminal” on page 19
z “Using a Local Terminal” on page 20
18
Local Terminal Configuration
Probe Configuration Using a Local Terminal
Probe Configuration Using a Local Terminal
Some initial configuration information must be entered into LanProbe before it
can communicate over the network interface or serial port. This initial
configuration for network communication consists of the following parameters:
z IP Address (for each Telemetry and Monitor/Transmit port)
z Default Gateway IP Address (if required) (for each Telemetry and
z
z
z
z
Monitor/Transmit port)
Subnet Mask (if required) (for each Telemetry and Monitor/Transmit port)
Ring Speed
Ring Number
Autodiscovery Echo Interval
The LanProbe uses the following configuration parameters to display time and
date information in the user interface only. LanProbe uses a separate internal clock
to time-stamp data collected from the network.
z Date
z Time
z Time Zone
The initial configuration for communication over the serial port consists of the
following parameters:
z
z
z
z
z
NOTE
Serial Port IP Address
Serial Port Subnet Mask (if required)
Serial Port Speed
Serial Port Mode
Modem Control String (if required)
If the trap destination is not set by a management station, a default trap destination
will be added. By default, traps will be sent to the first management station which
communicates via SNMP to the probe.
19
Local Terminal Configuration
Using a Local Terminal
Using a Local Terminal
You can configure LanProbe by connecting a terminal directly to LanProbe and
using LanProbe’s Main Menu. Refer to the following sections for additional
information on configuring LanProbe after you access LanProbe’s Main Menu:
z
z
z
z
z
NOTE
“Modify/View Configuration Values” on page 22
“Modify/View Security Values” on page 24
“Modify/View Interface Values” on page 25
“Display Interface Summary” on page 28
“Modify/View Serial Port Settings” on page 30
The LanProbe is not available to the network when you are in it’s configuration
menus.
Use the following procedure to access the LanProbe Main Menu:
1. Connect a terminal or a personal computer (PC) emulating a terminal to the
LanProbe’s RS-232 connector using a null modem cable. Refer to Appendix
A “Cables and Connectors”, for more information on cables.
2. Configure the terminal for 8 bits/character, 1 stop bit, no parity, Xon/Xoff
handshaking, and a baud rate of 9600.
3. Connect the power cord to the LanProbe and to a power source (either 100120/VAC or 220-240/VAC). LanProbe does not have a power switch, but is
turned on by connecting power.
4. Start the configuration by quickly pressing the CONFIG button on the back
of LanProbe one time only. After about 10 seconds, LanProbe displays its
Main Menu on the terminal. Figure 2-1 on page 21 shows LanProbe’s Main
Menu and Figure 2-2 on page 21 (Option 204 shown) shows the location of
the CONFIG button. If the Main Menu is not displayed, verify that the
previous steps in this procedure have been performed correctly.
20
Local Terminal Configuration
Using a Local Terminal
Main Menu - Revision
1. Modify/View configuration values ->
2. Modify/View security values ->
3. Modify/View interface values ->
4. Display interface summary
5. TFTP Download new firmware ->
6. XMODEM Download new firmware ->
7. Warm start and Exit
8. Cold start and Exit
Figure 2-1: LanProbe’s Main Menu
NOTE
Item 5 in Figure 2-1 is not displayed if the Allow TFTP firmware downloads
menu item is not enabled. Refer to “Modify/View Security Values” on page 24 for
more information on enabling this menu item.
If item 5 (TFTP Download new firmware) is not displayed, the number used to
access items 6, 7, and 8 will be different.
Figure 2-2: LanProbe Rear Panel
21
Local Terminal Configuration
Using a Local Terminal
NOTE
The LanProbe CONFIG button is recessed. This requires the use of a narrow,
pointed object (like a pen) to press the CONFIG button.
LanProbe executes a cold start if you press the CONFIG button twice within one
second. If this happens, wait for the cold start to be completed and press the
CONFIG button again to reenter the configuration mode.
A warm start or cold start is completed when the Fault LED goes off. If traffic is
present, the Activity LED flashes to show traffic.
Modify/View Configuration Values
Use the following procedure to configure items in the Modify/View Configuration
Values menu:
1. Press 1 to access the Modify/View configuration values menu item. The
Modify/View Configuration Values menu is displayed, as shown in Figure
2-3 on page 22.
Modify/View Configuration Values Menu - Firmware Rev
Memory configuration
x Mbytes
1. Autodiscovery Echo Interval (sec.)
1800
2. Date
3. Time
4. Time zone
Wed 05/05/97
09:12:00
PST8PDT
S. Save changes and exit
0. Cancel changes and exit
Figure 2-3: Modify/View Configuration Values Menu
2. Select each field requiring configuration (one at a time) by pressing its
corresponding number and then entering the values that are appropriate for
your network.
22
Local Terminal Configuration
Using a Local Terminal
Autodiscovery
Echo Interval
Press 1 and enter the autodiscovery echo interval, in
seconds, as desired for your probe (optional). This parameter
sets the time interval for the probe to transmit an
autodiscovery frame, which is used by HP OpenView
NetMetrix to maintain its network map.
The default value is 30 minutes (1800 seconds). A value of
zero results in no transmission of autodiscovery frames.
Date
Press 2 and enter the day of the week and then the date in
month/day/year format (mm/dd/yy, through 1999 or
mm/dd/yyyy, starting 2000).
Time
Press 3 and enter the time of day in hours, minutes, seconds
(hh:mm:ss) format.
Time Zone
Press 4 and enter your time zone in one to 15 characters
(optional).
The Time Zone characters are stored for your convenience
and are used only to time-stamp probe information.
Recommended practice is to use the format of Time Zone,
hours from Greenwich mean time, and then Daylight Saving
Time, such as PST8PDT for Pacific Standard Time (the
default). The probe does not automatically update the Time
field when your local time changes from standard time to
daylight savings and back.
The values you enter for date and time take effect as soon as you enter them.
All other parameters do not take effect until you select the Save Changes
and Exit menu item.
3. Press S to save the configuration changes and return to LanProbe’s Main
Menu. If you want to cancel your current changes and return to the
LanProbe’s Main Menu, press 0.
23
Local Terminal Configuration
Using a Local Terminal
NOTE
The other Main Menu items are explained in other chapters of this manual. The
TFTP Download new firmware and XMODEM Download new firmware
menu item is described in “Download New Firmware”. The Warm start and Exit
and Cold start and Exit menu items are explained in Chapter 5 “LanProbe
Operation”.
Modify/View Security Values
Use the following procedure to configure items in the Modify/View Security
Values menu:
1. If you want to restrict access to the probe press 2 to access the Modify/View
security values menu item, otherwise skip this section. The Modify/View
Security Values menu is displayed, as shown in Figure 2-4 on page 24.
Modify/View Security Values Menu - Firmware Rev
1. Allow packet capture
2. Allow TFTP firmware downloads
Yes
Yes
S. Save changes and exit
0. Cancel changes and exit
Figure 2-4: Modify/View Security Values Menu
2. Select each field requiring configuration (one at a time) by pressing its
corresponding number and then entering the values that are appropriate for
your network. Refer to “Access Security” on page 10 for more information
on security.
Allow Packet
Capture
Press 1 and enter Yes to allow or enter No to not allow
packet capture.
Allow TFTP
Press 2 and enter Yes to allow or enter No to not allow
24
Local Terminal Configuration
Using a Local Terminal
Firmware Downloads
TFTP firmware downloading.
3. Press S to save the configuration changes and return to LanProbe’s Main
Menu. If you want to cancel your current changes and return to the
LanProbe’s Main Menu, press 0.
Modify/View Interface Values
After you access the Modify/View Interface Values menu, you must first select the
port that you want to configure and then configure that port. For example, the
possible options for the port parameter could be the following:
z
z
z
z
z
z
z
z
[1] 1.1/Ethernet
[2] 1.2/Serial
[3] 2.1/Token_Ring
[4] 2.2/Token_Ring
[5] 3.1/Token_Ring
[6] 3.2/Token_Ring
[7] 4.1/Token_Ring
[8] 4.2/Token_Ring
Use the following procedure to configure items in the Modify/View Interface
Values menu:
1. Press 3 to access the Modify/View interface values menu item. The
Modify/View Interface Values menu is displayed, as shown in Figure 2-5 on
page 26.
25
Local Terminal Configuration
Using a Local Terminal
Modify/View Interface Values Menu - Firmware Rev
MAC Address
Interface Type
00 00 C6 XX XX XX
Token Ring
1.
2.
3.
4.
5.
2.1/Token_Ring
Telemetry
0.0.0.0
0.0.0.0
255.0.0.0
Port
Port Type
IP address
Default gateway IP address
Subnet mask
6. Token-Ring Speed (Mbps)
7. Ring Number
16
-1
S. Save changes and exit
0. Cancel changes and exit
Figure 2-5: Modify/View Interface Values Menu
2. Select each field requiring configuration (one at a time) by pressing its
corresponding number and then entering the values that are appropriate for
your network.
Port
26
Press 1 and enter the port number to be configured. Refer to
“Display Interface Summary” on page 28 for interface
summary information. After you enter a port number, the
configuration parameters are shown along with their current
Local Terminal Configuration
Using a Local Terminal
settings for the specified port number. You can then view or
configure the port’s parameters. The following are your port
choices:
z[1] 1.1/Ethernet
z[2] 1.2/Serial
z[3] 2.1/Token_Ring
z[4] 2.2/Token_Ring
z[5] 3.1/Token_Ring
z[6] 3.2/Token_Ring
z[7] 4.1/Token_Ring
z[8] 4.2/Token_Ring
Refer to “Modify/View Serial Port Settings” on page 30 for
information on configuring the Serial Port settings.
Port Type
Press 2 and select the port type as Telemetry, Monitor/
Transmit, or Monitor-only.
The telemetry port does not maintain network statistics for its
network. The telemetry interface only allows the retrieval of
network statistics from the non-telemetry ports. Port 1 is the
telemetry port by default and LanProbe must be configured
with exactly one telemetry port.
The Telemetry port only receives packets destined for its IP
address, can transmit packets onto the network, and is used
for SNMP communications to the probe. It requires the IP
Address, Subnet Mask, and Default Gateway IP Address
fields. The following apply to Telemetry ports:
zHP OpenView can discover the interface
zThe interface is IP addressable
zThe interface responds to RMON-1
zThe interface will transmit all traps from the probe
zThe interface will transmit all extended RMON packets
sample from Monitor-only ports, Monitor/Transmit ports.
27
Local Terminal Configuration
Using a Local Terminal
IP Address
Press 3 and enter the IP address for the probe. If the IP
address is 0.0.0.0, LanProbe will transmit Bootp Requests
for configuration information (including IP address) over the
network.
Default Gateway
IP Address
Press 4 and enter the default gateway IP address for the probe
(optional).
Subnet Mask
Press 5 and enter the subnet mask for the probe.
Token-Ring
Speed
Press 6 to modify or view the network speed setting.
The default configuration is set to 16Mbps network speed.
You can enter values of 4 or 16 for 4Mbps or 16Mbps
respectively.
Ring Number
Press 7 and enter the local ring number (in Decimal) for your
network. Set to -1 for use with ring parameter servers for
automatic setting of the ring number, and set to <x> to
explicitly set the ring number, where x is the ring number in
decimal.
Parameters do not take effect until you select the Save Changes and Exit
menu item.
3. Press S to save the configuration changes and return to LanProbe’s Main
Menu. If you want to cancel your current changes and return to the
LanProbe’s Main Menu, press 0.
Display Interface Summary
Use the following procedure to view the Display Interface Summary screen for
your LanProbe. Refer to Figure 2-6 on page 29.
1. Press 4, the Display Interface Summary item. The Display Interface
Summary item displays the number and type of each interface, the port type,
and each port’s IP address.
28
Local Terminal Configuration
Using a Local Terminal
2. Press Enter to continue.
3. From LanProbe’s Main Menu, press 7 to execute a warm start or press 8 to
execute a cold start. A cold start is required if you change the IP Address,
Default Gateway or Subnet Mask. For either menu choice, LanProbe exits
the Main Menu and restarts normal operations.
NOTE
A warm start resets all data collected by the probe. A cold start resets all data
collected by the probe and also resets any user-configuration information, such as
history studies, filters, and alarms to their default values. Refer to Chapter 5
“LanProbe Operation” for more information on what is reset by warm and cold
starts.
After the probe restarts (boots), it operates normally using the new
configuration information. The warm start or cold start occurs immediately
and there is no visual indication of when it finishes.
4. If you are performing the initial probe configuration, prepare LanProbe for
installation by disconnecting the power cord. You will not lose your initial
configuration information.
Display Interface Summary
Interface
-----------1.1/Ethernet
1.2/Serial
2.1/Token_Ring
2.2/Token_Ring
3.1/Token_Ring
3.2/Token_Ring
4.1/Token_Ring
4.2/Token_Ring
Port Type
---------Monitor/Transmit
Not Applicable
Telemetry
Monitor/Transmit
Monitor/Transmit
Monitor/Transmit
Monitor/Transmit
Monitor/Transmit
IP Address
----------15.6.72.216
0.0.0.0
15.6.72.216
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Figure 2-6: Display Interface Summary
29
Local Terminal Configuration
Using a Local Terminal
Modify/View Serial Port Settings
You can view or modify LanProbe’s serial port settings by entering the Serial Port
number (port 2) into the Modify/View Interface Values Menu’s Port parameter.
The Serial Port configuration parameters are then shown along with their current
settings. Use the following procedure to configure LanProbe’s serial port:
1. Enter the LanProbe’s Serial Port number (port 2) into the Modify/View
Interface Values Menu’s Port parameter as shown in Figure 2-5 on page 26.
Modify/View Interface Values Menu - Firmware Rev
Interface Type
Serial
1.
2.
3.
4.
1.2/Serial
Not Applicable
0.0.0.0
255.255.252.192
Port
Port Type
Serial port IP address
Serial port subnet mask
5. Serial port speed
6. Serial port mode
7. Serial port hardware flow control
8. Modem Init String
9. Modem Hangup String
10. Modem Connect Responses
11. Modem No-Connect Responses
9600
Direct
On
^s^M^d1^sATE0Q0V1X4 S0=1...
^d2^s+++^d2^sATH0^M^d2
/CONNECT/300/CONNECT/1200/...
/NO CARRIER/BUSY/NO DIALT...
S. Save Changes and Exit
0. Cancel Changes and Exit
Figure 2-7: Modify/View Serial Port Settings Menu
2. Select each field requiring configuration (one at a time) by selecting its
corresponding number as shown in Figure 2-7 and then entering the values
that are appropriate for your modem’s serial port.
30
Local Terminal Configuration
Using a Local Terminal
Serial port IP address
Press 3 and then enter the serial port IP address for the
probe. The default Serial Port IP Address is 0.0.0.0.
Serial port
subnet mask
Press 4 and then enter the serial port subnet mask for
the probe (optional). It is recommended that you do not
change the serial port subnet mask unless there is a
conflict. The default Serial Port Subnet Mask is
255.255.255.192.
Serial port speed
Press 5 and then enter a serial port speed (300 to 38,400
baud) for LanProbe’s SNMP connection. The default is
9600 baud. This speed is used only for Out-of-Band
access to LanProbe using SNMP. It does not affect the
serial connection for the local terminal, which is fixed at
9600 baud.
Make sure that the serial port speed is set to less than or
equal to the maximum speed of the modem to be used.
Serial port mode
Press 6 and then select the serial port mode by pressing 1
for direct connection (the default) or 2 for modem
connection.
Serial port hardware
flow control
Press 7 and then select hardware flow control Off by
pressing 1 or hardware flow control On (the default) by
pressing 2.
Modem Init String
Press 8 to enter the modem initialization string. Only the
first 20 characters of the 256 character maximum will be
displayed in the Modify/View Serial Port Settings menu.
The default is ^s^M^d1^sATEOQOV1X4 S0=1
S2=43^M.
Modem Hangup
String
Press 9 to enter the modem hang-up string. Only the
first 20 characters of the 256 character maximum will be
displayed in the Modify/View Serial Port Settings menu.
The default is ^d2^s+++^d2^sATHO^M^d2.
31
Local Terminal Configuration
Using a Local Terminal
Modem Connect
Responses
Press 10 to enter the modem connect responses. Only
the first 20 characters of the 256 character maximum will
be displayed in the Modify/View Serial Port Settings
menu. The default is /CONNECT/300/CONNECT
1200/1200/CONNECT 2400/2400/CONNECT
4800/4800/CONNECT 9600/9600/CONNECT
14400/14400/CONNECT 19200/19200/
CONNECT 38400/38400/.
Modem No-Connect
Responses
Press 11 to enter the modem no-connect responses.
Only the first 20 characters of the 256 character
maximum will be displayed in the Modify/View Serial
Port Settings menu. The default is /NO CARRIER/
BUSY/NO DIALTONE/NO ANSWER/ERROR/.
3. Press S to save the serial port configuration changes and return to
LanProbe’s Main Menu. If you want to cancel these changes and return to
LanProbe’s Main Menu, press 0.
If you need to configure any other LanProbe parameters, make your selection
from LanProbe’s Main Menu.
32
3
Installation
Installation
Installation
This chapter describes how to install the Agilent J3911A Multiport Token-Ring
LanProbe. Installing the Agilent LanProbe consists of the following tasks:
z
z
z
z
z
“Selecting a Location” on page 35
“Installing the Probe” on page 36
“Connecting the Probe” on page 41
“Starting the Probe” on page 56
“Verifying the Installation” on page 57
If you plan to configure the probe from a local terminal and have not yet done so,
go to Chapter 2 “Local Terminal Configuration”, and perform the configuration
now.
34
Installation
Selecting a Location
Selecting a Location
Select a location for your LanProbe where it will be the most useful. The
LanProbe can only monitor traffic that is present on the LAN where it is attached.
Since interconnect devices (bridges, for example) filter traffic, a LanProbe may
need to be attached on each side of an interconnect device for complete collection
of network statistics. In this respect, the placement of LanProbe affects the
statistics collected.
Consider the following installation requirements when selecting a location for
your probe:
z A flat surface that is large enough to support the probe (requires clearance at
rear and sides for cooling and rear panel access), adequate wall space, or
double high space in a 19 inch rack or cabinet.
z A grounded power outlet (either 100-120/VAC or 220-240/VAC).
z Access to a Token-Ring network MsAU connection.
z Access to an RS-232C connection (required only for Out-of-Band
communication).
z Access to a phone line and a modem within 50 feet (required only for Outof-Band communication using a modem connection).
NOTE
The MAC addresses for the probe can be found on the rear panel. It is a good idea
to make a note of the interface and its address prior to installing your LanProbe
because some installation methods make it difficult to see the rear panel without
removing the probe.
35
Installation
Installing the Probe
Installing the Probe
This section describes how to install your LanProbe. First decide which
installation method you are going to use and then install the probe using one of the
following methods:
z “Table Installation” on page 37
z “Rack or Cabinet Installation” on page 37
z “Wall Installation” on page 39
CAUTION
Do not attach the power cord to the LanProbe until the probe is completely
installed. If the power cord is already attached to LanProbe, remove it now (you
will not lose any configuration parameters). The probe does not have a power
switch but becomes operational when the power is attached.
36
Installation
Installing the Probe
Table Installation
Use the following procedure to install LanProbe on a table:
1. Attach the self-adhesive rubber feet to the bottom of the probe as marked in
each corner.
2. Place the probe on a flat surface (refer to the requirements as listed in
“Selecting a Location” on page 35).
Rack or Cabinet Installation
You can install LanProbe in a rack or cabinet with either the front or rear panel
facing out. You may want the rear panel facing out so that you can see the status
LEDs for each port. (The front panel Activity LED indicates when any of the
individual port LEDs are lit.)
Make sure you have screws that fit your rack (or cabinet) before installing the
probe as noted in Step 3 below.
Use the following procedure to install LanProbe in a rack or cabinet:
1. Attach the installation brackets to the probe with the 10-mm #M4 screws
(included), using a POZIDRIV #2 or cross-head screwdriver as shown in
Figure 3-1 on page 38.
2. Position the probe in the rack (or cabinet) and slide it up or down until the
rack holes line up with the holes in the brackets.
3. Attach the probe to the rack with the 5/8-in. #12-24 screws (included). Some
cabinets require 5/8-in. #10-32 screws (available as Agilent part number
2680-0302) instead of the 5/8-in. #12-24 screws.
Figure 3-1 on page 38 shows a rack or cabinet installation.
37
Installation
Installing the Probe
Figure 3-1: Install the Probe in a Rack or Cabinet
38
Installation
Installing the Probe
Wall Installation
Use the following procedure to install LanProbe on a wall:
1. Attach the installation brackets to the probe with the 10-mm #M4 screws
(included), using a POZIDRIV #2 or cross-head screwdriver as shown in
Figure 3-2 on page 40.
2. Attach the probe to a wood surface (minimum 1/2-in. plywood or
equivalent) on a wall with 5/8-in. #12 wood screws or equivalent (not
included).
Figure 3-2 on page 40 shows a wall installation.
39
Installation
Installing the Probe
Figure 3-2: Install LanProbe on a Wall
40
Installation
Connecting the Probe
Connecting the Probe
LanProbe communicates with NetMetrix either through Out-of-Band connections
using the 10Base-T/100Base-TX or Token-Ring telemetry interfaces or by using a
serial connection. You can connect up to four or six Token-Ring networks
depending on the number of Token-Ring interfaces installed in the probe.
You can establish both telemetry and serial Out-of-Band connections to give you
the option of communicating with the probe either over the telemetry network or
over the serial link, respectively. The telemetry connection has the advantage of
being faster than the serial connection. The disadvantage of using only the
telemetry connection is that certain network or component failures can result in a
loss of communications with the probe.
The Out-of-Band serial connection can be used as the primary means of
communication or as a backup link in case of a failure on your telemetry network.
The disadvantage of using only the serial connection is that it is a slower means of
communications.
Refer to one of the following sections in this chapter for specific information on
connecting the probe:
z “Connecting to the Network (Out-of-Band)” on page 41
z “Connecting to Token-Ring Networks” on page 45
z “Connecting Out-of-Band” on page 48
Connecting to the Network (Out-of-Band)
You can connect the probe to an Out-of-Band telemetry network as described in
one of the following topics. Figure 3-3 shows the rear panel of the probe and
Figure 3-4 on page 42 shows the details of the Multiport Token-Ring Interface.
z “Connecting to 10MB/s Ethernet Networks (Telemetry)” on page 42
z “Connecting to 10Base-T/100Base-TX Networks (Telemetry)” on page 44
z “Connecting to Token-Ring Networks (Telemetry)” on page 45
41
Installation
Connecting the Probe
CAUTION
Do not touch the probe connector pins or the cable connector pins. Static
discharge may damage equipment.
Figure 3-3: The Probe’s Rear Panel
Figure 3-4: Close-up of a Token-Ring Interface
Connecting to 10MB/s Ethernet Networks (Telemetry)
You can connect the probe to the network either by connecting the RJ-45
connector to a 10Base-T/100Base-TX half-duplex network or by connecting the
AUI connector to a 10MB/s Ethernet network. Use the following procedures to
connect the probe’s AUI connector to a 10MB/s Ethernet network for telemetry
communications. Never use both the AUI and RJ-45 connectors.
42
Installation
Connecting the Probe
1. Connect the probe’s AUI port, located on the rear panel, to the network with
an AUI cable. Figure 3-5 on page 43 shows how to connect the probe to a
10MB/s Ethernet network.
2. Select AUI as the Physical Connector parameter from the Modify/View
Interface Values menu. Refer to Step 1 on page 25 for information on
configuring the Physical Connector parameter.
Figure 3-5: Connecting the Probe to a 10MB/s Ethernet Network
The following types of network-specific MAUs are available for connecting to the
AUI port:
z 10Base-T MAU (Agilent 28685B) - IEEE 10Base-T for twisted-pair cabling
z Fiber-Optic MAU (Agilent 28683A) - for fiber-optic cabling
z 10Base-2 MAU (Agilent 28641B) - for ThinLAN cabling
NOTE
If the SQE test is available on the MAU, disable it.
43
Installation
Connecting the Probe
Connecting to 10Base-T/100Base-TX Networks (Telemetry)
You can connect the probe to the network either by connecting the RJ-45
connector to a 10Base-T/100Base-TX half-duplex network or by connecting the
AUI connector to a 10MB/s Ethernet network. The 100Base-TX Fast Ethernet
interface can function on a full-duplex network link but it will record RMON
information only for traffic monitored on the receive wires.
Use the following procedures to connect the probe’s RJ-45 connector to a 10MB/s
or 100MB/s Ethernet network for telemetry communications. Never use both the
AUI and RJ-45 connectors.
1. Connect the probe’s 10Base-T/100Base-TX (RJ-45) port, located on the rear
panel, to the network using a category 5 cable. Figure 3-6 on page 45 shows
how to connect the probe to a 10Base-T or 100Base-TX network.
2. Select RJ-45 as the Physical Connector parameter from the Modify/View
Interface Values menu. Refer to Step 1 on page 25 for information on
configuring the Physical Connector parameter.
3. If you are connecting to a device that supports the auto-negotiation protocol,
select Auto Negotiate for the Link Speed parameter from the Modify/View
Interface Values menu. Otherwise, select 10MB/s (for 10MB/s Ethernet) or
100MB/s (for 100MB/s Ethernet). Refer to Step 1 on page 25 for
information on configuring the Link Speed parameter.
The probe will automatically negotiate the speed of the interface if the Link
Speed parameter is set to Auto Negotiate and if the connected device
supports the auto-negotiation protocol.
4. If you selected 10MB/s or 100MB/s for the Link Speed parameter, you must
also select Half-Duplex for the Full/Half Duplex parameter from the
Modify/View Interface Values menu. Refer to Step 1 on page 25 for
information on configuring the Full/Half Duplex parameter.
44
Installation
Connecting the Probe
Figure 3-6: Connecting the Probe to a 10Base-T/100Base-T Network
Connecting to Token-Ring Networks (Telemetry)
You connect to Token-Ring networks for telemetry in the same way as you do to
monitor the network. Refer to “Connecting to Token-Ring Networks” below, for
information on making a telemetry connection to a Token-Ring network.
Connecting to Token-Ring Networks
Use the information in this section to connect the probe for telemetry or
monitoring Token-Ring networks.
CAUTION
Connecting the Token-Ring interface to your network while configured to the
wrong network speed (4Mb/16Mb) can cause disruption of all traffic on your
network and it will prevent the probe from properly inserting into the ring.
You can configure the Token-Ring Speed from the Modify/View Configuration
Values Menu. The probe is configured with a default setting for 16Mbps
networks. Refer to Chapter 2 “Local Terminal Configuration” for information on
the probe’s menus.
45
Installation
Connecting the Probe
You connect the Token-Ring interface to your network by using the appropriate
cables. The probe has both RJ-45 and DB-9 connectors on the rear panel for
connecting to Token-Ring networks. Figure 3-7 on page 46 shows the back panel
with the Token-Ring option installed.
NOTE
Do not attach cables to both the Token-Ring DB-9 and RJ-45 connectors
simultaneously. This causes the probe to malfunction, and can disrupt your
network. You must use only one network connector at a time for correct probe
operation.
CAUTION
The Token-Ring interface is not compatible with Token-Ring expansion modules
(Local Ringhub from Madge and other vendors, for example) which require
power from the Token-Ring interface. The Token-Ring interface must be
connected directly to the MsAU.
Token-Ring networks typically use Type 3 (Unshielded Twisted Pair (UTP)) cable
or Type 1 (Shielded Twisted Pair (STP)) cable. Networks using UTP cable
typically use the RJ-45 type connectors and networks using STP cable typically
use Token-Ring Data Connectors or DB-9 type connectors.
If your network uses RJ-45 connectors, you will need the standard cable with
RJ-45 connectors on both ends to connect the probe to the ring. Connect one end
of this cable to any open port of a Media Station Access Unit (MsAU) and connect
the other end to the RJ-45 connector on the probe. Figure 3-7 on page 46 shows
the Token-Ring interface connected to a Type 3 MsAU.
Figure 3-7: Connecting the Probe using RJ-45 Connectors
46
Installation
Connecting the Probe
NOTE
Do not connect the probe to either the ring-in (RI) or ring-out (RO) connection
port.
The Token-Ring interface can also be connected to a Type 3 MsAU using a Media
Filter. The Media Filter is used to connect from STP (DB-9) to UTP (RJ-45).
Figure 3-8 shows the Token-Ring interface connected to a MsAU using a Media
Filter.
Figure 3-8: Connecting the Probe using a Media Filter
If your network uses the Token-Ring Data Connectors, you need a Type 1 cable
with a Token-Ring Data Connector on one end and a DB-9 connector on the other
end to connect the probe to the ring. Connect the Token-Ring Data Connector plug
to any open port (excluding the RI or RO ports) of a MsAU and connect the DB-9
connector to the probe’s DB-9 connector. Figure 3-9 shows the Token-Ring
interface connected to a Type 1 MsAU using Token-Ring Data and DB-9
connectors.
47
Installation
Connecting the Probe
Figure 3-9: Connecting the Probe using Data & DB-9 Connectors
CAUTION
Do not touch the probe connector pins or the cable connector pins. Static
discharge may damage equipment.
Connecting Out-of-Band
Out-of-Band communications with LanProbe are conducted through the serial
port, not over the network. This mode of communications is optional.
The following methods are available for Out-of-Band connections:
z “Direct Connection” on page 48
z “Modem Connection” on page 49
z “Data Switch Connection” on page 53
Direct Connection
To make a direct connection to LanProbe, connect the NetMetrix management
station’s serial port to LanProbe’s RS-232C port using a null modem cable
(Agilent part number 24542G—9-to-25 pin, or equivalent). Figure 3-10 shows the
direct connection to the probe.
48
Installation
Connecting the Probe
Figure 3-10: LanProbe Direct Connection
Modem Connection
You can use a modem connection to increase the distance between the probe and
the NetMetrix management station. Perform the following tasks to make a modem
connection between a NetMetrix management station and LanProbe. Figure 3-11
on page 49 shows the modem connection to the probe.
z “Install the Management Station Modem” on page 50
z “Install the LanProbe Modem” on page 50
z “Configure the Management Station and LanProbe” on page 51
Figure 3-11: LanProbe Modem Connection
49
Installation
Connecting the Probe
Install the Management Station Modem
You need the following list of equipment to install the management station’s
modem:
z Hayes-compatible 300 to 38.4 K baud modem
z RS-232C (straight through) modem cable
z Modular phone cable with RJ-11 connectors or equivalent
Use the following procedure to install the management station’s modem:
CAUTION
Turn off all equipment prior to making cable connections.
1. Place the modem close enough to the management station to not violate the
50-foot RS-232C distance limitation.
2. Connect the RS-232C cable from the modem’s RS-232C port to the
management station’s serial port. Take care in selecting the appropriate
serial port on the management station (COM1 or COM2, for example).
3. Connect the RJ-11 modular phone cable from the modem To Line port to
the telephone jack.
4. Connect power to the modem and turn on the modem power switch (not
required for a PC internal modem).
5. Perform any other instructions as required by the modem manufacturer. If
you have any problems with the modem, contact the modem manufacturer
for assistance.
Install the LanProbe Modem
You need the following list of equipment to install the LanProbe modem:
z Hayes-compatible 300 to 38.4 K baud modem
z RS-232C (straight through) modem cable
z Modular phone cable with RJ-11 connectors or equivalent
Use the following procedure to install the LanProbe modem:
50
Installation
Connecting the Probe
1. Place the modem close enough to the probe to not violate the 50-foot
RS-232C distance limitation.
2. Connect an RS-232C cable from the modem’s RS-232C port to the
LanProbe’s RS-232 port. A null modem cable cannot be used for this
connection.
3. Connect the RJ-11 modular phone cable from the modem To Line port to
the telephone jack.
4. Connect power to the modem and place the modem power switch to on.
5. Perform any other instructions as required by the modem manufacturer. If
you have any problems with the modem, contact the modem manufacturer
for assistance.
Configure the Management Station and LanProbe
Refer to your NetMetrix documentation for information on configuring the
management station for use with a modem. Verify that the packet retransmission
timeout is set appropriately. For example, a 1500-byte SNMP packet requires
about one second to transmit over a 9600 baud connection, with another one
second for the reply. A packet retransmission timeout of three to five seconds is
appropriate for this example.
The LanProbe can be configured for Serial Line Internet Protocol (SLIP) link
communications either by using a local terminal through the serial port or by
using a NetMetrix management station over the network.
If you use the network to configure LanProbe, make the network connection (refer
to “Connecting to the Network (Out-of-Band)” on page 41) and then refer to your
NetMetrix documentation to configure the following LanProbe parameters:
z
z
z
z
z
Serial Port IP Address
Serial Port Subnet Mask
Serial Port Speed
Hardware Flow Control (if unsure, consult your modem’s documentation)
Modem Init String
51
Installation
Connecting the Probe
If you use an ASCII terminal to configure LanProbe as described in Chapter 2
“Local Terminal Configuration”, attach the terminal and configure the following
LanProbe parameters:
z
z
z
z
z
Serial Port IP Address
Serial Port Subnet Mask
Serial Port Speed
Hardware Flow Control (if unsure, ask your local network administrator)
Modem Init String
The Serial Port IP Address must be on the same IP subnet as the management
station’s serial IP address.
Normally, each company has one subnet mask that is used for all machines on
their network. Enter this subnet mask value into the Serial Port Subnet Mask
field. The Serial Subnet Mask used for the probe should match the subnet mask
used for the SLIP port on the management station.
Set the Serial Port Speed to a value that is less than or equal to the maximum
speed at which your modem can operate.
Set the Hardware Flow Control to Off (On is the default), unless you are using
high speed modems (14.4K baud or faster) with advanced features, such as error
correction and data compression. If the Hardware Flow Control is set to On, you
can set it to Off by using LanProbe’s menu or over the network from a NetMetrix
management station (refer to your NetMetrix documentation for details).
Verify that the Modem Init String is properly initialized for the attached modem
by referencing the modem’s documentation. The probe’s default modem
initialization string is configured to work with low-speed and medium-speed
Hayes compatible modems. The following modem settings are recommended for
low-speed to medium-speed modem connections:
Modem Flow Control:
Data Compression (if applicable):
Error Correction (if applicable):
52
Off
Off
Off
Installation
Connecting the Probe
Not all Hayes commands are the same for all Hayes-compatible modems. Refer
to your modem’s documentation to determine the commands required for each of
the above settings and append these commands to the end of the default Modem
Init String.
NOTE
Your modem’s documentation discusses the features that are relevant to your
modem. If your modem does not support a feature (data compression, for
example), you do not need to turn it off in the Modem Init String.
Some modems require you to set register values explicitly, rather than sending
Hayes style commands. In this case, follow your modem’s documentation to set
these registers.
If you are using a high-speed modem, you probably need to modify the default
modem initialization string. The following modem settings are recommended for
high-speed modem connections:
Modem Flow Control:
Carrier Detect:
Data Compression:
Error Correction:
Hardware Flow Control (RTS/CTS signaling)
Always On
Enabled
Enabled
After appending the appropriate commands to the modem initialization string,
warm start your LanProbe.
Refer to your NetMetrix documentation for information on how to establish
communications with LanProbe over the SLIP link.
Data Switch Connection
Use the data switch connection to provide the flexibility of using more than one
management station to communicate with more than one LanProbe.
To make a data switch connection to LanProbe, connect a NetMetrix management
station to LanProbe’s RS-232C port through a data switch. Set the Serial Port
Mode to Direct, if your probe is directly connected to the data switch, or set it to
Modem, if your probe must dial through a modem to another modem that is
attached to the data switch.
53
Installation
Connecting the Probe
To allow traps to be sent from the probe to your management station, specify a
Serial Trap Destination of type Switch or Modem Switch, using NetMetrix.
Refer to your data switch documentation for information on setting up your data
switch. There are many variations available for this connection method. Figure 312 on page 55 shows a possible data switch connection scheme.
54
Installation
Connecting the Probe
Figure 3-12: LanProbe Data Switch Connection
55
Installation
Starting the Probe
Starting the Probe
NOTE
If you are using the Bootp server method of configuration, do not attach the power
cord to the probe until told to do so in Chapter 4 “Bootp Server Configuration”.
If you used the local terminal method of configuration, attach the power cord to
LanProbe. The probe does not have a power switch, but is powered on when
power is attached. When powered on or reset, LanProbe runs self-tests and
transmits ICMP echo frames to the default gateway for the purpose of allowing
the probe to be discovered by the routers (ARP cache). The probe transmits four
ICMP echo request packets about 10 seconds after booting and again every
autodiscovery echo interval. Refer to Chapter 5 “LanProbe Operation” for more
information on resetting the probe.
56
Installation
Verifying the Installation
Verifying the Installation
You can verify the LanProbe installation by looking at the status LEDs on the
front or back of the probe. LEDs on the back of LanProbe show the status of each
port. After LanProbe restarts (boots), it runs a power-on self-test (POST) and then
starts normal operations.
The Fault LED is briefly turned on (about three seconds) during the POST. After
LanProbe passes the POST, the Fault LED turns off. The Activity LED flashes
during network activity. The ~Line On or Power LED should be on to indicate that
power is applied to the probe.
After LanProbe has passed its self-tests, look at the status LEDs to verify your
installation. The status LEDs should be in the following states:
LED
Activity
State
Flashing, if connected to a network with traffic, or may
appear to stay on solid during periods of steady traffic.
~ Line On or Power
On solid
Fault
Off
You can use NetMetrix to verify that LanProbe can be reached (refer to your
NetMetrix documentation).
57
Installation
Verifying the Installation
Troubleshooting the Installation
If the Activity LED is off, verify that LanProbe is properly connected to the
network and that there is traffic on the network. You can look at each port’s
Activity LED to see if there is traffic on any port.
If the ~ Line On or Power LED is off, verify that power is properly connected to
LanProbe and to the correct power source.
If the Fault LED is on, the probe failed the self-test. Repeat the installation
procedures and verification of installation.
If you are still having difficulty, call your local Agilent service representative.
58
4
Bootp Server Configuration
Bootp Server Configuration
Bootp Server Configuration
This chapter describes how to use the Bootp server method to configure the
Agilent J3911A Multiport Token-Ring LanProbe so that it can communicate over
the network. This chapter assumes that you have already installed LanProbe, but
have not attached the power cord.. If you plan to use the local terminal method of
configuration, skip this chapter and refer to Chapter 2 “Local Terminal
Configuration”.
The following sections are covered in this chapter:
z
z
z
z
60
“Probe Configuration Using a Bootp Server” on page 61
“Bootp Server Setup on an HP or Sun System” on page 63
“Bootp Server Setup on a PC” on page 67
“Configuring the Bootptab File” on page 73
Bootp Server Configuration
Probe Configuration Using a Bootp Server
Probe Configuration Using a Bootp Server
You can use a Bootstrap Protocol (Bootp*) server to load LanProbe’s IP
configuration. This method requires that a Bootp server maintains a file
containing client configuration information, maps from MAC addresses to IP
addresses, and responds to requests from clients. You can configure the probe
from an HP-UX, Solaris, or MS-DOS system acting as a Bootp server. The system
that is operating as the Bootp server must be connected to your network. Table 4-1
on page 62 shows the minimum requirements for a Bootp server operating on HP
9000, Sun SPARC, and PC systems.
Before you can use the Bootp server, you must edit the bootptab file to configure
the required LanProbe parameters. Refer to “Configuring the Bootptab File” on
page 73 for more information.
LanProbe’s MAC address is twelve characters long and is printed on a tag on the
back of the probe. You must determine the IP Address, Default Gateway IP
Address, and Subnet Mask from the network.
To allow LanProbe to use a Bootp server that is not on the same subnet, the router
involved must support Bootp Relay (the transfer of a Bootp request). For example,
if you have multiple LanProbes that you want to configure from a single Bootp
server, be sure that the routers in the path between your Bootp server and the
LanProbes support Bootp Relay. Otherwise, you will need to operate the Bootp
server on the same subnet as your LanProbes. You can configure multiple
LanProbes on one subnet and then place them on their respective segments.
NOTE
If there is a router on your network between the probe and the management
station, you must configure the router to forward bootp packets.
Bootp requests
are not properly forwarded by the IBM 8209 bridge product, when
used between Ethernet and Token-Ring.
*BOOTP, RFC 951, RFC 1084 phase I only
61
Bootp Server Configuration
Probe Configuration Using a Bootp Server
Table 4-1: Minimum Requirements for a Bootp Server
Bootp Server type
Item
HP
Sun
PC
Model or Processor
HP 9000
Model 700
or 800
Sun SPARC Model
1, 1+, 2, IPC, 5, 10,
20
286 or above
Operating System
HP-UX 9.x
or later
Solaris 2.1 or later
DOS 3.0 or later
Network Operating
System/Subsystem
ARPA
Berkeley
Services
Sun Networking
Services (Ethernet
and TCP/IP)
Microsoft LAN Manager
1.0 or later
-orNovell NetWare
environment, including
LSL.COM v1.2,
IPXODI.COM v1.2,
NETX.COM v3.1
or later
Floppy Drive
Not
Applicable
Not Applicable
3.5" Floppy Disk Drive
System Memory
Not
Applicable
Not Applicable
10KB of free memory to
run the installation
process. 100 KB of free
memory to run
BOOTPD.
62
Bootp Server Configuration
Bootp Server Setup on an HP or Sun System
Bootp Server Setup on an HP or Sun System
If your Bootp server is an HP-UX or Solaris system, use the following instructions
to configure LanProbe:
1. Determine the IP address for each Telemetry and Monitor/Transmit port to
be used for LanProbe.
2. Determine the name for each Telemetry and Monitor/Transmit port to be
used as LanProbe’s Domain Name Services (refer to the HP ARPA Services
manual) or configure an IP address and name for each Telemetry port for
LanProbe in your local /etc/hosts file.
3. Make sure that the Bootp server can communicate with LanProbe (if they
are separated by a router, the router must support Bootp Relay).
4. From the Bootp server, edit the client configuration file and enter the
following parameters for the Telemetry port and Monitor/Transmit ports (if
any) to be used for LanProbe (do not specify any other parameters):
zMAC Address
zIP Address
zDefault Gateway IP Address (if available)
zSubnet Mask
NOTE
The Bootp server must support the vendor specific subnet mask field and the
default gateway field.
5. Start the Bootp daemon as described in “Starting the Bootp Server on an HP
or Sun System” on page 65.
6. Connect the power cord to LanProbe and to a power source (either 100-120/
VAC or 220-240/VAC). LanProbe does not have a power switch but
becomes operational when power is attached.
63
Bootp Server Configuration
Bootp Server Setup on an HP or Sun System
The probe automatically broadcasts Bootp requests for each Telemetry and
Monitor/Transmit port when its IP address is 0.0.0.0 (the default). The
probe broadcasts Bootp requests to signal its need to be configured.
7. For HP-UX systems: Log in as root, then use SAM to follow the instructions
presented on the screen.
For HP-UX 9.x, choose:
Networking/Communications -> Service:Enable/Disable
For HP-UX 10.x and 11.x, choose:
Networking and Communications -> Network Services
NOTE
If the last screen presented in Step 7 displays bootp server enabled, (for
either HP-UX 9.x, HP-UX 10.x, or HP-UX 11.x) then your machine is already set
up as a bootp server.
8. Edit the /etc/bootptab file to configure the probe and add descriptive
comments to the file for reference. Refer to “Configuring the Bootptab File”
on page 73, the bootpd(1M) man page or the HP ARPA Services manual
for more information on configuring the /etc/bootptab file.
9. Use tail -f to check the system log file to ensure that the Bootp server
responded correctly to the Bootp request. The log file is /var/adm/
messages (Solaris), /usr/adm/syslog (HP-UX 9.x), or /usr/
adm/syslog/syslog.log (HP-UX 10.x and 11.x).
10. If you are using HP OpenView, you can verify that LanProbe has been
assigned the correct IP address for the Telemetry port and shows up on the
management station map as a network analyzer. The discovery process that
places LanProbe in the management station map can take several minutes to
complete.
64
Bootp Server Configuration
Bootp Server Setup on an HP or Sun System
NOTE
You may be able to decrease the required time for discovery of LanProbe by
pinging it continuously from your NetMetrix management station. You can also
ping LanProbe to verify that it responds to the new IP address.
Starting the Bootp Server on an HP or Sun System
You can start the Bootp server on an HP or Sun system in one of the following
ways. Refer to “Configuring the Bootptab File” on page 73 if you need to
configure the bootptab file.
Bootp for Solaris is shipped on the NetMetrix CD-ROM but it is not part of the
operating system.
standalone. Become superuser and give one of the following commands:
z /etc/bootpd -s
z /usr/lbin/bootpd -s
for HP-UX v. 9.x
for HP-UX v. 10.x & 11.x
z /usr/netm/sun4s/bootpd -s
for Solaris
inetd. Become superuser and use the following procedure:
1. Edit the file /etc/inetd.conf. Search for a line like the following and
ensure that the line is uncommented (does not contain a # character). If
necessary, add the line to the file.
bootps dgram udp wait root path/bootpd bootpd
Where path is one of the following:
/etc
/usr/lbin
for HP-UX v. 9.x
for HP-UX v. 10.x & 11.x
/usr/netm/sun4s
for Solaris
65
Bootp Server Configuration
Bootp Server Setup on an HP or Sun System
2. For HP-UX, give one of the following commands to force inetd to re-read
the inetd.conf file that you modified in Step 1 on page 65:
/etc/inetd -c
/usr/sbin/inetd -c
for HP-UX v. 9.x
for HP-UX v. 10.x & 11.x
3. For Solaris, determine the process ID for inetd by entering the following
command:
ps -ef | grep inetd
Then force inetd to re-read the inetd.conf file that you modified in Step 1 on
page 65 by giving the following command:
kill -HUP process_id
For additional information, refer to the man pages for bootpd(1M),
inetd(1M), inetd.conf(4M), ps(1M) and kill.
66
Bootp Server Configuration
Bootp Server Setup on a PC
Bootp Server Setup on a PC
Bootp software for a PC is included (on a 3.5" floppy disk) with your HP
LanProbe. Bootp software implements an internet Bootstrap Protocol (Bootp)
server as defined in RFC 951 and RFC 1048. It is run from the DOS prompt
either as a standalone executable or as a terminate-and-stay-resident (TSR)
program and communicates to a network interface card using the Microsoft NDIS
(LAN Manager), or Novell ODI (NetWare), network stack. Bootp software does
not support Microsoft Windows.
Refer to “Configuring the Bootptab File” on page 73 if you need to configure the
bootptab configuration file.
Use the following procedure to setup the Bootp server software on a PC:
1. Insert the 3.5" floppy disk into your disk drive.
2. Change the prompt to indicate your floppy disk drive volume and enter
setup. The following screen is displayed:
Bootp Setup
===========
Setup helps you install the Bootp server software for
use with either Microsoft LAN Manager or Novell ODI
version 3.1 software by:
- copying to your setup drive software for interfacing
the Bootp program to your networking software.
- modifying your CONFIG.SYS, AUTOEXEC.BAT, and
PROTOCOL.INI or NET.CFG files. (A copy of these files
are saved in CONFIG.BTP, AUTOEXEC.BTP, PROTOCOL.BTP
and NET.BTP, respectively.)
- copying the Bootp software to BOOTPD directory on your
startup drive.
- providing a README file that contains more information.
(Press return to continue or press ‘E’ to exit.)
67
Bootp Server Configuration
Bootp Server Setup on a PC
3. Press Return to continue. The following screen is then displayed:
Please specify startup drive to install Bootp on
[C:\]:
4. Specify the drive where you want to install the Bootp software and press
Return. The default is to install the Bootp software in C:\. The following
screen is then displayed:
Install Bootp Software for use with:
0: Microsoft LAN Manager 1.0 or later
1: Novell NetWare v3.1 or later
2: Exit this setup program
Enter choice [0 - 2]:
5. Specify the Network Operating System that you are using and then refer to
either “Using Microsoft LAN Manager” below or “Using Novell NetWare”
on page 70.
There will be different setup screens displayed depending on the Network
Operating System that you are using (Microsoft LAN Manager or Novell
NetWare).
Using Microsoft LAN Manager
If you have selected Novell NetWare v3.1 or later, skip to “Using Novell
NetWare” on page 70.
If you have selected Microsoft LAN Manager 1.0 or later from the setup menu,
use the following procedure to setup your Bootp installation.
68
Bootp Server Configuration
Bootp Server Setup on a PC
1. Skip this step if you only have one LAN interface in your system (the
following screen will not be displayed.) Specify the driver that will be used
for the Bootp server. This is an example; your driver may be different.
Bootp Installation for Microsoft LAN Manager:
=============================================
Setup has found multiple drivers that it can bind the
bootp software to.
Choose one of the following:
0: HPLAN
1: HPLANB
2: Exit this setup program
Enter number [0 - 2]:
2. The final screen looks like the following:
The following file has been copied to the directory
C:\LANMAN.DOS\:
- DISPKT10.DOS
The CONFIG.SYS and the PROTOCOL.INI files have been
modified. Unmodified backups have been saved as
C:\CONFIG.BTP and C:\LANMAN.DOS\PROTOCOL.BTP.
The following files have been copied to the directory
C:\BOOTPD:
- BOOTPD.EXE
- BOOTPTAB
- README.TXT
BOOTPTAB is a sample configuration file which you must
modify before executing BOOTPD.EXE.
Bootp Setup is complete.
Please read the README.TXT file for additional
information. You will need to restart your computer
before running the Bootp software.
3. Modify the sample bootptab configuration file and restart your computer
before running the Bootp software.
69
Bootp Server Configuration
Bootp Server Setup on a PC
Using Novell NetWare
If you have selected Microsoft LAN Manager 1.0 or later, go back to “Using
Microsoft LAN Manager” on page 68.
If you have selected Novell NetWare v3.1 or later from the setup menu, use the
following procedure to setup your Bootp installation.
1. Press return to continue from the following screen.
Bootp Installation for Novell networks:
=======================================
In order to use this product using the NetWare protocols,
you need to be running client versions of NetWare that
include:
- LSL.COM
v1.20 or later
Your NET.CFG file must specify a FRAME type of
ETHERNET_II. For example, your NET.CFG should include
something like:
LINK DRIVER HPWDSA8
FRAME ETHERNET_II
Bootp also requires that you do not have Novell TCP/IP
software (LAN Workplace for DOS) installed.
(Press return to continue or ‘E’ to Exit.)
2. Specify the location of the NET.CFG file. The default is for the NET.CFG
file to be located at C:\NOVELL\NET.CFG.
Setup could not find the NET.CFG file.
Please specify a full path and filename
(e.g. C:\NOVELL\NET.CFG):
70
Bootp Server Configuration
Bootp Server Setup on a PC
3. The final screen looks like the following:
The following file has been copied to the directory C:\:
- ODIPKT13.COM
The AUTOEXEC.BAT and the NET.CFG files have been modified.
A copy of the original files have been saved as
C:\AUTOEXEC.BTP and C:\NETWARE\NET.BTP.
The following files have been copied to the directory
C:\BOOTPD:
- BOOTPD.EXE
- BOOTPTAB
- README.TXT
BOOTPTAB is a sample configuration file which you must
modify before executing BOOTP.EXE
Bootp Setup is compete.
Please read the README.TXT file for additional
information. You will need to restart your computer before
running the Bootp software.
Starting the PC Bootp Server
You can start the PC Bootp server in one of the following ways:
z As a standalone executable program by entering the following:
bootpd -a IP address -s
z As a TSR (terminate-and-stay-resident) program by entering the following:
bootpd -a IP address
71
Bootp Server Configuration
Bootp Server Setup on a PC
Where:
-a IP address is required and specifies the IP address of the PC where you are
running bootpd.
-s specifies that you are running bootpd as a standalone executable (not as a
TSR). You may want to use the -s option if you do not need the Bootp daemon
to continually service bootp requests. This is preferable, since the Bootpd TSR
may consume a large amount of memory (depending on the size of your
bootptab file).
Upon startup, Bootpd reads the bootptab file and then listens for bootp request
packets from the network. Bootpd re-reads the bootptab file when it receives a
bootp request packet and detects that the file has been updated. If hosts are added,
deleted, or modified, their entries in Bootpd’s internal database are also updated
when the bootptab file is re-read. All Bootp status messages are logged to the
BOOTPD.LOG file.
You can now attach the power cord to LanProbe and to a power source (either
100-120/VAC or 220-240/VAC). LanProbe does not have a power switch but
becomes operational when power is attached. When powered on and when its IP
address is 0.0.0.0 (the default), LanProbe automatically broadcasts Bootp
requests that trigger the Bootp server to provide its configuration parameters.
When powered on and when its Telemetry and/or Monitor/Transmit port’s IP
addresses are 0.0.0.0 (the default), LanProbe automatically broadcasts Bootp
requests that trigger the Bootp server to provide its configuration parameters.
72
Bootp Server Configuration
Configuring the Bootptab File
Configuring the Bootptab File
Configure the bootptab file by using the following procedure and any ASCII text
editor to edit one of the files from Table 4-2.
Table 4-2: Bootp Server bootptab Files
Bootp Server:
Bootptab File Location
HP 9000 System
/etc/bootptab
Sun SPARC system
/usr/netm/config/bootptab
PC
C:\bootpd\bootptab
1. Enter your IP parameters into the bootptab file for each LanProbe that you
want to configure.
Use this format.
nodename:\
tag=value:\
tag=value:\
...
tag=value
The nodename is the host name of the LanProbe. The nodename can be up to
40 characters long using alpha-numerics, dashes, and dots. Do not use spaces
or underscores in the nodename.
Each tag and its associated value is an IP parameter configured for a
Telemetry port or LanProbe. Valid tags are listed in Table 4-3 on page 74. You
must provide a set of these tags for each Telemetry and Monitor/Transmit port
or LanProbe that you want to configure (some tags are optional).
73
Bootp Server Configuration
Configuring the Bootptab File
Blank lines and lines beginning with # in the bootptab file are ignored. You
must include a colon and a backslash to continue a line. The ht tag must
precede the ha tag.
An example bootptab file is shown at the end of this procedure.
Table 4-3: Bootptab File Tags
Tag
Description
hn
send nodename (Boolean flag, no “=value” is needed)
ht
hardware type (ether); must precede ha tag
vm
vendor magic cookie selector (must comply with RFC 1048)
ha
hardware address (link-level or MAC address expressed in
hexadecimal); the LanProbe’s hardware address is printed on a
label located on the Probe’s back panel.
ip
Internet Protocol (IP) address for the Probe
sm
subnet mask; this is required only if subnetting is being used
gw
IP address of the gateway used when sending packets off the local
subnet; one default gateway may be configured
2. Save the bootptab file after you have entered parameters for all of your
LanProbes.
3. Verify the bootp process by performing one of the items in Table 4-4 on
page 75.
74
Bootp Server Configuration
Configuring the Bootptab File
Table 4-4: Bootp Process Verification
Server
HP-UX
Bootp Server
Verification Process
Test the Bootp process by entering one of the following:
For HP-UX 9.x:
/etc/bootpquery <hardware address>
For HP-UX 10.x and 11.x:
/usr/sbin/bootpquery <hardware address>
Where <hardware address> is the MAC address of the
HP-UX workstation’s LAN interface.
Solaris
Bootp Server
If available, test the Bootp process by entering:
/etc/bootpquery <hardware address>
where <hardware address> is the MAC address of the
Solaris workstation’s LAN interface.
PC
Bootp Server
NOTE
Check the C:\bootpd\bootpd.log file for the entry
“Starting bootpd...”
Only bootpquery with bootptab entries include the ba tag.
75
Bootp Server Configuration
Configuring the Bootptab File
Example Bootptab File
The following is an example of the C:\bootpd\bootptab file provided with
the PC Bootp software. At the end of this bootptab file, there are example IP
configuration entries for a LanProbe.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
Example bootptab: database for bootp server.
Format:
nodename: tag=value: ... : tag=value
first field - nodename (hostname) of terminal followed by colon
(should be full domain name)
Blank lines and lines beginning with ‘#’ are ignored.
Make sure you include a colon and a backslash to continue a line.
Don’t put any spaces in the tag=value string.
The ht tag MUST precede the ha tag.
The options listed below are useful for Agilent LanProbes.
They are specified as tag=value and delimited by colons.
For a list of all possible options, see the
C:\BOOTPD\README.TXT file.
ba
hn
ht
ha
vm
ip
sm
gw
-
broadcast bootp reply for testing with bootpquery
send nodename (Boolean flag, no “=value” needed)
hardware type (ether) (must precede the ha tag)
hardware address (link level address) (hex)
vendor magic cookie selector (should be rfc1048)
LanProbe IP address
network subnet mask
gateway IP address
LanProbe example
lanprobe1:\
ba:\
hn:\
ht=ether:\
vm=rfc1048:\
ha=080009123456:\
ip=15.6.72.210:\
sm=255.255.248.0:\
gw=15.6.72.1
76
5
LanProbe Operation
LanProbe Operation
LanProbe Operation
The Agilent 3911A Multiport Token-Ring LanProbe is designed to operate
unattended once it has been configured and successfully completes its self-tests.
This chapter describes how to reset the probe and the effect that different restarts
have on probe data and measurement configuration settings.
78
LanProbe Operation
Restarting the Probe
Restarting the Probe
LanProbe can be restarted by performing a warm start or a cold start. In either
case, the probe executes self-tests and re-initializes. There are differences in the
effects of each type of restart.
z A warm start resets LanProbe’s measurement data only.
z A cold start resets all of LanProbe’s measurement data, filters, alarms, and
user-defined statistics studies (excluding communications configuration
parameters) back to default values.
Warm Start
A warm start resets LanProbe’s measurement data only. You can warm start
LanProbe by doing one of the following:
z Cycling power (or a power outage).
z Selecting the menu item Warm start and Exit from LanProbe’s Main Menu
when you have a local terminal connected to the probe, as described in Step
3 on page 82.
z Using NetMetrix to execute a LanProbe warm start. Refer to your NetMetrix
documentation for details.
Table 5-1 on page 80 shows which data and parameters are reset during a warm
start and during a cold start of a LanProbe.
79
LanProbe Operation
Restarting the Probe
Table 5-1: Probe Data and Parameters Reset by Warm or Cold Start
Category
LanProbe Memory Contents
Measurement
Data
Captured frames
Counted frames
Historical Token-Ring statistics
Current Token-Ring statistics
Host tables (RMON-1 & RMON-2)
Matrix tables (RMON-1 & RMON-2)
Host Top N statistics
Protocol distribution
Address map
User history
Logs
Echo Test counters
Alarm table
Filter table
Channel table
Buffer control table
Event table
Protocol directory
Community access table
Client tables
Historical study configuration
Echo Test table
Trap destination table
Serial configuration information for
outgoing connections, such as:
dial strings
Other Serial configuration information,
such as:
SLIP address and subnet mask
serial port speed
modem initialization strings
Probe configuration information,
such as:
IP address
default gateway
subnet mask
TFTP server address
Download filename
Time zone
Security Settings
Interface Status
Crash data (used by Agilent support)
Measurement
Configuration
Parameters
LanProbe
Configuration
Parameters
80
Warm
Start Status
Cold Start
Status
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Reset
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
Saved
LanProbe Operation
Restarting the Probe
Cycling Power
A power outage or cycling power to LanProbe causes a warm start. LanProbe
does not have a power switch; therefore, cycling the power consists of
disconnecting and reconnecting the power cord.
Selecting the Warm Start Menu Item
Use the following procedure to warm start the probe using LanProbe’s Main
Menu:
1. Connect a local terminal (or a PC emulating a terminal) to LanProbe. Refer
to Chapter 2 “Local Terminal Configuration” for information on connecting
a local terminal.
2. Press the CONFIG button once (on the back of the probe) to place LanProbe
into the configuration mode. Use a narrow, pointed object (like a pen) to
press the recessed CONFIG button. LanProbe then displays its Main Menu
on the terminal. Figure 5-1 shows LanProbe’s Main Menu.
Main Menu - Revision
1. Modify/View configuration values ->
2. Modify/View security values ->
3. Modify/View interface values ->
4. Display interface summary
5. TFTP Download new firmware ->
6. XMODEM Download new firmware ->
7. Warm start and Exit
8. Cold start and Exit
Figure 5-1: LanProbe’s Main Menu
81
LanProbe Operation
Restarting the Probe
3. Press 7 to execute a warm start and exit LanProbe’s Main Menu. The warm
start occurs immediately. The Activity and Fault LEDs are turned on during
a warm start. When the warm start completes, the Activity LED flashes to
indicate traffic (if present), the Fault LED turns off, and the ~Line On (or
Power) LED is on.
Cold Start
A cold start resets all of LanProbe’s measurement data as well as all alarm, event,
filter, and user-defined statistics configuration to their default values. Basic
communications configuration parameters (IP address, default gateway IP
address, and subnet mask) are not reset.
You can cold start LanProbe by doing one of the following:
z Pressing the CONFIG Button twice within one second.
z Selecting the menu item Cold start and Exit from LanProbe’s Main Menu
when you have a local terminal connected to the probe, as described on
page 83.
z Using NetMetrix to execute a LanProbe cold start. Refer to your NetMetrix
documentation for details.
Table 5-1 on page 80 shows which data and parameters are reset during a cold
start or warm start of LanProbe.
Pressing the CONFIG Button Twice
Pressing the CONFIG button twice within one second causes the probe to cold
start.
82
LanProbe Operation
Restarting the Probe
Selecting the Cold Start Menu Item
Use the following procedure to cold start the probe using LanProbe’s Main Menu:
1. Connect a local terminal (or a PC emulation a terminal) to LanProbe. Refer
to “LanProbe Operation” on page 77 for information on connecting a local
terminal.
2. Press the CONFIG button once (on the back of the probe) to place LanProbe
into the configuration mode. Use a narrow, pointed object (like a pen) to
press the recessed CONFIG button. LanProbe then displays its Main Menu
on the terminal. Figure 5-1 on page 81 shows LanProbe’s Main Menu.
3. Press 8 to execute a cold start and to exit LanProbe’s Main Menu. The cold
start occurs immediately. The Activity and Fault LEDs are turned on during
a cold start. When the cold start completes, the Activity LED flashes to
indicate traffic (if present), the Fault LED turns off, and the ~Line On (or
Power) LED is on.
83
LanProbe Operation
Restarting the Probe
84
6
Download New Firmware
Download New Firmware
Download New Firmware
The instructions in this chapter describe how to download new firmware to the
Agilent J3911A Multiport Token-Ring LanProbe. New firmware is downloaded
over the Ethernet or Token-Ring telemetry interface.
This download procedure is only necessary to upgrade your LanProbe firmware to
a new firmware release.
New firmware for the LanProbe comes in the form of a binary file. This binary
file can be received in the following ways:
z Sent to you by an Agilent Support Representative, on 3.5" floppy disk.
z Sent to you by an Agilent Support Representative via electronic means.
z Included with NetMetrix.
z Obtained via anonymous ftp from col.hp.com (15.255.240.16). The
/dist/netmetrix/lpfirmware directory contains the latest version
of LanProbe firmware. A README file found in this directory provides
more details about the files contained in the lpfirmware directory.
CAUTION
Downloading new LanProbe firmware resets stored probe data and some probe
configuration information (like filters, traps, and channels). It can affect the IP
address, subnet mask, or default gateway IP address in some situations. Refer to
the Readme file on the new firmware media for more information.
The available procedures for downloading new firmware to LanProbe are
documented in this chapter. You should first select a procedure and then go to that
section in this chapter and execute that procedure.
86
Download New Firmware
The following download procedures are covered in this chapter:
z “Downloading Firmware using an HP-UX Workstation and a Terminal” on
page 88
z “Downloading Firmware using a Networked PC and a Terminal” on page 93
z “Xmodem Download of Firmware” on page 98
You can also download firmware using NetMetrix. Refer to your NetMetrix
documentation for details.
87
Download New Firmware
Downloading Firmware using an HP-UX Workstation and a Terminal
Downloading Firmware using an HP-UX Workstation
and a Terminal
The following instructions assume you are using HP-UX 9.0, or later. Before
upgrading firmware, you must first establish an IP connection between your
HP-UX workstation and LanProbe.
The following steps are required to download firmware to your LanProbe:
1. “Install New Download Firmware on an HP-UX Workstation” below
2. “Download Firmware to LanProbe” on page 89
Install New Download Firmware on an HP-UX Workstation
To download a new firmware file to LanProbe using an HP-UX workstation and a
terminal, the new firmware file must be copied into the ~tftp directory on your
HP-UX workstation, and the file must be readable by tftp. Typically, the ~tftp
directory is /usr/tftpdir.
For more information on configuration and usage of tftp, refer to your HP-UX
tftp documentation (typically found in an ARPA Services manual).
88
Download New Firmware
Downloading Firmware using an HP-UX Workstation and a Terminal
Download Firmware to LanProbe
Once the new firmware is installed on the HP-UX workstation, you can download
it to LanProbe.
Verify the following before you start the download procedure:
z LanProbe is connected to the network.
z The IP address, subnet mask, and default gateway of LanProbe are
configured correctly.
z A terminal (or a PC running terminal emulator software) is attached to the
probe’s RS-232 port (using a null modem cable). Configure the
communication link for 8 bits per character, 1 stop bit, no parity, Xon/Xoff
handshaking, and a baud rate of 9600.
z You will also need the IP address of the HP-UX workstation.
Use the following procedure to download firmware to your LanProbe from the
HP-UX workstation using a terminal:
CAUTION
LanProbe executes a cold start if you press the CONFIG button twice within one
second. If this happens, wait for the cold start to be completed (about 45 seconds)
and then press the CONFIG button again to re-enter the configuration mode.
1. Press the CONFIG button on the back of LanProbe once. The LanProbe’s
Main Menu, as shown in Figure 6-1 on page 90, is displayed on the console.
NOTE
The LanProbe CONFIG button is recessed. This requires the use of a narrow,
pointed object (like a pen) to press the CONFIG button.
A warm start or cold start is completed when the Fault LED goes off. If traffic is
present, the Activity LED flashes to show traffic.
89
Download New Firmware
Downloading Firmware using an HP-UX Workstation and a Terminal
Main Menu - Revision
1. Modify/View configuration values ->
2. Modify/View security values ->
3. Modify/View interface values ->
4. Display interface summary
5. TFTP Download new firmware ->
6. XMODEM Download new firmware ->
7. Warm start and Exit
8. Cold start and Exit
Figure 6-1: LanProbe Main Menu (HP-UX Workstation)
NOTE
Item 5 in Figure 6-1 is not displayed if the Allow TFTP firmware downloads
menu item is not enabled. Refer to “Modify/View Security Values” on page 24 for
more information on enabling this menu item.
If item 5 (TFTP Download new firmware) is not displayed, the number used to
access items 6, 7, and 8 will be different.
2. Press 5 to display the Download Menu as shown in Figure 6-2.
90
Download New Firmware
Downloading Firmware using an HP-UX Workstation and a Terminal
TFTP Download Menu -- Firmware Rev.
1. Filename to download
2. tftp server IP address
3. Download firmware
firmware
X.X.X.X
0. Return to previous menu
LanProbe IP address:
Subnet mask:
Default gateway IP address:
0.0.0.0
0.0.0.0
0.0.0.0
Figure 6-2: LanProbe TFTP Download Menu (HP-UX Workstation)
3. Verify that LanProbe’s IP address, subnet mask, and default gateway
address, as displayed at the bottom of the Download Menu screen, are
correct. If you need to change the configuration information, press 0 to
return to the main menu and then press 1 to modify configuration options.
4. Press 1 from the Download Menu screen, and enter the filename to
download.
5. Press 2 and enter the IP address of the HP-UX workstation which is acting
as the tftp server.
6. Press 3 to download new LanProbe firmware and wait for LanProbe to
reboot automatically. It should take about 90 seconds to transfer the
firmware to LanProbe and for the automatic reboot to take place. The probe
relays will click at the end of the reboot process.
CAUTION
Do not reset, power-cycle, or reboot LanProbe immediately after the download
process. Doing this may cause your probe to be damaged. After the firmware file
has been downloaded to the probe, there will be a brief period (approximately
1 minute) while the probe is copying the firmware to the flash EPROM.
91
Download New Firmware
Downloading Firmware using an HP-UX Workstation and a Terminal
After the download process is complete, LanProbe reboots and starts running the
new firmware.
If an error occurs during the download process, LanProbe returns to the Main
Menu without storing the new firmware to memory.
92
Download New Firmware
Downloading Firmware using a Networked PC and a Terminal
Downloading Firmware using a Networked PC and a
Terminal
You can download new firmware to your LanProbe using a networked personal
computer (PC) and a dumb terminal. Before upgrading firmware, you must first
establish an IP connection between your networked PC and LanProbe.
The following steps are required to download firmware to LanProbe:
1. “Setup TFTP Server for Downloading” below
2. “Download Firmware to LanProbe” below
Setup TFTP Server for Downloading
Refer to your TFTP application manuals for information on how to setup your
server for downloading a file.
Download Firmware to LanProbe
Once your TFTP server is setup for downloading a file, you can download the new
firmware file to LanProbe.
93
Download New Firmware
Downloading Firmware using a Networked PC and a Terminal
Verify the following before you start the download procedure.
z The probe is connected to the network.
z The IP address, subnet mask, and default gateway of LanProbe are
configured correctly.
z A terminal (or a PC running terminal emulator software) is attached to the
probe’s RS-232 port (using a null modem cable). Configure the
communication link for 8 bits per character, 1 stop bit, no parity, Xon/Xoff
handshaking, and a baud rate of 9600.
z You will also need the IP address of the networked PC.
Use the following procedure to download firmware to LanProbe from the
networked PC using a terminal:
CAUTION
LanProbe executes a cold start if you press the CONFIG button twice within one
second. If this happens, wait for the cold start to be completed (about 45 seconds)
and then press the CONFIG button again to re-enter the configuration mode.
1. Press the CONFIG button on the back of the probe once. The LanProbe’s
Main Menu, as shown in Figure 6-3 on page 95, is displayed on the console.
NOTE
The LanProbe CONFIG button is recessed. This requires the use of a narrow,
pointed object (like a pen) to press the CONFIG button.
A warm start or cold start is completed when the Fault LED goes off. If traffic is
present, the Activity LED flashes to show traffic.
94
Download New Firmware
Downloading Firmware using a Networked PC and a Terminal
Main Menu - Revision
1. Modify/View configuration values ->
2. Modify/View security values ->
3. Modify/View interface values ->
4. Display interface summary
5. TFTP Download new firmware ->
6. XMODEM Download new firmware ->
7. Warm start and Exit
8. Cold start and Exit
Figure 6-3: LanProbe Main Menu (Networked PC)
NOTE
Item 5 in Figure 6-3 is not displayed if the Allow TFTP firmware downloads
menu item is not enabled. Refer to “Modify/View Security Values” on page 24 for
more information on enabling this menu item.
If item 5 (TFTP Download new firmware) is not displayed, the number used to
access items 6, 7, and 8 will be different.
2. Press 5 to display the Download menu as shown in Figure 6-4.
95
Download New Firmware
Downloading Firmware using a Networked PC and a Terminal
TFTP Download Menu -- Firmware Rev.
1. Filename to download
2. tftp server IP address
3. Download firmware
firmware
X.X.X.X
0. Return to previous menu
LanProbe IP address:
Subnet mask:
Default gateway IP address:
0.0.0.0
0.0.0.0
0.0.0.0
Figure 6-4: LanProbe TFTP Download Menu (Networked PC)
3. Verify that LanProbe’s IP address, subnet mask, and default gateway
address, as displayed at the bottom of the Download Menu screen, are
correct. If you need to change the configuration information, press 0 to
return to the main menu and then press 1 to modify configuration options.
4. Press 1, from the Download Menu screen, and enter the filename to
download.
5. Press 2 and enter the IP address of the networked PC which is acting as the
tftp server.
6. Press 3 to download new LanProbe firmware and wait for LanProbe to
reboot automatically. It should take about 90 seconds to transfer the
firmware to LanProbe and for the automatic reboot to take place. The probe
relays will click at the end of the reboot process.
CAUTION
Do not reset, power-cycle, or reboot LanProbe immediately after the download
process. Doing this may cause your probe to be damaged. After the firmware file
has been downloaded to the probe, there will be a brief period (approximately 1
minute) while the probe is copying the firmware to the flash EPROM.
96
Download New Firmware
Downloading Firmware using a Networked PC and a Terminal
After the download process is complete, LanProbe reboots and starts running the
new firmware.
If an error occurs during the download process, LanProbe returns to the Main
Menu without storing the new firmware to memory.
97
Download New Firmware
Xmodem Download of Firmware
Xmodem Download of Firmware
You can download firmware from your PC to LanProbe via Xmodem by using the
following procedure:
1. Access the HyperTerminal Windows 95 application or a similar
communications program which supports Xmodem file transfer.
2. Connect your PC to LanProbe’s RS-232 connector using a null modem
cable. Refer to Appendix A “Cables and Connectors”, for more information
on cables.
3. Configure the terminal emulator for 8 bits/character, 1 stop bit, no parity, no
flow control, and a baud rate of 9600.
4. Connect the power cord to LanProbe and to a power source (either 100-120/
VAC or 220-240/VAC). LanProbe does not have a power switch, but is
turned on by connecting power.
5. Start the configuration by quickly pressing the CONFIG button on the back
of LanProbe one time only. After about 10 seconds, LanProbe displays its
Main Menu on the terminal, as shown in Figure 6-5.
98
Download New Firmware
Xmodem Download of Firmware
Main Menu - Revision
1. Modify/View configuration values ->
2. Modify/View security values ->
3. Modify/View interface values ->
4. Display interface summary
5. TFTP Download new firmware ->
6. XMODEM Download new firmware ->
7. Warm start and Exit
8. Cold start and Exit
Figure 6-5: LanProbe Main Menu (XMODEM)
6. Press 6 to display the XMODEM download menu shown in Figure 6-6.
XMODEM Download Menu -- Firmware Rev.
1. Download at 38400 baud
2. Download at 19200 baud
3. Download at 9600 baud
0. Return to previous menu
Figure 6-6: LanProbe XMODEM Download Menu (Networked PC)
7. Press 1, 2, or 3 to select the download baud rate. You receive the following
message on your PC:
Downloading to Flash: Receiving File. . .
This and all of the messages are transmitted at 9600 baud. If you selected a
different baud rate, the messages will not be displayed correctly. However,
the download will work correctly.
99
Download New Firmware
Xmodem Download of Firmware
8. If you select a baud rate other than 9600, you will need to change the baud
rate of your terminal emulator to match the download speed that you
selected. If you are using the HyperTerminal application, select File ->
Properties -> Configure. You must select the Disconnect icon followed by
the Connect icon to get the baud rate changes to take effect.
9. Select Transfer and then Send File menu items from your PC’s Windows
application. You will be prompted to select the file to download.
The HyperTerminal application is configured for Zmodem by default. You
need to make sure that you select Xmodem from the Send File dialog box.
CAUTION
If you selected a baud rate other than 9600, the message following the successful
download will not be displayed correctly. In this case, wait approximately 2
minutes before power cycling the probe to ensure that the new firmware is written
to FLASH memory correctly.
If your download was not successful, it is recommended that you repeat the
process using 9600 baud so that all error message will be displayed correctly.
After the download process is complete, LanProbe reboots and starts running the
new firmware.
If an error occurs during the download process, LanProbe returns to the Main
Menu without storing the new firmware to memory.
If you are using an HP workstation and LanProbe takes more than 90 seconds to
download new firmware and to restart (boot), verify that the workstation is setup
correctly, and restart inetd by entering and running the following commands at
the workstation:
ps -ef | grep inetd
/etc/inetd -k
/etc/inetd
100
Download New Firmware
Xmodem Download of Firmware
NOTE
If you are experiencing tftp transfer timeouts or read errors, use the following
procedure to verify that tftp is configured correctly on your unix workstation.
1. Verify tftpd functionality by copying the firmware file to another directory
using the tftp command.
a. # cd /tmp
b. tftp 127.0.0.1
c. get firmware
d. quit
2. If the previous step fails, the problem is due to the tftpd configuration on the
unix server.
101
Download New Firmware
Xmodem Download of Firmware
102
A
Cables and Connectors
Cables and Connectors
Cables and Connectors
This appendix lists cables for use with the Agilent J3911A Multiport Token-Ring
LanProbe. The minimum connector pin-out are shown if you wish to use an
unlisted cable. Note that each connector pin-out does not necessarily match the
pin-out for the corresponding Agilent cable, but cables manufactured using at
least the minimum pin-out will function correctly.
This appendix covers the following sections:
z “Token-Ring Cabling Chart” on page 105
z “Serial Port Interface Cables” on page 106
z “Cable Connector Pin-Outs” on page 107
104
Cables and Connectors
Token-Ring Cabling Chart
Token-Ring Cabling Chart
The following table shows the most commonly used Token-Ring cable. Use this
table to verify that you are using compatible Token-Ring cabling throughout your
network. The cable designation is generally stamped on the cable jacket.
NOTE
Make sure that all of your cables have the same Velocity of Propagation (Vp).
Table A-1: Token-Ring Cable Type, Vp, and Impedance
Cable Type
VP
Impedance
Type 1 (STP)
78
150
Type 3 (UTP) level 3
60
100
Type 3 (UTP) level 4
69
100
Type 3 (UTP) level 5
78
100
105
Cables and Connectors
Serial Port Interface Cables
Serial Port Interface Cables
The following table shows the recommended cables for connecting LanProbe’s
serial port interface to a terminal or modem
Table A-2: Serial Port Interface Cable
Cable
Function
Connect a
terminal or PC
to the probe port
for configuring
the probe.
Connect a
modem to the
probe port for
SLIP
communications.
106
Agilent
Product
Number
Cable Type
Connectors
RS-232
“Crossover” or
“null modem”
cable
25-pin male to
25-pin male
13242G
25-pin male to
25-pin female
13242H
9-pin female to
25-pin male
24542G
25-pin male to
25-pin male
13242M,
13242N, or
17355M
25-pin male to
25-pin female
31391A
“Straightthrough” RS-232
modem cable
Cables and Connectors
Cable Connector Pin-Outs
Cable Connector Pin-Outs
LanProbe’s RS-232 Port Pin-Out
The following table shows the pin-out for LanProbe’s 25-Pin RS-232 port
(connector), which is used to connect to a terminal or modem using the
appropriate cable.
Table A-3: LanProbe’s RS-232 Port Pin-Out
NOTE
PIN
US
CCITT
DIN
1
CHS GND
101
2
Tx
103
D1
3
Rx
104
D2
4
RTS
105
S2
5
CTS
106
M2
6
DSR
107
M1
7
SIG GND
102
8
DCD
109
M5
20
DTR
108
S1
The probe asserts pins 20 and 4, pins 13, 14,16, and 19 are reserved, and all other
pins are not connected.
107
Cables and Connectors
Cable Connector Pin-Outs
LanProbe RS-232 Modem Cable Connectors
The following table shows the minimum pin-out for connecting LanProbe’s
RS-232 port to a modem using a 25-pin male to 25-pin male cable.
Table A-4: LanProbe to Modem Cable Min. Pin-Out
(25-Pin to 25-Pin)
Modem End
25-pin Male
108
Probe End
25-pin Male
2
<--
2
3
-->
3
4
<--
4
5
-->
5
6
-->
6
7
---
7
8
-->
8
20
<--
20
Cables and Connectors
Cable Connector Pin-Outs
25-pin Terminal/PC Cable Connectors
The following table shows the minimum pin-out for connecting LanProbe’s
RS-232 port to a 25-pin terminal (or PC) connector (also known as an RS-232
“Crossover” cable).
Table A-5: LanProbe to 25-Pin Terminal Cable Min. Pin-Out
Terminal/PC
LanProbe
2
-->
3
3
<--
2
7
---
7
9-pin Terminal/PC Cable Connectors
The following table shows the minimum pin-out for connecting LanProbe’s
RS-232 port to a 9-pin terminal (or PC) connector (also known as an RS-232
“Crossover” cable).
Table A-6: LanProbe to 9-Pin Terminal Cable Min. Pin-Out
Terminal/PC
LanProbe
2
<--
2
3
-->
3
5
---
7
109
Cables and Connectors
Cable Connector Pin-Outs
UTP Network Connector Pin-Out
The following table shows the RJ-45 (UTP) to RJ-45 connector pin-outs.
Table A-7: UTP (Type 3) Network Connector Pin-Outs
MsAU End
RJ-45
110
Probe End
RJ-45
3
<--
3
4
-->
4
5
-->
5
6
<--
6
Cables and Connectors
Cable Connector Pin-Outs
STP Network Connector Pin-Out
The following table shows the DB-9 (STP) to data connector pin-out. Refer to
Figure 1-1 for the color coded connection points.
Table A-8: STP (Type 1) Network Connector Pin-Outs
MsAU End
Data
Connector
Probe End
DB-9
Red
-->
1
Black
<--
5
Green
-->
6
Orange
<--
9
Figure 1-1: Data Connector Color Coded Connection Points
111
Cables and Connectors
Cable Connector Pin-Outs
112
B
LanProbe Specifications
LanProbe Specifications
LanProbe Specifications
This appendix lists the specifications for the Agilent J3911A Multiport TokenRing LanProbe.
Network Compatibility
Agilent J3911A
Base Hardware: 10Base-T/100Base-TX telemetry interface with RJ-45 and AUI
connectors.
Option 203:
4 IEEE 802.5, Token-Ring interfaces, 4 Mbytes or 16 Mbytes for
Type 1 (STP) or Type 3 (UTP) connectors.
Option 204:
6 IEEE 802.5, Token-Ring interfaces, 4 Mbytes or 16 Mbytes for
Type 1 (STP) or Type 3 (UTP) connectors.
The LanProbe can use either the network or the SLIP link to communicate with a
management station.
Software Standards
Remote Network Monitoring Management Information Base (RFC 1757),
Token-Ring RMON Extensions (1513), SNMP MIB-II (RFC 1213), SNMP (RFC
1157), RMON-2 (RFC 2021), Remote Network Monitoring MIB Protocol
Identifiers (RFC 2074), and Agilent Token-Ring LanProbe Private MIB.
Modem
Supports external Hayes-compatible modems from 300 to 38.4 K baud.
Media Types
STP (DB-9) and UTP (RJ-45)
Dimensions
H x W x D: 8.9 x 42.5 x 23.5 cm (3.5 x 16.8 x 9.3 in)
Weight
4.9 kg (10.8 lbs) without options
114
LanProbe Specifications
Power Requirements
120 VAC, 50/60 Hz,1.0 Amps; 240 VAC, 50/60 Hz, 0.6 Amps
Range: 100 VAC to 240 VAC +/- 10%
Environment
Operating
Non-Operating
Temperature
0°C to 55°C
(32°F to 131°F)
-40°C to 70°C
(-40°F to 158°F)
Relative Humidity
(non-condensing)
15% to 95%
at 40°C (104°F)
15% to 90%
at 65°C (149°F)
Maximum Altitude
4.6 km (15,000 ft)
4.6 km (15,000 ft)
Storage Temperature
-40°C to 70°C (-40°F to 158°F)
Probe Memory Allocation
The memory allocated to each parameter depends on how much memory is
installed in LanProbe. The memory parameter values relate to the various items in
the RMON or the Agilent private MIBs. These parameters were valid at the time
of publication.
Table B-1 on page 117 shows the memory allocated to each parameter for the
available LanProbe memory configurations. The memory allocation shown for
each table assumes that all of the available memory within the probe is allocated
to the identified table.
115
LanProbe Specifications
NOTE
The parameter values shown in Table B-1 on page 117 are approximate and
subject to change without notice. The values assume that RMON-2 tables
have not been created.
Host Table entries, Matrix Table entries, TopN entries, History buckets and
Trace buffers (packet capture buffers) are allocated dynamically from the
same memory allocation. The values shown for History buckets assume
that no Trace buffers are configured. If Trace buffers are configured, the
number of History buckets are reduced. The value for host and matrix table
sizes assume that both tables are the same size.
The value shown for Trace buffer octet capacity assumes that only the
default history studies are set up.
116
LanProbe Specifications
Table B-1: LanProbe Memory Allocation
Parameter
64MB
128MB
209,000
424,000
12
12
Maximum entries per TopN study
(e.g., top 50 nodes)
51,000
103,000
Maximum traffic matrix table size
345,000
698,000
Host table size
Maximum number of RMON MIB TopN studies
Maximum number of history studies
12
12
Total number of history buckets for all studies
239,000
659,000
Network layer host table size
293,000
593,000
Network layer traffic matrix table size
127,000
258,000
Application layer host table size
510,000
1,032,600
Application layer traffic matrix table size
261,000
527,000
Maximum entries per RMON-2 TopN Study
451,000
913,000
Maximum entries per RMON-2 address map
451,000
913,000
Maximum number of alarms
50,000
102,000
Maximum number of events
317,000
641,000
1,024
1,024
32*
32*
Log table entries
Maximum number of filters
Maximum number of channels
32*
32*
Maximum number of packet capture buffers
32*
32*
Trace buffer packet capacity
N/A
N/A
16-62MB
32-126MB
Maximum number of community names in
Community Access Table
20*
20*
Maximum number of IP address entries in
Client Table
20*
20*
Maximum number of trap destination entries
(Agilent private MIB)
30*
30*
Maximum SLIP connection entries
20*
20*
Maximum single shot ping
20
20
Maximum list pings
100
100
Trace buffer octet capacity
117
LanProbe Specifications
*
These numbers indicate that the probe will reserve memory for the minimum
number shown in the table. If memory available, these numbers can be higher.
RMON-2 Protocol Directory
Table B-2 shows the RMON-2 protocol directory in your probe.
NOTE
The parameter values shown in Table B-2 were accurate at the time of
printing and are subject to change without notice.
Table B-2: RMON-2 Protocol Directory
Description
Local
Index
ID
Parameters
ethernet
1
0.0.0.1
0
llc (802.2)
2
0.0.0.2
0
snap
3
0.0.0.3
0
ianaAssigned
4
0.0.0.5
0
ethernet.ip
5
0.0.0.1.0.0.8.0
0.0
llc.ip
6
0.0.0.2.0.0.0.6
0.0
snap.ip
7
0.0.0.3.0.0.8.0
0.0
wildcard.ip
8
1.0.0.1.0.0.8.0
0.0
ethernet.arp
9
0.0.0.1.0.0.8.6
0.0
snap.arp
10
0.0.0.3.0.0.8.6
0.0
wildcard.arp
11
1.0.0.1.0.0.8.6
0.0
ethernet.ipx
12
0.0.0.1.0.0.129.55
0.0
llc.ipx
13
0.0.0.2.0.0.0.224
0.0
snap.ipx
14
0.0.0.3.0.0.129.55
0.0
ianaAssigned.ipxOverRaw8023
15
0.0.0.5.0.0.0.1
0.0
wildcard.ipx
16
1.0.0.1.0.0.129.55
0.0
ethernet.appletalk
17
0.0.0.1.0.0.128.155
0.0
snap.appletalk
18
0.0.0.3.0.0.128.155
0.0
118
LanProbe Specifications
Table B-2: RMON-2 Protocol Directory (Continued)
Description
wildcard.appletalk
Local
Index
19
ID
Parameters
1.0.0.1.0.0.128.155
0.0
ethernet.chaosnet
20
0.0.0.1.0.0.8.4
0.0
snap.chaosnet
21
0.0.0.3.0.0.8.4
0.0
wildcard.chaosnet
22
1.0.0.1.0.0.8.4
0.0
ethernet.decnet unassigned
23
0.0.0.1.0.0.96.0
0.0
snap.decnet unassigned
24
0.0.0.3.0.0.96.0
0.0
wildcard.decnet unassigned
25
1.0.0.1.0.0.96.0
0.0
ethernet.decmop dump/load
assistance
26
0.0.0.1.0.0.96.1
0.0
ethernet.decmop remote console
27
0.0.0.1.0.0.96.2
0.0
ethernet.decnet phaseIV
28
0.0.0.1.0.0.96.3
0.0
ethernet.dec-lat
29
0.0.0.1.0.0.96.4
0.0
ethernet.decnet diagnostics
30
0.0.0.1.0.0.96.5
0.0
ethernet.decnet customer use
31
0.0.0.1.0.0.96.6
0.0
ethernet.decnet lavc, sca
32
0.0.0.1.0.0.96.7
0.0
ethernet.sna
33
0.0.0.1.0.0.128.213
0.0
llc.sna
34
0.0.0.2.0.0.0.4
0.0
snap.sna
35
0.0.0.3.0.0.128.213
0.0
wildcard.sna
36
1.0.0.1.0.0.128.213
0.0
ethernet.vines
37
0.0.0.1.0.0.11.173
0.0
snap.vines
38
0.0.0.3.0.0.11.173
0.0
wildcard.vines
39
1.0.0.1.0.0.11.173
0.0
ethernet.xns
40
0.0.0.1.0.0.6.0
0.0
llc.xns
41
0.0.0.2.0.0.0.128
0.0
snap.xns
42
0.0.0.3.0.0.6.0
0.0
wildcard.xns
43
1.0.0.1.0.0.6.0
0.0
wildcard.ip.icmp
44
1.0.0.1.0.0.8.0.0.0.0.1
0.0.0
wildcard.ip.tcp
45
1.0.0.1.0.0.8.0.0.0.0.6
0.0.0
wildcard.ip.udp
46
1.0.0.1.0.0.8.0.0.0.0.17
0.0.0
119
LanProbe Specifications
Table B-2: RMON-2 Protocol Directory (Continued)
Description
Local
Index
ID
Parameters
wildcard.ip.xns
47
1.0.0.1.0.0.8.0.0.0.0.22
0.0.0
wildcard.ip.iso-tp4
48
1.0.0.1.0.0.8.0.0.0.0.29
0.0.0
wildcard.ip.vines
49
1.0.0.1.0.0.8.0.0.0.0.83
0.0.0
wildcard.ip.igrp
50
1.0.0.1.0.0.8.0.0.0.0.88
0.0.0
wildcard.ip.ospfigp
51
1.0.0.1.0.0.8.0.0.0.0.89
0.0.0
wildcard.ip.mtp
52
1.0.0.1.0.0.8.0.0.0.0.92
0.0.0
wildcard.ipx.ncp
53
1.0.0.1.0.0.129.55.0.0.0.17
0.0.0
wildcard.ipx.sap
54
1.0.0.1.0.0.129.55.0.0.4.82
0.0.0
wildcard.ipx.rip
55
1.0.0.1.0.0.129.55.0.0.4.83
0.0.0
wildcard.ipx.netbios
56
1.0.0.1.0.0.129.55.0.0.4.85
0.0.0
wildcard.xns.netbios
57
1.0.0.1.0.0.6.0.0.0.0.1
0.0.0
wildcard.ip.tcp.ftp-d
58
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.20
0.0.0.0
wildcard.ip.tcp.ftp-c
59
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.21
0.0.0.0
wildcard.ip.tcp.telnet
60
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23
0.0.0.0
wildcard.ip.tcp.smtp
61
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.25
0.0.0.0
wildcard.ip.tcp.nicname
62
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.43
0.0.0.0
wildcard.ip.tcp.xns
63
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.52
0.0.0.0
wildcard.ip.tcp.dns
64
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.53
0.0.0.0
wildcard.ip.tcp.gopher
65
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.70
0.0.0.0
wildcard.ip.tcp.finger
66
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.79
0.0.0.0
wildcard.ip.tcp.http
67
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.80
0.0.0.0
wildcard.ip.tcp.npp
68
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.92
0.0.0.0
wildcard.ip.tcp.hostname
69
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.101
0.0.0.0
wildcard.ip.tcp.iso_tsap
70
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.102
0.0.0.0
wildcard.ip.tcp.pop2
71
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.109
0.0.0.0
wildcard.ip.tcp.pop3
72
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.110
0.0.0.0
wildcard.ip.tcp.sunrpc
73
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.111
0.0.0.0
120
LanProbe Specifications
Table B-2: RMON-2 Protocol Directory (Continued)
Description
Local
Index
ID
Parameters
wildcard.ip.tcp.nntp
74
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.119
0.0.0.0
wildcard.ip.tcp.ntp
75
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.123
0.0.0.0
wildcard.ip.tcp.netbios-ns
76
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.137
0.0.0.0
wildcard.ip.tcp.netbios-dgm
77
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.138
0.0.0.0
wildcard.ip.tcp.netbios-ssn
78
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.139
0.0.0.0
wildcard.ip.tcp.news
79
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.144
0.0.0.0
wildcard.ip.tcp.irc
80
1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.194
0.0.0.0
wildcard.ip.tcp.netware-ip
81
1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.140
0.0.0.0
wildcard.ip.tcp.exec
82
1.0.0.1.0.0.8.0.0.0.0.6.0.0.2.0
0.0.0.0
wildcard.ip.tcp.login
83
1.0.0.1.0.0.8.0.0.0.0.6.0.0.2.1
0.0.0.0
wildcard.ip.tcp.printer
84
1.0.0.1.0.0.8.0.0.0.0.6.0.0.2.3
0.0.0.0
wildcard.ip.tcp.lotusnote
85
1.0.0.1.0.0.8.0.0.0.0.6.0.0.5.72
0.0.0.0
wildcard.ip.tcp.ccmail
86
1.0.0.1.0.0.8.0.0.0.0.6.0.0.12.192 0.0.0.0
wildcard.ip.tcp.x11
87
1.0.0.1.0.0.8.0.0.0.0.6.0.0.23.112 0.0.0.0
wildcard.ip.udp.nicname
88
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.43
0.0.0.0
wildcard.ip.udp.xns
89
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.52
0.0.0.0
wildcard.ip.udp.dns
90
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.53
0.0.0.0
wildcard.ip.udp.bootp-server
91
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.67
0.0.0.0
wildcard.ip.udp.bootp-client
92
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.68
0.0.0.0
wildcard.ip.udp.tftp
93
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.69
0.0.0.0
wildcard.ip.udp.gopher
94
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.70
0.0.0.0
wildcard.ip.udp.finger
95
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.79
0.0.0.0
wildcard.ip.udp.http
96
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.80
0.0.0.0
wildcard.ip.udp.npp
97
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.92
0.0.0.0
wildcard.ip.udp.hostname
98
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.101 0.0.0.0
wildcard.ip.udp.sunrpc
99
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.111 0.0.0.0
wildcard.ip.udp.ntp
100
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.123 0.0.0.0
wildcard.ip.udp.netbios-ns
101
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.137 0.0.0.0
wildcard.ip.udp.netbios-dgm
102
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.138 0.0.0.0
121
LanProbe Specifications
Table B-2: RMON-2 Protocol Directory (Continued)
Description
wildcard.ip.udp.netbios-ssn
Local
Index
103
ID
Parameters
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.139 0.0.0.0
wildcard.ip.udp.news
104
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.144 0.0.0.0
wildcard.ip.udp.snmp
105
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161 0.0.0.0
wildcard.ip.udp.snmptrap
106
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.162 0.0.0.0
wildcard.ip.udp.irc
107
1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.194 0.0.0.0
wildcard.ip.udp.netware-ip
108
1.0.0.1.0.0.8.0.0.0.0.17.0.0.1.140 0.0.0.0
1
Wildcard.ipx includes ianaAssigned.ipxOverRaw8023 as a wildcard. It is used to
aggregate counters by using a single protocol value to indicate potentially many
base layer encapsulations of a network layer protocol.
122
Glossary
Glossary
Agent
A node (or software/hardware on a node) that supplies network management
information.
Battery-backed RAM
The probe’s memory that contains a copy of the probe configuration. If power is
removed from the probe (either by unplugging the power cord or from a power
outage), this memory is preserved by power provided by the probe's internal
battery.
Bridge
A device providing an intelligent connection between two otherwise independent
LANs. Bridges operate at layer 2 of the ISO OSI reference model. A bridge
inspects every packet originating on either LAN and creates a table of nodes and
their locations. It isolates the LANs from each other, allowing both sides to pass
traffic internally. If a transmission from one LAN is addressed to a node on the
other LAN, the bridge transmits it onto the other LAN for the destination node.
Broadcast address
The station address FFFFFF-FFFFFF. Packets intended for all nodes on a LAN
use this address as the destination address.
Broadcast packet
A packet sent to all nodes on a LAN.
Concentrator
An FDDI or Token-Ring network device that connects as a Dual Attachment
Station and has connections for additional devices (such as; stations,
concentrators, or bridges).
Console
The ASCII terminal, or PC emulating an ASCII terminal that is connected to the
probe and used to configure, monitor, and troubleshoot the probe.
Default Gateway Address
The address of the gateway which is closest to the probe.
124
DRAM
Dynamic Random Access Memory, which is the main memory of LanProbe.
Flash EPROM
EPROM that can be erased and reprogrammed while installed in a circuit.
Frame
A bit stream consisting of predefined fields that contain data, addresses, and
control information. In the IEEE 802.5 environment, this structure is often
referred to as the MAC frame. A frame is used in the Token-Ring environment to
transmit data between stations.
Gateway
A dedicated computer that is used to route frames from one dissimilar network to
another.
IEEE 802.5 Standard
Part of the Institute of Electrical and Electronics Engineers 802 family of LAN
standards. The 802.5 standard defines the physical layer (layer 1) and part of the
data link layer (layer 2) of the ISO OSI reference model for a Token-Ring LAN.
IP Address (Internet Protocol Address)
A 32-bit address that is divided into network-identifier and host-identifier fields,
which are used to identify a particular physical network or a particular device
attached to that physical network (respectively).
LAN (local area network)
A general-purpose communications network that interconnects a variety of
devices within a limited geographical area. A LAN might connect computers on
adjacent desks, within a building, or within several buildings of a campus. See
also extended LAN.
125
LAN cable
The medium through which data moves in a LAN. LAN cables come in many
types. For example, Type 1 ((STP) - Shielded Twisted-Pair cable) and Type 3
((UTP) - Unshielded Twisted-Pair cable).
LanProbe
See probe.
MAC address
A 12-digit (48 bit) hexadecimal number that identifies a specific network station
and allows messages to be directed to that station only. Because the IEEE has
assigned identifiers for each hardware manufacturer, no two pieces of equipment
have the same address. The address assigned according to the IEEE plan is
referred to as a device’s globally-administered station address. Some devices
provide an option for the user to assign a different station address that will
override the original. This type of address is referred to as a locally-administered
station address. The station address is also commonly called a MAC address,
Ethernet address, Token-Ring address, or physical address.
Manager
A node that collects network management information from agents.
Media Filter
A device used to convert Token-Ring adapter board output signal to function with
a particular type of wiring. Media Filters are required for 16 Mbps networks and
recommended for 4 Mbps networks using Type 3 (UTP) cable.
Management station
A station that collects network management information from probes.
MIB (Management Information Base)
A data structure used for communication and control of the probe.
126
Monitor-only Port
A Monitor-only port receives all network packets but cannot transmit packets onto
the network. It does not use the IP Address, Subnet Mask, and Default Gateway IP
Address fields. The following apply to Monitor-only ports:
z HP OpenView cannot automatically discover the interface
z Echo packets cannot be generated by the interface
z The interface is not IP addressable
Monitor/Transmit Port
A Monitor/Transmit port receives all network packets and can transmit packets
onto the network. It requires the IP Address, Subnet Mask, and Default Gateway
IP Address fields. The following apply to Monitor/Transmit ports:
z HP OpenView can discover the interface
z The interface is IP addressable
z The interface cannot respond to RMON groups 1 through 10 queries
MsAU (Media station Access Unit)
The attachment unit used to provide the physical connection and access to a
Token-Ring network.
NetMetrix
NetMetrix refers to the HP OpenView NetMetrix/UX software suite for HP-UX
and Solaris.
Node
A computer or other addressable device on a network, including PCs, terminals,
probes, routers, and mainframes. Usually, a node has a station address.
Object
Any device that can be monitored or controlled by use of the SNMP protocol.
Packet
A bit stream consisting of predefined fields that contain data, addresses, and
control information. In the IEEE 802.3 environment, this structure is often
referred to as the MAC frame. Packet is used in the Ethernet environment and is
used in this guide because it is the more commonly understood term. Different
protocols have different packet and frame specifications.
127
Private MIB
A proprietary MIB that has variables which are used for probe configuration and
control options.
Probe
A device on the LAN that monitors all frames and produces network management
information including current and historical traffic statistics and snapshots of
selected frames. Probes are also known as monitors.
Protocol
A set of rules that governs data transfer among devices on a network. A protocol
identifies the handshake type, frame size and format, timing, error recovery
scheme, word size or other characteristics of each transfer, depending on the
system.
Ring
See Token-Ring.
RMON MIB (Remote Network Monitoring MIB)
The collection of objects defined by the Internet Engineering Task Force in RFC
1757, RFC 1213, RFC 1157, RFC 2021, RFC 2074, Token-Ring RMON
Extensions, and Agilent LanProbe private MIB that are used for network
monitoring.
RS-232 port
A serial interface connector on a computer or peripheral that adheres to the current
RS-232 standard. The LanProbe RS-232 port adheres to this standard.
SAM (System Administration Manager)
A configuration tool provided by HP-UX for managing system resources and
changing configuration parameters.
Server
A device on the network that is dedicated to specific functions.
SIMM (Single Inline Memory Module)
DRAM that is mounted on a small printed circuit board that can be installed in the
Agilent LanProbe. Also see DRAM.
128
SLIP (Serial Line Internet Protocol)
A protocol used for serial communications.
SNMP (Simple Network Management Protocol)
A network management protocol used for communicating between network
managers and network objects.
Station
A computer or other addressable device on a network, including PCs, terminals,
probes, routers, and mainframes. A station must have an IP address.
STP (Shielded Twisted Pair)
LAN cable that is both twisted, in pairs, and shielded. Pair twisting and shielding
reduces crosstalk to a greater degree than UTP cable, especially at high
transmission rates.
Subnet Mask
Identifies the subnet field of a network address and is a 32-bit Internet address
written in dotted-decimal notation. A subnet mask is used to divide a network
into sub networks.
Telemetry Port
The Telemetry port receives all network packets, can transmit packets onto the
network, and is used for SNMP communications to the probe. It requires the IP
Address, Subnet Mask, and Default Gateway IP Address fields. The following
apply to Monitor/Transmit ports:
z HP OpenView can discover the interface
z Echo packets can be generated by the interface
z The interface is IP addressable
z The interface responds to RMON groups 1 through 9 queries
z The interface will transmit all traps from LanProbe
z The interface will transmit all extended RMON packet samples from
Monitor-only ports, Monitor/Transmit ports, and itself.
129
Terminal
An input/output device that permits interaction with a probe or computer. The
device can be a display and keyboard, or a personal computer. An ASCII
terminal, or PC emulating an ASCII terminal, can be connected to the probe for
configuration, monitoring, and troubleshooting the probe.
Token
A short frame that circulates over the ring until captured by a station that wants to
transmit a message. Tokens have a specific format as defined by the Token-Ring
standard.
Token-Ring
A LAN developed by IBM Corporation. Token-Ring transmits at 4 Mbit or 16
Mbit per second.
Token-Ring Cable
The MsAU cable used to connect devices to the Token-Ring network. This cable
connects a MsAU network port to either the RJ-45 or DB-9 probe port.
Topology
The organization of network devices in a network. Token-Ring uses a ring
topology.
UTP (Unshielded Twisted Pair)
A cable that is twisted in pairs. Pair twisting reduces crosstalk by canceling the
magnetic fields generated in each of the twisted wires.
Vp (nominal Velocity of Propagation)
The speed that a pulse travels along a given cable. Vp is expressed as a percentage
of the speed of light in a vacuum.
130
Index
Symbols
~ Line On LED 58
Numerics
100Base-TX Networks 44
10Base-2
MAU 43
10Base-T MAU 43
10Base-T Networks 44
10Base-T/100/Base-TX Networks
Connecting 44
10MB/s Ethernet Networks
Connecting 42
9000 System, Minimum Bootp Server Requirements
61
A
Access Security 10
Accessories, Optional 15
Activity LED 12, 58
Address Map
RMON-2 MIB 8
Agilent Assistance Phone Number xi
Agilent Private MIB 8
Alarms
RMON-1 MIB 8
Application Layer Traffic Matrix
RMON-2 MIB 8
Autodiscovery Echo Interval 19, 23
B
Back Panel LEDs 13
Back Panel, Probe 46
Bootp
Daemon 63
Process Verification 75
Relay 61
Server
Configuration and Installation 5
LanProbe Configuration 61
Minimum Requirements 62
Setup on a PC 67
Setup on HP or Sun System 63
Starting on a PC System 71
Starting on HP or Sun System 65
Bootptab File
Configuring 73
Example 76
Tags 74
Button
CONFIG 14, 22, 82, 89, 94
C
Cable
Media Filter 47
Type 1 (STP) 46
Cables
Connector Pin-Outs 107
Serial Port Interface 106
Cables and Connectors 103, 104
Cabling Chart, Token-Ring 105
Cold Start 82
Information Reset 79, 82
Menu Item 83
CONFIG Button 14, 22, 82, 89, 94
Configuration
and Installation Overview 5
Bootptab File 73
LanProbe, Bootp Server 61
LanProbe, Using a Local Terminal 19
Management Station and LanProbe, for Modem
51
Modify/View Menu 22
Options 2
131
Connection
Data Switch 53
Local/Direct, LanProbe 48
Modem 49
Out-of-Band 41, 48
Probe to the Network
10Base-T/100Base-TX Networks 44
10MB/s Ethernet Networks 42
Token-Ring Networks 45
Probe to the Network (Out-of-Band) 41
Ring-in (RI) 47
Ring-out (RO) 47
Connector
Cable Pin-Outs 107
DB-9 46
DB-9 to Data Connector Pin-Out 111
RJ-11 50
RJ-45 46
RJ-45 to RJ-45 Connector Pin-Outs 110
RS-232 Modem Pin-Out, 25 to 25-Pin 108
RS-232 Pin-Out, 25-Pin 107
RS-232, Terminal Connection 20
STP Network Connector Pin-Outs 111
Terminal Cable Pin-Out, 25-Pin 109
Terminal Cable Pin-Out, 9-Pin 109
Token-Ring Data 47
UTP Network Connector Pin-Outs 110
Connectors and Cables 103, 104
Cycling Power, LanProbe Warm Start 81
D
Data Connector 111
Data Connector, Token-Ring 47
Data Switch Connection 53
Date 19, 23
2000 23
DB-9 46
to Data Connector Cable Pin-Outs 111
Default Gateway IP Address 19, 28, 63
Direct Connection, LanProbe 48
132
Display Interface Summary
Menu 28
Download
Firmware
Using a Networked PC and a Terminal 93
Using Networked HP-UX Workstation and
Terminal 88
Using XMODEM 98
New LanProbe Firmware 86
E
Echo Test
Monitoring 3
RMON-1 MIB 8
Events
RMON-1 MIB 8
Exit
and Save Changes Menu 23, 28
Expansion Modules, Token-Ring 46
F
Fault LED 12, 58
Fiber-Optic
MAU 43
Filter, Media 47
Filters
RMON-1 MIB 8
Firmware Download
Allow (Enable) 25
TFTP, Enable 10
Frame Capture
RMON-1 MIB 8
H
Hardware Kit 14
Hayes-Compatible Modems 114
Help
Agilent Assistance Phone Number xi
History
RMON-1 MIB 8
Host Table
RMON-1 MIB 8
Host Top N
RMON-1 MIB 8
HP 9000 System, Minimum Bootp Server
Requirements 61
HP Private MIB 8
HP-UX Workstation, Using to Download new
Firmware 88
I
Impedance, Token-Ring Cable 105
Included Parts 14
Installation 36
and Bootp Server Configuration 5
and Configuration 5
LanProbe 34, 36
Rack or Cabinet 37
Table 37
Wall 39
Probe 2
Selecting a Location 35
Troubleshooting LanProbe 58
Verifying LanProbe 57
Interface Cables, Serial Port 106
Interface Summary
Display, Menu 28
Interface Values
Modify/View Menu 25
Introduction 2
IP Address 19, 28, 63
L
LAN Manager
Using 68
LanProbe 36
Cold Start 82
Menu Item 83
CONFIG Button 82
Configuration, Bootp Server 61
Connecting 41
Cycling Power, Warm Start 81
Download New Firmware 86
Hardware Kit 14
Included Parts 14
Installation 34
Main Menu 20
Memory Allocation 115
Modem Installation 50
Operation 78
Optional Accessories 15
Overview 6
Power Cord 15
Rack or Cabinet Installation 37
Rear Panel 21
Restarting 79
RMON-2 Protocol Directory 118
Self-Tests 57
Specifications 114
Starting 56
Table Installation 37
Wall Installation 39
Warm Start Menu Item 81
LED
~ Line On 12, 58
Activity 12, 58
Back Panel 13
Fault 12, 58
Power On 12, 58
Status 12, 57
Line On LED 12
Local Ringhub 46
Local Terminal
Configuration 14
and Installation Overview 5
Local Terminal Configuration 18
Log
RMON-1 MIB 8
133
M
MAC Address 63
Main Menu
LanProbe 20
Management Station 9
Modem Installation 50
MAU
10Base-2 43
10Base-T 43
Fiber-Optic 43
Media Filter 47
Media Station Access Unit (MsAU) 46
Memory Allocation, LanProbe 115
MIB
HP Private 8
RMON SNMP 8
Supported 8
Microsoft LAN Manager
Using 68
Modem
Carrier Detect 53
Connect Responses 32
Connection 49
Control String 19
Data Compression 52
Error Correction 52
Hang-Up String 31
Hardware Flow Control 52
Initialization String 31, 52
LanProbe Installation 50
Management Station Installation 50
No-Connect Responses 32
RS-232 Connector Pin-Out, 25 to 25-Pin 108
Serial Port
IP Address 52
Speed 52
Subnet Mask 52
Modify/View Configuration Values Menu 22
Modify/View Interface Values Menu 25
Modify/View Security Values Menu 24
Monitor/Transmit Port 27
134
Monitor-only Port 27
MsAU (Media Station Access Unit) 46
N
NetMetrix/UX (for UNIX)
HP OpenView 2
Network Layer Host Table
RMON-2 MIB 8
Network Layer Traffic Matrix
RMON-2 MIB 8
Novell NetWare
Using 70
O
OpenView NetMetrix/UX 2
OpenView NetMetrix/UX (for HP-UX or Solaris) 2
Optional Accessories 15
Out-of-Band
Connection 48
Serial Connection 41
Out-of-Bnd
Probe to the Network Connection 41
Overview
Installation and Configuration 5
LanProbe 6
System 6
P
Packet Capture
Enable 10
Packet Capture, Allow (Enable) 24
Parts, Included 14
PC Station, Using to Download new Firmware 93
PC System, Minimum Bootp Server Requirements 61
PC, Emulating a Terminal 14
Port Number 26
Port Type, Port Configuration 27
Ports
Monitor/Transmit 27
Monitor-only 27
Telemetry 27
POST
Power-On Self-Tests 57
Power
Cord 15, 56
LED 12, 58
Switch 56
Private MIB, HP 8
Probe
Back Panel 46
Rear Panel 46
Probe Configuration
RMON-2 MIB 8
Protocol Directory
RMON-2 MIB 8
Protocol Distribution
RMON-2 MIB 8
R
Rack or Cabinet Installation, LanProbe 37
Rear Panel, Probe 46
Restarting LanProbe 79
Ring Number 19, 28
Ring Speed 19
Ring Station Configuration
RMON-1 MIB 8
Ring Stations
RMON-1 MIB 8
Ring-in (RI) 47
Ring-out (RO) 47
RJ-11 Connector 50
RJ-45 46
to RJ-45 Connector Pin-Outs 110
RMON Conformance
RMON-2 MIB 8
RMON MIB 8
SNMP 8
RMON-1 MIB
Alarms 8
Echo Test 8
Events 8
Filters 8
Frame Capture 8
History 8
Host Table 8
Host Top N 8
Log 8
Ring Station Configuration 8
Ring Stations 8
Source routing Statistics 8
Statistics, Data Frames 8
Statistics, MAC Frames 8
Traffic Matrix 8
Trap 8
RMON-2 MIB
Address Map 8
Application Layer Host Table 8
Application Layer Traffic Matrix 8
Network Layer Host Table 8
Network Layer Traffic Matrix 8
Probe Configuration 8
Protocol Directory 8
Protocol Distribution 8
RMON Conformance 8
User History 8
RMON-2 Protocol Directory, LanProbe 118
RS-232 Connector
(Port) Pin-Out, 25-Pin 107
Terminal Connection 20
S
SAM 64
Save Changes and Exit Menu 23, 28
Security
Access 10
Firmware Download 10
Configure 25
Modify/View Security Values Menu 24
Packet Capture 10
Configure 24
135
Selecting a Location
for LanProbe 35
Self-Tests, LanProbe 57
Serial Communications
SLIP Link 3, 51
Serial Port
Hardware Flow Control 31
Interface Cables 106
IP Address 19, 31
Mode 19, 31
Modem Control String 19
Modify/View Settings 30
Settings 27
Speed 19, 31
Subnet Mask 19, 31
Server
Bootp
Minimum Requirements 62
Starting the HP or Sun 65
Starting the PC 71
Setup
Bootp Server
on a PC 67
on HP or Sun System 63
SLIP
Link Communications 3, 51
SNMP
Agent 6
RMON MIB 8
Source routing Statistics
RMON-1 MIB 8
Specifications, LanProbe 114
Start
Cold 82
Warm 79
Starting
Bootp Server, on a PC System 71
Bootp Server, on HP or Sun System 65
LanProbe 56
136
Station
Management 9
Statistics, Data Frames
RMON-1 MIB 8
Statistics, MAC Frames
RMON-1 MIB 8
Status LEDs 12, 57
Subnet Mask 19, 28, 63
Serial Port 31
Summary
Display Interface Summary Menu 28
Sun SPARC System, Minimum Bootp Server
Requirements 61
Supported MIBs 8
System
HP 9000, Minimum Bootp Server Requirements
61
PC, Minimum Bootp Server Requirements 61
Sun SPARC, Minimum Bootp Server
Requirements 61
System Overview 6
T
Table Installation, LanProbe 37
Telemetry Port 27
Terminal
Local, Configuration 14
PC, Emulating a 14
Probe Configuration (Local) 19
Using a Local 20
Terminal Cable Connector Pin-Out
25-Pin 109
9-Pin 109
Time 19, 23
Time Zone 19, 23
Token-Ring
Cable
Impedance 105
Velocity of Propagation 105
Cabling Chart 105
Data Connector 47
Token-Ring Networks
Connecting 45
Token-Ring Speed 28
Traffic Matrix
RMON-1 MIB 8
Trap
RMON-1 MIB 8
Troubleshooting
LanProbe’s Installation 58
Type 1 (STP) cable 46
Type 3 (UTP) cable 46
U
User History
RMON-2 MIB 8
V
Velocity of Propagation, Token-Ring cable 105
Verifying LanProbe’s Installation 57
W
Wall Installation, LanProbe 39
Warm Start 79
Cycling Power 81
Information Reset 79, 82
Menu Item 81
X
XMODEM Download of Firmware 98
137
138
Agilent Technologies, Inc. Offices
Asia-Pacific
Agilent Technologies, Inc.
24/F, Cityplaza One, 1111 King’s Road,
Taikoo Shing, Hong Kong, SAR
Tel:
(852) 3197–7777
Fax: (852) 2506–9284
Australia/New Zealand
Agilent Technologies Australia Pty. Ltd.
347 Burwood Highway
Forest Hill, Victoria 3131
Tel:
1 800 629 485 (Australia)
Fax: (61 3) 9272 0749
Tel:
0 800 738 378 (New Zealand)
Fax: (64 4) 802 6881
Canada
Agilent Technologies Canada Inc.
5150 Spectrum Way
Mississauga, Ontario L4W 5G1
Tel:
1 877 894 4414
Europe
Agilent Technologies, Inc.
Test and Measurement
European Marketing Organisation
P.O. Box 999
1180 AZ Amstelveen
The Netherlands
(31 20) 547 9999
Japan
Agilent Technologies Japan Ltd.
Measurement Assistance Center
9-1, Takakura-Cho, Hachioji-Shi,
Tokyo 192-8510, Japan
Tel:
(81) 426 56 7832
Fax: (81) 426 56 7840
Latin America
Agilent Technologies, Inc.
Latin American Region Headquarters
5200 Blue Lagoon Drive,Suite #950
Miami, Florida, USA 33126
Tel:
(305) 267–4245
Fax: (305) 267–4286
United States
Agilent Technologies, Inc.
Test and Measurement Call Center
P.O. Box 4026
Englewood, CO 80155-4026
1 800 452 4844
Download PDF