Networking Reference Guide

Networking Guide for
Nuclear Medicine Products
9202-0148 Rev. B
4535 601 32021
CSIP Level 1
Table of Contents
Ch. 1: Network Configuration Overview _______ 19
Ch. 2: IP Subnetting________________________ 85
Ch. 3: Network Hardware Overview __________ 119
Ch. 4: Network Peripherals_________________ 237
Ch. 5: ADAC Network Troubleshooting_______ 301
Ch. 6: Network File Structures ______________ 379
Ch. 7: File Editors ________________________ 433
Appendix A: Dec/Hex/Bin Conversions_______ 441
Appendix B: Networking Glossary __________ 443
Appendix C: OUI (MAC Address) Codes ______ 509
Appendix D: Networking Parts Display _______ 553
Appendix E: Router Access List Description __ 563
Philips Medical Systems

Nuclear Medicine
540 Alder Drive
Milpitas, California 95035
Proprietary Notice
This document and the information contained in it is proprietary and confidential information of Philips Medical Systems
("Philips") and may not be reproduced, copied in whole or in part, adapted, modified, disclosed to others, or disseminated
without the prior written permission of the Philips Legal Department. Use of this document and the information contained
in it is strictly reserved for current Philips personnel and Philips customers who have a current and valid license from
Philips for use by the customer’s designated in-house service employee on equipment located at the customer’s
designated site. Use of this document by unauthorized persons is strictly prohibited. Report violations of these
requirements to the Philips Legal Department. This document must be returned to Philips when the user is no longer
licensed and in any event upon Philips’ first written request.
Copyright Notice
© June 1, 2005, Koninklijke Philips Electronics N.V. All Rights Reserved.
Warranty Disclaimer
Philips provides this document without warranty of any kind, either implied or expressed, including, but not limited to,
the implied warranties of merchantability and fitness for a particular purpose.
Limitation of Liability
Philips has taken care to ensure the accuracy of this document. However, Philips assumes no liability for errors or
omissions and reserves the right to make changes without further notice to any products herein to improve reliability,
function, or design. Philips may make improvements or changes in the product(s) or program(s) described in this
document at any time.
CSIP Level 1
This document, and the information contained in it, is strictly reserved for current Philips Medical Systems (“Philips”)
personnel, Philips licensed representatives and Philips customers who have purchased a valid service agreement for use
by the customer’s designated in-house service employees on equipment located at the customer’s designated site. Use of
this document by unauthorized persons is strictly prohibited. This document must be returned to Philips when the user is
no longer licensed and in any event upon Philips’ first written request.
Trademarks
Sun and Ultra AXi are trademarks of Sun Microsystems, Inc.
SPARC is a trademark of SPARC International, Inc.
About This Manual

This Field Service manual describes concepts and contains instructions for installing Philips Medical Systems computer
networks and peripherals. This manual also describes network theory to the extent that is necessary for a trained Philips
Medical Systems Field Service Engineer to install and maintain advanced multi-system topologies.
This manual does not describe how to design custom hospital networks. However, the fundamental networking
information necessary to provide educated assistance to hospital IT staff is provided in this manual.
This manual illustrates possible Philips Medical Systems and hospital network layouts. The manual also provides tips for
installing and troubleshooting Philips Medical Systems only networks, and tips for interfacing to hospital networks.
Page 2 of 564 Networking Guide for Nuclear Medicine Products CSIP Level 1 9202-0148 Rev. B
Welcome to Philips Medical Systems Nuclear Medicine Networking
The purpose of this manual is help you connect Philips Medical Systems computers and
peripherals to Philips Medical Systems networks. This manual provides custom load instructions of
network files for Philips Medical Systems computers. The products covered are:
• Peg-X (i.e., Pegasys 5, 10, 15, 20, 25, etc.)
• Pegasys Ultra (i.e., Ultra 1, 60, High-Tier)
• Peg-X Acquisition Stations
• Atlas Acquisition Stations
• Skylight Computers and firewalls
• Peripherals and Network hardware
• LAN and WAN topology
To use this manual, you should be an Philips Medical Systems trained Field Service Engineer.
Specifications
When using this manual you will need to refer to the following manuals:
• Peg-X 3.4 Software Installation (9202-0117*)
• Pegasys Ultra Ver. 4.2 (9202-0142*)
• Atlas Acquisition Software Installation (9202-0143*)
• Pegasys Network Video Training Manual
• Current Version of Technical Tips
• Philips/ADAC Laptop computer
• DICOM Install and Users Manuals
Before starting, you should have the following computer media:

• 3.5” Floppy Disks
• 1/4” Tape Cassettes
• 100MB Zip Cartridges
• PegX 3.4 (or later) Software CD
• PegUltra 4.2 (or later) Software CD
• Atlas Software Disks and Cartridges
Special Notes / Conventions

• WARNING: Messages that alert you to conditions that may result in death or serious injury.
• CAUTION: Messages indicating conditions that may result in one or more of the following:
- Minor or moderate injury to you or the patient
- Damage to the equipment or other property
- Data loss
• Important: Vital information that describes how to properly install, configure, or use the
system.
• Note: Additional information that may help explain an action or procedure.
• PegX and PegUltra computers are Pegasys Systems.
• Bold type = characters you must type or points of interest/highlight
• <esc> = escape key depressed
• Fixed-width Courier generally indicates computer output or input.
9202-0148 Rev. B CSIP Level 1 Networking Guide for Nuclear Medicine Products Page 3 of 564
Table of Contents
Table of Contents.......................................................................................................................... 4
Chapter 1: Network Configuration Overview............................................................................ 19

Chapter Outline ......................................................................................................................... 19
Information for Using this Chapter ......................................................................................... 21
Network Fundamentals ............................................................................................................. 22
Basic Terminology................................................................................................................. 22
OSI Reference Model ............................................................................................................ 24
Examples of Commonly Known Protocols ........................................................................... 24
TCP/IP Protocol Layers ......................................................................................................... 25
Packets on the Wire ............................................................................................................... 25
Packet (or Data Frame) Format.............................................................................................. 25
Site Surveys – The Key to Planning ......................................................................................... 26
Site Survey Highlights ........................................................................................................... 26
Sections to Note ..................................................................................................................... 27
Custom Naming Suggestions................................................................................................. 27
Filtering Hints ........................................................................................................................ 28
Network Drawings ................................................................................................................. 29
Pegasys Networking General Guidelines................................................................................. 29
Planning for WAN & Complex LAN ....................................................................................... 31
Reasons to Custom Network.................................................................................................. 31
Fundamental Site Information ............................................................................................... 31
Cable Runs and Equipment.................................................................................................... 32
Communication is key ........................................................................................................... 32
Planning and Assistance from the Custom Networking Group ............................................. 33
Custom Network Guidelines.................................................................................................. 33
Network Configuration Examples............................................................................................ 35
Standalone Ultra and Atlas Network ..................................................................................... 36
Standalone PegUltra/Atlas Concepts .............................................................................. 37
Atlas Generic Camera Hookup........................................................................................ 38
Standalone PegUltra/Atlas Networking Guide................................................................ 38
Networked Ultra and Atlas Systems ...................................................................................... 40
Networked PegUltra and Atlas Systems, Concepts.......................................................... 41
Networking Guide - Networked PegUltra/Atlas Systems (multiple)................................ 41
Twisted Pair Mixed Environment Network........................................................................... 44
Twisted Pair Mixed Environment Network Concepts...................................................... 45
Twisted Pair Mixed Environment Networking Guide ...................................................... 45
Thinnet-Only Mixed Environment Networking .................................................................... 48
Thinnet-Only Mixed Environment Networking Concepts ................................................ 49
Thinnet-Only Mixed Environment Networking Guide ..................................................... 50
Thinnet-Twisted Pair Mixed Environment Networking ........................................................ 52
Thinnet-Twisted Pair Mixed Environment Networking Concepts ................................... 53
Thinnet-Twisted Pair Mixed Environment Networking Guide ........................................ 53
Reduced Repeaters (Hubs) in a Network ............................................................................... 54
Before Rewiring to Reduce Repeater Count .................................................................... 54
After Rewiring to Reduce Repeater Count ....................................................................... 54
Reduced Repeaters in a Network Concepts ..................................................................... 55
Custom Networks on a LAN/WAN ....................................................................................... 56
Custom Networks on a LAN/WAN Concepts.................................................................... 57
Custom Networks on a LAN/WAN Guide......................................................................... 58
Custom Networks on Hospital LANs with Second Ethernet Card ........................................ 60
Custom Networks on Hospital LANs with Second Ethernet Card Concepts ................... 61
Custom Networks on Hospital LANs with Second Ethernet Card Guide ........................ 62
Skylight/Jetstream Networking.............................................................................................. 64
Skylight/Jetstream Networking Concepts......................................................................... 65
CardioMD Networking .......................................................................................................... 66
CardioMD Networking Concepts..................................................................................... 67
WAN Connection Topics ........................................................................................................... 68
WAN Highlights .................................................................................................................... 68
How Fast is this WAN connection?....................................................................................... 69
Testing Throughput with command-line FTP........................................................................ 69
How can Sites estimate their throughput requirements?........................................................ 70
The Truth about Patient data space ........................................................................................ 71
Calculating space in KB for /files/pat on different drives ..................................................... 71
Why not use DSL for remote WebView or Peg2Peg on a WAN? ........................................ 72
WANs using DSL via VPN through Firewall........................................................................ 73
Other Network Configuration Topics ...................................................................................... 74
Conversion to All-Ultra Clusters ........................................................................................... 74
Configuration Precautions...................................................................................................... 75
Special Network Configurations-AFMs ................................................................................ 76
Sun Network File System Facilities....................................................................................... 77
NFS................................................................................................................................... 77
automount......................................................................................................................... 78
cron .................................................................................................................................. 79
rdist .................................................................................................................................. 80
rlogin................................................................................................................................ 81
rcp .................................................................................................................................... 82
References................................................................................................................................... 83
Chapter 2: IP Subnetting............................................................................................................ 85
Chapter Outline ......................................................................................................................... 85
Definitions................................................................................................................................... 87
What is an IP Address?.......................................................................................................... 87
What is an IP Network? ......................................................................................................... 87
What is a Network Number? ................................................................................................. 87
What is a Netmask? ............................................................................................................... 87
What is a Default Netmask? .................................................................................................. 87
What is a Subnet Mask?......................................................................................................... 88
What is an IP Subnet?............................................................................................................ 88
Why use IP Subnetting?......................................................................................................... 88
Introduction to IP Subnetting................................................................................................... 88
IP Addressing Principles ........................................................................................................... 89
IP Networks ........................................................................................................................... 91
IP Address Classes................................................................................................................. 92
Class A (1.0.0.0 — 126.255.255.255) .............................................................................. 92
Class B (128.0.0.0 — 191.255.255.255) .......................................................................... 93
Class C (192.0.0.0 — 223.255.255.255).......................................................................... 93
Note on Reserved Host ID Values ......................................................................................... 94
Network Numbering Principles................................................................................................ 94
Note on Dot Zero Notation .................................................................................................... 95
Network Numbering Rules .................................................................................................... 96
Netmasks..................................................................................................................................... 97
Decimal – Binary – Hexadecimal Conversion Table ............................................................ 98
Default netmasks.................................................................................................................... 98
Netmask Application ............................................................................................................. 98
Masking Rules ..................................................................................................................... 100
Note on Reserved Network Addresses ................................................................................ 101
IP Subnetting Principles.......................................................................................................... 102
Subnet Masks ....................................................................................................................... 102
Subnetting in Practice .......................................................................................................... 102
Subnetting a Class C network .............................................................................................. 104
Subnet Mask Translation Table ............................................................................................. 107
Examining the Netmask Values assigned on a Pegasys or Atlas ......................................... 109
Netmasks on SunOS 4.1.3u1 ............................................................................................... 109
Netmasks on Solaris............................................................................................................. 109
Real-World Example of IP Address Ranges in Subnets ...................................................... 110
The IP Subnet Calculator........................................................................................................ 112
How to run IP Subnet Calculator ......................................................................................... 113
The Hexpert Calculator ........................................................................................................ 114
Summary................................................................................................................................... 115
References ................................................................................................................................. 117
Chapter 3: Network Hardware Overview and Installation...................................................... 119

Chapter Outline........................................................................................................................ 119
Section Overview...................................................................................................................... 121
Wiring, Cables, and Terminators ........................................................................................... 122
Thicknet (10Base5) .............................................................................................................. 122
Thinnet (10Base2)................................................................................................................ 123
Twisted Pair (10BaseT, 100baseT) ...................................................................................... 124
Fiber Optic Cable (100baseFX) ........................................................................................... 126
ISDN (Integrated Services Digital Network)....................................................................... 127
T1 Line ................................................................................................................................. 127
Terminators .......................................................................................................................... 128
The Dreaded-T Diagram ...................................................................................................... 128
Connectors and Converters .................................................................................................. 129
Major Connectivity Components and Functionality............................................................ 130
Repeaters........................................................................................................................ 131
Hubs (Multi-port concentrators/repeaters) ................................................................... 131
Switches.......................................................................................................................... 131
VLANs ............................................................................................................................ 132
Routers ........................................................................................................................... 132
Gateways........................................................................................................................ 133
Filtering Bridges ............................................................................................................ 133
2nd Ethernet Cards ......................................................................................................... 133
Field Service Networking Hardware Parts............................................................................ 135
Example Drawings of Typical Network Deployments.......................................................... 136
Switched VLAN................................................................................................................... 137
Standard Routing LAN ........................................................................................................ 138
Standard Routing WAN ....................................................................................................... 139
Filtering Bridge LAN........................................................................................................... 140
2nd Ethernet Card.................................................................................................................. 141
Local Online Documentation of Custom Networks............................................................. 142
Installing Custom Networking Hardware ............................................................................. 144
Atlas 4-port Hub upgrade to 8-port Switch........................................................................... 145
Configuring a Router for Straight Routing........................................................................... 146
Gateway of Last Resort .................................................................................................. 161
Configuring a Router as a Filtering Bridge........................................................................... 163
All Target Devices in Same Subnet ..................................................................................... 163
Configuring a Router as a Filtering Bridge........................................................................... 179
Target devices both within subnet & beyond hospital router (IP locked) ........................... 179
Using rcp and vi to make editing access lists easier.............................................................. 200
Broadcast Traffic and its effect on CPU performance ......................................................... 208
Installing a 2nd Ethernet Card (Software & Hardware) ..................................................... 210
2ND Ethernet 10 Mbit PegX 2, 5, 10, or 20 QUICK guide - 09/21/2000 ............................. 211
2ND Ethernet 10/100 Mbit PegX 5, 10, or 20 QUICK guide - 09/21/2000.......................... 213
2ND Ethernet 10/100 Mbit Ultra 1 QUICK guide - 09/21/2000........................................... 215
2ND Ethernet 10/100 Mbit Ultra 10, 60 QUICK guide - 09/21/2000................................... 217
Network Speeds, Duplex, MTU, Ports and Auto-Negotiation ............................................. 219
Forcing 100Mbit, Half-duplex on Solaris............................................................................ 221
Forcing 100Mbit, Full-duplex on 4.1.3u1............................................................................ 222
How to check speed and duplex .......................................................................................... 222
Reducing MTU Value.......................................................................................................... 223
Creating a Defaultrouter File ................................................................................................. 224
Basic Ethernet Packet Routing Diagram.............................................................................. 224
Defaultrouter Guidelines...................................................................................................... 225
Centralized (connectivity for entire cluster) .................................................................. 226
Single-Point (One Pegasys only with 2nd Ethernet Card).............................................. 226
Configuring Additional Static Routes.................................................................................. 228
Shortcut Procedure for changing IP’s, subnet, default router ONLY ............................... 230
Chapter 4: Network Peripherals Hardware and Software ...................................................... 237

Scope ......................................................................................................................................... 237
Outline....................................................................................................................................... 237
Hardware Devices .................................................................................................................... 238
Formatters ............................................................................................................................ 238
Local Formatters ........................................................................................................... 238
Shared (Network) Formatters........................................................................................ 238
Formatter Installation........................................................................................................... 238
Formatters Requiring Sbus and PCI Formatter Cards ................................................. 238
Network Formatters ....................................................................................................... 239
Twisted Pair Formatter Network Cabling Diagram ............................................................ 240
Thinnet Formatter Network Cabling Diagram..................................................................... 242
Formatter Files......................................................................................................................... 244
cat /etc/hosts .................................................................................................................. 244
cat /vol/patients_db/formatcap ...................................................................................... 244
cat /vol/patients_db/formatcap_db ................................................................................ 246
cat /vol/patients_db/periph.rsc ...................................................................................... 248
cat /etc/modules/localdev.def......................................................................................... 249
cat /vol/patients_db/Codonics/codonicsprint.cfg........................................................... 249
Formatter Troubleshooting Information............................................................................... 251
PCI Formatters ..................................................................................................................... 251
Codonics Formatters ............................................................................................................ 251
Modems ..................................................................................................................................... 251
Installation............................................................................................................................ 251
Modem Files and Configuration Checks ............................................................................. 252
Modem Troubleshooting Information.................................................................................. 253
Optical Drives........................................................................................................................... 253
Optical Installation............................................................................................................... 254
Optical Files ......................................................................................................................... 254
TenX and MaxOptix Files.................................................................................................... 254
cat /vol/patients_db/periph.rsc...................................................................................... 254
cat /etc/modules/localdev.def ........................................................................................ 254
cat /etc/exports ............................................................................................................... 255
dmesg ............................................................................................................................. 255
TenX and MaxOptix Troubleshooting Information............................................................. 256
fsck /dev/rsd2a................................................................................................................ 256
Archive Tracker Files........................................................................................................... 256
cat /etc/exports (PegX)................................................................................................... 256
grep -i atx /usr/adac/site/`hostname`/ADACSetup......................................................... 257
cat /eoddir/atx.drives ..................................................................................................... 258
running atx ..................................................................................................................... 258
/eoddir/atxMakeRes /eoddir........................................................................................... 258
dmesg <Example from an Ultra-60>........................................................................ 259
Archive-Tracker Troubleshooting Information ................................................................... 260
Line Printers ............................................................................................................................. 260
Line Printer Installation ....................................................................................................... 260
Line Printer Files.................................................................................................................. 261
cat /vol/patients_db/periph.rsc....................................................................................... 261
cat /etc/modules/localdev.def ......................................................................................... 261
cat /etc/printcap ............................................................................................................. 261
Line Printer Troubleshooting Information........................................................................... 262
NUMA Direct Connect ............................................................................................................ 262
NUMA Installation .............................................................................................................. 262
NUMA Files......................................................................................................................... 262
NUMA Troubleshooting Information.................................................................................. 262
Software Options...................................................................................................................... 264
DICOM ..................................................................................................................................... 264
What is DICOM? ................................................................................................................. 264
DICOM Features.................................................................................................................. 264
What are the requirements?.................................................................................................. 265
DICOM Documents ............................................................................................................. 265
Conformance statement ................................................................................................. 265
DICOM Site Survey: ........................................................................................................... 265
DICOM Release Packages:.................................................................................................. 265
DICOM Installation ............................................................................................................. 266
DICOM Files and Troubleshooting Tools ........................................................................... 266
running DICOM............................................................................................................. 269
DICOM Transfer.................................................................................................................. 269
dicom_version ................................................................................................................ 269
cat /vol/patients_db/dicom/dicompeers.cfg ................................................................... 269
cat /vol/patients_db/dicom/dicomscp.cfg....................................................................... 270
DICOM Print ....................................................................................................................... 273
dicom_print_version ...................................................................................................... 273
cat /vol/patients_db/dicom/dicomprint.cfg .................................................................... 273
DICOM WorkList................................................................................................................ 275
dicom_worklist_version ................................................................................................. 275
cat /vol/patients_db/dicom/WorkListAtlasServer.cfg..................................................... 275
DICOM Troubleshooting Information................................................................................. 279
Peg2Peg Software..................................................................................................................... 279
Peg2Peg Network Connection ............................................................................................. 280
Peg2Peg Modem Connection............................................................................................... 280
Installation ........................................................................................................................... 280
Peg2Peg Files and Troubleshooting Tools .......................................................................... 281
Peg2Peg Troubleshooting Information ................................................................................ 284
WebView Software .................................................................................................................. 284
WebView Installation .......................................................................................................... 285
Network Connection ...................................................................................................... 285
Modem Connection ........................................................................................................ 285
WebView Files .................................................................................................................... 286
WebView Troubleshooting Information.............................................................................. 287
PPP Software............................................................................................................................ 288
PPP Installation.................................................................................................................... 288
PegX............................................................................................................................... 288
PegUltra......................................................................................................................... 288
PPP Files and Commands .................................................................................................... 289
PegX PPP Files ............................................................................................................. 289
Peg Ultra PPP Files ...................................................................................................... 291
PPP Troubleshooting Information ....................................................................................... 295
Shadow ...................................................................................................................................... 295
Shadow Installation.............................................................................................................. 296
Shadow Files........................................................................................................................ 296
Shadow Troubleshooting Information ................................................................................. 299
SeeMor ...................................................................................................................................... 299
SeeMor Installation .............................................................................................................. 299
SeeMor Files ........................................................................................................................ 300
SeeMor Troubleshooting Information ................................................................................. 300
Chapter 5: ADAC Network Troubleshooting .......................................................................... 301

Chapter 5 Outline..................................................................................................................... 301
Typical Information Needed Before You Begin Troubleshooting ...................................... 302
Cabling problems are generally caused by .......................................................................... 302
Software / Network Problems are generally caused by ....................................................... 302
General Guide to ADAC Network Hardware ....................................................................... 308
Electrical Diagnostics & Troubleshooting........................................................................... 308
Cabling ................................................................................................................................. 308
Thin Ethernet (coax) ...................................................................................................... 309
However, bus systems do have drawbacks,.................................................................... 309
Bus Topology DO'S........................................................................................................ 309
Bus Topology DONT'S ................................................................................................... 310
LAN Test Instruments.......................................................................................................... 310
Where do you start? ....................................................................................................... 310
CATEGORIZING LAN PROBLEMS................................................................................. 311
HARDWARE .................................................................................................................. 311
SOFTWARE ................................................................................................................... 312
CABLING PROBLEMS ARE GENERALLY.................................................................... 312
BASIC TROUBLESHOOTING HARDWARE TOOLS TO USE...................................... 312
Cable Troubleshooting Strategy........................................................................................... 313
General Principles ................................................................................................................ 313
Current and Ground Loop Tests........................................................................................... 314
Resistance Tests ................................................................................................................... 315
Shorts ............................................................................................................................. 315
Open circuits, Cable breaks........................................................................................... 316
Missing or Faulty terminators ....................................................................................... 316
All connections good, normal network .......................................................................... 317
FLUKE DSP-2000 Cable Analyzer ........................................................................................ 318
Introduction.......................................................................................................................... 318
Testing Twisted-Pair (10bT / 100bT) .................................................................................. 319
Testing Thin-net (10b2) ....................................................................................................... 321
Testing Fiber-Optic (10bFL)................................................................................................ 321
General Guide to Philips/ADAC Network Software Diagnostics........................................ 322
Software Troubleshooting Topics ........................................................................................ 322
Verifying NIS Maps............................................................................................................. 322
Cross-Binding with Multiple Masters in LAN/WAN ...................................................... 324
PegX Network Software Diagnostics...................................................................................... 324
Unix Command-line Diagnostics......................................................................................... 324
ping & ping -s ................................................................................................................ 324
uptime & rup .................................................................................................................. 325
ifconfig -a....................................................................................................................... 325
pstat -s............................................................................................................................ 326
netstat -rn ....................................................................................................................... 326
netstat -i ......................................................................................................................... 326
arp -a.............................................................................................................................. 327
nfsstat ............................................................................................................................. 327
/var/adm/messages......................................................................................................... 328
Monitoring and Diagnosing the Need for Filtering Using Etherfind................................... 329
Methodology for using etherfind ......................................................................................... 329
etherfind ......................................................................................................................... 331
High Level etherfind Summary ........................................................................................... 331
Medium Level etherfind Summary...................................................................................... 331
Low Level etherfind Summary ............................................................................................ 332
SOLARIS Network Software Diagnostics ............................................................................. 334
Unix Command-line Diagnostics......................................................................................... 334
ping & ping -s ................................................................................................................ 334
uptime & rup .................................................................................................................. 334
ifconfig -a....................................................................................................................... 335
swap ............................................................................................................................... 335
netstat -rn ....................................................................................................................... 336
netstat -i ......................................................................................................................... 336
arp -a.............................................................................................................................. 336
nfsstat ............................................................................................................................. 337
/var/adm/messages......................................................................................................... 338
Monitoring and Diagnosing the Need for Filtering Using Snoop ....................................... 339
Snooping Hints .................................................................................................................... 339
Methodology for snoop........................................................................................................ 339
Example of snoop output .................................................................................................... 341
Expand raw data file with different level of detail into new files........................................ 341
High Level snoop Summary ................................................................................................ 341
Medium Level snoop Summary........................................................................................... 342
Low Level snoop Summary................................................................................................. 343
Looking for Particular Types of Traffic............................................................................... 344
“Real world” example of using snoop & etherfind............................................................... 345
Problem & Description ........................................................................................................ 345
Using Snoop......................................................................................................................... 345
Examine and Correct the Router Configuration .................................................................. 351
Using Etherfind .................................................................................................................... 353
Hardware Address Not Found Infotip Summary Steps ....................................................... 355
WAN Troubleshooting............................................................................................................. 356
Mapping the Topology......................................................................................................... 356
The expanding ping test ....................................................................................................... 356
ISDN details......................................................................................................................... 357
Beware of Access Lists ........................................................................................................ 357
Security Topics .................................................................................................................... 357
Router/Filtering-Bridge Troubleshooting.............................................................................. 358
Using TELNET to Access the Configuration Interface ....................................................... 358
Examining the Running Configuration ................................................................................ 358
Using ping From Inside the Router...................................................................................... 359
Using arp From Inside the Router........................................................................................ 360
Using traceroute From Inside the Router............................................................................. 361
Examining the Ethernet Interfaces ....................................................................................... 361
Examining the Routing Tables............................................................................................. 363
Examining the Routing Protocols ........................................................................................ 365
Examining the Bridging Activity......................................................................................... 366
Updating Configuration Changes......................................................................................... 367
Exiting the Router ................................................................................................................ 367
Rebooting the Router ........................................................................................................... 368
EMERGENCY_STANDALONE ........................................................................................... 368
Emergency Standalone, Emergency Recovery .................................................................... 368
Hard Disk on the master Pegasys is Corrupted or Dead ...................................................... 369
Other Hardware Problem on master..................................................................................... 370
Steps for Reconfiguring Network Roles for a Cluster or Splitting Clusters........................ 371
Restore PegX ( Ultra only ) ..................................................................................................... 372
Failed /vol/patientsN install: ................................................................................................... 373
Sun Ethernet interface diagnostic .......................................................................................... 375
Sparc 5,10,20........................................................................................................................ 375
Ultra ..................................................................................................................................... 375
NI5210DG Ethernet Card Diagnostic .................................................................................... 376
Linksys Ethernet Card Diagnostic ......................................................................................... 377
Chapter 6: Network File Structures......................................................................................... 379

Scope.......................................................................................................................................... 379
Examples of PegX Network Files (links)................................................................................ 380
Examples of Ultra Network Files (links)................................................................................ 381
PegX Network Files ............................................................................................................. 381
PegX Master Files (“nmvap”).............................................................................................. 381
cat /.rhosts...................................................................................................................... 381
cat /etc/hosts .................................................................................................................. 382
cat /etc/peghosts (master only) ..................................................................................... 383
cat /etc/ethers ................................................................................................................. 383
cat /etc/defaultrouter...................................................................................................... 384
cat /etc/aliases................................................................................................................ 384
cat /etc/fstab ................................................................................................................... 385
cat /etc/auto.vol (master only) ...................................................................................... 385
cat /etc/hostname.le0 ..................................................................................................... 386
cat /etc/systems (master only) ....................................................................................... 386
cat /etc/ypservers (master only) .................................................................................... 386
cat /etc/modules/shared_dist.map (master only) .......................................................... 387
cat /etc/networks ............................................................................................................ 387
cat /etc/netmasks ............................................................................................................ 388
cat /etc/exports (differs depending on acq, options, etc..) ............................................ 389
cat /etc/install/sys_info .................................................................................................. 389
cat /usr/adac/site/`hostname`/ADACSetup .................................................................... 390
cat /vol/patients_db/partitions.map ............................................................................... 390
PegX Client Files (“nmvap1”) ............................................................................................. 391
cat /.rhosts...................................................................................................................... 391
cat /etc/hosts .................................................................................................................. 391
ypcat peghosts.byname .................................................................................................. 392
cat /etc/ethers ................................................................................................................. 392
cat /etc/defaultrouter...................................................................................................... 392
cat /etc/aliases................................................................................................................ 393
cat /etc/fstab ................................................................................................................... 394
cat /etc/auto.vol (master only) ...................................................................................... 394
cat /etc/hostname.le0 ..................................................................................................... 394
cat /etc/hostname.hme0.................................................................................................. 395
cat /etc/modules/shared_dist_map (master only) ......................................................... 395
cat /etc/networks ............................................................................................................ 395
cat /etc/netmasks ............................................................................................................ 396
cat /etc/exports (may be different in each system) ......................................................... 396
cat /etc/install/sys_info .................................................................................................. 397
PegX Acquisition Files ........................................................................................................ 398
cat /etc/modules/acq.cfg................................................................................................. 398
cat /etc/modules/acq_sw_config .................................................................................... 399
cat /etc/modules/adac.config ......................................................................................... 399
cat /usr/adac/pegx/data//COR/pc_stack11.cor .............................................................. 401
EPIC Detectors on a PegX Camera...................................................................................... 402
cat /usr/local/matador/etc/bootptab............................................................................... 402
PegX Acquisition PC Network Files ................................................................................... 403
type drives.bat ................................................................................................................ 403
type network.bat ............................................................................................................. 403
type hosts........................................................................................................................ 403
Ultra Master Files................................................................................................................. 404
cat /.rhosts...................................................................................................................... 404
cat /etc/hosts................................................................................................................... 404
cat /etc/ethers ................................................................................................................. 405
cat /etc/networks ............................................................................................................ 405
cat /etc/netmasks ............................................................................................................ 406
cat /etc/defaultrouter (Default router on joined subnet)............................................... 406
cat /etc/aliases................................................................................................................ 407
cat /etc/vfstab (Ultra-1 example, 2 hard drives) ........................................................... 407
cat /etc/auto.vol (master only) ....................................................................................... 408
cat /etc/nodename .......................................................................................................... 409
cat /etc/hostname.hme0 .................................................................................................. 409
cat /etc/hostname.hme1 .................................................................................................. 409
cat /etc/modules/shared_dist.map (master only) .......................................................... 410
cat /etc/dfs/dfstab ........................................................................................................... 411
cat /etc/dfs/sharetab ....................................................................................................... 411
cat /vol/patients_db/partitions.map ............................................................................... 412
Ultra Client Files.................................................................................................................. 413
cat /.rhosts...................................................................................................................... 413
cat /etc/hosts................................................................................................................... 413
ypcat peghosts.byname................................................................................................... 414
cat /etc/ethers ................................................................................................................. 414
cat /etc/networks ............................................................................................................ 414
cat /etc/netmasks ............................................................................................................ 415
cat /etc/defaultrouter (Default router on joined subnet)............................................... 416
cat /etc/aliases................................................................................................................ 416
cat /etc/vfstab (Ultra 60 example)................................................................................. 417
cat /etc/auto.vol (master only) .................................................................................. 417
cat /etc/nodename .......................................................................................................... 418
cat /etc/modules/shared_dist_map (master only) ......................................................... 419
Atlas Files with a Forte Camera Attached ........................................................................... 420
cat /etc/hosts .................................................................................................................. 420
cat /etc/ethers ................................................................................................................. 421
cat /etc/networks ............................................................................................................ 421
cat /etc/netmasks ............................................................................................................ 422
cat /etc/aliases................................................................................................................ 422
cat /etc/vfstab ................................................................................................................. 423
cat /usr/local/matador/etc/bootptab .............................................................................. 425
cat /export/home/atlas/etc/site.config ............................................................................ 425
cat /export/home/atlas/etc/acq_sw_config..................................................................... 426
cat /export/home/atlas/data/pc_atlas1.COR.................................................................. 426
Skylight Files ............................................................................................................................ 427
Sample “bootptab” Skylight EPIC Detectors & Gantry PC ................................................ 427
Dormant “bootptab” file for Skylight Gantry ...................................................................... 427
Determine Skylight “cameraname” ..................................................................................... 428
Ethernet Switch/Router in PC Tower .................................................................................. 429
IP Address for WAN port of Skylight Router .................................................................... 429
Netmask for WAN port of Skylight Router........................................................................ 430
Display the software packages and versions........................................................................ 430
Display SW version loaded.................................................................................................. 430
Changing Date and Time ..................................................................................................... 431
File for DatabaseHost of Atlas............................................................................................. 431
Skylight Gantry Log files .................................................................................................... 432
Chapter 7: File Editors ............................................................................................................. 433

File Editors ............................................................................................................................... 434
EMACS Editor..................................................................................................................... 434
EDLIN Editor ...................................................................................................................... 434
VI Editor .............................................................................................................................. 435
CHEATSHEET FOR THE vi EDITOR .............................................................................. 436
Getting into the editor .................................................................................................... 436
Save Files and Exit......................................................................................................... 436
Screen/Line Movement ................................................................................................... 436
Marking and Returning.................................................................................................. 437
Word Movement ............................................................................................................. 437
Search Functions............................................................................................................ 437
Delete Text ..................................................................................................................... 437
Cancel Edit Function ..................................................................................................... 437
Copy and Insert Text ...................................................................................................... 438
Copy and Insert Text (using named buffers).................................................................. 438
Change Text ................................................................................................................... 438
Word processing functions............................................................................................. 438
Add/Append Text ............................................................................................................ 438
Add new lines ................................................................................................................. 438
Change Text ................................................................................................................... 438
Interrupting/Canceling................................................................................................... 439
Search Functions............................................................................................................ 439
Move and Insert Text...................................................................................................... 439
Save Files and Exit......................................................................................................... 439
Move Between Documents ............................................................................................. 439
Control Edit Session....................................................................................................... 440
Special Functions........................................................................................................... 440
Decimal / Hexadecimal / Binary Conversion Table ................................................................. 441
Glossary of Networking Terms ................................................................................................ 443
Organizationally Unique Identifiers (OUI)................................................................................ 509
Networking Parts Display ......................................................................................................... 553
Filtering-Bridge Access-List Format........................................................................................ 563
< This page intentionally left blank >
Chapter 1: Network Configuration Overview
Chapter Outline
This chapter covers planning and implementation of different types of network

configurations. We cover the need for and how to get the most out of the Site Survey for planning
and the diagrams and roadmap instructions for configuring will assist you in an orderly network
installation. This chapter covers the following topics:
I. Information for Using this Chapter

II. Network Fundamentals
a. Basic Terminology
b. OSI Reference Model
c. Examples of Commonly Known Protocols
d. TCP/IP Protocol Layers
e. Packets on the Wire
f. Packets (or Data Frame) Format
III. Site Surveys – The Key to Planning
a. Site Survey Highlights
b. Sections to Note
c. Custom Naming Suggestions
d. Filtering Hints
e. Network Drawings
IV. Pegasys Networking General Guidelines
V. Planning for WAN & Complex LAN
a. Reasons to Custom Network
b. Fundamental Site Information
c. Cable Runs and Equipment
d. Communication is key
e. Planning and Assistance from the Custom Networking Group
f. Custom Network Guidelines
VI. Network Configuration Examples
a. Standalone Ultra and Atlas Network
i. Standalone PegUltra/Atlas Concepts
ii. Atlas Generic Camera Hookup
iii. Standalone PegUltra/Atlas Networking Guide
b. Networked Ultra and Atlas Systems
i. Networked PegUltra and Atlas Systems, Concepts
ii. Networking Guide - Networked PegUltra/Atlas Systems (multiple)
c. Twisted Pair Mixed Environment Network
i. Twisted Pair Mixed Environment Network Concepts
ii. Twisted Pair Mixed Environment Networking Guide
d. Thinnet-Only Mixed Environment Networking
i. Thinnet-Only Mixed Environment Networking Concepts
ii. Thinnet-Only Mixed Environment Networking Guide
e. Thinnet-Twisted Pair Mixed Environment Networking
i. Thinnet-Twisted Pair Mixed Environment Networking Concepts
ii. Thinnet-Twisted Pair Mixed Environment Networking Guide
f. Reduced Repeaters (Hubs) in a Network
i. Before Rewiring to Reduce Repeater Count
ii. After Rewiring to Reduce Repeater Count
iii. Reduced Repeaters in a Network Concepts
g. Custom Networks on a LAN/WAN
i. Custom Networks on a LAN/WAN Concepts
ii. Custom Networks on a LAN/WAN Guide
h. Custom Networks on Hospital LANs with Second Ethernet Card
i. Custom Networks on Hospital LANs with Second Ethernet Card Concepts
ii. Custom Networks on Hospital LANs with Second Ethernet Card Guide
i. Skylight/Jetstream Networking
i. Skylight/Jetstream Networking Concepts
j. CardioMD Networking
i. CardioMD Networking Concepts
VII. WAN Connection Topics
a. WAN Highlights
b. How Fast is this WAN connection?
c. Testing Throughput with command-line FTP
d. How can Sites estimate their throughput requirements?
e. The Truth about Patient data space
f. Calculating space in KB for /files/pat on different drives
g. Why not use DSL for remote WebView or Peg2Peg on a WAN?
h. WANs using DSL via VPN through Firewall
VIII. Other Network Configuration Topics
a. Conversion to All-Ultra Clusters
b. Configuation Precautions
c. Special Network Configurations-AFMs
d. Sun Network File System Facilities
IX. References
Information for Using this Chapter
There are additional manuals and documents referenced by this chapter. Make sure you have
access to the following documents. They may be found in a variety of places, including your on-site
cabinet for documentation and software, or the FS Hardware Manuals CDROM (4200-9113*), or the
on-line Intranet at http://intranet/departments/field_service/NM/techpubs.html:
• PegasysX Ver. 3.4 Software Field Service Manual (9202-0117*)
• Pegasys Ultra Ver. 4.2 Software Field Service Manual (9202-0142*)
• Atlas Acquisition Software Ver. * Installation Field Service Manual (p/n varies depending on
acquisition software version)
• Nuclear Medicine Site Survey Document CS-16-1*
• SOP-76 Product Implementation-Installation Responsibilities
• Installation Instructions for Atlas Universal Network Upgrade Kit (9343-2263*)
• DICOM Software Release Document (9215-0024*)
• CardioMD Service Manual (9202-0204*)
• SOP-24 Customer Support Procedure
The ‘Networking Guide’ instructions provided in this chapter are written for non-established
systems, standalone units not previously networked or configured for acquisitions. If you are
networking systems that have been in use for acquisitions, then certain backups must be performed
on those systems prior to performing the networking steps. Actual procedures for the different types
of cameras and systems may be found in their own manual sets. Be sure to:
• Backup all patient studies
• Backup display/processing defaults
• Backup acquisition files (matador, cortbl, acq.cfg, acq_sw_config, global_adac.config)
• Backup acquisition protocols
• Backup COR files
• Record the Ethernet numbers for the PC and the EPIC detectors
• Backup the next_examkey file on the master
• Backup gantcal.dat and gantlim.dat
• Once the installation/networking is completed, reload the backup information onto the newly
networked system. (Beware: some of these backups contain hostname specific info and may
cause a problem when being reloaded when the hostname has changed. Some of these files
would be the COR files, acq.cfg, acw_sw_config, etc. Also, once you have a solid
configuration you should make new backups and store them away to help out in the event that
disaster strikes.)
The instructions provided can be used for configuring both standard Philips/ADAC and
custom networks. For custom networking, be sure to map out the network on paper with each
system’s assigned host name and IP, domainname, defaultrouter information, and netmask
information, prior to actually networking the systems.
Network Fundamentals
BASIC TERMINOLOGY
AppleTalk protocol used by Apple MacIntosh computers and peripherals.
ATM Asynchronous Transfer Mode – dedicated-connection switching technology
using 53 byte “cells” with management capabilities to guarantee Quality Of
Service (QOS) for different data types.
AUI Attachment Unit Interface. An IEEE 802.3 cable connecting the MAU (media
attachment unit) to the networked device. The term AUI also can be used to
refer to the host back-panel connector to which an AUI cable might attach.
Also called transceiver cable.
BGP Border Gateway Protocol – exchanges Internet routes, optimized over EGP.
DECnet/LAT network protocols used by DEC computers (VAX, MicroVAX, etc.)
DNS Directory Name Service – translates Internet domain names into IP addresses –
often used within company networks to provide hierarchical sub-domain
organization and controls.
EGP Exterior Gateway Protocol – exchanges Internet routes.
FTP File Transfer Protocol – common and most basic way to transfer data and text
files.
HTTP Hypertext Transfer Protocol –transmits text and graphics displayed as web
pages.
IGRP Interior Gateway Routing Protocol – now EIGRP (Enhanced IGRP) has
efficient updates and handles metrics for multiple protocols.
IPX Internetwork Packet Exchange – Novell packet protocol.
ISDN Integrated Services Digital Network – first “affordable” dial-on-demand digital
connection over standard phone lines.
ISDN BRI Basic Rate Interface – Two 64 Kbps “B” Channels for data, One 16 Kbps “D”
channel for control and signals.
ISDN PRI Primary Rate Interface – Twenty Three 64 Kbps “B” Channels for data, One
64 Kbps “D” channel for control and signals.
LAN Local Area Network - collection of local nodes and links usually sharing an
address range within a building or site (complex LANs may use WAN
equipment for security and compartmentalization).
MAU Media Attachment Unit (IEEE 802.3) or multistation access unit (IEEE 802.5).
In IEEE 802.3, a device that performs IEEE 802.3 Layer 1 functions, including
collision detection and injection of bits onto the network. A MAU is referred to
as a transceiver in the Ethernet specification. IEEE 802.5 MAUs (sometimes
called MSAUs so as not to confuse them with IEEE 802.3 MAUs) are wiring
concentrators to which token ring lobes attach.
Networking the communication of data between two systems utilizing a protocol over a
given topology.
NIS Network Information Service – Sun Microsystem’s proprietary Naming
Service to provide for centralized administration of name, address and services
information.
NFS Networked File System –Unix boxes use this to mount and view remote
directory trees.
OSI Open Systems Interconnect – a reference model showing the layers used for
network communications (defined by the ISO … International Standards
Organization).
OSPF Open Shortest Path First – optimized internal gateway protocol, just exchanges
changes to route table, provides support for variable length subnet masking
PPP Point-to-Point Protocol – common way to define a network connection over a
modem.
protocol set of rules that govern the orderly exchange of data.
RIP Routing Internet Protocol – early interior gateway protocol – inefficient,
transfers entire routing table to all neighboring routers.
RPC Remote Procedure Call – client/server method to execute remote commands.
SLIP Serial Line Interface Protocol – early precursor to PPP.
SMTP Simple Mail Transfer Protocol – TCP/IP protocol used for sending email to
servers, most email clients these days use the POP3 or IMAP protocols to pull
email off the servers.
SNMP Simple Network Management Protocol – used by network equipment for
management and monitoring.
SONET Synchronous data transfer over Optical media Networking – standards for
international high-speed data exchange.
TCP Transmission Control Protocol – reliable connection-oriented services – FTP,
Telnet, SMTP – larger data payloads or applications that need real-time
response and interaction. This is like a person-to-person collect phone call or a
registered-returned-receipt document sent through the mail. In either case
extra care and steps are taken to be sure that the appropriate parties are
connected for the exchange.
Telnet Terminal Emulation over the Network – window for terminal session login to
command-line operations on certain types of computers.
TFTP Trivial File Transfer Protocol – insecure method to push data (like router
config files).
topology networking media and its style of deployment.
UDP User Datagram Protocol – unreliable connectionless services - RIP, DNS,
SNMP, NFS, TFTP - small data payloads that are easy to retransmit and do not
require setting up the overhead of communication tracking. Can be like a
Town Crier, announcing the current time, weather or news headline of interest
(RIP, DNS). Or can be like a mother calling to a child to come to dinner,
where the message is on the wind and she hopes they heard it but cannot be
sure; and the child calling back a reply is just as unsure if she actually heard it
(NFS, SNMP).
WAN Wide Area Network - collection of LANs across the street, town, state,
country, world via gateways to high-speed topologies.
XDR External Data Representation – defines interchangeable data format between
computers with different processor architectures and data formats.
Note: A more comprehensive glossary can be found in Appendix B of this manual.
OSI REFERENCE MODEL

7 Application programs use network calls to access data (FTP, Telnet, SMTP, DNS, etc.)
6 Presentation standardized data presentation to programs (XDR)
5 Session managed connections between applications (RPC)
4 Transport end-to-end data delivery, error detection and correction (TCP, UDP)
3 Network manages network delivery path (IP Routing), shields addressing from upstream
2 Data Link manages data hardware path (IP Frames with MAC addresses)
1 Physical hardware interface characteristics (Connectors, Voltages, Signal Interpretation)
EXAMPLES OF COMMONLY KNOWN PROTOCOLS

LAN Protocols TCP/IP, IPX (NetWare), AppleTalk, DECNET/LAT, Token Ring
WAN Protocols SLIP, PPP, SW56, X.25, 56DDS, ISDN (BRI/PRI), Frame Relay, FT1, T1,
SONET, T3, ATM
Routing Protocols Interior: RIP, IGRP, OSPF Exterior: EGP, BGP
TCP/IP PROTOCOL LAYERS
TCP/IP (Transmission Control Protocol / Internet Protocol) uses a simpler four-layer model
to define and describe its elements of data communication across the network. Some TCP/IP layers
correspond to several OSI layers.
• Application - programs & data presentation

OSI Layers 7 & 6 & 5
• Host-to-Host Transport - connections and end-to-end error detection and correction
OSI Layer 4
• Internet - defines datagram and handles routing of data (IP address + protocol ID)
OSI Layer 3
• Network Access - access data links through the physical network (Ethernet address)
OSI Layer 2 & 1
PACKETS ON THE WIRE

It is important to understand a simple model of how these packets of information move
through the interface and on/off the “wire”. One of the fundamental network access control methods
used is CSMA/CD (Carrier Sense Multiple Access / Collision Detect). This method says that all
interfaces listen for a quiet period (Carrier Sense) and then anyone can put a packet out (Multiple
Access). They are also listening to see if two or more units tried to put a packet on the wire at the
same time, generating collision signals (Collision Detect). If that happens all back-off for a random
amount of time and try again.
This way everyone gets a fair shot at putting a packet out onto wire. This rule governs
transmissions on shared media (thick-net, thin-net, 10bT hubs, etc.) and also on switched media when
multiple sources are trying to contact the same destination. There is also a rule set that the interfaces
follow which is based upon the destination Ethernet MAC address of the packet (broadcast or not,
targeted to us or not … see the figure in Broadcast Traffic and its effect on CPU performance in
Chapter 3). This rule basically says that all broadcast packets must be evaluated by the host CPU to
determine if that machine can fulfill the broadcast request. All other packets not directed directly to
our Ethernet address as the destination may be ignored.
PACKET (OR DATA FRAME) FORMAT

To better understand some of the sections in the following chapters it is necessary to have a basic
knowledge of how of information is stored in the packets. Here is the very simple layout. The
“meat” of the packet is between the Preamble and the FCS checksum and its size adds up to 1514
bytes, which is the largest allowable Ethernet frame length. Larger payloads are fragmented and
reassembled. The format of the Information section varies with the different layers and applications.
Preamble Destination Source Length “Information” FCS checksum

Unique 64-Bit MAC Address MAC Address
Signature (up to 1500
(6 bytes) (6 bytes) (2 bytes) bytes)
Site Surveys – The Key to Planning
You can only get to your destination or goal if you have a good plan or roadmap to follow. It
helps you know where you are, the path you must take and where you will finally wind up. This is
especially important in network planning since there are many hardware, software and configuration
elements involved. Without proper planning the networking details can turn into a nightmare for the
installer and the local FSE. This planning is important, regardless of whether you are working with a
standard Philips/ADAC network or a custom configuration that will interact with non- Philips/ADAC
equipment on the hospital network. In contrast to years past, most new installs today involve some
kind of custom networking and many existing sites are adding on connectivity to allow them to
leverage today’s data manipulation tools.
It would be a good idea to get access to, and review SOP-76 Product Implementation-
Installation Responsibilities (can be found below the Quality System Documentation page on our
Intranet at http://intranet/departments/doc_control/html/qsr.htm:) to get a good idea of all that goes on
behind the scenes from Order to Install and understand how you, and your tasks, fit into the “Big
Picture”.
SITE SURVEY HIGHLIGHTS

• The Nuclear Medicine Site Survey is a consolidation of the old Planning Network Survey,
DICOM Survey and the old V29 Surveys. We have made a comprehensive questionnaire to
help identify all the aspects you will need to have a successful install. (If you do not have the
latest version then please download the latest .PDF file of the current Nuclear Medicine Site
Survey from the TechPubs page under the Field Service section on the Philips Intranet
http://intranet/departments/field_service/NM/techpubs.html)
• If the networking is part of camera sale, then a service call is opened for a survey to be done
as soon as feasible after purchase becomes official.
• If networking products or services are sold separately, after the camera point-of-sale, then you
must remember to file the 3 networking parts ASAP to allow for adequate planning.
• The planning must be done early on to allow for planning, ordering of equipment and
scheduling of wiring and installation (especially since there is interaction with 3rd parties who
might have long lead times)
• Creating Before and After Network Drawings is essential (PowerPoint is preferred if possible
or .bmp so that anyone can read these without special software. MS-Visio is also a popular
format but requires and expensive software package to create them.)
• It is important to be as complete as possible on the information as it is the guideline for
planning and implementation. After all, the installers will only be implementing the plan that
you helped create and that you will be responsible for maintaining afterwards. It is not the
installer’s job to have to do a plan on-the-fly while trying to get the camera and system up and
running.
SECTIONS TO NOTE
• Customer Site Survey - page 3 of 9 #6 - Special Interfaces better specification of networking
options
• Customer Site Survey - page 7 of 9 #21 - Cable Runs advises customer is responsible for in-
wall infrastructure wiring and that we recommend using all Cat5 10bT
• Physical Site Survey - page 3 of 8 #7 - Network wiring checks for cable lengths and topology
(modified title from old Field Service Survey)
• Overview Networking Site Survey – provides a “big picture” of how network is now and what
changes will be made, and to determine if Custom Network Surveys are needed
• Cluster Networking Site Survey – you need one per cluster, (based on old Standard
Networking Survey), deals with local LAN-based services and configuration, includes the
drawings appendix to specify equipment and cable needs
• Custom Networking Site Survey - required if deemed by criteria in Overview Survey (if so,
need one per Cluster Survey), requires interaction with Site IT personnel, deals with cluster-
to-cluster and cluster-to-3rd_party_equipment communications, this is the place to define
WAN setups, Filtered connections to the Hospital LAN, and definitions of custom hostnames,
IP addresses, defaultrouter (gateway) and NIS domainname.
CUSTOM NAMING SUGGESTIONS

• Philips installation programs have a way for you to accept the default scheme for naming and
numbering which was alright when most of the Pegasys clusters remained an entity unto
themselves and were not connected to the hospital or department network. That has turned
into the exception and the general rule is that a Pegasys cluster is going to be linked up to
those larger networks (if not immediately then sometime soon after installation).
• The reason this is required is that a lot of sites will be using Peg2Peg Transfers to share data
between clusters and network rules state there can be no repetition of hostnames,
domainnames or IP addresses. It also helps prevent NIS cross-binding issues when adding on
new units or having to reload OS and Applications on a failed unit.
• It is good to pick custom hostnames and NIS domainnames that are somewhat personalized to
the initials of the particular institution. Using 2, 3 or 4 characters is optimal and we find that
it works best to have them be the first characters of the customized hostnames.
• The very best time to do this is when we have the opportunity of installing an entirely brand
new site. This will avoid many hours of rework if we have to do the custom naming at a later
date. Many options and peripherals have hostname linkages and they must therefore be de-
installed and re-installed when making the changes on an already established network.
• There are some terse hints to remind you on page 11 of 13 in Custom Network Site Survey
which is a subset of the Nuclear Medicine Site Survey Document CS-16-1*. We will reiterate
those hints here with some additional suggestions. These restrictions are based upon our
limitations and other vendors’ equipment may very well follow other naming rules.
• Hostnames should contain only lower-case letters (NO CAPS) and numbers and begin with a
letter (no punctuation is allowed other than an underscore as a separator). Hostnames are
never made up of all numbers. Don’t confuse the AE Titles for DICOM with hostnames.
They may be, and often are, all CAPS.
• Archiver/Tracker (and perhaps other peripherals) have a 10 character limitation for the
hostnames of the Pegasys units that the software is loaded on. Observe this limitation if your
cluster will (or does) have one of these hostname-length sensitive peripherals installed.
• The 2 or 3 letter site identifiers (4 letters max) must be at the beginning of the hostname and
not tacked onto the end (an example prefix would be cr for “Cain Regional”).
• Pegasys hostnames should differentiate between the older PegasysX and newer PegUltra
systems (eg. cradac# or cradc#, and crultra# or crult#).
• Acquisition PC hostnames should start with the letters pc, cannot exceed 10 characters and
must end in either the number 1 or 2 (eg. pc_crstk31).
• Epic detector hostnames must start with the hostname of the Atlas or acquisition Pegasys, the
system will automatically append “det1” or “det2” (eg. cratl2det1, cratl2det2, or cratl3det1,
cratl3det2).
• Hostnames for the Acquisition PC, Gantry PC and detector heads associated with one Atlas
system must follow a logical naming convention. Since the hostname of the Atlas becomes
the “base” name of the Acquisition PC, Gantry PC and detectors, the Atlas hostname must be
no longer than 6 characters. (For example, if the Atlas hostname is “cratl4”, the system will
generate these other hostnames: pc_cratl41, cratl4gantry, cratl4det1, cratl4det2).
• The new Skylight systems are special in that these internal camera component hostnames and
IP addresses will remain identical on each Skylight in the field. Only the externally visible
WAN port will have a unique hostname and IP address within the department’s scheme.
Important: UPPERCASE hostnames for Philips/ADAC units are NOT allowed! See
page 9 of 11 (Form CS-16-01, “Custom Networking Site Survey) for name specifications.
Also, hostnames containing all numbers are NOT allowed. Hostname must start with a
lowercase letter. DICOM AE_Titles can begin with an uppercase letter and are often
ALL_CAPS.
FILTERING HINTS
• We do our acquisitions live on the network and “hammer the wire” pretty hard. Although
new designs are helping to avoid this problem anything prior to the Skylight cameras has a
network vulnerability.
• Our diskless PCs and Detector heads use bootp, from a local bootp server in each camera, to
request an IP address and, most importantly, a code thread to get up and running.
• Some equipment on hospital networks, DHCP servers and the like, could answer up first and
provide a random IP address and no code thread.
• Philips requires its own local bootp server for reliability and redundancy, validated as such
• Interactivity with certain types of traffic on the hospital network, especially broadcast traffic,
can compromise an Acquisition unit, causing it to lock up and perhaps lose a study (especially
uncool for a stressed cardiac patient) or keep it from booting up quickly following a restart.
• Some sites have tried putting the Ethernet MAC addresses of the PCs and Detector Heads into
“ignore” lists on their DHCP and bootp servers, which would allow our units to come up to
multi-user and satisfy the requests locally and correctly. This seems to be an okay
workaround as long as there is no other traffic that interferes with the actual studies.
• So we talk to the IT Group at the site and strive to arrive at a mutually agreeable filtering
solution of a VLAN, routed subnet, filtering-bridge with ACLs, or 2nd Ethernet cards if
needed.
• A fix that should always be applied on the EPIC and Atlas boxes is the “hardware address not
found” techtip to reduce buildup of chatty messages from bootp and tftpd
NETWORK DRAWINGS
• It is essential to have both Before and After drawings to help visualize transition (some wind
up being done in multiple phases)
• Electronic drawings are preferred (PowerPoint or .bmp) but if you have to reduce and markup
a map that a site has or just do a couple hand drawings then go ahead and E-Fax them in.
• It is very easy to copy and paste from example drawings (or previous plans) and modify them
to fit your needs. There is a document called Readme_Drawings.txt that is available for
download from the …/tac/datashare/network tree on the Intranet.
• Also on that Intranet location there are some plans and proposal drawings to review and make
note of certain characteristics. You’ll find them in netexamples.ppt
• We will go over the simple steps anyone can do in a lab exercise during this course.
Pegasys Networking General Guidelines
• A Pegasys network, or cluster, consists of a Master (NIS, DB, shared-directories) and a

number of clients. A standalone is a network of one, a master of itself.
• The Virtual-DB (which allows all Pegasys in the cluster to seamlessly see all data on all
machines) comes at the price of dependency on a Pegasys Master
• A cluster is manageable within a department or building but not across a WAN or complex
LAN. For those configurations you should go to separate clusters and use Pegasys2Pegasys
Transfer to share data between them.
• Choose Pegasys roles carefully as they govern program and option linkages based upon the
hostnames, which makes redefinition complex, cumbersome and best done by backing up and
starting from scratch (see details in Chapter 5).
• NIS (yp) is the key to our centralized network administration.
• Only one NIS Master per NIS domain is allowed
• Master has template files (in /etc) and dbm-maps (in /var/yp and pushed to slaves)
• All our clients are NIS slaves and must be up & running during network config and
option/peripheral additions for NIS updates
• If factory-fresh (or OS reloaded) standalones named “adac” are not networked in a correctly
phased fashion, cross-binding may occur resulting in improper network configuration
• In PegasysX-PegasysUltra mixed networks the master must be a PegasysX unit.
• All-PegasysUltra network benefits support for the latest options and elimination of the two Gb
partition limit which affects available patient data space.
• PegasysX 3.3x and PegasysUltra 4.2x Field Service Manuals have flow-charts and
enhancements that make it a comprehensive guide to networking an All-PegasysUltra or
mixed PegasysX-PegasysUltra network…..get a copy, study it ahead of time.
• Be sure you follow the rules (backups, connections, bootup order, etc.) as they have been
thought out very carefully. Trying shortcuts cost everyone time and sleep.
• Be sure to do an “Add_Pegasys” on Master before running network_pegx on the client
• Be sure to reboot client after connecting network cable, before running network_pegx
• Make sure you do not have marginal network connections (esp. AUI connectors) and that the
10bT Link/Speed/Duplex indicators show expected status.
• Make sure that all the NIS maps within the Pegasys cluster are not out-of-sync (see details in
Chapter 5).
• If you are creating multiple Pegasys "clusters," (see outline in Chapter 5) be sure that you
build up the separate clusters on their own [temporary standalone] central switch (or hub) and
be sure that the old NIS maps have been cleaned up (see details in Chapter 5). Then, you can
rejoin them all back into the same central switch (or hub).
• Don’t forget you can always reference the Unix “man” pages on your PegX or Ultra
workstations for addition help related to any Unix command. Simply type "man
<command>" and the screen will page through the description of the arguments and the
output interpretation (Press space-bar for next page or ‘Ctrl-c’ to exit). Examples are: "man
ifconfig", "man arp", " man netstat", etc.
Planning for WAN & Complex LAN
The first thing to realize is that custom networking requires planning and investigation. It is
rarely ever a one-day plug-n-play exercise. Early planning allows for time to arrive at a solid plan
and to coordinate on required equipment and cable runs. Your planning stands a much better chance
of success if it is done in conjunction with the department representatives and the Site’s IT Group (if
existing). Keep in mind that our data will be a guest riding around on their network infrastructure.
Remember that you always have the benefit of leveraging more experienced local FSEs and the
Custom Networking Group to help with your understanding of planning, filling in the survey and the
implementation/maintenance of your custom network. Most of the time, the development of a plan is
a very collaborative activity. These are fundamental objectives to cover in the planning process:
• Identify reasons to custom network and new requirements
• Identify existing resources and limitations
• Plan and acquire missing resources
• Coordinate with all parties on phased implementation
• Schedule Philips/ADAC assistance if needed
• Heeding the guidelines
REASONS TO CUSTOM NETWORK

There are some sites that simply state that all computer equipment must be connected to their
network infrastructure, even if that machine does not need to communicate with others on the
network. However, nearly always there is a compelling reason that requires this type of connectivity.
Here are some of the more common reasons that we run into:
• A complex LAN requiring use of site network to overcome distances and workgroups
• Philips/ADAC Connectivity Products (LAN or WAN):
o Network-based Peg2Peg Transfer
o Printing/Formatting to site’s network printer
o DICOM (Print, Transfer, Worklist)
o Interfile Transfer
o Remote Viewing Packages (WebView, Shadow, AutoquantMD, ENsphere)
• NUMA data format conversion
• 3rd Party Packages (Joe Areeda's SeeMor, Dr. Mark Wittry's NucMed-Image, etc.)
• Desire of site’s network admin to have everything networked
FUNDAMENTAL SITE INFORMATION

Some basic questions to consider during the planning process:
• Are there any preconceived implementation plans? (Contact the IT department)
• What are the expectations for data throughput?
• How many sites are involved?
• Are there existing networks to be used?
• Are there existing site admins at any or all locations (if not, you and the Custom
Network Group will need to develop the plan)?
• Are there any restrictive network policies in place (no routers, single source equip.)?
• Have they planned out their Install/Monthly $$$ for WAN budget?
• What walls will equipment be placed next to and can they run a network drop there?
For existing network(s) you will need to attain or create a map detailing IP addresses,
hostnames, subnet masks, routers, bridges, switches, repeaters, etc. Two views are required, one as
it is now and one as it is desired to be.
CABLE RUNS AND EQUIPMENT

Aside of ensuring the technical feasibility of the desired data communications plan, some of
the most important components that need to be properly planned are cables and connectivity
components.
• We are responsible for in-room wiring up to wall ports. The site must run the
infrastructure through their walls and ceilings (there are reminders and signoffs on the
Customer, FS and Network Cluster Surveys). This is because the site facilities folks
are bonded and trained to run the cables according to state and local building codes.
• The cables and equipment that we provide should be selected from drawings located at
the end of the Networking Cluster Survey. Just indicate the quantity required in the
space on the drawing and submit the survey. Your CMT will make sure the
equipment is added to the order. Be sure to indicate if some components have special
requirements (like early shipping times).
• If any special or alternative equipment requirements come up during the planning
process, this should be handled by letting your CMT know what needs to be added.
COMMUNICATION IS KEY
• Discuss equipment location and wiring drops with local IT department early enough
for runs to be completed by install time (follow up to leave nothing to chance).
• Discuss filtering options with site’s IT Group early enough so correct equipment can
be ordered and installed (again follow up to be sure it is ready)
• Be sure that if the site’s IT Group is providing addressing and DICOM configuration
information, that you get it early enough to have the Custom Networking Group run
through it for a sanity check and so that it can be posted to the CMT drive so that the
installer can have access to it (if you can get the info on the survey before you submit
it, so much the better!)
PLANNING AND ASSISTANCE FROM THE CUSTOM NETWORKING GROUP

Be sure to be complete about all information, especially on the Network Overview Survey
where you check off if something is being done now or in the future. If possible provide some notes
on what future timeframe the site is considering.
Also, and most important, don’t forget to circle the correct answer (Y or N) to the last
question on whether you need help from the Custom Networking Group. If you do not give an
answer then we assume no help is required and that you have everything under control.
So what happens if a customer decides at install time that they need things to be hooked up to
the network? Although it may not be what the customer wants to hear, you should tell them that this
is an unscheduled development and that a proper plan will need to be drawn up to ensure a successful
configuration.
Sometimes this will involve additional charges for equipment, software and configuration
time to implement their desires that were expressed at the last minute. Try to impress upon them that
it is better to do it right than to do it rushed.
CUSTOM NETWORK GUIDELINES

• Each cluster (master with clients, or a standalone) needs unique network info (hostnames, IP-
addresses, NIS domainname). They might share the same subnet mask and defaultrouter
address but this is not always the case. The naming and numbering scheme might be dictated
by the site’s IT Group, department representatives or may have been assigned by you and the
Custom Networking Group. All that information should be spelled out on the worksheets in
the Network Custom Survey.
• Do NOT change network roles or positions in the cluster numbering scheme. If you want to
do that, you will need to go through the lengthy process of doing critical backups, deleting
options and peripherals, putting all units into emergency_standalone mode, re-networking
with network_pegx, and loading all options and peripherals again.
• When using network_pegx to create a custom cluster from existing Pegasys units, beware of a
potential problem (bug), when blending patients from the clients into the database. To make
sure you encounter no data loss …BACK UP EVERYTHING FIRST!!!
• Custom networks very often require a special subnet mask value and nearly always have a
defaultrouter (default gateway) value. Be sure that those targets out on the other subnet have
a default gateway value setup so they can return response packets back to us.
• Clusters with acquisition units that pre-date the Skylight breed of camera (Atlas and earlier)
need filtering from extraneous network traffic (segregating the broadcast domain) due to
timeout sensitivity from running diskless PC-NFS. Problems can show up at boot time and
keep the diskless components from coming up correctly. There may also be problems at
acquisition time where excessive broadcasts cause the heads to miss a handshake resulting in
a timeout and potential loss of the current study.
• Be sure that if you are customizing to a new NIS domainname that you’ll need to clean out
the remnants of the old domainname to avoid cross-binding issues (more on this in Chapter 5)
• In certain cases where just the IP addresses, subnet mask and defaultrouter are being changed,
it is possible to use a manual editing procedure to effect these changes. (See Manual Shortcut
Procedure in Chapter 3)
• Although many find it easier to use textedit you should get used to VI as you will
undoubtedly have to use it someday, (See command summaries in Chapter 7). Remember: if
you use textedit you should remove the <filename>% backup files.
• The “lcal” acquisition calibration program requires you to keep the same ending numerical
digits for your pc_stack name when renaming it and keep them <= 10 characters (see Custom
Naming Suggestions).
• Be sure when you’re done with Pegasys and Acquisition Cameras that you change the
configuration file(s)/Setup on other units like Codonics printers, NUMA, etc. per instructions
found in their Installation Manuals and User Guides.
Network Configuration Examples
On the following pages you will find examples of different types of networking
configurations for Pegasys clusters of Acquisition and Processing stations. Along with an example
drawing will be a section of important concepts to note and also a section containing an overview of
steps to accomplish the construction of that particular configuration. There is much to be learned and
understood by comparing the different types and observing their differences and similarities.
STANDALONE ULTRA AND ATLAS NETWORK
Note #11: The central connectivity switch should be places in a central location (or
wiring closet) so that all Philips/ADAC equipment can be connected to it.
Note #14: One newer Atlas systems ensure the straight through cable plugs into
appropriate uplink port of the 8 Port 10/100 Switch to provide uplink light.
(See Installation Instructions for Atlas Universal Network Upgrade Kit 9343-
2263). However, the older Atlas systems come with a 2150-5616 straight thru
cable from 4 Port 10 Mbit Hub to RJ-45 Panel. You must replace that straight
through cable with a 2150-5618 crossover cable
Note #15: In non-Power Pack Forte systems, tie wrap twisted pair cable to the umbilical
cable from the Forte Gantry PC to the 8-Port 10/100 Switch in the Atlas rack.
(See Installation Instructions for Atlas Universal Network Upgrade Kit
9343-2263).
Note #16: For optional Thinnet wiring connections, see Installation Instructions for Atlas
Universal Network Upgrade Kit 9343-2263.
Note #17: At Gantry PC and Atlas PC, remove BNC “T” and insert 10 Base T cable. If
PC Ethernet card is not type SIIG, you will have to do software configuration
to change from Thinnet to Twisted Pair per 9202-0143* (FSM,ATLAS S/W
INSTALL,FOR V5.1), page 53-54, Step #8.
Standalone PegUltra/Atlas Concepts

1. In a standalone PegUltra/Atlas environment, you should use a central, external 10/100
switch. Although it is possible to connect the Atlas directly to the back panel of the Peg Ultra, using
a switch has significant advantages not available with a direct connection, such as the ability to easily
expand your network with the following:
• network formatters,
• another Peg Ultra, or
• a new camera system.
2. In the above configuration, the Atlas interfaces to a Philips/ADAC camera. An Atlas

can also interface to a generic camera, but it requires an Atlas Generic (2152-3016*). Simply
connect the ADC to an Isolation Box, which will interface to the generic camera. An Atlas computer
can interface to only one camera at a time. Here is a de-cluttered view of that hookup.
Atlas Generic Camera Hookup
Standalone PegUltra/Atlas Networking Guide

1. Check operation of the system prior to running network_pegx to be sure you can
acquire and process an image.
2. Do not install any peripheral network devices or systems prior to running

network_pegx. In fact, if any are installed, they must be deleted.
3. Follow the instructions in the 9202-0142* (FSM, PEGULT SW INSTAL/CONFIG )

manual, for running network_pegx. Choose the option for ‘Master of Pegasys
Network’. Be sure to reboot the master Pegasys once the configuration is completed.
(You do have the opportunity to select a custom configuration, which lets you assign
site specific hostnames, IP addresses and NIS domainname. Be sure you have
completed the planning steps first to have all the information ready to enter.)
4. Run the Master Configuration script as shown in manual 9202-0142* (FSM, PEGULT
SW INSTAL/CONFIG ) under ‘Running Master Configuration on the Master’.
5. Reboot the Pegasys workstation.
6. Follow the instructions in the Atlas Acquisition Software Installation Manual (p/n
dependent on acquisition software version and camera type) for adding the Atlas
systems to the network. The steps that need to be performed are as follows:
• Preparing for software installation and networking- determine hostnames, IP
addresses, and Ethernet addresses (detectors and Net PC)
• Reconfigure the Atlas on the Network
• Connect the Atlas to the network
• Install/Update the Acquisition Software (EPIC, Binner, and PC Acq SW)
• Modify the Network Configuration.
• Adding an Atlas to the Database Host
• Creating the Net PC boot disk
• Completing and Verifying the Atlas Installation
• Install the Y2K compliant version of the Atlas Image Server to avoid possible
mixed data issues on your network (Version 5.1 Atlas Acquisition contains the
“2010” deviation). There is more than one way to accomplish this; please
consult the informational tips or contact technical support.
7. Install any optional software and peripherals on this standalone network.
NETWORKED ULTRA AND ATLAS SYSTEMS
Item #10: 10/100bT Crossover Cable (2150-561x).
(See document 9343-2263 “PROC,ETHERNET SWITCH INSTALL”).
However, the older Atlas systems come with a 2150-5616 straight thru cable
from 4 Port 10 Mbit Hub to RJ-45 Panel. You must replace that straight
through cable with a 2150-5618 crossover cable.
Note #9: In a subnet, if the central connectivity is a hub (rather than a switch) and if the
total number of hubs or repeaters exceeds four, you must rewire the PegX and
Atlas systems to exclude hubs inside PegX and Atlas (unless hubs in PegX or
Atlas have been upgraded to switches).
Note #11: The central connectivity switch should be placed in a central location (or
Networked PegUltra and Atlas Systems, Concepts

1. In an all Peg Ultra/Atlas Network you will connect systems to each other with a
central switch. When you configure systems, use a straight-through cable from the end-device to the
switch. If you need to connect two switches/hubs together then you need to use a crossover cable (or
a straight-through cable to the appropriately configured uplink port).
2. In the above configuration, the Atlas interfaces to a Philips/ADAC camera. An Atlas

can also interface to a generic camera, but it requires an Atlas Generic (2152-3016*). Simply
connect the ADC to an Isolation Box, which will interface to the generic camera. An Atlas computer
can interface to only one camera at a time. See Atlas Generic Camera Hookup.
3. A PegUltra can be the Database Host to two Atlas units. However, in an effort to
spread out the patient data load, it is best to assign one Atlas to one PegUltra.
4. This Networked cluster configuration can support:

• an analog hard copy formatter,
• a digital printer
• a network formatter.
• A variety of local data converters and remote viewers (NUMA, Shadow,
WebView)
Networking Guide - Networked PegUltra/Atlas Systems

(multiple)
To network multiple Peg Ultras with Atlas acquisition systems, perform these steps:
1. Check operation of both systems as standalone units to be sure you can acquire and
process an image.
2. Do not install any peripheral network devices or systems prior to networking the two
units together. In fact, if any are installed, they must be deleted.
3. On the system being setup as the network master, follow the instructions in the
9202-0142* (FSM, PEGULT SW INSTAL/CONFIG) manual, for running
network_pegx. Choose the option for ‘Master of Pegasys Network’. Be sure to reboot
the master Pegasys once the configuration is complete.
4. Perform the steps for ‘Running Add/Delete Pegasys on the Master’ from the
9202-0142* (FSM, PEGULT SW INSTAL/CONFIG) manual and add the client
system to the network.
5. Connect the Client network cable to the Master.
6. Reboot the PegUltra client with the network cable connected. Follow the instructions
in the manual 9202-0142* (FSM, PEGULT SW INSTAL/CONFIG) for ‘Networking
the Client’, and run network_pegx. Choose the option for ‘Client of Pegasys
Network’. Be sure to reboot the client once the configuration is completed.
SW INSTAL/CONFIG) under ‘Running Master Configuration on the Master’.
8. Reboot all the Pegasys workstations on the network starting with the master.
systems to the network. The steps that need to be performed are as follows:
“2010” deviation). There is more than one way to accomplish this; please consult
the informational tips or contact technical support.
10. Repeat Step 9 for each Atlas being added.
11. Install any optional software and peripherals on the network.
TWISTED PAIR MIXED ENVIRONMENT NETWORK
(See document 9343-2263 “PROC,ETHERNET SWITCH INSTALL”).
However, the older Atlas systems come with a 2150-5616 straight thru cable
from 4 Port 10 Mbit Hub to RJ-45 Panel. You must replace that straight
through cable with a 2150-5618 crossover cable
Note #9: In a subnet, if the central connectivity is a hub (rather than a switch) and if the
total number of hubs or repeaters exceeds four, you must rewire the PegX and
Atlas systems to exclude hubs inside PegX and Atlas (unless hubs in PegX or
Atlas have been upgraded to switches).
Item #19: RJ-45 Twisted Pair coupler (5090-9643)
Twisted Pair Mixed Environment Network Concepts

1. All new Philips/ADAC networks should be run on Cat5 10bT Twisted Pair wiring
connected to a centrally located 10/100 switch. This configuration allows for better
debugging and repair work when units are connected with a single point-to-point
connection, rather than in a serial fashion as in a Thinnet chain.
2. In a mixed (PegX and Ultra-Atlas) network, a PegX computer must be the master.
Important: It is recommended that the PegX master be upgraded to have at least 64MB
of CPU memory and should be the fastest Peg X computer in the network.
3. You cannot have more than four repeaters in a subnet. Each Hub counts as a repeater,
including those within the Atlas. Using a switch as your central connectivity helps to
alleviate this as each switch port is segmented and allows you to have a hub at the end.
It also helps if any qualifying Atlas units are upgraded to have internal switches
instead of hubs.
4. The central 10/100 Switch connects all peripherals and computers to each other. This
is called a STAR configuration network topology. There is a 100 meter (326 ft.) limit
of the Cat5 10bT twisted pair cable so choose your central location so that it will reach
all units in the subnet.
Twisted Pair Mixed Environment Networking Guide

To network a PegX and a PegUltra together, perform the following steps:
REMEMBER: The PegX must be configured as the network master.
1. Check operation on both systems to be sure you can acquire and process an image.
2. Do not install any peripheral network devices or systems prior to networking the units
together. In fact, if any are installed, they must be deleted.
3. On the system being setup as the network master, follow the instructions in the 9202-
0142* (FSM, PEGULT SW INSTAL/CONFIG) manual (9202-0117* “FSM,
PEGASYSX V3.40” for PegX), for running network_pegx. Choose the option for
‘Master of Pegasys Network’. Be sure to reboot the master Pegasys once the
configuration is complete. If you are configuring a PegX acquisition unit you will be
prompted to configure and update the Acq boot floppy during the network_pegx
session.
4. Perform the steps for ‘Running Add/Delete Pegasys on the Master’ from the 9202-
0142* (FSM, PEGULT SW INSTAL/CONFIG) manual (9202-0117* “FSM,
PEGASYSX V3.40” for PegX) and add the client system to the network.
5. Connect the Client network cable to the Master.
6. Reboot the PegUltra client with the network cable connected. Follow the instructions
in the manual 9202-0142* (FSM, PEGULT SW INSTAL/CONFIG) for ‘Networking
the Client’ (9202-0117* “FSM, PEGASYSX V3.40” for PegX), and run
network_pegx. Choose the option for ‘Client of Pegasys Network’. Be sure to reboot
the client once the configuration is completed.
SW INSTAL/CONFIG) under ‘Running Master Configuration on the Master’ (9202-
0117* “FSM, PEGASYSX V3.40” for PegX).
8. Reboot all the Pegasys workstations on the network starting with the master.
9. Repeat steps 4-8 for all clients being added to the network.
systems to the network.
The steps that need to be performed are as follows:
“2010” deviation). There is more than one way to accomplish this; please consult
the informational tips or contact technical support.
11. Repeat Step 10 for each Atlas being added.

12. Install any optional software and peripherals on the network.
THINNET-ONLY MIXED ENVIRONMENT NETWORKING
Item #3: Thinnet to 15 pin AUI Transceiver (5200-3011).
Item #5: 50 ohm terminators (5090-9251) installed on each end of the Thinnet run.
Item #6: BNC Tee connector (5090-1157). Avoid creating the “Dreaded-T Syndrome”.
Do not add a Thinnet cable between the Tee and the Transceiver.
Item #8: 15 pin AUI cable (2141-10xx).
Item #9: Sun MII-AUI converter (5200-3415). Does not require power supply if
operated with 5200-3011 Transceiver.
Note #10: In a subnet, if total number of hubs and repeaters exceeds four, you must
convert from Thinnet to Twisted Pair and rewire PegX and Atlas systems to an
external switch. (See Reduced Repeaters (Hubs) in a Network).
Item #21: BNC barrel connector (5090-3001). Use a barrel, not a Tee, to join two
lengths of RG-58 cable.
Item #23: Thinnet-Twisted Pair Transceiver (5200-3001).
Thinnet-Only Mixed Environment Networking Concepts

1. This Thinnet configuration is a BUS network topology whose backbone consists of
lengths of coaxial cabling, connected by tees from which hang end-unit transceivers.
The entire run is terminated by a resistive load at each end.
2. In a mixed (PegX and PegUltra/Atlas) Thinnet environment, you will install 50 ohm
RG-58 BNC cabling between systems and networked peripherals. The maximum
length of all the BNC cabling cannot exceed 600 feet in any one segment. If you need
to extend the reach of a Thinnet network you will need to use a Repeater (5200-1887).
3. In a mixed (PegX and Ultra-Atlas) environment, a Peg X computer must be the

network master.
Important: It is recommended that the PegX master be upgraded to have at least 64MB
of CPU memory and should be the fastest Peg X computer in the network.
4. Philips/ADAC will not create new Thinnet networks. Unless long Thinnet cable runs
already exist, and the site balks at paying for an upgrade, you should consider
converting Thinnet networks to twisted pair. Conversion may require installation of
converters and a switch, but has many advantages in improved reliability and the
ability to easily debug.
5. In this configuration, do not deviate from the internal network cabling shown on the
previous page. Our products are designed and validated with specific internal network
component configurations. Deviations may result in unpredictable and unreliable
network performance. Take care not to create the “Dreaded-T Syndrome”.
6. The “greater than or equal to four” repeater rule (or 5-4-3 rule) also applies to Thinnet
networks. If your network has more than four repeaters, you will need to convert the
existing Thinnet network to 10bT so that you can use a centralized 10/100 switch.
You’ll need individual Cat5 lines for the Sun, PC and the 10bT-BNC Adapter for the
Detector Heads. (See After Rewiring to Reduce Repeater Count for more details.)
Important: Hubs count as repeaters. Don’t forget the ones inside the Acq. Cabinets
when you’re tallying them up.
7. Notice that the Ultras are restricted to 10 Mbit transfers even though capable of 100
Mbit (because of the thinnet 10Mbit limitation)
Thinnet-Only Mixed Environment Networking Guide

Follow the same steps as in Twister Pair Mixed Environment Networking Guide
THINNET-TWISTED PAIR MIXED ENVIRONMENT NETWORKING
Item #1: 10/100 Switch - 24 port (5200-3679) or 8 port (5200-3657)
Item #4: 50 ohm RG-58 Coaxial cable (2141-07xx)
Item #5: 50 ohm terminators (5090-9251) installed on each end of the Thinnet run.
Item #6: BNC Tee connector (5090-1157). Avoid creating the “Dreaded-T Syndrome”.
Do not add a Thinnet cable between the Tee and the Transceiver.
Item #10: 10/100bT Crossover Cable (2150-561x)
Item #20: 10 Mbit Hub – 8 port (5200-3509)
Item #21: BNC barrel connector (5090-3001). Use a barrel, not a Tee, to join two
lengths of RG-58 cable.
Note #1: Older Atlas systems come with a 2150-5616 straight thru cable from the 4 Port
10 Mbit Hub to the RJ-45 Panel. You must replace straight thru cable with a
crossover cable by ordering an Item #10. New Atlas systems come with a built
in 8 port 10/100 switch and this cable is left as a straight thru and it is plugged
into the appropriate port to get a link light.
Note #10: In a subnet, if total number of hubs and repeaters exceeds four, you must
convert from Thinnet to Twisted Pair and rewire PegX and Atlas systems to an
external switch. (See Reduced Repeaters (Hubs) in a Network).
Note #14: Ensure straight through cable plugs into appropriate uplink port to provide
uplink light.
Thinnet-Twisted Pair Mixed Environment Networking Concepts

1. When a site has and extensive Thinnet infrastructure and it is logistically (or cost)
restrictive to completely rewire for Twisted Pair, they may choose to “hang” Twisted
Pair off the Thinnet backbone. The concepts found in Twister Pair Mixed
Environment Networking Concepts apply to the Twisted Pair section and those in
Thinnet-Only Mixed Environment Networking Concepts apply to the Thinnet run.
The exception is that any of the Ultras connected to the 10/100 switch may have 100
Mbit transfers, as can any Atlas with an internal 10/100 switch instead of a hub.
Thinnet-Twisted Pair Mixed Environment Networking Guide

Follow the same steps as in Twister Pair Mixed Environment Networking Guide.
REDUCED REPEATERS (HUBS) IN A NETWORK
Before Rewiring to Reduce Repeater Count
After Rewiring to Reduce Repeater Count
Item #7: 15 pin AUI to 10baseT Transceiver (5200-3282).
Item #18: 10BaseT straight thru cable, 3’ (2150-5616)

(To connect to extra RJ-45 panel jacks on Atlas Universal AXi only)
Item #19: RJ-45 Twisted Pair coupler (5090-9643)
Note #12: If the central connectivity is upgraded to a switch then multiple lines to Atlas
and PegX Tower are unnecessary. Instead you would use single uplinks as
shown in the section Twisted Pair Mixed Environment Network).
Reduced Repeaters in a Network Concepts

1. If at all possible, replace the central connectivity with a 10/100 switch instead of a
hub. This will avoid having to do this multiple wiring all together since each
segmented port of a switch can have a hub connected at the end of it. Sometimes
though, we are locked into having a hub as the central connectivity and then this
method applies.
2. The diagram Before Rewiring to Reduce Repeater Count shows PegX, PegUltra and
Atlas systems. Hubs count as repeaters. The repeater count is three, but if you add
more systems you will exceed the limit of four repeaters in a physical subnet. It is
very important not to exceed four repeaters, because the collision rate will increase
and the Department Ethernet can halt the systems on the network. Repeaters in a
network represent a bottleneck to IP broadcasts. If there are too many repeaters
(bottlenecks), network traffic will slow down and collisions will occur.
3. The diagram After Rewiring to Reduce Repeater Count shows how to bypass the hubs
in the Atlas and PegX systems. You will use the existing 10baseT-to-BNC converters
for the EPIC detector heads. To interface the PegX Acquisition PC to the hub, you will
need to obtain a 10baseT-to-AUI transceiver.
4. In the older PegX based Acquisition Tower, the NIC card in the PC will need to be
reconfigured to speak out the AUI port. Flip the little switch (older boards do not have
a slide switch, instead, they have a set of jumpers on the board which allow thin/AUI
as a choice) on the Ethernet Card (5200-1196) from BNC to 15-pin setting after
removing Thinnet Tee and attaching AUI cable.
CUSTOM NETWORKS ON A LAN/WAN
Custom Networks on a LAN/WAN Concepts

1. It is important to remember that when we perform custom networking, to join our
Pegasys cluster to a Department or Hospital network, our computers and their data are
“guests” of that larger network. We cannot dictate a network configuration because it
is easy for us to install and maintain, but rather we must conform to their guidelines
and arrive at a compromise configuration that also meets our needs.
2. Due to some design constraints in our product line we have certain vulnerabilities to
certain types of network traffic, which require us to have a filtered connection to the
Department or Hospital network. The majority of issues center around
BOOTP/DHCP interactions between our diskless devices (detector heads and Acq
PCs) and certain boot servers that may be on the Sites network. There are several
possible filtering techniques (VLANs, Routers, Second Ethernet Cards) which need to
be evaluated during the Site Survey process to see which method can be
accommodated at the Site. (See more in the section on Filtering Hints)
3. Nearly all the time you will need to reconfigure the members of the Pegasys cluster
with unique hostnames, IP addresses, defaultrouter (gateway) address and NIS
domainname. It is often advisable to prepend (prefix) the names with a 3 or 4 letter
abbreviation of the sites name (See the earlier section Custom Naming Suggestions).
Sometimes all you need to do is change the IP addresses, netmask and defaultrouter
(gateway) address and you can use the Manual Shortcut Procedure in Chapter 3. In
very rare occurrences you will be able to use a router and keep all our information
(hostname, IP addresses, etc.) as they already are configured [very convenient but very
rare].
4. Sometimes the WAN connection is accomplished by a private point-to-point digital

connection (ISDN, T1, Frame-Relay, etc.), which does not go through the Site’s
network. The Pegasys clusters on each end must still have unique hostnames, IP
addresses, defaultrouter (gateway) address and NIS domainname. These point-to-
point connections should be purchased by the customer from the Line Service
Provider (LSP) and include the Routers and other equipment and cables, the line
installation and monthly rate. This allows us to make a solid demarcation of service
responsibility between our equipment and that of the digital connection.
5. Most Cat5 connections are done using a straight-through cable between the switch and
the end-device. Sometimes on hub-hub, switch-switch or switch-hub connections you
will need to use a crossover cable but usually these devices have a separate or special
switchable uplink port. Make sure you have a good link light on each end.
Custom Networks on a LAN/WAN Guide
Follow the same steps as in Twister Pair Mixed Environment Networking Guide to setup the
Pegasys cluster. Be sure to use the custom hostnames, IP addresses, netmask and defaultrouter
(gateway) values that were assigned (or agreed to) by the site’s IT Administrator. Custom
configuration of the various options is covered in different sections of this manual and in the manuals
for the individual product options. The required information for all of these should be collected and
noted in the site surveys well ahead of install time. These surveys should be submitted a minimum or
4 or 5 weeks in advance of the targeted install date. This allows time for review, ordering parts and
getting cables run. (Consult SOP-76 Product Implementation-Installation Responsibilities)
CUSTOM NETWORKS ON HOSPITAL LANS WITH SECOND ETHERNET CARD
Item #11: 10/100bT Enet Card 10/100 Mbit: Ultra1 (5200-3224) or Ultra60/10 (5200-
3541)
Item #12: 10bT Enet Card PegX 10 Mbit (5200-3310)
Custom Networks on Hospital LANs with Second Ethernet Card

Concepts
1. The 2nd Ethernet card is a per-system, non-scalable, less attractive filtering solution
and it is not the configuration preferred by Philips/ADAC. However, certain restrictive
environments may require its use, such as when the sites IT group is not able to allow
or provide a filtered VLAN or router segment, or when there is a drastic shortage of IP
addresses. Whenever possible, a more general solution is desirable, such as using a
central router or a switched VLAN mechanism to our subnet in the Nuclear Medicine
Department. (See more in the section on Filtering Hints)
2. The most undesirable thing about using the 2nd Ethernet Card is that it must interrupt
the host processor (CPU of the Pegasys) for each broadcast packet it sees. In a
broadcast-rich environment this could steal a very real percentage of processing cycles
away from performing its regular data storage and processing tasks. On older PegX
based EPIC acquisition units certain types of broadcast traffic may result in messages
accumulating in the /var/adm directory and potentially could choke the root partition,
bringing the system to a halt. Furthermore, because each Pegasys unit in a medium to
large network might need connectivity, each would need to have its own 2nd Ethernet
Card.
3. The 2nd Ethernet Card allows a Pegasys to access both the hospital network as well as
our local LAN (which we often refer to as Department Ethernet). The operating
system prevents the hospital network’s extraneous broadcasts not addressed to our
systems from contaminating our local network. This allows the acquisition and
processing on our private LAN subnet without interference form unwanted traffic that
could disturb our operations. Also, important operations, like committing studies from
an Atlas to its Ultra Database Host, will not be subject to failures on the hospital
infrastructure.
4. Each 2nd Ethernet Card needs to be assigned an IP address for Hospital address range.
Additionally you will need to know the subnet mask and defaultrouter (or gateway) IP
address for that subnet (if there is no defaultrouter value then you can use the IP address of
the 2nd Ethernet Card itself). Once configured and operational you can use a network
configuration like this for sending images to a:
• PACs network,
• DICOM Printer/Formatter shared by other units (Ultrasound, CT, etc.)
• Peg Ultra or PegX system in another part of the hospital or across town using
Peg2Peg software over an upstream WAN connection.
Custom Networks on Hospital LANs with Second Ethernet Card

Guide
The same caveats for planning apply here as seen in Custom Networks on a LAN/WAN
Concepts. The steps to install and configure the Second Ethernet Cards can be found in Chapter 3 in
the section Installing a 2nd Ethernet Card (Software & Hardware)
SKYLIGHT/JETSTREAM NETWORKING
Note #18: The external (WAN) interface of the DSL Cable Router must be assigned a
unique IP address in the same Department Ethernet subnet as the Ultra to
which it will be committing data. The address will be 192.9.200.X in the
default Philips/ADAC scheme.
Note #19: Hospital facilities or IT groups must run 10/100bT cables in walls/ceilings and
provide wall-mounted RJ-45 panel jacks.
Skylight/Jetstream Networking Concepts

1. The Skylight/Jetstream acquisition products have a great improvement in the system
architecture over the older PegasysX & Atlas based products in that their acquisition
network components are internalized behind a filtering device. Data only becomes
visible to the Department Ethernet subnet when it is being committed to the Ultra
Database Host. All of the components remain behind the filter and immune to
interference from extraneous network traffic.
2. The internal hostnames and IP addresses of each of the components (Ultra-AXi, Acq
PC, Gantry PC, Detector Heads #1 and #2) are the same on each and every
Skylight/Jetstream that is installed in the field and they must NEVER be changed.
3. The unique address assigned to the WAN port of the filtering device must be in the
same subnet as the Ultra Database Host. This can be in the standard Philips/ADAC
numbering scheme or in the Hospital’s numbering scheme if the Pegasys cluster has
been custom networked. The appropriate addresses and mask values for that WAN
port are configured at the time the Skylight/Jetstream acquisition software is loaded.
4. In a network consisting of only Ultras and Skylight/Jetstream units (i.e. no older

Philips/ADAC equipment) there should be no need for further upstream filtering when
doing a custom network connection to the Hospital network.
5. The Skylight WAN port is only 10Mbit half-duplex.
CARDIOMD NETWORKING
Note #19: Hospital facilities or IT groups must run 10/100bT cables in walls/ceilings and
provide wall-mounted RJ-45 panel jacks.
CardioMD Networking Concepts
1. The CardioMD acquisition products were envisioned to be primarily deployed in
smaller clinic settings but they perform just as well in larger hospital settings. Since
the primary acquisition data pathway inside the camera is on a FireWire bus (not on
the network) we do not have to worry about network traffic interference as we have on
earlier cameras. If the CardioMD and its Ultra Database Host are the only members of
the cluster there should be no problem with uplinking the Philips/ADAC 10/100
switch to the hospital infrastructure. It is an equally acceptable configuration to
connect these units directly to different ports in the hospital switch.
2. If the CardioMD and its Ultra Database Host are members of a cluster containing the
older acquisition cameras that are susceptible to interference from certain types of
traffic then you would need filtering when uplinking to the hospital network. Usually
this would involve a centralized filtering solution, such as a VLAN or a Router.
3. If the CardioMD and its Ultra Database Host are the only members of the cluster and
there is a significant volume of traffic on the hospital network, you may want to keep
the data commits between the CardioMD and its Ultra Database Host on a quieter
private network. You could optionally connect the CardioMD and the Ultra to an
Philips/ADAC 10/100 switch and then use a Second Ethernet Card in the Pegasys
Ultra to uplink to the hospital network (See section Installing a 2nd Ethernet Card
(Software & Hardware). Note there are different cards for different types of Ultras:
For Ultra-1 (5200-3224) or for Ultra 60/10 (5200-3541).
4. Data is committed from the CardioMD unit to the Ultra Database Host using a
DICOM transfer interface.
5. The DICOM Transfer package must be loaded on the Ultra Database Host and then
follow the configuration steps to add a Remote Server as outlined in the DICOM
Software Release Document (9215-0024*). Then configure the CardioMD for the
Pegasys hostname, IP address and DICOM Port # as per the instructions in Chapter 9
of the CardioMD Service Manual (9202-0204*).
WAN Connection Topics
There are a lot of commonly asked topics about a Wide Area Network (WAN). These range
from what do we use it for (or when is it needed), how fast can it go, how much data will travel over
it and how much time to transfer typical study sets. Usually, several groups want to know this
information to be sure the solution is of sufficient bandwidth to provide the end-user with acceptable
data transfer performance.
WAN HIGHLIGHTS
• Usually used for Peg2Peg or Remote DICOM Print or Transfer (also Remote CPET client
workstations)
• Two types: Philips/ADAC-only and via Hospital LAN (not mutually exclusive but often are)
• Very often, sites already have connectivity and all that is required is to join our subnet onto
their network via custom networking techniques (VLAN, Router, etc.)
• It is always wise to work with site IT administration, if available. After all, it is their network
that we will interface to and our data will travel over.
• We always try to have the site purchase the Equipment, Installation plus Initial and Monthly
Line Charges from a local Line Service Provider (LSP). This helps us to keep a clear
demarcation of service responsibility between the Philips/ADAC Equipment and the WAN
Equipment.
• Faster dedicated (T1) are more expensive although prices are dropping all the time. More
affordable (ISDN) lines are slower, and we must beware of latch-up problems/delays if over
older equipment or long-distance (allotted connection time may expire before negotiations are
through and the conversation can commence). Also, if the ISDN dial-on-demand maintains
connections for better than half the day, the site will usually save money with a Dedicated
Digital Service (DDS) like a T1 line.
• Modem transfers typically will not see speeds better than 33.6 Kbps, since even a retrieve is
just a command to the remote side for them to push. This is why they are just so darned slow.
The technical reason for this limitation on the upload speed is due to Analog to Digital
quantization noise which is inherent when pushing the digital data out through a modem onto
an analog phone line. The quantization noise is avoided when the source computer is on a
direct digital network connection which allows any data being pulled from it to come down at
speeds approaching 56 Kbps.
HOW FAST IS THIS WAN CONNECTION?
(Bandwidth fun… LAN speeds have been thrown in for comparison)
Kbps B/sec KB/sec KB/min MB/min

Transfer Type
(bits) (bytes) (Kbytes) (Kbytes) (Mbytes)
Modem 14.4 1,843 1.8 108 0.11
Modem 28.8 3,686 3.6 216 0.22
Modem 33.6 4,300 4.2 252 0.25
56DDS (frame-relay) 56 7,168 7 420 0.42
ISDN1 (1 * 64) 64 8,192 8 480 0.48
ISDN1C (compress) 88 11,264 11 660 0.66 (act)
ISDN2 (2 * 64) 128 16,384 1 960 0.96
ISDN2C (compress) 184 23,552 23 1,380 1.38 (act)
ISDNPRI ( 23 * 64) 1,472 188,416 184 11,040 11.04
T-1 1,536 196,608 192 11,520 11.52
10MbitLAN 6,144 786,432 768 46,080 46.0 (act)
10MbitMAX 10,240 1,310,720 1,280 76,800 75.0
T-3 43,008 5,505,024 5,376 322,560 322.56
100MbitLAN 61,440 7,864,320 7,680 460,800 460.0 (act)
100MbitMAX 102,400 13,107,200 12,800 768,000 750.0
ATM / OC-3 155,520 19,906,560 19,440 1,166,400 1,166.40
OC-12 622,080 79,626,240 77,760 4,665,600 4,665.60
OC-48 (2.4Gbps) 2,488,320 318,504,960 311,040 18,662,400 18,662.40
Note: Just how fast is an OC-48 connection? A typical processed Gated SPECT is 20
Megabytes. The patient data files could be transferred across the network in 0.05 seconds!
However, if you’re considering having an OC-48 line run to your house to optimize
Internet access, as of this writing the approximate cost is about $450,000 per year…
TESTING THROUGHPUT WITH COMMAND-LINE FTP

Transfer rates may easily be measured in a Unix Window by performing an ftp between two
Pegasys units, here is an example:
PEGASYS@adac:#[2] cd /files/pat # where you want the test file to write

PEGASYS@adac:#[3] mkfile –v 10m junk # create a temporary 10 MB test file
PEGASYS@adac:#[4] chmod 666 junk # make sure test file is fully read-write
PEGASYS@adac:#[5] ls -l junk # verify that it made it and file size
-rw-rw-rw- 1 pegasys 10485760 Jun 3 12:20 junk
PEGASYS@adac:#[6] ftp adac4 # connect to remote system via ftp
Connected to adac4.
220 adac4 FTP server (SunOS 4.1) ready.
Name (adac4:pegasys): rt11
331 Password required for rt11.
Password: adacrt11
230 User rt11 logged in.
ftp> binary
200 Type set to I.
ftp> cd /files/pat # change directory on remote side
250 CWD command successful.
ftp> put junk # transfer file to remote system
200 PORT command successful.
150 Binary data connection for junk (191.11.60.24,1088) (10485760 bytes).
226 Binary Transfer complete.
local: junk remote: junk
10485760 bytes sent in 42 seconds (2.4e+02 Kbytes/s)
ftp> dir junk # check size of remote file
150 Binary data connection for /bin/ls (191.11.60.1024,1089) (0 bytes).
-rw-rw-rw- 1 rt11 users 10485760 Jun 3 12:21 junk
226 Binary Transfer complete.
remote: zzzzz
59 bytes received in 0.04 seconds (1.5 Kbytes/s)
ftp> delete junk # clean up remote after test
ftp> quit
221 Goodbye.
PEGASYS@adac:#[7] /bin/rm -f junk # clean up local after test
Doing the math (10485760 / 42 / 1024) gives us about 243.81 Kbytes/sec or about 14.29
Mbytes/min which indicates several possible configuration possibilities. They could be going across
a WAN consisting of a couple T1 lines bonded together or it could be a single T1 line using
compression accelerators on each end. It could also be that there is significant traffic on a local
10Mbit LAN such that our traffic only gets a portion of the bandwidth available.
You should use a typically sizable file to get a good estimate of transfer rate. FTP requires a
password protected account to get in, use rt11/adacrt11 instead of pegasys. Keep in mind you can
also check round-trip times with the command
ping -s <hostname>
You can use an IP address instead of the hostname, let it run for 30 or 40 cycles and use ctrl-c
to have it stop and print out the min/avg/max times. Typical LAN values are about 1 or 2 msec for
Pegasys and 33 or 34 msec for Acq PC.
HOW CAN SITES ESTIMATE THEIR THROUGHPUT REQUIREMENTS?

• Throughput requirements vary from site to site based upon:
o types of studies done
o acquisition parameters
o number of studies per day
o number of transfer sessions per day
• Some sites may choose to transfer after each study, some might do a few per day, others
might just do one big one at the end of the day. Some sites may elect to send only
portions of the entire study (processed-only, snapshots, …)
• Pick a typical study for a given study type and do a Files-> Show More to get the 6
character “Examkey”; then in a Unix Window perform the following (adjust the max
number for the highest numbered /vol/patients# directory on your network):
foreach i ( 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 )
ls -l /vol/patients${i}/”Examkey”*
end
• Tally up the number of bytes for the desired files to be transferred to get number of
Mbytes per typical study type
• Now they should be able to estimate number of Mbytes per any given transfer session
based upon types of studies included (eg. 4 transfers each day of 14 Mbytes each … two
Total Body at 2 Mbytes each and One Gated Spect at 10 Mbytes)
THE TRUTH ABOUT PATIENT DATA SPACE

Something that is often confusing to the customer, sales person and FSE is why does the disk
seem to hold a lot less data than is advertised on the spec sheet. Most of the time the disks are quoted
as the full capacity size advertised on the box. This is misleading to the actual space allotted for
patient data storage. Only a portion of that space is assigned to the partition that will house the
patient data (/files/pat). The rest goes to partitions that house the Operating System and
Philips/ADAC Product files. The raw space allocated to the patient data partition loses a bit to the
structuring of formatting and then a bit more to the structuring as the file system is created with
newfs. In the space that is left, the Pegasys software imposes an 80% warning ceiling as files stored
beyond that limit are subject to increasingly severe fragmentation. Also, remember that
customizations, some acquisition software and other things may reside in the /files/pat partition and
further reduce available patient data space. Let’s look at the math:
How to find partition info (in 512 byte blocks) in Unix Window as superuser:
dkinfo sd0 (for SunOS 4.1.3u1)
prtvtoc /dev/dsk/c0t0d0s2 (for Solaris 2.x)
CALCULATING SPACE IN KB FOR /FILES/PAT ON DIFFERENT DRIVES
20 GB Drive 9 GB Drive 4 GB Drive 2 GB Drive

Unformatted blocks (512 Bytes) 39,849,263 17,682,084 9,842,931 4,052,320
* 0.94 (formatting) 37,458,307 16,621,159 9,256,716 3,809,130
* 0.90 (newfs) 33,712,476 14,959,043 8,331,056 3,428,230
* 0.80 (Peg warning level) 26,969,982 11,967,234 6,664,844 2,742,584
/ 2 (convert to KB) 13,484,991 5,983,617 3,332,422 1,371,292
WHY NOT USE DSL FOR REMOTE WEBVIEW OR PEG2PEG ON A WAN?
Philips strongly urges caution when considering the use of any type of direct Internet
connectivity (such as DSL) due to Security and Patient Confidentiality reasons. Upcoming HIPAA
Patient Data Confidentiality Regulations mandates that much more secure access and transport
mechanisms be used to keep a patient’s demographic and image data from prying eyes. This is
especially true for any data traveling over the public Internet. Sites, Clinics and Physician’s homes
should always be protected by a Firewall when connected to the Public Internet to prevent
unauthorized access to their machines and data. Additionally, it is recommended for them to use
VPN tunneling (encrypted private channel) to ensure that all patient information is protected while it
traverses the Internet.
One possible method to leverage this type of connectivity is to have the Site IT Group setup a
VPN tunnel (encrypted private channel) through their Firewall to their internal LAN (depending on
policies, expertise and costs, this can be very easy, or nearly impossible, to do). On the client side,
the use of a hardware device to setup the VPN client (often within the firewall) is recommended to
avoid certain configuration issues on the PC. Of course, the Pegasys cluster would need a filtered
connection to the hospital LAN as well. Clearly there is a lot of planning, cooperation and
configuration needed to realize a solution like this.
Similarly, if there are several clinics that wish to leverage DSL to share data between Pegasys
clusters using Peg2Peg Transfer, they will need to hire a Third-Party Network Service Company to
setup their sites with connectivity, being sure to use Firewall devices with VPN support that will
support as many different channels as there are sites in the proposed WAN. It would be extremely
irresponsible for a site to be setup so that their equipment containing confidential patient data is
exposed directly to the Internet and not make use of encrypted data communications between sites.
Since available capabilities, equipment and configuration varies from region to region across
the country it is important for the customer to realize that we provide the applications that speak at
each end of the connection but that they are responsible for purchasing the appropriate connectivity
from their local Line Service Provider (LSP) who will install and configure it. This allows for a
service demarcation so that if issues arise in the LSP equipment or lines then their service personnel
can debug and correct the parts of the connectivity pathway that only they have access to. Remember
only the customer has the clout required to demand a rapid resolution from the LSP.
One important thing to keep in mind about DSL connections is that most of the connections
that are setup for homes or small clinics are usually ADSL (asymmetrical), which has differing
download and upload speeds (it is typical to get 1500 kilobits-per-second download max and 128
kilobits-per-second upload max). This means that any pushes from the remote side that has the low
upload speeds may not perform as well as users expected. It is best for a central site to have as big
and fast a “pipe” as possible and for all sites, if SDSL (symmetrical), where both upload and
download speeds are equal, is available the remote users may have a more even experience with
pushes and pulls.
Also note that where a Pegasys cluster or DICOM based remote client application are
involved, they will need to specify that they need DSL with static IP addresses. Each target unit
needs a resolvable IP address. These usually come with the slightly more expensive Business-class
service, as opposed to the regular Residential-class service, which typically uses dynamic addressing.
Dynamic addressing is allowable for WebView and AutoquantMD clients.
WANS USING DSL VIA VPN THROUGH FIREWALL
Doctors Home PC Peg Cluster with

with remote view ing WebView Server
client (WebView, (static IP addresses)
AutoquantMD, etc.)
Filtered connection to
Fire wall with VPN Hospital Network
client support
uplinked via DSL* (VLAN, Router, etc.)
Hos pital Network

Doctors ISP with VPN support
with DSL support
Fire wall
Internet
(with hole for VPN)
(the big, bad, scary,
insecure thing with
lots of bad people
running around on it) Hospital’s Internet
Service Provider (ISP)
*=Static IP addrs required for DICOM clients (Ensphere); SDSL recommended
Clinic2 Pegasys Clinic1Peg Cluster Clinic3 Pegasys

behind VPN firewall with Peg2Peg behind VPN firewall
device and uplink via device and uplink via
DSL** VPN hosting firewall DSL**
router with uplink via
ISP with DSL and DSL** ISP with DSL and
VPN support VPN support
ISP with DSL and
VPN support
Internet
(the big, bad, scary,
insecure thing with
lots of bad people
running around on it)
**=Static IP addrs required; SDSL recommended
Clusters may need additional filtering from other equipment at each Site’s local LAN
Other Network Configuration Topics
CONVERSION TO ALL-ULTRA CLUSTERS

Many sites are electing to convert to All-Ultra Pegasys Clusters with any remaining PegX
based Acquisition Units as standalone satellites, which use Peg2Peg to transfer their data into the All-
Ultra Cluster for processing and review. (Some prefer to keep the PegX units in a separate cluster to
share some peripherals between them).
Now that these Ultras no longer have a PegX master or peer-clients, we need to reclaim the
space lost from running the script to shrink_patient_volume, before the Ultra60 or Ultra10 were
added to a mixed PegX-PegUltra network. Currently the only safe way to do this is to start from
scratch on the hard-drive as you add the transplanted unit to the new All-Ultra Cluster.
An Ultra1 is configured with a 2nd disk drive as a 2Gb patient partition and never needed to
be shrunk, therefore it does not need to be unshrunk. Although the OS can see and address partitions
greater than 2Gb, the Ultra1 is not setup to recognize the 9Gb drives and is stuck at its current
configuration.
Overview of required steps:

• Plan before you break up your mixed cluster. If you have doubts about how to best
achieve the split then call Tech Support well ahead of time and discuss your options.
• Use a separate standalone switch to connect and build your all-Ultra cluster. This will
allow you to avoid cross-binding by keeping things separate until you have had a chance
to remove the old domainname directories from the new all-Ultra cluster (see the hints
under Verifying NIS Maps).
• Have a plan to deal with network printers and other peripherals during the migration
• Transfer all patient data to other Pegasys or offline storage
• Backup any defaults and customizations (also acquisition stuff if DBHOST)
• Shutdown the ultra
• Do a delete_pegasys on the old PegasysX master by using Add/Delete Pegasys which is
found on the rootmenu after logging in as root
• Re-OS or “dd” the drive from a known pristine replacement
• If this is the first ultra, run a custom network_pegx and say that you will be the master of a
network, otherwise, do an add_pegasys on all-ultra master for the new ultra client
• Do a network_pegx on transplanted PegUltra (be sure to use new unique hostnames, IP
addresses and NIS domainname)
• Be sure to clean up the old domainname directories under /var/yp (see the hints under
Verifying NIS Maps).
• Reload defaults and customizations
• When all ultras have been transplanted, you may leave the remaining PegX units in their
original cluster so that they may share whatever peripherals you will devote to the PegX-
only cluster (or for a more robust configuration you may run emergency_standalone and
load Peg2Peg Transfer on each of the PegX units so that they may just be acquisition
engines that will have their data pushed into the all-PegUltra cluster for processing and
archiving).
• Keep in mind that when creating the multiple clusters and standalones, that you need to be
sure that all the hostnames are unique and that all their unique IP addresses remain within
the subnet addressing boundaries. This will allow multiple clusters to take advantage of a
single network printer using DICOM Print (Codonics NP1660 for example).
CONFIGURATION PRECAUTIONS
• Be sure to follow the instruction manuals carefully about when to have machines
connected or disconnected to the network, at the boot (“ok”) prompt or powered off.
Many of the problems folks have during network reconfigurations result from machines
being online and an answering up when they shouldn’t. This especially comes into play
when trying to create new clusters, and having an old original one sitting there as
YP.pegasys. If the old cluster is not taken down and stays unavailable until the new
cluster has been fully established with all its members, the potential for cross-binding
exists which can result in many hours of frustrating debugging. Be sure that in the new
cluster you clean up any old NIS directories since they can add to cross-binding issues in
the future (see the hints under Verifying NIS Maps).
• Always be sure you have a good solid network connection to a “live” port. Be sure that a
Link light is illuminated at each end of the connection (if available) and that the speed and
duplex indicators match what the system thinks it is connected to (see How to check speed
and duplex).
• It is often useful to set the Ethernet interface in your laptop to the same settings that your
Philips/ADAC unit will be. Then plug into the wall port and try to open a Command
Window and ping some known IP addresses that are supposed to be alive on the subnet.
You can save yourself a lot of “tail-chasing” by assuring at the onset that you are using a
live port that is correctly connected to be in the desired subnet.
• Many have found a higher percentage of custom networking success by first doing a
custom network_pegx with the new names and numbers but having the unit disconnected
from the network and choosing the standalone option. If you are changing the NIS
domainname, you should login as root and clean out the remnants of the old NIS domain
information form under the /var/yp directory tree (see the hints under Verifying NIS
Maps). Finally, connect to the network, reboot and run a custom network_pegx again,
reusing the info that is now the defaults, but configure it as the appropriately numbered
client.
• Make sure that your netmask values are correct and in effect. If they are incorrect you run
into problems binding and doing other network activities. For more information, see
Netmask Application in Chapter 2
• Remember that the main thing in choosing which number the client is, is that it will
determine which /vol/patients# will be assigned to that machine. The simple rule of
thumb is: the /vol/patients# = (unit number – 1). So unit 2 has patients1, and so on.
• You MUST run emergency_standalone first before renetworking a client. The
networking scripts were written with the assumption that the machine is a standalone at
the onset. Note: All Pegasys-X units that have been networked into a cluster must be
allowed to have the mirroring activity occur by a cron job at 1:00 a.m. (The Ultra’s and
Blade’s avoid this by doing a bootstrapping at during the first reboot following the
running of the network_pegx script).
• emergency_recovery was designed for instances where the master goes down but
does not have any problems with its hard drive and the clients have been put into
emergency_standalone mode. If you have re-networked to create a different cluster with a
different master then you will need to put all into emergency_standalone mode before
using network_pegx to reconstruct the original network configuration.
• The restore_pegx command (only available on PegUltras) was really only designed
to be run to get you out of binding problems during network_pegx. For all other purposes
you should use emergency_standalone and then network_pegx.
• If there are routers that separate the equipment, you should always try to go for separate
clusters and use Peg2Peg Transfers between them. The instabilities of depending upon a
database master across a link that could potentially go down is a big reliability risk.
• When performing custom networking where the hostnames change, there is a flaw in the
network_pegx script that often results in the email files not being renamed to have the
new hostname extensions and perhaps incorrect permissions as well.
When the reconfiguration has been completed you should check in /var/spool/mail
to be sure that there is a pegasys_hostname file for each of the new hostnames in your
cluster. You may just have to do a “mv pegasys_oldname pegasys_newname”
to affect the repair. You should also do an “ls –l” to check the owner and group for the
files. They should be “pegasys:mail” if the master is a PegUltra and
“pegasys.users” if the master is a PegX.
SPECIAL NETWORK CONFIGURATIONS-AFMS

• In order to remain compliant with our GMP and Design and Implementation processes, great
care must be taken not to make changes or alterations that deviate from the intended use and
functionality of the product. The SOP-24 Customer Support Procedure spells this out in
detail (SOP-24 can be found below the Quality System Documentation page on our Intranet at
http://intranet/departments/doc_control/html/qsr.htm).
• Our policies and procedures state that all our Implementations and Field Repairs are to be
performed following released procedures and instructions. It is also stated that these
implementations and repairs must be done with Philips/ADAC approved parts and
components.
• Occasionally, the situation may require customized modifications to configuration files in a
manner that is outside the scope of the released procedures. Also, sometimes the need arises
for the local purchase and use of compatible cables and components. Whenever these types
of situations occur, you MUST log a call with Technical Support to request a review for an
Approved Field Modification (AFM). The Support Specialist will track this call with an
AFM designation. They will review the details you provide, check with engineering if
warranted, and return to you an approval (or alternative Field Repair workaround) with
instructions or a denial with explanation. Throughout this manual we will call out such
activities and procedures with the following symbol: AFM
• As always, if in doubt, call in and ASK FIRST, don’t assume and don’t just do it!
SUN NETWORK FILE SYSTEM FACILITIES

NFS
The NFS (Networked File System) facility uses RPC (Remote Procedure Calls) to allow
machines to transparently access remote file systems and sub-directories as if they were contained on
the local machine. This allows many machines to use the very same directory hierarchy from just
one machine. This is handy in that it allows users to access and manipulate the same information
without having to make copies to each individual machine and worry about cumbersome
synchronization details. This hierarchy must be “exported” from the machine donating the
information and “mounted” by each machine wishing to share this information. The directories we
typically access remotely on the Pegasys are /var/spool/mail, /vol/patients_db, /vol/rt11 and
/vol/patients# (where # is a number representing the unique patient volume from each of the Pegasys
in the cluster).
An interesting example of how we use this in our product is the electronic mail spool
directory, /var/mail (Solaris 2.x) or /var/spool/mail (SunOS 4.1.3u1). Keep in mind that for Pegasys
software compatibility purposes, we have created a symbolic link on the Solaris 2.x machines so that
/var/spool/mail points to the /var/mail directory. The machine that houses this directory where all
users mail files are kept (master), contains an entry in the file /etc/dfs/dfstab (Solaris 2.x) or
/etc/exports (SunOS 4.1.3u1) which consists of pathname of the directory it wishes to share:
In /etc/dfs/dfstab on Solaris 2.x:

share -F nfs -o rw /var/mail
In /etc/exports on SunOS 4.1.3u1 :

/var/spool/mail
The command “shareall” (Solaris 2.x) or “exportfs -a” (SunOS 4.1.3.u1) puts the list of
pathnames to share in an OS table, this happens automatically at boot time. The other machines
(clients) wishing to share this directory have an empty directory mount point, in this case it happens
to be /var/mail (Solaris 2.x) or /var/spool/mail (SunOS 4.1.3u1) as well, and an entry in the file
/etc/vfstab (Solaris 2.x) or /etc/fstab (SunOS 4.1.3u1), which consists of the machine and directory
we want to share, where we will mount it, what type of filesystem it is and a few options (like read-
write or read-only):
In /etc/vfstab on Solaris 2.x (if master is a Solaris 2.x):
adac:/var/mail - /var/mail nfs - yes hard,bg,rw,actimeo=0
(Or if master is a SunOS 4.1.3u1) :

adac:/var/spool/mail - /var/mail nfs - yes hard,bg,rw,actimeo=0
In /etc/fstab on SunOS 4.1.3u1

adac:/var/spool/mail /var/spool/mail nfs soft,bg,rw 0 0
At boot time all the requests listed in the /etc/vfstab (Solaris 2.x) or /etc/fstab (SunOS
4.1.3u1) file are processed by the mount command, and any coming from remote machines are made
visible to our local machine.
automount
The majority of our products’ NFS shared hierarchies are handled via the automounter. The
automounter makes NFS mounts, but uses control files other than /etc/vfstab (or /etc/fstab). These
mounts are made on-demand and by reference. That is, if you reference a file or command located in
a remote machines hierarchy, and the control files contain the location information, the mount will be
made automatically for you. As long as any command or file remains running or referenced, even
sitting idle in a shared sub-directory, that mount will remain in effect. The automounter periodically
checks to see if any elements are being referenced and if not, it unmounts the hierarchy.
The location information is made available to all machines via the NIS (Network Information
System) via NIS maps. These maps are generated on the NIS master from seed information files,
/etc/auto.vol and /etc/auto.home. Copies of these maps are pushed out to any NIS slaves in the
network. This makes it very easy to change or add new information without having to edit all the
/etc/vfstab (or /etc/fstab) files on every machine in the network. Simply update the seed file on the
master, cd /var/yp, make and the information is made available to the entire network. Keep in mind,
all the clients need to be up and running in order to receive the updated maps and keep in sync. You
should never delete or move any entries under the /vol tree as the automounter has control over this
special directory hierarchy. To see all potentially available paths you can do a “ypcat -k auto.vol”.
The automount hierarchies we use are under /vol (we used to also use /home back in the
SunView days before PegasysX came along, but now we have local home directories on each
machine). It is often confusing to do an “ls” of /vol or /home and only see a few of the expected sub-
directory name from all those we know are possible and supposed to be there. Don’t worry, they are
available but are not currently referenced. Here is how the reference is resolved. The exception is on
machines that are providing a given hierarchy, you will never see an entry for it when you do an “ls”
of /vol as the automounter on the sharer is smart enough to resolve the path without performing a
mount.
Lets take for example that a request is made to “cd” to a remote, shareable directory /vol/rt11.
The automounter intercepts the request, recognizes that it knows about /vol entries, sees that the
shared hierarchy is not already mounted, finds the location information entry in the appropriate map
(auto.vol in this case), decodes the machine and exported path, makes the appropriate temporary
directory mount point under the /tmp_mnt directory (/tmp_mnt/rt11 in this case), performs the mount
from the remote machine, creates a symbolic link in /vol (rt11->/tmp_mnt/rt11), finally the user is
placed in what appears to be /vol/rt11. This is all undone of course when the user is no longer sitting
in that directory or using files or programs located in that hierarchy. Using the “mount” command
will allow you to find out what is mounted under /tmp_mnt at any given time.
Besides the usual steps for exporting the shared hierarchy on the provider, the location
information must be setup and advertised from the NIS master.
Some of the typical entries on a master are found in /etc/auto.vol:
patients_db <tab> adac:/export/vol/patients/patients_db

patients0 <tab> adac:/export/vol/patients/patients0
rt11 <tab> adac:/export/vol/patients/rt11
The entries in /export/vol/patients are actually symbolic links to the actual directory locations:
patients_db -> /files/vol/patients/patients_db

patients0 -> /files/pat/patients/patients0
rt11 -> /files/pat/patients/rt11
The benefit of using this level of indirection via symbolic links is that if the need arises to
move the location of the actual directories (due to space constraints for example), then the symbolic
link needs only be changed and the automounter advertisement will remain valid and not require any
change. This is very advantageous on very large networks where it could take quite a while to push
out changes to a great many slave NIS servers.
cron
The cron facility allows us to specify that we want a certain job to be executed automatically
at certain times of our own choosing. The OS uses some jobs to perform cleanup functions and the
like. We use cron for the same thing as well as launching other regular monitoring and maintenance
programs.
Each user can have their own cron control file. They will have separate files on each machine
and will be located in /var/spool/cron/crontabs/username. Be careful, please DO NOT edit this file
by invoking your favorite editor directly, your changes will not be recognized and your programs will
not be started as you wished they would have been. Instead, use the command “crontab -e”, which
will throw you into the vi editor, allow you to make your changes and when you close the file it will
signal cron to read your updates and put them into the schedule for execution. You will edit the
crontab file for whatever username you currently are logged in as (or su’ed to). You can use the
command “crontab -l” to list your file from any directory and “crontab -r” to remove your crontab file
completely. Great care must be taken when editing the cron file as system balance depends on these
jobs. The typical structure of an entry in the crontab file is:
* * * * * /path/cmd > /path/somelog 2>&1 # comment
The time information is denoted by the five * positions. If left as is, the command will be run
every minute of everyday of every week .... You can dictate distinct time periods by modifying the
fields which are defined from left to right:
minutes (0 thru 59)
hours (0 thru 23)
days-of-month (1 thru 31)
month (1 thru 12)
days-of-week (0 thru 6, where 0 is Sunday)
For example,
0,30 6,18 * * 2-5 /myhome/mycommand > /myhome/mylog 2>&1
would execute mycommand every half-hour during the 6 AM and 6 PM hours of every week
Tuesday thru Friday.
rdist
We use the rdist command to synchronize duplicate copies of certain files and directory trees
from the master to the slaves. Different information is synchronized to the slaves at different time
intervals, depending upon the expected frequency of change. Some of these are every 15 minutes,
some every 1 hour, 4 hours or 24 hours.
There are numerous different entries in the crontab file, which invoke the PRE_RDIST
command with the appropriate arguments for type and time period. PRE_RDIST in turn calls rdist
using the map /etc/modules/shared_dist.map with the passed in argument. The rdist command looks
at the desired list of information and looks for any changes between the master and all the slaves
named in the shared_dist.map file. If changes are found then those files are synchronized out to the
slaves. For some directories a special command says that instead of just pushing all changes and new
files, it will additionally remove any files that were removed from the master but are still on the
slaves. This helps prevent certain critical file systems from filling up.
This synchronizing of files from the master to the slaves is of paramount importance in
keeping the files in the shared directories on the master (the ones that all the machines use) up to date
on the slaves so that if running the emergency_standalone procedures is required, those slaves will
have an accurate snapshot of the area that was provided by the now non-available master. Not all
shared hierarchies are synchronized to the slaves, only essential ones. For example,
/usr/adac/pegasys is not, as each machine uses a local home directory which will still be effective in
emergency_standalone mode. The first time rdist happens for some essential files that will facilitate
the emergency_standalone procedure, it is done during the middle of the night. So if one attempts to
run the emergency_standalone script on the same day as an initial installation, you will run into
problems.
There is a work-around:
(on the slave)

bootup into single-user mode “boot -s” or “b -s”
mount -at 4.2; mount -at lo
mkdir -p /files/mirror/adac/etc
(on the master)

if it can be booted into single-user mode, do so
cd /etc
tar cvf /dev/rst8 *
(back on the slave)

cd /files/mirror/adac/etc
tar xvpf /dev/rst8
then proceed with emergency_standalone process
Important: The shared_dist.map file is finely tuned; no editing required.
rlogin
Once you are logged into a system, and are in the big window, a Unix window or a Shell
window, you can access another Pegasys on the network using the rlogin command:
rlogin otherhostname
The rlogin (remote login) session you have in your window is the equivalent of logging into
the big window on that machines console or logged in via a modem. While you are rlogged into
another machine you may not start any Windowing-system oriented programs from the command line
as those have a requirement of actually logging in on the physical console (keep this in mind when
someone asks you rlogin and kill a locked up Openwin program and then to restart it so they do not
have to logout and login again). You may rlogin to another machine during your login session, and
another, and another, essentially threading your way around the network. Be careful though, as it is
easy to lose track of your pathways in a short time and it is always a good idea to clear the rlogin
chain before quitting a window or logging off your original machine. The best way is to use “exit” to
close your rlogins because when you get back to your original machine you will get the message
“Use logout to exit”, kind of a built in safety measure.
Note: The most notorious of all actions is losing track of your rlogin chain while you are
superuser and issuing the reboot command, thinking you are rebooting your own machine.
If you are rlogged into another unit when you do this, you have just yanked the rug out
from under it!
rcp
The rcp (remote copy) command allows us to push and pull files between machines on the
network without the hindrance of floppies or tapes and some number of footsteps. This can be a great
help when trying to restore a system file that has been accidentally removed from your local machine.
Important: Systems need to have entries for their NIS hostnames in each other’s
/.rhosts file for this to work properly.
To copy from local to remote:

rcp <filepath> other_host:filepath
To copy from remote to local:

rcp other_host:filepath <filepath>
OPTIONS
-p Attempt to give each copy the same modification times, access times, modes, and
ACLs if applicable as the original file. [This is especially good to use when replacing
missing OS files.]
-r Copy each subtree rooted at filename; in this case the destination must be a directory.
The “fsck” process sometimes removes system files that were active when a machine traps or has a
Stop-a run on it. This is a classic case where rcp can come in handy as you can often replenish the
file from another Pegasys on the network (provided it is of the same OS and machine type). You
may get some surprising error messages when you are superuser and are copying root owned system
files from local to remote. The root user is given the user ID of “nobody” for the life of an rsh
command on a remote machine. You will avoid these problems if you rlogin to the remote machine
and rcp from remote to local, (with respect to where you are currently logged in), which is the
equivalent of what you were trying to do. Confused? Good! Me too!
References
Books:
• TCP/IP Network Administration - Craig Hunt - O’Reilly & Associates, Inc. 6/95
ISBN: 0-937175-82-X (part of the Nutshell series)
• TCP/IP Unleashed - Timothy Parker Ph.D. et. al - SAMS Publishing 1996 ISBN: 0-
672-30603-4 (part of the Unleashed series)
Websites:
• http://www.cisco.com/univercd/home/home.htm See the Technology Information
section (although Cisco-centric has a lot of info)
• http://www.cavebear.com/CaveBear/Ethernet - one resource for Ethernet vendor and
type codes
• http://www.ethermanage.com/ethernet/ethernet.html - Charles Spurgeon’s Ethernet
Page with quick reference guides
Chapter 2: IP Subnetting
Chapter Outline
This chapter explains the principles of IP Subnetting. After reading this chapter you should
be able to identify the different classes of IP Networks, be able to identify the default Netmask for
any given network class, and know how a specific Subnet Mask establishes an IP Subnet range.
I. Definitions
a. What is an IP Address?
b. What is an IP Network?
c. What is a Network Number?
d. What is a Netmask?
e. What is a Default Netmask?
f. What is a Subnet Mask?
g. What is an IP Subnet?
h. Why use IP Subnetting?
II. Introduction to IP Subnetting
III. IP Addressing Principles
a. IP Networks
b. IP Address Classes
i. Class A (1.0.0.0 — 126.255.255.255)
ii. Class B (128.0.0.0 — 191.255.255.255)
iii. Class C (192.0.0.0 — 223.255.255.255)
c. Note on Reserved Host ID Values
Network Numbering Principles
d. Note on Dot Zero Notation
e. Network Numbering Rules
IV. Netmasks
a. Decimal – Binary – Hexadecimal Conversion Table
b. Default netmasks
c. Netmask Application
d. Masking Rules
e. Note on Reserved Network Addresses
V. IP Subnetting Principles
a. Subnet Masks
b. Subnetting in Practice
c. Subnetting a Class C network
VI. Subnet Mask Translation Table
VII. Examining the Netmask Values assigned on a Pegasys or Atlas
a. Netmasks on SunOS 4.1.3u1
b. Netmasks on Solaris
VIII. Real-World Example of IP Address Ranges in Subnets
IX. The IP Subnet Calculator
a. How to run IP Subnet Calculator
b. The Hexpert Calculator
X. Summary
XI. References
Related Topics (refer to other sections/chapters):
Chapter "3", Network Connectivity Hardware Overview

Routers, Gateways, Filtering Bridges
2nd Ethernet Cards
Installing a 2nd Ethernet Card (Software & Hardware)
Chapter "6", Network File Structures
/etc/hosts
/etc/networks
/etc/netmasks
/etc/defaultrouter file
Definitions
WHAT IS AN IP ADDRESS?
An IP Address is a 32-bit identifier assigned to a networked computer that uses the Internet
Protocol (IP). A computer’s IP address identifies the network it belongs to and its host ID number on
the network.
Example: Class A - 10.42.75.44
Example: Class B - 172.16.193.53
Example: Class C - 192.168.206.150
WHAT IS AN IP NETWORK?
An IP Network is the range of all IP Addresses designated by a Network Number and its
applied netmask.
WHAT IS A NETWORK NUMBER?

A Network Number is an identifying bit combination which designates, and fundamentally
organizes hosts into, a network. The network number makes up the upper portion of a host’s IP
address, and all hosts on a given network share the same base network number.
Example: Class C - 192.168.206.0
WHAT IS A NETMASK?
A Netmask is a 32-bit, software-defined configuration value used by the Internet Protocol to
extract network number and host ID information from the IP address. Sometimes referred to as
Address Mask, Network Mask, or simply mask. See also Subnet Mask definition below.
WHAT IS A DEFAULT NETMASK?

A Default (or Natural) Netmask is one that is applied automatically when no other value is
specified or in the event of an improper construct in the /etc/netmasks file. A default netmask
provides no sub networks in its particular IP address class.
Example: Class C - 255.255.255.0
WHAT IS A SUBNET MASK?
A Subnet Mask is a modified netmask used to divide one base network into multiple routable
sub networks.
Example: Class A - 255.255.255.224
Example: Class C - 255.255.255.192
WHAT IS AN IP SUBNET?
An IP Subnet is a subset of IP addresses specially partitioned out of a larger, base address
range using a subnet mask. Example:
Class IP Subnet Range Network Number Applied Netmask

A 10.42.75.32 – 10.42.75.63 10.0.0.0 255.255.255.224
B 172.16.192.0 – 172.16.207.255 172.16.0.0 255.255.240.0
C 192.168.206.128 – 192.168.206.191 192.168.206.0 255.255.255.192
WHY USE IP SUBNETTING?

Subnetting allows IP networks to be subdivided for purposes of security (by isolating critical
nodes) or performance (can reduce network traffic by preventing transmissions between nodes that do
not need to communicate with each other), or simply to isolate a LAN from network traffic on other
subnets.
Introduction to IP Subnetting
Computer networks consist of computers and other devices, often called hosts or nodes,
connected with individual segments of network cable. As such, networks can naturally be partitioned
physically, through the use of cable. In addition, they can be subdivided logically, through the use of
software-level configurations.
IP Subnets are "virtual" network sub-segments; they logically partition the traffic flowing
through the cables rather than the cables themselves. Subnets can subdivide a single physical
network segment or span multiple segments.
Subnetting allows some useful flexibility in defining relationships among network hosts, for
example, by organizing hosts into logical, specialized groups. Hosts on different subnets can only
"talk" to each other through specialized network gateway devices like routers (refer to the section
Gateways, in Chapter "3", Network Connectivity Hardware Overview). The ability to filter traffic
between subnets can improve network security, for example, by limiting access in desirable ways,
and can improve host performance, by making more bandwidth available to applications.
In practice, IP Subnetting is based on the values assigned for IP Addresses, Network
Numbers, and Netmasks (Subnet masks), and follows the rules of the Internet Protocol (IP)
governing communications among networked computers.
IP Addressing Principles
An IP Address is a 32-bit identifier assigned to a networked computer that communicates

according to the rules of the Internet Protocol. Usually, IP addresses are represented in the form
nnn.nnn.nnn.nnn, that is, four fields separated by dots, where each field contains a number in the
range 0 – 255. This is called dotted decimal notation.
For example, an IP Address may look like any of the following:
192.9.200.1
192.168.38.124
172.16.0.240
134.110.100.128
10.100.32.100
Note: IP addresses never include leading zeros. For example, 192.009.200.001 is

not correct.
To computers, however, IP address structure is essentially a binary code, represented by four

octets. An octet is an 8-bit binary number equivalent to a decimal number in the range 0 – 255.
Thus, the commonly-used Philips/ADAC IP address
192.9.200.1
is actually interpreted by a computer in the equivalent, binary form
11000000 00001001 11001000 00000001
How decimal form equates to binary:
192 .9 .200 .1
st nd rd th
1 octet 2 octet 3 octet 4 octet
Where the first octet would be described by the binary representation below:
Octet #1 = 192 128 64 32 16 8 4 2 1

Binary bit string
1 1 0 0 0 0 0 0
(192 = 128 + 64)
The second octet would be described:
Octet #2 = 9 128 64 32 16 8 4 2 1
Binary bit string
0 0 0 0 1 0 0 1
(9 = 8 + 1)
The third octet would be described:
Octet #3 = 200 128 64 32 16 8 4 2 1

Binary bit string
1 1 0 0 1 0 0 0
(200 = 128 + 64 + 8)
And the fourth octet would be described:
Octet #4 = 1 128 64 32 16 8 4 2 1
Binary bit string
0 0 0 0 0 0 0 1
(1)
Taken all together, 192.9.200.1 = 11000000 00001001 11001000 00000001
Form IP Address
Decimal 192 .9 .200 .1
Binary 11000000 00001001 11001000 00000001
A Philips/ADAC PegasysX, PegUltra, or Atlas computer’s IP address is recorded in the file
/etc/hosts. At boot time, the operating system consults this file to learn the host system’s IP
address so it can configure the network interface correctly. At multi-user runtime the IP addresses
are found by consulting the NIS hosts map for the PegasysX and PegUltra systems, while the Atlas
systems, which do not run NIS, continue to consult their local /etc/hosts files.
For a standalone, ALL-Philips/ADAC network, most of the IP addresses are automatically

assigned by the configuration scripts. For a Philips/ADAC custom network, containing multiple
Pegasys clusters or connected to a hospital network, the IP addresses are typically assigned by the
network administrator or decided upon during the network planning phase between the
Philips/ADAC FSE and the Milpitas Networking Group.
It is a rule that each host’s IP address must be unique within a given network. Some
machines may have more than one IP address if they contain multiple interfaces, like routers and
multi-homed gateways typically do.
If you need to apply or modify an IP address, you could use network_pegx or manually edit
/etc/hosts file on the appropriate Pegasys and Atlas nodes on network, become “su -” on the
master then cd /var/yp and make and finally reboot the network. (Complete instructions
available in Chapter 3 Shortcut Procedure for changing IP address, subnet, default router ONLY)
Important: If you need to change hostnames then you MUST use the network_pegx
method as there are too many linkages associated with hostnames to be sure that you will
edit them all.
IP NETWORKS
When networking computers, IP addresses serve two functions. First, the left-hand
(“upper”) portion of a computer’s IP address, called the Network Number (see the section Network
Numbering Principles later in this chapter), identifies the network to which a computer belongs.
Second, the right-hand (“lower”) portion, called the Host ID, identifies the individual computer
on its network. This addressing scheme is recognized in a standard way by implementations of IP.
It follows that a given IP network can be as large as the range of all host ID’s defined by a
given network number.
IP ADDRESS CLASSES
For networking purposes, IP addresses typically fall within one of three Classes:
Class IP Address Range

A 1.0.0.0 to 126.255.255.255
B 128.0.0.0 to 191.255.255.255
C 192.0.0.0 to 223.255.255.255
Notes:
• The first octet of an IP address is never 0.
• The range beginning 127 is reserved for loopback. (Loopback is a test mechanism of
network adapters. Messages sent to 127.0.0.1 do not get delivered to the network. Instead,
the adapter intercepts all loopback messages and returns them to the sending application.)
• The range 224.0.0.0 through 239.255.255.254 comprises class D, which are reserved for
Multicast packets. These are normal to see on our network as the Sun OS sets up a Multicast
route at boot time. Multicasting is often used for video conferencing which works like a
television broadcast where any number of users can simultaneously “tune in”. This address
range is also used by certain routing protocols (RIP v2 and OSPF). If you see excessive
Multicast traffic it may be time to explore subnetting or filtering your network.
• The range 240.0.0.0 through 255.255.255.254 comprises class E, which is reserved for
experimental use.
Class A (1.0.0.0 — 126.255.255.255)

The Class A address range includes all IP addresses for which the number in the first field
falls in the range 1 – 126 (the first octet is never 0; 127 is reserved for loopback). For Class A
networks, the 1st octet alone identifies the base network number and the remaining 2nd through
4th octets define the host ID of an individual machine.
Example: IP address 26.4.0.1 represents host 4.0.1 on network 26.
By normal network rules, Class A machines with the same 1st octet have clear communication
paths to each other as long as they are physically connected.
Class A networks are huge. Each can have a maximum number of 16,777,214 Hosts.
16,777,214 = 256 x 256 x 256 - 2 (2 = the first and last reserved values, host ID numbers 0.0.0 and
255.255.255 (see Note on Reserved Host ID Values below). All 126 possible class A network
numbers have been allocated (to governments, companies, and other organizations)
Example: the same network 26 can support any host in the IP range 26.0.0.1 –
26.255.255.254.
Class B (128.0.0.0 — 191.255.255.255)
The Class B address range includes all IP addresses for which the number in the first field
falls in the range 128 – 191. For Class B networks, the 1st and 2nd octets together identify the
network number and the remaining 3rd and 4th octets define the host ID of an individual machine.
Example: IP address 128.89.117.26 represents host 117.26 on network 128.89.
By normal network rules, Class B machines with the same 1st and 2nd octets have clear
communication paths to each other as long as they are physically connected.
Class B networks are large. Each can have a maximum number of 65,534 Hosts.
65,534 = 256 x 256 - 2 (2 = the first and last reserved values, host ID numbers 0.0 and
255.255).
Example: the same network 128.89 can support any host in the IP range 128.89.0.1 –
128.89.255.254.
Most of the 16,384 possible class B network numbers have been allocated.
Class C (192.0.0.0 — 223.255.255.255)

The Class C address range includes all IP addresses for which the number in the first field
falls in the range 192 – 223. For Class C networks, the 1st, 2nd, and 3rd octets together identify
the network number and the remaining 4th octet defines the host ID of an individual machine.
Example: IP address 192.15.28.16 represents host 16 on network 192.15.28.
By normal network rules, Class C machines with the same 1st, 2nd, and 3rd octets have clear
communication paths to each other as long as they are physically connected.
Class C networks are small. Each can have a maximum number of 254 Hosts.
254 = 256 - 2 (2 = the first and last reserved values, host ID numbers 0 and 255.)
Example: the same network 192.15.28 can support any host in the IP range 192.15.28.1 –
192.15.28.254.
Most LANs are class C networks. There can be over 2 million class C networks in an
internet.
NOTE ON RESERVED HOST ID VALUES
• The first and last values of any IP address range are reserved for special uses and should
not be assigned to any actual host.
• An IP address with all bits in the host ID portion set at 0 (0 decimal) identifies the network
itself (see the next section, Network Numbering Principles). For example, the class B host
140.163.201.102 may use the address 140.163.0.0 for special purposes, and having a live host
at that location could cause conflicts.
• An IP address with all bits in the host ID portion set at 1 (255 decimal) is a broadcast address.
For example: The broadcast address for a class C network 192.9.200 is 192.9.200.255. A
datagram sent to this address will simultaneously address every host on a network 192.9.200.
Network Numbering Principles
As mentioned in the last section, an IP Address = Network Number + Host ID.
What’s more, just as any networked computer is identified by its IP address, a network as a
whole is identified by its Network Number.
A Network Number is an identifying bit combination which designates, and fundamentally

organizes hosts into, a network. The network number makes up the leftmost (“upper”) portion of
a host’s IP address, and all hosts on a given network share the same base network number. Thus,
hosts on any IP network belong to a peer network designated by the network number. (Multi-homed
nodes, that contain multiple network adapters, can belong to multiple peer networks. Refer to the
section in Chapter "3", Installing a 2nd Ethernet Card (Software & Hardware)
Network numbers look very much like IP addresses but the two should not be confused.
Network numbers can also be represented in four octet decimal form equivalent to a binary string.
For example, consider the host IP address 10.0.0.1, an address commonly used on private
networks. As noted above, because it is a Class A address, its 1st octet by default refers to the
network number 10 (alternatively, 10.0.0.0 in dot zero notation; see Note below).
For Class B host IP address 155.33.62.224, the 1st and 2nd octets by default refer to the
network number 155.33 (or 155.33.0.0).
For Class C host IP address 192.168.192.105, the 1st, 2nd, and 3rd octets by default refer to the
network number 192.168.192 (or 192.168.192.0).
NOTE ON DOT ZERO NOTATION
As demonstrated above, in decimal notation, a network number is not necessarily represented
by four octets; the trailing “dot-zeros” are optional. On PegasysX, PegUltra and Atlas systems, use
of dot zero notation in system configuration files is illustrated in the following matrix:
Chart: Should Dot Zero Notation Be Used?
File PegasysX PegUltra and Atlas

Network Number Network Number
/etc/networks
NO OPTIONAL*
Network Number Network Number
NO OPTIONAL*
/etc/netmasks
Netmask value Netmask value
YES YES
Important: Be sure to double-check that correct dot zero syntax has been created as we
have noticed that the custom networking scripts create incorrect values when custom
subnetting is applied. The correct values should show the dot zero form of the default
(natural) network number for that particular Class of address.
Notice the important association between IP Address and Network Number; essentially,
"default" network numbers can be derived immediately from host IP addressing and its class
structure.
The PegasysX, PegUltra, or Atlas computer’s network number is recorded in the file
/etc/networks. At boot time, the operating system consults this file to learn the host system’s
base network address so it can configure the network interface correctly. At multi-user runtime the
network numbers are found by consulting the NIS networks map for the PegasysX and PegUltra
systems, while the Atlas systems, which do not run NIS, continue to consult their local /etc/networks
files.
If you need to apply or modify a network number, you could use network_pegx or manually
edit /etc/networks file on every Pegasys and Atlas node on network and reboot. (Complete
instructions for the Shortcut Procedure for changing IP address, subnet, default router ONLY are
available in Chapter 3-2: Installing Custom Networking Hardware).
NETWORK NUMBERING RULES
All hosts within the same network must have the same base network number (but remember
that it is possible to join different networks together with routers).
A network number becomes a reserved address that should never be assigned to any actual
host. Just as each host ID must be unique within a given network, each network number must be
unique within a given intranet or internet.
While host IDs are assigned by the network administrator, the network number is assigned by
the inter-network administrator. If a site has an address range that is “legal” out on the public
Internet, it was applied for and granted by a governing body, who is responsible for allocation and
avoiding duplications.
Since so many groups out in the world have been reserving the available addresses at an
alarming rate, there was a need to have an address scheme set aside that could be simultaneously used
by many different sites. The governing body set aside several nice sized chunks in each of the three
Classes. The only problem is that there can be no duplicate IP addresses out on the public Internet so
these became by design, non-routable addresses. Any routers that touch the Public Internet must be
programmed to make sure that these addresses to not get out onto the Internet. This is just fine for
some sites that want to have a private numbering scheme that fits the size of their user base. For
those sites who do need external access to the Internet though, there are methods of using Proxies or
Network Address Translation (NAT) to map a sites non-routable addresses to a small set of “legally”
allocated addresses that the site was assigned by the governing body. Here is a table of those non-
routable IP address ranges (designated as Private Address Space in RFC 1918):
Non-Routable IP CIDR Hosts Per Description

Address Range Notation Range (n-2)
192.168.0.0 – 192.168/16 254 Set of 256 Class C ranges
192.168.255.255
172.16.0.0 – 172.16/12 65534 Set of 16 Class B ranges
172.31.255.255
10.0.0.0 – 10/24 16777214 One entire Class A range
10.255.255.255
It is not uncommon that you will run into one or more of your sites that wants us to use
addresses from one of these ranges. The only time it really requires close scrutiny is if we are placed
into a 192.168.x.x range that is the same range that our modem-based Peg2Peg PPP clients were
assigned to. The distinct possibility of duplicate IP address use exists and must be checked for and
rectified if need be. Another instance to look out for is if we are placed into the 10.x.x.x range with
non-default subnet masking. You will need to eliminate the old entry for “arpa” in the /etc/networks
file to ensure proper configuration of the Ethernet interfaces (see Shortcut Procedure for changing
IP’s, subnet, default router ONLY)
IP addressing as a function of network numbering fundamentally organizes hosts into groups,
which can improve security and reduce network traffic, and allows a given group of hosts (peers) to
communicate efficiently with each other. A group may include all computers located in a single
facility or all computers used by a department. Overall, network addressing becomes even more
powerful when introducing subnetting using netmasks.
Netmasks
We have already seen that an IP Address represents both a Network Number and a Host ID
Number. When computers communicate with each other, the Internet Protocol rules use the network
number portion of an IP address to route a datagram between networks. The full address, including
the host ID, is used to make the final delivery when a datagram reaches the destination network.
In practice, the IP rules use a Netmask, which is a particular 32-bit, software-defined,

configuration value, to specify which portion of an IP address identifies the network and which
portion identifies the host. So while in general a network number matches the 1st octet of a host's IP
address for hosts in the Class A range, the 1st and 2nd octets for hosts in the Class B range, and the 1st,
2nd, and 3rd octets for hosts in the Class C range, netmasks are what truly establish communication
boundaries and group IP addresses together into network ranges. (See also IP Subnetting Principals
below)
Like IP addresses and network numbers, a netmask (sometimes referred to as address mask,
network mask, or simply mask) is usually represented by four octets (8-bit binary numbers equivalent
to a decimal number in the range 0 – 255) in "dotted decimal" notation. For example, a very common
subnet mask in its binary representation
11111111 11111111 11111111 00000000
is usually shown in the equivalent decimal form
255.255.255.0
Note: Some tools, for example, “ ifconfig –a ”, show IP addresses or netmasks in

hexadecimal notation. In hex, this same netmask would appear as 0xffffff00. To see what
values the pairs of hexadecimal characters should have when corresponding to their
decimal equivalents let’s examine the following Decimal–Binary–Hexadecimal
Conversion Table:
DECIMAL – BINARY – HEXADECIMAL CONVERSION TABLE
Decimal Binary Hexadecimal

0 00000000 00
128 10000000 80
192 11000000 c0
224 11100000 e0
240 11110000 f0
248 11111000 f8
252 11111100 fc
254 11111110 fe
255 11111111 ff
It is important to remember, a netmask is not an IP address, nor does one function

independently of an IP address. Instead, netmasks must be applied to IP addresses! For a
complete conversion table from 0-255 decimal, see Appendix A.
DEFAULT NETMASKS
Each of the three network classes and their respective IP address ranges described above has a
default netmask value applied automatically when no other value is specified (see the section IP
Subnetting Principles below). The default netmasks for the three network classes are as follows:
Address Class IP Address Range Default Netmask Hex Netmask

A 1.0.0.0 - 126.255.255.255 255.0.0.0 ff000000
B 128.0.0.0 - 191.255.255.255 255.255.0.0 ffff0000
C 192.0.0.0 - 223.255.255.255 255.255.255.0 ffffff00
NETMASK APPLICATION
It is important to know, however, that a netmask's binary value is what the Internet Protocol
rules apply to IP addresses in routing computations. The following table shows the default netmasks
for the three network classes in both decimal and binary forms:
Network Class Default Netmask Value
255 .0 .0 .0
A
11111111 00000000 00000000 00000000
255 .255 .0 .0
B
11111111 11111111 00000000 00000000
255 .255 .255 .0
C
11111111 11111111 11111111 00000000
As a rule, if a given bit of the mask is 1, the corresponding bit of the IP address is in the
network portion of the address, and if a given bit of the mask is 0, the corresponding bit of the IP
address is in the host portion.
For example, the following table shows the class A address 63.148.85.132 in both decimal
and binary forms, aligned with the mask 255.0.0.0, also in both decimal and binary forms:
Network
Element Host ID
Number
63 .148 .85 .132
IP Address
00111111 10010100 01010101 10000100
255 .0 .0 .0
Netmask
11111111 00000000 00000000 00000000
(Number of bits in default mask = 8 [of 32]; “eight bit mask” or /8 in CIDR and router
notation)
The next table shows the class B address 129.10.1.78 in both decimal and binary forms,
aligned with the mask 255.255.0.0, also in both decimal and binary forms:
Element Network Number Host ID

129 .10 .1 .78
IP Address
10000001 00001010 00000001 01001110
255 .255 .0 .0
Netmask
11111111 11111111 00000000 00000000
(Number of bits in default mask = 16 [of 32]; “sixteen bit mask” or /16 in CIDR and router
notation)
And the next table shows the class C address 192.15.28.16 in both decimal and binary forms,
aligned with the mask 255.255.255.0, also in both decimal and binary forms:
192 .15 .28 .16
IP Address
11000000 00001111 00011100 00010000
255 .255 .255 .0
Netmask
11111111 11111111 11111111 00000000
(Number of bits in default mask = 24 [of 32]; “twenty-four bit mask” or /24 in CIDR or router
notation)
The PegasysX, PegUltra, or Atlas computer’s non-default netmask value is recorded in the
file /etc/netmasks. At boot time, the operating system consults this file to learn if it should use
a non-default value to override the host system’s default netmask value, so it can configure the
network interface correctly. If there is no entry then the default is used. At multi-user runtime the
systems, while the Atlas systems, which do not run NIS, continue to consult their local /etc/netmasks
files.
Netmask values, especially non-default ones are assigned by the network administrator. If
no explicit assignment then the default values for the given Class are applied. Non-default subnet
mask values are explained further in the section Subnet Masks below.
Even when a network is not subnetted, the Internet Protocol applies the default (or
natural) netmask value; the result is one network. However, mask values are not limited to the
defaults; indeed, modifying the netmask (adding more mask bits), using a value other than the
default, is the very basis of subnetting.
MASKING RULES
In binary form, all valid address masks contain two parts: the all-ones left side (the network
number portion) and the all-zeros right side (the host ID portion). In fact, for a netmask to be valid,
some of its leftmost bits must be set to one. In addition, some of its rightmost bits must be set to
zero.
- It is invalid to have a netmask of all zeros

0000000 00000000 00000000 00000000 (0.0.0.0 decimal)
- It is likewise invalid to have a netmask of all ones

11111111 11111111 11111111 11111111 (255.255.255.255 decimal)
- The first octet is always valid so the mask is never a number less-than 255.0.0.0
- In the network environment the Philips/ADAC equipment “lives in”, when modifying address
masks, bits must fill in from left to right.
NOTE ON RESERVED NETWORK ADDRESSES
The first and last subnet ranges of any subnetted network are reserved and
unuasable due to the potential for ambiguity between whole-subnet-addresses and broadcast-
addresses of the non-subnetted network.
♦ We know the rule that the top and bottom addresses in a network range are reserved.
(See note on Reserved HostID Values above). For example in network 192.9.200
the addresses 192.9.200.0 and 192.9.200.255 are reserved.
♦ No matter how many subnet ranges we break this network into, the first subnet
range will always have the address 192.9.200.0 which on a mis-configured unit
could be mistaken for the all-network address to all 254 hosts on the Class C
network and not just those few members of the desired subnet range. This first
range is marked invalid to avoid the ambiguity. In this range all the added subnet
bits are zeros.
♦ Likewise the last subnet range will always contain the address 192.9.200.255 which
on a mis-configured unit could be mistaken for the broadcast address to all 254 hosts
on the Class C network and not just those few members of the desired subnet range.
This last range is marked invalid to avoid the ambiguity. In this range all the added
subnet bits are ones.
♦ Due to this “casting-out” we are unable to break up the different classes into a
network of just two halves. Nor can we have a network where there are only top
and bottom elements. So the list of unavailable netmasks would be:
Class A: 255.128.0.0
255.255.255.254
Class B: 255.255.128.0
255.255.255.254
Class C: 255.255.255.128
255.255.255.254
♦ Some networks use CIDR and some variable length subnet masking (via OSPF)
where these restrictions do not apply. Those types of networks are beyond the scope
of this manual.
The same address mask must be applied on all devices (hosts & nodes) on a network. There
are exceptions to this rule on networks using variable length subnet masking (typically implemented
with OSPF routing rules) but these configurations are beyond the scope of this manual.
IP Subnetting Principles
When a netmask is modified to partition a network into multiple routable subnets, it is called a
Subnet Mask.
Subnet masks divide a single base network IP address range into many distinct subnet
address ranges, so that each logical subnet has its own discrete address range. This enables a
hospital to configure gateway devices such as routers between the different logical subnets to better
manage the network traffic of different groups. For more information, refer to the section in Chapter
"3", Gateways)
SUBNET MASKS
The simplest subnet masks for each of the three classes of networks are as follows, where n is
a number other than zero:
Address Class Subnet Mask

A 255.n.0.0
B 255.255.n.0
C 255.255.255.n
The values of n will be one of those found in the hexadecimal column of the Decimal –
Binary – Hexadecimal Conversion Table seen previously in this chapter. (The other zeros in the
mask for a class A or class B address can also be replaced by a different number, but, for simplicity,
that possibility is ignored for now.)
SUBNETTING IN PRACTICE
Since the netmask specifies which portion of the IP address identifies the network and which
portion identifies the host, modifying the netmask shifts the boundary between the network
portion and the host portion. At the binary level, subnet masks "take" bits from the host ID portion
of the IP address and use them to differentiate subnets. By this means, more than one logically
distinct network can be managed under a single class A, class B, or class C network number.
Note: When a network is partitioned into subnets by a subnet mask, the resulting subnets
still all have the same base network number but they have a different base subnet
number.
For example, a hospital that has a Class B Network probably will not want 65,534 hosts in
one big network. They would apply a Subnet Mask to have a manageable number of subnets, each
having a smaller number of hosts in each subnet address range. The users on the radiology subnet,
accounting and billing subnet, research subnet, administration subnet and nuclear medicine subnet
can all go about their business without being exposed to, and therefore not slowed down by, any other
group’s traffic.
The following is a simple example of subnetting partitions in a class B network. Set the third
octet of the mask to 255; that is, use the default netmask of a class C network. The following table
shows the class B address 128.89.2.26 in both decimal and binary form, aligned with the mask
255.255.255.0, also in both decimal and binary form.
Subnet
Number
128 .89 .2 .26
IP Address
10000000 01011001 00000010 00011010
Subnet 255 .255 .255 .0
Mask 11111111 11111111 11111111 00000000
Using this (subnet) mask with this address makes the Class B address act like a Class C
address in that the 1st through 3rd octets together define the network (and subnet) and the 4th octet
alone identifies the host machine. So in this case 128.89.2.x would be a different subnet from
128.89.3.x or 128.89.207.x although all are in the Class B 128.89.x.x network.
To be more precise, from outside the network, packets are routed to net 128.89. It is only
when packets reach a router that is directly within the network that routing software takes account of
the subnet mask. In this case, the bits of the third octet identify the subnet. Thus, the mask partitions
the network 128.89 into 254 (254 = 2^8 mask bits – 2) subnets (See Note on Reserved Network
Addresses above), each supporting up to 254 (254 = 2^8 host bits - 2) hosts (See Note on Reserved
Host ID Values Above).
Another example is shown below:

10.100.32.100 = Class A address
255.255.255.0 = Class C Netmask
Network
Element Subnet Number Host ID
Number
10 .100 .32 .100
IP Address
00001010 01100100 00100000 01100100
Subnet 255 .255 .255 .0
Mask 11111111 11111111 11111111 00000000
Using this (subnet) mask with this address, makes the Class A address act like a Class C
address in that the 1st through 3rd octets together define the network (and subnet) and the 4th octet
alone identifies the host machine. In this case, the mask partitions the network 10 into 65,534
(65,534 = 2^16 mask bits – 2) subnets (See Note on Reserved Network Addresses above), each
supporting up to 254 (254 = 2^8 host bits - 2) hosts (See Note on Reserved Host ID Values Above).
Notice that if an octet of the IP address is entirely used to identify the network or subnet
number, the corresponding octet of the netmask has the decimal value 255 (binary 11111111), and if
an octet of the address is entirely used to identify the host ID, the corresponding octet of the mask has
the decimal value 0 (binary 00000000; see the following table).
Decimal Value in Binary Value in

Function
Field of Mask Field of Mask
255 11111111 Identify network number
0 00000000 Identify host ID
In more complex cases, however, values other than 255 may be used. Let’s examine one of
those now.
SUBNETTING A CLASS C NETWORK

For example, when subnetting a class C network, 255 cannot be used in the fourth field of the
subnet mask. In fact, for any Class C IP network, the value n that is substituted for 0 in the 4th octet
of the netmask must be one of the decimal values shown in column 1 of the following table.
Column 1 Column 2 Column 3 Column 4

Decimal Binary Number of Number of
Value Value Usable Subnets Valid Host IDs
192 11000000 2 62
224 11100000 6 30
240 11110000 14 14
248 11111000 30 6
252 11111100 62 2
Note: Any decimal value other than those shown in column 1 of the table above results in
discontinuous strings of 1s and 0s, which can create undesirable consequences for most
software that interprets addresses subnetted under this mask. This is true at least for
Philips/ADAC computers and networking equipment and most typical TCP/IP networking
topologies.
Column 2 shows the values of n as binary numbers. It is these binary values which are used
in routing computations. Recall that if a given bit of the mask is 1, the corresponding bit of the IP
address is part of the network ID. If a given bit of the mask is 0, the corresponding bit of the IP
address is part of the host ID. Remember also that bits must fill in from left to right
Column 3 indicates the number of usable subnets into which the mask partitions the network.
As a rule, if there are s mask bits set to 1’s, then there are 2^s - 2 usable subnets. (Ordinarily two, the
first and last, subnet ranges are reserved. See Rules below.)
Column 4 indicates the number of valid host IDs that can be assigned within each subnet
using the remaining host ID bits. As a rule, if the last h mask bits are 0’s, that is, identify the host ID,
there are 2^h - 2 possible hosts. (Remember that two/the first and last host IDs are reserved. Also
see Rules.)
Notice that decimal value 128 (binary 10000000) is omitted from the table. This is because
when used in the fourth octet of a class C network’s subnet mask, it allows 0 usable subnets (2^1 - 2
= 2 - 2 = 0). Decimal value 254 (binary 11111110) is also omitted, because it allows 0 valid host IDs
(2^1 - 2 = 2 - 2 = 0).
As an example, suppose a hospital has class C network 192.15.28 and uses subnet mask
255.255.255.224.
Recall that the mask is 255.255.255.0 with no subnetting. Compare these two masks’ binary
representations:
255.255.255.0 = 11111111 11111111 11111111 00000000 (24 bit mask)

255.255.255.224 = 11111111 11111111 11111111 11100000 (27 bit mask)
With subnet mask 255.255.255.224, the three leftmost bits of the IP address' fourth octet
identify the subnet.
The following table shows the class C address 192.15.28.37 in both decimal and binary form,
aligned with the mask 255.255.255.224, also in both decimal and binary form.
Host
Element Network Number SN
ID
192 .15 .28 .37
IP Address
11000000 00001111 00011100 001 00101
Subnet 255 .255 .255 .224
Mask 11111111 11111111 11111111 111 00000
(SN = Subnet Number)
Having a 224 in the last field of the mask tells the software to use the three leftmost bits of the
last octet of the address to define the subnet, and only the last five bits of the address to identify the
host machine.
Typically, the same subnet mask must be applied on all devices (hosts & nodes) across all
subnets of a single base network. There are exceptions to this rule on networks using variable
length subnet masking (typically implemented with OSPF routing rules) but these configurations are
beyond the scope of this manual.
To demonstrate how any device uses its netmask, let’s attempt to answer the question “How
does a subnet mask play a role in determining if a particular IP Address is within our local segment,
or has to be routed?”
Fact: If the Target IP address is within the same network as the Source IP address, it will NOT be
routed outside the segment. If the Target IP address is OUTSIDE the network of the Source IP
address, it MUST be sent to the router (gateway). If no router is present, the packet will be dropped
and the ICMP error "Host unreachable" will usually be returned.
IP Address Network Network Subnet Host

Source 160.149.115.8 10100000 10010101 01110011 00001000
Target 160.149.117.201 10100000 10010101 01110101 11001001
Mask 255.255.252.0 11111111 11111111 11111100 00000000
In the example above, we have a Source and Target IP Address in a typical Ethernet packet.
We can see that the first octet is 160, thus defining a class "B" address. Therefore, the first 16 bits
(natural mask of 255.255.0.0) define our network as 160.149.0.0. Since in our example the first 16
bits of each IP address are identical, they belong to the same network.
However, we also observe that there is a subnet mask applied (/22 in this case) where an
additional 6 subnet bits are defined. Therefore, even though these two IP Addresses are in the same
network, because all of the first 22 bits (denoted in boldface) do NOT match, these IP Addresses are
NOT in the same segment (subnet). This datagram would have to be forwarded to a router
(gateway).
Here is another example for comparison:
IP Address Network Network Subnet Host

Source 160.149.115.8 10100000 10010101 01110011 00001000
Target 160.149.114.66 10100000 10010101 01110010 11001001
Mask 255.255.252.0 11111111 11111111 11111100 00000000
In this example, we observe that the Target Address has changed. Furthermore, we observe
that the first 22 bit positions of these IP Addresses are identical. Therefore, these addresses are
members of the SAME subnet and will NOT have to be routed.
The PegasysX, PegUltra, or Atlas computer’s non-default netmask value is recorded in the
file /etc/netmasks. At boot time, the operating system consults this file to learn if it should use
a non-default value to override the host system’s default netmask value, so it can configure the
network interface correctly. If there is no entry then the default is used. At multi-user runtime the
systems, while the Atlas systems, which do not run NIS, continue to consult their local /etc/netmasks
files.
The netmask values help the OS determine if requests to send messages to particular IP
addresses are “in-band” (within our subnet) or “out-of-band” (in a different subnet). This information
is used, in turn, to see if there are other interfaces or a default router or gateway to send the “out-of-
band” traffic to. (See the flow chart of how this works in Chapter 3, Basic Ethernet Packet Routing
Diagram)
Netmask values, especially non-default ones are assigned by the network administrator. If
no explicit assignment then the default values for the given Class are applied. Non-default subnet
mask values were explained further in the section Subnet Masks above.
If you need to apply or modify a subnet mask, you could use network_pegx or manually
edit /etc/netmasks file on every Pegasys and Atlas node on network and reboot (Complete
instructions available in Chapter 3, Shortcut Procedure for changing IP’s, subnet, default router
ONLY)
Subnet Mask Translation Table
The following page has a full table that defines subnet masks as they apply to the IP
addressing scheme on the binary level.
Standard IP Address Subnet Masks
Bits, Sub-networks, and Hosts Translation Tables
Class A (1 - 126.x.x.x) Bits in Mask Number of Max Hosts

Decimal Value Binary Equivalent Subnet Total Usable Subnets per Subnet
255.0.0.0 * 11111111 00000000 00000000 00000000 0 8 / 32 1 16,777,214
255.192.0.0 11111111 11000000 00000000 00000000 2 10 / 32 2 4,194,302
255.224.0.0 11111111 11100000 00000000 00000000 3 11 / 32 6 2,097,150
255.240.0.0 11111111 11110000 00000000 00000000 4 12 / 32 14 1,048,574
255.248.0.0 11111111 11111000 00000000 00000000 5 13 / 32 30 524,286
255.252.0.0 11111111 11111100 00000000 00000000 6 14 / 32 62 262,142
255.254.0.0 11111111 11111110 00000000 00000000 7 15 / 32 126 131,070
255.255.0.0 11111111 11111111 00000000 00000000 8 16 / 32 254 65,534
255.255.128.0 11111111 11111111 10000000 00000000 9 17 / 32 510 32,766
255.255.192.0 11111111 11111111 11000000 00000000 10 18 / 32 1,022 16,382
255.255.224.0 11111111 11111111 11100000 00000000 11 19 / 32 2,046 8,190
255.255.240.0 11111111 11111111 11110000 00000000 12 20 / 32 4,094 4,094
255.255.248.0 11111111 11111111 11111000 00000000 13 21 / 32 8,190 2,046
255.255.252.0 11111111 11111111 11111100 00000000 14 22 / 32 16,382 1,022
255.255.254.0 11111111 11111111 11111110 00000000 15 23 / 32 32,766 510
255.255.255.0 11111111 11111111 11111111 00000000 16 24 / 32 65,534 254
255.255.255.128 11111111 11111111 11111111 10000000 17 25 / 32 131,070 126
255.255.255.192 11111111 11111111 11111111 11000000 18 26 / 32 262,142 62
255.255.255.224 11111111 11111111 11111111 11100000 19 27 / 32 524,286 30
255.255.255.240 11111111 11111111 11111111 11110000 20 28 / 32 1,048,574 14
255.255.255.248 11111111 11111111 11111111 11111000 21 29 / 32 2,097,150 6
255.255.255.252 11111111 11111111 11111111 11111100 22 30 / 32 4,194,302 2
Class B (128 - 191.x.x.x) Bits in Mask Number of Max Hosts

255.255.0.0 * 11111111 11111111 00000000 00000000 0 16 / 32 1 65,534
255.255.192.0 11111111 11111111 11000000 00000000 2 18 / 32 2 16,382
255.255.224.0 11111111 11111111 11100000 00000000 3 19 / 32 6 8,190
255.255.240.0 11111111 11111111 11110000 00000000 4 20 / 32 14 4,094
255.255.248.0 11111111 11111111 11111000 00000000 5 21 / 32 30 2,046
255.255.252.0 11111111 11111111 11111100 00000000 6 22 / 32 62 1,022
255.255.254.0 11111111 11111111 11111110 00000000 7 23 / 32 126 510
255.255.255.0 11111111 11111111 11111111 00000000 8 24 / 32 254 254
255.255.255.128 11111111 11111111 11111111 10000000 9 25 / 32 510 126
255.255.255.192 11111111 11111111 11111111 11000000 10 26 / 32 1,022 62
255.255.255.224 11111111 11111111 11111111 11100000 11 27 / 32 2,046 30
255.255.255.240 11111111 11111111 11111111 11110000 12 28 / 32 4,094 14
255.255.255.248 11111111 11111111 11111111 11111000 13 29 / 32 8,190 6
255.255.255.252 11111111 11111111 11111111 11111100 14 30 / 32 16,382 2
Class C (192 - 223.x.x.x) Bits in Mask Number of Max Hosts

255.255.255.0 * 11111111 11111111 11111111 00000000 0 24 / 32 1 254
255.255.255.192 11111111 11111111 11111111 11000000 2 26 / 32 2 62
255.255.255.224 11111111 11111111 11111111 11100000 3 27 / 32 6 30
255.255.255.240 11111111 11111111 11111111 11110000 4 28 / 32 14 14
255.255.255.248 11111111 11111111 11111111 11111000 5 29 / 32 30 6
255.255.255.252 11111111 11111111 11111111 11111100 6 30 / 32 62 2
* Default mask for each Class (A, B, or C) -- not subnetted. Shown for reference only
Note that in each Class certain masks are not usable because they would result in either:
a) no usable subnets (2s – 2 where s is # subnet bits)
b) no usable hosts (2h – 2 where h is # host bits)
Both of these are to avoid conflicts between addresses that are reserved for identifying/broadcasting
to the entire network/subnet.
Examining the Netmask Values assigned on a Pegasys or Atlas
We can look at the output of the “ifconfig –a” command to check if the desired netmask has
been applied. All you need to do is open a Unix Window and type the “ifconfig –a” command and
look for the hexadecimal value given for mask for the interface you are interested in (usually le0 on
SunOS 4.1.3u1 and hme0 on Solaris). Examples from each OS are shown below with the mask
values highlighted. Be sure to use the Decimal – Binary – Hexadecimal Conversion Table to convert
the pairs of characters into dotted-decimal notation (in our example below it turns out to be
255.255.255.0).
NETMASKS ON SUNOS 4.1.3U1

PEGASYS@cyclops:#[1] ifconfig -a
le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
inet 192.9.200.70 netmask ffffff00 broadcast 192.9.200.0
lo0: flags=49<UP,LOOPBACK,RUNNING>
inet 127.0.0.1 netmask ff000000
PEGASYS@cyclops:#[2]
NETMASKS ON SOLARIS
PEGASYS@storm:#[1] ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
PEGASYS@storm:#[2]
If the applied netmask values do not match those that are required, it is probably due to a
missing or incorrect entry. A common problem is that often the Base Network number is not used in
the /etc/networks and /etc/netmasks files (network_pegx on PegUltras will often try to use the Base
Subnet number instead).
To repair an erroneous entry you’ll need to check and make fixes to the /etc/networks and
/etc/netmasks files on all of the Pegasys and Atlas units within the cluster and then perform a “make”
in /var/yp on the master Pegasys. Remember to use the Base Network number for the appropriate
Address Class. Examples: Class A = 10 or 10.0.0.0; Class B = 172.16 or 172.16.0.0; Class C =
192.168.### or 192.168.###.0 [where ### is between 0 and 255].
Real-World Example of IP Address Ranges in Subnets
Let’s reiterate for a moment on the concept of reserved subnet ranges to avoid whole-network
addressing and broadcasting conflicts. In the following example, for any Class C network x.x.x, (first
octet is 192 – 223) since we reserve the top and bottom address of each address range, the available
address ranges established by subnet masks are as follows:
Invalid – Only two subnets created which are both reserved to eliminate conflicts:
255.255.255.128 [x.x.x.1 to x.x.x.126] -- reserved
[x.x.x.129 to x.x.x.254] -- reserved
Two valid subnets with 62 hosts each:

x.x.x.65 to x.x.x.126
x.x.x.129 to x.x.x.190
Six valid subnets with 30 hosts each:

x.x.x.33 to x.x.x.62
x.x.x.97 to x.x.x.126
x.x.x.129 to x.x.x.158
x.x.x.161 to x.x.x.190
x.x.x.193 to x.x.x.222
Fourteen valid subnets with 14 hosts each:

. . . to . . .
x.x.x.225 to x.x.x.238
Thirty valid subnets with 6 hosts each:

x.x.x.9 to x.x.x.14
. . . to . . .
x.x.x.241 to x.x.x.246
Sixty-two valid subnets with 2 hosts each:

x.x.x.5 to x.x.x.6]
. . . to . . .
x.x.x.249 to x.x.x.250
Invalid - subnets of 2 only have reserved bottom & top addresses
255.255.255.254
Invalid - subnets of 1 do not have bottom & top addresses

255.255.255.255
In each example above, for a given subnet mask, each address range is a separate subnet. In
the third section, a device assigned in an address x.x.x.50 will not talk to a device in an assigned
address x.x.x.70 unless we have additional network hardware to route traffic between the two
networks (refer to Chapter 3: Routers, Gateway and Filtering Bridges)
Now consider the following real-world example. A hospital plans to use the 192.15.28.0
network for its internal (intranet) hosts. The human resources department wants their computers to
be on a controlled part of this network because they store payroll information and other sensitive
employee data.
Because this is a Class C network, its default netmask, 255.255.255.0, which in binary is 24
bits (that is, 11111111 11111111 11111111 00000000), allows one network of 254 hosts (the first
and last addresses, 192.15.28.0 and 192.15.28.255, are reserved for network identification and
broadcasts). Recall that under the default netmask, all computers on the network are peers by default.
To subnet this network, more than the 24 contiguous bits must be set to be ones in the subnet
mask. For instance, adding two more bits, applying the 26-bit mask "255.255.255.192" creates a
four-subnet network, with two valid subnet ranges (the upper and lower ranges have been left in for
reference but grayed out; notice they have all zeros and all ones in the subnet mask column), as
follows.
Network address (24 bits) Subnet Extended Host address range

mask network
(2 bits)
11000000 00001111 00011100 00 192.15.28.0 192.15.28.1 – 192.15.28.62
11000000 00001111 00011100 01 192.15.28.64 192.15.28.65 - 192.15.28.126
11000000 00001111 00011100 10 192.15.28.128 192.15.28.129 – 192.15.28.190
11000000 00001111 00011100 11 192.15.28.192 192.15.28.193 - 192.15.28.254
When increasing the subnet mask, we always add binary bits from left to right, doubling the
number of potential subnets (less the two reserved ranges) each time we add a bit. A two-bit subnet
number can support up to four subnets (2 valid!), a three-bit number supports up to eight (six valid!),
a four-bit number supports up to sixteen (fourteen valid!), and so on. Remember 2^s-2 where s is the
number of subnet bits. Here is that info cleaned up into decimal and showing whole-subnet and
broadcast addresses:
Subnet Address Subnet
Whole-Subnet
Base Network SN Host ID Range Broadcast
Address
Number ID Address
192.15.28.1 -
192 .15 .28 .0 192.15.28.0 192.15.28.63
192.15.28.62
192.15.28.65 -
192 .15 .28 .64 192.15.28.64 192.15.28.127
192.15.28.126
192.15.28.129 -
192 .15 .28 .128 192.15.28.128 192.15.28.191
192.15.28.190
192.15.28.193 -
192 .15 .28 .192 192.15.28.192 192.15.28.255
192.15.28.254
The IP Subnet Calculator
Now you know how a subnet mask partitions a network, which ranges are invalid and which
addresses within the other ranges are reserved. Hey, that’s a lot to remember! You’re probably
saying to yourself “Hey, there has to be a better way to figure all this out!”
Suppose you’ve been given some IP addresses and a subnet mask and you wish to determine
the range of IP addresses your equipment will be living in Also suppose you’ve been given an IP
address of a target device out on the hospital network that they want you to communicate with (e.g.
DICOM printer, image formatter, etc.). It would be handy to be able to find out if it is in the same or
a different IP address range as your Pegasys Workstation. If it is in a different subnet then you also
need to be given a defaultrouter (or gateway) address within your subnet that will propagate your
communications to the other subnets.
One great tool you can use to figure all this out is the WildPackets IP Subnet Calculator. It
runs on your FSE laptop and you can download it from their website.
Using your browser: http://www.wildpackets.com/products/ipsubnetcalculator

(this path may vary and you may need to re-navigate the products page, also, they may require you to
register on a sign up screen before you can get to the final download screen, where they might also
give you a password to unlock the setup file when you run it --- be sure to make note of that
password!)
Installation is very easy, just type in the password they gave you and accept the defaults.
HOW TO RUN IP SUBNET CALCULATOR
Start the application from the Start menu tree or from a shortcut icon if you made one.
In the IP Address field: double-click in each of the octet fields and type in the different octets of the
unit you are interested, your Pegasys workstation for instance, let’s say it is 192.15.28.71, and be sure
to hit the <enter> key after you type in the last octet.
Click on the Address Info Tab

- Notice the info fields show you:
- What Class network you have and what the range of those are
- Which bits map to network number and which to hosted
- The binary representation of your IP address
- The hexadecimal representation of your IP address (Useful for some router configurations in
Chapter 3)
Now Click on the Subnet Info Tab

- Use the pull-down to set the number of additional subnet bits in use (our example uses 2
subnet bits)
- Notice that the total mask bits is 26 and the dotted decimal notation is 255.255.255.192
- It also tells us we have a max of 2 usable subnet and a max of 62 usable hostIDs in each of
those subnets
- We also see a binary representation of the network number bits, subnet bits and hostID bits
- It shows us the Subnet Host Address Range that our machine lives in (192.15.28.65 –
192.15.28.126)
- Also we see the whole-subnet address (192.15.28.64) and the subnet broadcast address
(192.15.28.127)
Now Click on the Subnet/Hosts Tab

- You’ll have to slide the column settings around to eliminate the “…” and see all the numbers
- You’ll have a table of valid subnets with their base, host range and broadcast addresses
- Let’s say our target device has an address of 192.15.28.161
- From looking at this table we can see that it is located in another subnet (192.15.28.129 –
192.15.28.190)
- If we’re going to be able to talk to it then we will need to be given the address of a
defaultrouter or gateway in our address range (192.15.28.65 – 192.15.28.126) and then we can
setup the /etc/defaultrouter file to allow our packets to be propagated to the target device in its
subnet.
The CIDR Tab is for more complex subnetting schemes in which our Pegasys clusters cannot
currently operate. We are ignoring these topics for now.
THE HEXPERT CALCULATOR
If you decide to pay the price to get the officially registered version, there are some additional
features available in the IP Subnet Calculator. If you use the Calculator pull-down at the top of the
tool, you can select the Hexpert Calculator.
Click on the Base Converter Tab

- Select how many bits wide your number is (we usually deal with 8 bits for an octet)
- Double-click in the field you wish to type in the number to convert
- The other fields update automatically as you type
- You can see your number in decimal, hexadecimal, binary and octal
- Remember, you always have access to the good-old Windows calculator. Just use the View
pull-down and select Scientific and then you can do your conversions with that as well.
Click on the Base Lookup Tab

- A big table you can scroll through (best to expand to full screen for this one)
Click on the Bit-Swapper Tab

- Mostly used if dealing with Token Ring networks. We’ll just ignore this one for our
purposes.
Click on the OUI Finder Tab

- A built-in Organizationally Unique Identifier (OUI) database.
- Knowing what kind of unit is putting out the packets in question is very helpful in debugging.
- You can lookup the maker of the Ethernet circuitry in question, based upon the first six
characters of the twelve-character Ethernet MAC address.
- Just type it in and hit enter and see if there is a match.
- Remember, the manufacturer of the Ethernet circuitry is not always the name that is on the
outside of the box that contains it, so don’t be surprised if you look up 005004 and find it says
3COM when the IP address takes us to find it is a Compaq PC. You can bet it has a 3COM
NIC inside.
- If you don’t get a match, it might be that the equipment in question is newer than the built-in
list in the program. To find a more current list, just enter “OUI table IEEE” into your
favorite online search engine and you should be able to locate several links to this
information…
Summary
• The Internet Protocol rules use IP Addresses, Network Numbers, and Netmasks (Subnet masks)
to govern communications among networked computers.
• An IP Address is a 32-bit identifier assigned to a computer that uses the Internet Protocol.
• A computer’s IP address identifies the network it belongs to and its host ID number on the
network.
• IP addresses usually are represented in the form nnn.nnn.nnn.nnn, that is, four fields separated by
dots, where each field contains a value in the range 0 – 255 (called dotted decimal notation).
• An IP Address typically looks like the following:
192.9.200.1
• IP addresses never include leading zeros. For example, 192.009.200.001 is not correct.
• PegUltra and Atlas units typically use “dot zero” notation for their network numbers while the
PegasysX units do not
• To computers, IP address structure is a binary code, represented by four octets. An octet is an 8-

bit binary number equivalent to a decimal number in the range 0 – 255.
• IP addresses typically fall within one of three Classes: A, B, or C
• Each IP address must be unique within a given network.
• An IP Address = Network Number + Host ID.
• Host IDs are assigned by the network administrator.
• A Network Number is an identifying bit combination which designates, and fundamentally

organizes hosts into, a network.
• All hosts on a given network must share the same base network number.
• A network number becomes a reserved address that should never be assigned to any actual host.
• Each network number must be unique within a given internet.
• The network number is assigned by the inter-network administrator.
• A Netmask is a 32-bit, software-defined configuration value used by the Internet Protocol to
extract network number and host ID information from the IP address. Sometimes referred to as
Address Mask, Network Mask, or simply mask. See also Subnet Mask.
• A Default Netmask is one that is applied automatically when no other value is specified.
• A default netmask provides no sub networks in its particular IP address class.
• For network routing on Philips/ADAC systems, default netmasks are applied automatically
during bootup, unless a non-default (modified) subnet mask value has been specified.
• Netmask values are assigned by the network administrator.
• In binary form, all valid address masks contain two parts: the all-ones left side (the network
number portion) and the all-zeros right side (the host ID portion).
• When modifying address masks, bits must fill in from left to right.
• A Subnet Mask is a modified netmask used to divide one base IP network into multiple routable
sub networks.
• An IP Subnet is a subset of IP addresses specially partitioned out of a larger, base address range
using a subnet mask.
• Subnetting allows IP networks to be subdivided for security or performance purposes, or simply

to isolate a LAN from network traffic on other subnets.
• The lower and upper addresses of any network/subnet are reserved for whole-subnet and
broadcast addressing respectively
• When subnetting, the lower and upper subnets ranges are invalid so as to avoid ambiguity
between addresses reserved for identifying/broadcasting to the entire network/subnet
• Use “ifconfig –a” in a Unix Window to check on the applied netmask. Convert the hexadecimal
pairs back to decimal to check in the /etc/netmasks file to see if it is the desired mask.
• Use the IP Subnet Calculator to help you sort out the relationships between the number of subnet
bits used, number of subnets and their ranges and number of hosts per subnet
References
Note: These hyperlinks are only valid when you have a live [or proxy] connection to the
Internet. Furthermore, due to the dynamic nature of the Internet, web page content and link
changes, some or all of these links may no longer be available. All links were tested at
time of this document’s release.
David Loomes: Glossary of Network Terms. This document has been included as Appendix B for
your convenience. All information is © David Loomes and the University of Bradford, used with
permission. You can also view the HTML version at the following address:
http://www.et.brad.ac.uk/help/.xferfile/.glossary.html
Links to RFC’s, Standards and Technical Publications

http://www.faqs.org/rfcs/
IP Tutorial: Network Numbering

http://compnetworking.about.com/compute/compnetworking/library/weekly/aa042900a.htm
IP Tutorial: Subnetting
http://compnetworking.about.com/compute/compnetworking/library/weekly/aa043000a.htm
Download the WildPackets IP Subnet Calculator

http://www.wildpackets.com/products/ipsubnetcalculator
Current list of Organizationally Unique Identifiers (OUI). These are the first 3 of 6 hexadecimal
numbers in a MAC address that define the manufacturer of a particular Ethernet interface. This
document has been included as Appendix C for your convenience.
To find a more current list, just enter “OUI table IEEE” into your favorite online search engine and
you should be able to locate several links to this information…
Chapter 3: Network Hardware Overview and
Installation
Chapter Outline
I. Overview
II. Wiring, Cables, and Terminators
a. Thicknet (dark ages)
b. Thinnet (light at the end of the tunnel)
c. Twisted pair / Cat5 (modern era, individual node reliability)
d. Fiber Optics, multi-mode, Gigabit+, (light “in” the tunnel)
e. ISDN / T1 Lines (Wide Area dedicated digital connections)
f. Terminators
i. Avoiding the “Dreaded T” – never add a barrel to Tee connector
g. 5-4-3 Rule (including graphical representation)
III. Connectors and Converters
a. Transceivers
b. Media Converters
IV. Switches, Hubs, Repeaters and Connectivity
a. Repeaters (10base2, 10base5, repeater count)
b. Hubs (repeater count, 10/100)
c. Switches (does not add to repeater count)
i. Layer-2 (routes traffic automatically to correct port, reduces unnecessary
normal backbone traffic, still propagates broadcasts to all ports)
ii. Layer-3 (Adds routing capability within the switch. These are supplied,
programmed, and maintained by hospital IT groups)
d. VLAN (Let the hospital IT group give me shelter)
e. Routers (filters / bridges between network segments)
f. Gateways
g. Filtering Bridges (divides traffic within a segment)
h. 2nd Ethernet cards (non-scalable solution; attaches to other network segment, letting
local machine have a static route to equipment located there.)
V. Current Custom Networking Parts Availability
VI. Example network configuration drawings
a. Switched VLAN
b. Standard Routing LAN
c. Standard Routing WAN
d. Filtering Bridge LAN
e. 2nd Ethernet Card
f. Local Online Documentation of Custom Networks
VII. Installing Custom Networking Hardware
a. Atlas 4-port Hub upgrade to 8-port Switch
b. Configuring a router for Straight Routing
c. Configuring a Cisco router as a Filtering Bridge, where target devices are:
i. All within same subnet
ii. Both within subnet and beyond hospital router (IP locked)
d. Using rcp and vi to make editing access lists easier
e. Broadcast Traffic and its effect on CPU performance
f. Installing a Second Ethernet Card (Hardware & Configuration)
i. 2nd Ethernet 10 Mbit card on a Pegasys-X 2, 5, 10, or 20
ii. 2nd Ethernet 10/100 Mbit card on a Pegasys-X 5, 10, or 20
iii. 2nd Ethernet 10/100 Mbit card on an Ultra 1
iv. 2nd Ethernet 10/100 Mbit card on an Ultra 10 or Ultra 60
g. Network Speeds, Duplex, MTU, Ports and Auto-Negotiation
i. Forcing 100Mbit, Half-duplex on Solaris
ii. Forcing 100Mbit, Full-duplex on 4.1.3u1
iii. How to check speed and duplex
iv. Reducing MTU Value
h. Configuration and creation of an /etc/defaultrouter file
i. Basic Ethernet Packet Routing Flowchart
ii. Defaultrouter Guidelines
iii. Configuring Additional Static Routes
i. Manual shortcut IP Address Procedure (a time-saving alternative to network_pegx
ONLY IF changing IP, defaultrouter, and/or netmask)
Section Overview
This section of the chapter describes physical network hardware that you might be asked to
service, install, or upgrade. Descriptions and highlights of advanced networking hardware are
included. Many hospitals are implementing similar hardware to accommodate future growth for data
and communications. Also included are diagrams to help you visualize hardware usage. The
following topics are covered:
• Wiring / Cables (Thicknet, Thinnet, Cat5 / UTP, Fiber),

• Connectors & Converters
• Switches, Hubs, Repeaters and Connectivity
• Gateways (Bridges, Routers, and 2nd Ethernet cards)
• Customizing networking hardware
The second section of this chapter extends into hardware configuration of custom networks.
This will assist you in changing your network configuration and settings to match those set forth by
the hospital IT department or network facilities administrator. The second section also includes
sample router configurations, 2nd Ethernet card installation procedures, and a Shortcut Custom
Networking procedure, as an alternative to network_pegx.
Wiring, Cables, and Terminators
Different types of physical cabling and equipment make up the “backbone” of any network.
This section will give you an overview of the different types of network cables you might come
across in hospital LAN (Local Area Network) and WAN (Wide Area Networks.)
Note: The term “terminator” is loosely used to describe a closed-end coax BNC connector
with a 50-ohm resistor soldered between the center conductor and the shielding. Two of
these devices properly “terminate” a 10base2 (thinnet) or 10base5 (thicknet) network,
resulting in a measured circuit impedance of about 26-28 ohms. However, “terminator” or
“termination” is also commonly used to describe the physical “connector” crimped onto
various cable types, such as an RJ45 connector crimped onto a length of Category-5 (UTP
or Unshielded Twisted Pair) cable. Be sure you are clear on how the term “terminator” is
used in the document that you are reading.
THICKNET (10BASE5)
Thicknet cable is a large diameter (about 1.0cm or
0.4in) coaxial cable and is relatively cumbersome and
inflexible. The outer insulation of the cable may be plain
PVC (yellow) or Teflon (orange-brown color). Electrical
characteristics include a 50 ohm impedance rating and a
solid center conductor. The maximum number of taps /
transceivers is 100 per segment. Nodes must be connected
on the pre-marked 2.5 meter nodal marks by punching a hole in the center conductor with a special
“coring tool.” (Several of these special tools should be floating around the regions, though rarely
used. They are likely located in the regional offices.)
Nodes are connected in a “daisy chain”
configuration. It was used primarily to span inter-
department distances that exceeded the maximum capability
of thinnet before more efficient WAN implementations
became more popular. 10base5 cable is designed to allow
transceivers to be added while existing connections are live.
This is done using "vampire tap" transceivers along the
cable’s length for connecting to network devices via AUI
Ethernet.
The most common problem with the vampire tap transceiver is intermittent connections,
causing either packet loss or loss of connectivity. This is especially evident when the intermittent
connection is on the Master Pegasys’ primary Ethernet port. The 10base5 standard notes that you
may provide a thicknet coaxial segment with a grounding point for electrical safety. To avoid
disrupting the Ethernet signals carried by the cable, there must only be one grounding point.
Thicknet (10base5) Specifications
Minimum Length 8.2 ft / 2.5 m
Maximum Length 1,640 ft / 500 m
Transfer Speed up to 10Mbps
Maximum # of Nodes / segment 100 (nodes must be connected on the 2.5
m nodal marks on cable)
THINNET (10BASE2)
Until the late 1990’s, 10base2 was the most commonly used method of
connectivity in Philips/ADAC Nuclear Medicine networks. 10base2 utilizes 50-
Ohm RG58 coaxial cable (not RG59 75-Ohm video cable which is commonly used
for video formatters), a stranded center conductor, and BNC terminators (seen at
right). Thinnet, like thicknet, is a “daisy chain” topology and must be terminated at
both physical ends [by a 50-Ohm terminator] to operate properly. However, the
physical cable is a smaller diameter (approximately 0.5 cm or 3/16th of an inch),
more flexible, and easier to work with than it’s thicknet predecessor.
Unlike thicknet, thinnet uses Tee (“T”) connectors

instead of “vampire tap” transceivers. This eliminates the
need for bulky external transceivers because many Ethernet
NIC’s (Network Interface Card) supply a built-in 10base2
(BNC) port. However, older Sun systems (IPC, IPX, SS1+,
SS2) used 15-pin AUI
connectors for Ethernet
medium independence.
This allowed flexibility, but requires an external transceiver. A
commonly used 10base2 AUI transceiver is the ST-500
(5200-1785). The maximum number of taps / transceivers is 30
per segment.
The 10base2 IEEE Standard notes that you may provide a thinnet coaxial segment with a
grounding point for electrical safety. To avoid disrupting the Ethernet signals carried by the cable,
there must only be one grounding point. Furthermore, there should be no tight bends in any cable
segment to avoid signal degradation. Bends and kinks can alter the signal and result in reflections,
which can alter the integrity of the data packets. Be sure to examine the entire 10base2 run, even
inside the acquisition towers, to ensure that someone was not over-zealous trying to dress the cables
to look “pretty” and putting kinks in the cable.
Thinnet (10base2) Specifications

Minimum Length 1.64 ft / 0.5 m
Maximum Length 606 ft / 185 m
Transfer Speed up to 10Mbps
Maximum # of Nodes / Segment 30
TWISTED PAIR (10BASET, 100BASET)
10baseT over UTP (Unshielded Twisted Pair) uses two pairs of twisted
copper cable (of 4 pairs available) with an RJ45 connector on both ends. The RJ45
connector resembles an RJ11 phone jack, but is much larger and contains 8
conductors. The two spare wire pairs are used only in high-speed copper networks
(such as Gigabit over copper).
There is a great deal of confusion with regard to the standards and performance characteristics
of twisted pair wiring. Here is a good rule of thumb: CAT5 is rated to 100M, CAT5e is rated to
350M, CAT6 and CAT6e is rated to 550M or 1000M depending on your source, and CAT7 is
supposedly rated to 700M or presumably 1000M.
As of this writing, there is no approved CAT6 or CAT7. While some folks are selling
products they call Level 6 or 7, there aren’t even specs for them, making CAT5e the best available
option. CAT6 cable is being made with 23 gauge conductor wire as opposed to the slightly smaller
24 gauge for CAT5e and also has a separator to handle crosstalk better.
Both CAT5 and CAT5e have 100 ohm impedance and electrical characteristics supporting
transmissions up to 100 MHz. The differences between CAT5 and CAT5e show in all aspects of
performance: capacitance, frequency, resistance, attenuation, and NEXT. CAT5e components were
designed with high-speed gigabit Ethernet in mind. While CAT5 components may function to some
degree in a gigabit Ethernet, they perform below standard during high-data transfer scenarios.
CAT5e cables work with ATM and gigabit speed products. Simply, if you are using a 100Mbps
switch, get CAT5e cable instead of CAT5.
Philips/ADAC nuclear medicine networks are now adopting this medium as the standard
topology going forward. Many older networks are being upgraded/converted to Cat5 topology by
request or out of necessity for the following reasons:
• Reliability – The “star” topology” means that no one link

(except the Master Pegasys) can take down the entire network.
• Troubleshooting – A quality central hub/switch offers
diagnostic lights to quickly determine link status as well as
connection speed (10/100Mbps).
• Parts availability – When the appropriate networking
components are not available through Field Service Parts, request an AFM from Tech
Support to purchase Cat5 networking supplies, including patch and crossover
cables, crimping tools, and transceivers, which are readily available at local office
supply and specialty computer stores.
Important: If using a “central” hub or switch for a star topology, a small UPS
(Uninterruptible Power Supply) is highly recommended to avoid a power outage taking out
your entire network.
Philips/ADAC responsibility for Cat5 cabling is
for cables that are (a) internal to equipment, (b) exterior
of system to wall jack and (c) from the Philips/ADAC
central switch or hub to wall jacks or patch panel.
Infrastructure wiring must be handled by the facilities (IT)
group and installed to local and State code (i.e., plenum
cable, avoiding fluorescent light fixtures, motors, EMI,
etc). Although Philips/ADAC is not responsible for this
wiring, FSE’s are often asked to participate in planning
the department wiring layout. Spare drops in each
network device location are highly recommended,
especially for the Master Pegasys.
As seen to the right, RJ45 connector pinouts can be

identified as follows: Hold the cable with the RJ45 connector
pointing away from you, with the copper leads on top and the lock-tab on the bottom. Pin 1 is on the
left.
Illustrated below are diagrams showing the pinouts of the two most commonly used cables in
Cat5 networks. The “straight” cable is used to connect any device (PC, printer, etc) to a hub or
switch. The “crossover” cable is used to connect “like devices” to each other and to uplink any
switch or hub together. An example of “like devices” would be a hub-to-hub, hub-to-switch (referred
to as “uplink”), switch to switch, or PC-PC connection (such as two laptops connected directly to
each other). Make sure your crossover cables are clearly marked. Philips/ADAC supplied crossover
cables typically have red labels.
Cat5 (10baseT / 100baseT) Specifications
Minimum Length 1 ft / 0.3 m (Philips/ADAC does have a 6 inch
crossover cable 2150-5617)
Maximum Length 328 ft / 100 m
Transfer Speed Varies, based on quality of cable; Cat1 through
Cat4 = 10Mbps, Cat5 = 100Mbps, Cat5e or Cat6 =
up to 1 Gigabit (1000baseT)
Maximum # of Nodes / Segment N/A
FIBER OPTIC CABLE (100BASEFX)

Fiber optic based networks are becoming more popular in
large hospitals and institutions that require an immense amount of
large image sets and data to be transferred between campus locations.
Philips/ADAC nuclear medicine networks are rarely connected
directly to fiber NIC cards or transceivers. Instead, a Cat5 uplink is
used to connect our LAN to a network closet that contains one or
more switch banks on the hospital fiber optic backbone.
Occasionally we need to extend beyond the 100m limitation of Cat5.
This can be done by using a fiber run with 10/100baseT to 10/100baseFL media converters on each
end, extending our LAN to a distant workstation that needs to be part of the virtual database.
We consider this as infrastructure wiring and the responsibility of the local IT or facilities
group on behalf of the department. (Refer to ADAC Responsibilities for Cat5 wiring above) You
should advise these group(s) to procure the cable and media converters at the same time to ensure that
all the connector types and media converters are compatible.
Illustrated to the right are some example optical connectors. Top Left: “Push/Pull SC,” Top
Right: “Bayonet-type ST,” Middle: “Assorted connectors and optical cabling”, Bottom: “Assorted
Single-Mode SC FC LC ST connectors)”
The facility network administrator(s) or IT Department will be responsible for maintaining
these “special portions” of the network and will provide the FSE with information regarding
connection points, configuration information, and routers (if required). Fiber optic backbones (as
well as 100baseT and 1000baseT) are often capable of supporting VLAN (Virtual LAN) where a
LAN can be simulated over a WAN, even though all it’s nodes are not physically connected to the
same hub or switch. Extended discussion of this topic is beyond the scope of this manual.
Fiber Optic Cable (100baseFX) Specifications

Minimum Length 3.2 ft / 1 m
Maximum Length Varies, up to 2km (2,000 m)
Transfer Speed up to 10 Gigabits (10,000Mbps) per second as
of this writing.
Maximum # of Nodes / Segment N/A
ISDN (INTEGRATED SERVICES DIGITAL NETWORK)

Digital telecommunications “phone” lines with 2 channels that can yield a combined capacity
of 128 kbps. This is commonly known as Basic Rate ISDN (BRI). The original specifications for
ISDN were based around voice and non-voice telephone-type services: telephony, data, telex,
facsimile, as it was hoped that the ISDN would evolve from the (then) emerging digital telephone
networks. ISDN is sometimes used to provide a direct link between smaller clinics with a dedicated
connection similar to a phone line. ISDN requires special “modems,” which are really ISDN Routers
that translate this service to TCP/IP in order to utilize programs such as Peg2Peg via network.
Extended discussion of this topic is beyond the scope of this manual. For an example of deployment,
see Figure 3-3 of “A Standard Routing WAN”)
T1 LINE
T-1 is a North American standard for point-to-point digital (network) circuits over two twisted
pairs. A T-1 line carries 24 64kbps channels (also known as DS-0) for a total usable bit rate of
1,536kbps (1.536 Mbps). Customers may lease a fractional T-1, using only some of the 24 T-1 slots.
A T-1C contains two T-1 lines; T-2 supports four T-1 circuits. A T-3 communications circuit
supports 28 T-1 circuits and provides 44.736Mbits/sec of bandwidth. These dedicated high-speed
connections are used in WAN (Wide Area Network) topologies to connect large institutions together
across very long distances. Costing up to several thousand dollars per month to lease, these are used
to connect Philips/ADAC Networks that have to transfer a large volume of data in a short amount of
time. They may be utilized in the hospital backbone your “custom network” is connected to.
Extended discussion of this topic is beyond the scope of this manual. For an example of deployment,
see Figure 3-3 of “A Standard Routing WAN”)
TERMINATORS
10base5 (Thicknet): There must be a type “N” 50-ohm terminator installed at each end of a
thick coaxial cable segment (total of 2 terminators). (Philips/ADAC Part# 5090-8092)
10base2 (Thinnet): There must be a BNC 50-ohm terminator installed at each end of a thin
coaxial cable segment (total of 2 terminators). (Philips/ADAC Part# 5090-9251) Beware of people
trying to splice in an extension of the backbone by using a barrel to connect a tee and a run of cable.
This results in triple-termination, which we also refer to as “the Dreaded-T”
THE DREADED-T DIAGRAM
Right
50 T T T T 50
PC Peg Peg Printer
Wrong
50 T T T T T 50
Barrel
PC Peg Peg Printer

T
Peg
50
5-4-3 Rule: Ethernet and IEEE 802.3 implement a rule, known as the 5-4-3 rule, for the
number of repeaters and segments on shared access Ethernet backbones in a tree topology.
The 5-4-3 rule divides the network into two types of physical segments: populated (user)
segments, and unpopulated (link) segments. User segments have users' systems connected
to them. Link segments are used to connect the network's repeaters together.
The rule mandates that between any two nodes on the network, there can only
be a maximum of five segments, connected through four repeaters, or concentrators,
and only three of the five segments may contain user connections.
The Ethernet protocol requires that a signal sent out over the LAN reach every part of
the network within a specified length of time. The 5-4-3 rule ensures this. Each repeater that a
signal goes through adds a small amount of time to the process, so the rule is designed to
minimize transmission times of the signals.
The 5-4-3 rule -- which was created when Ethernet, 10base5, and 10base2 were the
only types of Ethernet network available -- only applies to shared-access Ethernet backbones.
A switched Ethernet network should be exempt from the 5-4-3 rule because each switch has a
buffer to temporarily store data and all nodes can access a switched Ethernet LAN
simultaneously.
5-4-3 Rule Illustration - 5 segments, 4 repeaters, 3 populated segments.
CONNECTORS AND CONVERTERS

• Ethernet Transceiver: The MAU (Media Access Unit) that connects a host to a cable
segment through an AUI (Attachment Unit Interface) connector. They support all types of
Ethernet media, such as Coax (thin or thick), UTP and Fiber Optic, and provide diagnostic
LED’s for instant troubleshooting. Commonly found in ADAC nuclear medicine networks,
the ST-500 transceiver converts from AUI to 10base2 (thinnet). They are found in both
department and image Ethernet applications.
• AUI (Attachment Unit Interface) <-> 10baseT transceiver (5200-3282) Used for older PegX
based acquisition.
Important: “Image Ethernet” (the network link between the ACP board(s) in the
Pegasys-X card cage and the AT-Serializer in the acquisition PC) is NOT 802.3
compliant and therefore cannot be connected to a standard “department” Ethernet.
• Media Converters: Ethernet Coax/UTP Converter (commonly called the “ThinTwist” and
used inside our acquisition enclosures) converts the coaxial Ethernet to the 10BASE-T
twisted-pair Ethernet, and vice versa, providing one UTP port for connection to a UTP cable
segment and one BNC port to a thinnet coaxial cable segment. These devices are not
commonly found in older, established networks but are found inside Pegasys-X EPIC and
Atlas stacks. They are typically used to convert the “spaghetti coax or RG-174” EPIC
detector segment to Cat5 for connection to the internal Milan 4-port hub or the Atlas 8-port
10/100 switch.
• 10baseT <- > 10baseFL: These are used when a processing-only Pegasys, that needs to be
part of the Pegasys Virtual_Database, is over 100 meters from the central switch or hub. A
Cat5 cable from the central switch attaches to one converter, then a fiber-optic cable covers
the long distance, and a converter on the other end takes it back to Cat5 to attach to the remote
Pegasys.
Important: If a second switch is at the remote location, to service several processing-
only Pegasys units, be sure to use the uplink port to ensure you get a proper link light.
If there are acquisition units at the remote location then a second “cluster” should be
configured for reliability purposes and Peg2Peg transfers should be used to share data
between the clusters.
MAJOR CONNECTIVITY COMPONENTS AND FUNCTIONALITY

Configuration details of the Philips/ADAC Nuclear Medicine network are handled extensively in
the Nuclear Medicine Site Survey Document CS-16-1*. The Cluster Networking Site Survey
contains drawings of typical LAN deployments. The Custom Networking Site Survey contains
worksheets to plan the configuration of DICOM based equipment, custom IP address schemes and to
define the type of filtering that will be used when we connect our LAN to the hospital or department
LAN. This filtering is critical to reliability since we have some vulnerabilities to recent advances in
networking technology which could affect our ability to reboot our acquisition stations or
successfully complete a study.
• We do our acquisitions live on the network and “hammer the wire” pretty hard.
• Our diskless PCs and Detector heads use bootp, from a local bootp server in each camera
(host PegX stack or Atlas), to request an IP address and a code thread to get up and running.
Some equipment on hospital networks, DHCP servers and the like, could answer up first and
provide a random IP address and no code thread. Philips/ADAC requires its own local bootp
server for reliability and redundancy. Some sites have tried putting the Ethernet MAC
addresses of the PCs and Detector Heads into “ignore” lists on their DHCP and bootp servers,
which would allow our units to come up to multi-user and satisfy the requests locally and
correctly. This seems to be an okay workaround as long as there is no other traffic that
interferes with the actual studies.
• Interactivity with certain types of traffic on the hospital network, especially broadcast traffic,
can compromise an Acquisition unit, causing it to lock up and perhaps lose a study (especially
uncool for a stressed cardiac patient). So we talk to the IT Group at the site and strive to
arrive at a mutually agreeable filtering solution of a VLAN, routed subnet, filtering-bridge
with ACLs (Access Control List), or 2nd Ethernet cards if need be.
• A fix that should always be applied on the EPIC and Atlas boxes is the “hardware address not
found” technical tip to reduce buildup of chatty messages from bootp and tftpd.
Repeaters
• Join two segments at the physical layer.
• Provide signal amplification and pulse “clean up” functions.
• Extend single cable length limitation. ADAC has commonly used these on older 10base2
networks to extend the Thinnet backbone.
• Cannot exceed four* in a LAN. (Note: 5-4-3 Rule)
Note: 10baseT hubs, like the Milan 4-port in a tower or the external Allied Telesyn
8-port, count as repeaters. MCD-only units contain two internal hubs, which count as
repeaters, whereas 10/100baseT switches are NOT counted as repeaters.
• Pass the contents of all packets from one segment to the other.
• Do not relieve network congestion or reduce collision rate.
• Delay the amount of time it takes for a packet to get to its destination.
Hubs (Multi-port concentrators/repeaters)

• A hub is a shared-Bus, multi-port repeater (you could think of it as a collapsed Thinnet
backbone in a box).
• All packets are replicated (broadcast, unicast, multicast).
• All devices have to divvy up the bandwidth.
• Only one device can talk at a time, lots of collisions.
• Counts as a repeater in the networks’ “repeater count” (remember to count the ones inside the
EPICs and Atlases).
• If a hub is your central connectivity then you must pay special attention to the repeater count
rules. (Switches are so inexpensive now we can use them instead of hubs)
Switches
• A “hub on steroids”
• Allows pairs of simultaneous conversations at full bandwidth.
• Divides up the collision domain.
• You only see traffic destined directly for you (and of course, any broadcasts the switch is
exposed to),
• NOT a complete magic filtering black box
• If a switch is your central connectivity you do not need to worry about counting hubs in the
acquisition towers. Since each port segments the collision domain you do not have to
consider using multiple Cat5 cables, instead just use a single uplink from the acquisition
tower to the switch.
• Upstream hospital switches with VLANs and Routing provide the broadcast filtration.
VLANs
• VLAN = Virtual LAN (also know as ELAN on ATM equipment)
• This is the method that Philips/ADAC prefers a site to use to provide us filtered connectivity
to their LAN. Their infrastructure equipment must support the ability to VLAN and their IT
Group will provide the configuration support.
• A way to define certain ports of switches, in different physical locations, to appear as one
switch connecting equipment needing to work as a group
• Provides filtration of the broadcast domain (!!!)
• Requires sophisticated switching network to implement
• Requires upstream Routing to allow traffic to exit the VLAN and communicate with
equipment on other VLANs (like a PACS server or a DICOM printer)
• We cannot configure a VLAN on our unmanaged 8-port and 24-port switches. It must be
done within the equipment that we uplink to.
Routers
• Routes packet traffic between different IP address subnets (one per interface) based on Class,
IP Address and Subnet Netmask
• Used to provide desired communication between VLANs in a switched environment
• Routers are the next desired filtering choice if a site is not able to provide a VLAN for us
• Separates both the collision and broadcast domains
• Keeps a dynamic table of which addresses are available and where so it knows which
interface to forward the packet to (perhaps to another router down the line)
• Works in conjunction with other routers via a Routing Protocol (RIP, IGRP, etc.)
• Require us to setup our Pegasys and Atlas units with a /etc/defaultrouter file so that the Sun
Operating System knows who to forward out-of-band traffic to. This file contains just the IP
address of a router that is ping-able in our subnet range.
• If more than one router needs to be known to our equipment then we can setup additional
route statements. For Solaris 2.5.1 this is done in the /etc/rc2.d/S69inet file and for SunOS
4.1.3_U1 this is done in the /etc/rc.local file. (There are instructions in a later chapter.)
• Can control who can speak through the router by using Access Control Lists (ACLs).
Especially important to remember when trying to troubleshoot connectivity problems at a site
where the IT Group has imposed access lists.
• Some can be configured as a filtering-bridge with ACLs to filter traffic within a given subnet
IP address range (see below)
Gateways
• A gateway is any device that contains multiple network interfaces connected to different
subnets. So a gateway can be a router, a PC (or other computer) with multiple Network
Interface Cards (NIC’s), or other infrastructure equipment with the intelligence to determine
which interface a packet should be transferred to in order for it to travel onto its final
destination.
• The contents of our /etc/defaultrouter file may contain the IP address of the interface,
addressable within our subnet, if it will be used to propagate our packets to a remote target
device.
• It is important to remember that if we need a default route to reach a remote device, then it
must have a default route, or gateway, defined for it to be able to converse with us (DICOM
Transfer, DICOM Print, etc.). Often, if we have added one of our routers to provide a filtered
connection to a Switched network that never had a router or gateway, the remote targets will
need a configuration change to look at the IP address on their side of our router to be their
gateway value.
Filtering Bridges
• Bridges are used to filter traffic within a single IP address subnet range.
• Delays packets somewhat, since the bridge must read the Ethernet address before forwarding
selected data.
• Do not add to the repeater count.
• Older, simple bridges reduce traffic between segments by keeping a table of 12-digit Ethernet
MAC addresses and only propagating packets directed to a device on the other side.
Unfortunately broadcast packets must always be propagated to the other side on these older
bridges so they are not effective filters to help reduce exposure to the vulnerabilities that
affect our acquisition units.
• When conditions warrant that we use a bridging device in order to stay within the IP address
range of the hospital subnet, we use a specially configured Philips/ADAC Router. We set it
up to NOT do routing, but instead define a bridge group and use Access Control Lists (ACLs)
on each interface that will only let through packets with certain Ethernet MAC addresses.
This configuration only uses one additional IP address from the Hospital’s IP address pool.
This method of filtering takes considerable overhead to initially configure and also to keep
updated over time, when machines are added or swapped out. Keep in mind that if you
replace a failing Ethernet interface (say on a Sun Motherboard) you must update the Ethernet
address in the ACL for the appropriate interface in the Filtering Bridge.
2nd Ethernet Cards

• Although fairly easy to install and configure, they are the filter choice of last resort for ADAC
as they are not scalable and still interrupt the Pegasys processor to evaluate broadcast packets.
• Cannot provide security; only centralized solution like a router/VLAN can do that
• Provides a single-point filtered access to another network for a given Pegasys machine (we do
not use them on an Atlas motherboard).
• You need a 2nd Ethernet Card for each Pegasys machine that needs to talk to devices on the
other network. (For DICOM Print it is usually more cost effective to use a centralized
solution instead, so that all Pegasys units have connectivity to the remote DICOM printer).
• Have to interrupt the processor for every broadcast packet they see, could potentially affect
performance.
• They are especially handy if a site wants to have controlled access points (non-centralized
solution for the entire cluster) or if they only have a minimal number of IP addresses
available.
• Always remember to use “boot –r” after physically installing a 2nd Ethernet Card in a Pegasys
running Solaris 2.5.1 or greater so that the card will be seen by the operating system.
Important: Always use Philips/ADAC Parts when installing a 2nd Ethernet card. A
hospital provided or 3rd party interface might not be properly recognized as an hme device
on a Sun Pegasys workstation, even with a “boot –r” and may not work correctly. This
is especially important for the PCI based NIC’s for the Ultra60 and Ultra10. To be
absolutely sure, double-check the Philips/ADAC part number of the NIC against that
mentioned at the beginning of the instruction document appropriate for your particular
configuration.
Field Service Networking Hardware Parts
(Most commonly used only; Bold indicates preferred part, prices rounded to nearest U.S. dollar(s), verified as of 8/1/02)
Routers
5200-3680 Cisco 2621 Two 10/100 Cat5 NIC $7,349
5200-3280 Cisco 2514 Two 10Mbit AUI-NIC $4,364 Phase-out
Switches
5200-3657 Allied Telesyn 8port 10/100 $729
5200-3679 Allied Telesyn 24port 10/100 $1,712
5200-3681 Cisco 3524 24port 10/100 $6,905 CNG only
5200-3286 Netgear 2port 10/100 (MCD) $2,179 Old-MCD only
5200-3765 Linksys 8-port Switch / Network Filter (Router) $369 Skylight only
Hubs
5200-3509 Allied Telesyn 8port 10Mbit w/Coax $308 Join 10base2/Cat5
5101-8448 3COM 24port 10/100 2bus $4,800 Phase-out
5200-3008 Milan 4port w/ BNC (EPIC) $2,184
5200-3287 Netgear 8port 100Mbit (MCD) $3,489 Old-MCD only
Sun NICs (2nd Ethernet Cards)
5200-3541 Sun Ult60-Ult10 10/100 PCI $2,071
5200-3224 Sun Ult1-SS5/10/20 10/100 SBUS $2,936
5200-3310 Sun SS2/5/10/20 10Mbit SBUS $3,402
PC NICs (ISA or PCI Interface)
5200-1196 Ethernet, Acq PC, & Transcam 10Mbps $1,577 Old AUI/10b2 only
5200-3399 Linksys Non-PnP, use 2152-3329 for PnP Upg. $146 Obsolete, upg to PnP
2152-3329 Linksys PnP upgrade kit for Atlas PC, 10Mbps $316
5200-3558 Linksys PnP, Atlas Acq PC, Gantry PC, 10Mbps $152 Includes boot PROM
5200-3181 Ethernet PCI, Intel, 100Mbps $640 Old-MCD only
Transceivers
5200-3282 Allied Telesyn 10bT-AUI $116
5200-3011 Milan 10b2-AUI $203
5200-1785 Cabletron ST500 10b2-AUI (Thinnet ONLY) $1,390
5200-3001 Twisted Pair – Thin Adapter 10bT-10b2 $456
5200-1624 Cabletron ST500 10b5-AUI (Thicknet ONLY) $1,419 Need coring tool
Media Converters
5200-3009 “ThinTwist” 10b2-10bT Converter $506
Thinnet Repeaters (Cable runs > 600 feet in length)
5200-1887 Cabletron MR2000C 10b2-AUI $2,536 Thinnet only
Example Drawings of Typical Network Deployments
These following drawings illustrate examples of the minimal fundamental configurations.

These demonstrate several examples of connection to hospital backbones that have been supported by
Philips/ADAC Technical Support.
SWITCHED VLAN
Figure 3.1 illustrates our preferred setup where our Philips/ADAC-only 10/100 switch has a
single uplink to a VLAN port in the Hospital backbone. We set our default router value to an address
in our subnet that the IT Group provides as the entity, which will propagate our packets out to other
VLANs on their network.
Figure 3.1
IP=144.32.x.y IP=144.32.96.1
Mask=255.255.240.0 Hospital Backbone Mask=255.255.240.0
Switch with upstream
Gateway routing to other VLANs Gateway
Two One
DICOM 3rd Party DICOM NUMA ADAC DICOM

Viewing TCP/IP Image TCP/IP WebView Network
Station Acq. Cam Server based software Printer
Port in hospital switch

setup with VLAN for ADAC
Subnet 144.32.96.x
to allow filtering of extraneous
/etc/defaultrouter = 144.32.96.1
traffic and broadcasts
while providing connectivity
to the hospital equipment Auto-Sensing Cluster1 3rd Party
Pegasys
10/100 Switch Network
Acq.
Camera2
adac adac1 atlas1 adac2 NUMA 3rd Party

PegUltra PegUltra Acq PegUltra from other Acq.
(master) (client1) (camera1) (client2) protocols Camera1
Note that in this configuration, EVERY device in the entire network has a separate Cat5 drop
to the central switch. All devices connected to an Atlas (i.e., EPIC detectors, Atlas AX(i), acquisition
PC, gantry PC) should connect to its internal switch/hub. The Atlas utilizes a crossover cable or the
crossover port, connected to the rear chassis coupler to provide an uplink to the central switch. The
central switch should ideally be on UPS power, even if in a “network closet.” Philips/ADAC
currently recommends the APC Pro 650VA for an Ultra workstation which would more than suffice
for this application. Another recommendation is to request “hot spares” or extra drops in the event of
an infrastructure problem to avoid having to run cables on floors, in walls, etc.
Keep in mind that devices on the hospital network must also have a gateway value defined for
their subnet in order to return communication to us…
STANDARD ROUTING LAN
As shown in Figure 3.2, while still incorporating all Cat5 and a central 10/100 switch for
department connectivity, in this case we do not have a VLAN connection to the hospital network.
We use a router as a filtering network device that passes ONLY traffic destined to or originating from
our network. It is programmed by default to reject broadcast and/or multicast traffic, significantly
reducing to “background” traffic on the department network and thereby increasing reliability.
Figure 3.2
Subnet 144.32.96.x
Gateway = 144.32.96.1 Hospital Backbone

IP=144.32.96.1
ADAC Mask=255.255.240.0
Router
With Dual NICs IP=192.9.200.254
Mask=255.255.255.0
Subnet 192.9.200.x Auto-Sensing Cluster1 3rd Party

/etc/defaultrouter = 192.9.200.254 Pegasys
Acq.
Camera2

The router has two interfaces that MUST be programmed for different subnets. The two
subnets can be in two different classes (Class “C” and a class “B” in our example) or two different
subnets within the same class. Routers manage packets between one subnet and another. If there are
other routers on the hospital network, it is important that our router speaks the same protocols (RIP,
IGRP, etc…) as they do. If they use IGRP, then the site’s IT Group must tell us the Group #. If a
routing protocol other than RIP or IGRP is in use, then ask the site’s IT Group to configure the
routing protocol for you.
STANDARD ROUTING WAN
Figure 3.3 illustrates a typical setup of two Philips/ADAC clusters in different cities. Each
cluster has its own IP address subnet range and a local default router value. The exterior interfaces of
the routers are in a third subnet range defined just for the devices to use for their external linkages.
In cases where sites communicate through ISDN “cloud” the Router and DSU/CSU are
replaced by an ISDN Router, utilizing SPID numbers instead of the external IP addresses. Sites
should be purchasing routing equipment, line installation and monthly rates from a local Line Service
Provider (LSP). This LSP will be responsible for the routers (installation and configuration) and
lines.
Figure 3.3
IP=144.32.96.1 IP=144.32.127.254
Mask=255.255.240.0 Mask=255.255.240.0
Cluster2
Remote Clicnic 10/100 Switch Router DSU/CSU
City B
Subnet 144.32.96.x Site Purchases

/etc/defaultrouter = 144.32.96.1 High Speed
Routers and High
Hostnames = locbadac, locbadac1, locbadac2… Dedicated
Domainmane = YP.locb Speed lines from
Digital Service
(Frame-Relay,T1) Local Line Service
~0.5-11.5 Mb/min Provider
IP=144.32.80.1
Mask=255.255.240.0
Cluster1
Main Hospital 10/100 Switch Router DSU/CSU
City A
IP=144.32.127.253
Mask=255.255.240.0
Subnet 144.32.80.x
Hostnames = locaadac, locaadac1, locaadac2…
Domainmane = YP.loca
Important: UPPERCASE hostnames for ADAC units are NOT allowed! See page 9
of 11 (Form CS-16-01, “Custom Networking Site Survey) for name specifications. Also,
hostnames containing all numbers are NOT allowed. Hostname must start with a
lowercase letter. DICOM AE_Titles can begin with an uppercase letter and are often
ALL_CAPS.
FILTERING BRIDGE LAN
Figure 3.4 illustrates the use of an Philips/ADAC Router (same unit as in Figure 3.2) which
has been programmed to be a filtering bridge. Note that both NIC’s in the box are set to the same IP
address to facilitate the definition of a bridge group (see instructions in the next chapter). The control
of which packets can travel through the box is done with ACLs (Access Control Lists) which consist
of statements that permit forwarding of packets Ethernet MAC addresses of our choosing.
Figure 3.4
IP=144.32.96.1
Mask=255.255.240.0
Subnet 144.32.96.x
Gateway = 144.32.96.1 Hospital Backbone Gateway

Access-List 700 for DICOM units
ADAC Both NICS set to
Filtering Bridge IP=144.32.96.56
Mask=255.255.240.0
With Dual NICs
Access-List 701 for Pegs
Subnet 144.32.96.x Auto-Sensing Cluster1 3rd Party

/etc/defaultrouter = 144.32.96.1 Pegasys
Acq.
Camera2

This configuration can be used in a situation where the hospital IT staff cannot provide us a
VLAN or a dedicated subnet and they demand that we conform to their IP address configuration and
connect directly to their subnet addressing scheme. The router serves as a filter, eliminating
undesirable broadcast and multicast traffic. It also limits traffic to packets from systems defined in
the ACLs. However, this configuration requires more management as systems are added and/or
reconfigured on the hospital network or in the department.
2ND ETHERNET CARD
Figure 3.5 illustrates the use of a 2nd Ethernet Card to provide connection of one machine only
(“adac” in our example) to a hospital backbone. The 2nd Ethernet Card is assigned an address in the
Hospital IP address space while the main interface and the rest of the Philips/ADAC cluster remain in
the standard 192.9.200.x scheme. If additional Pegasys units need connectivity, they must have their
own 2nd Ethernet card and unique IP addresses.
Figure 3.5
IP=144.32.96.1
Mask=255.255.240.0
Subnet 144.32.96.x
Gateway = 144.32.96.1 Hospital Backbone Gateway

Auto-Sensing Cluster1 3rd Party

IP=144.32.96.56 Pegasys
Acq.
Mask=255.255.240.0
2nd Camera2
NIC
Subnet 192.9.200.1
(Refer to Form CS-16-01, Page 10 of 13, “Custom Networking Site Survey”) Sometimes the
nd
2 Ethernet card solution is the only one that will work at a given site, especially with sites that
cannot provide enough IP addresses. The major drawbacks to a 2nd Ethernet card are (a) the host
Pegasys will be subject to the hospital network’s broadcast traffic direct, interrupting the CPU for
every broadcast packet, and (b) ONLY the host Pegasys with the card (in this example “adac”) can
communicate with the hospital backbone.
LOCAL ONLINE DOCUMENTATION OF CUSTOM NETWORKS
Whenever a WAN (Wide Area Network) or custom LAN to a hospital/clinic network is
implemented, best practice under any circumstance is to use unique hostnames and domain names
that relate to each location. For extremely complex networks, the FSE might also consider placing a
pointer to a file containing notes describing network configuration in the modem host’s /etc/motd
file. This text file is displayed on the screen during every login, thus can be used to provide useful
information to any technical or applications support person that might modem in to assisting
troubleshooting a network related problem. Here is an example:
PEGASYS@jeff:#[1] more /etc/motd

Sun Microsystems Inc. SunOS 5.5.1 Generic May 1996
31 Dec 99 23:59:59 -- Y2K Check Performed. System is Y2K Clean - just in time!
*** Attention Remote Support: Complex custom network configured. Please see
*** the /etc/adacnet.info file for more information!
With this file in place, these messages will be displayed during every login via modem,
alerting remote support personnel to special network notes. Example login:
SUPERUSER@jeff:#[14] telnet jeff

Trying 12.34.56.78...
Connected to jeff.
Escape character is '^]'.
UNIX(r) System V Release 4.0 (jeff)
login: pegasys
Last login: Wed Aug 8 15:46:19 from jeff
Sun Microsystems Inc. SunOS 5.5.1 Generic May 1996
31 Dec 99 23:59:59 -- Y2K Check Performed. System is Y2K Clean - just in time!
*** Attention Remote Support: Complex custom network configured. Please see
*** the /etc/adacnet.info file for more information!
Welcome to jeff.
Here is an example of what you might place in the /etc/adacnet.info file:
PEGASYS@jeff:#[1] more /etc/adacnet.info
#######################################################################
#
# Any Hospital, Any City, State, USA *** Sun Host Database
# ADAC FSE Representative: Joe Zuchecki
# Network Configuration Engineer: Kim Johnson
# Clinical Engineering Technician: Mark Weber
#
# Default Domain is YP.anyhospital
# Default Router is 10.99.150.1 (Connection to WAN Locations)
# Subnet masking is 255.255.255.0 (/24)
#
# Atlas (FORTE) connected through backplane of Atlas to allow 100 MBits
# Entire network is CAT-5 backbone to a dedicated 10/100 switch.
# Pegasys systems are connected directly via 10baseT jack on motherboard
# Ultra-60 systems are connected via 100baseT jack on motherboard
# VPN is configured and in use. IT responsible for implementation.
#
#######################################################################
Installing Custom Networking Hardware
This section includes procedures for installing custom networking hardware and some
supporting operating system configurations, whereas the previous section includes diagrams to help
you visualize hardware usage.
When customizing network configuration, it is a good practice to work from a list of network
information (IP addresses, subnet masks, hostnames, default router values, allowed Ethernet
numbers, etc.) and from “Before” and “After” network drawings. These documents should have been
generated while the Custom Networking Site Survey was filled out. A copy of this information
should be kept with the system, at the site, just in case an installer and/or other FSE needs or needs to
update the information in the future. You might consider taping a copy to the top of a central switch
or network closet door, if allowed.
You will find templates for such lists in the Nuclear Medicine Site Survey Document
CS-16-1*. There is a default template in the “Cluster” Networking Site Survey, item 7, IP Addresses
and Hostnames – Default Values, on page 7 of 9. Also you will find a custom template in the
“Custom” Networking Site Survey, item 10, IP Addresses and Hostnames – Custom Values, on page
9 of 11.)
Atlas 4-port Hub upgrade to 8-port Switch
For reliability and better performance you are able to upgrade Atlas units in the field from an
older Milan 10Mbit 4-port Hub to a newer 10/100Mbit 8-port switch. You should order the upgrade
kit (2152-3318), which contains a detailed instruction document (9343-2263) on how to perform this
upgrade.
To summarize this procedure, the FSE will be eliminating all coaxial network cable inside the
Atlas (except for spaghetti coax or RG-174 for detectors, which run through a “Tee” connector to a
Cat5 media converter) and upgrading all devices to Cat5. All these connections will route to the new
8-port switch and increase network reliability.
Another advantage of the 10/100 switch versus a 4-port 10Mbit hub is that Atlas and Ultra
Pegasys computers will auto sense the 100Mbit port and link up automatically at the faster speed,
thereby dramatically increasing the speed of Atlas commits the configured database host. (This
statement assumes both Atlas AX(i) and host Pegasys Ultra are connected to 100Mbit ports).
Remember that network effective throughput is governed by the weakest link. Example: If
your Atlas has an internal 10/100Mbit switch and your Ultra is plugged into a different 10/100Mbit
switch, but both are uplinked to a central 10Mbit hub, then your communications speed, for commits
of patient data, will be limited to 10Mbits / second.
Configuring a Router for Straight Routing
You would use and configure an Philips/ADAC Router (5200-3680) to do straight routing
when we are able to have a subnet range defined entirely for our Philips/ADAC equipment. Some
sites may allow us to keep our default numbering scheme but usually they will require us to renumber
our IP addresses to fit into their numbering scheme. If we are only changing the IP addresses and not
the hostnames or NIS domainname, then we can make use of the manual renumbering instructions
“Shortcut Procedure for changing IP address, subnet, default router ONLY” in this document.
Otherwise, you will have to use network_pegx in “custom” mode.
Hospital Target
ADAC Network ADAC or
Infrastructure Equipment
(Subnet A) Hospital Router
(Subne t B) (Subnet B)
Keep in mind you will need to be creating a default router entry in an

/etc/defaultrouter file. You should consult the instructions, notes and guidelines at the end
of this chapter to understand exactly how that file should be configured. See Figures 3.2 and 3.3 in
the previous chapter for examples of how this type of outer would fit into typical Philips/ADAC
configurations.
Note: IP Addresses shown in the following directions are examples only; your local
addresses will vary. Be sure to coordinate with the hospital network IT group for
configurations before you begin.
Things you need before you begin:
• For each of the two 10/100 interfaces, you need the correct values for IP address, Subnet
Mask, and Full or Half Duplex.
• You also need to assign which Routing Protocol the router will use, RIP or IGRP (if IGRP the
Site IT Group must tell you which IGRP Group number to use). If any other type of Routing
Protocol is to be used, give the IT Group access to the router and let them configure for it.
• Finally, you’ll assign a “hostname” for the router and create three passwords, which should be
shared with the IT Group. They may, in fact, want to have input on what the hostname and
password entries should be.
To begin, set up a Hyperterm or Procomm session to your laptop’s serial port (usually COM1
but check your system configuration) with settings Bits per second (Baud rate) = 9600, Data bits = 8,
Parity = None, Stop bits = 1, Flow Control = Hardware. Then connect the included flat RJ45 console
cable to the 9-pin adapter and plug it into your serial port. It is always safest doing configurations
with you laptop and the console port, so that if the network settings for the Ethernet interfaces
become inactive, you won’t cut a telnet session out from under yourself. If possible, you should
physically connect the two interfaces, 0/0 and 0/1, to their respective live connections prior to
configuration. Our convention is to attach the 0/0 interface to the hospital (or department) side and
to attach the 0/1 interface to the Pegasys cluster side.
If this router has already been configured, you should restore its factory default “out-of-the-
box” status by doing the “erase_startup” command shown at the beginning of this procedure. If
configuring from a factory default state, skip to the section where it asks if you want to enter “the
initial configuration dialog,” indicated by the pointing hand clipart:
System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)

Copyright (c) 1999 by cisco Systems, Inc.
TAC:Home:SW:IOS:Specials for info
C2600 platform with 32768 Kbytes of main memory
program load complete, entry point: 0x80008000, size: 0x371d9c
Self decompressing the image :

#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.

170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software

IOS (tm) C2600 Software (C2600-I-M), Version 12.0(3)T3, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 15-Apr-99 15:41 by kpma
Image text-base: 0x80008088, data-base: 0x80693A88
cisco 2621 (MPC860) processor (revision 0x102) with 24576K/8192K bytes of memory.
Processor board ID JAD042707XJ (1198747761)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
2 FastEthernet/IEEE 802.3 interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
Press RETURN to get started!
00:00:07: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up

00:00:07: %SYS-5-CONFIG_I: Configured from memory by console
00:00:07: %SYS-5-RESTART: System restarted --
00:00:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0,
changed state to up
changed state to up
<enter>
adacrtr>enable
Password: adacsu
adacrtr#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm] <enter>
[OK]
Erase of nvram: complete
adacrtr#
< Power-cycle the router now and see the startup info again >

#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.

Bridging software.
--- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]: yes
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Basic management setup configures only enough connectivity

for management of the system, extended setup will ask you
to configure each interface on the system
Would you like to enter basic management setup? [yes/no]: no
First, would you like to see the current interface summary? [yes]: yes
Any interface listed with OK? value "NO" does not have a valid configuration
Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 unassigned NO unset up up
Configuring global parameters:
Enter host name [Router]: adacrtr
The enable secret is a password used to protect access to
privileged EXEC and configuration modes. This password, after
entered, becomes encrypted in the configuration.
Enter enable secret: adacsu
The enable password is used when you do not specify an

enable secret password, with some older software versions, and
some boot images.
Enter enable password: adacen
The virtual terminal password is used to protect

access to the router over a network interface.
Enter virtual terminal password: adacvt
Configure SNMP Network Management? [yes]: no
Configure IP? [yes]: yes
Important: Next two answers based in information provided by the hospital IT group.
If IGRP, you need group #. If neither, then disable both and ask the hospital IT group to
configure this router.
< This example shows the configuration of the RIP protocol, if your required protocol is IGRP
then you would switch your yes and no answers below. Additionally you would be asked for an
IGRP group number (assigned by the site IT group). Also in the configuration outputs shown
below you would see “router igrp igrp_group#” instead of “router rip”. >
Configure IGRP routing? [yes]: no
Configure RIP routing? [no]: yes
< In some versions of the Cisco IOS you are asked the following >
Configure Bridging? [no]: no
Async lines accept incoming modems calls. If you will have

users dialing in via modems, configure these lines.
Configure Async lines? [yes]: no
Configuring interface parameters:
< Note: If the ports that the router will uplink to are capable of full-duplex, you may enable it
for an interface to realize increased throughput >
Do you want to configure FastEthernet0/0 interface? [yes]: yes
Use the 100 Base-TX (RJ-45) connector? [yes]: yes
Operate in full-duplex mode? [no]: yes
Configure IP on this interface? [yes]: yes
IP address for this interface: 144.32.96.1
Subnet mask for this interface [255.255.0.0] : 255.255.240.0
Class B network is 144.32.0.0, 20 subnet bits; mask is /20
Class C network is 192.9.200.0, 24 subnet bits; mask is /24
The following configuration command script was created:
hostname adacrtr
enable secret 5 $1$LgL/$L9C2eCDR44IoTYKZWf3ge/
enable password adacen
line vty 0 4
password adacvt
no snmp-server
!
ip routing
no bridge 1
!
interface FastEthernet0/0
media-type 100BaseX
full-duplex
ip address 144.32.96.1 255.255.240.0
!
media-type 100BaseX
full-duplex
ip address 192.9.200.254 255.255.255.0
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
!
router rip
redistribute connected
network 144.32.0.0
network 192.9.200.0
!
end
< Note: Now we will tell it to save to nvram and reboot >
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Enter your selection [2]: 2
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.

changed state to up
changed state to up
00:02:27: %IP-5-WEBINST_KILL: Terminating DNS process
<enter>
adacrtr>
adacrtr>enable
Password: adacsu
< Now we’ll check the configuration >

adacrtr#sho run
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname adacrtr
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.1 255.255.240.0
no ip directed-broadcast
full-duplex
!
ip address 192.9.200.254 255.255.255.0
full-duplex
!
router rip
network 144.32.0.0
network 192.9.200.0
!
ip classless
no ip http server
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password adacvt
login
!
no scheduler allocate
end
< We have found that we have to do an explicit copy command to ensure it is saved to nvram >
adacrtr#
adacrtr#copy running start
Destination filename [startup-config]? <enter>
< And finally let’s reboot the router and make it reload from nvarm >
adacrtr#
adacrtr#reload
Proceed with reload? [confirm] <enter>
00:04:27: %SYS-5-RELOAD: Reload requested


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.

changed state to up
changed state to up
<enter>
adacrtr>
adacrtr>enable
Password: adacsu
adacrtr#sho run
!
version 12.0
!
hostname adacrtr
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.1 255.255.240.0
full-duplex
cdp enable
!
ip address 192.9.200.254 255.255.255.0
full-duplex
no cdp enable
!
router rip
network 144.32.0.0
network 192.9.200.0
!
ip classless
no ip http server
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Now we will turn off the annoying “feature” that tries to externally resolve misspellings>
<Make sure your line settings match the line entries you see in a show run>
adacrtr#conf term
Enter configuration commands, one per line. End with CNTL/Z.
adacrtr(config)#line con 0
adacrtr(config-line)#transport preferred none
adacrtr(config-line)#exit
adacrtr(config)#line aux 0
adacrtr(config)#line vty 0 4
adacrtr(config)#no service config
adacrtr(config)#^Z
adacrtr#
00:01:56: %SYS-5-CONFIG_I: Configured from console by console
< Let’s check to be sure our changes have been put in place. However, the changes won’t be
effective until after we reboot the router. >
<enter>
adacrtr#sho run
!
version 12.0
!
hostname adacrtr
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.1 255.255.240.0
full-duplex
no cdp enable
!
ip address 192.9.200.254 255.255.255.0
full-duplex
no cdp enable
!
router rip
network 144.32.0.0
network 192.9.200.0
!
ip classless
no ip http server
!
!
line con 0
exec-timeout 0 0
transport preferred none
line aux 0
line vty 0 4
password adacvt
login
!
end
adacrtr#
< Now let’s copy our in-memory configuration to nvram >

< Now we will reboot the router so it reloads from nvram >
adacrtr#
adacrtr#reload


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.

Bridging software.

changed state to up
changed state to up
< Let’s check that configuration one last time >

<enter>
adacrtr>
adacrtr>enable
Password: adacsu
adacrtr#sho run
!
version 12.0
!
hostname adacrtr
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.1 255.255.240.0
full-duplex
no cdp enable
!
ip address 192.9.200.254 255.255.255.0
full-duplex
no cdp enable
!
router rip
network 144.32.0.0
network 192.9.200.0
!
ip classless
no ip http server
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacrtr#
< Note: Done. Now you may disconnect the console cable, plug the two Ethernet ports into the
hubs or switches and do some ping tests. >
< Create defaultrouter and local hostname entries for the router interfaces. >
On every Pegasys and Atlas, create (or edit) the file /etc/defaultrouter, entering
only the IP address interface on the ADAC side of the router. On Pegasys network master, become
superuser (su -) edit the file /etc/hosts to add the IP address and hostnames for both of the router
interfaces. You also should put in any “internal” and “external” IP addresses of remote routers to
help document the topology and to make it easier when you do ping tests. EXAMPLE: from above
configuration
192.9.200.254 adacrtr # near side of router

144.32.96.1 adacrtrhosp # far (hospital) side of router
Now update and push the NIS maps:
cd /var/yp
make
Finally, reboot the Pegasys network. If you have not already done so, test connectivity with
the ping command. Determine if you can ping:
§ the Pegasys network’s router interface (“near side” of router).

§ the hospital network’s router interface (“far side” of router).
§ Other known network devices/nodes/routers on the hospital network.
Important: If you can ping both sides of the router yet cannot ping a hospital-network
device, that device might be missing a gateway entry, which is required to do a return echo
to us when we ping it.
Confirm /etc/defaultrouter file (or gateway value) for nodes on far network, if
necessary. Remote systems must have a gateway setting to communicate back to our subnet. An
example of doing this would be using a printer’s front panel keypad to enter a gateway IP address.
Once properly configured, connected and booted up, it should be possible to open a Unix
window on a Pegasys and telnet to the IP address or hostname you have assigned to the interface on
the ADAC side of the router. Then you can get in to enable mode to examine the status of the router,
or tweak some aspects of the configuration. Do not change IP addresses during a telnet session or
you will lose your connection. Example of telnetting in:
telnet adacrtr
password: <our standard is adacvt>
adacrtr> enable
password: <our standard is adacsu>
adacrtr#
< ADDITIONAL COMMAND INFO: The following commands may be done through a telnet
session into one of the interfaces, but to be completely safe it is recommended to use the console
port to adjust the configuration >
< telnet in to update the clock to current time UTC/GMT. Remember to adjust to GMT
from your timezone. The device ONLY displays GMT so be sure you get the conversion
correct. Do this once you have the unit installed, connected and powered on. >
*** From a UNIX Window on a Pegasys:
PEGASYS-adac> telnet 144.32.96.1 <enter>

Password: adacvt <enter>
adacfilter>en
Password: adacsu
adacfilter#clock set 12:24:00 11 JUN 2001
adacfilter#sho clock
12:24:04.147 UTC Mon Jun 11 2001
Gateway of Last Resort
Note: In a custom network environment where there is another router (gateway) on the
hospital side of the network (leading to other segments of the hospital WAN), you might
run into a situation where IP addresses outside the local hospital segment cannot be
reached (this should not be the case if the routing protocol has been correctly setup so all
the routers can share routing tables). Additionally, hospital IT staff might need to gain
access to our router from a remote location to assist in configuration. In these cases, you
may need to define the hospital’s router as a “Gateway of last resort.” Be sure to speak
with your local IT representative to (a) determine if this is necessary, and (b) obtain the
OTHER router’s IP address. To define a “Gateway of last resort,” follow these
instructions:

PEGASYS-adac> telnet 192.9.200.254
Password: adacvt
<enter>
adacrtr>en
Password: adacsu
adacrtr#conf term
adacrtr(config)#ip route 0.0.0.0 0.0.0.0 144.32.111.254
adacrtr(config)#^Z
adacrtr#
%SYS-5-CONFIG_I: Configured from console by console
adacrtr#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is 144.32.111.254 to network 0.0.0.0
C 192.9.200.0/24 is directly connected, FastEthernet0/1
S* 0.0.0.0/0 [1/0] via 144.32.111.254

adacrtr#reload
. . . <router reboots>
Configuring a Router as a Filtering Bridge
ALL TARGET DEVICES IN SAME SUBNET
You would configure and use an Philips/ADAC Router (5200-3680) to be a Filtering Bridge
when our equipment must be renumbered for connection to an existing hospital network AND the
Philips/ADAC equipment will exist in the same IP subnet as the equipment we are connecting to
(DICOM Printers, PACS, etc.) In this configuration the router is NOT setup to do routing. Instead,
we configure a bridge-group over both of the Ethernet interfaces. We only need to be assigned one
IP address from within the subnet for this device as we setup the same address on both Ethernet
interfaces. The filtering is performed by the use of Access-Lists, one defined for each interface,
which contain the Ethernet MAC addresses of the devices that are allowed to talk through Filtering
Bridge from one side or the other.
Hospital Target
ADAC Network Filtering
(Subnet A) Bridge
(Subnet A) (Subnet A)
If we are only changing the IP addresses on the Philips/ADAC equipment and not the
hostnames or NIS domainname, then we can make use of the manual renumbering instructions,

/etc/defaultrouter file. This will typically point to a router or gateway out on the hospital
network. You should consult the instructions, notes and guidelines at the end of this chapter to
understand exactly how that file should be configured. See Figure 3.4 in the previous chapter for an
example of how this type of router setup would fit into typical Philips/ADAC configurations.
• One IP address in the Pegasys subnet that will be assigned to BOTH cards in the router
• The subnet mask (or netmask)
• A list of Ethernet MAC addresses for the Pegasys units needing access (These will go into
access-list 701)
• A list of Ethernet MAC addresses for the Hospital units needing access (These will go into
access-list 700)
There are several ways to collect the Ethernet MAC addresses which you will need to create
your access lists. The most obvious is to ask the site’s IT group to provide you with a list of the
hostnames, IP addresses and Ethernet MAC addresses. If you only have the IP addresses then it is
possible to use a combination of a “ping” command and an “arp” command to gather the information
you need. This can be done from a variety of machines. Of course for the units the Pegasys cluster
knows of you can do it from a UNIX window on a Pegasys. For the hospital network you might need
to setup your laptop or the router interface to an available IP address that was given to you by the IT
group. Then you can do the ping and arp from that unit.
• From Pegasys UNIX window: ping IP_address arp -a
• From Laptop CMD window: ping IP_address arp -a
• From Router command line: ping IP_address show ip arp


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]
cisco Systems, Inc.


Bridging software.

changed state to up
changed state to up
<enter>
adacrtr>
adacrtr>enable
Password: adacsu
adacrtr#
Erasing the nvram filesystem will remove all files! Continue? [confirm]
[OK]
adacrtr#
< You must now power cycle the router to clear and start from scratch >

#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.


Enter host name [Router]: adacfilter


some boot images.

Configure RIP routing? [no]: no
< Note: We did NOT define any Routing Protocols >
< Note: Notice that we used the same IP address on both cards. We will now see the
automatically-generated config definition. >
hostname adacfilter
enable secret 5 $1$9WZo$XATUOm7heWm4ZXmROIjts0
line vty 0 4
password adacvt
no snmp-server
!
ip routing
!
media-type 100BaseX
full-duplex
ip address 144.32.96.56 255.255.240.0
!
media-type 100BaseX
full-duplex
ip address 144.32.96.56 255.255.240.0
!
end
< Note: Now we tell it to save to nvram and reboot >

144.32.96.0 overlaps with FastEthernet0/0 < This is an OK Message >


changed state to up
changed state to up
00:02:11: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to
administratively down
changed state to down
<enter>
adacfilter>
adacfilter>enable
Password: adacsu
adacfilter#
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.56 255.255.240.0
full-duplex
!
no ip address
shutdown
full-duplex
< Note: Notice that the router thinks we entered an illegal config by having the same IP
address on both cards, so it rejected it for the second card and orders a shutdown for that
interface (we will fix that up in just a bit) >
!
ip classless
no ip http server
!
!
line con 0
transport input none
line aux 0
line vty 0 4
password adacvt
login
!
end
< Now we’ll go back in and redefine the same IP address and setup a bridge group>
adacfilter#conf term
adacfilter(config)#no ip routing
adacfilter(config)#no service config
adacfilter(config)#line con 0
adacfilter(config-line)#transport preferred none
adacfilter(config-line)#exit
adacfilter(config)#line aux 0
adacfilter(config)#line vty 0 4
adacfilter(config)#bridge 1 protocol ieee
adacfilter(config)#int FastEthernet 0/1
adacfilter(config-if)#ip address 144.32.96.56 255.255.240.0
adacfilter(config-if)#bridge-group 1
adacfilter(config-if)#exit
adacfilter(config-if)#^Z
adacfilter#
<enter>
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
shutdown
full-duplex
bridge-group 1
!
ip classless
no ip http server
!
bridge 1 protocol ieee
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Now we’ll set up the access lists for each card and tie them to the correct interfaces.
Remember the 700 list is Hospital devices and is tied to the 0/0 interface, which uplinks to the
hospital network switch or hub, and the 701 list is Philips/ADAC Pegasys devices and is tied to
0/1 interface, which uplinks to the Philips/ADAC network switch or hub. We will also undo the
shutdown of the second interface. >
adacfilter(config)#access-list 700 permit 0800.6600.b9aa
adacfilter(config)#access-list 700 permit 0800.6600.bb6a
adacfilter(config)#access-list 700 permit 0800.6600.9afa
adacfilter(config)#access-list 700 permit 0800.6600.c1aa
adacfilter(config)#access-list 700 permit 0800.690d.233a
adacfilter(config)#access-list 700 permit 0800.20ad.b36a
adacfilter(config)#access-list 701 permit 0800.201b.2dca
adacfilter(config)#access-list 701 permit 0800.207e.863a
adacfilter(config)#access-list 701 permit 0800.2094.4f4a
adacfilter(config)#access-list 701 permit 0800.20ea.d01a
adacfilter(config)#access-list 701 permit 0800.209b.ae5a
adacfilter(config)#access-list 701 permit 0800.20ad.469a
adacfilter(config-if)#bridge-group 1 input-address-list 700
adacfilter(config-if)#bridge-group 1 input-address-list 701
adacfilter(config-if)#no shutdown
adacfilter(config-if)#
changed state to up
adacfilter#
<enter>
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
bridge-group 1 input-address-list 700
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
!
ip classless
no ip http server
!
access-list 700 permit 0800.6600.b9aa 0000.0000.0000
access-list 700 permit 0800.6600.bb6a 0000.0000.0000
access-list 700 permit 0800.6600.9afa 0000.0000.0000
access-list 700 permit 0800.6600.c1aa 0000.0000.0000
access-list 700 permit 0800.690d.233a 0000.0000.0000
access-list 700 permit 0800.20ad.b36a 0000.0000.0000
access-list 701 permit 0800.201b.2dca 0000.0000.0000
access-list 701 permit 0800.207e.863a 0000.0000.0000
access-list 701 permit 0800.2094.4f4a 0000.0000.0000
access-list 701 permit 0800.20ea.d01a 0000.0000.0000
access-list 701 permit 0800.209b.ae5a 0000.0000.0000
access-list 701 permit 0800.20ad.469a 0000.0000.0000
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Note: Now we will commit our config and reboot the router >
adacfilter#copy running start
adacfilter#reload


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.

changed state to up
changed state to up
< Note: Now we review our config to confirm it came back up correctly >
<enter>
adacfilter>
adacfilter>enable
Password: adacsu
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
no ip mroute-cache
full-duplex
bridge-group 1
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
no ip mroute-cache
full-duplex
bridge-group 1
!
ip classless
no ip http server
!
access-list 700 permit 0800.6600.b9aa 0000.0000.0000
access-list 700 permit 0800.6600.bb6a 0000.0000.0000
access-list 700 permit 0800.6600.9afa 0000.0000.0000
access-list 700 permit 0800.6600.c1aa 0000.0000.0000
access-list 700 permit 0800.690d.233a 0000.0000.0000
access-list 700 permit 0800.20ad.b36a 0000.0000.0000
access-list 701 permit 0800.201b.2dca 0000.0000.0000
access-list 701 permit 0800.207e.863a 0000.0000.0000
access-list 701 permit 0800.2094.4f4a 0000.0000.0000
access-list 701 permit 0800.20ea.d01a 0000.0000.0000
access-list 701 permit 0800.209b.ae5a 0000.0000.0000
access-list 701 permit 0800.20ad.469a 0000.0000.0000
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#
< Note: Done. Now you can plug it into the correct hubs or switches and do some ping tests. >
< Create local hostname entries for the filtering-bridge and any router interfaces. >
On Pegasys network master, become superuser (su -) edit the file /etc/hosts to add the IP
address and hostname for the filtering-bridge interface. You also should put in any “internal” and
“external” IP addresses of remote routers to help document the topology and to make it easier when
you do ping tests. EXAMPLE: from above configuration
144.32.96.56 adacfilter # address of our filtering-bridge

144.32.96.1 hosprtrint # near (internal) side of hospital router
144.32.31.254 hosprtrext # far (external) side of hospital router
cd /var/yp
make
§ the Pegasys network’s filtering-bridge interface.

Note: If you can ping the filtering-bridge yet cannot ping a hospital-network device, that
device might be beyond the local subnet we are connected to. We may need to get more
details about the Ethernet MAC address of an encapsulating router which brings the
target’s packets to our local subnet. The IT group is the best place to start to investigate
these details.
the ADAC side of the filtering-bridge. Then you can get in to enable mode to examine the status of
the router, or tweak some aspects of the configuration. Do not change IP addresses during a telnet
session or you will lose your connection. Example of telnetting in:
telnet adacfilter
adacfilter> enable
adacfilter#
session into one of the interfaces, but to be completely safe it is best to use the console port to
adjust the configuration. To add an entry to an existing access list and commit the changes, be
sure you use the correct list number (700 for hospital devices and 701 for ADAC devices ) >

adacfilter>en
Password: adacsu
adacfilter(config)#access-list 700 permit 0800.66ab.cdef
adacfilter(config)#^Z
adacfilter#
<enter>
adacfilter#
Important: To clean out a mistaken, obsolete or unwanted entry in an access list you
have to delete the whole access-list and re-enter all elements. Unfortunately this is a
limitation of the Cisco command line environment for which we have no control.

Password: adacvt
<enter>
adacfilter>en
Password: adacsu
adacfilter(config)#no access-list 700
adacfilter#
< follow the access-list creation steps shown above in this document >
< telnet in to update the clock to current time UTC/GMT. Remember to adjust to GMT from
your timezone. The device ONLY displays GMT so be sure you get the conversion correct. Do
this once you have the unit installed, connected and powered on. >
PEGASYS-adac> telnet 144.32.96.56 <enter>

adacfilter>en
Password: adacsu
12:24:04.147 UTC Mon Jun 11 2001
Configuring a Router as a Filtering Bridge
TARGET DEVICES BOTH WITHIN SUBNET & BEYOND HOSPITAL ROUTER (IP LOCKED)
You would use this procedure to configure a Philips/ADAC Router (5200-3680) to be a

Filtering Bridge when our equipment is connected to a hospital network AND the remote devices are
connected directly to the Hospital network as well as having to go through a Hospital router (DICOM
Printers, PACS, etc.) When we connect in this way, the Ethernet packets received from the remote
hosts (through the router) are “branded” with the MAC address of the encapsulating router instead of
the actual device hardware MAC address. However, the Ethernet packets from devices connected
directly to the hospital network contain their own MAC address.
Target
ADAC Ne twork Filtering Bridge
Equipment
(Subnet A) (IP locked)
(Subnet A)
Hospital Target
Hospital
Route r
(Subnet A) (Subnet B)
In this configuration the router is NOT setup to do routing. Instead, we configure a bridge-
group over both of the Ethernet interfaces. We only need to be assigned one IP address from within
the subnet for this device as we setup the same address on both Ethernet interfaces. The filtering is
performed by the use of Access-Lists, one defined for each interface, which contain the Ethernet
MAC addresses of the devices that are allowed to talk through Filtering Bridge from one side or the
other. The important point here is that we have to accommodate for the MAC addresses of some the
target devices changing in the Ethernet packets as they pass through the Hospital’s router(s).
Additionally, we are qualifying each allowed target device by examining its IP address. This impacts
throughput and involves more bookkeeping and overhead, but it provides improved security. We will
also configure special constructs to support the “ARP” conversations that always occur between
devices as they learn each other’s MAC addresses as they assemble the IP packets.
If we are only changing the IP addresses on the Philips/ADAC equipment and not the
hostnames or NIS domainname, then we can make use of the manual renumbering instructions,

/etc/defaultrouter file. This will typically point to a router or gateway out on the hospital
network. You should consult the instructions, notes and guidelines at the end of this chapter to
understand exactly how that file should be configured. See Figure 3.4 in the previous chapter for an
example of how this type of router setup would fit into typical Philips/ADAC configurations.
• One IP address in the Pegasys subnet that will be assigned to BOTH cards in the router
• The subnet mask (or netmask)
• A list of Ethernet MAC addresses and IP Addresses for the Pegasys units needing access
(These will go into access-list 1111. Each Pegasys will get a pair of entries, one for standard
IP and one for ARP)
• A list of Ethernet MAC addresses and IP addresses of the Hospital units needing access, that
are located on the same subnet (or Philips/ADAC side) of the Hospital router. (These will go
into access-list 1110. Each local target will get a pair of entries, one for standard IP and one
for ARP)
• A list of Ethernet MAC addresses and IP addresses of the Hospital units needing access that
are located on the other side of the Hospital router. (These will go into access-list 1110. Each
remote target will get one entry for standard IP). However, since they’re on the other side of
the hospital router, their Ethernet MAC addresses will NOT go into access-list but we do want
to make note of them though, in case that changes and they’re moved to our side of the
hospital router.
• The Ethernet MAC address and IP address of both of interfaces of the Hospital router that
encapsulates the packets right before they enter our subnet. (These addresses will be
combined with statements containing each of the individual IP addresses and go into access-
list 1110 to cover all units located on the far side of the Hospital router. They will also be
used in statements for communication from each router interface as well as any ARP packets
that are propagated by the router.)
Note: The IP addresses will need to be converted to hexadecimal notation, i.e.,

144.112.96.42 = 0x9070602A. See Chapter 2 on using the IP Subnet
Calculator for easily doing the conversion.)
There are several ways to collect the Ethernet MAC addresses which you will need to create
your access lists. The most obvious is to ask the site’s IT group to provide you with a list of the
hostnames, IP addresses and Ethernet MAC addresses. If you only have the IP addresses then it is
possible to use a combination of a “ping” command and an “arp” command to gather the information
you need. This can be done from a variety of machines. Of course for the units the Pegasys cluster
knows of you can do it from a UNIX window on a Pegasys. For the hospital network you might need
to setup your laptop or the router interface to an available IP address that was given to you by the IT
group. Then you can do the ping and arp from that unit.
• From Pegasys UNIX window: ping IP_address arp -a
• From Laptop CMD window: ping IP_address arp -a
• From Router command line: ping IP_address show ip arp
Consider the following drawing and table while you follow the programming example below:
IP=144.32.96.1
MAC=0009.43f7.0d20
NucMed Switch Radiology Switch
Subnet 144.32.96.x NucMed Subnet 144.32.112.x
Mask=255.255.240.0 Gateway Mask=255.255.240.0
Gateway = 144.32.96.1 Gateway = 144.32.112.1
IP=144.32.112.1
MAC=0009.43f7.0d21
FUJI FUJI RTP Doctor’s
DICOM 1 DICOM 3 for Image 2 WebView
Printer 1 Printer 2 Fusion PC
IP=144.32.96.26 IP=144.32.96.44 IP=144.32.112.188 IP=144.32.112.193
MAC=00c0.4f01.e0d2 MAC=00c0.4f01.ded5 MAC=0800.20f5.8606 MAC=0010.a4d1.3805
Access-List 1110 for Hospital units
ADAC MAC=0009.7c8b.a240
Filtering Bridge Both NICS set to IP=144.32.96.56 Mask=255.255.240.0
MAC=0009.7c8b.a241
With Dual NICs
Access-List 1111 for Pegs
Auto-Sensing
10/100 Switch Pegasys Network Cluster
Subnet 144.32.96.x
Mask=255.255.240.0
adac adac1 /etc/defaultrouter = 144.32.96.1
PegUltra 4 PegUltra
(master) (client1)
IP=144.32.96.60 IP=144.32.96.70
MAC=0800.2092.d4c5 MAC=0800.2091.a72e
It is often helpful to represent this information in tabular form:
MAC Address IP address (decimal) IP address (hex) Description

0800.2092.d4c5 144.32.96.60 0x9020603C Pegasys Master
0800:2091.a72e 144.32.96.70 0x90206046 Pegasys Client
0009.7c8b.a241 144.32.96.56 0x90206038 Filtering-Bridge 0/1
0009.7c8b.a240 144.32.96.56 0x90206038 Filtering-Bridge 0/0
00c0.4f01.e0d2 144.32.96.26 0x9020601A Fuji Print Spooler #1
00c0.4f01.ded5 144.32.96.44 0x9020602C Fuji Print Spooler #2
0009.43f7.0d20 144.32.96.1 0x90206001 NucMed Router 0/0
0009.43f7.0d21 144.32.112.1 0x90207001 NucMed Router 0/1
0080.20f5.8606 144.32.112.188 0x902070BC RTP for Image Fusion
0010.a4d1.3805 144.32.112.193 0x902070C1 Dr’s WebView PC


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.

changed state to up
changed state to up
<enter>
adacrtr>
adacrtr>enable
Password: adacsu
adacrtr#
Erasing the nvram filesystem will remove all files! Continue? [confirm]
[OK]
adacrtr#
< You must now power cycle the router to clear and start from scratch >

#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.

Enter host name [Router]: adacfilter


some boot images.

Configure RIP routing? [no]: no
< Note: We did NOT define any Routing Protocols >

< Note: Notice that we used the same IP address on both cards. We will now see the
automatically-generated config definition. >
hostname adacfilter
line vty 0 4
password adacvt
no snmp-server
!
ip routing
!
media-type 100BaseX
full-duplex
ip address 144.32.96.56 255.255.240.0
!
media-type 100BaseX
full-duplex
ip address 144.32.96.56 255.255.240.0
!
end
< Note: Now we will tell it to save to nvram and reboot >
144.32.96.0 overlaps with FastEthernet0/0 < This is an OK Message >


changed state to up
changed state to up
00:02:11: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to
administratively down
changed state to down
<enter>
adacfilter>
adacfilter>enable
Password: adacsu
adacfilter#
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.56 255.255.240.0
full-duplex
!
no ip address
shutdown
full-duplex
< Note: Notice that the router thinks we entered an illegal config by having the same IP
address on both cards, so it rejected it for the second card and orders a shutdown for that
interface (we will fix that up in just a bit) >
!
ip classless
no ip http server
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Now we’ll go back in and redefine the same IP address and setup a bridge group >
adacfilter(config)#no ip routing
adacfilter(config)#no service config
adacfilter(config)#line con 0
adacfilter(config)#line aux 0
adacfilter(config)#line vty 0 4
adacfilter(config)#bridge 1 protocol ieee
adacfilter(config-if)#ip address 144.32.96.56 255.255.240.0
adacfilter#
<enter>
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
shutdown
full-duplex
bridge-group 1
!
ip classless
no ip http server
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Now we’ll set up the access lists for each card and tie them to the correct interfaces.
Remember the 1111 list is for Pegasys devices and is tied to the 0/1 output interface, which
uplinks to the Philips/ADAC network switch or hub, and the 1110 list contains Hospital devices
and are tied to 0/0 output interface, which uplinks to the hospital network switch or hub. We
will also undo the shutdown of the 0/1 interface. >
< REMEMBER: when defining the 1110 list that the units that live on the far side of that
router will be covered in each permit statement with the same Ethernet MAC address of the
interface on our side of that router, but coupled with their individual unique IP addresses. The
units that live in the hospital subnet on our side of the that router will have both their unique
Ethernet MAC address and IP address in their permit statements. >
<IMPORTANT: Each of these access-list commands are one long line and actually wrap-
around before you have to hit “Return” >
Note: The IP addresses will need to be converted to hexadecimal notation, i.e.,

144.112.96.42 = 0x9070602A. See Chapter 2 on using the IP Subnet
Calculator for easily doing the conversion.
To further clarify the “access-list” commands, please review the following: (see also Appendix E)
… The line
access-list 1110 permit 00c0.4f01.e0d2 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1A 4 eq 0x9020601A
says make an entry in access-list 1110 that will allow packets through (from a target in our hospital subnet)
with a source Ethernet MAC address 00c0.4f01.e0d2 without masking any of those address bits
(0000.0000.0000). The destination Ethernet MAC address can be of any value (special “wildcard”
construct 0000.0000.0000 ffff.ffff.ffff). Finally look at byte-offset 1A (hexadecimal for 26)
and compare 4 bytes to see if it is equal to the hexadecimal equivalent of the source IP address that
corresponds to the source Ethernet MAC address. This handles regular IP packets from units within our
hospital subnet. This is part of a pair of entries for each allowed target.
… The line
ffff.ffff.ffff 0x1C 4 eq 0x9020601A
says make an entry in access-list 1110 that will allow packets through (from a target in our hospital subnet)
with a source Ethernet MAC address 00c0.4f01.e0d2 without masking any of those address bits
construct 0000.0000.0000 ffff.ffff.ffff). Finally look at byte-offset 1C (hexadecimal for 28)
corresponds to the source Ethernet MAC address. This handles ARP request packets from units within our
hospital subnet. This is part of a pair of entries for each allowed target.
… The line
access-list 1110 permit 0009.437f.0d20 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1A 4 eq 0x902070BC
says make an entry in access-list 1110 that will allow packets through with a source Ethernet MAC address
0009.437f.0d20 (encapsulating router) without masking any of those address bits (0000.0000.0000).
The destination Ethernet MAC address can be of any value (special “wildcard” construct 0000.0000.0000
ffff.ffff.ffff). Finally look at byte-offset 1A (hexadecimal for 26) and compare 4 bytes to see if it is
equal to the hexadecimal equivalent of the source IP address that corresponds to the remote unit. This handles
regular IP packets from units beyond the hospital router (or from the router itself). There should be an entry
for each target beyond the router and one for each of the router’s interfaces.
… The line
access-list 1110 permit 0009.437f.0d20 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x26 4 eq 0x90206036
says make an entry in access-list 1110 that will allow packets through with a source Ethernet MAC address
0009.437f.0d20 (encapsulating router) without masking any of those address bits (0000.0000.0000).
The destination Ethernet MAC address can be of any value (special “wildcard” construct 0000.0000.0000
ffff.ffff.ffff). Finally, look at byte-offset 26 (hexadecimal for 38) and compare 4 bytes to see if it is
equal to the hexadecimal equivalent of the destination IP address that corresponds to the unit for which they
need to know its Ethernet MAC address. This handles ARP request packets from units beyond the filter.
There should be an entry for each Pegasys (or allowed target) within our filtered subnet.
… The line
access-list 1111 permit 0800.2092.d4c5 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1A 4 eq 0x9020603C
says make an entry in access-list 1111 that will allow packets through (typically from a Pegasys) with a source
Ethernet MAC address 0800.2092.d4c5 without masking any of those address bits
construct 0000.0000.0000 ffff.ffff.ffff). The destination Ethernet MAC address can be of any
value. Finally look at byte-offset 1A (hexadecimal for 26) and compare 4 bytes to see if it is equal to the
hexadecimal equivalent of the source IP address that corresponds to the source Ethernet MAC address. This
handles regular IP packets from units within our subnet. This is part of a pair of entries for each Pegasys (or
allowed target).
… The line
ffff.ffff.ffff 0x1C 4 eq 0x9020603C
says make an entry in access-list 1111 that will allow packets through (typically from a Pegasys) with a source
Ethernet MAC address 0800.2092.d4c5 and without masking any of those address bits
construct 0000.0000.0000 ffff.ffff.ffff). Finally look at byte-offset 1C (hexadecimal for 28)
corresponds to the source Ethernet MAC address. This handles ARP request packets from units within our
subnet. This is part of a pair of entries for each Pegasys (or allowed target).
For more information you can consult the online documentation at http://www.cisco.com/
adacfilter(config)#access-list 1110 permit 00c0.4f01.e0d2 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x9020601A
adacfilter(config)#access-list 1110 permit 00c0.4f01.e0d2 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1C 4 eq 0x9020601A
adacfilter(config)#access-list 1110 permit 00c0.4f01.ded5 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x9020602C
adacfilter(config)#access-list 1110 permit 00c0.4f01.ded5 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1C 4 eq 0x9020602C
adacfilter(config)#access-list 1110 permit 0009.43f7.0d20 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x902070BC
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x902070C1
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x90206001
0000.0000.0000 ffff.ffff.ffff 0x26 4 eq 0x9020603C
0000.0000.0000 ffff.ffff.ffff 0x26 4 eq 0x90206046
adacfilter(config)#access-list 1111 permit 0800.2092.d4c5 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x9020603C
adacfilter(config)#access-list 1111 permit 0800.2092.d4c5 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1C 4 eq 0x9020603C
adacfilter(config)#access-list 1111 permit 0800.2092.a72e 0000.0000.0000
adacfilter(config)#access-list 1111 permit 0800.2092.a72e 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1C 4 eq 0x90206046
adacfilter(config-if)# bridge-group 1 spanning-disabled
adacfilter(config-if)# bridge-group 1 input-pattern-list 1110
adacfilter(config-if)# bridge-group 1 spanning-disabled
adacfilter(config-if)# bridge-group 1 input-pattern-list 1111
adacfilter(config-if)#no shutdown
adacfilter(config-if)#
changed state to up
adacfilter#
<enter>
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
bridge-group 1 spanning-disabled
bridge-group 1 input-pattern-list 1110
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
full-duplex
bridge-group 1
!
ip classless
no ip http server
!
access-list 1110 permit 00c0.4f01.ded5 0000.0000.0000 0000.0000.0000
access-list 1110 permit 0009.43f7.0d20 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1A 4 eq 0x902070C1
ffff.ffff.ffff 0x1A 4 eq 0x90206001
ffff.ffff.ffff 0x26 4 eq 0x9020603C
access-list 1111 permit 0800.2092.a72e 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1C 4 eq 0x90206046
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
< Note: Now we will commit our config and reboot the router >
adacfilter#reload


#################################################################################
#################################################################################
#################################################################################
#################################################################################
############################################################################ [OK]

cisco Systems, Inc.


Bridging software.

changed state to up
changed state to up
< Note: Now we review our config to confirm it came back up correctly >
<enter>
adacfilter>
adacfilter>enable
Password: adacsu
adacfilter#sho run
!
version 12.0
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
no ip mroute-cache
full-duplex
bridge-group 1
bridge-group 1 output-pattern-list 1110
!
ip address 144.32.96.56 255.255.240.0
no ip route-cache
no ip mroute-cache
full-duplex
bridge-group 1
bridge-group 1 output-pattern-list 1111
!
ip classless
no ip http server
!
ffff.ffff.ffff 0x1A 4 eq 0x902070C1
ffff.ffff.ffff 0x26 4 eq 0x9020603C
ffff.ffff.ffff 0x1C 4 eq 0x90206046
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#
< Note: Done. Now you can plug it into the correct hubs or switches and do some ping tests. >
< Create local hostname entries for the filtering-bridge and any router interfaces. >
On Pegasys network master, become superuser (su -) edit the file /etc/hosts to add the IP
address and hostname for the filtering-bridge interface. You also should put in any “internal” and
“external” IP addresses of remote routers to help document the topology and to make it easier when
you do ping tests. EXAMPLE: from above configuration
144.32.96.56 adacfilter # address of our filtering-bridge

144.32.96.1 hosprtrint # near (internal) side of hospital router
144.32.31.254 hosprtrext # far (external) side of hospital router
cd /var/yp
make
§ the Pegasys network’s filtering-bridge interface.

Note: If you can ping the filtering-bridge yet cannot ping a hospital-network device, that
device might be beyond the local subnet we are connected to. We may need to get more
details about the Ethernet MAC address of an encapsulating router which brings the
target’s packets to our local subnet. The IT group is the best place to start to investigate
these details.
the Philips/ADAC side of the filtering-bridge. Then you can get in to enable mode to examine the
status of the router, or tweak some aspects of the configuration. Do not change IP addresses during a
telnet session or you will lose your connection. Example of telnetting in:
telnet adacfilter
adacfilter> enable
adacfilter#
session into one of the interfaces, but to be completely safe it is best to use the console port to
adjust the configuration. To add an entry to an existing access list and commit the changes, be
sure you use the correct list number (1111 for Pegasys devices which will speak outbound
through the hospital interface and 1110 for hospital devices which will speak outbound through
the Pegasys side interface) >

Password: adacvt
<enter>
adacfilter>en
Password: adacsu
adacfileter#conf term
adacfilter(config)#access-list 1110 permit 000C.011b.2dca 0000.0000.0000
0000.0000.0000 ffff.ffff.ffff 0x1A 4 eq 0x9020703A
adacfilter#
< enter >
adacfilter#
Important: To clean out a mistaken, obsolete or unwanted entry in an access list you
have to delete the whole access-list and re-enter all elements. Unfortunately this is a
limitation of the Cisco command line environment for which we have no control.

Password: adacvt
<enter>
adacfilter>en
Password: adacsu
adacfilter#
< follow the access-list creation steps shown above in this document >
< telnet in to update the clock to current time UTC/GMT. Remember to adjust to GMT from
your timezone. The device ONLY displays GMT so be sure you get the conversion correct. Do
this once you have the unit installed, connected and powered on. >

Password: adacvt
<enter>
adacfilter>en
Password: adacsu
12:24:04.147 UTC Mon Jun 11 2001
Using rcp and vi to make editing access lists easier
One sad fact is that command-line editing of access-lists in the router can be tedious. If there
are entries that are no longer needed then you cannot easily just delete a line. You have to delete the
whole access-list and retype it in. If the access lists are small this is not too much of a problem but if
they are large it can be very cumbersome to have to erase them and type them in again just to make
corrections. Corrections can be made a bit easier by copying the nvram image from the router to a
file in the Pegasys home directory via an rcp command. Then we can edit the text file with vi and
make changes easily. Then we will rcp the file back to the startup config, refresh the running config
and then reload and examine to be sure everything has been applied correctly by comparing the
running and startup configurations.
Note: You should NEVER change IP addresses of the router interfaces while logged in
via a telnet session. You will get “cut off” mid-configuration. Use a console connection
instead.

Trying 10.1.1.91...
Connected to 10.1.1.91.
User Access Verification
Password: adacvt
adacfilter>en
Password: adacsu
adacfilter#
<The access-lists will have been setup the first time from the command-line per the examples
shown in the previous sections. First we will compare the running and startup configurations
to make sure they are in sync.>
adacfilter#show running
Current configuration : 2110 bytes

!
version 12.2
!
hostname adacfilter
!
enable secret 5 $1$F9e7$JrfhIVDaCZHFY.2NtgNHV/
!
ip subnet-zero
no ip routing
!
!
!
!
!
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip classless
ip http server
ip pim bidir-enable
!
access-list 1110 permit 0010.a4d1.3805 0000.0000.0000 0000.0000.0000
ffff.ffff.ffff 0x1A 4 eq 0xA010163
ffff.ffff.ffff 0x1C 4 eq 0xA010163
ffff.ffff.ffff 0x1A 4 eq 0xA01015C
ffff.ffff.ffff 0x1A 4 eq 0xA01341D
ffff.ffff.ffff 0x26 4 eq 0xA010111
access-list 1111 permit 0800.20f5.8605 0000.0000.0000 0000.0000.0000
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#show startup
Using 2132 out of 29688 bytes
!
version 12.2
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
!
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip classless
ip http server
ip pim bidir-enable
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#
<Now we will use rcp to place a copy of the nvram startup image into the home directory of the
pegasys user on a Pegasys. The construct uses the following remote path and filename syntax:
rcp://username@IP_address/filename to tell rcp to place filename in the home directory of the
username user on the machine with IP_address.>
adacfilter#
adacfilter#copy startup rcp://pegasys@10.1.1.17/adfiltcfg
Address or name of remote host [10.1.1.17]? <enter>
Destination username [pegasys]? <enter>
Destination filename [adfiltcfg]? <enter>
!
2132 bytes copied in 0.608 secs
adacfilter#
<Now, open another UNIX window on the Pegasys, cd to the pegasys user home directory
(/usr/adac/pegasys), and use vi to change the file (adfiltcfg in our example) with access list
entries.
In this example we changed the ending of the hexadecimal IP address from 62 to 64 for the 3rd
and 4th lines on the 1110 list>
<Now, go back to the original UNIX window with the telnet login so we can clear the nvram
startup, use rcp to copy in the new edited version and sync the start and running access-lists>
adacfilter#erase startup
Erasing the nvram filesystem will remove all files! Continue? [confirm] <enter>
[OK]
adacfilter#
adacfilter#copy rcp://pegasys@10.1.1.17/adfiltcfg startup
![OK]
2132 bytes copied in 27.964 secs (78 bytes/sec)
adacfilter#
adacfilter#
adacfilter#copy startup running
Destination filename [running-config]? <enter>
2132 bytes copied in 0.936 secs
adacfilter#
adacfilter#reload
System configuration has been modified. Save? [yes/no]: yes

[OK]
Connection closed by foreign host.
PEGASYS-adac>
<Now wait for a couple minutes for the router to reload from nvram and get to the point where
we can telnet back in and compare the running and startup configurations to see if our changes
have been applied correctly>
Trying 10.1.1.91...
Password: adacvt
adacfilter>en
Password: adacsu
adacfilter#show running
Current configuration : 2132 bytes

!
version 12.2
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
!
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip classless
ip http server
ip pim bidir-enable
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#show startup
Using 2110 out of 29688 bytes
!
version 12.2
!
hostname adacfilter
!
!
ip subnet-zero
no ip routing
!
!
!
!
!
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip address 10.1.1.91 255.255.252.0
no ip route-cache
no ip mroute-cache
speed auto
full-duplex
bridge-group 1
!
ip classless
ip http server
ip pim bidir-enable
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacfilter#
adacfilter#exit
PEGASYS-adac>
Broadcast Traffic and its effect on CPU performance
Illustrated below is a generic “Network Receive” flowchart for TCP/IP using CSMA/CD
(Carrier Sense Multiple Access/Collision Detection). The purpose here is to demonstrate how
excessive background traffic (especially broadcasts) can have a negative impact on CPU
performance. The more broadcasts are “seen” on the wire, the more the CPU but be interrupted.
Network nodes can transmit any time but only one can hold the wire to put on its info. If
there are simultaneous transmissions, a collision occurs, nodes detect this and send JAM signal
telling all nodes to “back off” and wait random unique times before trying again. Upon successful
transmission, all nodes see packet and use the following process:
Network Interface
Deliver data
Listen to
to correct
Network Wire
TCP Port (Process)
Detect IP Packet No INTERRUPT CPU

Preamble?
Yes Yes
Read Destination Did the

MAC Address Discard No
Integrity
Data Check Pass?
Broadcast
Address?
No Perform Integrity
Check
My No Ignore
Yes
Address? Packet
Yes
Yes
Read Dataframe Reached

Contents End Of
Frame?
No
Installing a 2nd Ethernet Card (Software & Hardware)
You would typically use and configure a 2nd Ethernet Card (see part numbers in the different
instruction sections) when a site has a very limited number of IP addresses to offer. Often they
cannot afford to provide IP addresses for all of the components of our Philips/ADAC cluster.
Sometimes we have to use these cards when the site’s IT Group cannot provide a Switched VLAN
and will not allow for a router to be used.
The important thing to remember is that only the machine with a 2nd Ethernet Card will be
able to talk to the other network, which is sometimes a desired configuration constraint if they want
to restrict where the data is transferred from and who is transferring it. Please see other descriptive
aspects about 2nd Ethernet Cards in the previous chapter. See Figure 3.5 in the previous chapter for
an example of how this type of router setup would fit into typical Philips/ADAC configurations.
Keep in mind you will need to create a default router entry in an /etc/defaultrouter
file. The different instruction sets mention creating this but you should consult the notes and
guidelines at the end of this chapter to understand exactly how that file should be configured.
Furthermore, the device name for the card you install varies depending on the product line. Refer to
the following table to determine the device name for your system:
PegX PegX
Interface Type Blade Ultra 10/60 Ultra 1
5/10/20 2/5/10/20
10/100 Mbit PCI hme0 hme1
10/100 Mbit SBUS hme1 hme0
10 Mbit SBUS le1
Since the validation and approval of the Ultra 10/60 (PCI) 2nd Ethernet Card Field Service Kit
(2153-3304), only this kit is authorized for new installations of 2nd Ethernet cards going forward. We
have, however, included the procedures for all card types to allow for maintenance of existing
(previously installed) cards in the field. This may be required for sites where an existing card has to
be replaced or in the event of a hard drive cash and recovery.
Choose from one of the following four different procedures for installing a 2nd Ethernet Card
for your particular environment (be sure to verify that you have the correct part number of the card
you received):
• 2nd Ethernet 10 Mbit card on a Pegasys-X 2, 5, 10, or 20 (Reference only)

• 2nd Ethernet 10/100 Mbit card on a Pegasys-X 5, 10, or 20 (Reference only)
• 2nd Ethernet 10/100 Mbit card on an Ultra 1 (Reference only)
• 2nd Ethernet 10/100 Mbit card on an Ultra 10 or Ultra 60 (Approved)
Important: The 2nd Ethernet Card procedure for the Blade is very similar to that of the PCI
Card for the Ultra10 and Ultra60, except that for the Blade it is configured to be hme0. The
interface card is slot specific - contact technical support for more information.
2ND ETHERNET 10 MBIT PEGX 2, 5, 10, OR 20 QUICK GUIDE - 09/21/2000
This is for installing the Sun X1053A SBUS 10 MB card on a PegasysX 2, 5, 10, or 20
(Note: ADAC 4x4 partnumber for this card is 5200-3310) [ Boot PROM Rev. 2.0 or greater]
It is assumed that you have obtained the following information from the IT Group at the facility:
1) IP address for the new card,
2) Netmask of network we will be joining,
3) IP address of defaultrouter or gateway device on subnet we will be joining,
4) (optionally) sites desired hostname for the card’s new IP address.
Be sure you have an available SBUS slot in which to place the card.
Don’t put the card in the machine yet, do the software configuration first.
Log in as root or become superuser in a UNIX-Window “su -” (on machine that will get the card).
Use the VI editor to create and edit the following files.
The standard interface on the motherboard is le0, the new interface card will be le1 (that’s ellie-one)
Create new file: /etc/hostname.le1

Enter Hostname of 2nd card ( example: pegcard1 )
Create new file: /etc/defaultrouter

Enter only IP of Router/Gateway on subnet you’ll join ( example: 172.16.32.1)
Edit existing file: /etc/hosts

Add the IP and Hostname of 2nd E-net ( example: 171.16.32.63 pegcard1)
Edit existing file: /etc/networks

Enter new IP and “network name”
( one octet for class A , two octets for class B and three octets for class C )
( example: hosp-ether 172.16 hospether )
OPTIONALLY: if site uses non-default subnet mask.

Edit existing file: /etc/netmasks -Enter new “network root” and subnet mask.
( example: 172.16 255.255.252.0 )
You need not make entries in the /etc/netmasks file if the site uses the appropriate class
defaults:
Class A (1.x.x.x – 126.x.x.x) 255.0.0.0
Class B (128.x.xx – 191.x.x.x) 255.255.0.0
Class C (192.x.x.x – 223.x.x.x) 255.255.255.0
If this is being done on a MASTER or STANDALONE skip this paragraph and go to next page.
If this is being done on a CLIENT, go to the MASTER and repeat the above steps,
(EXCEPT for the /etc/hostname.le1 and /etc/defaultrouter files, DO NOT create
that file on the MASTER since it will not have the card in it).
On Master (once all has been edited, still as root or su –):

Type: cd /var/yp
Type: make
Back on the machine that will get the 2nd Ethernet card (still as superuser)
Type: halt
Wait for the machine to come to the boot (ok) prompt and power it off.
Install the 2nd Ethernet card, hook up the 10bT cable and boot up.
Watch the bootup messages you should see that the card is recognized.
Once up, you can verify the configuration by doing the following in a UNIX-Window:
Type: ifconfig –a
( check for info on le1, you should see Inet for IP address, the netmask in Hexadecimal, and the
broadcast address. )
Type: netstat –rn

( you should see at least a line of data for le1 and also a line for the defaultrouter containing the IP
address you provided )
Try pinging IP addresses of units on the network the 2nd Ethernet card attached to.
Examine the traffic seen on each interface.

First the traffic on the hospital or clinic network:
Type: etherfind –i le1 ip

“Ctrl-c” to quit
Next, the traffic on the local Philips/ADAC network:

2ND ETHERNET 10/100 MBIT PEGX 5, 10, OR 20 QUICK GUIDE - 09/21/2000
This is for installing the Sun X1059A SBUS 10/100 MB card on a PegasysX 5, 10, or 20 running Peg
3.31 or better. (Note: ADAC 4x4 partnumber for this card is 5200-3224)
4) (optionally) sites desired hostname for the card’s new IP address
The standard interface on the motherboard is le0, the new interface card will be hme0
Create new file: /etc/hostname.hme0





( example: 172.16 255.255.252.0 )
defaults:
Class A (1.x.x.x – 126.x.x.x) 255.0.0.0
Class B (128.x.xx – 191.x.x.x) 255.255.0.0
Class C (192.x.x.x – 223.x.x.x) 255.255.255.0
(EXCEPT for the /etc/hostname.hme0 and /etc/defaultrouter files, DO NOT create
On Master (once all has been edited, still as root or su -):
Type: cd /var/yp
Type: make
Type: halt
Type: ifconfig –a
( check for info on hme0, you should see Inet for IP address, the netmask in Hexadecimal, and the
broadcast address. Note: Some very old cards may show up as be0 and the above directions would
use be0 instead of hme0 ie. If old card is “be0” you will have to create /etc/hostname.be0 not hme0.
The be0 cards surfaced during the early version of the Sparc20 based MCD units. )
Type: netstat –rn

( you should see at least a line of data for hme0 and also a line for the defaultrouter containing the IP

Type: etherfind –i hme0 ip


2ND ETHERNET 10/100 MBIT ULTRA 1 QUICK GUIDE - 09/21/2000
This is for installing the Sun X1059A SBUS 10/100 MB card on an Ultra 1
(Note: ADAC 4x4 partnumber for this card is 5200-3224)
The standard interface on the motherboard is hme0, the new interface card will be hme1





( example: 172.16 255.255.252.0 )
defaults:
Class A (1.x.x.x – 126.x.x.x) 255.0.0.0
Class B (128.x.xx – 191.x.x.x) 255.255.0.0
Class C (192.x.x.x – 223.x.x.x) 255.255.255.0
Type: cd /var/yp
Type: make
Type: halt
Note: Do a <Stop-A> when the first boot text appears and at the ok prompt, Type: boot -r
This is necessary on machines running Solaris so they can recognize new devices.
Type: ifconfig –a
broadcast address )
Type: netstat –rn

( you should see at least a line of data for hme1 and also a line for the defaultrouter containing the IP

Type: snoop –d hme1


2ND ETHERNET 10/100 MBIT ULTRA 10, 60 QUICK GUIDE - 09/21/2000
This is for installing the Sun X1033A PCI 10/100 MB card on an Ultra 10 or Ultra 60
(Note: ADAC 4x4 partnumber for this card is 5200-3541. Entire kit w/ instructions is 2153-3304)
Be sure you have an available PCI slot in which to place the card.
The standard interface on the motherboard is hme0, the new interface card will be hme1





( example: 172.16 255.255.252.0 )
defaults:
Class A (1.x.x.x – 126.x.x.x) 255.0.0.0
Class B (128.x.xx – 191.x.x.x) 255.255.0.0
Class C (192.x.x.x – 223.x.x.x) 255.255.255.0
Type: cd /var/yp
Type: make
Type: halt
Note: Do a <Stop-A> when the first boot text appears and at the ok prompt, Type: boot -r
This is necessary on machines running Solaris so they can recognize new devices.
Type: ifconfig –a
broadcast address )
Type: netstat –rn

( you should see a line of data for hme1 and also a line for the defaultrouter containing the IP address
you provided )



Network Speeds, Duplex, MTU, Ports and Auto-Negotiation
• Network speeds we deal with on the LAN are 10 Mbps (Megabits per second) and 100 Mbps
(Gigabit+ currently are increasingly popular for backbones)
• Effective throughput usually realizes no more than 60% of theoretical limit. Keep this in
mind when measuring transfer rates.
• 10base2 (Thinnet) is limited to 10 Mbps (as are our Pre-Skylight detectors and the Milan 4-
port hub and other devices… Forte/Atlas 10/100 switch upgrade helps by reducing backbone
traffic on the wire)
• 100 Mbps requires Cat5 cabling or better and 100Mbps or 10/100Mbps capable equipment.
• Shadow requires 100Mbit connection “all the way through” for proper performance.
• Full-Duplex is simultaneous traffic in both directions (like a phone conversation) while Half-
Duplex waits for one direction to finish before the other can send (like a ham radio
conversation … over)
• Some devices cannot auto-negotiate the speed and duplex settings well (or at all) and require
us to “tie down” our interface. The unmanaged Allied Telesyn switches we use, settle on half
duplex when they run into difficulties with the auto-negotiation, while our Ultra interfaces try
to stay at full duplex. To combat this we can force to 100Mbit, Half-duplex as shown below.
Other, more intelligent switches used by different IT Groups have the ability to program the
speed and duplex settings for the ports, so with these we stand a chance of improving
throughput by trying to force the Ultras to 100Mbit, Full-duplex instead (just swap the 1 and 0
on the hdx and fdx settings).
• Our Pegasys (like most Ethernet interfaces) is configured to have a MTU (Maximum
Transmission Unit) of 1500 bytes (you see this when you do an “ifconfig -a”). This says the
information part along with the destination MAC address, source MAC address and payload
length value, will not exceed 1514 bytes which is the largest any Ethernet packet can be (see
Packet Format in Chapter 1). In some rare cases, some VLAN configurations require
additional overhead in each packet so we need to reduce our MTU setting to accommodate
those extra bytes required by the site’s infrastructure. This allows us to successfully transmit
packets (for Peg2Peg Transfer, DICOM, etc.) to other targets outside of our VLAN without
loosing any information. The steps to reduce the MTU value are shown below.
• Slow commit times for Atlas acquisition data can be adversely affected by mismatches in
interface speed between the Atlas and Ultra Ethernet interfaces. In addition to checking the
Speed and Duplex as shown in the section below, you can corroborate the need to “tie down”
the settings on the interface by measuring for packet errors during data transmissions. You
can measure this on the Database Host Ultra during a commit of the study, or you can look at
the accumulation of the study on the Ultra-AXi. In a UNIX Window, as Superuser, you can
use the “netstat –i 5” command to measure for packet errors every 5 seconds. Always start
the measurement in advance of the data event and ignore the first line of data as that is
cumulative counts up until you first start the command. Then as the data is transferred if you
see errors show up under the “errs” column you know there is a problem (usually “late
collisions” from a duplex mismatch). Here is an example of an error condition:
SUPERUSER@adac2:#[1] netstat -i 5
input hme0 output input (Total) output
packets errs packets errs colls packets errs packets errs colls
2518 262 1360 0 0 63611 262 4588 0 0
2 0 1 0 0 70 0 1 0 0
245 28 112 0 0 311 28 112 0 0
547 67 354 0 0 628 67 356 0 0
237 25 148 0 0 301 25 148 0 0
2 0 2 0 0 81 0 2 0 0
2 0 2 0 0 67 0 2 0 0
2 0 2 0 0 55 0 2 0 0
<ctrl-C>
SUPERUSER@adac2:#[2]
FORCING 100MBIT, HALF-DUPLEX ON SOLARIS
Create new file /etc/rc2.d/S68hmeconf (as “su”) containing this (if typing manually, you
MUST include first line containing #!/bin/sh, but can exclude the comments after that line):
#<--BEGIN INCLUDED SCRIPT - DO NOT USE THIS LINE -->
#!/bin/sh
# S68hmeconf
#
# Forces network interface hme0 to desired speed and duplex
# with autonegotiation turned off
#
# This works equally well on an Ultra-AX or Ultra AXi in an Atlas
# just as it does on an Ultra1, Ultra60 or Ultra10 Pegasys
# as they all are running Solaris 2.5.1
# Note: this will not work on an older Pegasys running SunOS 4.1.3
#
# The default setting of this template file is 100Mbit Half Duplex
# To make it something different, simply change the 0 to a 1 after
# the desired speed/duplex attribute. Be sure other adv_* values are set to 0
#
# If you need to have this done to an interface other than hme0
# just change the value in the instance setting line.
# For example on an Ultra60 with a 2nd Ethernet Card that uplinks
# to the hospital network switch that has problems with autonegotiation
# you would change instance 0 to instance 1 since that card would be hme1
# For Blade motherboard, use /dev/eri instance 0 (since it would be eri0)
# Note: PegBlade 2nd Ethernet card is device hme0.
#
# To use this template on an Ultra
# - be sure it is in Unix format (use dos2unix if needed to
# convert ctrl-M)
# - copy it into /etc/rc2.d
# - chown root /etc/rc2.d/S68hmeconf
# - chgrp sys /etc/rc2.d/S68hmeconf
# - chmod 744 /etc/rc2.d/S68hmeconf
# - reboot your machine
#
# ADAC 2001
case "$1" in
'start')
/usr/sbin/ndd -set /dev/hme instance 0
/usr/sbin/ndd -set /dev/hme adv_10fdx_cap 0
/usr/sbin/ndd -set /dev/hme adv_10hdx_cap 0
/usr/sbin/ndd -set /dev/hme adv_100T4_cap 0
/usr/sbin/ndd -set /dev/hme adv_100fdx_cap 0
/usr/sbin/ndd -set /dev/hme adv_100hdx_cap 1
/usr/sbin/ndd -set /dev/hme adv_autoneg_cap 0 # must be last
;;
'stop')
;;
esac
#<--END INCLUDED SCRIPT - DO NOT USE THIS LINE -->
• Then, set owner and permissions (as superuser “su” or while logged in as root:
chown root /etc/rc2.d/S68hmeconf

chgrp sys /etc/rc2.d/S68hmeconf
chmod 744 /etc/rc2.d/S68hmeconf
• Reboot your machine and then reseat Cat5 RJ-45 connection.
Note: Do not try to defeat the forced settings by changing “adv_autoneg_cap” to 1 and all other
values in script to zero. This can cause the network interface to shut down. To return to standard
(hardware) auto negotiation, instead do the following to disable the script without deleting it (as
superuser “su”):
cd /etc/rc2.d
mv S68hmeconf X68hmeconf
< Reboot your machine and then reseat Cat5 RJ-45 connection >
FORCING 100MBIT, FULL-DUPLEX ON 4.1.3U1

• Cannot be done on 4.1.3u1.
• Default is for the 5200-3224 10/100 card to come up in half-duplex mode and auto-negotiate
speed from there.
• The installation manual that comes from Sun shows an alternate way to do it for Solaris, but
nothing for 4.1.X; besides the Openboot Prom level must be at least 2.9 (SS5/10/20 models
probably never got up this high and there might be additional kernel limitations)
• If your card cannot latch up correctly you may need to revert to using 5200-3101 which is a
10Mbit only card.
HOW TO CHECK SPEED AND DUPLEX

• You can check the speed and duplex settings for an interface on a PegUltra Solaris box (or a
4.1.3u1 box with an hme interface) by unplugging the 10bT cable from the RJ45 port on the
back, wait a second or two, reattach the cable and check the text in the console window.
(Note: You must reseat the cable right after changing the attributes and rebooting) If it
doesn’t say anything about duplex then assume half-duplex. (Not recommended to check this
way during clinical use of a busy network)
• Another less disruptive way to check on the speed and duplex is to use these commands in a
UNIX Window as Superuser on an Ultra Solaris 2.x OS:
/usr/sbin/ndd –set /dev/hme instance 0
(to check the values for a 2nd Ethernet Card on Ultra 60 or 10 use instance 1 instead)
/usr/sbin/ndd /dev/hme link_speed
(where a return value of 0 = 10Mbit and 1=100Mbit)
/usr/sbin/ndd /dev/hme link_mode
(where a return value of 0 = half-duplex and 1=full-duplex)
• On most switches and hubs there are indicator lights for the speed at least, and for the duplex
mode on some. Also managed switches and hubs (ours are unmanaged) have a way to login
to them to examine (and set) the port attributes.
REDUCING MTU VALUE

• We can reduce the MTU (Maximum Transmission Unit) value by adding an adjustment line
to one of the boot files that starts up the Ethernet interfaces. The new MTU value is
something that should be provided by the site IT group and will always be less than 1500
bytes (the standard default). (Not recommended to make these changes during clinical use
of a busy network)
Open a UNIX window

Become superuser (su -)
cd /etc/rc2.d
cp -p S72inetsvc X72inetsvc.orig
cat –n S72inetsvc
This will list out the file with the line numbers
Look for the following line:
/usr/sbin/ifconfig –au netmask + broadcast +
Note the line number for that entry
vi +nn S72inetsvc (where nn is the line number noted above)

This will open the vi editor with the cursor already on that line.
Type o (a little ohh) to open a new line below where the cursor is, and add the following lines of
information:
# Approved Field Modification (AFM Net-48)

/usr/sbin/ifconfig hme0 mtu 1400 (your value may be different)
Once added, press the ESC key and then type :wq! To write the changes and quit the edit.
Reboot the Pegasys for the change to be implemented.
Creating a Defaultrouter File
A default router (also sometimes referred to as a gateway) is a device that will help forward
packets addressed to systems outside the local subnet (governed by the netmask value applied to the
IP address range you live in).
Note: The default router IP address MUST be in same subnet that the Pegasys units live
in (or else we will get a “network unreachable” error).
Here is how the default router comes into play when an assertion is made to a device outside our IP
subnet (like a remote DICOM printer):
BASIC ETHERNET PACKET ROUTING DIAGRAM

Basic Ethernet Packet Routing
Ethernet Packet
to be sent out
Destination IP
YES Choose interface
address in
local subnet?
on that subnet
NO
static route or Do we have

YES YES Choose that
defaultrouter interface for
interface
defined? that subnet?
NO NO
Is there a local
NO Error: Network is Transmit
interface in that
unreachable Packet
subnet (2nd NIC)?
YES
Choose that Transmit

interface Packet
DONE
DEFAULTROUTER GUIDELINES
In custom networks, this file should be created on all Pegasys workstations and Atlas AX(i)
systems. The other hospital network devices (DICOM printer, PACS system, Shadow PC, etc.) are
configured for a default router or gateway by a variety of different procedures. A qualified 3rd party
service representative, local biomedical engineer, or IT/PACS administrator should edit the gateway
address on these systems. It is important that they are configured properly, otherwise they cannot
respond to us through their gateway. When you have problems reaching a remote device, you should
consider checking if the remote system has a gateway value configured.
During a Pegasys network configuration (when running the network_pegx script), you are
asked if there is a default router, as in the below example:
Is a default router entry needed for this unit?
Note: Unless you understand routing select NO. By default dynamic routing
will be functioning via in.routed and your system will be listening for
broadcasts from configured routers. Selecting yes will result in disabling
dynamic routing and only your selected static route will be used.
Is a default router entry needed for this unit [y/n: n]? y <RETURN>
If you answer yes and give the IP address, then the /etc/defaultrouter file will be
created automatically for you.
Important: Even if the correct IP address is in the default bracketed text, you must re-type
it anyway. This is due to a bug in the script that does not allow the default entry.
On an Atlas system, running setup2 and entering a gateway IP address will create the
/etc/defaultrouter file on the Ultra-AX harddrive.
If an “out of band (not in our subnet)” bootp request comes along, the bootp server will create
a log entry in /var/adm/messages. If you see these occurring throughout the file, refer to
the “Hardware Address not found…” Informational Tip for correcting this.
If you are adding a router to your subnet after the fact, you will need to create this file
manually, as per the instructions that follow.
One of the most important reasons that we define a default router is that it prevents the routing
daemon from running on the Ultra-Pegasys and Atlas Ultra-AX systems. If a Solaris machine runs
“routed”, it broadcasts its network interface as a valid route point off the subnet. This is a bad
thing if we are connected to a hospital network as we may be seen as a valid router by other PCs and
hospital equipment (shortest number of hops wins). They then think they can forward us packets to
send out of their subnet (to the Internet, for example, which of course we cannot do).
There are two scenarios to consider when trying determining what the correct value for the
default router will be:
Centralized (connectivity for entire cluster)

If the Philips/ADAC router is located between our central switch/hub and the hospital
network, then on all Pegasys and Atlas units, the defaultrouter = IP address of the interface on the
ADAC equipment’s side of the router.
If we have a Philips/ADAC central switch/hub uplinked to VLAN ports on a hospital switch
(or if all pieces of Philips/ADAC equipment are plugged into VLAN ports on a hospital switch, then
on all Pegasys and Atlas units the defaultrouter = IP address of their router or gateway that services
the subnet we live in, as defined by the hospital’s IT administration.
-OR-
Single-Point (One Pegasys only with 2nd Ethernet Card)

On each Pegasys with a 2nd Ethernet Card, the defaultrouter = IP address of the router or
gateway on hospital network
After you have determined the correct value of the IP address to use for the default router, it is
simple to manually create a "/etc/defaultrouter" file on each Pegasys or Atlas system that
will require one. The “defaultrouter” file you create must contain only one IP address, that of the
router or gateway within the local subnet. To create a defaultrouter file, open a UNIX window,
become superuser (su) and do the following steps:
1. Type: cd /etc <Return>

2. Type: vi defaultrouter
a. To enter the insert mode, type: i
b. And without hitting return, type nnn.n.nnn.nnn<esc>
(where nnn.n.nnn.nnn = defaultrouter IP address)
c. And again without hitting return, hit <esc>
3. Type: :wq! <return>
4. Type: more defaultrouter
a. (Verify that you see the assigned IP address)
5. Perform the above four steps on each Pegasys and Atlas AX(i) in the cluster that needs to be
connected to the Hospital network.
6. Finally, reboot each of the systems on which you have created this file.
Remember: If you have to reboot the master, do it first and once it is back at the login prompt, then
you MUST go reboot all the clients.
Hey, but what if site says they don’t have a defaultrouter or gateway (this usually means they
just have one big flat network)?
If a centralized filtering solution is being used (if the site says there is no gateway, just one big flat
network):
For an Ultra/Atlas (Solaris) we can create an /etc/notrouter file using the “touch” command
and reboot, as seen in example below:
SUPERUSER@jeff:#[1] touch /etc/notrouter

SUPERUSER@jeff:#[2] shutdownprep
Preparing operating system for shutdown:

========================================
Do you REALLY want to SHUT DOWN? (Y or N): y
You have decided to shutdown, do NOT poweroff until you see

">" or "ok" prompt
Setting Database mode: offline
SUCCESS: Database Off-Line
Preparing database files for shutdown:

======================================
performing logout cleanup tasks
No match
No match
No match
No match
No match
REMEMBER: do NOT poweroff until you see ">" or "ok" prompt
. . . . . .
ok boot
For a Pegasys-X system running SunOS 4.1.3_U1, we have to comment out the startup clause for
routed in the /etc/rc.local file by putting a “#” sign in column 1 on each line of that section.
(Note: this clause is found around line #136)
PEGASYS@jeff:#[1] more /etc/rc.local < Note: partial file shown >

#
# @(#)rc.local 1.116 91/05/10 SMI; from UCB 4.27 83/07/06
#
. . . < content reduced, find section below >
#
# Run routed only if we don't already have a default route installed.
#
defroute="`netstat -n -r | grep default`"
if [ -z "$defroute" ]; then
if [ -f /usr/etc/in.routed ]; then
in.routed; echo 'running routing daemon.'
fi
fi
. . . < once you find it, comment out the entire section as seen below by inserting “#” signs in
front of each line. If using the vi editor, use “i”, then “#”, then “<Esc>” >
#
# Run routed only if we don't already have a default route installed.
#
#defroute="`netstat -n -r | grep default`"
#if [ -z "$defroute" ]; then
# if [ -f /usr/etc/in.routed ]; then
# in.routed; echo 'running routing daemon.'
# fi
#fi
Now reboot the Pegasys-X for the above changes to take effect. (If this a Master Pegasys, you must
shutdown and reboot entire network in sequence)
If using a 2nd NIC card then you could use the appropriate method mentioned above or you could set
defaultrouter = IP address of 2nd NIC (although not technically correct, it does achieve the same
result).
CONFIGURING ADDITIONAL STATIC ROUTES
Sometimes you may find you have configured to a site’s default router and, as they evolve,
another router is added (which also has an interface on our subnet), to connect to equipment on a
different subnet. Let’s say that subnet contains a unit on it that we need to talk to.
We want to keep the default router in place so we can get to all the targets we have always
been able to reach. However, we need to tell the OS that if we request to talk to an IP address in a
special different subnet, we want that request to go through a router other than the one that is defined
as our default.
This is where static routing statements come in handy. The OS looks to see if static routes are
defined just before it looks to see if there is a default route definition (see Basic Ethernet Packet
Routing Diagram above). We will put in two routing statements. The first defines that a host (the IP
address of interface of the other router) can be reached by going through our interface that is attached
to the correct subnet. Since that interface is in our unit the metric value is 0. The second defines that
any units living in the remote base subnet range may be reached by going to the host we just defined.
Since that unit is on the same subnet as our interface the metric value is 1. Here is an easy method to
configure this static route by creating a new file to be used at boot time:
Open a UNIX window

Become superuser (su -)
cd /etc/rc2.d
vi S70addroute
This will open the vi editor and it should say “New File” at the bottom of the window.
Type i (a little “i”) to begin insert mode, and add the following lines of information (your addresses
and the date will vary):
#
# ADD Static Route to 10.1.52.0 Subnet MM/DD/YYYY
# example:
# route add host IP_addr_router IP_addr_our_enet 0
# route add net base_IP_addr_subnet IP_addr_router 1
#
route add host 10.1.1.92 10.1.1.17 0
route add net 10.1.52.0 10.1.1.92 1
Once added, press the ESC key and then type :wq! To write the changes and quit the edit. Then
reboot the Pegasys for the change to be implemented.
Notes: (Further clarification of “route add” statements)
ü The second IP address in the “route add host” line is the interface in our machine which
takes us to the router in question (could be the motherboard address or the 2nd Ethernet Card
address).
ü The first address in the “route add net” line is the Base Subnet Address of the subnet that is
on the other side of the router in question (remember the trailing dot zeroes).
ü "The last value in each line is the hop count, or a measure of how far away from our
computer the named interface is. A value of zero means that interface is connected to our
machine (motherboard or 2nd Ethernet). A value of one means that the interface belongs to
another box that is connected to our subnet."
Shortcut Procedure for changing IP’s, subnet, default router ONLY
Philips/ADAC Pegasys network (NIS Tar Floppy Version)

(INSTEAD of /usr/adac/pegx/scripts/load/network_pegx program)
This procedure can be used in place of the network_pegx script when reconfiguring a Pegasys
network to connect to a hospital or clinic WAN (wide area network) when changing only IP
addresses, subnet, and defaultrouter (gateway). This procedure assumes that the default (or
current) hostnames, NIS domainname and Pegasys network roles (master/slave) will not change. The
number of files requiring editing to incorporate a change of hostnames has proliferated over the years
with an increasing number of options that leverage hostnames in their configuration. Therefore, it is
recommended you rely on the network_pegx method when also modifying hostnames.
Although this document may appear to be lengthy, it contains many helpful tips and examples
throughout. It has been designed to answer any questions you might have along the way and, most
importantly, to save you a lot of time. As an example, an entire network of 6 Pegasys computers, two
Pegasys-X acquisition PC’s, 3 Atlas systems, two DICOM formatters, and two Codonics printers has
been reassigned in only four hours, including full testing! It would have taken at least twice that long
if the proper peripherals de-install, emergency-standalone, network_pegx, peripherals re-install
method were used.
Please review this entire procedure carefully before you begin ! ! !
There are a few items you MUST have prior to beginning this procedure:
• A formatted, defect-free, blank 1.44MB floppy disk. (For copying NIS maps) Also, you
should be sure that each of the clients can read a floppy image produced on the master.
Simply doing a “tar tvf …” of a floppy created with “tar cvf …” on the master will suffice.
Do not begin this procedure until all clients can read a floppy image generated on the
master (unless you’ll be using the FTP transfer method instead)!
• For each ATLAS on the network, you’ll need:
o Current version Atlas Utility Disk (Working Copy) to access CVT100 terminal
emulation.
o Current version Atlas Boot Builder for appropriate (PNP / Non-PNP) Ethernet card.
o PC-NFS license floppy.
• Field Service Laptop, complete with Ethernet interface, transceiver, and network cable(s).
• Cheat-sheet for vi editor (if needed, can be found on TAC Online Documents CD V1.1 under
path \TAC\TAC_DOCS\LATEST\NETWKDOC\NETCLS97\C_VIASST.DOC
• Service manual or instructions for editing device-specific configurations for any networked
peripherals, such as Codonics, local DICOM formatters, NUMA, DeltaManager, Helios, etc.
• If the Pegasys clients are in the same physical subnet then you can use the FTP method to
transfer NIS maps instead of the floppy method. If any of the clients reside beyond a router
then you MUST use the floppy method to update NIS maps on them.
This procedure assumes that the existing physical topology will not change. If you will be converting
to CAT5 or any other topology, you should consider completely finishing one procedure before
starting the other. Performing both procedures simultaneously might lead to a troubleshooting
nightmare!
CLIENT INSTRUCTIONS: Edit last client (adacN) to first client (adac1), then Pegasys master.
1. Open a Unix window.
2. Become superuser (Ultra: su –, adacsu PegX: su, adacsu)
3. cd /etc
If unit is a PegX then continue to step 4, otherwise perform the following check.
On an Ultra, /etc/hosts should actually be a symbolic link that points to /etc/inet/hosts
you can check this by doing an ” ls -l /etc/hosts” and you should see the
following at the end of the line:
hosts -> /etc/inet/hosts
If it does not have the arrow pointer then there are two separate hosts files. You must
reconcile the contents of /etc/hosts and /etc/inet/hosts and make sure the correct info is
in /etc/inet/hosts. Then we will fix the symbolic link in the /etc directory as follows:
rm /etc/hosts (answer y if prompted)
ln –s /etc/inet/hosts /etc/hosts
Now proceed to step 4.
4. vi hosts ( edit all old IP addresses that are changing to new IP
addresses. Clients should only have two entries: 127.0.0.1 localhost and it’s own.
Only the master of the cluster should have all the other network IP addresses in it.
Note: Often the hosts file has read-only permissions set, so after you have finished
your editing, use the following command to write changes and quit the editor:
a. :wq! ( Write, quit, override read-only permissions! )
5. If the site has defined a default router (gateway), create (edit) /etc/defaultrouter file:
a. vi defaultrouter ( if new, will state “defaultrouter” [New File] )
b. dGi ( Delete contents and enter insert mode )
c. ##.##.##.## ( type ONLY the IP address of router or gateway )
d. <ESC> ( escape from insert mode )
e. :wq! ( Write, quit, override read-only permissions! )
6. If the network number will change from the current scheme (i.e., 192.9.200.??? will become
128.55.???.???) then you must change the entry in the /etc/networks file to reflect the change.
a. Note: one octet = Class A, two octets = Class B, three octets = Class C.)
b. Class “A” example:
sun-ether 10
(Note: If you are defining a Pegasys cluster to be a 10.x.x.x network, you
must delete the existing line the file defining arpa to be a 10 network)
c. Class “B” example:
sun-ether 128.55
d. Class “C” example:
sun-ether 199.200.10
7. If the network is subnetted beyond the usual defaults, then add an entry at the end of the
/etc/netmasks file. The left column represents the base network number, the right column is the
mask, both in dotted-decimal notation. Remember, Class “A” = one octet, Class “B” = first two
octets, Class “C” = first three octets. On Ultra systems, the same rule applies, but you must fill
in the remaining octets with zeros…
a. Three Ultra netmask examples:
201.42.80.0 255.255.255.192 ( Class “C” )
128.55.0.0 255.255.252.0 ( Class “B” )
10.0.0.0 255.255.255.0 ( Class “A” )
b. Three PegX netmask examples:
201.42.80 255.255.255.192 ( Class “C” )
128.55 255.255.252.0 ( Class “B” )
10 255.255.255.0 ( Class “A” )
Note: You may see trailing dot-zero (.0) notation in the /etc/networks and /etc/netmasks files on the
Ultra systems. This is okay, as long as the appropriate number of dot-zeros are following the base
network number for that particular Class (eg. A = x.0.0.0; B = x.x.0.0; C = x.x.x.0)
8. cd /etc/install ( PegX only. Ultra does not have sys_info file )

9. vi sys_info ( change IP address = <New IP address> )
If a non-Atlas acquisition camera(s) is connected to this Pegasys stack, then

10. edit a:\nfs\hosts ( PC Floppy: edit host & pc IP addresses )
11. edit a:\nfs\network.bat
( Only for a non-default subnet mask Add a new line just after the “net start rdr” line )
net subnet 255.##.##.##
Note: You might consider making a fresh backup of this newly configured floppy.
If a non-Atlas EPIC Camera is connected to this Pegasys stack, then

12. cd /usr/local/matador/etc
13. vi bootptab
a. Change ip=<new IP address> for both heads.
b. Change sm=<new subnet mask> throughout file.
14. halt (Take system down to the OK prompt. Remember: when the network is being
rebooted, EPIC detector heads also require reboot to have their new IP addresses activated)
… Go to the next Client in the chain and perform steps 1 – 14 from above.
MASTER INSTRUCTIONS: If this is a Standalone or Master Pegasys:

15. PERFORM STEPS 1 – 14 from above.
16. At the OK prompt type:
a. boot -s ( Reboot single user mode. Note: An Ultra will prompt “INIT:
SINGLE USER MODE... or give root password for system maintenance”
to which you should type in “adacsu” for system maintenance. This gets you to
the # prompt. )
17. cd /var/yp
18. cat /etc/defaultdomain ( Determine current NIS_domainname )
and then
domainname NIS_domainname ( YP.pegasys or Custom Domainname if applicable )
19. /usr/sbin/ypinit -m ( If this is an PegX: /usr/etc/yp/ypinit -m )
Note: Ultra: answer ( <ctrl-d>, y, n, y ) to destroy existing and recreate YP maps.
Note: PegX, answer ( n, y, <ctrl-d>, y ) to destroy existing and recreate YP maps.
Be sure you say “yes” it is OK to destroy the existing maps!!! You will save yourself hours
of re-work!
20. If all Pegasys clients are within the same physical subnet then you can use the FTP method to
update NIS maps and skip to step 22. Otherwise, put a 3.5” blank floppy into the floppy drive,
then issue the following commands:
fdformat ( pre-format the floppy )
Note: Script will prompt you to insert a non-write protected floppy and press <Return> to
continue. During the process, you will see scrolling periods until complete. Then, issue the
following:
tar cvf /dev/rfd0c NIS_domainname ( YP.pegasys or Custom Domainname if
applicable )
Note: you should see 20-30 files scroll by; these are the YP maps. This is normal.
21. eject floppy ( or press eject button; write-protect disk )
22. sync; reboot
NOW BACK TO THE CLIENTS: First client ( adac1 ), then in order to last client ( adacN )
23. boot -s ( Reboot single user mode. Note: An Ultra will prompt “Press CTRL-D for
normal startup…” to which you should type in “adacsu” for system maintenance. This will
dump you to the # prompt. )
24. cd /var/yp
25. If you are using the FTP method continue to step 26; if using the floppy method then skip to
step 36.
26. At the Pegasys prompt: cd NIS_domainname
27. At the Pegasys prompt: ftp IP_address_of_master
28. At the Name prompt type: root
29. At the Password prompt type: adacsu
30. At the ftp> prompt type: binary
31. At the ftp> prompt type: cd /var/yp/NIS_domainname
32. At the ftp> prompt type: prompt
33. At the ftp> prompt type: mget *
34. At the ftp> prompt type: quit
35. >>> Skip to step 39
36. Put 3.5” floppy with New NIS maps created from master peg into the floppy drive.
37. tar xvpf /dev/rfd0 ( copies Master’s YP maps to client )
38. eject floppy ( or press eject button )
39. sync; reboot ( That’s it… you’re done with this one! )
40. Follow steps 23–39 from above on the rest of the clients. After you’ve finished and rebooted
the last client, you should login all Pegasys systems and proceed to test displays, choosing
images across the network. You should also reboot and test any PegX acquisition PC’s stations
at this time.
ATLAS SYSTEMS: If you have any Atlas system(s), you must reconfigure them as follows:
41. Shutdown Atlas stack (any order if you have more than one) and power off. Insert current
version Utility Disk (Working Copy) and power-up Atlas. You should also take this time to
locate your PC-NFS license disk for this workstation and a formatted, blank floppy.
42. cvt100 ( enter terminal emulation mode at A:\> )
43. After Atlas is booted (about 2 minutes), press <Enter> for login: prompt.
44. Login to Atlas as “root”, password “adacsu”
If this atlas is served by any client (other than a standalone master) then
a. cd /etc
b. vi hosts ( Update IP address for Master Pegasys )
45. setup2
46. [b] Modify Site/Camera Configuration ( May be [c] on Common Camera )
Update the IP address for this station’s database host.
47. [S] Save and go back
48. [a] Reconfigure Network on this Atlas
Update IP addresses and subnet mask for Atlas, NetPC, Detectors, and GantryPC.
49. [S] Save & Reboot
50. After reboot of Atlas (on a Philips/ADAC camera), power-cycle gantry to reboot the EPIC
detectors. This will force them (via bootp) to take on their new network configurations.
51. Remove Utility Disk and Acquisition ZIP disk from the stack.
52. Install current version “Boot Builder” floppy for this Atlas and reboot Acquisition PC. Using
all new IP addresses and PC-NFS license disk, create a new boot image.
Choose “Yes” to overwrite existing “station1.img” file.
53. Remove all floppies from Atlas and reboot Acquisition PC. This station is done!
54. Repeat steps 41 – 53 above for all remaining Atlas systems on this network.
When you’re done, test acquisition on all Atlas acquisition stations.
SKYLIGHT SYSTEMS: If you have any Skylight/Jetstream system(s), you must reconfigure them
as follows:
55. Using the Windows-2000 PC console, open a Hyperterm session and telnet to the Ultra-AXi.
56. Login: atlas
57. Password: atlas
58. su –
59. Password: adacsu
60. cd /etc
61. vi externalip.temp # Update IP address for Linksys external WAN port
62. vi netmasks # Update base network number and netmask on the line
with the #NETWORKID comment. The first set of numbers is the base network number
expressed in dot-zero notation (ie. Class C = #.#.#.0; Class B = #.#.0.0; Class A = #.0.0.0).
The second series of numbers is the actual netmask for that network number. Sample below:
root@192.9.200.240:1 >cd /etc
root@192.9.200.240:2 >more netmasks
192.168.1.0 255.255.255.0
192.9.200.0 255.255.255.0 #NETWORKID
63. cd /var/named
64. vi ns.camera # Update IP address on line with ;dbhostnameip
comment … for Pegasys DBHOST in same subnet as Linksys WAN port. Sample below:
root@192.9.200.240:1 >cd /var/named
root@192.9.200.240:2 >tail ns.camera
; Put the static addresses here. This should not change
;
localhost A 127.0.0.1
camera A 192.168.1.11
linksys A 192.168.1.1
;
; Put the external addresses after here.
;
adac A 192.9.200.1 ;dbhostnameip
databasehost CNAME adac
65. Reboot Skylight PC Tower.
CardioMD SYSTEMS: If you have any CardioMD system(s), you must reconfigure them as
follows from the CardioMD Windows-NT Desktop:
66. Click left on: Start -> Settings -> Control Panel
67. Double-click left on: Network icon
68. Click left on: Protocols tab
69. Click left on: TCP/IP Protocol entry
70. Click left on: Properties button
71. Click left on: IP Address tab
72. Click left on: Specify and IP Address selection circle
73. Double-click left on first numerical field in: IP Address area
74. Type in the desired IP Address separated by dots
75. Double-click left on first numerical field in: Subnet Mask area
76. Type in the desired Subnet Mask separated by dots
77. Double-click left on first numerical field in: Default Gateway area
78. Type in the desired Default Gateway separated by dots
79. Click left on: Apply button
80. Click left on: OK button
81. Click left on: Start -> Shutdown
82. Click left on: Restart selection
83. Click left on: OK button
84. Don’t forget you need to update the C:\Win2000\System32\Drivers\etc\hosts
file with the name of the Pegasys you will transfer data to and also update the info in the
DICOM configuration. Follow sections 3.7.2 and 3.7.3 in Chapter 8 of the CardioMD
Installation Manual.
NETWORKED PERIPHERALS: Don’t forget Codonics, Helios, local DICOM devices…

• NUMA: Open Windows Control Panel, Network, TCP/IP Properties for installed
Ethernet card. Change IP address and Subnet Mask. Also edit the “adac” IP address entry
in C:\WINDOWS\HOSTS file. Reboot the system and do a test ping + data transfer test.
Note: NUMA prefers that they be contacted to modem in and make any changes to their
systems. If you must make the changes yourself, then please do them the courtesy of
contacting them the next day to inform them of the changes so they can update their
configuration profile for this site.
• Transcam: Edit the following files after exiting to DOS, then reboot (Similar steps to those
for non-Atlas Acquisition PC Boot Floppy except we work in C:\NFS instead of A:\NFS)
EDIT C:\NFS\HOSTS (Edit IP Addresses)
EDIT C:\NFS\NETWORK.BAT (add “net subnet” if needed, as in Step 11)
• Codonics: Change the IP address (and subnet if appropriate) via the front panel.
• Helios: Change the IP address (and subnet if appropriate) via the front panel.
• DeltaManager: If you have any Apple Macintosh-based DeltaManager systems on you
LAN, you’ll have to reconfigure the TCP/IP settings for each system under the logo. You
may also have to change IP address of FTP destination hosts in the DeltaManager
configuration. System must be rebooted after changes.
Chapter 4: Network Peripherals Hardware and
Software
Scope
This chapter provides and catalogs example network files and troubleshooting information for
each of the peripheral hardware devices and software options available that are network related. The
chapter topics are:
Outline
HARDWARE DEVICES
I. Formatters
a. Local Formatters
b. Shared (Network) Formatters
II. Formatter Installation
a. Formatters Requiring Sbus and PCI Formatter Cards
b. Network Formatters
III. Modems
IV. Opticals
a. TenX
b. MaxOptix
c. Archive Tracker
V. Line Printers
VI. NUMA Direct Connect
SOFTWARE OPTIONS
I. DICOM
a. DICOM Transfer
b. DICOM Print
c. DICOM WorkList
II. Peg2Peg
III. WebView
IV. PPP
V. Shadow
VI. SeeMor
In the past, various other hardware and software peripherals have been available that are now
no longer supported on the Y2K platform. These include: Centor, RT11, MITA, MaxDelta Transfer,
GE and Picker Direct Connect, Viewpoint, PCAccess, Pega Modem, Image Report Generation,
Programmer’s Toolkit, and Easyload. These peripherals are not described in this chapter and are
listed here only for the sake of completeness.
(Within this chapter, the part number notations for the manuals used for hardware configuration and
software installation are followed by an “* ”. This is used as a wild card character to represent the
latest revision of the appropriate manual.)
Hardware Devices
FORMATTERS
Local Formatters
3M, GE, and other laser hard copy imagers require the SBus or PCI Formatter Cards,
depending on the host system, and are configured as local devices, only usable by the system to
which the formatter is connected.
• PegX requires a 2143-5524 SBus card (Note: The 2143-5525 SBus card is needed for 3M
formatters, 30MHz)
• Ultra1 requires a 2153-3300 SBus card.
• Ultra60 and Ultra10 require the PCI formatter card, option 2157-3251B
Shared (Network) Formatters

Helios, Seiko, Codonics, PostScript II, and DICOM compatible formatters are configured as
shared network devices in a Pegasys Network and exist as hosts on the network to which they are
connected.
FORMATTER INSTALLATION
Formatters Requiring Sbus and PCI Formatter Cards
Install the formatter card in the appropriate slot and follow the instructions provided in the
PegX or PegUltra Software Field Service Installation Manual (9202-0117* or 9202-0142*).
Installation instructions for the PCI formatter cards are included in the option package, 2157-3251B.
Important: Some formatters have the ability to run in interlace or non-interlace mode.
The PCI formatter card (GFX 8P) does NOT support formatters running in interlace
mode. The formatter must be capable of running in non-interlace mode to use this card.
Network Formatters
Helios and Seiko formatters are installed using the formatter setup floppies included with the
PegX and PegUltra software. The installation instructions are provided in the Software Field Service
Installation Manual for the system software (9202-0117* and 9202-0142*).
Important: Seiko formatters using a Milan Fastport interface are not supported on the
Y2K platform.
Codonics formatters can be installed using the Codonics formatter setup floppy or the
Codonics setup software CD. Installation instructions for the floppy setup are found in the Codonics
Formatters Software Field Service Manual (9202-0147*). Instructions for installing the Codonics
formatter from the CD are found in the Codonics Color Dye Sublimation Printers Release Document
(9215-0023*). To date, the only Codonics requiring that the software CD be used is the EP1660
Series.
When installing the above network formatters using the appropriate setup floppy, as well as
when installing the Codonics from the software CD, the software should be installed and configured
on the network master.
The PostScript II software is required for formatting to a PostScript Level 2 network-capable
formatter, such as a Lexmark color or black and white formatter. The installation instructions can be
found in the PostScript Level 2 Release Document (9215-0152*). The software should be installed
and configured on the master of the Pegasys network. There can only be one PostScript II formatter
actively installed on the network for use with this software.
Important: This software is strictly for installing and configuring a PostScript Level 2
formatter, for image display hard copy formats, and is not to be confused with a line (text)
printer.
DICOM formatters are configured within the DICOM software configuration utility, typically on
the master. The DICOM software package is addressed in the Software Options section.
Twisted Pair Formatter Network Cabling Diagram
Item 2: 10/100bT Straight-Through CAT5 Cable (Device to Switch/Hub) (5200-341x)

Item 7: 15 pin AUI to 10baseT Transceiver (5200-3282)
Item 13: RG-59 Coax Video Cable (2140-35xx)
Item 14: PegX S-bus Formatter Card (2143-3266A) or for 3M (2143-3266B)
Item 15: PegUltra Formatter Card (for S-bus 2153-3300) or (for PCI 2157-3251A)
Note: The RG-59 (video coax) and the RG-58 (networking coax) cables are NOT interchangeable.
Thinnet Formatter Network Cabling Diagram
Item 3: Thinnet to 15 pin AUI Transceiver (5200-3011)

Item 4: RG-58 Coax Network Cable (2141-07xx)
Item 5: 50 Ohm Terminator (5090-9251)
Item 6: T-connector (5090-1157)
Item 13: RG-59 Coax Video Cable (2140-35xx)
Item 14: PegX S-bus Formatter Card (2143-3266A) or for 3M (2143-3266B)
Item 15: PegUltra Formatter Card (for S-bus 2153-3300) or (for PCI 2157-3251A)
Item 21: BNC Barrel Connector (5090-3001)
Notes: The RG-59 (video coax) and the RG-58 (networking coax) cables are NOT interchangeable.
A Codonics printer has thinnet and RJ-45 ports, and it auto senses the ports. To
configure the IP address for the printer, refer to the Codonics Operators Manual. A
Helios Printer is a grayscale hard copy formatter. An AUI port connects the printer to
your network. You will need to order an AUI-10BaseT or AUI-thinnet converter.
Formatter Files
The following files contain information about formatters connected to the network. Files
which pertain to only PegX or PegUltra platforms are noted. If there is no notation, the files pertain
to both. The file entries listed should represent the correct syntax and configuration values for the
particular peripheral device, though the description name, hostname, and IP address of the device
may differ from site to site. The bolded entries in the following file represent examples of shared
network formatters.
cat /etc/hosts
127.0.0.1 localhost loghost
192.168.1.3 webview
192.9.200.81 shadow1
192.9.200.10 rogue timehost
192.9.200.20 cyclops
192.9.200.240 atlas1
192.9.200.43 lexmark # Postscript Level-II
192.9.200.73 PS_PRINTER # Codonics Postscript on cyclops
192.9.200.250 dicom_pr_test
192.9.200.50 ep1650
192.9.200.55 codonics_ep1660
192.9.200.52 helios1
Notes: Performing the Codonics installation using the setup floppy created the ep1650
entry in the hosts file. The installation from the Ver5.0 Software CD created the
codonics_ep1660 host entry.
The following two files contain the formatter entries. All of the formatters connected to
systems on the network and to the network itself should be seen here. Please note that there are some
differences between the entries in each file. The entry may be presented differently or may be
missing, dependent upon which platform will be utilizing the file.
cat /vol/patients_db/formatcap
(Formatter file used by the PegX Systems--This file lives on the master’s hard drive but is
accessible by all stations on the network, since the /vol/patients_db directory is shared.)
%seiko_raster_rogue
remark "raster maker"
model seiko
host rogue
spool $COMMON_TEMP_PATH
lprtype file_only
local yes
%helios1
remark "Helios810_Digital_Laser_Imager"
model polaroid
host rogue
lprtype no
%DICOM_pr
remark "DICOM printer"
model seiko
host rogue
lprtype file_only
local no
%hi_res_cyclops
remark "Sbus Formatter"
model HI_RES
host cyclops
lprtype video_only
local yes
%ep1650
remark “Codonics_digital_PS_(EP_Series)”
model seiko
host rogue
lprtype no
local no
%film_ep1660
model seiko
host rogue
lprtype file_only
local no
%paper_ep1660
model seiko
host rogue
lprtype file_only
local no
%PS_PRINTER
remark "Codonics digital Postscript (np-1600)"
model seiko
host cyclops
lprtype no
local no
cat /vol/patients_db/formatcap_db
(Formatter file used by PegUltra Systems--This file lives on the master’s hard drive but is
accessible by all stations on the network, since the /vol/patients_db directory is shared.)
%seiko_raster_rogue
remark "raster maker"
model seiko
host rogue
lprtype file_only
local yes
%helios1
remark "Helios810_Digital_Laser_Imager"
server_host rogue
spool_path $COMMON_TEMP_PATH
image_type grey_map
file_type helios
print_type lpr
print_parameter image_file
remove_image server
%DICOM_pr
file_type raster
image_type true_color
server_host rogue
print_type file_only
%hi_res_cyclops
remark "Video Formatter on SBus"
server_host cyclops
image_type grey_map
file_type raster
print_type video_only
remove_image client
model HI_RES
local yes
%ep1650
remark "Codonics_digital_PS_(EP_Series)"
server_host rogue
image_type true_color
file_type raster
print_type lpr
print_parameter request_file
remove_image client
model seiko
%film_ep1660
file_type raster
image_type pseudo_color
server_host rogue
%paper_ep1660
file_type raster
image_type pseudo_color
server_host rogue
%pci_hi_res_gray_rogue
remark "(Video Formatter gray on the PCI Bus for Motif Apps)"
server_host rogue
image_type grey_map
file_type raster
remove_image client
model HI_RES
%pci_hi_res_gray_inv_rogue
remark "(Video Formatter inverted gray scale on the PCI Bus for
Motif APPS)"
server_host rogue
image_type grey_inv
file_type raster
remove_image client
model HI_RES
%pci_hi_res_gray_peg_rogue
remark "(Video Formatter gray scale on the PCI Bus for Pegasys
Apps)"
server_host rogue
image_type grey_map
file_type raster
remove_image client
model scopix
copy_pix_width 1020
copy_pix_height 807
%pci_hi_res_gray_inv_peg_rogue
remark "(Video Formatter inv gray on the PCI Bus for Pegasys APPS)"
server_host rogue
image_type grey_inv
file_type raster
remove_image client
model scopix
copy_pix_width 1020
copy_pix_height 807
%lexmark
remark "Generic Post Script Printer"
file_type raster
print_type client_command
print_parameter request_file
server_host rogue
print_command "/usr/adac/pegx/scripts/adac_Solaris_postscript_filter"
Notes: The film_ep1660 and paper_ep1660 configuration entries in each file were created
using the Codonics Ver5.0 software, loaded from the CD. Also, The PCI Formatter card
software installation created all four entries seen in the formatcap_db file (pci_hi_res…).
The bolded entries within the following files, represent example entries for formatters. The
entries ending in ‘LOCAL’ specify the formatters only accessed by their host system and ‘ALL’
specify the shared network formatters.
cat /vol/patients_db/periph.rsc
# Contains entries for all peripherals on the network
FORMATTER seiko_raster_rogue rogue /dev/ LOCAL
FORMATTER helios1 rogue /dev/helios1 ALL
FORMATTER DICOM_pr rogue /dev/null ALL
FORMATTER hi_res_cyclops cylops /dev/ LOCAL
FORMATTER ep1650 rogue /dev/ep1650 ALL
FORMATTER film_ep1660 rogue /dev/null ALL
FORMATTER paper_ep1660 rogue /dev/null ALL
FORMATTER pci_hi_res_gray_rogue rogue /dev/pci_rogue LOCAL
FORMATTER pci_hi_res_gray_inv_rogue rogue /dev/pci_rogue LOCAL
FORMATTER pci_hi_res_gray_peg_rogue rogue /dev/pci_rogue LOCAL
FORMATTER pci_hi_res_gray_inv_peg_rogue rogue /dev/pci_rogue LOCAL
LINEPRINTER epson_cyclops cyclops /dev/ttyb
OPTICAL opti_cyclops cyclops /dev/sd2a
FORMATTER Lexmark rogue /dev/Lexmark ALL
FORMATTER PS_PRINTER Cyclops /dev/PS_PRINTER ALL
The following file contains the names of the peripheral devices selected as defaults for the
local system. The file listed shows examples of possible entries. The entries in the localdev.def file
can vary from system to system on the network.
cat /etc/modules/localdev.def
The next file is the configuration file created for the Codonics printers when loading the
software from the Ver5.0 software CD. This file resides on the master of the network and is shared
through the /vol/patients_db directory.
cat /vol/patients_db/Codonics/codonicsprint.cfg
#################################################################################
###
#
# DICOM Configuration File for Remote DICOM Printer Servers
#
# Definition: A DICOM printer is a DICOM Application Entity that performs the SCP
role of
# DICOM print management service class in a remote host.
#
# Copyright (C) 1996 ADAC Laboratories, Milpitas, CA 95035
#
# This files contain entries of DICOM printers. The format of an entry is like
the following.
#
# % Printer_name
# node = printer_host_name (same as in /etc/hosts)
# port = TCP_port_number
# callingAEtitle = my_calling_AE_title
# calledAEtitle = printer_called_AE_title
# format = STANDARD\1,1 | STANDARD\2,2
# film_size_ID = 8INX10IN
# orientation = LANDSCAPE | PORTRAIT
# medium = PAPER | BLUE FILM | CLEAR FILM
# copies = 1 | number
# priority = HIGH | MED | LOW
# transpose = NO | YES
# grayscale = NO | YES
# magnification = REPLICATE | BILINEAR | CUBIC | NONE
# trim = NO | YES
# frequency = 15 | number in secs
# timeout = 30 | number in secs
#
#
# Note: The Printer_name must be unique.#
#################################################################################
###
#
#
%film_ep1660
node = codonics_ep1660
port = 104
callingAEtitle = ADAC_SCU
calledAEtitle = DICOM_SCP
format = STANDARD\1,1
film_size_ID = 8INX10IN
orientation = LANDSCAPE
medium = FILM
copies = 1
priority = MED
transpose = YES
grayscale = YES
reverse_video = NO
magnification = REPLICATE
trim = NO
config_info =
min_density =
max_density =
smooth = NO
border_density = BLACK
empty_img_density = BLACK
film_destination = MAGAZINE
start_preview = NO
frequency = 5
timeout = 10
%paper_ep1660
node = codonics_ep1660
port = 104
film_size_ID = A
medium = PAPER
copies = 1
priority = MED
transpose = NO
grayscale = NO
reverse_video = NO
trim = NO
config_info = mcm=101
min_density =
max_density =
smooth = NO
start_preview = NO
frequency = 5
timeout = 10
Formatter Troubleshooting Information
PCI FORMATTERS
If there are two PegUltra clients on the network that require a PCI formatter card, be aware
that when installing the second PCI card, the entries in the periph.rsc and formatcap_db files for the
original client’s card installed will be overwritten with the information of the second client’s
hostname. The files must be edited manually to recreate the entries for the original card. There is a
tech tip that demonstrates the edits needed.
CODONICS FORMATTERS
If both film and paper media is used with the same Codonics formatter, then two separate
configuration entries should be created, one for film and one for paper, with the correct settings for
the media used. The examples in the previous section demonstrate the correct entries in the
codonicsprint.cfg file and in the formatcap/formatcap_db files. Having the two separate
configuration entries reduces the number of problems seen with format failures due to a bad
configuration.
Modems
Every new camera system that is shipped to a customer includes an external modem that can
be configured for remote diagnostic access, remote image transfer, and/or remote image reading.
Types of modems existent in the field include Telebit-Trailblazer, Telebit-Worldblazer, US Robotics
Courier, and Motorola. Currently, US Robotics modems are included with new systems. Motorola
modems are primarily configured on systems outside of North America.
Telebit modems can only be used for remote diagnostic access, and must be replaced if the
customer wishes to perform image transfers or remote reading of images. Motorola and US Robotics
modems, however, can be used for all of the functions listed above.
To perform any function, the modem must first be configured and initialized. Additional
software configurations required for some functions are described in the Software Option section,
under the specific software category.
INSTALLATION
Important: All modems are connected to a serial port on either the PegX or the PegUltra
systems. Either serial port, a or b, can be used on the PegX system. However, only serial
port b can be used on PegUltra systems, as serial port a is reserved for License “dongle”.
Telebit modem installations are not supported in the Y2K base applications software load.
This is not an issue with the new systems being shipped, however, this can potentially affect an
existing site. If a problem arises that requires the hard drive be replaced, the modem initialization
script for the Telebit style modems will be lost. The modem will have to be upgraded to a US
Robotics or the modem would have to be installed from a non-Y2K compliant software version CD.
(The pega_modem option would have to be installed from a Ver3.31 or Ver3.30 PegasysX software
CD; these are the only CDs containing the Telebit initialization script.) The guidelines for installing
and testing the Telebit modem is explained in procedure 9343-1136.
US Robotics and Motorola modems are installed and tested using a software floppy. After
installing and successfully completing the test, messages reporting ‘modem pre-test OK’ and ‘Done’
will be reported. If the test is not successful, there are various possible error messages and
suggestions for resolving the cause of the error listed in the installation document, 9355-0102*. If
you have problems initializing the port on an Ultra, try going to admintool and setting the serial
port to "Initialize only,” them run modem init script, then set back to “Modem Bi-directional.”
MODEM FILES AND CONFIGURATION CHECKS

The following file shows examples of modem entries in bold. This file is not a shared
network file and should be checked on the system where the modem is installed. This particular
system has two modems configured on it, one on serial port a (ttya) and the other on serial port b
(ttyb). If only one modem is configured on a system, the serial port not being used will have an entry
similar to that for tty00.
head /etc/ttytab (This file exists on and applies to PegX systems only.)
#
# @(#)ttytab 1.7 92/06/23 SMI
#
# name getty type status comments
#
console "/usr/etc/getty cons8" sun on local secure
ttya "/usr/etc/getty D19200" dialup on remote
ttyb "/usr/etc/getty std.38400" dialup on remote
tty00 "/usr/etc/getty std.9600" unknown off local secure
tty01 "/usr/etc/getty std.9600" unknown off local secure
The following command reports the information from admintool on a PegUltra system. The
bolded entry shows values for a modem installed on serial port b.
pmadm -l -p zsmon (PegUltra)
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>

zsmon ttymon ttyb u root /dev/term/b b -
/usr/bin/login - 38400 ldterm, ttcompat login: - tvi925 n #Modem -
Bidirectional
zsmon ttymon ttya u root /dev/term/a I -
/usr/bin/login – 9600
ldterm,ttcompat login: - tvi925 y #Terminal - Hardwired
The character devices for the serial ports on a PegX system should exist in the /dev directory.
The following command can be used to list them. The results of the listing should match that seen
below. These nodes must exist in order to successfully initialize the modem.
ls –lrt /dev/cua* (PegX)

crw-rw-rw- 1 root 12, 128 Feb 2 15:20 /dev/cua0
crw-rw-rw- 1 root 12, 129 Feb 7 14:47 /dev/cua1
MODEM TROUBLESHOOTING INFORMATION

Various problems can occur between initializing the modem and dialing in on the modem.
Typically they can be resolved by verifying/correcting the entries in the above files. Please refer to
the technical tips to resolve any modem problems.
Optical Drives
Three varieties of optical drives currently exist in the field as of this writing:
1. TenX (Maxtor drive)

2. MaxOptix
3. Archive Tracker (1.3GB, 2.6GB, 5.2GB)
The TenX drive was the optical drive originally offered, however, it is no longer shipped to
the field. It is obsolete, since hardware replacements are no longer available. It utilizes Maxtor
WORM (Write Once Read Many) media, which is also difficult to obtain. It is described here for
completeness. Although CD-R is also a variety of WORM media, CD-R disks are not compatible
with this proprietary drive media format.
The MaxOptix drive is offered as a replacement for TenX drives that exist in the field, as
well as an optical option for the PegX systems. It can only be configured on a PegX system. It is not
compatible with the PegUltra systems. It uses re-writable optical media. This media may be re-used
after formatting, if desired. This may serve to reduce cost for the customer as they can reuse the
media after the shelf life of the archives has expired.
Archive-Tracker is currently the only optical available for configuration with the PegUltra
systems being shipped. It is compatible with both PegX and PegUltra systems. The Archive Tracker
also uses re-writable optical media. This media may be re-used after formatting, if desired. This may
serve to reduce cost for the customer as they can reuse the media after the shelf life of the archives
has expired.
OPTICAL INSTALLATION
TenX and MaxOptix drives are configured on PegX systems with the mkopticals script. This
installation script creates the necessary file entries for access to the optical drive. The script can be
run from a UNIX window by typing the following command: $PEGXSCRIPTS/load/mkopticals
and answering the prompts given. It can also be configured from the “ADAC Config Tools” entry
on the root menu when logged in as root with X-Windows running. Instructions are provided in the
PegX Software Field Service Installation Manual, 9202-0117*.
The Archive-Tracker option is installed and configured from its own software CD. The
installation makes the necessary modifications to the appropriate files needed for the Tracker optical
drive. Follow the instructions provided in the Archive Tracker Release Document, 9215-0086*, to
configure the hardware and install the option software.
OPTICAL FILES
The following files contain information about the optical drives on the network.
TENX AND MAXOPTIX FILES

The bolded entry within the following files represents an example entry for either a TenX or
MaxOptix optical drive.
# Contains entries for the default peripherals selected for the local system
The optical directory is exported, so other network hosts (PegX only) can access the optical.
The following entry, shown in bold, only exists on the system where the drive is physically
connected.
cat /etc/exports
/files/vol/patients/patients_db
/var/spool/mail
/files/pat/patients/patients0
/files/pat/patients/centor
/files/pat/patients/rt11
/files/pat/patients/mita
/usr/adac/informix
/files/pat/camera1
/files/camera1
/etc/modules
/var/spool/pcnfs
/worm/physical/opti_cyclops
Also check that the /dev directory contains an entry for sd2a ( ls /dev/sd2a), and that the /worm
directory exists ( ls /worm). Also verify that the drive is being seen on bootup. Use the dmesg
command to display the bootup messages and search for the ‘target 2’ device.
The following is an example of possible entries found in the dmesg report. The bolded entry shows
the optical device, in this example it is a TenX drive. The output will vary depending on the number
of recent reboots or the amount of time since the last reboot.
dmesg
C ENABLED in COPYBACK mode
SunOS Release 4.1.3_U1 (ADAC_PEGX_SUN4M_HSBQEHME) #1: Sat Nov 2 11:24:00
PST 1996
Copyright (c) 1983-1993, Sun Microsystems, Inc.
cpu = SUNW,SPARCstation-20
mod0 = Ross,RT625 (mid = 8)
mem = 81460K (0x4f8d000)
avail mem = 76619776
cpu0 at Mbus 0x8 0x240000
entering uniprocessor mode
Ethernet address = 8:0:20:74:a5:63
espdma0 at SBus slot f 0x400000
esp0 at SBus slot f 0x800000 pri 4 (onboard)
sd0 at esp0 target 3 lun 0
sd0: <ADAC_2126_SEAGATE cyl 2733 alt 2 hd 19 sec 80>
sd2 at esp0 target 2 lun 0
sd2: Vendor 'Ten', product 'OCU-110S', (unknown capacity)
st0 at esp0 target 4 lun 0
st0: <Archive QIC-150>
ledma0 at SBus slot f 0x400010
le0 at SBus slot f 0xc00000 pri 6 (onboard)
SUNW,bpp0 at SBus slot f 0x4800000 pri 3 (sbus level 2)
SUNW,DBRIe0 at SBus slot e 0x10000 pri 9 (sbus level 5)
cgsix0 at SBus slot 2 0x0 pri 9 (sbus level 5)
cgsix0: screen 1152x900, single buffered, 1M mappable, rev 11
zs0 at obio 0x100000 pri 12 (onboard)
zs1 at obio 0x0 pri 12 (onboard)
SUNW,fdtwo0 at obio 0x700000 pri 11 (onboard)
MMCODEC: manufacturer id 1, rev 2
root on sd0a fstype 4.2
swap on sd0b fstype spec size 95000K
dump on sd0b fstype spec size 94980K
le0: Twisted Pair Ethernet
le0: No carrier - twisted pair cable problem or hub link test disabled?
pegainit: VDLOAD
Image memory found @ pegasys0
System Controller found @ pegasys0
ACP 0 found @ pegasys0
8 bit Image memory found @ pegasys0
ADACLab,pegasys0 at SBus slot 1 0x8000 pri 2 (sbus level 1)
Note: Instead of simply typing dmesg, an advanced search string could be used to only list
the desired information: dmesg | grep sd2
Entering this command string will list only the sd2 entries from the dmesg report.
TENX AND MAXOPTIX TROUBLESHOOTING INFORMATION

If an optical disk is suspected of being corrupted, the fsck command can be used to repair the
optical media. Load the media in the drive and as superuser, type the command:
fsck /dev/rsd2a
The command runs on the media loaded in the optical drive and reports similar messages and
prompts as when run on a system hard drive.
ARCHIVE TRACKER FILES

The Archive-Tracker optical does not have any entries in the periph.rsc or localdev.def file on
any of the systems.
The following file exists on a PegX system and contains the Atx entry only if the drive is
physically connected to that system. There is no corresponding file on the PegUltra platform.
cat /etc/exports (PegX)

/var/spool/mail
/usr/adac/informix
/files/pat/camera1
/files/camera1
/etc/modules
/var/spool/pcnfs
/AtxDrv
An entry exists at the end of the ADACSetup file to set the environmental variables for the
Archive-Tracker option. If any of the entries are missing, the Tracker application reports errors or
fails to perform. The bolded entries in the following file will vary depending on the hostnames on the
network and the configuration setup at installation of the software.
grep -i atx /usr/adac/site/`hostname`/ADACSetup

##atx Archive-Tracker setup
setenv ATX_DATE US ##atx
setenv VOL_NAME_BASE tech_support ##atx
setenv ATXDBPORT 13000 ##atx
setenv OPTICAL_MOUNT /Atx ##atx
setenv ATX_PATH /eoddir ##atx
setenv ATXDBHOST rogue ##atx
setenv OPTICAL_HOST rogue ##atx
setenv ATX_OPT_DEV sd18 ##atx
Note: The value for the ATX_OPT_DEV entry is dependent on the type of system to
which the drive is physically connected. Refer to the following table for the values:
System ATX_OPT_DEV
PegX Tower sd3
Ultra1 sd0
Ultra60 sd18
Ultra10 sd0 (sd4, sd19 also possible)
The default SCSI device value for the Archive-Tracker on an Ultra10 is sd0. On some
systems in the field this value has varied, including sd4 and sd19. If you encounter problems when
installing the Archive-Tracker drive on an Ultra10, please refer to the tech tips or contact technical
support.
The same ‘atx’ line entries that appear at the end of the ADACSetup file should also appear in
the /eoddir/atx.env file. If for some reason the entries do not exist in the ADACSetup file they can be
retrieved from the atx.env file and copied to the end of the ADACSetup file. The atx.env file exists
on all the systems with the Tracker software installed.
There may be other entries reported in the ADACSetup file that pertain to networks including
a Mass Storage jukebox. On one such network, the result of the previous command, grep –i atx
/usr/adac/site/`hostname`/ADACSetup, would generate an output similar to the following, again the
bolded entries will vary.
##atx Archive-Tracker setup

setenv ATX_DATE US ##atx
setenv VOL_NAME_BASE nuc_med ##atx
setenv ATXDBPORT 13000 ##atx
setenv OPTICAL_MOUNT /Atx ##atx
setenv ATX_PATH /eoddir ##atx
setenv ATXDBHOST adac1 ##atx
setenv OPTICAL_HOST adac1 ##atx
setenv ATX_OPT_DEV sd18 ##atx
##ms.atx Mass Storage setup

setenv ATX_PATH /eoddir ##ms.atx
setenv ATX_ISM_HOST jukebox ##ms.atx
setenv ATX_ISM_PATH /vol/patients13 ##ms.atx
Note: Details about the Mass Storage system are not provided here, since there are a
limited number of customers with this option. Please contact technical support if
assistance is needed with a Mass Storage site.
The following file contains the optical hostname, the name given to the drive at installation,
and the SCSI device name for the drive. The file only exists on the system where the drive is
physically connected.
cat /eoddir/atx.drives
roguetrackersd18
(where optical hostname= rogue, drive name= tracker, and SCSI device name= sd18)
One of the features of the Tracker option is that it maintains a database of the patients that
have been archived and the volume disk to which they were archived. There are files and processes
associated with this Tracker database that can be referenced for troubleshooting purposes. Only one
system on the network is the Tracker database host. It may or may not be the system where the drive
is physically connected. The hostname reported next to the ATXDBHOST entry in the ADACSetup
or atx.env file is the Tracker database host. On the database host system, the following files can be
checked for information accuracy and troubleshooting.
Verify that the two database processes for the Archive-Tracker are running:
running atx
331 ? S 0:00 /bin/sh /etc/rc.atx.dbsrvr 13000 /eoddir
353 ? S 0:00 /eoddir/atxDbServer 13000 atxDbServer /eoddir
If these two processes are not running, the Tracker applications will report an error if trying to
archive or restore patient data.
There is also a resource file that contains more information about the Tracker database directories and
other parameters set at installation of the software that can be helpful when troubleshooting Tracker
database access problems:
/eoddir/atxMakeRes /eoddir
Resource file already exists:
DB directory: /vol/patients0/atxDB
DB backup directory: /vol/patients0/atxBack
DB journal directory #1: /vol/patients0/atxJou
DB journal directory #2:
DB volume log directory: /vol/patients0/atxVlog
DB backup start hour: 1
DB backup start minute: 0
DB backup interval hour: 24
DB maximum capacity: 52428800
DB reminder interval: 30
DB record retain time: 0
Do you still want to update resource file (y/n)? n

Resource file not updated.
The dmesg command can be used on the PegX and PegUltra systems to identify whether or
not the Tracker drive is seen by the system on reboot. The SCSI device associated with ‘target 3’
reflects the Tracker drive.
dmesg <Example from an Ultra-60>

Feb 19 11:41
cpu0: SUNW,UltraSPARC-II (upaid 0 impl 0x11 ver 0x20 clock 360 MHz)
SunOS Release 5.5.1 Version Generic_103640-23 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1996, Sun Microsystems, Inc.
mem = 262144K (0x10000000)
avail mem = 259801088
Ethernet address = 8:0:20:9b:2c:eb
root nexus = Sun Ultra 60 UPA/PCI (UltraSPARC-II 360MHz)
pci108e,80000 at root: UPA 0x1f 0x4000
pci108e,80001 at root: UPA 0x1f 0x2000
glm0: Rev. 5 Symbios 53c875 found.
PCI-device: scsi@3, glm #0
glm1: Rev. 5 Symbios 53c875 found.
PCI-device: scsi@3,1, glm #1
sd0 at glm0: target 0 lun 0
sd0 is /pci@1f,4000/scsi@3/sd@0,0
<SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
sd6 is /pci@1f,4000/scsi@3/sd@6,0
sd18 is /pci@1f,4000/scsi@3,1/sd@3,0
root on /pci@1f,4000/scsi@3/disk@0,0:a fstype ufs
PCI-device: ebus@1, ebus #0
su0 at ebus0: offset 14,3083f8
su0 is /pci@1f,4000/ebus@1/su@14,3083f8
su1 at ebus0: offset 14,3062f8
su1 is /pci@1f,4000/ebus@1/su@14,3062f8
keyboard is </pci@1f,4000/ebus@1/su@14,3083f8> major <37> minor <0>
mouse is </pci@1f,4000/ebus@1/su@14,3062f8> major <37> minor <1>
stdin is </pci@1f,4000/ebus@1/su@14,3083f8> major <37> minor <0>
SUNW,ffb0 at root: UPA 0x1e 0x0
SUNW,ffb0 is /SUNW,ffb@1e,0
stdout is </SUNW,ffb@1e,0> major <131> minor <0>
boot cpu (0) initialization complete - online
se0 at ebus0: offset 14,400000
se0 is /pci@1f,4000/ebus@1/se@14,400000
SUNW,hme0: CheerIO 2.0 (Rev Id = c1) Found
PCI-device: network@1,1, hme #0
SUNW,hme0 is /pci@1f,4000/network@1,1
dump on /dev/dsk/c0t0d0s1 size 1587152K
SUNW,hme0: Using Internal Transceiver
SUNW,hme0: 100 Mbps half-duplex Link Up
pcmcia: no PCMCIA adapters found
Note: Instead of simply typing dmesg, an advanced search string could be used to only list
the desired information: dmesg | grep “target 3”
Entering this command string will list the ‘target 3’ entries only from the dmesg report.
ARCHIVE-TRACKER TROUBLESHOOTING INFORMATION

The optical media for Archive-Tracker can also be checked and repaired using fsck: fsck
/dev/rsd18c The device name will differ depending on the system the drive is connected to, so refer
to the ADACSetup file entry for the ATX_OPT_DEV field to identify the device name to use. (The
example fsck command listed is for a drive connected to an Ultra60 system- sd18.) The device name,
when running the fsck command, must always be preceded by an ‘r’ and followed by a ‘c’.
Possible problems can be encountered with access to the Tracker Database, either when archiving or
restoring.
• Verify that the drive is seen on the optical host system
• Verify the atx entries in the ADACSetup file
• Verify the information in the resource file for accuracy (atxMakeRes)
• Verify access to all of the atx directories listed in the resource file output
• Verify that the database server processes are running on the ATXDBHOST
Refer to the technical tips and to the Archive Tracker Release Document for further
troubleshooting information.
Important: Archiver/Tracker software will not install on Pegasys systems whose

hostnames exceed 10 characters.
Line Printers
It is possible to connect a text printer to any Pegasys system via a serial port connection. HP
Laserjet, Epson and Okidata line printers have been configured successfully on a Pegasys system.
These printers are designated for simple text printing, not image formatting. This hardware/software
configuration does not support the formatting of images.
LINE PRINTER INSTALLATION

Line printers can be installed on a Pegasys system with the following command:
$PEGXSCRIPTS/load/mkprinters
This command should be executed from the system where the line printer is connected. The
script advances through the install and prompts for responses as needed. The “ADAC Config Tools
Menu”, when logged in as root, is another way to access the mkprinters program for installing a line
printer.
LINE PRINTER FILES

The bolded lines in the following files are examples of line printer entries on the Pegasys
network.
cat /etc/printcap
#
# This is a sample of printcap entries used by various printers/plotters.
# All entries have been commented out to avoid complaints from the line
# printer daemon about printers that don't really exist.
#
# # DecWriter over a tty line.
# lp|ap|arpa|ucbarpa|LA-180 DecWriter III:\
# :br#1200:fs#06320:tr=\f:if=/usr/lib/lpf:lf=/usr/adm/lpd-errs:
# # typical remote printer entry
# ucbvax|vax|vx|ucbvax line printer:\
# :lp=:rm=ucbvax:sd=/usr/spool/vaxlpd:lf=/usr/adm/lpd-errs:
# varian|va|Benson Varian:\
# :lp=/dev/va0:sd=/usr/spool/vad:mx#2000:pl#58:px#2112:py#1700:tr=\f:\
# :of=/usr/lib/vpf:if=/usr/lib/vpf:tf=/usr/lib/rvcat:cf=/usr/lib/vdmp:\
# :gf=/usr/lib/vplotf:df=/usr/local/dvif:\
# :vf=/usr/lib/vpltdmp:lf=/usr/adm/lpd-errs:
# versatec|vp|Versatec plotter:\
# :lp=/dev/vp0:sd=/usr/spool/vpd:sb:sf:mx#0:pw#106:pl#86:px#7040:py#2400:\
# :of=/usr/lib/vpfW:if=/usr/lib/vpsf:tf=/usr/lib/vcat:cf=/usr/lib/vdmp:\
# :gf=/usr/lib/vplotf:vf=/usr/lib/vpltdmp:lf=/usr/adm/lpd-errs:\
# :tr=\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\
# \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\
# \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n:
epson_cyclops|cyclops-2ttyb:\
:lp=/dev/ttyb:sd=/usr/spool/epson_cyclops:\
:lf=/usr/spool/epson_cyclops/error_log:br#9600:\
:fs#06020:fc#0300:xs#040:
LINE PRINTER TROUBLESHOOTING INFORMATION

If there are problems printing to the line printer, check for the existence of the line printer
entries in the files listed above. If they are missing or incorrect, run the command to add a new
printer.
NUMA Direct Connect
NUMA is a third party vendor that provides connectivity hardware to interface other Nuclear
Medicine vendor products with the Pegasys. It is a PC system that receives images from the other
Nuclear Medicine vendor, translates those images to Pegasys format and transfers the translated file
to the Pegasys for display or processing. There can also be a bi-directional option installed that
allows for the translation of Pegasys format images to the other vendor format.
NUMA INSTALLATION
The hardware for the Direct Connect system is installed by NUMA, Inc.
NUMA FILES
The NUMA system performs all of the translation and moving of the image files. Once the
images are received on the NUMA PC, the Gammacon program executes to convert the files. After
conversion, the files are placed in a ‘waiting’ directory on the PC. NUMA ftp is the program that
copies the files from the ‘waiting’ directory to the /vol/mita directory on the Pegasys, and calls the
generic_add_db script on the Pegasys to add the images to the database.
NUMA TROUBLESHOOTING INFORMATION

If the Pegasys is not receiving images from the NUMA PC, there are only three things to
verify on the Pegasys:
• /vol/mita directory exists
• ownership/permissions of generic_add_db script
ownership: pegasys, users
permissions: -rwxrwxr-x
• ownership/permissions/checksum of add_to_db script (which is called by the

generic_add_db script)
ownership: pegasys, users
permissions: -rwxrwxr-x
checksum: PegX = 5F35DA75
PegUltra = 1F656216
If all of the information on the Pegasys is correct, have the customer contact NUMA to
troubleshoot the PC. NUMA is responsible for supporting the PC interface.
Note: As of the time of this writing, if the site has a Bi-Directional NUMA, there is a
known problem with the polling frequency of the NUMA box when it looks at the Out-
basket directory /vol/rt11/native. Since it checks once per minute, the login tracking files
(/var/adm/wtmpx and others) add a new entry each time and fill up at a rate of just over 1
MB per day. This can go on for a couple months on a PegUltra, but on a PegX unit it will
choke the root file system in just a couple weeks. The current know solution is to purge
the files by copying /dev/null to them. Example:
PEGASYS@adac:#[11] cd /var/adm
PEGASYS@adac:#[12] ls -l
total 4450
drwxrwxr-x 5 adm adm 512 Oct 31 1997 acct/
-rw------- 1 uucp bin 0 Oct 31 1997 aculog
-r--r--r-- 1 root other 3696 Jan 23 16:27 lastlog
drwxrwxr-x 2 adm adm 512 Oct 31 1997 log/
-rw-r--r-- 1 root other 129 Jan 21 12:03 messages
-rw-r--r-- 1 root other 186 Jan 15 10:55 messages.0
-rw-r--r-- 1 root other 1637 Dec 28 09:09 messages.3
drwxrwxr-x 2 adm adm 512 Oct 31 1997 passwd/
drwxrwxr-x 2 adm sys 512 Oct 31 1997 sa/
-rw-rw-rw- 1 bin bin 0 Oct 31 1997 spellhist
-rw------- 1 root root 3384 Nov 16 09:06 sulog
-rw-r--r-- 1 root bin 324 Jan 23 16:27 utmp
-rw-r--r-- 1 root bin 3348 Jan 23 16:27 utmpx
-rw-rw-rw- 1 root root 189 Oct 31 1997 vold.log
-rw-rw-r-- 1 adm adm 195624 Jan 23 16:27 wtmp
-rw-rw-r-- 1 adm adm 2020704 Jan 23 16:27 wtmpx
PEGASYS@adac:#[13] cp /dev/null wtmp

cp: overwrite wtmp (yes/no)? y
cp: cannot create wtmp: Permission denied
PEGASYS@adac:#[14] su
Password:
adac# cp /dev/null wtmp

adac# cp /dev/null wtmpx
adac# ls -l
total 82
drwxrwxr-x 5 adm adm 512 Oct 31 1997 acct
-rw------- 1 uucp bin 0 Oct 31 1997 aculog
-r--r--r-- 1 root other 3696 Jan 23 16:27 lastlog
drwxrwxr-x 2 adm adm 512 Oct 31 1997 log
-rw-r--r-- 1 root other 129 Jan 21 12:03 messages
-rw-r--r-- 1 root other 1637 Dec 28 09:09 messages.3
drwxrwxr-x 2 adm adm 512 Oct 31 1997 passwd
drwxrwxr-x 2 adm sys 512 Oct 31 1997 sa
-rw-rw-rw- 1 bin bin 0 Oct 31 1997 spellhist
-rw------- 1 root root 3421 Jan 23 16:27 sulog
-rw-r--r-- 1 root bin 324 Jan 23 16:27 utmp
-rw-r--r-- 1 root bin 3348 Jan 23 16:27 utmpx
-rw-rw-rw- 1 root root 189 Oct 31 1997 vold.log
-rw-rw-r-- 1 adm adm 0 Jan 23 16:28 wtmp
-rw-rw-r-- 1 adm adm 0 Jan 23 16:28 wtmpx
Software Options
DICOM
WHAT IS DICOM?
DICOM- Digital Imaging and COMmunications in Medicine is a multi-modality medical
image and communication/connectivity software package developed according to the ACR
(American College of Radiology) and NEMA (National Electrical Manufacturers Association)
standard. The Philips/ADAC DICOM release is based on the DICOM Version 3.0 standard.
DICOM FEATURES
• Exports and imports image data to and from Nuclear Medicine computer systems.
• Imports multi-modality medical images
• Exports and imports image data to and from archiving systems that support DICOM
• Prints color and greyscale images to a local or remote DICOM formatter
WHAT ARE THE REQUIREMENTS?
DICOM is a software-only package. For it to work, all network hardware setup must be
completed and communication established between the systems, whether a router, switch, or second
Ethernet card is used as the interface.
DICOM DOCUMENTS
Conformance statement
A customer or other vendor wishing to connect via DICOM to a PegasysX or PegUltra system
may request information about Philips/ADAC's DICOM software. The DICOM 3.0 Conformance
Statement - Pegasys (9605-0132*) contains the information about sending and receiving DICOM
files to and from a Pegasys system, PegX or PegUltra.
The Philips/ADAC DICOM 3.0 Conformance statement (in PDF format) requires the Adobe
Acrobat Reader. The latest TAC Version 1.1 CD contains this DICOM Conformance statement in
PDF format. The file is in the following location:
D:\Tac\Tac_docs\Latest\Netwkdoc\Dicom\Pegxcnfm.pdf
When a Pegasys system connects to a DICOM PACS (archive and storage system often
shared by many departments in a hospital), it is necessary to get the DICOM Conformance statement
from the PACS system manufacturer only. It is not necessary to get Conformance statements from
each of the different vendors that send images to the PACS - even if these "other vendor" images may
be transferred to the Pegasys system from the PACS system. Conformance statements for other
vendors are only required if there is direct connectivity between the Pegasys and the ‘other vendors’
systems.
DICOM SITE SURVEY:

The purpose of Philips/ADAC’s DICOM Site Survey is twofold: 1) To allow the Engineering
group to review information about the DICOM system the customer wishes to connect to, and 2) to
get important configuration parameters from the other DICOM vendor that Philips/ADAC needs to
know when running the Configuration Utility during the DICOM installation. The DICOM site
survey is currently part of the Custom Networking Survey section of the Nuclear Medicine Site
Survey Document CS-16-1*.
DICOM RELEASE PACKAGES:

As of this writing, Several DICOM packages are available to the customer:
PASY,DICOM V4.24 SW OPT (Full DICOM Ultra/Blade)
PASY, PASY,DICOM WL 5.0 SW SOL8 OPT (WorkList Ultra/Blade Solaris 8 ONLY)
PASY,DICOM V4.22 SW OPT (Full DICOM Transfer/Print package, PegX)
PASY,DICOM PRINT V4.22 SW OPT (DICOM Print package, PegX)
PASY,DICOM WL V3.41/4.21 SW (WorkList Option package, PegX / Ultra 2.5.1)
The above packages include software for both PegX/PegUltra systems (except Solaris 8 versions).
DICOM 4.24 cannot be loaded on PegX systems. Furthermore, a PegX cluster must be
running Version 4.22 in order to communicate to a cluster running DICOM Version 4.24. You must
spilt a mixed network into multiple domains so that the PegX cluster can run DICOM 4.22 and the
PegUltra 2.5.1 cluster runs DICOM Version 4.24.
DICOM Image Transfer contains the software and documentation that allows for configuring
the Pegasys system to connect to DICOM systems from other vendors. DICOM Print allows Pegasys
images to be printed to DICOM formatters. DICOM WorkList allows for the import of patient
information stored in a Radiology Information System (RIS) to an Atlas-based acquisition system
prior to performing the study.
All the Philips/ADAC DICOM packages include a site license, which allows the software to
be loaded on any number of Pegasys systems in the customer’s network.
DICOM INSTALLATION
Each Philips/ADAC DICOM software package has a specific release document that contains
its installation instructions (DICOM Image Transfer 9215-0024*, DICOM Print 9215-0033*, and
DICOM WorkList 9215-0130*). The release documents also review the DICOM Configuration
application and creation of DICOM entries within that utility. If loading more than one of the
Philips/ADAC DICOM software options, be sure to load them in the following order to prevent
problems: DICOM Image Transfer, DICOM Print, then DICOM WorkList.
Special Notes:
• Be aware, the Image Transfer CD also contains the DICOM Print option, however, DO NOT
load the print option from the Image Transfer CD, part number 9104-0071B. The version of
DICOM Print on this CD is defective. To avoid this issue altogether, ensure that
DICOM Version 4.22 is available at all your sites (latest version as of this writing)
• Also, as a general rule, the DICOM software should first be loaded and configured on the
master of the network, then installed on the clients.
DICOM FILES AND TROUBLESHOOTING TOOLS

Review the following files if any problems occur while performing a DICOM transfer,
imaging to a DICOM formatter, or using the DICOM WorkList software.
The first section includes commands that are used to troubleshoot both DICOM Image
Transfer and Print problems. The second section reviews commands and files specific to the DICOM
Image Transfer configuration, the third section reviews commands and files specific to the DICOM
Print configuration, and the fourth reviews those files specific to the DICOM WorkList configuration.
The bolded entries in the following file represent DICOM systems added by the DICOM
Configuration application.
cat /etc/hosts
192.168.1.3 webview
192.9.200.81 shadow1
192.9.200.20 cyclops
192.9.200.240 atlas1
# DICOM_config added the following hosts
192.9.200.250 dicom_pr_test
# end DICOM_config
192.9.200.55 ep1650
192.9.200.66 codonics_ep1660
192.9.200.52 helios1
192.9.200.251 TransferTest
# end DICOM_config
192.9.200.249 BROKER
# end DICOM_config
The following command demonstrates physical network connectivity. If the ping does not
return a successful response, there is a connectivity problem. The ping command can be followed
either by the IP address of the host system or the hostname.
ping <IP address of DICOM server or printer>

or
ping <hostname> Examples follow:
adac# ping 192.9.200.251

192.9.200.215 is alive
adac# ping TransferTest

TransferTest is alive
If the ping is successful, run the dicom_echo command, shown below. If, however, a
response other than “…is alive” is received, address the connectivity problem. The dicom_echo
command tests the DICOM connection to a remote DICOM server or DICOM printer. It checks the
DICOM configuration parameters to be sure that they are correct. The syntax is as follows:
dicom_echo -c <called AE Title> -t <calling AE Title> -v <node> <port>

where:
-c is followed by the Called AE Title- the title of the remote server or formatter or
peer_server’s_called_AE_title, printer_called_AE_title
-t is followed by the Calling AE Title- the title of the Pegasys, or my_calling_AE_title,
typically ADAC_SCU
-v represents verbose mode
node is the hostname of the remote server or formatter
port is the port number of the remote server or formatter
The parameters needed for the dicom_echo command can be found in either the
dicompeers.cfg file or the dicomprint.cfg file, depending on whether a remote server or a formatter is
being tested.
Example: (Some of the reported information has been removed for space consideration. The
important information is displayed.)
dicom_echo -c cyclops -t ADAC_SCU -v cyclops 104

DUL FSM Table: State: 1 Event: 0
DUL Event: A-ASSOCIATE request (local user)
DUL Action: AE 1 Transport Connect
DUL Event: Transport conn confirmation (local)
DUL Action: AE 2 Send Associate RQ PDU
Constructing Associate RQ PDU
Read PDU HEAD TCP: type: 2, length: 181 (b5)
DUL Event: A-ASSOCIATE-AC PDU (on transport)
DUL Action: AE 3 Associate Confirmation Accept
PDU Type: Associate Request PDU Length: 187
02 00 00 00 00 b5 00 01 00 00 63 79 63 6c 6f 70
. . . . . <extracted text>
Command received: 8030

Echo context: Context
Verification Response
Message ID Responded to: 1
Verification Status: 0000
Echo Response
Message ID Responded To: 1
Data Set Type: 0101
Status: 0000 Successful operation
Class UID: 1.2.840.10008.1.1
DUL Event: A-RELEASE request primitive
DUL Action: AR 1 Send Release RQ
Read PDU HEAD TCP: type: 6, length: 4 (4)
DUL Event: A-RELEASE-RP PDU (on transport)
DUL Action: AR 3 Confirm Release
If “Successful operation” is reported on the “Status” line, shown above in bold, the DICOM
connectivity is confirmed. If one or more of the configuration parameters is incorrect, ‘Successful
operation’ will not be reported. It is necessary to verify the information of the configuration
parameters with the vendor of the remote system or formatter if the dicom_echo fails.
Note: Some devices do not support a handshake back with the dicom_echo command,
even though they may be configured correctly and fully functional. Verify with the vendor
of the remote system or formatter whether or not they support a handshake back from the
dicom_echo command.
The following command reports all the DICOM processes running on the Pegasys System.
There should be one image server process, one inbasket process, and at least one print process for
each configured DICOM formatter.
running DICOM
root 656 1 0 Jan 31 ? 0:00 /usr/adac/pegx/bin/solaris/DICOM_imgserver -c
rogue –p 104
root 653 1 0 Jan 31 ? 0:00 /usr/adac/pegx/bin/solaris/DICOM_inbasketd -
inbasket DICOM_Inbasket_rogue
root 18094 1 0 07:28:23 ? 0:00 /usr/adac/pegx/bin/solaris/DICOM_ printd
root 18096 1 0 07:28:23 ? 0:00 /usr/adac/pegx/bin/solaris/DICOM_
preview_printd
DICOM TRANSFER
The following command reports the software tag and the release version of the Philips/ADAC
DICOM Image Transfer software loaded on the Pegasys system.
dicom_version
Example of output from the command:
| Product Name: Dicom (Transfer and Print)

| Release Version: 4.22
| Part Number: 9104-0071C Rev. A
| Architecture: solaris
| Software Tag: DICOM422R01
| Tag Date: $Date: 2001/02/20 20:25:13 $
| (c) 1999 ADAC Laboratories, Inc.
| Year 2000 Compliant
The release version, part number and software tag will vary depending on the release loaded.
The configuration files for the DICOM software reside in /vol/patients_db/dicom. The following
files should be reviewed:
The dicompeers.cfg file contains configuration information for the Remote Peers system
that is setup under the DICOM configuration utility. It also provides the information needed for the
dicom_echo command when testing a remote server connectivity.
cat /vol/patients_db/dicom/dicompeers.cfg
#
# DICOM Configuration File for Remote Peers
#
# Definition: A remote DICOM peer is a DICOM Application Entity in a remote host
.
# The remote host should be configured to be reachable via TCP/IP.
#
#
# This files contain entries of remote peers. The format of an entry is like the
following.
#
# % Description
# node = remote_host_name (same as in /etc/hosts)
# media_type = DICOM_TCP_IP
# isPegasys = YES | NO
# calledAEtitle = peer_server's_called_AE_title
# max_PDU_size = maximum_PDU_size
# matrix_type = NATIVE_MATRIX | SQUARE_MATRIX | POWER_OF_2_MATRIX | POWER_
OF_2_SQUARE_MATRIX
# max_dimension = size | NATIVE_SIZE
# pixel_mode = depth | NATIVE_DEPTH | BYTE_DEPTH | WORD_DEPTH | BYTE_WORD_
DEPTH
#
#
################################################################################
####
#
#
%DICOM_Transfer
node = TransferTest
port = 104
media_type = DICOM_TCP_IP
isPegasys = NO
max_PDU_size = 16384
timeout = 0
matrix_type = NATIVE_MATRIX
max_dimension = NATIVE_SIZE
pixel_mode = NATIVE_DEPTH
Photometric_Type = MONOCHROME2
%Mitra_RIS
node = BROKER
port = 3320
isPegasys = NO
calledAEtitle = broker
timeout = 0
Photometric_Type = MONOCHROME2
The following file contains the DICOM configuration information for the Local DICOM
Server (the Pegasys).
cat /vol/patients_db/dicom/dicomscp.cfg
################################################################################
####
#
# DICOM Configuration File for Local DICOM Servers
#
# Definition: A local DICOM server is a DICOM Application Entity serving in the
local host.
# It provides services of DICOM service classes, such as Verification and
Storage.
#
#
# This files contain entries of DICOM servers. The format of an entry is like th
e following.
#
# % Description
# media_type = DICOM_TCP_IP
# calledAEtitle = my_called_AE_title
# callingAEtitle = * (or AE1, AE2, ...)
# admitted_hosts = * (or host1, host2, ...)
# source_database = source_database_name
# target_database = target_database_name
# max_PDU_size = maximum_PDU_size
# matrix_type = NATIVE_MATRIX | SQUARE_MATRIX | POWER_OF_2_MATRIX | POWER_
OF_2_SQUARE_MATRIX
# max_dimension = size | NATIVE_SIZE | UNLIMITED_SIZE
# pixel_mode = NATIVE_DEPTH | BYTE_DEPTH | WORD_DEPTH | BYTE_WORD_DEPTH
#
#
# Note: The Called AE title must be unique.
#
################################################################################
####
#
#
%ADAC_SCP@rogue
node = rogue
port = 104
timeout = 0
calledAEtitle = rogue
admitted_AEs = *
admitted_hosts = *
%rogue
node = rogue
port = 104
timeout = 0
calledAEtitle = rogue
admitted_AEs = *
admitted_hosts = *
To better understand remote/local server applications, consider this information:
• If typing on the Pegasys host, the Remote Server will be the computer you are sending
data to. The ‘Called AE Title’ will be the DICOM name of the computer you are sending
to. Your ‘Calling AE Title’ will be “ADAC_SCU” or some name specified by the
vendor. The Remote Server may use the Calling AE Title to know who is "calling" or
trying to communicate to it with DICOM. Some Remote Servers accept data from only a
certain list of "callers". Often, the Remote Server accepts data from all callers - meaning
the Remote Server does not care what the "Calling AE Title" is set to.
• If you are typing on the Pegasys host, your "Local Server" will be this Pegasys computer.
The Pegasys ‘Called AE Title’ will be hostname, where hostname is the hostname of the
Pegasys system. This is the default ‘Called AE Title’ assigned to the Pegasys system
during the software installation. It can be modified if required by the other vendor. The
‘Calling AE Title’ in the local server file is the title of the remote systems that are
allowed access to the Pegasys via DICOM. The default is an “ * “, meaning that the Local
Server (the Pegasys) does not care what the other DICOM system is calling itself.
• You do not need to configure the Local Server if the Pegasys system will only export to
another DICOM system. For printing to a DICOM printer, you do not need to set up a
local Pegasys server.
• It is important to ensure that there is agreement between all the vendor’s configuration
files for the server Called AE title, clients Calling title, TCP/IP port number and the
hostnames. If they do not match on each end then a DICOM association cannot be created
and the data transfers cannot take place.
• All the Pegasys use the same DICOM config files from the shared directory
/vol/patients_db/dicom which is shared from the master. As such there may be limitations
about defining individual titles on a per-Pegasys basis.
• Remember, even though a device is DICOM Spec. 3.0 compliant it does not mean that all
possible DICOM facilities have to be supported, some are push-only clients *Users), some
can be pushed to and will push to you but won’t allow query-retrieve (Conformance
Statements should spell out the supported Service Classes).
• It is always wise to backup the DICOM configuration files to floppy once successfully
configured. Repeat this any time you change and test a new configuration. Insert a
scratch floppy, label disk “DICOM Configuration Backups” with today’s date and open a
Unix Window. Type the following commands:
cd /vol/patients_db/dicom
tar cvf /dev/rfd0c *.cfg
• In the event you have to restore the above backup, insert floppy and type the following in
a Unix Window:
cd /vol/patients_db/dicom
tar xvf /dev/rfd0c
DICOM PRINT
DICOM Print software loaded on the Pegasys system.
dicom_print_version
Example of output from the command
| Product Name: Dicom (Print Only)
| Release Version: 4.22 (or 3.41)
| Part Number: 9104-0069A Rev. A
| Software Tag: DICOM422R01
| Tag Date: $Date: 2001/02/20 20:25:13 $
The configuration files for the DICOM print software also reside in the
/vol/patients_db/dicom directory. The dicomprint.cfg file contains the entries created for a
DICOM formatter through the DICOM Configuration utility. This file contains the information
needed for the dicom_echo command.
cat /vol/patients_db/dicom/dicomprint.cfg
#############################################################################
####
#
# DICOM Configuration File for Remote DICOM Printer Servers
#
# Definition: A DICOM printer is a DICOM Application Entity that performs the SC
P role of
# DICOM print management service class in a remote host.
#
#
# This files contain entries of DICOM printers. The format of an entry is like t
he following.
#
# % Printer_name
# node = printer_host_name (same as in /etc/hosts)
# calledAEtitle = printer_called_AE_title
# format = STANDARD\1,1 | STANDARD\2,2
# film_size_ID = 8INX10IN
# orientation = LANDSCAPE | PORTRAIT
# medium = PAPER | BLUE FILM | CLEAR FILM
# copies = 1 | number
# priority = HIGH | MED | LOW
# transpose = NO | YES
# grayscale = NO | YES
# magnification = REPLICATE | BILINEAR | CUBIC | NONE
# trim = NO | YES
# frequency = 15 | number in secs
# timeout = 30 | number in secs
#
#
# Note: The Printer_name must be unique.#
################################################################################
####
#
#
%DICOM_pr
node = dicom_pr_test
port = 104
film_size_ID = 8INX10IN
medium = CLEAR FILM
copies = 1
priority = MED
transpose = NO
grayscale = YES
reverse_video = NO
trim = NO
config_info =
min_density =
max_density =
smooth =
start_preview = YES
frequency = 5
timeout = 10
Entries for DICOM printers configured on the network are also created in the formatcap,
formatcap_db, and periph.rsc files. Examples of these files displayed in the initial formatter section
earlier in this chapter can be reviewed for the DICOM entries.
DICOM WORKLIST
DICOM WorkList software loaded on the Pegasys system.
dicom_worklist_version
Example of output from the command
| Product Name: Dicom WorkList

| Release Version: 4.21
| Part Number: 9104-0073B Rev. A
| Software Tag: Ver300R26
| Tag Date: $Date: 2000/03/08 10:19:21 $
The RIS (Radiology Information System) is configured as a remote server through the
DICOM Configuration application. The entry for the RIS is created in the dicompeers.cfg file. This
entry provides the information needed for the dicom_echo command. Refer to the DICOM Transfer
section for an example of the dicompeers.cfg file.
The DICOM WorkList option has an additional configuration file that is modified to
customize WorkList functions. The WorkListAtlasServer.cfg file is modified to identify the RIS to
search, time and frequency of downloads from the RIS, parameters for searching the RIS, and the
patient folder management scheme.
The bolded entries in the following file are the fields that are typically modified. Refer to the
Worklist Software Release Document for permissible field entries. The only field that must be
modified is the “pcRISToSearch”. The “Description” given to the RIS within the DICOM
Configuration utility is what is entered for that field.
cat /vol/patients_db/dicom/WorkListAtlasServer.cfg
// $Id: WorkListAtlasServer.cfg,v 1.2 2000/06/07 09:22:57 stuarts Exp $
//
// The purpose of this file is to provide the various DICOM WorkList tools
// with configuration information.
// The values in this file are reasonable though not necessarily optimal
// default values. These defaults should be encoded in the various
// Worklist tools in case the site specific file has no entry for the
// parameter, or in case the site specific file is missing.
// The format of this file is a modified C Like Information File Format

// variable_name = value ;
// where double quotes imply a string, otherwise the value is numeric.
// numeric values can potentially be float or double, but so far, all of
// the numeric values in this file are of type integer.
// The "//" is intended as the comment symbol, as in C++
// The /* */ C style comment symbol should also be supported
// across line breaks, but at a minimum, the // symbol must be ...
// Which databases to search through internally, and in what order

//
// The site could chose to not search the PegDB (all patients always create
// a new exmk unless there is a Worklist entry that satisfies that patient
// matching criteria).
// The site could chose to not search the Worklist table
//
pcDatabasesToSearch = "PegDB, Worklist";
// The names to use when looking for a RIS that is available

// These names map to the names used in dicompeers.cfg
// Within a set bounded by (), only the first RIS available should be used.
// Each of the sets should be searched however, in case there are independent
// RIS's being used (which may not be an ideal way to run a hospital,
// but we need to provide flexibility for the user...
// pcRIStoSearch = "(ris1, ris2);(ris3)";

pcRIStoSearch = "(Mitra_RIS)";
// integer number of days before flushing an unused worklist table entry

iMaximumAgeBeforeDeletion = 7;
// integer number of days before flushing a used worklist table entry

iMaximumUsedEntryAge = 3;
// How Frequently to DownLoad from the RIS, in (integer) hours

iRISDownLoadFrequency = 3;
// Earliest time to Search the RIS (military time)

pcRISDownLoadStartTime = "06:15";
// Latest time to Search the RIS (military time)

pcRISDownLoadStopTime = "20:00";
// Default Constraints for Download of Information from RIS
// By default Constrain downloads to today only (=1)

iDefaultDownloadConstraintToday=1;
// Range of Dates for search

// Note, this will be overridden if
// iDefaultDownloadConstraintToday=1, so the value
// should be 0 for ...ConstraintToday if you want to use a range
// Days Past
iDefaultDownloadConstraintDateRangePast=0;
// Days in the Future
iDefaultDownloadConstraintDateRangeFuture=0;
// Modality Constraint, limit to Nuclear Medicine i.e. NM

pcDefaultDownloadConstraintModality="NM";
// Station Names to constrain search on download

// No constraints to start with, but example might be
//
// pcDefaultDownloadConstraintStationNames="adac,adac1,adac2";
pcDefaultDownloadConstraintStationNames="";
// Procedure Description to constrain search on download

// No constraints to start with
pcDefaultDownloadConstraintProcedureDescriptions="";
// Performing Physicians to constrain search on download

pcDefaultDownloadConstraintPerformingPhysicians="";
// Requesting Services to constrain search on download

pcDefaultDownloadConstraintRequestingServices="";
// Patient Folder Management
// The Procedure Names which are to be kept together within an exmk

// The names must include the two character abbreviation as well
// While there are some initial defaults that ship with the cameras
// the defaults tend to vary depending on camera generation...
// Most sites have customized the names...
pcPatMatchProcedures = "(GS GATED STRESS,GR GATED REST,GD GATED DELAY);(MC MCD,MA
MCDAC)";
// The age in days at which matching procedures are no longer kept together
// for example, a new stress study should not be kept with a rest study
// that was done over 200 days ago...
iPatMatchMaximumAge = 7;
// The method for building the 34 character string which will be passed
// back to the Atlas for presentation on the PC Acquisition Screen.
// The information here should be right justified in that field
// Mapping of values into the display string to be delivered to the acquisition

// system. Mappings should be left adjusted, and space padded on the right.
// Overlapped mappings should be prevented by an intelligent GUI,

// but in general should be handled by providing a rigid sequence of
// mappings in the code, with Accession # being mapped last to ensure
// that it is never overlapped/mapped over.
iAccessionMapStart = 0; // Start with the beginning of the Accession Number

iAcqDispAccessionStart = 0; // Map Accession to start at the 10+1th character
iAcqDispAccessionStop = 17; // Terminate the Accession field map at the 26+1th
iRequestedProcedureDescriptionMapStart = 5; // Start at 5+1th char of descriptio
n
iAcqDispRequestedProcedureDescriptionStart = 0;
iAcqDispRequestedProcedureDescriptionStop = 0;
iRequestedProcedureIDMapStart = 0;
iAcqDispRequestedProcedureIDStart = 0;
iAcqDispRequestedProcedureIDStop = 0;
iPatientNameMapStart = 0;
iAcqDispPatientNameStart = 0;
iAcqDispPatientNameStop = 0;
iPatientIDMapStart = 0;
iAcqDispPatientIDStart = 0;
iAcqDispPatientIDStop = 0;
iPatientDOBMapStart = 0;
iAcqDispPatientDOBStart = 0;
iAcqDispPatientDOBStop = 0;
iPatientGenderMapStart = 0;
iAcqDispPatientGenderStart = 0;
iAcqDispPatientGenderStop = 0;
iPatientPregnancyStatusMapStart = 0;
iAcqDispPatientPregnancyStatusStart = 31;
iAcqDispPatientPregnancyStatusStop = 34;
iPatientMedicalAlertsMapStart = 0;
iAcqDispPatientMedicalAlertsStart = 0;
iAcqDispPatientMedicalAlertsStop = 0;
iImagingServiceReasonMapStart = 0;
iAcqDispImagingServiceReasonStart = 0;
iAcqDispImagingServiceReasonStop = 0;
iImagingServiceCommentsMapStart = 0;
iAcqDispImagingServiceCommentsStart = 0;
iAcqDispImagingServiceCommentsStop = 0;
iRequestedProcedureReasonMapStart = 0;
iAcqDispRequestedProcedureReasonStart = 0;
iAcqDispRequestedProcedureReasonStop = 0;
iScheduledProcedureStartDateMapStart = 0;
iAcqDispScheduledProcedureStartDateStart = 0;
iAcqDispScheduledProcedureStartDateStop = 0;
iScheduledProcedureStepDescMapStart = 0;
iAcqDispScheduledProcedureStepDescStart = 17;
iAcqDispScheduledProcedureStepDescStop = 30;
iScheduledProcedureStepIDMapStart = 0;
iAcqDispScheduledProcedureStepIDStart = 0;
iAcqDispScheduledProcedureStepIDStop = 0;
iScheduledPerformingPhysicianMapStart = 0;
iAcqDispScheduledPerformingPhysicianStart = 0;
iAcqDispScheduledPerformingPhysicianStop = 0;
iReferringPhysicianMapStart = 0;
iAcqDispReferringPhysicianStart = 0;
iAcqDispReferringPhysicianStop = 0;
Important: The pcRISToSearch entry contains the description name given to the RIS
entry in the dicompeers.cfg file.
There are entries in the cron that reflect the settings for the frequency of download from the RIS and
the deletion of aged WorkList entries from the local WorkList database.
The bolded entries below reflect examples of the cron entries for the WorkList option.
crontab -l pegasys
2,17,32,47 * * * * /usr/adac/pegx/scripts/load/rt_keep_running pegasys >

/dev/null 2>&1 # rt_keep_running
33 0,6,12,18 * * * /usr/adac/pegx/scripts/RUNDEL WASTEBASKET 12:00 > /dev/null
2>&1 # WASTEBASKET
#7 0,6,8,10,12,14,16,18 * * * /usr/adac/pegx/scripts/check_dirs > /dev/null 2>&1
# check_dirs
15 6,9,12,15,18 * * * /usr/adac/pegx/scripts/DownloadTodaysWorklist > /dev/null
2>&1
15 6,9,12,15,18 * * * /usr/adac/pegx/scripts/WorkListDeleteAgedEntries.csh >
/dev/null 2>&1
DICOM TROUBLESHOOTING INFORMATION

Various problems can cause errors in DICOM Transfer, Print or WorkList functions. Refer to
the technical tips for specifics. It is important to verify the connectivity and the configuration files
before advancing to any additional troubleshooting steps. Most problems are either network or
configuration problems.
Peg2Peg Software
The Peg2Peg Software option allows for the transfer of data between two Pegasys systems on
different local networks. This option permits for exporting or importing data through either a
network-based or modem-based connection. There are certain system requirements that must be met
before installing the Peg2Peg Transfer software:
PEG2PEG NETWORK CONNECTION
System configurations must be performed on both clusters of Pegasys computers to be
connected prior to installing the Peg2Peg Software. The clusters must be accessible to each other
through a network connection. Use the ping command to validate the TCP/IP (Transmission Control
Protocol/Internet Protocol) connection.
PEG2PEG MODEM CONNECTION

The modem connection requires that the modem be installed, configured and initialized on the
system prior to installing the Peg2Peg option. The modem transfer of Peg2Peg runs on PPP, (Point-
to-Point Protocol; see PPP software section later in this chapter). PPP hostnames for the local and
remote sites must be unique since they will exist in the network hosts files. The Peg2Peg software
must be installed on the system where the modem is installed.
INSTALLATION
The steps for installation depend upon which type of connection will be used, network or
modem. The complete installation procedure can be found in the Pegasys To Pegasys Transfer
Software Release Document (9215-0034*). The general steps for installing the software are listed
below.
Network Connection:
• Load Peg2Peg software
• Configure Peg2Peg software
Modem Connection (PegX):

• Load Morning Star PPP software
• Load PPP Configuration software from floppy
• Configure PPP software
Modem Connection (PegUltra):

NOTE: The PPP software is already incorporated into the base software for the PegUltra systems, so
it is not necessary to load it on the Ultra, but you must on the PegX platform.
• The PPP Configuration software must be loaded on both PegX and PegUltra systems.
• There are two steps to configure the software for modem transfers
o PPP
o Peg2Peg Configuration.
PEG2PEG FILES AND TROUBLESHOOTING TOOLS
The following are files and processes specific to the Peg2Peg software. (The PPP software
used with the modem interface has its own set of files to review when troubleshooting, and is
reviewed in the PPP Software Option section later in this chapter.) The Peg2Peg files and processes
listed here relate to both network and modem connections.
Individual entries must exist in the local master's /etc/hosts and dicompega.cfg files
for each and every one of the targets in the remote Pegasys cluster that have Peg2Peg loaded on
them. You should also be sure that the master of that remote Pegasys cluster has similar info for each
of your local Pegasys units that have Peg2Peg loaded on them. Entries for remote systems
transferring via a network connection appear as regular hostnames. The entries for remote systems
using a modem connection typically start with 'ppp' and are listed with both an "in" and an "out"
extension. Only the "in" flavor will appear in the dicompega.cfg configuration file.
The bolded entries in the following file are those for the Peg2Peg Transfer remote systems:
ypcat hosts
192.168.243.2 ppp243_out
192.168.243.1 ppp243_in
192.168.100.1 ppp100_in
192.168.100.2 ppp100_out
192.9.200.80 adac_pier
Note: The "ypcat hosts" command often displays many duplicated entries on an All-
Ultra network with a Ultra Master. This is normal and due to the method in which the
"makedbm" program generates the maps on the master Pegasys. For large networks, you
might consider filtering out duplicate entries by issuing the following alternative:
"ypcat hosts | sort –u"
The following is the Peg2Peg configuration file. This configuration file stores the
information required for communication between remote Pegasys systems either through a network
or a modem connection.
• cat /vol/patients_db/peg2peg/Ver300/config/dicompega.cfg
#################################################################################
###
#
# Configuration File for Remote Pegasys
#
# Definition: A remote Pegasys is a remote ADAC Pegasys.
# The remote host should be configured to be reachable via TCP/IP.
#
#
# This files contain entries of remote peers. The format of an entry is like the
following.
#
# % Description
# node = remote_host_name (same as in /etc/hosts)
#
#
#################################################################################
###
#
#
%Pierremont
node= adac_pier
%VA Grand Junction

node = ppp100_in
%Wolv
node = ppp243_in
Note: The first entry in the dicompega.cfg file above is an example of an entry created for
a network connection. The last two entries are examples of entries created for a modem
connection. The modem connection entry must be the “_in” node, since this is the
connection interface that is used on the remote system for the dialup connection. The
software obtains the node names from the hosts file entries.
There is an image server process that must be running in order for the Peg2Peg transfers to
work properly. The process is started on install of the software and as a part of the bootup script.
The following command verifies that the process is running.
running PEG
root 517 1 0 Sep 07 ? 0:00 /usr/adac/peg2peg/Ver300/bin/PEGASYS_imgserver
Note: More than one process may be reported with the ‘running’ command. This is the
only one necessary for the Peg2Peg software.
If the process is not running, it can be restarted either by rebooting the system or running the
following command as superuser.
/usr/adac/peg2peg/Ver300/bin/restart_peg2peg
As stated before, the image server process should restart on reboot of the system. If this process fails
to start on reboot, check the following file and verify the entry for the image server and its syntax.
The bolded entries demonstrate what should exist. The positioning of the entry within the file,
depends on what order the software was loaded on the system.
cat /etc/rc.local.adac.end (on PegX)
(The complete file is not listed only the pertinent information included here)
#!/bin/csh -f
#
# $Header: /usr/adac/Repository/pegx/pegx/config/system/rc.local.adac.end.sun413
,v 1.7 1995/10/20 00:30:08 walt Exp $
#
# HANDLE GETTING THE Environment from ADACSetup
set thishost=`hostname`
………
#
# Enable recording of MATADOR detector messages to logfiles...
#
if ( -f /usr/local/matador/bin/logdetector ) then
/usr/local/matador/bin/logdetector cyclopsdet1
/usr/local/matador/bin/logdetector cyclopsdet2
endif
# DICOM_imgserver
if ( -f /usr/adac/pegx/bin/sun413/DICOM_imgserver) then
/usr/adac/pegx/bin/sun413/DICOM_imgserver -c cyclops -p 104 &
endif # end DICOM_imgserver
# DICOM_inbasketd daemon
if ( -f /usr/adac/pegx/bin/sun413/DICOM_inbasketd) then
/usr/adac/pegx/bin/sun413/DICOM_inbasketd
endif # end DICOM_inbasketd
# PEGASYS_imgserver daemon
if ( -f /usr/adac/peg2peg/Ver300/bin/PEGASYS_imgserver) then
/usr/adac/peg2peg/Ver300/bin/PEGASYS_imgserver &
endif # end PEGASYS_imgserver
# DICOM_printd daemon
if ( -f /usr/adac/pegx/bin/sun413/DICOM_printd) then
/usr/adac/pegx/bin/sun413/DICOM_printd
endif # end DICOM_printd
cat /usr/adac/pegx/scripts/adac_local_boot_end.csh (on PegUltra)

(The complete file is not listed only the pertinent information included here)
#!/bin/csh -f
#
# $Header:
/usr/adac/Repository/pegx/pegx/src/pegasys/bin_scripts/adac_local_boot_end.csh,v
1.1.1.2 1998/09/02 03:10:56 softbld Exp $
#
#
# The following sets $HOME and the environment. This script runs during
# boot, and there is no user context available at run time.
#
setenv HOME /
source ${HOME}.cshrc
# HANDLE GETTING THE Environment from ADACSetup
set thishost=`hostname`
. . . . .
#
if ( -x ${CONFIG_PATH}dbadm ) then
echo "Begin database preparation..."
${CONFIG_PATH}dbadm db_prep
echo "End database preparation."
endif
# PEGASYS_imgserver daemon
if ( -f /usr/adac/peg2peg/Ver300/bin/PEGASYS_imgserver) then
/usr/adac/peg2peg/Ver300/bin/PEGASYS_imgserver &
endif # end PEGASYS_imgserver
# DICOM_inbasketd daemon
if ( -f /usr/adac/pegx/bin/solaris/DICOM_inbasketd) then
/usr/adac/pegx/bin/solaris/DICOM_inbasketd
endif # end DICOM_inbasketd
# DICOM_printd daemon
if ( -f /usr/adac/pegx/bin/solaris/DICOM_printd) then
/usr/adac/pegx/bin/solaris/DICOM_printd
endif # end DICOM_printd
# DICOM_imgserver
if ( -f /usr/adac/pegx/bin/solaris/DICOM_imgserver) then
/usr/adac/pegx/bin/solaris/DICOM_imgserver -c rogue -p 104 &
# DICOM_imgserver
if ( -f /usr/adac/pegx/bin/solaris/DICOM_imgserver) then
/usr/adac/pegx/bin/solaris/DICOM_imgserver -c rogue -p 104 &
PEG2PEG TROUBLESHOOTING INFORMATION

Failures with Peg2Peg Transfer typically occur due to configuration, image server, or PPP
problems. Verify that the configuration files are correct and that the appropriate processes are
running for use with the program. Refer to the technical tips for assistance in resolving any
problems. Most modem transfer failures are PPP related, check the PPP software section in this
chapter and the technical tips also.
WebView Software
WebView is a software application that displays Pegasys Nuclear Medicine images on a local
or remote PC. There are actually three configurations of Webview:
• Remote PC uses modem PPP connection directly to the host Pegasys

• Local PC uses TCP/IP connection to the host in Pegasys cluster
• Remote PC uses PPP to hospital terminal pool, then TCP/IP to Pegasys host
(last two require Pegasys cluster with filtered connection to hospital Network)
Be sure when you fill in the Networking Site Surveys that you indicate the correct type of
connection for your site. The application transfers a copy of selected datasets from the Pegasys
WebView server to the PC client and displays them in the selected format. The software also
supports saving the images to the PC hard drive in DICOM or JPEG format.
The WebView package contains 2 software components, one which is loaded on the Pegasys
Server and one which is loaded on the PC Client. The PC Client can be configured to access the
server either through a network or modem connection. The network connection uses TCP/IP. The
modem connection uses PPP, like the Peg2Peg software. The files and commands specific to PPP
will be discussed in the PPP software section later in this chapter.
WEBVIEW INSTALLATION
The system requirements for the Pegasys Server and the PC Client are specified in their
respective release documents, 9215-0123* and 9215-0125*. The steps for installation are dependent
upon the type of connection that will be used, network or modem. The complete installation
procedures can be found in the respective WebView Software Release Documents (Server-9215-
0123*, Client-9215-0125*). The general steps for installing the software are listed below.
Network Connection
• Load WebView Server software on the Pegasys
• Load the WebView Client software on the PC
• Configure the connection in the LAN environment
Modem Connection
• Load WebView Server software on the Pegasys
• Load WebView Client software on the PC
• Configure the connection for using a modem
• Perform any necessary tech tips.
Important: PPP software and Configuration application must be installed on the Pegasys
Server prior to configuring a modem connection entry for the WebView Client. However,
if the software has already been installed (i.e. for Peg2Peg) there is no need to reinstall,
though the configuration still must be performed.
WEBVIEW FILES
The following are files and processes specific to the WebView software. The PPP software
used with the modem interface has its own set of files to review when troubleshooting, and is
reviewed in the PPP Software Option section, later in this chapter. The WebView files and processes
listed here relate to both network and modem connections.
An entry must exist in the hosts file on the Pegasys for every PC Client system configured for
use with the WebView software. The bolded entries in the following file represent those for the
WebView PC Clients.
ypcat hosts
192.168.218.1 ppp218_in
192.168.218.2 ppp218_out
192.168.218.4 WV_PC
192.168.218.3 webview
Important: If the Pegasys Server is a client on the Philips/ADAC network, verify that an
entry for the WebView PC Client also exists in the local /etc/hosts file.
In the example above, ‘webview’ represents a host entry for a modem connection. Note that
the IP address follows the same numerical notation as the local server’s PPP entries (192.168.218).
The WV_PC entry represents a LAN connection and follows the same IP numbering as the network
systems (192.9.200). On the Pegasys Server, there should be at least two http daemons running. The
command to check for these and the output of the command on a PegX and PegUltra are listed below.
running http (PegX)

607 ? IW 0:00 /files/pat/NCSAhttpd/httpd -f /files/pat/NCSAhttpd/conf/htt
611 ? IW 0:00 /files/pat/NCSAhttpd/httpd -f /files/pat/NCSAhttpd/conf/htt
running http (Peg Ultra)

bin 862 856 0 10:52:04 ? 0:00 /opt/NCSAhttpd/httpd -f /opt/NCSAhttpd/conf/httpd
root 856 1 0 10:52:04 ? 0:00 /opt/NCSAhttpd/httpd -f /opt/NCSAhttpd/conf/httpd
The http daemon starts on reboot of the system. If the daemon is not running the following
commands can be issued from a UNIX window to restart the daemon.
PegX (as superuser)
/sbin/sh /etc/rc.local.adac.webview
PegUltra
/etc/init.d/ncsahttpd start
On the PC Client, verify the entry in the hosts file for the Pegasys Server. An entry should
exist regardless of the type of connection, network or modem. From a DOS prompt,
type hosts
# Copyright (c) 1994 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Chicago
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
192.168.50.1 adac # default peg

129.9.107.195 adac2_sg # sutter Gen. ca
192.9.200.10 rogue
Important: If the same client will be interfacing with multiple Pegasys Servers, there
must be a unique hostname and IP for all of the Pegasys systems the client will be
connecting to at the various facilities.
The WebView software is an active X application running under Internet Explorer. Therefore
in order to run WebView an URL entry for the Pegasys Server must be entered and verified. The
proper syntax of the URL is listed below.
http://hostname/WEBVIEW/WebView.htm
(Where hostname is the hostname of the Pegasys Server the PC is connecting to.)
e.g. http://rogue/WEBVIEW/WebView.htm
WEBVIEW TROUBLESHOOTING INFORMATION

When troubleshooting WebView problems, check the following:
• hosts files on the Pegasys and the PC
• validity of the URL
• WebView Server daemon is running
• Network connection with ping command ( if PC is connected to the LAN)
• Modem connection and associated ppp files as described in the following section.
There are various technical tips to assist in determining WebView problems. Please refer to
these for additional information.
PPP Software
PPP (Point to Point Protocol) software allows for a connection between systems not on the
same physical network. It creates a network TCP/IP connection over a modem line. This software is
used by the Peg2Peg and WebView software packages when using a modem connection.
PPP INSTALLATION
There are two components to the PPP software, the actual PPP software and the PPP
Configuration software. The PPP software for the PegX systems is Morningstar PPP and is loaded
from the floppy provided as part of the Peg2Peg package. Unlike the PegX systems, the PPP
software for the PegUltra systems is included in the base Solaris OS software, and does not need to
be installed from a separate floppy. However the PPP Configuration software, also loaded from
floppy, must be installed on both platforms.
The complete installation procedures for the PPP software are provided in the Pegasys To
Pegasys Transfer Software Release Document (9215-0034*). The general steps are listed below.
Prior to loading the PPP software, the modem should be installed and initialized. These installation
steps are required when using the PPP software with the Peg2Peg Transfer software or with the
WebView software.
PegX
• Install PPP Morningstar software
• Install PPP Configuration software
PegUltra
• Install PPP Configuration software
Please note that the PPP Morningstar software and PPP Configuration software are only
provided as a part of the Peg2Peg Transfer software. They are not included in the WebView software
package. It will be necessary to obtain the PPP software to configure the WebView software for a
modem connection if Peg2Peg Transfer software is not already installed at the site.
PPP FILES AND COMMANDS

The following files should be reviewed if any problems occur with Peg2Peg modem transfer
and WebView remote viewing programs. The files specifically relate to the PPP software.
The ppp_config.db file is created by the installation of the PPP Configuration software and is
modified through the Configuration Utility. The initial entries (ppp218) represent the PPP entries for
the local system. The lines in the file beginning with ‘entry’ represent the sites configured in the PPP
Configuration utility on the Call List page. There are incoming and outgoing interfaces for all
systems setup for a connection, with the exception of the WebView entry. WebView only requires a
configured outgoing interface. The PPP handshake takes place between an incoming and an outgoing
interface. If either is missing for a Peg2Peg entry, the PPP connection will fail.
cat /usr/adac/ppp/ppp_config.db
ppp on
incoming ppp218_in 192.168.218.1
outgoing ppp218_out 192.168.218.2
phone 3219597
tty b 38400
timeout 0
debug 2
entry webview 192.168.218.3 * * * 1 WebView
entry ppp243_out 192.168.243.2 ppp243_in 192.168.243.1 5551234 1 Wolverine
entry ppp100_out 192.168.100.2 ppp100_in 192.168.100.1 19995554321 1 VA Grand
Junction
The following files define the dial-out procedure and setup (beginning with an entry in
Systems which indexes an entry in the Devices file, which in turn indexes an entry in the Dialers file)
and are modified by the PPP Configuration utility. The PegX version of the files will be listed first,
followed by the PegUltra version.
Verify the bolded information for correctness. If incorrect, modify the file to correct the
information using either vi or textedit.
PegX PPP Files

tail /etc/ppp/Systems
#
# This connects across a TCP tunnel through an existing IP network
# It expects a line like "ppp 57/tcp ppp" in this system's /etc/services
# and a line like "ppp stream tcp nowait root /usr/etc/pppd pppd nodetach"
# in realhost's /etc/inetd.conf
#
#bogon Any tcp/realhost/ppp
#
# This connects to a system that's protected by a callback modem (in
# this case, a Telebit T3000 with S46=2).
#
#server Any ACU 38400 19071234567 TIMEOUT 60 \
# ENTER\sPASSWORD: my_modem_password\M \
# ENTER\SPASSWORD: my_modem_password\m \
# ogin: my_login_name ssword: my_login_password
ppp243_in Any ACU 38400 5551234 in:--in: ppp word: \qadac_ppp
ppp100_in Any ACU 38400 19995554321 in:--in: ppp word: \qadac_ppp
Note: The entries at the end of the Systems file should match the call list entries
configured under the PPP Configuration utility.
cat /etc/ppp/Devices
#
# /etc/ppp/Devices - PPP devices file
#
# Format:
#
#dialer device speed
#
# dialer: The name of the dialer in Dialers to use
# with this device, or the word "Direct".
#
# device: The name of the device in the /dev directory
# (ttya, cua, rsd0a/0, etc.).
#
# speed: This field is string matched against the speed
# field of entries in the Systems file when the
# Systems device field is set to ACU. Speeds
# must either be valid baud-rate numbers or must
# begin with them (2400, 38400, 19200-PEP, etc.).
adac_modem_b_38400 cua1 38400 crtscts
Important: The letter following the ‘adac_modem_’ string must be the serial port the
modem is configured on. If the entry in the Devices file is incorrect, verify the Local Port
Configuration in the PPP Configuration utility. Verify the entry for the local port
configured within the call list entries is correct, a or b, depending on which serial port the
modem is connected to on the local system.
tail /etc/ppp/Dialers
#
# Use this SmartLink dialer when you can't be sure of the modem's saved
# settings staying constant between sessions
#SMARTLINK_2834 ABORT NO\sCARRIER ABORT ERROR ABORT NO\sDIALTONE \
# ABORT BUSY ABORT NO\sANSWER TIMEOUT 5 "" AT OK-AT&F-OK \
# AT&FL0W1&D3&K3&Y0S0=1S37=17 OK ATDT\T TIMEOUT 60 CONNECT
adac_modem_b_38400 ABORT NO\sCARRIER ABORT NO\sDIALTONE ABORT BUSY \
TIMEOUT 5 "" ATQ2V1 OK-ATQ2V1-OK AT*FL3*SM3S0=1&C1&D2*DE19*EC0*DC1&S0S2=
255*MM0Y1 OK ATDT\T \
TIMEOUT 60 CONNECT
Note: The entry in the Dialers file listed above is the initialization string for a Motorola
modem. The following initialization string would replace the one seen if the modem is a
US Robotics:
adac_modem_b_38400 ABORT NO\sCARRIER ABORT NO\sDIALTONE ABORT BUSY \

TIMEOUT 5 "" ATQ2V1 OK-ATQ2V1-OK ATS2=255S12=255&A0&D2&H1&R2&K1&M4&B1\nA
TDT\T \
TIMEOUT 60 CONNECT
Again, the letter following the ‘adac_modem_’ string must be the serial port the modem is
configured on.
Peg Ultra PPP Files
cat /etc/uucp/Systems
#ident "@(#)Systems 1.5 92/07/14 SMI" /* from SVR4 bnu:Systems 2.4 */
#
# Entries have this format:
#
# Machine-Name Time Type Class Phone Login
#
# Machine-Name node name of the remote machine
# Time day-of-week and time-of-day when you may call
# (e.g., MoTuTh0800-1700). Use "Any" for any day.
# Use "Never" for machines that poll you, but that
# you never call directly.
# Type device type
# Class transfer speed
# Phone phone number (for autodialers) or token (for
# data switches)
# Login login sequence is composed of fields and subfields
# in the format "[expect send] ...". The expect field
# may have subfields in the format "expect[-send-expect]".
#
# Example:
# cuuxb Any ACU 1200 chicago8101242 in:--in: nuucp word: panzer
#
# See the System and Network Administration Manual for details
ppp243_in Any adac_modem_b 38400 5551234 "" P_ZERO in:-\r\n\c-in: ppp word:
adac_ppp
ppp100_in Any adac_modem_b 38400 19995554321 "" P_ZERO in:-\r\n\c-in: ppp word:
adac_ppp
Note: The entries at the end of the Systems file should match the call list entries
configured under the PPP Configuration utility.
tail /etc/uucp/Devices
# ---To use a STREAMS network that conforms to the AT&T Transport Interface
# and that uses the Network Listener Service dial script to negotiate
# for a server:
#
# networkx,eg devicex - - TLIS \D nls
#
#
# ---To use a non-STREAMS network that conforms to the AT&T Transport
# Interface and that uses the Network Listener Service dial script
# to negotiate for a server:
#
# networkx,eg devicex - - TLI \D nls
#
########
#
#
# NOTE: blank lines and lines that begin with a <space>, <tab>, or # are
# ignored.
# protocols can be specified as a comma-subfield of the device type
# either in the Devices file (where device type is field 1)
# or in the Systems file (where it is field 3).
#
########
#
ACU cua/b - Any hayes
Direct cua/b - Any direct
adac_modem_b cua/b - Any adac_modem
tail /etc/uucp/Dialers
##########
# DATAKIT(r) serial port connection script
#
# Commands: Explanation:
# ------------ ---------------------------------------------------
# "" no special character translation table
# "" expect nothing
# \d delay to give some settling time
# TION:--TION: wait for the DESTINATION: prompt, if it does not come
# send a carriage return and wait again.
# \D send the specified token
##########
datakit "" "" \d TION:--TION: \D
adac_modem =,-, "" \dA\pTE1V1X1Q0*FL3*SM3S0=1&C1&D2*DE19*EC0*DC1&S0S2=255*MM0Y
1\r\c OK\r \EATDT\T\r\c CONNECT
Note: The entry in the Dialers file listed above is the initialization string for a Motorola
modem. The following initialization string would replace the one seen if the modem is a
US Robotics:
adac_modem =,-, "" \dA\pTB0E1V1X1Q0S2=255S12=255&A0&D2&H1&R2&K1&M4&B1\r\c OK\r

\EATDT\T\r\c CONNECT
The next two files contain the configured interfaces for PPP. They are created and modified
by the PPP Configuration software.
PegX
cat /etc/ppp/Autostart
pppd 192.168.218.2:192.168.243.1 auto idle 150
pppd 192.168.218.2:192.168.100.1 auto idle 150
PegUltra
cat /etc/asppp.cf
#
# Copyright (c) 1997 by Adac Laboraties, Inc.#
#
ifconfig ipdptp0 plumb ppp218_in down

ifconfig ipdptp1 plumb ppp218_out ppp243_in up
ifconfig ipdptp2 plumb ppp218_out ppp100_in up
defaults
inactivity_timeout 0
ipcp_async_map 0
path
peer_system_name ppp
interface ipdptp*
path
peer_system_name ppp243_in
interface ipdptp1
path
peer_system_name ppp100_in
interface ipdptp2
The following command reports the configured interfaces on the Pegasys system. The PPP interfaces
should be reported as “UP” and “RUNNING”. Examples of outputs from the command on both a
PegX and a PegUltra are displayed.
PegX
ifconfig –a
ether 8:0:20:82:12:f3
du0: flags=51<UP,POINTOPOINT,RUNNING>
inet 192.168.218.2 --> 192.168.243.1 netmask ffffff00
du1: flags=51<UP,POINTOPOINT,RUNNING>
PegUltra
ifconfig -a
ether 8:0:20:9b:2c:eb
ipdptp0: flags=8d0<POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 8232
ether 0:0:0:0:0:0
ipdptp1: flags=8d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 8232
ether 0:0:0:0:0:0
ipdptp2: flags=28d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,UNNUMBERED> mtu 8232
ether 0:0:0:0:0:0
The system where the PPP software is loaded should have a PPP daemon process running. The
following command can be used to check for this process. Example outputs of the command are
listed.
running ppp
< PegX >
28796 ? 5 <2:27 pppd[off (Idle timeout), du0]
192.168.130.2:192.168.55.1 auto idle 150
28798 ? 5 <o:42 pppd[off, du 1] 192.168.130.2:192.168.146.1 auto
idle 150
< Ultra>
root 9893 1 0 Jun29 ? 0:00 /usr/sbin/aspppd -d 1
The PPP activity is captured in log files. The following represent examples of the PPP log files.
PegX
cat /var/adm/pppd.log
6/19- 11:51:18-28800 Morning Star PPP
6/19- 11:51:18-28800 du2: pppd 192.169.130.2:192.168.88.1 auto idle 150
6/19- 16:43:08-28796 tcp 192.168.130.2/3825 -> 192.168.55.1/6104 40 fin
bringup
6/19- 16:43:08-28796 Dialing ppp055_in (cua1 38400 3218302
adac_modem_b_38400)
6/19- 16:43:30-28796 STREAMS module ‘pppframe’ not pushed (Invalid
argument)
6/19- 16:43:33-28796 PPP connected to 192.168.55.1 on du0
6/19- 15:46:04-28796 Disconnected from 192.169.55.1 (Idle timeout)
6/19- 16:46:04-28796 ioctl(cua1, TCFLSH) failed: Inappropriate ioctl for
device
PegUltra
cat /etc/log/asppp.log
13:17:59 Link Manager (9893) started 06/29/00
13:17:59 parse_config_file: Successful configuration
13:21:58 process_ipd_msg: ipdptp6 needs connection
Device Type adac_modem_b wanted
13:23:29 start_ip: IP up on interface ipdptp6, timeout set for 150
seconds
13:25:58 process_ipd_msg: interface ipdptp6 has disconnected
13:25:58 disconnect: disconnected connection from ipdptp6
PPP TROUBLESHOOTING INFORMATION

When troubleshooting PPP problems, whether in connection with Peg2Peg or WebView
software, check the following:
• Verify the PPP configuration file
• Verify the Systems, Devices, and Dialers file
• Make sure the PPP daemon is running
• Verify the configuration interface (ifconfig)
Refer to the technical tips for more information dealing with troubleshooting Peg2Peg and WebView
modem problems.
Shadow
Shadow is a Pegasys application interface that allows PC users to access and run purely X
Windows-based applications (like Autoquant and AutoSpect) on Pegasys workstations and control
these applications and view the graphics on their local PC. The application processes run on the
Pegasys host, but allows the PC video, mouse and keyboard control. Once displayed on the local PC,
interactions with the applications are identical to the standard interaction on the Pegasys console.
The program is very network intensive, requiring up to 32Mbit/sec Ethernet bandwidth for the fastest
and largest beating heart display.
Notes:
• Shadow PC must be configured on the Pegasys network, all Cat5 100bT wiring.
• Shadow cannot run via modem or across a WAN (it is too bandwidth intensive)
• Should try to have one Shadow server per Shadow PC client
• Standard Pegasys applications cannot be displayed by Shadow.
• A PegUltra must be the Shadow server, cluster cannot include any PegX systems.
• Requires full 100 Mbit network throughput between PC and Shadow server.
• PC Minimum OS specs: Win98, Win95 Rev. B, WinNT 4.0 sp 4.0 (not validated for Win2K
or WinME)
SHADOW INSTALLATION
Complete installation instructions and system requirements for both the Pegasys and the PC
are included in the Shadow Release Document (9215-0114*).
SHADOW FILES
Installation of the software on the Pegasys system creates a ‘shadow’ directory under
/vol/patients_db. Within this directory are various files and subdirectories associated with
applications available on this server for use on the Shadow PC.
The full path of the directory created by the Shadow installation:
/vol/patients_db/shadow
The files and subdirectories that exist in the ‘shadow’ directory:
ls –lrt /vol/patients_db/shadow
-rw-rw-rw- 1 pegasys users 591 Apr 13 2000 shadowAppsList.331
-rw-rw-rw- 1 pegasys users 451 Jul 19 2000 shadowAppsList
drwxrwxrwx 2 pegasys other 512 Feb 14 15:48 temp/
drwxrwxrwx 8 root other 512 Feb 14 15:48 RXC/
The shadowAppsList file contains a list of the programs that can be run using Shadow.
This is a generic list and does not represent the programs actually loaded on this Pegasys system.
cat /vol/patients_db/shadow/shadowAppsList
AutoQuant autoquant qca.csh -automatch
AutoSPECTPlus autospect_plus asp.csh
Qgs qgs qgs.csh
View2d vu2d /files/pat/APPS/v23d/run_ws_app vu2d
View3d vu3d /files/pat/APPS/v23d/run_ws_app vu3d
InSPECT inspect ${PROTOCOL_PATH}/inspect.shell
ProSPECT prospect ${PROTOCOL_PATH}/prospect.shell
Image_Fusion image_fusion image_fusion.csh
X-Terminal terminal ${X11HOME}/bin/xterm
CardiaQ cardiaq cardq.csh
When installing the Shadow components on the Pegasys host, the following directory is
created.
/vol/patients_db/shadow/RXC
During installation, the script searches the Pegasys host for the programs listed in the
shadowAppsList file. The matching programs found are displayed for selection. From the programs
displayed, those the customer wishes access to, from the PC, are selected. Once the selection is
completed, additional subdirectories are created on the Pegasys host. Examples are listed below.
ls -lrt /vol/patients_db/shadow/RXC
drwxrwxrwx 2 root other 512 Feb 14 15:48 Qgs/
drwxrwxrwx 2 root other 512 Feb 14 15:48 AutoSPECTPlus/
drwxrwxrwx 2 root other 512 Feb 14 15:48 AutoQuant/
drwxrwxrwx 2 root other 512 Feb 14 15:48 X-Terminal/
drwxrwxrwx 2 root other 512 Feb 14 15:48 Image_Fusion/
drwxrwxrwx 2 root other 512 Feb 14 15:48 CardiaQ/
The subdirectories listed represent the programs the Shadow PC will have access to. Within
each of these directories is a ‘.rxc’ file that is called by the Shadow PC to run the requested program.
An example is listed below.
ls -lrt /vol/patients_db/shadow/RXC/AutoQuant
-rw-rw-rw- 1 root other 288 Feb 14 15:48 rogue.rxc
The contents of the ‘.rxc’ file are shown.
cat /vol/patients_db/shadow/RXC/AutoQuant/rogue.rxc
[RX Connection]
Description=AutoQuant (rogue)
Version=3
Type=1
Temporary=0
AutoDescription=1
Host=192.9.200.40
Method=RLOGIN
ResponseTimeout=10
ReceiveTimeout=2
NeverCloseConnection=1
line1=1,0,login:|Username:,pegasys,0,0
line2=0,0,]|:,(${PEGXSCRIPTS}/shadow_exec autoquant %IP#% &),0,1
Note: ‘rogue.rxc’ is an example name of the file existent under the application directories
for Shadow. The syntax of the filename is hostname.rxc, where hostname is the
name of the Pegasys Shadow server.
The same file appears under each of the application directories. The bolded entries in the
following example represent the fields that will vary between the ‘.rxc’ file under each directory.
cat /vol/patients_db/shadow/RXC/Qgs/rogue.rxc
[RX Connection]
Description=Qgs (rogue)
Version=3
Type=1
Temporary=0
AutoDescription=1
Host=192.9.200.40
Method=RLOGIN
ResponseTimeout=10
ReceiveTimeout=2
line2=0,0,]|:,(${PEGXSCRIPTS}/shadow_exec qgs %IP#% &),0,1
It is possible to have a maximum of two Pegasys Shadow servers on a single network cluster.
If more than one system can act as a Shadow server, there will be an additional ‘.rxc’ file entry for
any given application. The only difference between the ‘.rxc’ file contents, within the same
application directory, will be the ‘Host’ entry and the hostname in parentheses. For example:
ls -lrt /vol/patients_db/shadow/RXC/Qgs/
-rw-rw-rw- 1 root other 276 Feb 14 15:48 rogue.rxc
-rw-rw-rw- 1 root other 276 Feb 23 11:33 storm.rxc
cat /vol/patients_db/shadow/RXC/Qgs/rogue.rxc
[RX Connection]
Description=Qgs (rogue)
Version=3
Type=1
Temporary=0
AutoDescription=1
Host=192.9.200.40
Method=RLOGIN
ResponseTimeout=10
ReceiveTimeout=2
cat /vol/patients_db/shadow/RXC/Qgs/storm.rxc
[RX Connection]
Description=Qgs (storm)
Version=3
Type=1
Temporary=0
AutoDescription=1
Host=192.9.200.10
Method=RLOGIN
ResponseTimeout=10
ReceiveTimeout=2
Similar application directories and ‘.rxc’ files reside on the Shadow PC in the following
directory:
C:\Program Files\ADACLabs\Shadow\
The information in this file on the PC should match the information on the Pegasys server’s
‘.rxc’ file
SHADOW TROUBLESHOOTING INFORMATION

Typically if there are problems with the Shadow program they are either resource or
installation related. As mentioned before the application program runs on the Pegasys server. When
the application is called from the PC a shadow process is started. If the program is terminated
incorrectly on the PC, a phantom shadow process will be left on the Pegasys host and can cause tie
ups of system resources. The following command can be used to find any shadow processes.
running shadow
pegasys 18094 1 0 07:28:23 ? 0:00 /usr/adac/pegx/scripts/shadow_exec
pegasys 18096 1 0 07:40:13 ? 0:00 /usr/adac/pegx/scripts/shadow_exec
If processes, such as those listed, are reported when no active Shadow session is running on
the PC, the phantom processes can be killed.
From the examples:
kill 18094
kill 18096
Important: The correct way to exit the shadow application is to Quit the application from
within the specific program window. For example, if the AutoQuant application is being
run on the Shadow PC, then the QUIT button within the AutoQuant application is used to
kill the Shadow process; do not use the ‘X’ on the Windows border.
It is possible that an application is not available for use on the Shadow PC, even though the
software is installed on the Pegasys server. Typically this is a problem if an application was installed
either after the Shadow software was installed, or simply was not selected when it was installed. In
this case, the Shadow software would have to be reinstalled.
SeeMor
SeeMor software is another medical image viewing program provided by a third party vendor,
Areeda Associates Ltd. It allows for the viewing of medical images, including Pegasys images, on
an Intel-based PC or an Apple MacIntosh. The software is mentioned here for completeness.
SEEMOR INSTALLATION
The third party vendor is responsible for the installation of the software.
SEEMOR FILES
All associated components of the SeeMor software are maintained by the vendor.
SEEMOR TROUBLESHOOTING INFORMATION

No troubleshooting information is provided, since the vendor is responsible for supporting
this product’s components. If any additional information is needed refer to the vendor web site at the
following URL: http://www.areeda.com
Chapter 5: ADAC Network Troubleshooting
Chapter 5 Outline
I. General Information
a. Typical Information Needed
b. Cabling Problems are Generally
c. Software / Network Problems are Generally
II. Flow Charts
a. Network Troubleshooting
b. Hardware Diagnostic
c. Software Diagnostic
d. Network “Sniffing” using Etherfind or Snoop
III. General Guide to Philips/ADAC Network Hardware/Electrical Diagnostics &
Troubleshooting
a. Cabling
b. LAN Test Instruments
c. General Principles
d. Current, Ground Loop Tests
e. Resistance Tests
f. FLUKE DSP-2000 Cable Analyzer
IV. General Guide to Philips/ADAC Network Software Diagnostics
a. Software Troubleshooting Topics
b. WAN Troubleshooting
c. Router / Filtering-Bridge Troubleshooting
d. EMERGENCY_STANDALONE
e. EMERGENCY_RECOVERY
f. Network Role Reconfiguration and Cluster Splitting
g. RESTORE_PEGX
h. Sun Ethernet Interface Diagnostic ( ROM diag )
i. NI5210DG PC Interlan Ethernet diagnostic
j. Linksys PC Ethernet diagnostic
TYPICAL INFORMATION NEEDED BEFORE YOU BEGIN TROUBLESHOOTING
• Location of users machine, contact name and number.
• Network/Machine configuration, types of units, network map, etc.
• Workstation Version, PC version, Acquisition or Option PC?
• What happened, time and date, can it be repeated?
• What were the error messages? Where were they displayed?
• Do other users experience the same problem?
• Were there any recent changes to the computer or network? Also ask Site IT.
• What solutions have been tried to solve the problem? (reset unit, power-off/on, replacing
hardware, root login)
• Did this work before or is this something new?
CABLING PROBLEMS ARE GENERALLY CAUSED BY

• connectors and terminators
• crimps, splices, bends
• noise, voltages and ground loops
• short and open circuits
• exceeding cable and/or workstation limits
SOFTWARE / NETWORK PROBLEMS ARE GENERALLY CAUSED BY
• Not all units where connected to the network and booted up when the new unit or peripherals
where added to the network
• Incorrectly configured network (Software and/or Hardware)
• Messages causing file system full issues (messages, mail and log files)
• Traffic from site network causing acquisition problems
• Network equipment going out causing Giant packets or collisions
Important: The following flow charts are concise examples they do not have complete
details on running commands. Later in this chapter are examples and details, on the
commands mentioned in the flow charts.
NETWORK TROUBLESHOOTING FLOW CHART
System Check
Check Plug in and

System is No turn on System
it on?
Check to see if other units
have the same problem
with target unit
Yes
in a unix window
"ping" IP number of
target
Only this Check SW
unit fails Yes configuration of
with target this unit
Did ping Check HW, Go to HW

No A
pass? Diagnostic section
No
Check SW Check SW
Yes
configuration of configuration of
target unit Master unit
in a unix window ping

host name of target
Did ping No Check SW, Go to SW

B
pass? Diagnostic section
Yes
HARDWARE DIAGNOSTIC FLOW CHART
Cat 5 Twisted Pair. 10Base- 10 Base 2, Thinnet

Reseat cable: No 2, Thin- Yes Reseat Network cables,
Both ends Net? All BNC, "Ts", Barrels.
Check cross over

Cable and/or Port Look for bends,
frayed cables &
bad crimps
No Change
Green
link LED No
on hub?
Cycle power
Hub/Switch
Check Ethernet All
No Change BNC cable: Yes units
Yes
Ohm out cable fail?
Swap with good

Try pinging from RJ-45 cable
No
other systems to
same target No Change
system If > 25ohms look
for an open in e-net
cable Is this a
Swap with good
PC ?
Hub/Switch
Yes
No Change
Only this Swap with good If < 25ohms look

Yes Test PC Ethernet
system motherboard or for a short in e-net
No
Card
fails? network card cable ( this chapter )
If PC, run board test

No
If Sun, run port test Check master of Check Transceiver

( this chapter ) network or E-net Adaptor
Only 1
Check master of
Segment No B
network
Bad?
Test Pegasys Ethernet

Replace Port from ok prompt
Yes Swap Ports or ( this chapter )
Switch/Hub for
Swap Cable
bad segment
SOFTWARE DIAGNOSTIC FLOW CHART
Check routing tables

netstat -?
Ask if network Is this a Use
configuration changed PegX Yes etherfind
unit? command
Check ARP tables

arp -a
No
Make sure all Pegasys C
were up during change
Check network Is this an

connectivity/speed Ultra or Use snoop
nfsstat Atlas
Yes
command
Check NIS maps with unit?
ypcat command
No
Check Logs for C
abnormal messages
Check up time
Not an adac unit.
use rup command
Check messages for

network traffic issues
Check netmask values

Check information
ifconfig -a
against past history
Possible
need for Yes
network
Check swap space usage filtering? Ask IT about Site
pstat / swap router, switch, etc.
No
Network "Sniffing with etherfind & snoop"
Check logs for Time

frame between
suspect messages
Calculate timeframe
window to capture
packets in Unix Shell
Unit
PegX Solaris
type?
Run for specific time frame

Run for specific time frame
snoop -o zsu.dat
etherfind -t -ip > zsx1.txt
snoop -t a -i zsu.dat > zsu1.txt
etherfind -t -v -ip > zsx2.txt
snoop -t a -V -i zsu.dat > zsu2.txt
etherfind -t -v -x -ip > zsx3.txt
snoop -t a -v -i zsu.dat > zsu3.txt
Note:(different views of different time
Note:(different views of same time
slices)
slice)
Check for other vendor Check for other vendor

Packets, (-apple, -decnet, Packets, (apple, decnet,
-broadcast) broadcast)
Check for tftp, giant Check for tftp, giant

packet, or other errors packet, or other errors
Examine output collected wit h Examine output collected

etherfind and consult with Site with snoop and consult with
IT and/or Adac Support Site IT and/or Adac Support
General Guide to ADAC Network Hardware
ELECTRICAL DIAGNOSTICS & TROUBLESHOOTING

In LAN's we deal with voltages (electrical signals), which are generally very small (less than
5.0VDC p-p). The differences between no signal and signal can be less than 1.0 volts. In fact, noise
voltages can even be interpreted as signals. This is one reason why the cabling media must be
protected from noise sources and free from induced noise voltages.
Because a LAN comprises many components, its often difficult to decide where to start
finding the problem. However, there are a few basic rules we can learn which will point us in the
right direction, with the aim of minimizing downtime. Information is vital for troubleshooting. You
need access to details about:
• cable types - (thinnet, thicknet, RJ-45, etc.)
• network layout, location of terminators, hubs, routers, repeaters etc
• workstation location
• workstation information (system name, address, software configurations)
• network interface card types, settings
• past history (recent changes, is fault repeatable)
CABLING
Cable related problems generate 90% of all LAN faults. Needless to say, cabling performed
at or before installation time should be certified in writing, along with test results detailing the
measurements taken. Any configuration work Philips/ADAC does also needs to be incorporated into
the network design drawings. The major problems associated with cables are:
• extraneous voltages, noise, ground loops
• excessive cable lengths (lets add just one more workstation)
• poor termination's, connectors
• wrong type of cable
• incorrectly installed to begin with
There are restrictions on cable types, distances and number of workstations attached.
Thin Ethernet (coax)
• 30 max Taps/Segment
• .5 meters minimum between taps
• 185 meters per cable segment
• 5 max node segments, (4 repeaters), ( 3 segments contain users )
• See 5-4-3 rule in ‘Network Hardware Connectivity Chapter’.
• Use RG-58AU cable (50 ohms)
• 50 ohm terminator on each end of the cable, only one side of which is earthed
• On older PegX systems check Back panel BNC coupler. short to chassis or loose
• each “T” connector plugs directly into a network card installed in a PC or a Transceiver.
Never place a Barrel into the Bottom of the “T” connector.
Note: Thin Ethernet systems use a BUS topology. This describes the manner in which the
various hardware equipment of the LAN is interconnected.
• each end of the Lan backbone is terminated in 50 ohms
• connections to systems are made via T-connectors
• each workstation is attached to a single cable thread ( usually Transceiver or NIC)
• signals are received by all workstations ( Shared Media )
However, bus systems do have drawbacks,

• a cable fault will take down the entire LAN
• a faulty workstation can take down the entire LAN
• there are limits on the number of workstations
• there are limits on the length of cable
• workstations must be a minimum distance apart
Bus Topology DO'S

• use a single cable type (RG58AU)
• 50 ohm T-connectors from a single supplier
• ground the coax cable only at one end
• keep the cable away from noise sources
• observe cable and workstation limits
Bus Topology DONT'S

• mix different cable types (RJ-59) and (RJ-58)
• mix 75 ohm and 50 ohm terminators
• solder connectors
• run cable near power cables, or air conditioning units, or lighting
• earth ground the coax cable in more than one place
• exceed cable distances or workstation limits
• bend or damage the coax cable
• run spurs or drop cables from a ‘T’ connector
LAN TEST INSTRUMENTS

The basic instruments for fault finding are
• multimeter (resistance, continuity and voltage) suitable when the network is not alive, hard to
do on site but preferable.
• time domain reflectometer TDR
• visual inspection (condition of cables, port link lights, loose connections)
• software diagnostics
• Fluke DSP-2000 Wire Tester
Where do you start?

• is the entire LAN down, all users affected
o check cable, connectors, measure resistance
o check power to external hubs, switches, routers
o check to see if server is running
• some users affected
o check to see if PC can boot past NFS
o issue ping and ypcat commands from each unit
o see examples of ping and ypcat in software section of this procedure
o run NIC diagnostics
o any recent changes?
Any other problems are generally configuration faults, particularly in the way in which the
network has been configured or managed. These are problems like
• inability to run certain applications

• can't access certain files or directories
Often problems are sporadic and intermittent in nature. Faults can be linked to external
activity (the cable deriving noise voltages via lift motors etc). With intermittent faults, it is important
to obtain information about
• which users noticed it first

• what were they doing when it failed
• has this happened before
• does it happen at the same time every day
• is it repeatable
• is there any difference between this and the last time (if there was one)
The trouble-shooter must know the hardware and software configurations of the various
workstations and servers on the network. These details should be filled out and kept in folders.
Included should be cable layouts, access points, cable distances, workstation locations etc. Remember
that INFORMATION is the key. The more you know about the system, the easier your job will be.
We always recommend to any Installer or FSE that the first thing they do is fully document
the entire LAN, both software and hardware and leave a copy on site. Always update the drawings
and information whenever changes are made or noticed.
CATEGORIZING LAN PROBLEMS

HARDWARE
• Cabling, Connectors, Cable type, Switches, Hubs
• Workstations, PC’s, Acquisition units, NIC and peripherals, etc
• Servers
• Bridges/Routers
• Printers
• Power Supply
SOFTWARE
• Workstation shell
• Application Software
• Incorrect Configurations
• Access rights, drive mappings
• Data Integrity, backups
CABLING PROBLEMS ARE GENERALLY

• connectors and terminators
• crimps, splices, bends
• noise, voltages and ground loops
• exceeding cable and workstation limits
BASIC TROUBLESHOOTING HARDWARE TOOLS TO USE
• Rx monitor devices
º sometimes the problem is the environment, heat and/or power issues
º recommend site put all external hubs, switches and routers on ups
• ohm-meter
º tests resistance of cable, presence of terminators, open and short circuits
º limited use on live network
• time domain reflectometer
º tests for cable imperfections, shorts and open circuits, impedance mismatches
• volt-meter
º tests for voltage, ground loops, noise voltages, spikes
º tests for voltage, -1.7v on Ethernet means streaming NIC
CABLE TROUBLESHOOTING STRATEGY

• Divide and conquer. Split the cable segment in half, and take a measurement on both halves.
This should isolate the fault into one half. Repeat the process till the fault is found.
GENERAL PRINCIPLES
• know the cable type and characteristics
• know the cabling layout/scheme, access points and numbering
• know what to expect for good and bad measurements
• visual inspection is important
• start with what you know is good, isolate the rest
• segment/divide where possible, make one big problem into several smaller ones
VOLTMETER TESTING
The use of a voltmeter in cable testing is restricted, but necessary at times to find unusual faults.
• Voltage tests
These tests can test for the normal or abnormal presence of signal activity on the cable.
Ethernet 802.3 uses the following voltage levels,
o high = -.2 to -.5
o low = -1.6 to -1.9
o carrier sense = -.9 to -1.2
o collision = -1.5 to -1.7
A streaming node (a workstation continuously sending) is easily identified by the voltage present on
the cable, and the Ethernet coax cable is properly grounded on only one end.
• Noise tests
Some of the newer hand held fault tools measure noise levels on the cable. This is the mean
voltage read when there is no network activity. It is best to measure this on a system which is
down and all workstations are turned off.
Sources of noise are
o computer power supplies and motherboards
o power breaker panels and/or mains supplies
o large inductive loads, air conditioning, lift motors
o large transformers
For Ethernet, noise measured should be lower than 0.04v per cable segment.
CURRENT AND GROUND LOOP TESTS

The measurements relate to the difference in ground potentials between two points on the same cable.
Ethernet tries to overcome this problem by specifying that only one end of the cable is to be
grounded, but in practice the shield of the conductor cable gets connected to mains ground or some
nearby metal, the shield may also be open and not grounded on either end. This can create differences
in voltage between the various ground points. As a result, voltage travels down the cable and flows
into the network cards. This either damages the card or causes intermittent faults or errors on the
network.
By inserting the meter into the earth shield, and measuring the current flowing (or voltage
difference), this type of fault is easily identified.
There should be no voltage difference or current measured.
Note: Example from a simple Philips/ADAC network with a BNC from point A to point
B, Measured 7.5v from BNC shield to Hub shield on “A” side and 5.5v from BNC shield
to “thintwist” adapter on “B” side. There was no chassis/earth ground on either end of the
BNC Network. Make sure one end of the Thinnet is connected to chassis ground.
RESISTANCE TESTS
These are the more common tests applied to cabling systems. Resistance tests find the following
faults
• shorts
• open circuits
• missing or faulty terminators
A good Ethernet system has two 50 ohm terminators, one at each end of the cable. These appear in
parallel, thus a good system will measure 25 to 27 ohms, a shorted system less than 25 ohms, an open
circuit or poor connection as greater than 25 to 27 ohms. The tests should be performed on a dead
network (preferably all workstations/servers turned off).
Shorts
A shorted cable will always read less than half the resistance of a single terminator. In the example
below, the meter reads “0.34 ohms” because of the impedence characteristics of the cable itself,
which can never read a perfect 0.00 ohms.
Open circuits, Cable breaks
A cable break or open circuit will always read the value of one terminator (or greater).
Changing the point of measurement will identify in which portion of the cable segment the break
occurs.
Missing or Faulty terminators

If both terminators are missing or faulty, the resistance reading will be very high.
If one of the terminators is missing or faulty, the resistance reading will be the value of one of the
terminators.
Splitting the cable segment at the point of measurement, then taking readings into both sections will
reveal one segment as open (;), the other at 50 ohms.
All connections good, normal network

• A good Ethernet System will measure 25 to 27 ohms.
FLUKE DSP-2000 Cable Analyzer
INTRODUCTION
The FLUKE DSP-2000 Cable Analyzer is a tool that verifies the integrity of network cabling,
be it Twisted-Pair (10bT or 100bT), Thin-net (10b2) or Fiber-Optic (10bFL). These tests are passive
and are to be done on cables that not connected to an active network, or in the case of Thin-net a total
run test may be done if all the computers are turned off.
This kit is available for troubleshooting suspect wiring at sites having networking problems.
You request it be sent to you by sending an E-Mail to Walt Klingenberg
(Walt.Klingenberg@philips.com) or Richard Bell (Richard.Bell@philips.com) with all the pertinent
information. ie. Address to send to, name of FSE, Priority Code, Site Code and any other relevant
information.
There is an extensive, easy-to-understand, users manual included in the carrying case with the
equipment but we will attempt to summarize the facts necessary to test the 10bT and 10b2 cables
commonly used in Philips/ADAC networks.
It works by running tests from the Main Unit to the Smart Remote connected to the far end of
the cable.
The units run on rechargeable batteries, which take about 3.5 hours to fully charge. It is
suggested that you charge them ahead of time so that they are cordless and portable. If unable to
charge them ahead of time then it is possible to run the tests while the units are charging with their
adapters plugged into the wall power.
Although the FLUKE DSP-2000 is capable of storing values for different cables to be printed
out in a report later we will not focus on that capability in this write up.
When you power up each of the units, they perform internal self-tests and let you know if they
pass or fail. If you have a failure, do not use them to analyze the cables at your site. Return it to
Field Service Parts with a big, bold note that the unit needs repair.
Typically when you press the TEST button to start an AUTOTEST you will see the following
message:
WARNING:
THE PREVIOUS TEST RESULTS HAVE NOT BEEN SAVED.
Press SAVE to save results
Press TEST to start.
Since we are not going to collect these readings in memory to form a report, just simply hit the TEST
button again to begin the AUTOTEST.
TESTING TWISTED-PAIR (10BT / 100BT)

• Try to test one length of Twisted-Pair (10bT) at a time if possible.
• When measuring Twisted pair we use the Smart Remote unit. It will help measure Near End
Cross-talk (NEXT) which is the amount of noise that one pair can inflict on a neighboring
pair.
• Be sure that you power on both units before connecting the cables to the Main and Remote
units. Units have protection circuitry that is enabled when its turned on.
• Examine the cable to try to ascertain the characteristics (Cat 5, Cat 4, Cat 3 … sometimes
these are listed as Cat V, Cat IV, Cat III or Level 5, Level 4, Level 3, if you are testing the in-
wall cable from a wall plate to a patch-panel then it’s a safe bet that it was run with Cat 5, but
you should check with the IT Group or Site Facilities to be sure. If the cables are shielded to
reduce cross-talk then the Cable Type will be STP (shielded twisted pair) or ScTP (screened
twisted pair) instead of UTP (unshielded twisted pair) in the selection below.
• Set the selector to the SETUP position and press the Blue Button under the word Choice on
the screen. Then use the Blue Buttons under the words Page Up and Page Down to find the
page with the appropriate Test Standard:
o TIA Cat 5 Channel = In-Wall Cable (w/ punchdowns)
o TIA Cat 5 Basic Link = In-Wall Cable
o 100BASE-TX = Single Cat 5 Cable
o 10BASE-T = Single Cat 4 Cable
o 10BASE-T = Single Cat 3 Cable
• Use Arrow Cursor Keys to highlight the correct one and press the ENTER Key.
• Now use the Arrow Cursor keys to select the appropriate Cable Type and press the ENTER
key
• UTP 100 Ohm Cat 5 = In-Wall Cable (w/ punchdowns)
o UTP 100 Ohm Cat 5 = In-Wall Cable
o UTP 100 Ohm Cat 5 = Single Cat 5 Cable
• Now turn the selector back to the AUTOTEST position.
• Plug the cable to be tested into Cable Test RJ-45 port of the Main Unit and then attach it to
the RJ-45 port of the Smart Remote. (If you are testing a run through a wall you will need to
use the two 2-meter Cat5 test 10bT cables in the kit and attach the Main Unit with one to
Wall Port and the Smart Remote to the correct patch-panel port with the other cable).
• Make sure that the Smart Remote is powered on and has passed its self-test.
• On the Main Unit, press the TEST button (you’ll probably need to press it a second time to
skip the save).
• The test results are shown and you should check if the AUTOTEST is PASS or FAIL.
• If all the tests PASS then the unit will beep once, it will show the word PASS and display the
Headroom value (smallest NEXT margin between any set of pairs). You should note that the
cable is good, label if necessary, move to the next one.
• If one or more of the tests FAIL you will hear three beeps, it will show the word WARNING
and display the suggested problem. You should hit the ENTER button to continue. Now you
will see the word FAIL and the name of the first failed test. Press the Blue Button under the
words “View Result” to see the status of all the tests.
• Use the Arrow Cursor Keys to highlight the test you want to study more and press the ENTER
Key. Typical failures are in the following tests;
o WIRE MAP – short, open, split or reversed pairs, crossed pairs or wires
o Impedance – only valid if cable > 16 ft., shorter cables always pass
o NEXT – measured from Main Unit, shows which pairs exceed limits
o NEXT @ Remote – measured from Smart Remote
(You can go into SINGLE TEST and use the TDX ANALYZER to pinpoint the peak
value and location of the NEXT failures)
Refer to the User’s Guide for more details on interpreting test failures.
• If you have a bad single twisted-pair cable then replace it with one from your stock or if
needed, request an AFM from Tech Support to be able to get one of the appropriate
length and category from a local store that carries networking components (Best
Buy, CompUSA, Radio Shack, Circuit City, Fry’s, etc.)
• If you find a bad infrastructure cable running through the wall back to the patch panel you
should label the port, notify the IT Group or Facilities Group and see if there is an alternate
port that can be actively wired back to the correct equipment.
• When testing a Cross-over cable the AUTOTEST mode will beep three times and show you a
wire-map with 1&2 crossed with 3&6 and it will say FAIL. This is okay, just press the Blue
Button below the words Continue Test. The rest of the testing should complete and it will
beep three times again and say FAIL – WIRE MAP. Press the Blue Button below the words
View Result and examine the results of the rest of the tests. If they all say PASS then your
Cross-over cable is just fine. Press the exit button until you get back to the main AUTOTEST
menu.
TESTING THIN-NET (10B2)

• Try to test on length of Coax RG-58 at a time if possible.
• When measuring Thin-net we do not use the Smart Remote unit.
• Set the selector to the SETUP position and press the Blue Button under the word Choice on
the screen. Then use the Blue Buttons under the words Page Up and Page Down to find the
page with IEEE 10Base2. Use the Arrow Cursor keys to select IEEE 10Base2 and press the
ENTER Key. Use the Arrow Cursor Key to select RG-58 and press the ENTER Key. Now
turn the selector back to the AUTOTEST position.
• Plug the RJ45 to BNC adapter cable into the Main Unit and then attach 10b2 cable to it.
• Make sure that there is a Tee or Barrel on the end of the Coax run.
• Now make sure that there is a 50 Ohm Terminator on the end.
• Press the TEST button (you’ll probably need to press it a second time to skip the save).
• The test results are shown and you should check if the AUTOTEST is PASS or FAIL.
• To PASS the Resistance should be between 48 and 65 Ohms and the Impedance should be
between 42 and 58 Ohms (cables less than 15 ft will always PASS impedance tests).
• Notice there is no length indication given in this test, it will just say NO REFLECTION.
• To get that you need to re-run the AUTOTEST with the 50 Ohm Terminator removed so just
remove the Tee or Barrel and the Terminator.
• Press the TEST button (you’ll probably need to press it a second time to skip the save).
• Your AUTOTEST result will be FAIL since the Resistance is now Open but you will see the
reported cable length (and the maximum limit). You will also be told if the cable is less than
15 feet, so that you know to ignore the Impedance test result.
TESTING FIBER-OPTIC (10BFL)

• The DSP-2000 kit contains a pair of Fiber-Optic light source and measuring units. Since none
our internal parts use this type of cable, we will not detail the testing of it here. That testing
typically should be left to the IT Group or Facilities and there are auxiliary instruction sheets
in the documentation pouch in the kit.
General Guide to Philips/ADAC Network Software Diagnostics
SOFTWARE TROUBLESHOOTING TOPICS

Following are Topics for Pegx (X) followed by Ultra (U) sections:
• verify the NIS maps…they are key (X,U)

• ping (check for connectivity) (X,U)
• ping –s (response time study) (X,U)
• uptime (time since last boot, load avg.) (X,U)
• rup (uptime for all in our domain) (X,U)
• ifconfig -a (health of interfaces and values) (X,U)
• pstat –s (swap space), PegX only ( X , -- )
• swap –s (swap space) , Solaris only ( -- , U )
• netstat -rn (routing tables) (X,U)
• netstat -i (network I/O stats) (X,U)
• arp –a (Ethernet/IP addrs known to us) (X,U)
• nfsstat (NFS stats) (X,U)
• /var/adm/messages (-bootp fill up -giant packets) (X,U)
• etherfind (src/dst study of data packets) -ip, -decnet, -apple –broadcast ( PegX ) ( X , -- )
• etherfind -ip | egrep -v ‘host1|host2|…‘ (find non-local traffic) ( X , -- )
• snoop (src/dst study of data packets) -ip, -decnet, -apple –broadcast ( Solaris ) ( -- , U )
• Real World Example of Snoop & Etherfind usage (X,U)
• Hardware Address Not Found Infotip Summary Steps ( X , U )
• WAN Troubleshooting - Mapping the Topology (X,U)
• WAN Troubleshooting - The expanding ping test (X,U)
• WAN Troubleshooting - ISDN details (X,U)
• WAN Troubleshooting - Beware of Access Lists (X,U)
• WAN Troubleshooting - Security Topics (X,U)
VERIFYING NIS MAPS

In order for the Pegasys cluster to function correctly, the information in the master’s NIS
template files (those in /etc) must be current and accurate. Additionally, the NIS maps generated
from those template files must be synchronized between the master and all the client Pegasys units.
After checking the template files and all the NIS maps you should be able to determine if one or more
units is out of synchronization by having more or less information than expected. You should also
verify when examining the template files, that all the information about devices and peripherals are
accounted for and have not been inadvertently deleted.
• To start off let’s make sure that all the clients are up. In a Unix Window on the master Type:
rup to make sure each peg on the network is up and running. Press ‘Ctrl-c’ to exit rup
command. While you’re at it, look to make sure the master has been up longer than each of
the clients. If that’s not the case, you will need to reboot the offending client, or perhaps the
entire network.
• Use `cat` or `more` to view the master’s template files in the /etc directory (hosts, ethers,
auto.vol, peghosts, systems, ypservers, netmasks, networks). Note: See chapter 6, Network
File Structure, for examples of typical file contents.
• Check to see if the output of `ypcat` of each of the NIS maps (hosts, ethers, auto.vol,
peghosts.byname, systems, ypservers, netmasks, networks) on the master and all clients are
identical. If not, a client was down during some reconfiguration event and missed an update.
For some of the maps you must use `ypcat –k` to see the keyword and value pairs.
REMEMBER: When adding/deleting a Pegasys or adding/deleting a Peripheral you must
have all the Pegasys clients up and running.
Important: When checking the maps on each Pegasys be sure to use the `ypwhich`
command to see which Pegasys is serving up the NIS maps to your current machine. In
the Pre-Solaris days it was common for each Pegasys to be serving up NIS maps to
themselves. Security changes in the NIS tools for Solaris make it difficult to ensure that
configuration, so it is conceivable that an entire cluster has their maps served up by one or
two Pegasys units.
• If you need to grind new NIS maps and push them out to all the slave servers, fix any missing
or erroneous information in the master’s template files. Then, on the master, as superuser, do
the following:
cd /var/yp
/bin/rm -f *.time
make (you may need to use /usr/ccs/bin/make on a Solaris unit)
See tech tips about updating NIS maps for more information.
Cross-Binding with Multiple Masters in LAN/WAN
Important: When you have Ultras in a cluster that is Custom Networked (especially
when there are multiple Pegasys clusters) it is possible that old and erroneous NIS maps
are being served up by the Ultras. This does not apply when you have only one Pegasys
cluster using the standard hostname, domainname and IP addressing scheme. When the
Ultra is custom networked and put in to a new NIS domain, the old NIS domain (typically
YP.pegasys) information is not eradicated. The Solaris OS has the ability to serve up
maps for multiple domains, as long as the files are found in the right locations. To identify
if you have these old domainname files on an Ultra:
cd /var/yp
domainname (to see what your running NIS domain name is)
ls (check for old domain name directories like YP.pegasys)
If you have any (let’s call them olddomain) then do the following:
/bin/rm –rf olddomain

cd /var/yp/binding
/bin/rm –rf olddomain
cd /var/yp
vi aliases (delete the line with the olddomain name in it)
Do this on each Ultra system and then reboot the entire cluster containing the Ultra. Then
reboot the other Pegasys cluster, if there is one, to ensure that there is no NIS cross-binding going on.
PegX Network Software Diagnostics
Note: The following are examples only. Your output will be different according to your
network size, name, and configuration.
UNIX COMMAND-LINE DIAGNOSTICS

ping & ping -s
( ping uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP
ECHO_RESPONSE from a host or gateway. ( See if Unit on network Response to a request )
-s packetsize; Specifies the number of data bytes to be sent. The default is 56, which translates
into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. Very low level
handshaking between two interfaces, no guarantee of compatibility between protocols at upper level).
Check to see if system will respond.
-s option, Check for packet lose and turn around time; Should be between 0-3 ms for a SUN system,
and 30-45 ms for PC system.
PEGASYS@adac2:#[11] ping adac3
adac3 is alive
PEGASYS@adac:#[2] ping -s adac4

PING adac4: 56 data bytes
64 bytes from adac4 (191.11.60.41): icmp_seq=0. time=2. ms
64 bytes from adac4 (191.11.60.41): icmp_seq=1. time=1. ms
Press ‘Ctrl-c’ to exit ping –s
----adac4 PING Statistics----

2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/1/2
uptime & rup

( uptime gives a one line display of the following information. The current time, how long
the system has been running, how many users are currently logged on, and the system load averages
for the past 1, 5, and 15 minutes.
rup displays a summary of the current system status of a particular host or all hosts on the
local network. The output shows the current time of day, how long the system has been up, and the
load averages. The load average numbers give the number of jobs in the run queue averaged over 1,
5 and 15 minutes ) Check if master has been up longer than clients, if not reboot clients
PEGASYS@adac2:#[1] uptime
4:05am up 9 days, 13:16, 1 user, load average: 0.41, 0.10, 0.03
PEGASYS@adac2:#[2] rup
adac3 up 9 days, 16:18, load average: 1.73, 1.92, 1.95
adac up 9 days, 16:21, load average: 0.04, 0.00, 0.00
Press ‘Ctrl-c’ to exit rup
ifconfig -a
( ifconfig is used to configure the kernel-resident network interfaces. It is used at boot time
to set up interfaces as necessary. After that, it is usually only needed when debugging or when
system tuning is needed.
If no arguments are given, ifconfig displays the status of the currently active interfaces. If a
single interface argument is given, it displays the status of the given interface only; if a single -a
argument is given, it displays the status of all interfaces, even those that are down. Otherwise, it
configures an interface )
• Check the netmask value, especially on a custom configuration. Output is Hex “ff = 255”
Example shown is a system with a second Ethernet card: le1:
PEGASYS@adac:#[4] ifconfig -a
Example is a Peg-Tower with MCD ( Note: hme0 maybe be0 with Older E-Net Card):
PEGASYS@adac2:#[1] ifconfig -a
le0: flags=40<RUNNING>
hme0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
pstat -s
( pstat interprets the contents of the various system tables and writes it to standard output.
-s Displays information about the swap or paging space usage )
PEGASYS@adac:#[10] pstat -s
13648k allocated + 2588k reserved = 16236k used, 78760k available
netstat -rn
( The netstat command symbolically displays the contents of various network-related data structures.
There are a number of output formats, depending on the options for the information presented.
-r Show the routing tables
-n Show network addresses as numbers (normally netstat interprets addresses and attempts to
display them symbolically )
PEGASYS@adac:#[7] netstat -rn
Routing tables
Destination Gateway Flags Refcnt Use Interface
127.0.0.1 127.0.0.1 UH 5 1087539 lo0
default 191.11.60.1 UG 1 335148 le1
192.168.1.0 192.168.1.1 U 42 3386970 le0
191.11.60.0 191.11.60.24 U 0 218542 le1
PEGASYS@adac2:#[2] netstat -rn

Routing tables
Destination Gateway Flags Refcnt Use Interface
127.0.0.1 127.0.0.1 UH 4 423035 lo0
192.168.1.0 192.168.1.20 U 44 3445621 hme0
netstat -i
( -i Show the state of interfaces which have been auto-configured (interfaces statically
configured into a system, but not located at boot time are not shown). If the -a options is also
present, multicast addresses currently in use are shown for each Ethernet interface and for each IP
interface address. Multicast addresses are shown on separate lines following the interface address
with which they are associated )
Check Collision Percentage ( Collis * 100 / Opkts ) > 5% then network may be getting
saturated and subnetting should be considered
PEGASYS@adac:#[8] netstat -i
Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue
le0 1500 sun-ether adac 2232117 445 2135755 1933 1325 0
le1 1500 bi-ether abgate1 2531162 0 553856 0 331 0
lo0 1536 loopback localhost 2354698 0 2354698 0 0 0
PEGASYS@adac2:#[3] netstat -i
be0 1500 sun-ether adac2 3658137 1004 3164156 362 965 0
arp -a
( arp - (address resolution protocol) manipulates the kernel's ARP cache in various ways.
The primary options are clearing an address mapping entry and manually setting up one. For
debugging purposes, the arp program also allows a complete dump of the ARP cache.
-a [hostname], --display [hostname] Shows the entries of the specified hosts. If the hostname
parameter is not used, all entries will be displayed )
Important: If your using arp to see the Ethernet address of a system, ping that target
system first.
PEGASYS@adac2:#[10] arp -a
adac (192.168.1.1) at 8:0:20:75:8a:35
pc_stack21 (192.168.1.21) at 0:a0:c9:1e:53:26
adacdet1 (192.168.1.8) at 8:0:3e:23:da:a2
adacdet2 (192.168.1.9) at 8:0:3e:23:da:c8
adac2det1 (192.168.1.28) at 8:0:3e:23:da:be
adac2det2 (192.168.1.29) at 8:0:3e:23:da:af
adac3 (192.168.1.30) at 8:0:20:75:76:3d
nfsstat
( The nfsstat command displays statistics kept about NFS client and server activity )
Typical output is Server/Client rpc/nfs stats
• if client rpc retrans>5% of client calls…bad
• if badxid ~= retrans..nfs server can’t keepup (not data corruption but server performance)
• if retrans hi but badxid low or zero, then the network is slow or has data corruption, “Giant
Packet”
• You can zero counters with -z as root (unlike netstat which needs a reboot to zero)
• Zero & study trend over time, ‘nfsstat –z’, test different events and monitor with nfsstat
to see if badxid or retrans increase with certain events.
PEGASYS@adac:#[9] nfsstat
Server rpc:
calls badcalls nullrecv badlen xdrcall
1002614 0 0 0 0
Server nfs:
calls badcalls
1002614 10
null getattr setattr root lookup
readlink read
48 0% 58760 5% 632 0% 0 0% 426456 42% 0 0% 442540 44%
wrcache write create remove rename link
symlink
0 0% 55115 5% 5402 0% 3675 0% 1720 0% 0 0% 0 0%
mkdir rmdir readdir fsstat
41 0% 0 0% 3418 0% 4807 0%
Client rpc:
calls badcalls retrans badxid timeout wait newcred timers
614413 2834 0 75 2834 0 0 642
Client nfs:
calls badcalls nclget nclsleep
611576 0 611576 0
null getattr setattr root lookup readlink
read
0 0% 20842 3% 1441 0% 0 0% 68577 11% 432238 70% 85729 14%
wrcache write create remove rename link symlink
0 0% 0 0% 0 0% 1523 0% 0 0% 0 0% 0 0%
0 0% 0 0% 837 0% 389 0%
Client rpc:
calls badcalls retrans badxid timeout wait newcred timers
614413 2834 0 75 2834 0 0 642
Client nfs:
calls badcalls nclget nclsleep
611576 0 611576 0
null getattr setattr root lookup readlink
read
0 0% 20842 3% 1441 0% 0 0% 68577 11% 432238 70% 85729 14%
0 0% 0 0% 0 0% 1523 0% 0 0% 0 0% 0 0%
0 0% 0 0% 837 0% 389 0%
/var/adm/messages
• A system may hang if the “messages” files are very large, also /tmp may have a large amount
of files, especially if it is a print spooler. If the system is a network master it may hang the
entire network
• One culprit is bootp messages…
• Another is bad disk blocks…could be a sign the hard drive is going out
• Yet another is a defective memory module;
Jul 3 07:03:39 adac unix: Multiple Softerrors:

Jul 3 07:03:39 adac unix: Seen 128 Intermittent and 128 Corrected Softerrors
Jul 3 07:03:39 adac unix: from SIMM DIMM3
Jul 3 07:03:39 adac unix: CONSIDER REPLACING THE SIMM.
Jul 3 07:03:39 adac unix: Softerror: Intermittent ECC Memory Error SIMM DIMM3
Jul 3 07:03:39 adac unix: ECC Data Bit 33 was corrected
• Mail spool directory on master /var/spool/mail is supposed to be cleaned weekly by cron, if

full examine the messages for clues as to where else to look. If the root mail file is HUGE,
you might consider copying to /files/pat then purging the original by becoming “su” and
doing a “cp /dev/null /var/spool/mail/root”
• You may see “giant packet” message…a sign of faulty connectors, xcvrs, older DEC systems
• Giant Packet on TCP/IP is > 1500 bytes (compare ATM/FDDI ~= 4500, Token Ring ~=
17000, both require translational routers to put data on a TCP/IP subnet)
• Faulty/old hardware and flaky connections can reduce interpacket gap so that two normal
packets will appear to be one large packet
MONITORING AND DIAGNOSING THE NEED FOR FILTERING USING ETHERFIND

• Study /var/adm/messages files on Peg Tower, with Epic Heads, and Atlas systems to examine
for numerous messages about bootp and tftp. These may be filling up at such a rate as to clog
the root partition and hang the machine.
• On 4.1.3u1 boxes become Superuser ( su, adacsu ) and run etherfind with different arguments
(-broadcast, -decnet, -apple, -ip)
• Look for excessive traffic from sources with IP addresses that are not assigned to our
equipment or to the equipment site communicates with (PACS servers, DICOM printers)
METHODOLOGY FOR USING ETHERFIND

• You cannot capture a “scoop” for multiple analysis reprocessing. Each formatted output is a
frozen look in time.
• Check messages and if errors are repeating in 1-3 minute intervals, then create etherfind files
that will capture events for that amount of time.
• For more detailed information on etherfind use the man pages.
• From a unix window, type “man etherfind”. Here is an excerpt showing the argument
syntax and overview:
PEGASYS@adac:#[1] man etherfind

Reformatting page. Wait... done
ETHERFIND(8C) MAINTENANCE COMMANDS ETHERFIND(8C)
NAME
etherfind - find packets on Ethernet
SYNOPSIS
etherfind [ -d ] [ -n ] [ -p ] [ -r ] [ -t ] [ -u ] [ -v ]
[ -x ] [ -c count ] [ -i interface ] [ -l length ]
expression
AVAILABILITY
This program is available with the Networking software
installation option. Refer to Installing SunOS 4.1 for
information on how to install optional software.
DESCRIPTION
etherfind prints out the information about packets on the
ethernet that match the boolean expression. The short
display, without the -v option, displays only the destina-
tion and src (with port numbers). When an Internet packet
is fragmented into more than one ethernet packet, all frag-
ments except the first are marked with an asterisk. With
the -v option, the display is much more verbose, giving a
trace that is suitable for analyzing many network problems.
You must be root to invoke etherfind.
OPTIONS
-d Print the number of dropped packets. Not necessarily
reliable.
-n Do not convert host addresses and port numbers to

names.
-Press space-bar for next page or ‘Ctrl-c’ to exit
Remember that running etherfind without an interface argument will select the default
interface on the motherboard (le0). To view traffic on another interface (like a 2nd Ethernet
card) then specify that device (etherfind –i le1 or etherfind –i hme0).
-Create files, 1-5 minutes in length, using etherfind and desired switches.
• Change directory
cd /files/pat
• Monitor the messages file to make sure you capture the error and place in the background
tail -f /var/adm/messages &
Note: After gathering data, enter fg to bring back to the foreground and press “Ctrl-c” to exit command.
• Create a high level summary file (standard port dump)

etherfind -t -ip > zsx1.txt
• Create a medium level summary file (port-RPC dump)

etherfind -t -v -ip > zsx2.txt
• Create a low level summary file (hex dump)

etherfind -t -v -x -ip > zsx3.txt
• Try honing in on specific special data types

etherfind -broadcast
etherfind -decnet
etherfind -apple
etherfind
etherfind prints out the information about packets on the Ethernet network
-t Timestamp: precede each packet listing with time value in seconds since the first packet
-v Verbose mode: print out some of the fields of TCP and UDP packets
-x Dump the packet in hex, in addition to the line printed for each packet by default
-ip True if the packet is an IP packet
SUPERUSER@cyclops:#[4] cd /files/pat
Note: Run for predetermined amount of time.
SUPERUSER@cyclops:#[6] tail -f /var/adm/messages &

Note: Observe messages to see when you have captured the log in question.
SUPERUSER@cyclops:#[7] etherfind -t -ip > zsx1.txt

- Press ‘Ctrl-c’ to stop build.
SUPERUSER@cyclops:#[8] etherfind -t -v -ip > zsx2.txt

SUPERUSER@cyclops:#[10] etherfind -t -v -x -ip > zsx3.txt

- After stopping the build of etherfind, press fg , brings the tail of
messages to the foreground. press “ctrl-c” to exit the tail command. If job
is lost find job # by typing the command “running tail” use kill command
to stop job, “kill job#”
To view the output of each file:
HIGH LEVEL ETHERFIND SUMMARY

SUPERUSER@cyclops:#[16] more zsx1.txt
Using interface le0
icmp type
type lnth proto source destination src port dst port
0.00 306 udp wolverine sun-ether route route
2.75 146 udp beast storm 1021 2049
2.75 138 udp storm beast 2049 1021
2.78 146 udp beast storm 1021 2049
2.78 90 udp storm beast 2049 1021
3.46 146 udp beast storm 1021 2049
3.46 90 udp storm beast 2049 1021
MEDIUM LEVEL ETHERFIND SUMMARY

Using interface le0
0.00 TCP from rogue.1023 to cyclops.login seq BA0CBB48, ack 4D1A72CC, window 8760, 1 bytes data
0.14 TCP from rogue.1023 to cyclops.login seq BA0CBB49, ack 4D1A72CC, window 8760, 1 bytes data
0.26 TCP from rogue.1023 to cyclops.login seq BA0CBB4A, ack 4D1A72CD, window 8760, 1 bytes data
2.51 UDP from cyclops.route to sun-ether.route 292 bytes

2.56 TCP from rogue.1023 to cyclops.login seq BA0CBB58, ack 4D1A72DC, window 8760,
2.60 TCP from rogue.1023 to cyclops.login seq BA0CBB58, ack 4D1A72DC, window 8760, 1 bytes data
2.86 TCP from rogue.1023 to cyclops.login seq BA0CBB59, ack 4D1A72DD, window 8760,
2.93 TCP from rogue.1023 to cyclops.login seq BA0CBB59, ack 4D1A72DD, window 8760, 1 bytes data
8.63 UDP from wolverine.route to sun-ether.route 272 bytes

8.92 TCP from rogue.1023 to cyclops.login seq BA0CBB6A, ack 4D1A7505, window 8760,
14.31 UDP from beast.1021 to storm.2049 112 bytes

14.31 UDP from storm.2049 to beast.1021 56 bytes
14.32 UDP from storm.2049 to beast.1021 56 bytes
LOW LEVEL ETHERFIND SUMMARY

Using interface le0
08 00 20 89 eb bb 08 00 20 0f 49 f6 08 00 45 00
00 84 aa 4d 00 00 ff 11 00 99 c0 09 c8 64 c0 09
c8 0a 03 fd 08 01 00 70 00 00 00 0b 52 99 00 00
00 00 00 00 00 02 00 01 86 a3 00 00 00 02 00 00
00 01 00 00 00 01 00 00 00 20 3b 16 59 60 00 00
00 05 62 65 61 73 74 65 6d 70 00 00 00 83 00 00
00 05 00 00 00 01 00 00 00 65 00 00 00 00 00 00
00 00 00 80 00 0f 00 00 00 02 00 0a 00 00 00 00
42 c0 3b 18 dd c4 00 0a 00 00 00 00 42 c0 3b 18
dd c4 ee 68 00 00 00 92 00 00
10.47 TCP from 192.9.200.150.1128 to 192.9.200.85.telnet seq 68F33395, ack

1E09E0D5, window 4096, 1 bytes data
08 00 20 76 cf 1d 08 00 20 1f a9 6d 08 00 45 00
00 29 13 a3 00 00 3c 06 5a 2d c0 09 c8 96 c0 09
c8 55 04 68 00 17 68 f3 33 95 1e 09 e0 d5 50 18
10 00 8a e5 00 00 64 04 52 00 02 03 00 00 00 44
00 00 00 4c
10.49 TCP from 192.9.200.85.telnet to 192.9.200.150.1128 seq 1E09E0D5, ack

68F33396, window 4096,
08 00 20 1f a9 6d 08 00 20 76 cf 1d 08 00 45 00
00 28 45 b8 00 00 3c 06 28 19 c0 09 c8 55 c0 09
c8 96 00 17 04 68 1e 09 e0 d5 68 f3 33 96 50 10
10 00 ee ed 00 00 64 04 52 00 02 03 00 00 00 44
00 00 00 4c
10.71 TCP from 192.9.200.150.1128 to 192.9.200.85.telnet seq 68F33396, ack

1E09E0D5, window 4096, 2 bytes data
08 00 20 76 cf 1d 08 00 20 1f a9 6d 08 00 45 00
00 2a 13 a5 00 00 3c 06 5a 2a c0 09 c8 96 c0 09
c8 55 04 68 00 17 68 f3 33 96 1e 09 e0 d5 50 18
10 00 e1 e3 00 00 0d 00 50 18 10 00 00 00 00 44
00 00 00 4c
( -decnet True if the packet is a DECNET packet)
SUPERUSER@adac:#[4] etherfind -decnet

Using interface le0
icmp type
lnth proto source destination src port dst port
Press ‘Ctrl-c’ to stop command
( -apple True if the packet is an AppleTalk protocol Packet)
SUPERUSER@adac:#[5] etherfind -apple

Using interface le0
icmp type
( -broadcast True if the packet is a broadcast packet)
SUPERUSER@adac:#[6] etherfind -broadcast

Using interface le0
icmp type
SOLARIS Network Software Diagnostics
Note: The following are examples only. Your output will be different according to your network
size, name and configuration.
UNIX COMMAND-LINE DIAGNOSTICS

ping & ping -s
“ping” uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP
ECHO_RESPONSE from a host or gateway. ( See if Unit on network Response to a request )
-s packetsize Specifies the number of data bytes to be sent. The default is 56, which translates into
64 ICMP data bytes when combined with the 8 bytes of ICMP header data) Very Low
level handshaking between two interfaces, no guarantee of compatibility between
protocols at upper level) Check to see if system will respond.
-s Check for any packet lose or slow return time; Time should be between 0-3 ms for a
SUN system, and 30-45 ms for a PC system.
root@rogue:/# ping cyclops

cyclops is alive
root@rogue:/# ping -s cyclops
PING cyclops: 56 data bytes
64 bytes from cyclops (192.9.200.70): icmp_seq=0. time=0. ms
64 bytes from cyclops (192.9.200.70): icmp_seq=1. time=0. ms
Press ‘Ctrl-c’ to stop test
^C
----cyclops PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
uptime & rup

( uptime gives a one line display of the following information. The current time, how long
the system has been running, how many users are currently logged on, and the system load averages
for the past 1, 5, and 15 minutes.
rup displays a summary of the current system status of a particular host or all hosts on the
local network. The output shows the current time of day, how long the system has been up, and the
load averages. The load average numbers give the number of jobs in the run queue averaged over 1,
5 and 15 minutes )
Check if master has been up longer than clients, if not reboot clients
root@rogue:/# uptime
7:33am up 3 day(s), 18:47, 4 users, load average: 0.05, 0.04, 0.04
root@rogue:/# rup
192.9.200.85 up 17 days, 22:16, load average: 1.16, 1.04, 1.01
wolverine up 10 days,
18:07, load average: 0.26, 0.23, 0.00
192.9.200.10 up 2 days,
14:44, load average: 0.32, 0.26, 0.00
cyclops up 2 days,
18:26, load average: 0.40, 0.38, 0.02
192.9.200.15 up 15 days,3 mins, load average: 1.21, 1.20, 1.00
beast up 2 days,
15:50, load average: 0.01, 0.03, 0.00
rogue up 2 days,
18:45, load average: 0.10, 0.05, 0.04
192.9.200.55 up 1 day,18:36, load average: 0.08, 0.04, 0.04
192.9.200.90 up 11 days,1:58, load average: 0.04, 0.06, 0.06
sys_m up 20:39, load average: 0.07, 0.05, 0.05
storm up 2 days, 15:56, load average: 0.16, 0.07, 0.07
Press ‘Ctrl-c’ to exit rup
ifconfig -a
( ifconfig is used to configure the kernel-resident network interfaces. It is used at boot time
to set up interfaces as necessary. After that, it is usually only needed when debugging or when
system tuning is needed.
If no arguments are given, ifconfig displays the status of the currently active interfaces. If a
single interface argument is given, it displays the status of the given interface only; if a single -a
argument is given, it displays the status of all interfaces, even those that are down. Otherwise, it
configures an interface )
Check the netmask value, especially on a custom configuration.
root@rogue:/# ifconfig -a
ether 8:0:20:9b:2c:eb
ipdptp0: flags=8d0<POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 8232
ether 0:0:0:0:0:0
ipdptp1: flags=8d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 8232
ether 0:0:0:0:0:0
swap
(The swap utility provides a method of adding, deleting, and monitoring the system swap
areas used by the memory manager.
-s Print summary information about total swap space usage and availability)
pegasys@rogue:/usr/adac/pegasys# swap -s
total: 46976k bytes allocated + 33424k reserved = 80400k used, 1710144k available
netstat -rn
(The netstat command symbolically displays the contents of various network-related data
structures. There are a number of output formats, depending on the options for the information
presented.
-n Show network addresses as numbers (normally netstat interprets addresses and
attempts to display them symbolically). This option may be used with any of the
display formats.
-r Show the routing tables. When -s is also present, show routing statistics instead. )
root@rogue:/# netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
127.0.0.1 127.0.0.1 UH 0 118 lo0
192.168.3.1 192.9.200.60 UGH 0 0
192.168.32.1 192.9.200.60 UGH 0 0
192.168.243.1 192.168.218.2 UH 2 0 ipdptp1
192.168.100.1 192.168.218.2 UH 2 0 ipdptp2
192.9.200.0 192.9.200.40 U 3 36 hme0
224.0.0.0 192.9.200.40 U 3 0 hme0
netstat -i
( -i Show the state of interfaces which have been auto-configured (interfaces statically
configured into a system, but not located at boot time are not shown). If the -a options is also
present, multicast addresses currently in use are shown for each Ethernet interface and for each IP
interface address. Multicast addresses are shown on separate lines following the interface address
with which they are associated )
Check Collision Percentage ( Collis * 100 / Opkts ) > 5% then network may be getting
saturated and subnetting should be considered
root@rogue:/# netstat -i
hme0 1500 adac-net rogue 84943 0 16867 0 0 0
ipdptp0 8232 0.0.0.0 ppp218_in 0 0 0 0 0 0
ipdptp1 8232 ppp243_in ppp218_out 0 0 0 0 0 0
arp -a
(arp manipulates the kernel's ARP cache in various ways. The primary options are clearing
an address mapping entry and manually setting up one. For debugging purposes, the arp program
also allows a complete dump of the ARP cache.
-a [hostname]
--display [hostname] Shows the entries of the specified hosts. If the hostname parameter is not
used, all entries will be displayed )
Note: If your using arp to see the Ethernet address of a system, ping that target system first to force
ARP to update the table with it’s MAC address.
root@rogue:/# arp -a
Net to Media Table
Device IP Address Mask Flags Phys Addr
------ -------------------- --------------- ----- ---------------
hme0 cyclops 255.255.255.255 08:00:20:75:72:0f
hme0 storm 255.255.255.255 08:00:20:89:eb:bb
hme0 rogue 255.255.255.255 SP 08:00:20:9b:2c:eb
hme0 wolverine 255.255.255.255 08:00:20:82:12:f3
hme0 224.0.0.0 240.0.0.0 SM 01:00:5e:00:00:00
nfsstat
( The nfsstat command displays statistics kept about NFS client and server activity )
• Typical output is Server/Client rpc/nfs stats
• If client rpc retrans>5% of client calls…bad
• if badxid ~= retrans..nfs server can’t keepup (not data corruption but server performance)
• if retrans hi but badxid low or zero, then the network is slow or has data corruption, “Giant
Packet”
• You can zero counters with -z as root (unlike netstat which needs a reboot to zero)
• Zero & study trend over time, ‘nfsstat –z’, test different events and monitor with nfsstat
to see if badxid or retrans increase with a certain events.
root@rogue:/# nfsstat
Server rpc:
Connection oriented:
calls badcalls nullrecv badlen xdrcall dupchecks dupreqs
0 0 0 0 0 0 0
Connectionless:
calls badcalls nullrecv badlen xdrcall dupchecks dupreqs
0 0 0 0 0 0 0
Server nfs:
calls badcalls
0 0
Version 2: (0 calls)
null getattr setattr root lookup readlink read
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0%
null getattr setattr lookup access readlink read
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
write create mkdir symlink mknod remove rmdir
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
rename link readdir readdir+ fsstat fsinfo pathconf
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
commit
0 0%
Server nfs_acl:
null getacl setacl getattr access
0 0% 0 0% 0 0% 0 0% 0 0%
null getacl setacl
0 0% 0 0% 0 0%
Client rpc:
Connection oriented:
calls badcalls badxids timeouts newcreds badverfs timers
0 0 0 0 0 0 0
cantconn nomem interrupts
0 0 0
Connectionless:
calls badcalls retrans badxids timeouts newcreds badverfs
1723 0 0 0 0 0 0
timers nomem cantsend
0 0 0
Client nfs:
calls badcalls clgets cltoomany
0 0 0 0
null getattr setattr root lookup readlink read
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0%
null getattr setattr lookup access readlink read
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
write create mkdir symlink mknod remove rmdir
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
rename link readdir readdir+ fsstat fsinfo pathconf
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
commit
0 0%
Client nfs_acl:
null getacl setacl getattr access
0 0% 0 0% 0 0% 0 0% 0 0%
null getacl setacl
0 0% 0 0% 0 0%
/var/adm/messages
• A system may hang if the “messages” files are very large, also /tmp may have a large
amount of files, especially if it is a print spooler. If the system is a network master it
may hang the entire network
• One culprit is bootp messages…
• Another is bad disk blocks…call in for help
• Yet another is a defective memory module:
Jul 3 07:03:39 adac unix: Multiple Softerrors:
Jul 3 07:03:39 adac unix: Seen 128 Intermittent and 128 Corrected Softerrors
Jul 3 07:03:39 adac unix: from SIMM DIMM3
Jul 3 07:03:39 adac unix: CONSIDER REPLACING THE SIMM.
Jul 3 07:03:39 adac unix: Softerror: Intermittent ECC Memory Error SIMM DIMM3
Jul 3 07:03:39 adac unix: ECC Data Bit 33 was corrected
• Mail spool dir on master /var/spool/mail cleaned weekly by cron, if full examine the
messages for clues as to where else to look
• You may see “giant packet” message…a sign of faulty connectors, xcvrs, older DEC
• Giant Packet on TCP/IP is > 1500 bytes (compare ATM/FDDI ~= 4500, Token Ring
~= 17000, both require translational routers to put data on a TCP/IP subnet)
• Faulty/old hardware and flaky connections can reduce interpacket gap so that two
normal packets will appear to be one large packet
MONITORING AND DIAGNOSING THE NEED FOR FILTERING USING SNOOP

• Study /var/adm/messages files on EPIC and Atlas systems to examine for numerous
messages about bootp and tftp. These may be filling up at such a rate as to clog the
root partition and hang the machine
• On Solaris boxes become Superuser ( su - , adacsu ) and run snoop with different
arguments (broadcast, decnet, apple, ip)
• Look for excessive traffic from sources with IP addresses that are not assigned to
Philips/ADAC equipment or to the equipment site communicates with (PACS servers,
DICOM printers)
SNOOPING HINTS
• It is better to use snoop (available only on a Solaris box) if possible because you can
study one sample in a variety of ways. With etherfind (on SunOS 4.1.3u1) you just
get the ASCII output in one desired format and timestamps are only relative.
• You see a counter of packets while snoop is outputting to the capture file, no counter
with etherfind
• If you know you can hone in on conversations that involve just two machine then use
the “between host1 host2” filter
• If you need to look at an interface other than the default (motherboard), like a 2nd
Ethernet Card, then for snoop you would use “-d hme1” and for etherfind “-i le1” (or
whatever your device names happen to be)
• You might review interesting output with the site IT Group
METHODOLOGY FOR SNOOP

• Check messages and if errors are repeating in 1-5 minute intervals then create snoop
files that can capture time frame with error message.
• For more detailed information on snoop use the man pages. From a unix window,
“man snoop” Here is an excerpt showing the argument syntax and overview.
pegasys@sys_g:/usr/adac/pegasys# man snoop
Reformatting page. Wait... done
snoop(1M) Maintenance Commands snoop(1M)
NAME
snoop - capture and inspect network packets
SYNOPSIS
snoop [ -aCDNPSvV ] [ -t [ r | a | d ] ] [ -c maxcount ]
[ -d device ] [ -i filename ] [ -n filename ]
[ -o filename ] [ -p first [ , last ] ] [ -s snaplen ]
[ - x
offset [ , length ] ]
[ expression ]
AVAILABILITY
SUNWcsu
DESCRIPTION
snoop captures packets from the network and displays their
contents. snoop uses both the network packet filter and
streams buffer modules to provide efficient capture of pack-
ets from the network. Captured packets can be displayed as
they are received, or saved to a file for later inspection.
snoop can display packets in a single-line summary form or

in verbose multi-line forms. In summary form, only the data
pertaining to the highest level protocol is displayed. For
example, an NFS packet will have only NFS information
displayed. The underlying RPC, UDP, IP, and ethernet frame
information is suppressed but can be displayed if either of
the verbose options are chosen.
snoop requires an interactive interface.

-Press space-bar for another page or ‘Ctrl-c’ to exit .
Remember that running snoop without an interface argument will select the default
interface on the motherboard (hme0). To view traffic on another interface (like a 2nd
Ethernet card) then specify that device (snoop –d hme1).
• Gather just a “scoop” of data to study offline, stop it with “ctrl-c”, after running for a
minute or two at the most. Only run longer if you suspect a repetitive pattern signature.
cd /files/pat
Note: Observe messages to see when you have captured the log in question.
tail -f /var/adm/messages &
snoop -o zsu.dat
• After stopping the build of snoop, enter fg , brings the tail of messages to the foreground,
press “ctrl-c” to exit the tail command. If job is lost check by typing the command
“running tail” end job with, “kill job#”
• Create a high level summary file from scoop file (standard packet summary)
snoop -t a -i zsu.dat > zsu1.txt
• Create a medium level summary file from scoop file (packet layer summary)
snoop -t a -V -i zsu.dat > zsu2.txt
• Create a low level summary file from scoop file (packet layer details)
snoop -t a -v -i zsu.dat > zsu3.txt
• Try honing in on specific special data types

snoop broadcast
snoop decnet
snoop apple
EXAMPLE OF SNOOP OUTPUT

Run snoop command for predetermined amount of time.
root@sys_g:/files/pat# tail -f /var/adm/messages &

root@sys_g:/files/pat# snoop -o zsu.dat
Using device /dev/hme (promiscuous mode)
164
Press ‘Ctrl-c’ to exit snoop

Press fg, to bring tail command to foreground.
Press ‘Ctrl-c’ to exit tail command.
EXPAND RAW DATA FILE WITH DIFFERENT LEVEL OF DETAIL INTO NEW FILES
root@sys_g:/files/pat# snoop -t a -i zsu.dat > zsu1.txt
root@sys_g:/files/pat# snoop -t a -V -i zsu.dat > zsu2.txt
root@sys_g:/files/pat# snoop -t a -v -i zsu.dat > zsu3.txt
NOTE: If you add the arguments “-x 0” to that last command you will get a hexadecimal/ASCII
output of each packet along with the other information (this can create an extremely lengthy log file,
especially when image data is involved, so use it only if you need it). Here is what the command
would look like:
root@sys_g:/files/pat# snoop -t a -v –x 0 -i zsu.dat > zsu4.txt
HIGH LEVEL SNOOP SUMMARY

root@sys_g:/files/pat# more zsu1.txt
1 8:12:53.80643 cyclops -> sys_g RLOGIN C port=1023
2 8:12:53.80651 sys_g -> cyclops RLOGIN R port=1023 /dev/hme (promiscuou
3 8:12:53.94298 192.9.200.60 -> sun-ether RIP R (13 destinations)
5 8:12:54.79922 sys_g -> cyclops RLOGIN R port=1023 \r1
7 8:12:54.80639 sys_g -> cyclops RLOGIN R port=1023 \r2 \r3 \r4
25 8:12:59.03047 192.9.200.60 -> (broadcast) ARP C Who is 192.9.200.9, 192.9.200.9 ?
26 8:12:59.03120 192.9.200.60 -> (broadcast) ARP C Who is 192.9.200.8, 192.9.200.8 ?
29 8:13:0.00547 sys_g -> cyclops RLOGIN R port=1023 \r22 \r23 \r24 \r25 \r26
Packet counter decluttering: egrep –v –i ‘rlogin|telnet’ zsu1.txt
Standard naming decluttering: egrep –v ‘adac|stack|odonics’ zsu1.txt
MEDIUM LEVEL SNOOP SUMMARY

________________________________
1 8:12:53.80643 cyclops -> sys_g ETHER Type=0800 (IP), size = 60 bytes
1 8:12:53.80643 cyclops -> sys_g IP D=192.9.200.20 S=192.9.200.70 LEN=40, ID=58099
1 8:12:53.80643 cyclops -> sys_g TCP D=513 S=1023 Ack=2719054441
Seq=2059136137 Len=0 Win=4096
________________________________
2 8:12:53.80651 sys_g -> cyclops ETHER Type=0800 (IP), size = 86 bytes
2 8:12:53.80651 sys_g -> cyclops IP D=192.9.200.70 S=192.9.200.20 LEN=72, ID=45653
2 8:12:53.80651 sys_g -> cyclops TCP D=1023 S=513 Ack=2059136137
Seq=2719054441 Len=32 Win=8760
2 8:12:53.80651 sys_g -> cyclops RLOGIN R port=1023 /dev/hme (promiscuou
________________________________
3 8:12:53.94298 192.9.200.60 -> sun-ether ETHER Type=0800 (IP), size = 306 bytes
3 8:12:53.94298 192.9.200.60 -> sun-ether IP D=192.9.200.0 S=192.9.200.60 LEN=292,
ID=9794
3 8:12:53.94298 192.9.200.60 -> sun-ether UDP D=520 S=520 LEN=272
3 8:12:53.94298 192.9.200.60 -> sun-ether RIP R (13 destinations)
________________________________
Seq=2059136137 Len=0 Win=4096
________________________________
Seq=2719054473 Len=3 Win=8760
________________________________
Seq=2059136137 Len=0 Win=4096
________________________________
Seq=2719054476 Len=9 Win=8760
LOW LEVEL SNOOP SUMMARY

ETHER: ----- Ether Header -----
ETHER:
ETHER: Packet 1 arrived at 8:12:53.80
ETHER: Packet size = 60 bytes
ETHER: Destination = 8:0:20:89:c9:78, Sun
ETHER: Source = 8:0:20:75:72:f, Sun
ETHER: Ethertype = 0800 (IP)
ETHER:
IP: ----- IP Header -----
IP:
IP: Version = 4
IP: Header length = 20 bytes
IP: Type of service = 0x00
IP: xxx. .... = 0 (precedence)
IP: ...0 .... = normal delay
IP: .... 0... = normal throughput
IP: .... .0.. = normal reliability
IP: Total length = 40 bytes
IP: Identification = 58099
IP: Flags = 0x0
IP: .0.. .... = may fragment
IP: ..0. .... = last fragment
IP: Fragment offset = 0 bytes
IP: Time to live = 60 seconds/hops
IP: Protocol = 6 (TCP)
IP: Header checksum = 8b6e
IP: Source address = 192.9.200.70, cyclops
IP: Destination address = 192.9.200.20, sys_g
IP: No options
IP:
TCP: ----- TCP Header -----
TCP:
TCP: Source port = 1023
TCP: Destination port = 513 (RLOGIN)
TCP: Sequence number = 2059136137
TCP: Acknowledgement number = 2719054441
TCP: Data offset = 20 bytes
TCP: Flags = 0x10
LOOKING FOR PARTICULAR TYPES OF TRAFFIC

root@sys_g:/files/pat# snoop decnet
root@sys_g:/files/pat# snoop apple

root@sys_g:/files/pat# snoop broadcast

192.9.200.60 -> sun-ether RIP R (13 destinations)
cyclops -> (broadcast) ARP C Who is 192.9.200.79, 192.9.200.79 ?
cyclops -> (broadcast) ARP C Who is 192.9.200.78, 192.9.200.78 ?
192.9.200.60 -> (broadcast) ARP C Who is 192.9.200.8, 192.9.200.8 ?
192.9.200.60 -> (broadcast) ARP C Who is 192.9.200.9, 192.9.200.9 ?
cyclops -> sun-ether RIP R (14 destinations)
“Real world” example of using snoop & etherfind
PROBLEM & DESCRIPTION

So you have a site that complains their Atlas has locked up. You find that the slash (/)
partition is full and that in /var/adm the messages file is huge. You look at the messages file and see
that there are a lot of messages from the bootpd daemon saying that different hardware addresses
cannot be found. These Ethernet MAC addresses are from units that are not our detector heads or
PCs so they must be coming from exposure we have being hooked up to the hospital network. You
zero out the messages file by doing “cp /dev/null /var/adm/messages”.
You also search for, find and apply the Techtip on “Hardware Address not Found” which has
you adjust one of the settings in the /etc/syslog.conf file to be daemon.warning. You verify that those
“hardware address not found” messages are not accumulating any more and consider the issue closed.
But then, about a week or so later, you get another call complaining about the same thing.
You find that the slash (/) partition is full and that in /var/adm the messages file is huge. You look at
the messages file and see that there are now a lot of messages that look like:
Mar 23 14:37:08 atlas1 tftpd[1746]: tftpd: nak: Transport endpoint is already

connected
Mar 23 14:38:12 atlas1 last message repeated 7 times
connected
connected
So it looks like there is still interactivity from the hospital network interacting with our
processes and generating these errors. So let’s try to trace them out and see who is doing this so we
can go to the IT group and give them at least an Ethernet MAC address (maybe even an IP address)
to track down. Study the messages file and look at the timing cycles. Figure on when we will catch
another event.
In the above example we can see that a cluster of 8 of these “nak” events last for about one
minute and that there is about 10 minutes between the starts of each cluster of 8. So we would want
to do our capture with a one or two minute pad on each end to make sure we capture the event (say
from 15:04 to 15:09). In fact we can use a trick with background processes to view when the event
happens and then we will know exactly when we can end the capture.
USING SNOOP
Important: You should run this in a UNIX Shell (not UNIX window) so the scrolling buffer
does not overfill from activity of the packet counter.
tail –f /var/adm/messages & # The ampersand (&) puts it in background

snoop –o /files/pat/zsu.dat # You’ll see the counter go up while it counts packets
# let this run until the pair of messages happen again
<ctrl-c> # To stop the snoop command
fg # To bring the tail command back into foreground
<ctrl-c> # To stop the tail –f command
now explode the zsu.dat into the three levels of detail files
snoop –t a –i zsu.dat > zsu1.txt

snoop –t a –V –i zsu.dat > zsu2.txt
snoop –t a –v –i zsu.dat > zsu3.txt
Since we know the problem came from the tftp daemon we can do a search for that text string
(ignoring case):
SUPERUSER@storm:#[72] grep -i tftp zsu1.txt

3251 6:36:15.59091 192.9.200.253 -> BROADCAST TFTP Read "network-confg" (octet)
3264 6:36:18.62732 atlas1 -> 192.9.200.253 TFTP Error: file not found
3266 6:36:18.67610 twistercard -> 192.9.200.253 TFTP Error: file not found
3358 6:36:36.69703 192.9.200.253 -> BROADCAST TFTP Read "cisconet.cfg" (octet)
3478 6:36:57.97144 192.9.200.253 -> BROADCAST TFTP Read "adacrtr-confg" (octet)
3584 6:37:18.99743 192.9.200.253 -> BROADCAST TFTP Read "adacrtr.cfg" (octet)
the output is of the form
Packet# Timestamp source host dest host nature of the packet
Now we will do a more of the zsu2.txt file and look at the packet info for the packets
numbered 3251, 3264, 3266. Use the /searchstring search feature of more to skip to where
you want to go but remember that you may have to use the “n” key to skip over places where the
number you are searching for is located within another number… look for packet “3251”
more zsu2.txt <Ret>

# you’ll see a page full of the contents of the file
. . . . .
/3251 <Ret> # remember you may have to use “n” a couple times
________________________________
3251 6:36:15.59091 192.9.200.253 -> BROADCAST ETHER Type=0800 (IP), size = 64
bytes
3251 6:36:15.59091 192.9.200.253 -> BROADCAST IP D=255.255.255.255 S=192.9.2
00.253 LEN=50, ID=0
3251 6:36:15.59091 192.9.200.253 -> BROADCAST UDP D=69 S=8286 LEN=30
. . . . .
________________________________
3264 6:36:18.62732 atlas1 -> 192.9.200.253 ETHER Type=0800 (IP), size = 61
bytes
3264 6:36:18.62732 atlas1 -> 192.9.200.253 IP D=192.9.200.253 S=192.9.200
.240 LEN=47, ID=55081
3264 6:36:18.62732 atlas1 -> 192.9.200.253 UDP D=8286 S=32905 LEN=27
. . . . .
________________________________
3266 6:36:18.67610 twistercard -> 192.9.200.253 ETHER Type=0800 (IP), size = 61
bytes
3266 6:36:18.67610 twistercard -> 192.9.200.253 IP D=192.9.200.253 S=192.9.200
.150 LEN=47, ID=10097
3266 6:36:18.67610 twistercard -> 192.9.200.253 UDP D=8286 S=2370 LEN=27
So we see this unit 192.9.200.253 broadcasting to do a tftp read of a config file and these two
units are answering back that “hey I don’t have the file.” Just to get more info, we will look at the
really detailed explosion of these packets in the zsu3.txt file
more zsu3.txt <Ret>

# you’ll see a page full of the contents of the file
. . . . .
ETHER:
ETHER: Destination = ff:ff:ff:ff:ff:ff, (broadcast)
ETHER: Source = 0:2:b9:71:6f:c0,
ETHER:
IP:
IP: Version = 4
IP: Flags = 0x0
IP: Protocol = 17 (UDP)
IP: Header checksum = 32b4
IP: Source address = 192.9.200.253, 192.9.200.253
IP: Destination address = 255.255.255.255, BROADCAST
IP: No options
IP:
UDP: ----- UDP Header -----
UDP:
UDP: Source port = 8286
UDP: Destination port = 69 (TFTP)
UDP: Length = 30
UDP: Checksum = 0000 (no checksum)
UDP:
TFTP: ----- Trivial File Transfer Protocol -----
TFTP:
TFTP: Opcode = 1 (read request)
TFTP: File name = "network-confg"
TFTP: Transfer mode = octet
. . . . .
ETHER:
ETHER: Destination = 0:2:b9:71:6f:c0,
ETHER: Source = 8:0:20:88:53:1a, Sun
ETHER:
IP:
IP: Version = 4
IP: Flags = 0x4
IP: .1.. .... = do not fragment
IP: Header checksum = 9292
IP: Source address = 192.9.200.240, atlas1
IP: Destination address = 192.9.200.253, 192.9.200.253
IP: No options
IP:
UDP:
UDP: Destination port = 8286
UDP: Length = 27
UDP: Checksum = 0BD8
UDP:
TFTP:
TFTP: Opcode = 5 (error)
TFTP: Error = 1 (file not found)
TFTP: Error string = "File not found"
. . . . .
ETHER:
ETHER: Destination = 0:2:b9:71:6f:c0,
ETHER: Source = 8:0:20:1f:a9:6d, Sun
ETHER:
IP:
IP: Version = 4
IP: Flags = 0x0
IP: Header checksum = 45a6
IP: Source address = 192.9.200.150, twistercard
IP: Destination address = 192.9.200.253, 192.9.200.253
IP: No options
IP:
UDP:
UDP: Destination port = 8286
UDP: Length = 27
UDP: Checksum = 0000 (no checksum)
UDP:
TFTP:
TFTP: Opcode = 5 (error)
TFTP: Error = 1 (file not found)
TFTP: Error string = "File not found"
So we can see from the Source MAC addr of 3251 and the dest addr from packets 3264 and
3266 that the MAC address of the offender is 0:2:b9:71:6f:c0 Or, using all 12 characters
would be 00:02:b9:71:6f:c0
If we look at the first 6 chars and check the Vendor Codes Tables we will see that it is a Cisco
product. For your convenience, these vendor-specific codes are included in Appendix C of this
manual. You can also download a more current table from the web if you have Internet access. Just
enter the phrase “OUI table IEEE” into your favorite Internet search engine.
But hey… lets look at the output of the grep –i tftp zsu.txt1 again. Look at one of
the config files; it names adacrtr-config. We usually name our routers adacrtr (per the
example of the configuration)
EXAMINE AND CORRECT THE ROUTER CONFIGURATION
SUPERUSER@storm:#[77] telnet 192.9.200.253
Trying 192.9.200.253...
Password: adacvt
adacrtr>en
Password: adacsu
adacrtr#sho ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 192.9.200.10 0 0800.2089.ebbb ARPA FastEthernet0/0
Internet 192.9.200.40 2 0800.209b.2ceb ARPA FastEthernet0/0
Internet 192.9.200.70 0 0800.2075.720f ARPA FastEthernet0/0
Internet 192.9.200.150 5 0800.201f.a96d ARPA FastEthernet0/0
Internet 192.9.200.240 0 0800.2088.531a ARPA FastEthernet0/0
Internet 192.9.205.253 - 0002.b971.6fc1 ARPA FastEthernet0/1
Internet 192.9.200.253 - 0002.b971.6fc0 ARPA FastEthernet0/0
adacrtr#
we have verification from the hostname and also from the MAC addr on 0/0 and 0/1
lets look at the configuration for the router
adacrtr#show run
!
version 12.0
service config
!
hostname adacrtr
!
enable secret 5 $1$5nc6$CVmR1g9lGNbG9bBsGBiop.
!
ip subnet-zero
!
!
!
!
ip address 192.9.200.253 255.255.255.0
!
ip address 192.9.205.253 255.255.255.0
!
router rip
network 192.9.200.0
network 192.9.205.0
!
ip classless
no ip http server
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacrtr#
This all looks usual per the config in the example we use except for the service config line. If
we go to http://www.cisco.com/ and look at the technical docs and find the command reference we
see that if this is on the router will do tftp broadcasts looking for config files to load via ftp even
though they have the info in nvram, so we do
adacrtr#conf term
adacrtr(config)#no service config
adacrtr(config)#^Z
adacrtr#
adacrtr#copy running startup
adacrtr#reload
Now we zero out the messages file,
cp /dev/null /var/adm/messages
Reboot and examine and see there are no more tftp nak messages generated. Problem solved!
Note: Sometimes its not a unit on the hospital network, but one of our own. Always
chase it out and gather all data possible to corroborate in multiple ways
USING ETHERFIND
So how would we have done this using “etherfind” on a PegX running SunOS 4.1.3?
Remember that we have to do separate format views of different slices of time with etherfind. We’ll
use the “tail –f” trick again to know when to stop.
tail –f /var/adm/messages &

# The ampersand (&) spawns it in background
etherfind -t –ip > /files/pat/zsx1.txt
# You see counter go up while it counts packets
<ctrl-c> # To stop the etherfind command
PEGASYS@storm:#[11] grep -i tftp zsx1.txt

403.99 64 udp 192.9.200.253 broadcast 8046 tftp
Single line output

Timestamp Bytes Protocol Source Destination TCP/IP-Port Service
We see triples here, the request from the router and then the answer from the two units that they do
not have the file requested (see details from the snoop run above).

etherfind -t -v –ip > /files/pat/zsx2.txt
# Counter goes up while it counts packets
PEGASYS@storm:#[14] grep -i tftp zsx2.txt

520.95 UDP from 192.9.200.253.9651 to broadcast.tftp 30 bytes
single line output … no real additional help over what is in the first file
Timestamp Protocol Source.Port# Dest.servicetype #bytes

etherfind -t -v -x –ip > /files/pat/zsx3.txt
# Counter goes up while it counts packets
PEGASYS@storm:#[16] more zsx3.txt
. . . . .
/tftp
...skipping

ff ff ff ff ff ff 00 02 b9 71 6f c0 08 00 45 00
00 32 00 00 00 00 ff 11 32 b4 c0 09 c8 fd ff ff
ff ff 1d fd 00 45 00 1e 00 00 00 01 6e 65 74 77
6f 72 6b 2d 63 6f 6e 66 67 00 6f 63 74 65 74 00
c8 64 03 77 02 98 ed d4
Multi-line output, first line for the packet is same output as from the previous file but now we
have a hex dump of the packet contents. To decode a bit here, suffice it to know that the first 12
bytes (6 pairs) of characters are a hexadecimal representation of the Ethernet MAC address of the
Destination (since this is a Broadcast it is going to everyone … all F’s) and the next 12 bytes (6 pairs)
are for the Ethernet MAC address of the Source.
So from these outputs we have the IP address of the Source unit and we have also found its
Ethernet MAC address (we can matchup the first 6 digits to see what kind of hardware it is) and we
can go to the IT group to have them help us track down what is going on.
One thing missing here is the easy identification of the name of the config file that was being
broadcasted for. We would have to do a painful decode the byte-pairs from hex to ASCII to try to
get those clues (a true sniffer would be able to show use that easily).
Clearly we are better off trying to debug from an Ultra running Solaris 2.x OS, but if you have
to do it on an all PegX network, then you might find it useful to do a “man ascii” and find the
following table to help in your conversion:
Hexadecimal - Character
| 00 NUL| 01 SOH| 02 STX| 03 ETX| 04 EOT| 05 ENQ| 06 ACK| 07 BEL|
| 08 BS | 09 HT | 0A NL | 0B VT | 0C NP | 0D CR | 0E SO | 0F SI |
| 10 DLE| 11 DC1| 12 DC2| 13 DC3| 14 DC4| 15 NAK| 16 SYN| 17 ETB|
| 18 CAN| 19 EM | 1A SUB| 1B ESC| 1C FS | 1D GS | 1E RS | 1F US |
| 20 SP | 21 ! | 22 " | 23 # | 24 $ | 25 % | 26 & | 27 ' |
| 28 ( | 29 ) | 2A * | 2B + | 2C , | 2D - | 2E . | 2F / |
| 30 0 | 31 1 | 32 2 | 33 3 | 34 4 | 35 5 | 36 6 | 37 7 |
| 38 8 | 39 9 | 3A : | 3B ; | 3C < | 3D = | 3E > | 3F ? |
| 40 @ | 41 A | 42 B | 43 C | 44 D | 45 E | 46 F | 47 G |
| 48 H | 49 I | 4A J | 4B K | 4C L | 4D M | 4E N | 4F O |
| 50 P | 51 Q | 52 R | 53 S | 54 T | 55 U | 56 V | 57 W |
| 58 X | 59 Y | 5A Z | 5B [ | 5C \ | 5D ] | 5E ^ | 5F _ |
| 60 ` | 61 a | 62 b | 63 c | 64 d | 65 e | 66 f | 67 g |
| 68 h | 69 i | 6A j | 6B k | 6C l | 6D m | 6E n | 6F o |
| 70 p | 71 q | 72 r | 73 s | 74 t | 75 u | 76 v | 77 w |
| 78 x | 79 y | 7A z | 7B { | 7C | | 7D } | 7E ~ | 7F DEL|
So using the ASCII conversion chart, starting at 6e out near the end of the third line and continuing
into the fourth we get “network-confg octet” which corresponds to some of the output we saw from
the first of the snoop outputs above. We would have to decode several of these to discover the string
“adacrtr-confg” which gave us our other big corroborating clue that we were dealing with broadcasts
from the Philips/ADAC router.
Remember in our example we determined that the IP address was a device we knew about and were
able to corroborate that we needed to examine that router further to see what the source of the
broadcast might be.
The solution, in this case, to use is to defeat the “service config” from the routers config as shown
above.
HARDWARE ADDRESS NOT FOUND INFOTIP SUMMARY STEPS
• Edit the /etc/syslog.conf file and find the appropriate line

• Solaris:
*.err;kern.debug;daemon.notice;mail.crit;user.none /var/adm/messages
• 4.1.3u1:
*.err;kern.debug;daemon,auth.notice;mail.crit;user.none /var/adm/messages
• Change the daemon.notice entry to daemon.warning on Solaris. (on 4.1.3u1, just change the
word daemon to daemon.warning)
• Get the PID of the syslogd process with ps -ef | grep syslog (use ps -ax | grep
syslog on 4.1.3u1)
• Send it a -HUP signal with kill -HUP <PID>
• Observe the /var/adm/messages file to be sure the messages are not showing up (a few
still may be if they are at warning level or above … this indicates further filtering needed)
WAN Troubleshooting
MAPPING THE TOPOLOGY

• Map out the critical players (Pegasys and Routers); Fill in the /etc/hosts file on the master
with entries for the local and remote routers alongside the remote Pegasys that was added
during the configuration step (then remake YP).
• Consult that drawings or tables you did during the Site Survey where you should have noted
the /etc/defaultrouter values
• Whether they are routers on an Philips/ADAC-only WAN or the gateways (defaultrouters) on
the Hospital Networks, those defaultrouters entries are the ones you want to put in /etc/hosts.
For complex topologies, the IT Group might be able to provide additional midpoint routers to
test against. These might be routers provided by the Line Service Provider (LSP)
THE EXPANDING PING TEST

• Open a Unix Window on a Pegasys at one end of the WAN
• ypcat hosts to see entries for the routers and remote host(s)
• can’t ping local defaultrouter - local LAN problem
• can’t ping remote defaultrouter - LSP router or line problem
• cant ping remote Pegasys unit - remote LAN problem
• With these simple tests you should be able to determine if you need to turn the problem over
to the site and their LSP, or if you perhaps need to be looking for a local LAN problem at the
remote site (perhaps with IT Group help).
• As long as the site has a modem connection you may not even have to travel there at all. It
would help to leave an instruction sheet at the site so they could perform the tests.
ISDN DETAILS
• Sites should request that the ISDN routers (and therefore the lines) to be setup as data-only
and either Bonded (both 64kbps channels act as one) or Bandwidth-on-demand with a low
activation threshold. Either way this should provide for maximum throughput and minimum
transfer time.
• Each router is setup so that packets it receives bound for a remote subnet, will invoke the
dialer to connect with the remote router, which will pass them on to the target unit.
• The routers should be setup with a reasonable idle-timeout value to drop the connection
shortly after a transfer is done in order to realize the cost saving rates of ISDN.
• Look out for latch-up delays. The ISDN link should come up upon assertion from the first
ping and well within the 30 second TCP/IP timeout.
BEWARE OF ACCESS LISTS

• If the routers use access lists to control who can travel through them, you may need to consult
with the IT Group to see if things are configured properly to allow your packets to travel all
the way to the end unit you need to communicate with
• If you are using a Philips/ADAC router as a filtering-bridge with MAC address access lists,
and you are suddenly unable to ping across to the remote destination, you might need to
explore if a MAC address changed due to a motherboard being swapped out. In more
complex situations perhaps a failing gateway router was swapped out; the new one will have
different MAC addresses.
SECURITY TOPICS
• Remember, do not assign passwords to the pegasys account or have different root passwords
on each machine. This causes a lot of the automated functionality of the cluster to become
non-operational (like commit, split, Peg2Peg and others)
• There is no individual access control for Peg2Peg between clusters. You can make a Pegasys
receive-only by removing the Import and Export items off the rootmenu or you can make one
send-only by just removing Import.
• We are still waiting for Engineering to address full password protection and additional
security in a future release (HIPAA requirement may force this to be sooner than later).
Router/Filtering-Bridge Troubleshooting
The following are examples of commands that you would use to debug and to configure an
Philips/ADAC Router (5200-3680) that has been setup either as a straight router or as a filtering-
bridge. We assume the user has basic UNIX knowledge to navigate around the Pegasys (either in a
UNIX Window or over the modem) and the ability to telnet to a desired target. This is just meant to
be examples of the typical commands used and not an exhaustive primer on debugging techniques
and strategies. The examples that are shown are taken from a variety of debugging sessions and
therefore the hostname of the router/filtering-bridge, addresses used and configurations will not be
consistent from one example to the next.
USING TELNET TO ACCESS THE CONFIGURATION INTERFACE

This is a typical example of getting into the router via telnet (could be while logged in
remotely over a modem) to gain access to the command-line configuration interface where you may
debug and make adjustments to the configuration. Most everything needs to be done from the
privileged “enable” mode. It is assumed that you have already successfully configured the router
with valid IP address(es).

adacfilter>en
Password: adacsu
EXAMINING THE RUNNING CONFIGURATION

Once you have used telnet to access the router and get into “enable” mode it is easy to look at
the current configuration that is running in the routers memory (presumably this is identical to the
version that is stored in NVRAM and that nobody has made a change without saving it).

adacrtr#show running
!
version 12.0
!
hostname adacrtr
!
!
ip subnet-zero
!
!
!
!
ip address 144.32.96.1 255.255.240.0
full-duplex
!
ip address 192.9.200.254 255.255.255.0
full-duplex
!
router rip
network 144.32.0.0
network 192.9.200.0
!
ip classless
no ip http server
!
!
line con 0
line aux 0
line vty 0 4
password adacvt
login
!
end
adacrtr#
USING PING FROM INSIDE THE ROUTER

While you are inside the router you may ping addresses on either subnet through either
interface. In fact you are in the very special position of being co-resident on both subnets (imagine
you have two separate computers one on each subnet). Thus, it should be possible to ping any
address in either network from within the router, even if you are unable to ping through the router
from either network.
Very often you may be able to ping targets out on the hospital subnet that you cannot reach by
pinging from the Pegasys. This is usually due to the fact that the remote target does not have a
default gateway setup. The site admin (or the targets 3rd party service person) will need to setup a
default gateway setting to the IP address of our router on the hospital side. That way the target
device knows how to get packets through to a subnet different than its own (without that default
gateway they get a “network unreachable” type of error when trying to reply).
In some cases the remote target may have a default gateway setup to be some other router on
the hospital network and there may not be agreement in the routing protocols used to update the paths
(see “show ip route” below) and the IT Group must be consulted to resolve the issue.
Important: If you are inside a router configured to be a filtering-bridge you will not be
able to do a successful ping to a remote target until you have added its address to the
Access Control List.
When ping runs in the router it does five (5) ICMP echoes to the remote target and keeps
statistics on success/failure and round-trip time.

adacfilter#ping 192.1.2.42
Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.1.2.42, timeout is 2 seconds:
!!!!!
Success rate 100 percent (5/5), round-trip min/avg/max = 1/200/1000 ms
adacfilter#
USING ARP FROM INSIDE THE ROUTER

the current arp table to see the IP addresses and Ethernet addresses of the interfaces that have sent
packets through the router. If you have some IP addresses you are interested in discovering the
Ethernet addresses for, ping them first to make sure they are alive and to refresh them in the table and
then use the “show ip arp” command. Note that the Ethernet addresses are in four-dot-four-dot-
four notation for the 12 bytes of the address. Often we can use “ping” and “show ip arp” do
discover the addresses we will need to create the access lists. These must be collected before we
apply the lists, because once applied, new addresses will not be permitted to pass packets back
through. Also you should always see at least two entries that will be for the two interfaces in the
router (denoted by a dash “-“ in the Age column). Notice that usually, at least for the Cisco routers
we use, the Hardware (MAC) addresses are nearly identical but off-by-one on the last digit and that
there is one on each interface (the one ending in 0 corresponding to the 0/0 interface and the one
ending in 1 corresponding to the 0/1 interface).

adacfilter#show ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 192.1.2.90 2 0800.20c1.67e2 ARPA FastEthernet0/1
Internet 192.1.2.29 - 0001.9680.eeb0 ARPA FastEthernet0/0
Internet 192.1.2.29 - 0001.9680.eed1 ARPA FastEthernet0/1
Internet 192.1.2.42 0 00d0.b7c0.897a ARPA FastEthernet0/0
adacfilter#
USING TRACEROUTE FROM INSIDE THE ROUTER

Once you have used telnet to access the router, configured as a straight router, and get into
“enable” mode it is easy to the routes that a packet will go through to get to its target destination.
Using the “traceroute ip-address” command you will see IP addresses and timing
information for all of the router “hops” along the way. This is extremely handy when dealing with a
multiple site WAN and you are trying to find out why you can talk to some sites and not others (the
Expanding Ping Test seen earlier in WAN Troubleshooting is a good test to use in parallel). Things
you may discover using this tool are unexpected router loops/paths and sometimes that you have
duplicate IP address issues with one or more of your targets.

adacrouter#traceroute 192.3.2.42
Type escape sequence to abort.

Tracing the route to 192.3.2.42
1 192.157.32.1 1000 msec 0 msec 0 msec

2 192.3.6.17 4 msec 12 msec 16 msec
3 192.3.2.42 16 msec 16 msec 16 msec
adacrouter#
EXAMINING THE ETHERNET INTERFACES

the current state of the Ethernet interfaces. The “show ip int” command displays if the interface
is up or down, if the line protocol is up or down, the addresses assigned and the other rules governing
the actions of that particular interface. Here we see the report the two Ethernet interfaces of our
router. Some routers will also have statistics on serial ports, if so equipped.

adacfilter#show ip int
FastEthernet0/0 is up, line protocol is up
Internet address is 192.168.252.252/24
Broadcast address is 255.255.255.255
Address determined by non-volatile memory
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Null turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
IP route-cache flags are None
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
FastEthernet0/1 is up, line protocol is up
Internet address is 192.168.252.252/24
Broadcast address is 255.255.255.255
Address determined by non-volatile memory
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Null turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
IP route-cache flags are None
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
adacfilter#
EXAMINING THE ROUTING TABLES
Once you have used telnet to access the router, configured for straight routing, and get into
“enable” mode it is easy to look at the current state of the Routing Tables. The “show ip route”
command displays any known routes. There should always be two, denoted by C, for the two
interfaces connected inside the router. The command displays a key for the symbols so that the
different types of routes may be identified. Ones we will typically see are S (for a Static route) and R
(for a RIP learned route). Different sites use different routing protocols besides RIP (IGRP, EIGRP,
OSPF, etc.) so tables will vary widely from site to site. Using this command is a good way to verify
if the different routers are sharing their information correctly (or at all).
Here is an example of a router that has had the Gateway of Last Resort set. Typically this is
done in a situation where there is not successful communication of routing protocols to another router
(it is the logical equivalent of how we setup the defaultrouter on a Pegasys). Note that a static route
has been setup for this Gateway of Last Resort and the only other paths the router knows about are its
own two interfaces (denoted by C). For more information on this topic, see the end of the Straight
Router section in Chapter 3.

adacrouter#show ip route
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

S* 0.0.0.0/0 [1/0] via 144.32.111.254
adacrouter#
Here is a different example of a router, running the RIP routing protocol so that the routers on
the network can update each other with the paths they know about. We see a fairly healthy routing
table which helps the router decide who to hand off packets to so that they will navigate the best path
to their desired location. Note that this example comes from an older Cisco 2514 (our latest ones are
Cisco 2621) and one of the differences is that the interfaces are called Ethernet0 and Ethernet1
(instead of FastEthernet 0/0 and FastEthernet 0/1). The other main difference is that the 0 interface in
this example is on the Pegasys side and the 1 interface is on the hospital side (this differs from our
current convention which is exactly opposite). This router was configured long before we adopted
the convention and indeed it really makes no difference. It is just nice to have the convention to help
people keep their mental models straight.
adacrtr1#show ip route
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
S 192.9.201.0 [3/0] via 172.19.14.10

C 192.9.200.0 is directly connected, Ethernet0
R 192.168.33.0 [120/3] via 172.17.2.65, 00:00:22, Ethernet1
R 192.168.50.0 [120/4] via 172.17.2.65, 00:00:22, Ethernet1
R 192.168.8.0 [120/2] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.11.0 [120/3] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.13.0 [120/5] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.14.0 [120/6] via 172.17.1.101, 00:00:13, Ethernet1
216.175.17.0 is variably subnetted, 2 subnets, 2 masks
R 216.175.17.0 255.255.255.0
[120/6] via 172.17.1.151, 00:00:14, Ethernet1
R 216.175.17.11 255.255.255.255
[120/3] via 172.17.2.65, 00:00:22, Ethernet1
R 192.168.15.0 [120/7] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.1.0 [120/1] via 172.17.1.151, 00:00:14, Ethernet1
R 192.168.2.0 [120/4] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.3.0 [120/1] via 172.17.1.153, 00:00:04, Ethernet1
R 192.168.4.0 [120/2] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.5.0 [120/1] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.6.0 [120/4] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.7.0 [120/5] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.31.0 [120/6] via 172.17.2.65, 00:00:22, Ethernet1
R 192.168.16.0 [120/3] via 172.17.1.101, 00:00:13, Ethernet1
R 192.168.20.0 [120/8] via 172.17.1.151, 00:00:14, Ethernet1
R 192.168.21.0 [120/3] via 172.17.2.65, 00:00:22, Ethernet1
R 172.44.0.0 [120/9] via 172.17.1.151, 00:00:14, Ethernet1
R 172.45.0.0 [120/2] via 172.17.1.90, 00:00:25, Ethernet1
R 175.45.0.0 [120/6] via 172.17.1.101, 00:00:13, Ethernet1
R 172.46.0.0 [120/2] via 172.17.1.153, 00:00:04, Ethernet1
R 172.47.0.0 [120/1] via 172.17.1.153, 00:00:04, Ethernet1
R 172.40.0.0 [120/1] via 172.17.1.83, 00:00:24, Ethernet1
[120/1] via 172.17.2.65, 00:00:22, Ethernet1
R 172.41.0.0 [120/2] via 172.17.1.151, 00:00:14, Ethernet1
R 172.42.0.0 [120/9] via 172.17.1.151, 00:00:14, Ethernet1
R 172.43.0.0 [120/1] via 172.17.1.83, 00:00:24, Ethernet1
R 172.36.0.0 [120/2] via 172.17.1.90, 00:00:25, Ethernet1
R 172.37.0.0 [120/2] via 172.17.1.90, 00:00:25, Ethernet1
R 172.38.0.0 [120/2] via 172.17.2.65, 00:00:22, Ethernet1
R 130.14.0.0 [120/7] via 172.17.2.65, 00:00:22, Ethernet1
204.153.216.0 is variably subnetted, 2 subnets, 2 masks
R 204.153.216.0 255.255.255.0
[120/1] via 172.17.2.65, 00:00:22, Ethernet1
R 204.153.216.41 255.255.255.255
[120/1] via 172.17.2.65, 00:00:23, Ethernet1
R 172.34.0.0 [120/2] via 172.17.1.90, 00:00:26, Ethernet1
R 172.35.0.0 [120/2] via 172.17.1.90, 00:00:26, Ethernet1
R 172.60.0.0 [120/4] via 172.17.2.65, 00:00:23, Ethernet1
R 172.61.0.0 [120/3] via 172.17.1.155, 00:00:25, Ethernet1
R 172.58.0.0 [120/4] via 172.17.2.65, 00:00:23, Ethernet1
R 172.59.0.0 [120/4] via 172.17.2.65, 00:00:23, Ethernet1
R 172.55.0.0 [120/1] via 172.17.1.83, 00:00:25, Ethernet1
R 172.49.0.0 [120/9] via 172.17.1.151, 00:00:15, Ethernet1
R 205.166.193.0 [120/7] via 172.17.2.65, 00:00:23, Ethernet1
R 172.28.0.0 [120/4] via 172.17.1.151, 00:00:15, Ethernet1
R 172.29.0.0 [120/1] via 172.17.1.90, 00:00:26, Ethernet1
R 172.30.0.0 [120/1] via 172.17.2.65, 00:00:24, Ethernet1
[120/1] via 172.17.1.83, 00:00:25, Ethernet1
R 172.31.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.24.0.0 [120/1] via 172.17.1.90, 00:00:26, Ethernet1
R 172.25.0.0 [120/1] via 172.17.1.90, 00:00:26, Ethernet1
R 172.26.0.0 [120/1] via 172.17.1.90, 00:00:26, Ethernet1
R 172.27.0.0 [120/1] via 172.17.1.90, 00:00:26, Ethernet1
R 172.21.0.0 [120/2] via 172.17.1.151, 00:00:15, Ethernet1
R 172.22.0.0 [120/1] via 172.17.1.151, 00:00:15, Ethernet1
R 172.16.0.0 [120/1] via 172.17.1.155, 00:00:25, Ethernet1
C 172.17.0.0 is directly connected, Ethernet1
R 172.18.0.0 [120/1] via 172.17.1.155, 00:00:25, Ethernet1
S 172.19.0.0 [1/0] via 172.17.1.83
R 192.1.1.0 [120/2] via 172.17.1.151, 00:00:15, Ethernet1
R 172.100.0.0 [120/2] via 172.17.2.65, 00:00:24, Ethernet1
R 192.8.1.0 [120/2] via 172.17.1.151, 00:00:15, Ethernet1
R 172.76.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.77.0.0 [120/4] via 172.17.2.65, 00:00:24, Ethernet1
R 172.78.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.79.0.0 [120/4] via 172.17.2.65, 00:00:24, Ethernet1
R 172.73.0.0 [120/4] via 172.17.2.65, 00:00:24, Ethernet1
R 172.74.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.75.0.0 [120/2] via 172.17.1.155, 00:00:25, Ethernet1
R 172.92.0.0 [120/9] via 172.17.1.151, 00:00:15, Ethernet1
R 172.88.0.0 [120/4] via 172.17.2.65, 00:00:24, Ethernet1
R 172.89.0.0 [120/1] via 172.17.2.65, 00:00:24, Ethernet1
R 204.181.143.0 [120/1] via 172.17.2.65, 00:00:24, Ethernet1
R 172.90.0.0 [120/1] via 172.17.2.65, 00:00:24, Ethernet1
R 172.85.0.0 [120/2] via 172.17.1.90, 00:00:26, Ethernet1
R 172.86.0.0 [120/3] via 172.17.1.90, 00:00:26, Ethernet1
R 172.87.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.80.0.0 [120/3] via 172.17.2.65, 00:00:24, Ethernet1
R 172.81.0.0 [120/4] via 172.17.2.65, 00:00:24, Ethernet1
R* 0.0.0.0 0.0.0.0 [120/1] via 172.17.2.65, 00:00:24, Ethernet1
[120/1] via 172.17.1.101, 00:00:15, Ethernet1
adacrtr1#
EXAMINING THE ROUTING PROTOCOLS

Once you have used telnet to access the router, configured for straight routing, and get into
“enable” mode it is easy to look at the current state of the Routing Protocols. The “show ip
protocol” command displays any known routing protocols. Typically we will only see one
protocol described, however, some sites may have complex topologies requiring more than one
routing protocol. The command displays which protocol is in effect, the networks that are directly
connected to local interfaces and lists any routers that share their information with our router via this
particular protocol.

adacrouter#show ip protocol
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 1 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: connected, rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 1 1 2
FastEthernet0/1 1 1 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
144.32.0.0
192.9.200.0
Routing Information Sources:
Gateway Distance Last Update
144.32.111.254 120 00:00:12
Distance: (default is 120)
EXAMINING THE BRIDGING ACTIVITY

Once you have used telnet to access the router, which has been configured as a filtering-
bridge, and get into “enable” mode it is easy to look at the current summary of bridging activity for a
given Ethernet address and whether it has been forwarded or blocked. The “show bridge”
command displays this information and you can find out which side of the router the packets are
coming from by looking to see if it is from 0/0 (hospital side by our convention) or 0/1 (Pegasys
side).

adacfilter#show bridge
Total of 300 station blocks, 281 free

Codes: P - permanent, S - self
Bridge Group 1:
Address Action Interface Age RX count TX count

00d0.b77e.e8e2 forward FastEthernet0/0 3 0 0
00c0.4f01.ded4 forward FastEthernet0/0 0 134 0
0040.0555.5b54 forward FastEthernet0/0 2 3 0
0030.b6d9.0c1c forward FastEthernet0/0 0 833006 6189
0090.270a.b0a8 forward FastEthernet0/0 3 0 0
00c0.4f01.e0d1 forward FastEthernet0/0 0 465 624
0006.29e9.7010 forward FastEthernet0/0 4 0 0
0002.160d.cfa0 forward FastEthernet0/0 3 0 0
0090.275c.80fe forward FastEthernet0/0 3 0 0
00d0.b7c0.890a forward FastEthernet0/0 0 2984 2001
0002.55e4.64ea forward FastEthernet0/0 5 0 0
0006.29f7.a537 forward FastEthernet0/0 3 0 0
0800.20c1.67d2 forward FastEthernet0/1 1 3004 3004
00d0.b715.15dd forward FastEthernet0/0 3 0 0
0010.4bc5.5990 forward FastEthernet0/0 0 423 0
0040.a000.1ad5 forward FastEthernet0/0 1 0 0
0002.5564.e037 forward FastEthernet0/0 1 0 0
0004.0008.9076 forward FastEthernet0/0 0 0 0
0090.275a.ec02 forward FastEthernet0/0 0 0 0
adacfilter#
UPDATING CONFIGURATION CHANGES

This is a typical example of getting into the router via telnet (could be while logged in
remotely over a modem) to make configuration changes and save them to the NVRAM of the router
(or filtering-bridge).

adacfilter>en
Password: adacsu
adacfilter(config)#type in your config changes …
adacfilter#
<enter>
adacfilter#
EXITING THE ROUTER

When you are finished you may simply type in quit to return to the Pegasys.

adacfilter#quit
PEGASYS-adac>
REBOOTING THE ROUTER
Sometimes you will want to tell the router to reboot in order to make sure that the
configuration that is stored in NVRAM will boot up correctly. This is done with the reload
command. You will be automatically returned to the Pegasys and after waiting for several minutes,
you may telnet back in to check the configuration. We assume you are already telnetted into the
router and sitting at the “enable” mode prompt.

adacrtr#reload
Connection closed.
PEGASYS-adac>
<Wait for 3 or 4 minutes>

adacrtr>en
Password: adacsu
adacrtr#show running
<Examine the configuration output>
adacrtr#quit
PEGASYS-adac>
EMERGENCY_STANDALONE
EMERGENCY STANDALONE, EMERGENCY RECOVERY

If the network master develops a problem (hard disk or other hardware) that requires it to be
taken off the network and unavailable to provide its usual services (Master Pegasys of the network is
down), then it might be desirable to have the clients be able to continue to function (although in a
limited fashion). This can be done by converting the clients into EMERGENCY STANDALONE
systems.
The Emergency Standalone procedure allows you to use the client Pegasys, in
emergency_standalone mode, while the master is disabled or being repaired. While in Emergency
Standalone mode, the Pegasys system will only be able to use the data on its local hard drive(s) and
peripheral devices connected locally to itself.
Emergency Standalone is provided as a last resort effort to allow master-less clients to
continue operation until the master is repaired. Systems running Version 3.20 or later will make a
copy of the current state of the client prior to converting to an emergency_standalone so that it can be
easily recovered into its former network role (provided that the configuration on the master’s hard
drive has not changed).
Note: If the master’s problem is one that is not related to the hard drive (such as boards in the
imaging chain or other components) then careful consideration should be given to the decision of
whether to put the clients into Emergency Standalone mode. If the repair will be made within a half a
day or so, by simple replacement of the failed component, then it might be worth your while to leave
the clients be and just allow the acquisitions to continue to be done on the Atlas units, even though
they won’t be able to commit the images to their DB_HOST. Once the master is repaired and back
up the studies can be manually committed and all should be back to normal. If you had put the
clients into emergency standalone mode, you would incur additional time to have to run the
emergency_recovery procedure and wait while all the studies with duplicate examkeys are blended
back into the big database, sometimes this represents several hours of additional work. There will be
times when you just have to place the clients into Emergency Standalone mode and then deal with the
proper mechanisms to rejoin them once the repairs to the master have been made.
After the master or network connection has been repaired and it is time to reunite the clients that were
placed into Emergency Standalone mode, you will take one of the two following paths:
1. If the Master Hard Disk or Configuration has changed, refer to the section “ Standard
Networking or Custom Networking” in the appropriate FSE SW install manual using
network_pegx.
2. If Master Hard Disk or Configuration has not changed, refer to the section “Emergency
Recovery” in the appropriate FSE SW install manual using emergency_recovery.
HARD DISK ON THE MASTER PEGASYS IS CORRUPTED OR DEAD

If the hard disk on the master Pegasys is corrupted or dead and needs to be re-OSed or replaced
(which in effect takes down the entire network):
a. Site needs client running until Master is repaired:

1. Disconnect master from network, then boot it up and down as needed (there will be
delays while it tries to talk to the clients now unavailable)
2. Boot up in single-user mode and run emergency_standalone on each client the site
needs up and running. Refer to instructions in FSE install manual.
3. Any client the site does not need leave alone at this time.
4. Atlas stations can still acquire and save the image to the atlas hard disk, they can not
send any files to a non-standalone DBHOST until the master is repaired and the
network re-established. Alternately if you have placed the DBHOST in
emergency_standalone you can re-network the Atlas to the DBHOST. This will
populate, on the DBHOST, in emergency_standalone, the atlas/dicom, directory, files
and configuration that normally reside on the master of the network.
5. Any PegX Acq station needs to have its boot floppy updated to the new temporary
NIS domainname.
b. Once the master’s hard drive is repaired or replaced:

1. Boot and configure new drive as a master of the network using network_pegx.
2. Do an Add_Pegasys for each client one at a time on the master. Same role as before
the hard disk died, ie. Same IP, client number and name for each Pegasys.
3. On each client Pegasys , in order, run network_pegx. Remember keep the same Name,
IP number and client number as before. The client number is important so that you get
the same /vol/patients# as before. Remember your client number is one more than
your patients# is (ie. adac1 has /vol/patients1 so client number is 2).
4. Run master configuration on the master. (Sites that have cooked DB Index files larger
than normal will require you to use the Tech Tip to grow them larger and recollect the
database again. Do this later after all else has been reconnected and reconfigured).
5. If master was an Acquisition station, Load acquisition and backup configuration
software.
6. Network any Atlas connected to the network. Note: If you are loading Atlas Version
5.1/5.2 or earlier, there is a possibility of corrupting the atlas2pega script,
leading ultimately to mixed data. Contact technical support for more information.
7. Update any boot floppies for the PegX Acq nodes.
8. Reload and reconfigure all peripherals.
9. Reload all optional software and restore and site specific backups.
OTHER HARDWARE PROBLEM ON MASTER

If there is any other type of hardware problem in the Master Pegasys that requires extended
downtime, yet the hard drive and configuration is NOT changing:
a. Site needs client running until Master is repaired.

1. Disconnect master from network, then boot it up and down as needed (there will be
delays while it tries to talk to the clients now unavailable)
2. Boot up in single-user mode and run emergency_standalone on each client the site
needs up and running. Refer to instructions in FSE install manual.
3. Any client the site does not need, leave alone at this time
4. Atlas stations can still acquire and save the image to the atlas hard disk, they can not
send to any files to a non-standalone DBHOST until the master is repaired and
network re-established. Alternately if you have placed the DBHOST in
emergency_standalone you can re-network the Atlas to the DBHOST. This will
populate, on the DBHOST in emergency_standalone, the atlas/dicom, directory, files
and configuration that normally reside on the master of the network..
5. Any PegX Acq station needs to have its boot floppy updated to the new temporary
NIS domainname.
b. Master is repaired ( Network role and configuration HAS NOT changed )

1. Reboot any Client not placed into emergency_standalone
2. Reboot any Atlas connected to the network whose DBHOST was not put into
emergency_standalone
3. If the client was placed in emergency_standalone; run emergency_recovery.
4. If an old PegX unit then the boot floppy will need to be updated to restore
domainname.
5. Run master configuration on the master pegasys. …This probably not needed.
STEPS FOR RECONFIGURING NETWORK ROLES FOR A CLUSTER OR SPLITTING CLUSTERS
a. Clarification of steps for reconfiguring network roles of units in a Pegasys cluster. This
scheme applies changing network roles to select a new master for a cluster, as well as when
you are splitting and existing cluster into separate clusters (for example to separate the
PegUltra and PegX units). Remember standalone Pegasys units are clusters of one and
require unique hostname, IP address and NIS domainname.
1. DO YOUR BACKUPS (patients, acq, defaults, custom menus, etc.) If at all

possible, make sure the patient data is archived and delete it from the systems as it will
make the process run quicker and smoother. Also you would be covered should you
run into a problem which requires starting one or more units from scratch. If possible
schedule with your customer ahead of time so they can have the archiving complete
when you come to start the reconfiguration task. Be sure to document any Printer
and DICOM configuration information you may need to re-enter later.
2. Uninstall / Remove all options and peripherals. These usually have hostname
related configuration hooks which become invalid (and sometimes troublesome) when
hostnames or network role relationships change.
Important: On an Ultra, /etc/hosts should actually be a symbolic link that points to
/etc/inet/hosts you can check this by doing an ” ls -l /etc/hosts” and you should
see the following at the end of the line:
hosts -> /etc/inet/hosts
If it does not have the arrow pointer then there are two separate hosts files. You must
reconcile the contents of /etc/hosts and /etc/inet/hosts and make sure the correct info is in
/etc/inet/hosts. Then we will fix the symbolic link in the /etc directory as follows:
rm /etc/hosts (answer y if prompted)
ln –s /etc/inet/hosts /etc/hosts
3. One at a time, halt a client, do a Delete_Pegasys on the master, boot the client up
single-user and run emergency_standalone. The network_pegx script was only
designed to work when run on a unit that is a standalone (not on a client).
4. Once all units are in standalone mode, halt them all to the boot prompt (> or ok).
Important: If possible, use a separate 10/100 switch, not connected to the rest of the
network, to start building your new cluster. This helps avoid NIS cross-binding. After
your cluster has been completed you may move it back to the regular network connections.
5. Choose the one to be the new master, boot it up and run network_pegx with the
custom option and assign it as the new master of a network of pegasys units. Be sure
to clean up any old NIS domain entries (see above).
6. One at a time for each of the clients, do an Add_Pegasys on the master and then
boot the client up and do a custom network_pegx to add it to the group. Be sure
to clean up any old NIS domain entries (see above).
7. Once all the clients are done, you can initialize the database with Master Config.
8. Update all the acquisition boot floppies and run the scripts for the Atlas units to
assign their network info and bind them to their DBHOST units.
9. Reload all the options / peripherals / custom info you backed up at the beginning.
10. Test, test, test! Make sure that acquisitions can commit and be viewed within the
Virtual_DB, test options and peripherals (especially the connectivity related ones).
Note: All of the detailed steps should be documented in several ways in the 3.4 or 4.2
Pegasys manuals (flowcharts and indexes) and Options/Peripherals manuals but may not
be in overview summary form as above.
Note: If you now have an ALL Ultra network with some units that used to be attached to a
PegX master, the only way to get back the Full Patient Space on those units is to RE-OS
and Load Philips/ADAC Software. There is NO “Undo Shrink Large Pat” program.
Restore PegX ( Ultra only )
• When running network_pegx, one of the first steps that is taken is that the system’s network
configuration information is saved in a savedir located in /files/pat.
• Each savdir is assigned a number that you refer to when accessing the configuration information
stored in the directory.
• If you want to restore a Pegasys Ultra to a previous network configuration, you use the
restore_pegx script and savedir reference number. See complete instructions in the 9202-0142*
manual.
The savedir entries are saved if you do not elect to delete them at the end of the network_pegx
process. There may be many of these savedir entries set aside for you to choose from. If you want to
go back to the earliest known state when network_pegx was first run on this system then choose the
one with the earliest date. If you had a stable state earlier in your day, before you started to run
network_pegx then choose the earliest time of the day. Remember the very first savedir created
should get it back to a Standalone Ultra , adac, 192.9.200.1 configuration. Each time someone runs
network_pegx on the unit, it will create a new savedir.NNN file. You can examine the dates of the
available savedir entries with the following commands:
cd /files/pat
ls –lrtd savedir*
drwxrwxrwx 3 root other 0512 Jul 2 10:30 savedir.1909
drwxrwxrwx 3 root other 0512 Jul 5 8:30 savedir.504
drwxrwxrwx 3 root other 0512 Nov 8 10:30 savedir.843
Select the savedir.1909 file to get back to the original standalone system configuration.
Use the following commands:
cd /usr/adac/pegx/scripts/load
restore_pegx 1909
Suggestions on when to use restore_pegx.

a. If you have a failed network_pegx run which results in your client not being able to
communicate with the cluster
1. Select the first savedir of the day (if there have been multiple attempts at
network_pegx) as this should be a known good configuration.
2. If system has hung and unable to boot up to multi-user, Follow tech tip “Running
restore_pegx When Booted as Single User” client will not boot if not connected to its
network.
b. If the site no longer needs the Ultra system and it is a client on a network.
1. Follow restore_pegx procedure before disconnecting from network
2. If already disconnected, Follow tech tip “Running restore_pegx When Booted as
Single User” client will not boot if not connected to its network.
c. Failure during network_pegx so system did not complete its reconfiguration. Now the pegasys
will not boot. Follow tech tip “Running restore_pegx When Booted as Single User” if system
will not boot.
d. Corrupted Network and NIS configuration so system does not know its current role on the
network. Follow tech tip “Running restore_pegx When Booted as Single User” if system will
not boot.
e. DO NOT use it to “glue” back clients that have been separated from the master by using the
Emergency Standalone procedure. If master’s hard drive did not change then use Emergency
Recovery instead.
Reference Informational (“Info”) Tips:

1. Can’t Run Emergency Standalone on the Ultra
2. Error When Running network_pegx on the Ultra Client
3. ‘inetd’ Messages reported in /var/adm/messages After Network Change
4. Steps for Reconfiguring a Mixed Network
5. Running restore_pegx When Booted as Single User
Failed /vol/patientsN install:
This happens occasionally when running network_pegx to add a client onto a Pegasys cluster.
It is characterized by the inability to see patients for that directory when changing scope to that
machine inside Patient Selection, no mention of visiting that slave when recollecting the database and
inability to report on that directory when using Show Patient Data Space. Problems exhibited are no
entry in auto.vol and/or partitions.map on the master but there is an entry in the /etc/exports file on
slave. Once fixed the space server on the slave will have to be restarted. Prove that it is fixed by
trying a network data transfer after restarting space server.
To repair:
On the master (as su -):

• Place an entry in /etc/auto.vol
patientsN <tab> adacN:/export/vol/patients/patientsN
• Place an entry in /vol/patients_db/partitions.map
N <tab> 1 <tab> 80 <tab> 90 <tab> /vol/patientsN

N <tab> 1 <tab> 80 <tab> 90 <tab> /vol/patientsN/temp
• Rebuild the master’s NIS Maps and push them out:
cd /var/yp
make
On the slave (as superuser):

• Verify an entry in the /etc/dfs/dfstab (Solaris 2.x) or /etc/exports (SunOS 4.1.3u1) file for
/files/pat/patients/patientsN
• Verify symbolic link is in /export/vol/patients. Use
ls -l /export/vol/patients
should find the following:
patientsN -> /files/pat/patients/patientsN
if not there create it by doing the following:
cd /export/vol/patients
ln -s /files/pat/patients/patientsN patientsN
shareall (Solaris 2.x) or exportfs –a (SunOS 4.1.3u1)
(Exit “su” mode ; as pegasys)

• Restart Space Server using Pegasys Status - Full Status option.
Back on the master (Exit “su” mode; as pegasys):

• Reinitialize database using Pegasys Status - Full Status option.
Sun Ethernet interface diagnostic
SPARC 5,10,20
At the ok prompt; type: test net
( Normal response With Ethernet cable RJ-45 connected. )
Using AUI Ethernet Interface

Internal loopback test -- succeeded
External loopback test -- Lost carrier (transceiver cable problem?)
Send failed.
Using TP Ethernet Interface

External loopback test -- succeeded
( Error response With Ethernet cable RJ-45 removed. )
Using AUI Ethernet Interface

Send failed.
Using TP Ethernet Interface

Send failed.
Net selftest failed. Return code = -1
ULTRA
Power cycle the Ultra or type reset at the ok prompt
Press: <Stop-a> as soon as the display comes back on. (do not let Ultra reboot)
At the ok prompt, type: test net
( Normal response With Ethernet cable RJ-45 connected. )
Internal loopback test – succeeded

Transceiver check – passed
( Error response With Ethernet cable RJ-45 removed. )
Internal loopback test – succeeded

Transceiver check – failed
Net selftest failed. Return code = -1
NI5210DG Ethernet Card Diagnostic
Note: This diagnostic is for the Interlan Ethernet Card in the Peg Tower, Generic PC.
(5200-1196 CONTROLLER CARD,ETHERNET/AT)
Insert the boot disk or diagnostic floppy that has the NI5210DG diagnostic.
Reboot PC <Ctrl-alt-del> keys
At the Blue Message ( Host Pegasys must be up and ready before proceeding )
Press <Ctrl–c> keys
Terminate Batch Job (y/n)?

Type <Y>
A:>
Type NI5210DG <enter>
Note : Option A (run all test) will fail if the pc was booted past the Blue Pegasys message.
The Ethernet card has to be properly terminated ( 25 ohms) for the test to pass.
STATUS
Parameters
Test Repetition = 10 | Cards Installed = 1 | I/O ADDR = 360
Max Error Count = 10 | Card under test = 1 | Mem ADDR = CC000
Logging Device = nul | | Mem Size = 16K
Network Address = XXXXXXXX | Diagnostic V 1.11 | Interrupt = IRQ2
1. type D Change parameters 19. type B Internal tests

2. type D Change Network address 20. type A Network Address Prom Test
3. type Y (change address) Status (address rom test passed)
4. type 1 Address Rom 21. type <enter>
5. type I Change I/O address 22. type B Buffer Ram Test
6. type Y (yes) Status (buffer ram test passed)
7. type 360 (new address) 23. type <enter>
8. type J Interrupt channel 24. type C 82586 internal test
9. type Y (yes) Status (82586 internal test passed)
10. type 2 (interrupt 2) 25. type <enter>
11. type K change mem or config 26. type D Internal loop back test
12. type Y (yes) Status (internal loop back passed)
13. type CC000 (new address) 27. type X (exit to main menu)
14. type Y (change mem size) 28. type A RUN ALL TEST
15. type 16 (size of memory) Status (CARD 1 PASSED)
16. type L (save/recall parameters) 29. type <enter>
17. type S (save) 30. type X (exit)
18. type X (exit)
Note: Test C and D may fail if you have a 486 PC
REBOOT The PC <Ctrl-Alt-Del>
Linksys Ethernet Card Diagnostic
Note: This diagnostic is for the Linksys Ethernet PC card. Insert the appropriate, non-PnP or PnP,
utility disk for card under test. First, reboot the PC by pressing <Ctrl-Alt-Del> keys simultaneously.
A:> cd enetlsys
A:>\enetlsys> setup
press <enter>
Highlight ( Configure the Ether16 Lan Card Hardware ) “ older version of diagnostic”
press <enter>
Highlight ( Set up Configurations )
press <enter>
CONFIGURE CARD
NON-PnP PC PnP PC PnP Gantry

Node ID xx xx xx xx xx xx Node ID xx xx xx xx xx xx Node ID xx xx xx xx xx xx
Bus Mode 16-bit Bus Mode 16-bit Bus Mode 16-bit
Card Type Ether16 CT Card Type Ether16 CT Card Type Ether16 CT
Set up Configuration Set up Configuration Set up Configuration

Connector Type BNC Connector Type RJ-45 Connector Type RJ-45
I/O Base Address 320H I/O Base Address 320 I/O Base Address 240
Interrupt Number 10 (16-bit) Interrupt Number 10 (16-bit) Interrupt Number 10 (16-bit)
Remote Boot Enable Plug-n-Play Disabled Plug-n-Play Disabled
Boot ROM Address CC000H Full Duplex Disabled Full Duplex Disabled
Boot ROM Size 16K Remote Boot Enable Remote Boot Enable
Boot ROM Address CC000 Boot ROM Address D8000
Boot ROM Size 16K Boot ROM Size 16K
press <esc> exit configuration menu

Highlight ( Adaptor Basic Diagnostic)
press <enter>
Adapter Diagnostics
Node Address : xx xx xx xx xx xx
I/O Base Address : 320H “example address shown”
Connector Type : UTP (RJ-45) “example connection shown”
Interrupt Numbers : 10 (16-bit)
---------------------------------------------------Cycle #-----------------------------------------------------
Current I/O Base Address ……………………………………………………………...Pass/Fail
DC-DC Convert, Oscillator, Crystal T7213……………………………………………Pass/Fail
EEPROM……………………………………………………………………………….Pass/Fail
Lan Setup Registers…………………………………………………………………….Pass/Fail
Memory…………………………………………………………………………………Pass/Fail
Lan Controller Functions……………………………………………………………….Pass/Fail
Cable Connection……………………………………………………………………….Pass/Fail
Loop back Mode Testing……………………………………………………………….Pass/Fail
After a few passes press <esc> key to get back to Diagnostic Screen
press <esc> to go back to Main Screen
Arrow Down to Exit and press <enter>
Chapter 6: Network File Structures
Scope
This chapter shows PegX, PegX PC, PegUltra, and Atlas network file contents. If you believe
you have a system with corrupted files, compare your files to those in this chapter. Your host names
and IP address numbers may be different but the structure should be relatively the same. This chapter
contains these files:
• Examples of PegX Network Files (links)

• Examples of Ultra Network Files (links)
• PegX Master Files (“nmvap”)
• PegX Client Files (“nmvap1”)
• PegX Acquisition Files
• EPIC Detectors on a PegX Camera
• PegX Acquisition PC Network Files
• Ultra Master Files
• Ultra Client Files
• Atlas Files with a Forte Camera Attached
• Skylight Files
Note: The files shown in this chapter include only pertinent information. Extraneous text
(i.e., comments) has been removed. Actual configurations vary between sites; these
examples demonstrate the variety of networks in use today. ALSO, The Pegasys 5.0
(Solaris 8) file structure parallels that of the PegUltra running Solaris 2.5.1.
Examples of PegX Network Files (links)
Master Client
/.rhosts /.rhosts
/etc/hosts /etc/hosts
/etc/peghosts ypcat peghosts.byname
/etc/ethers /etc/ethers
/etc/defaultrouter Ë /etc/defaultrouter Ë
/etc/aliases /etc/aliases
/etc/fstab /etc/fstab
/etc/auto.vol /etc/auto.vol
/etc/hostname.le0 /etc/hostname.le0
/etc/systems /etc/hostname.hme0 ËË
/etc/ypservers /etc/systems
/etc/modules/shared_dist.map /etc/ypservers
/etc/networks /etc/modules/shared_dist.map
/etc/netmasks /etc/networks
/etc/exports /etc/netmasks
/etc/install/sys_info /etc/exports
/usr/adac/site/`hostname`/ADACSetup /etc/install/sys_info
/vol/patients_db/partitions.map /usr/adac/site/`hostname`/ADACSetup
PegX Acquisition Atlas

/etc/modules/acq.cfg /etc/hosts
/etc/modules/acq_sw_config /etc/ethers
/etc/modules/adac.config /etc/networks
/usr/adac/pegx/data//COR/pc_stack11.cor /etc/netmasks
/etc/aliases
/etc/dfs/sharetab
PegX Epic /etc/dfs/dfstab
/usr/local/matador/etc/bootptab /etc/hostname.hme0
/etc/vfstab
/usr/local/detector/etc/bootptab
PegX PC /export/home/atlas/etc/site.config
A:\nfs\drives.bat /export/home/atlas/etc/acq_sw_config
A:\nfs\network.bat /export/home/atlas/data/pc_atlas1.COR
A:\nfs\hosts
Examples of Ultra Network Files (links)
Master Client
/.rhosts /.rhosts
/etc/hosts /etc/hosts
/etc/peghosts ypcat peghosts.byname
/etc/ethers /etc/ethers
/etc/networks /etc/networks
/etc/netmasks /etc/netmasks
/etc/defaultrouter Ë /etc/defaultrouter Ë
/etc/aliases /etc/aliases
/etc/vfstab /etc/vfstab
/etc/auto.vol /etc/auto.vol
/etc/nodename /etc/nodename
/etc/hostname.hme0 /etc/hostname.hme0
/etc/hostname.hme1 ËË /etc/hostname.hme1 ËË
/etc/systems /etc/systems
/etc/ypservers /etc/ypservers
/etc/modules/shared_dist.map /etc/modules/shared_dist.map
/etc/dfs/dfstab /etc/dfs/dfstab
/etc/dfs/sharetab /etc/sharetab
/usr/adac/site/`hostname`/ADACSetup /usr/adac/site/`hostname`/ADACSetup
/vol/patients_db/partitions.map
Ë Optional file; exists only on specially configured systems.
ËË hostname.xxx file name:
hostname.le0 - file for 10Mb Ethernet on PegX motherboard

hostname.le1 - file for 10Mb 2nd Ethernet installed in PegX system
hostname.hme0 - file for 100Mb 2nd Ethernet installed in PegX system
hostname.hme0 - file for 100Mb Ethernet on Ultra motherboard
hostname.hme1 - file for 100Mb 2nd Ethernet installed in Ultra system
hostname.hme0 - file for 100Mb 2nd Ethernet installed in Blade system
PEGX NETWORK FILES
The following are network files from a PegX on a Class B custom network. The Pegasys
network file names do not have to change when you change from one class of network to another.
This example has custom host names and IP addresses.
PEGX MASTER FILES (“NMVAP”)

cat /.rhosts
-rw-rw-rw- 1 root staff 95 Jul 19 16:47 /.rhosts
(The /etc/hosts.equiv and .rhosts files provide the “remote authentication” database for
rlogin(1), rsh(1), rcp(1), and rcmd(3N). The files specify remote hosts and users that are considered
trusted. Trusted users are allowed to access the local system without supplying a password. The
library routine ruserok( ) (see rcmd(3N)) performs the authentication procedure for programs by
using the /etc/hosts.equiv and .rhosts files. The /etc/hosts.equiv file applies to the entire system,
while individual users can maintain their own .rhosts files in their home directories. These files
bypass the standard password-based user authentication mechanism. To maintain system security,
care must be taken in creating and maintaining these files.)
nmvap
nmvap1
nmvap4
nmohsu
nmvap3
nmvap2
pc_stack1
cat /etc/hosts
-rw-rw-rw- 1 root staff 857 Jul 19 16:46 /etc/hosts
(The hosts file is a local database that associates the names of hosts with their Internet
Protocol (IP) addresses. The hosts file can be used in conjunction with, or instead of, other hosts
databases, including the Domain Name System (DNS), the NIS hosts map and the NIS+ hosts table.
Programs use library interfaces to access information in the hosts file. The hosts file has one entry
for each IP address of each host. If a host has more than one IP address, it will have one entry for
each, on consecutive lines.)
# Sun Host Database

#
# If the NIS is running, this file is only consulted when booting
127.0.0.1 localhost
#
191.254.118.177 nmvap timehost loghost
191.254.118.178 nmvap1
191.254.118.185 nmvap4
191.254.118.186 pc_stack41
191.11.7.44 nmohsu # This Pegasys is a client across two routers
191.254.118.184 nmvap3
191.254.118.187 pc_stack31 # solus
191.254.118.179 pc_stack11 # vertex
191.254.118.182 nmvap2
191.254.118.183 pc_stack1 # orbitr
191.254.118.188 nmvap3det1
191.254.118.189 nmvap3det2
191.254.118.180 nmvap1det1 # Matador detector head 1
191.254.118.181 nmvap1det2 # Matador detector head 2
191.254.121.114 Imation pc1 # “DICOM printer #1”
191.254.121.115 2D-103 # “DICOM printer #2”
172.16.32.63 pegcard1 # ( 2nd ethernet card installed in nmvap1 )
cat /etc/peghosts (master only)
-rw-rw-rw- 1 root staff 349 Jul 19 16:46 /etc/peghosts
(On the master, this file is the NIS template for Pegasys networking and acquisition functional
properties. The automounter provides this information to system utilities and programs that request
these values.)
## DESCRIPTION
## this file contains the name of all the Pegasys Sun workstations on a
## network with their associated roles.
## Format of line entry and Key to symbols below:
## HOST ACQ(y/n) NIS(m/s/c) DB(m/s/c) SHD(m/s/c)
##
## HOST - hostname of a Pegasys Sun workstation
## ACQ - does the machine have acquisition camera(s)
## NIS - Network Information Systems role ... map lookup facility
## DB - Distributed Network Database role ... for engine master/mirror
## SHD - Shared Directory role ... shared and automounted directories
## y-has functionality
## n-does not have functionality
## m-master
## s-slave
## c-client
nmvap ACQ:y NIS:m DB:m SHD:m
nmvap1 ACQ:y NIS:s DB:c SHD:n
nmohsu ACQ:n NIS:s DB:c SHD:n
nmvap2 ACQ:n NIS:s DB:c SHD:n
cat /etc/ethers
-rw-rw-rw- 1 root staff 1174 Jul 19 16:46 /etc/ethers
(The ethers file is a local source of information about the (48 bit) Ethernet addresses of hosts
on the Internet. The ethers file can be used in conjunction with or instead of other ethers sources,
including the NIS maps ethers.byname and ethers.byaddr and the NIS+ table ethers. Programs use
the ethers(3N) routines to access this information. The ethers file has one line for each host on an
Ethernet.)
# This file is automatically maintained.

# DON'T EDIT IT UNLESS YOU KNOW WHAT YOU'RE DOING
8:0:20:1f:e5:47 nmvap
8:0:20:c:7e:4a nmvap4
8:0:20:76:b2:30 nmvap1
02:07:01:13:b3:0e pc_stack11 # vertex
8:0:20:d:16:e4 nmohsu
8:0:20:7b:3c:ec nmvap3
02:07:01:03:08:09 pc_stack31 # solus
8:0:20:7e:51:c nmvap2
02:07:01:0c:b6:6f pc_stack1 # orbitr
02:07:01:12:ed:17 pc_stack41
cat /etc/defaultrouter
-rw-rw-rw- 1 root staff 12 Feb 25 1999 /etc/defaultrouter
191.254.118.190
Note: This file exists only on systems specially configured with a default router. Only the
IP address of the gateway/router is listed in the file and only one IP address allowed in the
file.
cat /etc/aliases
-rw-r--r-- 1 root staff 1940 Jul 19 16:13 /etc/aliases
(On the master, this file is the NIS template for email addresses and aliases for all of the user
accounts and handles email to the pegasys user in a special way (the message is duplicated into a
separate mailbox for each Pegasys unit on the network so that no messages are missed due to deletion
by any one person). The automounter provides this information to system utilities and programs that
request these values. )
# Aliases can have any mix of upper and lower case on the left-hand side,
# but the right-hand side should be proper case (usually lower)
#
# >>>>>>>>>> The program "newaliases" will need to be run after
# >> NOTE >> this file is updated for any changes to
# >>>>>>>>>> show through to sendmail.
#
# Alias for a person, so they can receive mail by several names:
# epa:eric
#######################
# Local aliases below #
#######################
users:manager,diag,pegasys,informix,rt11,adacrmt
manager:manager@nmvap
diag:diag@nmvap
pegasys:pegasys@nmvap
informix:informix@nmvap
rt11:rt11@nmvap
adacrmt:adacrmt@nmvap
pegasys: peglist
peglist: pegnmvap,pegnmvap1,pegnmvap2,pegnmvap3,pegnmvap4,pegnmohsu,
pegnmvap: /var/spool/mail/pegasys_nmvap
pegnmvap1: /var/spool/mail/pegasys_nmvap1
pegnmohsu: /var/spool/mail/pegasys_nmohsu
Note: Only the Master has entries below the line # Local aliases below #.
cat /etc/fstab
-rw-rw-rw- 1 root staff 257 Oct 26 1999 /etc/fstab
(The /etc/fstab file contains entries for file systems and disk partitions to mount using the
mount(8) command, which is normally invoked by the rc.boot script at boot time. This file is used by
various utilities that mount, unmount, check the consistency of, dump, and restore file systems. It is
also used by the system itself when locating the swap partition.)
/dev/sd0a / 4.2 rw 1 1
/dev/sd0h /files 4.2 rw 1 3
/dev/sd0g /usr 4.2 rw 1 2
/dev/sd0d /files/pat 4.2 rw 1 4
/dev/fd0 /pcfs pcfs rw,noauto 0 0
/dev/sr0 /cdrom hsfs ro,noauto 0 0
cat /etc/auto.vol (master only)

-rw-rw-rw- 1 root staff 2078 Jul 19 16:46 /etc/auto.vol
(auto.vol resides in the /etc directory, and contains auto-mount(8) map entries for volumes,
automouunt reads the auto.master NIS map, which contains an entry for auto.vol and /vol.
References to /vol/volume_name are translated by the auto-mount daemon using the auto.vol
map, and the directory specified in the map entry is mounted.
The concept of a volume is that it is a self contained directory hierarchy that can be NFS
mounted. It is referenced using a known volume_name. The use of an automount map is suggested
so that the volume and its contents can be referenced through /vol. This is advantageous because
location-transparency (that is, which host the volume is on) and replication of read-only volumes can
be provided using the automount mechanism.)
## DESCRIPTION
## template for NIS map auto.vol that is copied and sed'ed
## to replace adac with the master NIS servers hostname upon install
# DON'T EDIT IT UNLESS YOU KNOW WHAT YOU'RE DOING!
#
patients_db nmvap:/export/vol/patients/patients_db
patients0 nmvap:/export/vol/patients/patients0
rt11_1 nmvap:/export/vol/patients/rt11_1
rt11_2 nmvap:/export/vol/patients/rt11_2
centor nmvap:/export/vol/patients/centor
rt11 nmvap:/export/vol/patients/rt11
mita nmvap:/export/vol/patients/mita
patients1 nmvap1:/export/vol/patients/patients1
patients6 nmohsu:/export/vol/patients/patients6
cat /etc/hostname.le0
-rw-rw-rw- 1 root staff 7 Feb 25 1999 /etc/hostname.le0
(This file contains the hostname of the Pegasys unit and is consulted at boot time when the
initial configuration of the ethernet interface is being done.)
nmvap
cat /etc/systems (master only)

-rw-rw-rw- 1 root staff 2108 Jul 19 16:13 /etc/systems
(On the master, this file is the NIS template for list of machines and NIS classifications (like
masterbootserver, pcnfs, etc.). This file became mostly a bookkeeping map when we changed from
the Sun 386i units to the Sparcstations. It was required during the transitional period and remains
today (though with changes to a couple scripts, it could be eventually eradicated). The automounter
provides this information to system utilities and programs that request these values.)
## DESCRIPTION
## an NIS map ADAC carried over from the 386i to the Sparc to keep
## track of hostname arch os and NIS role
## although some parts supplanted by the new peghosts map for rel200
## some scripts still make use of the information contained herin
nmvap sun4c sunos4.1.1 "" -1 -1 master_bootserver
nmvap1 sun4c sunos4.1.1 "" -1 -1 slave_bootserver
nmohsu sun4c sunos4.1.1 "" -1 -1 slave_bootserver
pc_stack31 pcnfs unknown "" -1 -1 network_client
pc_stack1 pcnfs unknown "" -1 -1 network_client
cat /etc/ypservers (master only)

-rw-rw-rw- 1 root staff 87 Jul 19 16:46 /etc/ypservers
(On the master, this is the NIS template for the hostnames of the master and the Pegasys
machines that are NIS slaves. The automounter provides this information to system utilities and
programs that request these values.)
## DESCRIPTION
## this file contains the name of the NIS master and all the NIS slaves
## on a network
nmvap
nmvap4
nmvap1
nmohsu
nmvap3
nmvap2
cat /etc/modules/shared_dist.map (master only)
-rw-rw-rw- 1 root staff 4659 Jul 19 16:13 /etc/modules/shared_dist.map
## DESCRIPTION
## A template for the rdist file that will be distributed
## for shared_files rule from the peghosts--> SHD:m to SHD:s machines
## for rule nis_mirror from the peghosts--> NIS:m to NIS:s machines##
UPDATED for PegX which shares a lot less with its bretheren
## converted all targets to use MIRROR_SLAVE_HOST as the PegX's
# files/dirs to be backed up fairly often as they are important and dynamic
# these are ok to push to other PegX and PegMD use MIRROR_SLAVE_HOST now
SHARED_FILES_1HR = (
/files/vol/patients/patients_db/curr/OBJK.lock
/files/vol/patients/patients_db/formatcap
/files/vol/patients/patients_db/periph.rsc
/files/vol/patients/patients_db/partitions.map
/files/vol/patients/patients_db/tbconfig
/files/vol/patients/patients_db/tbparam
/etc/auto.home
/etc/auto.master
/etc/auto.vol
/etc/bootparams
/etc/ethers
/etc/group
/etc/hosts
/etc/inetd.conf
/etc/magic
/etc/netgroup
/etc/netmasks
/etc/networks
/etc/passwd
/etc/peghosts
/etc/printcap
/etc/protocols
/etc/publickey
/etc/rc
/etc/rc.local
/etc/remote
/etc/rpc
/etc/sendmail.cf
/etc/services
/etc/systems
/etc/ypservers
cat /etc/networks
-rw-r--r-- 1 root staff 208 Feb 23 1999 /etc/networks
(The /etc/networks file on the master is the NIS template for network address values across
the network. At the beginning of the boot process the local copy of /etc/networks on each Pegasys is
consulted but after a certain point in the booting sequence the values from the NIS maps are used
instead. On each Pegasys there will be an entry in this file for the current network name and number
(plus any aliases))
#
# Sun customer networks
# This file is never consulted when the NIS are running
#
loopback 127
sun-ether 152.131 sunether ethernet localnet
sun-oldether 125 sunoldether
#
# Internet networks
#
arpanet 10 arpa
ucb-ether 46 ucbether
hosp-ether 172.16 hospether #( 2nd ethernet card)
Important: If your IP address begins in the 10 address range, remember to remove the
“arpanet 10 arpa” line from the networks file.
cat /etc/netmasks
-rw-rw-rw- 1 root staff 517 Feb 25 1999 /etc/netmasks
(The /etc/netmasks file on the master is the NIS template for netmask values across the
network. At the beginning of the boot process the local copy of /etc/netmasks on each Pegasys is
consulted but after a certain point in the booting sequence, the values from the NIS maps are used
instead. There is an implied netmask that the program ifconfig applies at boot time based upon your
IP class, unless an entry in the /etc/netmasks file tells it to do otherwise.)
#
# Network masks database
#
# only non-default subnet masks need to be defined here
#
# Network netmask
129.144 255.255.255.0
129.145 255.255.255.0
129.146 255.255.255.0
129.147 255.255.255.0
129.148 255.255.255.0
129.149 255.255.255.0
129.150 255.255.255.0
129.151 255.255.255.0
129.152 255.255.255.0
129.153 255.255.255.0
129.154 255.255.255.0
129.155 255.255.255.0
129.156 255.255.255.0
129.157 255.255.255.0
129.158 255.255.255.0
129.159 255.255.255.0
128.32 255.255.255.0
152.131 255.255.255.240 # subnet mask entry for this class B network.
172.16 255.255.255.0 #( 2nd ethernet subnet )
cat /etc/exports (differs depending on acq, options, etc..)
-rw-rw-rw- 1 root staff 174 Feb 25 1999 /etc/exports
(The /etc/exports file contains entries for directories that can be exported to NFS clients.
This file is read automatically by the exportfs(8) command. If you change this file, you must run
exportfs(8) for the changes to affect the daemon's operation. Only when this file is present at boot
time does the rc.local script execute exportfs(8) and start the NFS file-system daemon, nfsd(8). The
/etc/xtab file contains entries for directories that are currently exported. This file should only be
accessed by programs using getexportent() (see exportent(3)). Use the -u option of exportfs to
remove entries from this file.)
/var/spool/mail
/files/pat/patients/rt11_1
/files/pat/patients/rt11_2
/usr/adac/informix
/files/pat/camera1
/files/camera1
/etc/modules
/var/spool/pcnfs
/worm/physical/opti_nmvap
cat /etc/install/sys_info
-rw-rw-rw- 1 root staff 298 Feb 25 1999 /etc/install/sys_info
(System Information File, Should have current system role and information.)
hostname=nmvap
sys_type=standalone
ether_name=le0
ip=191.254.118.177
yp_type=master
domainname=vapdx
op_type=install
reboot=yes
rewind=no
arch_str=sun4.sun4m.sunos.4.1.3_U1
root=sd0a
user=sd0g
termtype=sun
timezone=PST8PDT
server=
server_ip=
exec_path=
kvm_path=
static_sizing=no
cat /usr/adac/site/`hostname`/ADACSetup
-rw-rw-rw- 1 root wheel 6620 Jul 19 17:27 /usr/adac/site/`hostname`/ADACSetup
# This is the .cshrc file that defines all environment vars needed for
# pegasys use.
# setenv SPACE_SERVER NOHOST

setenv DB_ARCH informix
setenv COLORMAP_PATH ${DATA_PATH}icb/colormaps/
setenv DB_SERVER nmvap #(Should be name of MASTER)

setenv DBPATH //nmvap #(Should be name of MASTER)
setenv INFORMIXDIR /usr/adac/informix
if (`hostname` != ${DB_SERVER} && “${DB_SERVER}” != “NOHOST”)
setenv DATABASE_PATH /adac/patients_db/

setenv ARCHIVE_PATH /adac/patients_db/
setenv PATIENT_PATH /adac/patients0/
setenv COMMON_TEMP_PATH /vol/patients5/temp/
setenv DB_WORKING_PATH /adac/patients_db/curr/

setenv DB_CURRENT_PATH /adac/patients_db/curr/
setenv FORMAT_PATH /adac/fmttemp/
setenv CONVERT_PATH /adac/rt11/
setenv CENTOR_PATH /adac/centor/
setenv DB_SERVER nmvap #(Should be Name of Master)

endif
setenv CENTOR_TEMPLATE_PATH ${DATA_PATH}centor/
cat /vol/patients_db/partitions.map
-rw-rw-rw- 1 pegasys users 1019 Jul 19 16:46 /vol/patients_db/partitions.map
(This file should contain a pair of lines for patients# and patients#/temp for each patient data
directory housed on each Pegasys on the network. It can be noted here that this file indirectly serves
two other functions;
• the order in which the patient partitions are rebuilt into the database (“Rebuilding patient
directory /vol/patientsX. This may take a while…”)
• the % of patient partition usage allowed before warning and critical errors begin to appear
(i.e., 80% / 90%) of total patient partition size)
0 1 80 90 /vol/rt11_1
0 1 80 90 /vol/rt11_2
0 1 80 90 /vol/centor
0 1 80 90 /vol/rt11
0 1 80 90 /vol/mita
0 1 80 90 /vol/patients0
0 1 80 90 /vol/patients0/temp
Note: partitions.map file exists on network master, is shared to all clients.
PEGX CLIENT FILES (“NMVAP1”)
cat /.rhosts
-rw-rw-rw- 1 root staff 95 Jul 19 16:13 /.rhosts
while individual users can maintain their own .rhosts files in their home directories. These files
bypass the standard password-based user authentication mechanism. To maintain system security,
care must be taken in creating and maintaining these files.)
nmohsu
nmvap
nmvap1
nmvap2
nmvap3
nmvap4
pc_stack11
VHAPORDIG1
cat /etc/hosts
-rw-rw-rw- 1 root staff 136 Jan 30 13:57 /etc/hosts
#
# Sun Host Database
#
# If the NIS is running, this file is only consulted when booting
#
127.0.0.1 localhost
#
191.254.118.178 nmvap1 timehost loghost
191.254.118.179 pc_stack11 # vertex
172.16.32.63 pegcard1 #( 2nd ethernet card install in this system )

cat: peghosts: No such file or directory
these values.)
Note: ypcat prints out values in a Network Information Service (NIS) map specified
by mname, which may be either a map name or a map nickname. Since ypcat uses the
NIS service, no NIS server is specified. To look at the network-wide peghosts database,
peghosts.byname, (with the nickname peghosts), type in:
ypcat peghosts.byname
nmvap ACQ:y NIS:m DB:m SHD:m
nmohsu ACQ:n NIS:s DB:c SHD:n
nmvap2 ACQ:n NIS:s DB:c SHD:n
cat /etc/ethers
-rw-rw-rw- 1 root staff 116 Jan 21 2002 /etc/ethers
Ethernet.)

8:0:20:76:b2:30 nmvap1
02:07:01:13:b3:0e pc_stack11 # vertex
cat /etc/defaultrouter
-rw-rw-rw- 1 root staff 12 Jan 21 2002 /etc/defaultrouter
191.254.118.190
file.
cat /etc/aliases
-rw-rw-rw- 1 root staff 1136 Jan 21 2002 /etc/aliases
##
#
#
# @(#)aliases 1.10 89/01/20 SMI
##
# Following alias is required by the mail protocol, RFC 822
# Set it to the address of a HUMAN who deals with this system's mail problems.
Postmaster: root
# Alias for mailer daemon; returned messages from our MAILER-DAEMON
# should be routed to our local Postmaster.
MAILER-DAEMON: postmaster
# Aliases to handle mail to programs or files, eg news or vacation
# decode: "|/usr/bin/uudecode"
nobody: /dev/null
# Sample aliases:
# Alias for distribution list, members specified here:
#staff:wnj,mosher,sam,ecc,mckusick,sklower,olson,rwh@ernie
# Alias for distribution list, members specified elsewhere:
#keyboards: :include:/usr/jfarrell/keyboards.list
#epa:eric
#######################
#######################
cat /etc/fstab
-rw-rw-rw- 1 root staff 278 Jan 21 2002 /etc/fstab
(The /etc/fstab file contains entries for file systems and disk partitions to mount using the
mount(8) command, which is normally invoked by the rc.boot script at boot time. This file is used by
various utilities that mount, unmount, check the consistency of, dump, and restore file systems. It is
also used by the system itself when locating the swap partition.)
/dev/sd0a / 4.2 rw 1 1
/dev/sd0h /files 4.2 rw 1 3
/dev/sd0g /usr 4.2 rw 1 2
/dev/sd0d /files/pat 4.2 rw 1 4
/dev/fd0 /pcfs pcfs rw,noauto 0 0
/dev/sr0 /cdrom hsfs ro,noauto 0 0
nmvap:/var/spool/mail /var/spool/mail nfs rw,hard,bg 0 0

cat: auto.vol: No such file or directory
References to /vol/volume_name are translated by the auto-mount daemon using the auto.vol map,
and the directory specified in the map entry is mounted. The concept of a volume is that it is a self
contained directory hierarchy that can be NFS mounted. It is referenced using a known
volume_name. The use of an automount map is suggested so that the volume and its contents can be
referenced through /vol. This is advantageous because location-transparency (that is, which host the
volume is on) and replication of read-only volumes can be provided using the automount
mechanism.)
Note: ypcat prints out values in a Network Information Service (NIS) map specified by
mname, which may be either a map name or a map nickname. Since ypcat uses the NIS
service, no NIS server is specified. Type in:
ypcat -k auto.vol
patients_db nmvap:/export/vol/patients/patients_db
patients6 nmohsu6:/export/vol/patients/patients6
patients1 nmvap1:/export/vol/patients/
patients0 nmvap:/export/vol/patients/patients0
centor nmvap:/export/vol/patients/centor
rt11 nmvap:/export/vol/patients/rt11
mita nmvap:/export/vol/patients/mita
cat /etc/hostname.le0
-rw-rw-rw- 1 root staff 8 Jan 21 2002 /etc/hostname.le0
nmvap1
cat /etc/hostname.hme0
-rw-rw-rw- 1 root staff 9 Jan 23 2002 /etc/hostname.hme0
pegcard1
Note: File exists only on hosts specially configured with a 2nd ethernet card; file does not
exist on systems without a 2nd ethernet card.

cat: systems: No such file or directory

cat: ypservers: No such file or directory
cat /etc/modules/shared_dist_map (master only)

cat: /etc/modules/shared_dist_map: No such file or directory
cat /etc/networks
-rw-rw-rw- 1 root staff 209 Jan 21 2002 /etc/networks
(plus any aliases))
#
#
loopback 127
#
# Internet networks
#
Arpanet 10 arpa
sun-ether 152.131
hosp-ether 172.16 hospether #( 2nd ethernet card)
cat /etc/netmasks
-rw-r--r-- 1 root staff 517 Jan 21 2002 /etc/netmasks
#
# Network masks database
#
# only non-default subnet masks need to be defined here
#
# Network netmask
129.144 255.255.255.0
129.145 255.255.255.0
129.146 255.255.255.0
129.147 255.255.255.0
129.148 255.255.255.0
129.149 255.255.255.0
129.150 255.255.255.0
129.151 255.255.255.0
129.152 255.255.255.0
129.153 255.255.255.0
129.154 255.255.255.0
129.155 255.255.255.0
129.156 255.255.255.0
129.157 255.255.255.0
129.158 255.255.255.0
129.159 255.255.255.0
128.32 255.255.255.0
152.131 255.255.255.240 #-Subnet entry for this class B network .
172.16 255.255.255.0 #( 2nd ethernet subnet )
cat /etc/exports (may be different in each system)

-rw-rw-rw- 1 root staff 220 Jan 24 14:55 /etc/exports
(The /etc/exports file contains entries for directories that can be exported to NFS clients.
This file is read automatically by the exportfs(8) command. If you change this file, you must run
exportfs(8) for the changes to affect the daemon's operation. Only when this file is present at boot
time does the rc.local script execute exportfs(8) and start the NFS filesystem daemon, nfsd(8). The
/etc/xtab file contains entries for directories that are currently exported. This file should only be
accessed by programs using getexportent() (see exportent(3)). Use the -u option of exportfs to
remove entries from this file.)
/usr/adac/informix
/files/pat/camera1
/files/camera1
/etc/modules
/var/spool/pcnfs
/worm/physical/opti_nmvap1
/AtxDrv
cat /etc/install/sys_info
-rw-rw-rw- 1 root staff 300 Jan 21 2002 /etc/install/sys_info
(System Information File, Should have current system role and information.)
hostname=nmvap1
sys_type=standalone
ether_name=le0
ip=191.254.118.178
yp_type=master
domainname=vapdx
op_type=install
reboot=yes
rewind=no
arch_str=sun4.sun4m.sunos.4.1.3_U1
root=sd0a
user=sd0g
termtype=sun
timezone=PST8PDT
server=
server_ip=
exec_path=
kvm_path=
static_sizing=no
-rwxrwxrwx 1 root wheel 7846 Jun 28 12:04 /usr/adac/site/`hostname`/ADACSetup
# pegasys use.
setenv DB_SERVER nmvap #(Name of Master DB Server)
setenv DBPATH //nmvap #(Name of Master DB Server)
setenv INFORMIXDIR /usr/adac/informix
if (`hostname` != ${DB_SERVER} && "${DB_SERVER}" != "NOHOST")
setenv DATABASE_PATH /adac/patients_db/

setenv ARCHIVE_PATH /adac/patients_db/
setenv PATIENT_PATH /adac/patients0/
setenv COMMON_TEMP_PATH /vol/patients5/temp/
setenv DB_WORKING_PATH /adac/patients_db/curr/

setenv DB_CURRENT_PATH /adac/patients_db/curr/
setenv FORMAT_PATH /adac/fmttemp/
setenv CONVERT_PATH /adac/rt11/
setenv CENTOR_PATH /adac/centor/
setenv DB_SERVER nmvap #(Name of Master DB Server)
endif
setenv CENTOR_TEMPLATE_PATH ${DATA_PATH}centor/
PEGX ACQUISITION FILES

cat /etc/modules/acq.cfg
-rw-rw-rw- 1 pegasys 2568 Jul 26 1998 /etc/modules/acq.cfg
## DESCRIPTION
## The acq.cfg template developed for ADAC single-head cameras using
## release 1.1 or greater, and the macq program set instead of acq.
## Nature of changes to its format and using head1 in field 3
## makes it incompatible to run a with any Pre-1.1 single-head
## cameras on the same Pegasys unit.
-ACQ pc_stack1 head1 /dev/pegasys_acp0 /tmp/ACP_STAT.0 pc_acq.0 NM

generic cam_snum0 20015346
#-ACQ pc_nodnm1 head1 /dev/pegasys_acp1 /tmp/ACP_STAT.1 pc_acq.1 NM c_type1

cam_snum1 20025346
#-ACQ pc_nodnm2 head1 /dev/pegasys_acp2 /tmp/ACP_STAT.2 pc_acq.2 NM c_type2

cam_snum2 20035346
#-ACQ pc_nodnm3 head1 /dev/pegasys_acp3 /tmp/ACP_STAT.3 pc_acq.3 NM c_type

3 cam_snum3 20045346
##########################################
# Default config stuff for hospital
# INT# institution number
# INTNAME institution name
##########################################
-INT# Instnumb
-INTNAME Instname
-HOSTNAME nmvap
cat /etc/modules/acq_sw_config
-rw-rw-rw- 1 root staff 266 Aug 4 1998 /etc/modules/acq_sw_config
/acq_sw_cam/REVISION "1"
/acq_sw_cam/TITLE "ACQUISITION CAMERA SOFTWARE CONFIGURATION FILE"
/pc_stack1/CAMERA_DIR "camera1"
/pc_stack1/CAMERA_TYPE "generic"
/pc_stack1/SW_REV_LEV "200"
/pc_stack1/AUTO_AOR_ADJ "yes"
/pc_stack1/COR /usr/adac/pegx/data//COR/pc_stack1.cor
Note: The PegX Acqusition examples above are similar, on a Master or a Client, except
hostname, pc_stackN, and specific camera information will be different.
cat /etc/modules/adac.config
-rw-rw-rw- 1 pegasys staff 11445 Sep 26 2001 /etc/modules/adac.config
# *** ADAC Configuration Database version 6 ***

# Original Name : nmvap4:/vol/patients_db/global_adac.config
# Creation date : 98-06-19_06:50:39
# Field Ordering : CAMERA
# 2 : HEAD
# 3 : SOFTMAG
# 4 : MATRIX
# 5 : XAOR
# 6 : YSHIFT
# 7 : AOR_DATE
# 8 : UNIFORMITY
# 9 : UNI_DATE
# 10 : CALFACTOR
# 11 : CAL_DATE
# 12 : FAN_FOCAL
# 13 : FAN_FOCAL_DATE
# 14 : FAN_XAOR
# 15 : FAN_AOR_DATE
# 16 : FAN_CENTER
# 17 : FAN_CENTER_DATE
#****#
#****#
17
varble
head1
1.000000
512
%XAOR not defined
%YSHIFT not defined
%AOR_DATE not defined
008f0102
15Aug2000_08:34:47
0.581240
19980623_09:16:29
%FAN_FOCAL not defined
%FAN_FOCAL_DATE not defined
%FAN_XAOR not defined
%FAN_AOR_DATE not defined
%FAN_CENTER not defined
%FAN_CENTER_DATE not defined
#****#
17
varble
head2
1.000000
512
%XAOR not defined
%YSHIFT not defined
%AOR_DATE not defined
%UNIFORMITY not defined
%UNI_DATE not defined
0.577960
19980623_09:16:29
#****#
17
varble
head1
1.000000
64
-0.294447
35.507938
24Feb2000_16:20:16
%CALFACTOR not defined
%CAL_DATE not defined
#****#
17
varble
head2
1.000000
64
0.262424
35.643158
24Feb2000_16:20:16
%CALFACTOR not defined
%CAL_DATE not defined
Note: adac.config is a LOCAL copy of global_adac.config.

global_adac.config exists on the master pegasys in /vol/patients_db
cat /usr/adac/pegx/data//COR/pc_stack11.cor
-rw-rw-rw- 1 pegasys users 662 Sep 26 2001 /usr/adac/pegx/data/COR/pc_stack11.cor
# Version 1.00
Filename : pc_stack11.cor
#
/VXHR/head1/90
date = 21 Jul 99
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 997l0d02
start angle = 180
degrees of rotation = 360
clockwise = 1
x mean = -0.09
y mean = -0.00
number of yshift value = 1
yshift = 30.43
number of xaor values = 1
xaor = -0.09
uniformity = %UNIFORMITY not defi
#0000#
/VXHR/head2/90
date = 21 Jul 99
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 997l0d03
start angle = 270
clockwise = 1
x mean = 0.21
y mean = -0.00
yshift = 30.57
xaor = 0.21
#0000#
/LEHR/head1/180
date = 21 Jul 99
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 997l0d05
start angle = 180
clockwise = 1
x mean = -0.11
y mean = 0.00
yshift = 32.48
xaor = -0.11
#0000#
/LEHR/head2/180
date = 21 Jul 99
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 997l0d06
start angle = 0
clockwise = 1
x mean = 0.07
y mean = -0.00
yshift = 32.60
xaor = 0.07
#0000#
#0000#
#0000#
EPIC DETECTORS ON A PEGX CAMERA

cat /usr/local/matador/etc/bootptab
-rw-rw-rw- 1 bin users 655 May 30 2001 /usr/local/matador/etc/bootptab
#
# file: bootptab
# purpose: configuration file for bootp daemon on UNIX
# created: 25-Sep-94
# property of ADAC Laboratories
#
# revision history:
# 25-Sep-94 Doug Murray initial version; derived from VxWorks
recommended version
#
# $Header: /usr/local/adacpool/matador/src/util/bootp/bootptab,v 1.4 1994/09/25
23:31:06 dougm Beta $
#
global.matador:\
:sm=255.255.255.0:hn:vm=rfc1048:\
:hd=/usr/local/matador/lib:bf=matador:
sample1:ht=ethernet:ha=080000000001:ip=192.9.200.78:tc=global.matador
adacdet1:ht=ethernet:ha=08003e229c5f:ip=192.9.200.78:tc=global.matador
adacdet2:ht=ethernet:ha=08003e229c6f:ip=192.9.200.79:tc=global.matador
Note: Host names, Ethernet addresses, IP addresses and Netmask value are examples only,
yours may be different. Beware, inaccurate addresses result in boot and runtime errors.
PEGX ACQUISITION PC NETWORK FILES

The network files for a PegX PC reside on the PC boot floppy. To look at the network files
on the PC boot floppy, follow these steps:
• Have the Acquisition PC booted to the Main Menu

• Exit to DOS, then type
a:
cd \nfs
dir
§ The system will display the NFS directory. Ensure files drives.bat,
network.bat and hosts files appear in the directory.
type drives.bat
net use d:\\adac\files\camera1
net use e:\\adac\etc\modules
type network.bat
net nisdomain YP.pegasys
net start rdr pc_stack1 *
net subnet 255.255.255.192
net nisset adac
net pcnfsd adac
Note: The subnet line will only appear if you have a custom subnet mask. If you need to
add a subnet netmask, use a DOS text editor to insert a "net subnet" line as shown above
which includes your custom subnet mask. Use EDLIN editor for DOS version 5 and
below. Use EDIT editor for DOS version 6 and above.
type hosts
192.9.200.1 adac
192.9.200.2 pc_stack1
ULTRA MASTER FILES
These are the network files you will see on a PegUltra. In this example, the Master has a
second ethernet card installed.
cat /.rhosts
-rw-rw-rw- 1 root other 14 Sep 26 2000 /.rhosts
while individual users can maintain their own .rhosts files in their home directories.
These files bypass the standard password-based user authentication mechanism. To maintain
system security, care must be taken in creating and maintaining these files.)
adac
adac1
adac2
adac3
adac4
atlas1
+ +
cat /etc/hosts
lrwxrwxrwx 1 root other 15 Nov 8 1999 /etc/hosts -> /etc/inet/hosts
-rw-r--r-- 1 pegasys users 152 Oct 3 2000 /etc/inet/hosts
Programs use library interfaces to access information in the hosts file.
The hosts file has one entry for each IP address of each host. If a host has more than one IP
address, it will have one entry for each, on consecutive lines.)

192.9.200.1 adac timehost timehost
192.9.200.10 atlas1
192.9.200.2 adac1
192.9.200.20 atlas2
192.9.200.3 adac2
192.9.200.4 adac3
192.9.200.40 atlas4
192.9.200.5 adac4
192.9.200.50 ep1650
192.9.200.30 atlas3
172.16.32.63 pegcard1 #( 2nd ethernet card )

-rw-rw-rw- 1 root other 30 Nov 8 1999 /etc/peghosts
these values.)
adac ACQ:n NIS:m DB:m SHD:m

adac1 ACQ:n NIS:s DB:c SHD:n
cat /etc/ethers
-rw-rw-rw- 1 root other 116 Nov 8 1999 /etc/ethers
Ethernet.)

8:0:20:8d:29:1 adac
8:0:20:8f:21:76 adac1
8:0:20:89:ef:8c adac3
8:0:20:8f:d4:64 adac2
8:0:20:85:d2:50 adac4
cat /etc/networks
lrwxrwxrwx 1 root root 15 Apr 12 1999 /etc/networks -> ./inet/networks
-rw-rw-rw- 1 root other 394 Nov 8 1999 /etc/inet/networks
(plus any aliases))
#ident "@(#)networks 1.4 92/07/14 SMI" /* SVr4.0 1.1 */

#
# The networks file associates Internet Protocol (IP) network numbers
# with network names. The format of this file is:
loopback 127
sun-ether 192.9.200 sunether ethernet localnet
#Internet networks
arpanet 10 arpa
hosp-ether 172.16 hospether ( 2nd ethernet card in this system)
line “arpanet 10 arpa” from the networks file.
cat /etc/netmasks
lrwxrwxrwx 1 root root 15 Apr 12 1999 /etc/netmasks -> ./inet/netmasks
-r--r--r-- 1 root sys 567 Apr 12 1999 /etc/inet/netmasks
#
# The netmasks file associates Internet Protocol (IP) address
# masks with IP network numbers.
#
# network-number netmask
#
# The term network-number refers to a number obtained from the Internet Network
# Information Center. Currently this number is restricted to being a class
# A, B, or C network number. In the future we should be able to support
# arbitrary network numbers per the Classless Internet Domain Routing
# guidelines.
#
# Both the network-number and the netmasks are specified in
# "decimal dot" notation, e.g:
#
# 128.32.0.0 255.255.255.0
#
172.16.0.0 255.255.255.0 #( 2nd ethernet card subnet )
Note: See Chapter 2: IP Subnetting for information on subnet rules.
cat /etc/defaultrouter (Default router on joined subnet)

-rw-rw-rw- 1 root other 14 Jul 23 11:53 /etc/defaultrouter
172.16.32.1
file.
cat /etc/aliases
lrwxrwxrwx 1 root other 17 Nov 8 1999 /etc/aliases -> /etc/mail/aliases
-rw-r--r-- 1 pegasys users 1389 Nov 8 1999 /etc/mail/aliases
##
#
#
# @(#)aliases 1.10 89/01/20 SMI
##
Postmaster: root
nobody: /dev/null
# Sample aliases:
#epa:eric
#######################
#######################
manager:manager@adac
users:manager,diag,informix,rt11,pegasys
diag:diag@adac
informix:informix@adac
rt11:rt11@adac
pegasys: peglist
peglist: pegadac, pegadac1, pegadac2
pegadac: /var/mail/pegasys_adac
pegadac1: /var/mail/pegasys_adac1
pegadac2: /var/mail/pegasys_adac2
cat /etc/vfstab (Ultra-1 example, 2 hard drives)

-rw-rw-r-- 1 root sys 951 Apr 12 1999 /etc/vfstab
(The file /etc/vfstab describes defaults for each file system. The information is stored in a
table with the following column headings:
device device mount FS fsck mount mount

to mount to fsck point type pass at boot options
The fields in the table are space-separated and show the resource name (device to mount), the
raw device to fsck (device to fsck), the default mount directory (mount point), the name of the file
system type (FS type), the number used by fsck to decide whether to check the file system
automatically (fsck pass), whether the file system should be mounted automatically by mountall
(mount at boot), and the file system mount options (mount options). (See respective mount file
system man page below in SEE ALSO for mount options.) A '-' is used to indicate no entry in a
field. This may be used when a field does not apply to the resource being mounted.) Remember the
“ctds” in the disk descriptions in the device column stands for the following: c = controller;
t = target; d = disknumber; s = slice. A slice is what we referred to in 4.1.3u1 as a partition.
#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /usr ufs 1 no -
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /opt ufs 2 yes -
/dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0s6 /files ufs 2 yes -
/dev/dsk/c0t1d0s7 /dev/rdsk/c0t1d0s7 /files/pat ufs 2 yes -
swap - /tmp tmpfs - yes -
/dev/dsk/c0t5d0s2 /dev/rdsk/c0t5d0s2 /zip ufs - no -
/dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0s2 /cdrom/cdrom0 hsfs 4 no ro
/dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0s2 /cdrom hsfs 4 no ro
/dev/diskette /dev/rdiskette /pcfs pcfs 4 no rw

-rw-rw-rw- 1 root other 1863 Nov 8 1999 /etc/auto.vol
References to /vol/volume_name are translated by the auto-mount daemon using the auto.vol map,
and the directory specified in the map entry is mounted. The concept of a volume is that it is a self
contained directory hierarchy that can be NFS mounted. It is referenced using a known
volume_name. The use of an automount map is suggested so that the volume and its contents can be
referenced through /vol. This is advantageous because location-transparency (that is, which host the
volume is on) and replication of read-only volumes can be provided using the automount
mechanism.)
## DESCRIPTION
## template for NIS map auto.vol that is copied and sed'ed
## to replace adac with the master NIS servers hostname upon install
patients_db adac:/export/vol/patients/patients_db
patients0 adac:/export/vol/patients/patients0
rt11_1 adac:/export/vol/patients/rt11_1
centor adac:/export/vol/patients/centor
rt11 adac:/export/vol/patients/rt11
mita adac:/export/vol/patients/mita
patients1 adac1:/export/vol/patients/patients1
cat /etc/nodename
-rw-r--r-- 1 root other 6 Nov 16 2002 /etc/nodename
adac
-rw-rw-rw- 1 root other 6 Nov 8 1999 /etc/hostname.hme0
adac
-rw-rw-rw- 1 root other 6 Jul 23 11:52 /etc/hostname.hme1
pegcard1 # contains hostname of 2nd ethernet card
Note: File exists only on hosts specially configured with a 2nd ethernet card; file does not
exist on systems without a 2nd ethernet card.

-rw-rw-rw- 1 root other 1352 Nov 8 1999 /etc/systems
## NAME
## systems.sun4
## DESCRIPTION
## an NIS map ADAC carried over from the 386i to the Sparc to keep
## track of hostname arch os and NIS role
## although some parts supplanted by the new peghosts map for rel200
## some scripts still make use of the information contained herin
adac sun4c sunos4.1.1 "" -1 -1 master_bootserver
atlas1 pcnfs unknown "" -1 -1 network_client
adac1 sun4c sunos4.1.1 "" -1 -1 slave_bootserver

-rw-r--r-- 1 root other 6 Nov 8 1999 /etc/ypservers
## USAGE
## this is a data file installed to /etc/ypservers and used to make
## NIS maps on the master machine and push them out to all the slaves
adac
adac1
adac3
adac2
adac4
cat /etc/modules/shared_dist.map (master only)

-rw-r--r-- 1 root other 4591 Nov 8 1999 /etc/modules/shared_dist.map
## NAME
## shared_dist.map
## DESCRIPTION
## A template for the rdist file that will be distributed
## for shared_files rule from the peghosts--> SHD:m to SHD:s machines
files/dirs to be backed up fairly often as they are important and dynamic
# these are ok to push to other PegX and PegMD use MIRROR_SLAVE_HOST now
SHARED_FILES_1HR = (
/files/vol/patients/patients_db/curr/OBJK.lock
/files/vol/patients/patients_db/formatcap
/files/vol/patients/patients_db/periph.rsc
/files/vol/patients/patients_db/partitions.map
/files/vol/patients/patients_db/tbconfig
/files/vol/patients/patients_db/tbparam
# This files are mirrored, not disributed in place to functional locations
# They will be backed up once a day
ETC_MIRROR_FILES_24HRS = (
/etc/mail/aliases
/etc/auto.home
/etc/auto_home
/etc/auto.master
/etc/auto_master
/etc/auto.vol
/etc/bootparams
/etc/ethers
/etc/group
/etc/hosts
/etc/inetd.conf
/etc/rc3.d
/etc/magic
/etc/netgroup
/etc/nsswitch.conf
/etc/netmasks
/etc/networks
/etc/passwd
/etc/peghosts
/etc/protocols
/etc/publickey
/etc/remote
/etc/rpc
/etc/mail/sendmail.cf
/etc/services
/etc/shadow
/etc/system
/etc/systems
/etc/ypservers
/etc/uucp
cat /etc/dfs/dfstab
-rw-r--r-- 1 root other 890 Nov 8 1999 /etc/dfs/dfstab
(dfstab resides in directory /etc/dfs and contains commands for sharing resources across a
network. dfstab gives a system administrator a uniform method of controlling the automatic sharing
of local resources. Each line of the dfstab file consists of a share(1M) command. The dfstab file
can be read by the shell to share all resources. System administrators can also prepare their own shell
scripts to execute particular lines from dfstab. The contents of dfstab are executed automatically
when the system enters run-level 3)
# place share(1M) commands here for automatic execution

# on entering init state 3.
#
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -F nfs -o rw /files/vol/patients/patients_db
share -F nfs -o rw /var/mail
share -F nfs -o rw /files/pat/patients/patients0
share -F nfs -o rw /files/pat/patients/rt11_1
share -F nfs -o rw /files/pat/patients/centor
share -F nfs -o rw /files/pat/patients/rt11
share -F nfs -o rw /files/pat/patients/mita
share -F nfs -o rw /usr/adac/informix
cat /etc/dfs/sharetab
-rw-r--r-- 1 root root 427 Nov 5 2001 /etc/dfs/sharetab
(sharetab resides in directory /etc/dfs and contains a table of local resources shared by the
share command. Each line of the file consists of the following fields:
pathname resource fstype specific_options description
where
pathname Indicates the path name of the shared resource.
resource Indicates the symbolic name by which remote systems can access the resource.
fstype Indicates the file system type of the shared resource.
specific_options Indicates file-system-type-specific options that were given to the share command
when the resource was shared.
description Describe the shared resource provided by the system administrator when the resource
was shared.)
/files/pat/patients/rt11_1 - nfs rw
/files/pat/patients/centor - nfs rw
/files/pat/patients/rt11 - nfs rw
/files/pat/patients/mita - nfs rw
/opt/adac/act/informix - nfs rw
/files/vol/patients/patients_db - nfs rw
/files/pat/patients/patients0 - nfs rw
/var/mail - nfs rw
Note: sharetab is a dynamically created file from dfstab.
-rw-rw-rw- 1 root root 6556 Nov 5 2001 /usr/adac/site/`hostname`/ADACSetup
# pegasys use.
The line to look for is setenv DB_SERVER adac (just past 40%)
setenv DB_SERVER adac #(Name of DataBase master)
setenv DBPATH //adac #(Name of DataBase master)

cat /vol/patients_db/partitions.map
-rw-rw-rw- 1 pegasys users 227 Apr 12 1999 /vol/patients_db/partitions.map
0 1 80 90 /vol/rt11_1
0 1 80 90 /vol/rt11_2
0 1 80 90 /vol/rt11_3
0 1 80 90 /vol/rt11_4
0 1 80 90 /vol/rt11_5
0 1 80 90 /vol/centor
0 1 80 90 /vol/rt11
0 1 80 90 /vol/mita
Note: partitions.map file exists on network master, is shared to all clients.
ULTRA CLIENT FILES

cat /.rhosts
-rw-rw-rw- 1 root other 98 Jun 12 08:22 /.rhosts
while individual users can maintain their own .rhosts files in their home directories.
These files bypass the standard password-based user authentication mechanism. To maintain
system security, care must be taken in creating and maintaining these files.)
adac
adac1
adac2
adac3
adac4
atlas3
+ +
cat /etc/hosts
lrwxrwxrwx 1 root root 15 Nov 2 1999 /etc/hosts -> /etc/inet/hosts
-rw-r—r-- 1 root other 78 Oct 9 2001 /etc/inet/hosts

192.9.200.2 adac1
192.9.200.1 adac timehost loghost
192.9.200.30 atlas3

cat: peghosts: No such file or directory
these values.)
mname, which may be either a map name or a map nickname. Since ypcat uses the NIS
service, no NIS server is specified. To look at the network-wide peghosts database,
peghosts.byname, (with the nickname peghosts), type in:
ypcat peghosts.byname
adac ACQ:n NIS:m DB:m SHD:m
cat /etc/ethers
-rw-rw-rw- 1 root other 23 Jul 7 2000 /etc/ethers
Ethernet.)
8:0:20:89:eb:bb adac1
cat /etc/networks
lrwxrwxrwx 1 root root 15 Nov 2 1999 /etc/networks -> ./inet/networks
-rw-rw-rw- 1 root staff 212 May 4 1999 /etc/inet/networks
(plus any aliases))
#
#
loopback 127
#
# Internet networks
#
arpanet 10 arpa
sun-ether 192.9.200
line “arpanet 10 arpa” from the networks file.
cat /etc/netmasks
lrwxrwxrwx 1 root root 15 Nov 2 1999 /etc/netmasks -> ./inet/netmasks
-r--r--r-- 1 root sys 567 Nov 2 1999 /etc/inet/netmasks
#
#
#
# guidelines.
#
#
# 128.32.0.0 255.255.255.0
#
Note: See chapter 2 for information on subnet rules.
cat /etc/defaultrouter (Default router on joined subnet)
-rw-rw-rw- 1 root other 14 Jul 23 11:53 /etc/defaultrouter
172.16.32.1
file.
cat /etc/aliases
lrwxrwxrwx 1 root other 17 Nov 8 1999 /etc/aliases -> /etc/mail/aliases
-rw-r--r-- 1 pegasys users 1389 Nov 8 1999 /etc/mail/aliases
##
#
#
# @(#)aliases 1.10 89/01/20 SMI
##
Postmaster: root
nobody: /dev/null
# Sample aliases:
#epa:eric
#######################
#######################
cat /etc/vfstab (Ultra 60 example)

-rw-rw-r-- 1 root sys 951 Apr 12 1999 /etc/vfstab

field. This may be used when a field does not apply to the resource being mounted.) Remember the
“ctds” in the disk descriptions in the device column stands for the following: c = controller;
t = target; d = disknumber; s = slice. A slice is what we referred to in 4.1.3u1 as a partition.

#
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /files ufs 2 yes -
/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /files/pat ufs 2 yes -
/dev/dsk/c0t6d0s2 - /cdrom/cdrom0 hsfs - no ro
/dev/dsk/c0t6d0s2 - /cdrom hsfs - no ro
/dev/diskette - /pcfs pcfs - no rw

cat: cannot open /etc/auto.vol
References to /vol/volume_name are translated by the auto-mount daemon using the auto.vol
map, and the directory specified in the map entry is mounted.
The concept of a volume is that it is a self contained directory hierarchy that can be NFS
mounted. It is referenced using a known volume_name. The use of an automount map is
suggested so that the volume and its contents can be referenced through /vol. This is
advantageous because location-transparency (that is, which host the volume is on) and replication of
read-only volumes can be provided using the automount mechanism.)
mname, which may be either a map name or a map nickname . Since ypcat uses the NIS
service, no NIS server is specified. Type in:
ypcat -k auto.vol
patients_db adac:/export/vol/patients/patients_db
patients0 adac:/export/vol/patients/patients0
centor adac:/export/vol/patients/centor
rt11 adac:/export/vol/patients/rt11
mita adac:/export/vol/patients/mita
cat /etc/nodename
-rw-r--r-- 1 root other 6 Nov 16 2002 /etc/nodename
adac1
-rw-rw-rw- 1 root other 6 Nov 8 1999 /etc/hostname.hme0
adac1
-rw-rw-rw- 1 root other 6 Jul 23 11:52 /etc/hostname.hme1
pegcard1 # contains hostname of 2nd ethernet card

cat: systems: No such file or directory

cat: ypservers: No such file or directory
cat /etc/modules/shared_dist_map (master only)
cat: cannot open /etc/modules/shared_dist_map
cat /etc/dfs/dfstab
-rw-rw-rw- 1 root other 822 Dec 7 2000 /etc/dfs/dfstab
# place share(1M) commands here for automatic execution

#
# .e.g,
share -F nfs -o rw /files/pat/patients/patients1
share -F nfs -o rw /files/pat/patients/centor
share -F nfs -o rw /files/pat/patients/rt11
share -F nfs -o rw /files/pat/patients/mita
share -F nfs -o rw /usr/adac/informix
share -F nfs -o rw -d “ETC_MoDuLeS” /etc/modules
-rw-r--r-- 1 root root 440 Jun 26 10:31 /etc/dfs/sharetab
… where

description Describes the shared resource provided by the system administrator when the resource
was shared.)
/files/pat/patients/centor - nfs rw
/files/pat/patients/rt11 - nfs rw
/files/pat/patients/mita - nfs rw
/opt/adac/act/informix - nfs rw
/etc/modules - nfs rw EtC_MoDuLeS
/files/pat/patients/patients1 - nfs rw
Note: sharetab is a dynamically created file from dfstab.
-rw-rw-rw- 1 root other 7415 Nov 2 2001 /usr/adac/site/`hostname`/ADACSetup
# pegasys use.
The line to look for is setenv DB_SERVER adac (just past 40%)
setenv DBPATH //adac #(Name of DataBase master)

ATLAS FILES WITH A FORTE CAMERA ATTACHED

This example is for a system named atlas1
cat /etc/hosts
lrwxrwxrwx 1 root root 18 Nov 12 1998 /etc/hosts -> /etc/inet/hosts
-r--r--r-- 1 root sys 233 Feb 23 1999 /etc/inet/hosts
#
# Internet host table
#
127.0.0.1 localhost
192.9.200.1 adac
192.9.200.240 atlas1
192.9.200.241 pc_atlas1
192.9.200.248 atlas1det1 Detector1
192.9.200.249 atlas1det2 Detector2
192.9.200.242 atlas1gantry Gantry
cat /etc/ethers
-rw-r--r-- 1 root other 89 Feb 25 1999 /etc/ethers
Ethernet.)
00:40:05:73:46:b1 pc_atlas1
00:40:05:73:44:af atlas1gantry
08:00:3e:2f:2d:fd atlas1det1
08:00:3e:01:5f:b8 atlas1det2
cat /etc/networks
lrwxrwxrwx 1 root root 15 Nov 12 1998 /etc/networks -> ./inet/networks
-r--r--r-- 1 root sys 389 Feb 23 1999 /etc/inet/networks
(plus any aliases))
#ident "@(#)networks 1.4 92/07/14 SMI" /* SVr4.0 1.1 */

#
# The networks file associates Internet Protocol (IP) network numbers
# with network names. The format of this file is:
#
# network-name network-number nicnames . . .
#
#
# The loopback network is used only for intra-machine communication
#
loopback 127
#
# Internet networks
#
arpanet 10 arpa # Historical
cat /etc/netmasks
lrwxrwxrwx 1 root root 15 Nov 12 1998 /etc/netmasks -> ./inet/netmasks
-r--r--r-- 1 root sys 563 Feb 25 1999 /etc/inet/netmasks
#
#
#
# guidelines.
#
#
#
192.9.200.0 255.255.255.0
Note: See Chapter 2: IP Subnetting for information on subnet rules.
cat /etc/aliases
lrwxrwxrwx 1 root root 14 Nov 12 1998 /etc/aliases -> ./mail/aliases
-rw-r--r-- 1 root bin 1201 Nov 12 1998 /etc/mail/aliases
(These files contain mail addresses or aliases, recognized by sendmail(1M) for the local host)
#ident "@(#)aliases 1.13 92/07/14 SMI" /* SVr4.0 1.1 */

##
#
#
# @(#)aliases 1.8 86/07/16 SMI
##
Postmaster: root

nobody: /dev/null
# Sample aliases:
#epa:eric
#######################
#######################
cat /etc/vfstab
-rw-rw-r-- 1 root sys 640 Nov 12 1998 /etc/vfstab

field. This may be used when a field does not apply to the resource being mounted.)

#
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /var ufs 1 no -
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /export/home ufs 2 yes -
/dev/dsk/c0t6d0s0 /dev/rdsk/c0t6d0s0 /cdrom hsfs - no -
-rw-r--r-- 1 root root 8 Feb 25 1999 /etc/hostname.hme0
atlas1
cat /etc/dfs/dfstab
-rw-r--r-- 1 root sys 445 Nov 12 1998 /etc/dfs/dfstab
# Place share(1M) commands here for automatic execution

#
# Issue the command '/etc/init.d/nfs.server start' to run the NFS
# daemon processes and the share commands, after adding the very
# first entry to this file.
#
# .e.g,
share -F nfs -o rw /export/home/atlas/files/camera1
share -F nfs -o rw /export/home/atlas/files/pat/gantry
-rw-r--r-- 1 root root 43 Jul 22 07:00 /etc/dfs/sharetab
… where
description Describes the shared resource provided by the system administrator when the resource
was shared.)
/export/home/atlas/files/camera1 - nfs rw
/export/home/atlas/files/pat/gantry - nfs rw
Note: sharetab is a dynamically created file from dfstab. If corrupted, delete and reboot.
cat /usr/local/matador/etc/bootptab
-rwxr-xr-x 1 root other 363 Feb 25 1999 /usr/local/matador/etc/bootptab
.global.gantry::sm=255.255.255.0:hn:vm=rfc1048:to=480:hd=/usr/local/gantry/lib:bf
=vxBoot.img:
.global.matador::sm=255.255.255.0:hn:vm=rfc1024:to=480:hd=/usr/local/detector/lib
:bf=matador:
.global.detector::sm=255.255.255.0:hn:vm=rfc1024:to=960:hd=/usr/local/detector/li
b:bf=vxWorks:
station1:ht=ethernet:ip=192.9.200.241:ha=0040057346b1:hd=/export/home/atlas/files
/camera1/bootp:bf=station1.img
atlas1gantry:ht=ethernet:ha=0040057344af:ip=192.9.200.242:tc=.global.gantry
atlas1det1:ht=ethernet:ha=08003e2f2dfd:ip=192.9.200.248:tc=.global.matador
atlas1det2:ht=ethernet:ha=08003e015fb8:ip=192.9.200.249:tc=.global.matador
Note: Host names, Ethernet addresses, IP addresses and Netmask value are examples
only, yours may be different. Beware, inaccurate addresses result in boot and runtime
errors.
cat /export/home/atlas/etc/site.config
-rwxrwxrwx 1 atlas root 809 Jul 23 13:16 /export/home/atlas/etc/site.config
#
# this is the default Site Configuration file.
# measurements are cm, except where noted.
#
sitename "Comm Hosp of NeverLand"
servernode "atlas1"
clientnode "pc_atlas1"
databasenode "adac"
device "Forte"
devicetype "Forte"
modality "NM"
serialnumber "atlas-97001"
focallength "200.000000"
detectors 2
detectorname 1 "Detector1"
pixelcal 1 "0.595930"
axisrotation 1 "0.062519"
crystaldepth 1 "2.240000"
sourcewindow 1 "130.0000"
emissionwindow 1 "130.0000"
detectorname 2 "Detector2"
pixelcal 2 "0.599600"
axisrotation 2 "0.062519"
crystaldepth 2 "2.240000"
sourcewindow 2 "130.0000"
emissionwindow 2 "130.0000"
cat /export/home/atlas/etc/acq_sw_config
-rwxrwxrwx 1 atlas users 57 Feb 25 1999 /export/home/atlas/etc/acq_sw_config
/pc_atlas1/COR "/export/home/atlas/data/pc_atlas1.COR"
cat /export/home/atlas/data/pc_atlas1.COR
-rwxrwxrwx 1 atlas users 1213 Jul 23 13:16 /export/home/atlas/data/pc_atlas1.COR
# Version 1.00
Filename : pc_atlas1.cor
#
/VXGP/head1/90
date = 12Dec2000
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 00cc0300
start angle = 90
clockwise = -1
x mean = -0.01
y mean = 0.00
yshift = 34.51
xaor = -0.01
uniformity =
#0000#
/VXGP/head2/90
date = 12Dec2000
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 00cc0301
start angle = 180
clockwise = -1
x mean = 0.03
y mean = -0.00
yshift = 34.42
xaor = 0.03
uniformity =
#0000#
/INTR/head1/180
date = 07Dec2000
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 00c70300
start angle = 180
clockwise = -1
x mean = 0.01
y mean = -0.00
yshift = 30.08
xaor = 0.01
uniformity =
#0000#
/VXGP/head2/180
date = 07Dec2000
time =
softmag = 1.0
matrix = 64
pixdepth = 16
srcfile = 00c70301
start angle = 0
clockwise = -1
x mean = -0.01
y mean = 0.00
yshift = 30.20
xaor = -0.01
uniformity =
#0000#
#0000#
#0000#
Skylight Files
SAMPLE “BOOTPTAB” SKYLIGHT EPIC DETECTORS & GANTRY PC

-rw-r--r-- 1 root other 402 Jul 19 10:53 /etc/bootptab
atlas@165.114.41.214:10 > cat /etc/bootptab

.global.gantry::sm=255.255.255.0:hn:vm=rfc1048:to=480:hd=/opt/gantry/lib
:bf=vxB:
cameragantry:ht=ethernet:ha=00400573fe63:ip=192.168.1.15:tc=.global.gantry
.global.detector::sm=255.255.255.0:hn:vm=rfc1024:to=960:hd=/opt/detector/lib:bf:
cameradet1:ht=ethernet:ha=0001af036e79:ip=192.168.1.13:tc=.global.detector
cameradet2:ht=ethernet:ha=0001af0378b6:ip=192.168.1.14:tc=.global.detector
DORMANT “BOOTPTAB” FILE FOR SKYLIGHT GANTRY

-rwxrwxrwx 1 atlas users 516 Feb 6 2001 /opt/gantry/etc_skylight/bootptab
Note: You should disregard the following file as it was part of the Skylight development
process (notice the empty value for the MAC address "ha=:"). When examining the
Skylight configuration you should ONLY consider the file in the /etc directory (see
sample above).
atlas@165.114.41.214:9 > more /opt/gantry/etc_skylight/bootptab

#
# file: bootptab
# purpose: VxWorks bootp configuration;
# created: 05-Feb-01
# property of ADAC Laboratories
#
#
# revision history:
# 05-Feb-01 Ron Koops Initial version
#
#
# $Header:
/usr/adac/Repository/camera/camera/gantry/argos/etc_skylight/bootpta$
#
.global.gantry::sm=255.255.255.0:hn:vm=rfc1048:\:hd=/opt/gantry/lib:bf=vxBoot.img
:\:to=480:
cameragantry:ht=ethernet:ha=:ip=192.168.1.15:tc=.global.gantry
DETERMINE SKYLIGHT “CAMERANAME”

Do this on the DATABASE_HOST Pegasys for the Skylight in a UNIX window:
Type: ypcat hosts
You will see something like the following:
pegasys@adac:/usr/adac/pegasys# ypcat hosts

165.114.43.154 ps_printer
165.114.41.242 adac timehost
165.114.41.103 cygnus
165.114.41.112 camera
165.114.41.242 adac timehost
165.114.41.182 camera@165.114.41.182
Ultra network with a Ultra Master (as seen above). This is normal and due to the method
in which the "makedbm" program generates the maps on the master Pegasys. For large
networks, you might consider filtering out duplicate entries by issuing the following
alternative: "ypcat hosts | sort –u"
telnet into Atlantis ( Skylight ) You can not “rsh” or “rlogin” thru the Linksys Router.
telnet <cameraname> (e.g., telnet camera@165.114.41.182)
login: atlas
password: atlas
ETHERNET SWITCH/ROUTER IN PC TOWER
1. A reboot of the axi in pc tower loads proper switch set-up parameters.

2. A reset of the switch using reset 4sec pressed in, on the switch causes Manufacturer default
settings to be loaded.
3. The switch is programmed in such a way as to allow the acquisition pc to ping the database host
but the atlas cannot be pinged from the ultra database host.
4. Diagnostic connections to the atlas from the ultra database host can be accomplished via the
telnet, echo, or ftp protocols.
5. The connection between switch and ultra workstation utilizes a crossover cat-5 cable.
Sample telnet session from Ultra workstation
1. On workstation open a Unix window

2. Type telnet atlas1
3. Login type atlas
4. Password type atlas
5. Type cd /etc
6. Type cat hosts
System response:
127.0.0.1 localhost
192.168.1.12 cameraclient (acquisition pc)
192.168.1.11 camera loghost (sun axi)
192.168.1.15 cameragantry (gantry pc)
192.168.1.13 cameradet1 (detector #1)
192.168.1.14 cameradet2 (detector #2)
Notes:
A. This IP addressing scheme will always be the same regardless of the number of cameras
installed on the network. This is due to the fact that each acquisition string (sun axi,
acqusition pc, gantry pc, cameradet1, cameradet2) are a network unto themselves and
unreachable from the outside world except via telnet, echo or ftp.
B. The Ultra workstations can have custom IP addressing schemes and can communicate with
the outside world.
IP ADDRESS FOR WAN PORT OF SKYLIGHT ROUTER

The configuration tool creates a file that contains the IP address that is assigned to the external WAN
port of the Skylight Router. This assignment happens each time the Ultra-Axi motherboard is
rebooted.
-rw-rw-rw- 1 atlas users 13 Jul 19 10:49 /etc/externalip.temp
Type the following at the root prompt:
pegasys@161.88.8.111:11 > cat /etc/externalip.temp
The system will display the following:
161.88.8.111
NETMASK FOR WAN PORT OF SKYLIGHT ROUTER

The configuration tool updates the /etc/netmasks file that contains the entry for the netmask that is
assigned to the external WAN port of the Skylight Router. This assignment happens each time the
Ultra-Axi motherboard is rebooted. The entry will be the one with #NETWORKID in it.
-rw-r--r-- 1 root other 62 Jul 19 10:49 /etc/netmasks
Type the following at the root prompt:
pegasys@161.88.8.111:11 > cat /etc/netmasks
192.168.1.0 255.255.255.0
161.88.0.0 255.255.252.0 #NETWORKID
DISPLAY THE SOFTWARE PACKAGES AND VERSIONS

To List packages loaded, type the following at the root prompt:
root@165.114.224.1> pkginfo - | grep ADAC <Enter>
system ADACbin binner software

system ADACcamd camera diagnostics software
system ADACdet detector software
system ADACgant gantry software
system ADACserv control software
system ADACticd ADAC TIC-driver software
system ADACtouch Skytouch
system ADACutil util libs
system ADACvbc visibroker software
DISPLAY SW VERSION LOADED

At the root prompt, type the following:
root@165.114.224.1> versions <Enter>
System: camera
sunOS 5.8 SUNW, UltraSPARC -IIi-Engine
Manager: Version1.0 (Atlantis110R02)
Publisher: Version1.0 (Atlantis110R02)
Binner: Version 8.0b (Atlantis110R02)
Gantry: Version1.0.0 (Atlantis110R02)
Detector: Atlantis110R02
Controller: Atlantis110R02
Data Server: Atlantis110R02
The following files are backed up: ( using Backup script )

(all detection calibrations)
/opt/detector/data [All Detector files, energy,linearity,tbstat]
/opt/gantry/etc/*.local [config.barf.local & config.devices.local]
~atlas/data/Facility.<Facilityname>
system_config (all files) [/export/home/atlas/etc/ IP & MAC Info ]
COR files in ~atlas/data/Calibration/Correction [ COR & CORQA files ]
~atlas/tic/adactic.config [tic driver config file ]
When the backup is complete, the following message appears:
Done.
CHANGING DATE AND TIME

Login as root.
console login: root <Enter>
Password: adacsu <Enter>
Enter the new date and time by typing the following at the prompt:
root> camera# ./chg_tz_date <Enter>
FILE FOR DATABASEHOST OF ATLAS

On an old atlas system, when I was looking for the name of the database host, I would always look at
the site.config file for the information. The same file on the Skylight just says "databasehost". To find
the name of the database host for a Skylight camera, do the following.
-rw-r--r-- 1 root other 409 Jul 19 13:30 /var/named/ns.camera
telnet <cameraname>
login: atlas
password: atlas
cd /var/named
cat ns.camera
The hostname will be visible near the bottom of the file.
Example:
telnet camera@165.114.41.182
login: atlas
Password: atlas
Last login: Mon Oct 8 15:01:10 from camera1
#####
# # ## # # ###### ##### ##
# # # ## ## # # # # #
# # # # ## # ##### # # # #
# ###### # # # ##### ######
# # # # # # # # # # #
##### # # # # ###### # # # #
atlas@165.114.41.182:1 >cd /var/named

atlas@165.114.41.182:2 >cat ns.camera
@ IN SOA camera.ns.cam
2000082401 ; serial
3600 ; refresh
900 ; retry
1209600 ; expire
43200 ; default_ttl
)
NS camera
;
; Put the static addresses here. This should not change
;
localhost A 127.0.0.1
camera A 192.168.1.11
linksys A 192.168.1.1
;
; Put the external addresses after here.
;
eng242 A 165.114.41.242 ;dbhostnameip
databasehost CNAME eng242
SKYLIGHT GANTRY LOG FILES

-rwxrwxrwx 1 atlas users 105385 Jul 24 16:10 LOG.debugging
-rwxrwxrwx 1 atlas users 738 Jul 23 20:57 LOG.debugging.0
-rwxrwxrwx 1 atlas users 410499 Jul 24 16:10 LOG.messages
-rwxrwxrwx 1 atlas users 493484 Jul 23 21:59 LOG.messages.0
cd /opt/gantry/data/Logfiles
ls
LOG.debugging
LOG.debugging.??
LOG.messages
LOG.messages.?
Chapter 7: File Editors
This Appendix describes the essential commands for the following file editors:
I. EMACS Editor
II. EDLIN Editor
III. VI Editor
IV. Cheatsheet for the VI Editor
File Editors
EMACS EDITOR
EMACS is a comprehensive editor. It will edit files created in DOS version 6.0 and above.
The following is a list of the essential commands which you can execute while holding the control
key down:
<cntrl>h Enter the online help system
<cntrl>x <cntrl>s Save the file
<cntrl>x <cntrl>c Exit emacs
<cntrl>x u Undo last edit (can be repeated)
<cntrl>g Got out of current command operation
<cntrl>p Up/down/forward/back by line or character
<cntrl>v Forward/backward by one screen
<cntrl>s Search for characters
<cntrl>d Delete a character
EDLIN EDITOR
EDLIN version 1 comes with MS-DOS versions 3 through 5. There are simple commands
showing how to use EDLIN when editing a boot floppy. The following is a list of commands which
you can execute while holding the control key down:
<cntrl>c puts you in command mode immediately without adding

characters
<cntrl>z <enter> inserts an end of file character and returns you to command
mode
e <enter> saves and quits
l (“el”) will list lines in a file
p is a lot like l, except p moves the current line forward to the last
line displayed
i2 would insert a line before line 2
l2 (“el 2”) would put you at line 2.
VI EDITOR
You can use VI Editor to edit UNIX files locally or from remote via modem (proper terminal
emulation such as vt100 is required for screen text and cursor manipulation). If your terminal
window (or session) is not responding properly to screen paints, issue the following commands:
PEGASYS@adac:#[1] set term=vt100

PEGASYS@adac:#[2] setenv TERM vt100
PEGASYS@adac:#[3] setenv EDITOR vi
PEGASYS@adac:#[4] tset
To use the VI Editor:

• Open a UNIX window and become super user
• Type: vi <filename>
CHEATSHEET FOR THE VI EDITOR
Walt Klingenberg
Rev 0.2 12:47 2/1/96
Getting into the editor
vi document -Edit doc
vi + document -Edit doc going forward to last line upon entry
vi +23 document -Edit doc going forward to line 23 upon entry
vi +/exp document -Edit doc going forward to line with matching exp
vi doc1 doc2 doc3 -Edit list of docs
(See move between docs section under LAST LINE MODE)
view doc1 -Edit doc in read-only mode
Important: You are automatically in COMMAND MODE
Save Files and Exit

ZZ -Exit editor, saving changes (equivalent to :wq)
Screen/Line Movement
j -Move cursor down
k -Move cursor up
h -Move cursor left
l -Move cursor right
0 -Go to line start (zero)
$ -Go to line end
% -Go to matching brace/paren
^ -Go to first non-blank character of a line
G -Go to last line in file
3G -Go to line 3 in file
5| -Go to column 5 in current line
ctrl-f -Page forward a screenfull
ctrl-b -Page backward a screenfull
ctrl-d -Scroll forward a screenfull
ctrl-u -Scroll backward a screenfull
ctrl-l -Refresh screen
ctrl-g -Show current filename and line number for cursor position
z<cr> -Redraw screen with current line at top of window
z- -Redraw screen with current line at bottom of window
z. -Redraw screen with current line at middle of window
H -Move cursor to line at top of window
M -Move cursor to line at middle of window
L -Move cursor to line at bottom of window
ctrl-y -Scroll window up 1 line keeping cursor at current line
ctrl-e -Scroll window down 1 line keeping cursor at current line
Marking and Returning
mx -Mark current position with variable marker named x
'x -Go to first non-white in line you marked with variable marker
named x
`x -Go to position you marked with variable marker named x
(note this one above uses a back-tick)
d'x -Delete from line marked with variable marker named x to
current line
:'x,'yw file -Write lines in marked range to new file
Word Movement
w -Go forward 1 word
3w -Go forward 3 words
b -Go back 1 word
3b -Go back 3 words
e -Go forward to the end of word (or next word)
3e -Go forward to the 3rd end of word from current position
W -Go forward 1 word
3W -Go forward 3 words
B -Go back 1 word
3B -Go back 3 words
E -Go forward to the end of word (or next word)
3E -Go forward to the 3rd end of word from current position
Search Functions
n -Repeat previous search in same direction
N -Reverse direction of previous search
Delete Text
x -Delete one character at cursor
3x -Delete 3 characters at cursor
X -Delete one character before cursor
3X -Delete 3 characters before cursor
dw -Delete one word
dd -Delete one line
D -Delete from current cursor position to end of line
d0 -Delete from current cursor position to beginning of line
dG -Delete from current line to end of file
d3w -Delete 3 words
4dd -Delete 4 lines including the current one and the three below
Cancel Edit Function

u -Undo last change
U -Restore current line
. -Do last change over again
"4p -Retrieve and put 4th last delete
Copy and Insert Text
Y -Yank a copy of a line
yy -Yank a copy of a line
5Y -Yank a copy of 5 lines
5yy -Yank a copy of 5 lines
p -Put yanked lines below current line
P -Put yanked lines above current line
Copy and Insert Text (using named buffers)

"xdd -Delete line into buffer named x
"x5Y -Yank 5 lines into buffer named x
"xp -Put yanked lines from buffer named x below current line
"xP -Put yanked lines from buffer named x above current line
Change Text
r -Replace one character with one and only one character
Word processing functions

J -Join next line to current
4J -Join 4 lines to current
sp -Transpose two characters
===================================================
some characters put you into INPUT MODE
(REMEMBER: use <esc> then finished with input !!!)
(puts you back in COMMAND MODE)
===================================================
Add/Append Text
a -Append after cursor
A -Append at line end
i -Insert before cursor
5i -Insert text 5 times
I -Insert at beginning of line
Add new lines

o -Open a line below cursor
O -Open a line above cursor (letter “O” not zero)
Change Text
cw -Change a word
3cw -Change 3 words
C -Change line
s -Replace one character with one or more characters
5s -Replace 5 characters with one or more characters
R -Replace one character or more characters by Type-over
S -Replace entire line
6S -Replace 6 entire lines
===================================================
some characters put you into LAST LINE "ex" MODE
( <cr> to exit or automatically exiting )
(puts you back in COMMAND MODE)
===================================================
Interrupting/Canceling
<esc> -End insert or incomplete command
ctrl-c -interrupt insert or command
Search Functions
/exp -Go forward to exp pattern
?exp -Go backward to exp pattern
:g/exp/p -Show all occurrences of the pattern exp in file
/exp/+2 -Go 2 lines past line with matching exp pattern
?exp?-3 -Go 3 lines before line with matching exp pattern
fx -Find next occurrence of character x on current line
Fx -Find previous occurrence of character x on current line
tx -Find char. before next occurrence of character x on
current line
Tx -Find char. after previous occurrence of character x on
current line
Move and Insert Text

:3,8d -Delete lines 3 thru 8
:1,.d -Delete lines 1 thru current
:.,$d -Delete lines current thru last
:1,$d -Delete lines 1 thru last
:.,.+3d -Delete lines current thru current+3
:4,9m 12 -Move lines 4 thru 9 to 12
:2,5t 13 -Copy lines 2 thru 5 to 13
:5,9w junk -Write lines 2 thru 5 to a file called junk
Save Files and Exit

:w -Write buffer to current file
:w newfile -Write buffer to new file
:w! file -Write Absolutely
:wq -Write buffer and quit editor
:q -Quit editor
:q! -Quit editor discarding current change buffer
:e! -Reedit, discarding changes
:r file -Read in named file below current line
:f -Show current file name and line number (same as crtl-g)
Move Between Documents

:n -Go to next file in edit list
:n docs -Go to next file in new edit list (you can name many
new files)
:e docname -Edit new document not originally named on command line
:e # -Switch to last named/edited file (only if on 2nd or more
in list)
crtl-^ -Works the same as :e #
Control Edit Session
:set all -Show all setting
:set nu -Display line numbers
:set nonu -Turn off line numbers
:set sm -Show match for braces/parens when in insert mode
:set nosm -Turn off show match
:set ai -Turn on autoindent
:set noai -Turn off autoindent
:set list -display invisible chars
:set wm=5 -Wrap lines 5 spaces from right margin
:set ts=4 -Set tabstops to 4 spaces per tab (8 is default)
Special Functions
:1,$! sort -Sort entire file alphabetically (the default
for sort)
:5,8! sort -Sort lines 5 thru 8
:1,$! sort -u -Sort entire file removing exactly duplicate lines
:1,$! sort -n -Sort entire file numerically
:!command -Escape to shell, run command and return
Decimal / Hexadecimal / Binary Conversion Table
A P P E N D I X B
Glossary of Networking Terms

Included with permission from David Loomes and the University of Bradford,
West Yorkshire, United Kingdom, BD7 1DP. Please see the notes at the end
of the glossary for credits and more information.
10Base2
A physical layer communications specification for 10Mbps, baseband data transmission over
a coaxial cable (Thinnet) with a maximum cable segment length of 185 meters. [Source:
RFC1983]
10Base5
a coaxial cable (Thicknet) with a maximum cable segment length of 500 meters. [Source:
RFC1983]
10BaseF
a fiber-optic cable. [Source: RFC1983]
10BaseT
a twisted-pair copper wire. See also: Ethernet, twisted pair. [Source: RFC1983]
802.11
The set of IEEE Working Groups and subsequent standards for the definition of wireless LAN
protocols. The Physical Layer (air interface) incorporates Spread Spectrum techniques to
avoid detection, interception and interference between devices. The results so far are 802.11b,
which has a data rate of 11Mbit/s and uses the 2.4GHz radio band, then 802.11a which has a
data rate of 54Mbit/s and uses the 5GHz radio band, so it is not inherently interoperable with
802.11b. Subsequently 802.11g has a data rate of greater than 20MBit/s with the 2.4GHz
range, so there is scope for interworking with 802.11b devices. Then 802.11h enhances the
802.11a standard to select frequencies and trim power output to avoid interference with
HIPERLAN devices in Europe which use the same 5GHz band. The 2.4GHz and 5GHz radio
bands are license exempt so are attractive to general users. There is a built-in security
method, Wired Equivalent Privacy (WEP) within 802.11b standard, but there is an initial
move to use 802.1x security mechanisms before 802.11i is fully developed to enhance
security and authentication mechanisms (ongoing at March 2002). See also: 802.x, Bluetooth,
HIPERLAN, IEEE, Spread Spectrum, Wired Equivalent Privacy, Wireless Local Area
Network.
802.x
The set of IEEE Working Groups and subsequent standards for the definition of fixed and
wireless LAN and MAN protocols. See also: 802.11, Bluetooth, IEEE, Wireless Local Area
Network.
822
See: RFC 822
:-)
This odd symbol is one of the ways a person can portray "mood" in the very flat medium of
computers--by using "smiley faces". This is "metacommunication", and there are literally
hundreds of such symbols, from the obvious to the obscure. This particular example expresses
"happiness". Don't see it? Tilt your head to the left 90 degrees. Smiles are also used to denote
sarcasm. [Source: ZEN]
A
Address record for a host of given name in Domain Name Service.
abstract syntax
A description of a data structure that is independent of machine- oriented structures and
encodings. [Source: RFC1208]
Abstract Syntax Notation One (ASN.1)
The language used by the OSI protocols for describing abstract syntax. This language is also
used to encode SNMP packets. ASN.1 is defined in ISO documents 8824.2 and 8825.2. See
also: Basic Encoding Rules. [Source: RFC1392]
Acceptable Use Policy (AUP)
Many transit networks have policies which restrict the use to which the network may be put.
For example, some networks may only be used for non-commercial purposes. Some AUPs
limit the type of material which can be made available to the public (e.g., pornographic
material). Enforcement of AUPs varies with the network. See also: netiquette. [Source:
RFC1983]
Access Control List (ACL)
Most network security systems operate by allowing selective use of services. An Access
Control List is the usual means by which access to, and denial of, services is controlled. It is
simply a list of the services available, each with a list of the hosts permitted to use the service.
[Source: RFC1392]
ACK
See: Acknowledgment
acknowledgment (ACK)
A type of message sent to indicate that a block of data arrived at its destination without error.
See also: Negative Acknowledgement. [Source: NNSC]
ACL
See: Access Control List
ACSE
Association Control Service Element. The method used in OSI for establishing a call between
two applications. Checks the identities and contexts of the application entities, and could
apply an authentication security check. [Source: RFC1208]
AD
See: Administrative Domain
address
There are four types of addresses in common use within the Internet. They are email address;
IP, internet or Internet address; hardware or MAC address; and URL. See also: email address,
IP address, internet address, MAC address, Uniform Resource Locator. [Source: RFC1983]
address mask
A bit mask used to identify which bits in an IP address correspond to the network and subnet
portions of the address. This mask is often referred to as the subnet mask because the network
portion of the address (i.e., the network mask) can be determined by the encoding inherent in
an IP address. See also: Classless Inter- domain Routing. [Source: RFC1983]
address resolution
Conversion of a network-layer address (e.g. IP address) into the corresponding physical
address (e.g., MAC address). See also: IP address, MAC address. [Source: RFC1983]
Address Resolution Protocol (ARP)
Used to dynamically discover the low-level physical network hardware address that
corresponds to the high level IP address for a given host. ARP is limited to physical network
systems that support broadcast packets that can be heard by all hosts on the network. It is
defined in RFC 826. See also: proxy ARP, Reverse Address Resolution Protocol. [Source:
RFC1983]
ADMD
Administration Management Domain. An X.400 Message Handling System public service
carrier. Examples:- MCImail and ATTmail in the U.S., British Telecom Gold400mail in the
U.K. The ADMDs in all countries worldwide together provide the X.400 backbone. See
PRMD. [Source: RFC1208]
Administrative Domain (AD)
A collection of hosts and routers, and the interconnecting network(s), managed by a single
administrative authority. [Source: RFC1392]
administrivia
Administrative tasks, most often related to the maintenance of mailing lists, digests, news
gateways, etc.
Advanced Research Projects Agency (ARPA)
An agency of the U.S. Department of Defense responsible for the development of new
technology for use by the military. ARPA (formerly known as DARPA, nee ARPA) was
responsible for funding much of the development of the Internet we know today, including the
Berkeley version of Unix and TCP/IP. [Source: NNSC]
Advanced Research Projects Agency Network (ARPANET)
A pioneering long haul network funded by ARPA. It served as the basis for early networking
research, as well as a central backbone during the development of the Internet. The
ARPANET consisted of individual packet switching computers interconnected by leased
lines. See also: Advanced Research Projects Agency. [Source: FYI4]
agent
In the client-server model, the part of the system that performs information preparation and
exchange on behalf of a client or server application. [Source: RFC1208]
alias
A name, usually short and easy to remember, that is translated into another name, usually long
and difficult to remember. [Source: RFC1392]
American National Standards Institute (ANSI)
This organization is responsible for approving U.S. standards in many areas, including
computers and communications. Standards approved by this organization are often called
ANSI standards (e.g., ANSI C is the version of the C language approved by ANSI). ANSI is a
member of ISO. See also: International Organization for Standardization. [Source: NNSC]
American Standard Code for Information Interchange (ASCII)
A standard character-to-number encoding widely used in the computer industry. See also:
EBCDIC. [Source: RFC1392]
anonymous FTP
Anonymous FTP allows a user to retrieve documents, files, programs, and other archived data
from anywhere in the Internet without having to establish a userid and password. By using the
special userid of "anonymous" the network user will bypass local security checks and will
have access to publicly accessible files on the remote system. See also: archive site, File
Transfer Protocol, World Wide Web. [Source: RFC1983]
ANSI
See: American National Standards Institute
AOW
Asia and Oceania Workshop. One of the three regional OSI Implementors Workshops,
equivalent to OIW and EWOS.
API
See: Application Program Interface
AppleTalk
A networking protocol developed by Apple Computer for communication between Apple
Computer products and other computers. This protocol is independent of the network layer on
which it is run. Current implementations exist for LocalTalk, a 235Kb/s local area network;
and EtherTalk, a 10Mb/s local area network. [Source: NNSC]
application
A program that performs a function directly for a user. FTP, mail and Telnet clients are
examples of network applications. [Source: RFC1392]
application layer
The top layer of the network protocol stack. The application layer is concerned with the
semantics of work (e.g., formatting electronic mail messages). How to represent that data and
how to reach the foreign node are issues for lower layers of the network. [Source:
MALAMUD]
Application Program Interface (API)
A set of calling conventions which define how a service is invoked through a software
package. [Source: RFC1208]
archie
A system to automatically gather, index and serve information on the Internet. The initial
implementation of archie provided an indexed directory of filenames from all anonymous
FTP archives on the Internet. Later versions provide other collections of information. See
also: archive site, Gopher, Prospero, Wide Area Information Servers. [Source: RFC1392]
archive site
A machine that provides access to a collection of files across the Internet. For example, an
anonymous FTP archive site provides access to archived material via the FTP protocol.
WWW servers can also serve as archive sites. See also: anonymous FTP, archie, Gopher,
Prospero, Wide Area Information Servers, World Wide Web. [Source: RFC1392]
ARP
See: Address Resolution Protocol
ARPA
See: Defense Advanced Research Projects Agency
ARPANET
See: Advanced Research Projects Agency Network
AS
See: Autonomous System
ASCII
See: American Standard Code for Information Interchange
ASN.1
See: Abstract Syntax Notation One
assigned numbers
The RFC [STD2] which documents the currently assigned values from several series of
numbers used in network protocol implementations. This RFC is updated periodically and, in
any case, current information can be obtained from the Internet Assigned Numbers Authority
(IANA). If you are developing a protocol or application that will require the use of a link,
socket, port, protocol, etc., please contact the IANA to receive a number assignment. See also:
Internet Assigned Numbers Authority, STD. [Source: STD2]
asynchronous
Transmission by individual bytes, not related to specific timing on the transmitting end.
Asynchronous Transfer Mode (ATM)
A standard which defines high-load, high-speed (1.544Mbps through 1.2Gbps), fixed-size
packet (cell) switching with dynamic bandwidth allocation. ATM is also known as "fast
packet." [Source: RFC1983]
ATM
See: Asynchronous Transfer Mode
AUP
See: Acceptable Use Policy
attribute
The form of information items provided by the X.500 Directory Service. The directory
information base consists of entries, each containing one or more attributes. Each attribute
consists of a type identifier together with one or more values. Each directory Read operation
can retrieve some or all attributes from a designated entry. [Source: RFC1208]
AUSCERT
Australian Computer Emergency Response Team.
authentication
The verification of the identity of a person or process. [Source: MALAMUD]
auto-magic
Something which happens pseudo-automatically, and is usually too complex to go into any
further than to say it happens ``auto-magically.''
Autonomous System (AS)
Internet (TCP/IP) terminology for a collection of routers under a single administrative
authority using a common Interior Gateway Protocol (IGP) for routing packets. See
subnetwork. [Source: RFC1392]
backbone
The top level in a hierarchical network. Stub and transit networks which connect to the same
backbone are guaranteed to be interconnected. See also: stub network, transit network.
[Source: RFC1392]
bandwidth
Technically, the difference, in Hertz (Hz), between the highest and lowest frequencies of a
transmission channel. However, as typically used, the amount of data that can be sent through
a given communications circuit. [Source: RFC1392]
bang path
A series of machine names used to direct electronic mail from one user to another, typically
by specifying an explicit UUCP path through which the mail is to be routed. See also: email
address, mail path, UNIX-to-UNIX CoPy. [Source: RFC1392]
BAR
Backbone Access Router between a MAN and the JANET backbone.
baseband
A transmission medium through which digital signals are sent without complicated frequency
shifting. In general, only one communication channel is available at any given time. Ethernet
is an example of a baseband network. See also: broadband, Ethernet. [Source: NNSC]
Basic Encoding Rules (BER)
Standard rules for encoding data units described in ASN.1. Sometimes incorrectly lumped
under the term ASN.1, which properly refers only to the abstract syntax description language,
not the encoding technique. See also: Abstract Syntax Notation One. [Source: NNSC]
BBS
See: Bulletin Board System
BCNU
Be Seein' You [Source: RFC1392]
BCP
The newest sub series of RFCs which are written to describe Best Current Practices in the
Internet. Rather than specifying a protocol, these documents specify the best ways to use the
protocols and the best ways to configure options to ensure interoperability between various
vendors' products. BCPs carry the endorsement of the IESG. See also: Request For
Comments, Internet Engineering Steering Group. [Source: RFC1983]
BDP
Netscape's Browser Distribution Program.
BECTa
British Educational Communications and Technology Agency.
BER
See: Basic Encoding Rules
Berkeley Internet Name Domain (BIND)
Implementation of a DNS server developed and distributed by the University of California at
Berkeley. Many Internet hosts run BIND, and it is the ancestor of many commercial BIND
implementations. See also: Domain Name System. [Source: RFC1983]
Berkeley Software Distribution (BSD)
Implementation of the UNIX operating system and its utilities developed and distributed by
the University of California at Berkeley. "BSD" is usually preceded by the version number of
the distribution, e.g., "4.3 BSD" is version 4.3 of the Berkeley UNIX distribution. Many
Internet hosts run BSD software, and it is the ancestor of many commercial UNIX
implementations. [Source: NNSC]
BGP
See: Border Gateway Protocol
big-endian
A format for storage or transmission of binary data in which the most significant bit (or byte)
comes first. The term comes from "Gulliver's Travels" by Jonathan Swift. The Lilliputians,
being very small, had correspondingly small political problems. The Big-Endian and Little-
Endian parties debated over whether soft- boiled eggs should be opened at the big end or the
little end. See also: little-endian. [Source: RFC1208]
binary
11001001
BIND
See: Berkeley Internet Name Domain
Birds Of a Feather (BOF)
A Birds Of a Feather (flocking together) is an informal discussion group. It is formed, often
ad hoc, to consider a specific issue and, therefore, has a narrow focus. See also: Working
Group. [Source: RFC1392]
Bitnet
Because It's Time NETwork. An academic computer network that provided interactive
electronic mail and file transfer services, using a store-and-forward protocol, based on IBM
Network Job Entry protocols. Bitnet-II encapsulated the Bitnet protocol within IP packets and
depended on the Internet to route them. [Source: RFC1208]
Blue Book
the document describing a File Transfer Protocol used in the UK academic and research
community which was implemented on a wide range of computers and which allowed file
transfers between dissimilar computers. Also known as Network Independent File Transfer
Protocol (NIFTP). Now mostly superseded by Internet protocols (see FTP).
Bluetooth
An IEEE standard 802.15.1 for short range (up to 10m) wireless links between mobile
computers, phones and other portable peripheral devices. This uses the 2.4GHz band with a
data rate of 1Mbit/s. Work was in progress in March 2002 on a High Rate (20Mbit/s or
greater) version 802.15.3 in the same 2.4GHz band. Also known as Personal Area Network.
See also: Wireless Local Area Network.
BNC
Bayonet Nut Connector. A connector used on coaxial cables such as 10Base2 Ethernet.
BOC
Bell Operating Company. More commonly referred to as RBOC for Regional Bell Operating
Company. The local telephone company in each of the seven U.S. regions. [Source:
RFC1208]
BOF
See: Birds Of a Feather
BOOTP
The Bootstrap Protocol, described in RFC 951 and RFC 1084, is used for booting diskless
nodes. Updated in RFC 1395 and RFC 1497 and superseded by DHCP. See also: Reverse
Address Resolution Protocol, Dynamic Host Configuration Protocol. [Source: RFC1392]
Border Gateway Protocol (BGP)
The Border Gateway Protocol is an exterior gateway protocol defined in RFC 1267 and RFC
1268. It's design is based on experience gained with EGP, as defined in STD 18, RFC 904,
and EGP usage in the NSFNET Backbone, as described in RFC 1092 and RFC 1093. See
also: Exterior Gateway Protocol. [Source: RFC1392]
bounce
The return of a piece of mail because of an error in its delivery. [Source: ZEN]
bridge
A device which forwards traffic between network segments based on datalink layer
information. These segments would have a common network layer address. See also:
gateway, router. [Source: RFC1392]
broadband
A transmission medium capable of supporting a wide range of frequencies. It can carry
multiple signals by dividing the total capacity of the medium into multiple, independent
bandwidth channels, where each channel operates only on a specific range of frequencies. See
also: baseband. [Source: RFC1392]
broadcast
A special type of multicast packet which all nodes on the network are always willing to
receive. See also: multicast, unicast. [Source: RFC1392]
broadcast storm
An incorrect packet broadcast onto a network that causes multiple hosts to respond all at once,
typically with equally incorrect packets which causes the storm to grow exponentially in
severity. [Source: RFC1392] See also: Ethernet meltdown.
brouter
A device which bridges some packets (i.e., forwards based on datalink layer information) and
routes other packets (i.e., forwards based on network layer information). The bridge/route
decision is based on configuration information. See also: bridge, router. [Source: RFC1392]
BSD
See: Berkeley Software Distribution
BTW
An abbreviation for ``By The Way''.
Bulletin Board System (BBS)
A computer, and associated software, which typically provides electronic messaging services,
archives of files, and any other services or activities of interest to the bulletin board system's
operator. Although BBS's have traditionally been the domain of hobbyists, an increasing
number of BBS's are connected directly to the Internet, and many BBS's are currently
operated by government, educational, and research institutions. See also: Electronic Mail,
Internet, Usenet. [Source: NWNET]
C&NL MAN
Cumbra and North Lancashire Metropolitan Area Network.
Campus Wide Information System (CWIS)
A CWIS makes information and services publicly available on campus via kiosks, and makes
interactive computing available via kiosks, interactive computing systems and campus
networks. Services routinely include directory information, calendars, bulletin boards,
databases. [Source: RFC1392]
catenet
A network in which hosts are connected to networks with varying characteristics, and the
networks are interconnected by gateways (routers). The Internet is an example of a catenet.
See IONL. [Source: RFC1208]
CCIRN
See: Coordinating Committee for Intercontinental Research Networks
CCITT
See: Comite Consultatif International de Telegraphique et Telephonique
CCR
Commitment, Concurrency, and Recovery. An OSI application service element used to create
atomic operations across distributed systems. Used primarily to implement two-phase commit
for transactions and nonstop operations. [Source: RFC1208]
CERNET
China Education and Research Network.
CERT
See: Computer Emergency Response Team
CFV (Call For Votes)
Initiates the voting period for a Usenet newsgroup. At least one (occasionally two or more)
email address is customarily included as a repository for the votes.
checksum
A computed value which is dependent upon the contents of a packet. This value is sent along
with the packet when it is transmitted. The receiving system computes a new checksum based
upon the received data and compares this value with the one sent with the packet. If the two
values are the same, the receiver has a high degree of confidence that the data was received
correctly. [Source: NNSC]
CHEST
Combined Higher Education Software Team negotiates agreements with suppliers, especially
for site licenses, for the education community, thus making it the educational shop window
for purchases of software, data, information, training materials and other IT related products.
CIDR
See: Classless Inter-domain Routing
circuit switching
A communications paradigm in which a dedicated communication path is established between
two hosts, and on which all packets travel. The telephone system is an example of a circuit
switched network. See also: connection-oriented, connectionless, packet switching. [Source:
RFC1392]
ClariNews
The fee-based Usenet news feed available from ClariNet Communications.
Classless Inter-domain Routing (CIDR)
A proposal, set forth in RFC 1519, to allocate IP addresses so as to allow the addresses to be
aggregated when advertised as routes. It is based on the elimination of intrinsic IP network
addresses; that is, the determination of the network address based on the first few bits of the
IP address. See also: IP address, network address, supernet. [Source: RFC1983]
ClydeNet
River Clyde area's Metropolitan Area Network.
client
A computer system or process that requests a service of another computer system or process.
A workstation requesting the contents of a file from a file server is a client of the file server.
See also: client-server model, server. [Source: NNSC]
client-server model
A common way to describe the paradigm of many network protocols. Examples include the
name-server/name-resolver relationship in DNS and the file-server/file-client relationship in
NFS. See also: client, server, Domain Name System, Network File System. [Source:
RFC1392]
CLNP
Connectionless Network Protocol. The OSI protocol for providing the OSI Connectionless
Network Service (datagram service). CLNP is the OSI equivalent to Internet IP, and is
sometimes called ISO IP. [Source: RFC1208]
CLTP
Connectionless Transport Protocol. Provides for end-to-end Transport data addressing (via
Transport selector) and error control (via checksum), but cannot guarantee delivery or provide
flow control. The OSI equivalent of UDP. [Source: RFC1208]
CMIP
Common Management Information Protocol. The OSI network management protocol.
[Source: RFC1208]
CMOT
CMIP Over TCP. An effort to use the OSI network management protocol to manage TCP/IP
networks. [Source: RFC1208]
CNAME
Canonical Name (alternative name for a host) in Domain Name Service.
CNI
See: Coalition for Networked Information
Coalition for Networked Information (CNI)
A consortium formed by American Research Libraries, CAUSE, and EDUCOM (no, they are
not acronyms) to promote the creation of, and access to, information resources in networked
environments in order to enrich scholarship and enhance intellectual productivity. [Source:
RFC1392]
Coloured Books
set of standard protocols and recommendations for the different aspects of networking
software developed and used by the UK academic and research community. Now superseded
by Internet protocols. See also protocol.
Comite Consultatif International de Telegraphique et Telephonique
(CCITT) This organization is part of the United National International Telecommunications
Union (ITU) and is responsible for making technical recommendations about telephone and
data communications systems. Every four years CCITT holds plenary sessions where they
adopt new standards; the most recent was in 1992. Recently, the ITU reorganized and CCITT
was renamed the ITU-T. See also: International Telecommunications Union -
Telecommunications. [Source: RFC1983]
Computer Emergency Response Team (CERT)
The CERT was formed by DARPA in November 1988 in response to the needs exhibited
during the Internet worm incident. The CERT charter is to work with the Internet community
to facilitate its response to computer security events involving Internet hosts, to take proactive
steps to raise the community's awareness of computer security issues, and to conduct research
targeted at improving the security of existing systems. CERT products and services include
24-hour technical assistance for responding to computer security incidents, product
vulnerability assistance, technical documents, and tutorials. In addition, the team maintains a
number of mailing lists (including one for CERT Advisories), and provides an anonymous
FTP server, at "cert.org", where security-related documents and tools are archived. The CERT
may be reached by email at "cert@cert.org" and by telephone at +1-412-268-7090 (24-hour
hotline). See also: Advanced Research Projects Agency, worm. [Source: RFC1392]
congestion
Congestion occurs when the offered load exceeds the capacity of a data communication path.
[Source: RFC1392]
connection-oriented
The data communication method in which communication proceeds through three well-
defined phases: connection establishment, data transfer, connection release. TCP is a
connection-oriented protocol. See also: circuit switching, connectionless, packet switching,
Transmission Control Protocol. [Source: RFC1392]
connectionless
The data communication method in which communication occurs between hosts with no
previous setup. Packets between two hosts may take different routes, as each is independent
of the other. UDP is a connectionless protocol. See also: circuit switching, connection-
oriented, packet switching, User Datagram Protocol. [Source: RFC1392]
Coordinating Committee for Intercontinental Research Networks (CCIRN)
A committee that includes the United States FNC and its counterparts in North America and
Europe. Co-chaired by the executive directors of the FNC and the European Association of
Research Networks (RARE), the CCIRN provides a forum for cooperative planning among
the principal North American and European research networking bodies. See also: Federal
Networking Council, RARE. [Source: MALAMUD]
core gateway
Historically, one of a set of gateways (routers) operated by the Internet Network Operations
Center at Bolt, Beranek and Newman (BBN). The core gateway system formed a central part
of Internet routing in that all groups must advertise paths to their networks from a core
gateway. [Source: MALAMUD]
Corporation for Research and Educational Networking (CREN)
This organization was formed in October 1989, when Bitnet and CSNET (Computer +
Science NETwork) were combined under one administrative authority. CSNET is no longer
operational, but CREN still runs Bitnet. See also: Bitnet. [Source: NNSC]
COS
Corporation for Open Systems. A vendor and user group for conformance testing,
certification, and promotion of OSI products. [Source: RFC1208]
COSINE
Cooperation for Open Systems Interconnection Networking in Europe. A program sponsored
by the European Commission, aimed at using OSI to tie together European research networks.
[Source: RFC1208]
C-Pop
Core Point of Presence on JANET backbone.
cracker
A cracker is an individual who attempts to access computer systems without authorization.
These individuals are often malicious, as opposed to hackers, and have many means at their
disposal for breaking into a system. See also: hacker, Computer Emergency Response Team,
Trojan Horse, virus, worm. [Source: RFC1392]
CRC
See: cyclic redundancy check
CREN
See: Corporation for Research and Educational Networking
CSMA/CD
Carrier Sense Multiple Access with Collision Detection. The access method used by local
area networking technologies such as Ethernet. [Source: RFC1208]
CSNET
Computer+Science Network. Formerly a large computer network, mostly in the U.S. but with
international connections. CSNET sites included universities, research labs, and some
commercial companies. Now merged with BITNET to form CREN. See Corporation for
Research and Educational Networking. [Source: RFC1208]
CU-SeeMe
Pronounced "See you, See me," CU-SeeMe is a publicly available videoconferencing program
developed at Cornell University. It allows anyone with audio/video capabilities and an
Internet connection to videoconference with anyone else with the same capabilities. It also
allows multiple people to tie into the same videoconference. [Source: RFC1983]
CWIS
See: Campus Wide Information system
Cyberspace
A term coined by William Gibson in his fantasy novel Neuromancer to describe the "world"
of computers, and the society that gathers around them. [Source: ZEN]
Cyclic Redundancy Check (CRC)
A number derived from a set of data that will be transmitted. By recalculating the CRC at the
remote end and comparing it to the value originally transmitted, the receiving node can detect
some types of transmission errors. [Source: MALAMUD]
DARPA
Defense Advanced Research Projects Agency. See: Advanced Research Projects Agency
Data Encryption Key (DEK)
Used for the encryption of message text and for the computation of message integrity checks
(signatures). See also: encryption. [Source: RFC1392]
Data Encryption Standard (DES)
A popular, standard encryption scheme. See also: encryption, Pretty Good Privacy, RSA.
[Source: RFC1983]
datagram
A self-contained, independent entity of data carrying sufficient information to be routed from
the source to the destination computer without reliance on earlier exchanges between this
source and destination computer and the transporting network. See also: frame, packet.
[Source: J. Postel]
Data Link Layer
The OSI layer that is responsible for data transfer across a single physical connection, or
series of bridged connections, between two Network entities. [Source: RFC1208]
DCA
See: Defense Information Systems Agency
DCE (1)
Data Circuit-terminating Equipment
DCE (2)
See: Distributed Computing Environment
DDN
See: Defense Data Network
DDN NIC
See: Defense Data Network Network Information Center
DECnet
A proprietary network protocol designed by Digital Equipment Corporation. The functionality
of each Phase of the implementation, such as Phase IV and Phase V, is different. [Source:
RFC1392]
default route
A routing table entry which is used to direct packets addressed to networks not explicitly
listed in the routing table. [Source: MALAMUD]
Defense Advanced Research Projects Agency (DARPA)
See: Advanced Research Projects Agency.
Defense Data Network (DDN)
A global communications network serving the US Department of Defense composed of
MILNET, other portions of the Internet, and classified networks which are not part of the
Internet. The DDN is used to connect military installations and is managed by the Defense
Information Systems Agency. See also: Defense Information Systems Agency. [Source:
RFC1392]
Defense Data Network Network Information Center (DDN NIC)
Often called "The NIC", the DDN NIC's primary responsibility is the assignment of Internet
network addresses and Autonomous System numbers, the administration of the root domain,
and providing information and support services to the DDN. It is also a primary repository for
RFCs. See also: Autonomous System, network address, Internet Registry, Network
Information Center, Request For Comments. [Source: RFC1392]
Defense Information Systems Agency (DISA)
Formerly called the Defense Communications Agency (DCA), this is the government agency
responsible for managing the DDN portion of the Internet, including the MILNET. Currently,
DISA administers the DDN, and supports the user assistance services of the DDN NIC. See
also: Defense Data Network. [Source: RFC1392]
DEK
See: Data Encryption Key
DES
See: Data Encryption Standard
DHCP
See: Dynamic Host Configuration Protocol
dialup
A temporary, as opposed to dedicated, connection between machines established over a
standard phone line. [Source: RFC1392]
Directory Access Protocol
X.500 protocol used for communication between a Directory User Agent and a Directory
System Agent. [Source: MALAMUD]
Directory System Agent (DSA)
The software that provides the X.500 Directory Service for a portion of the directory
information base. Generally, each DSA is responsible for the directory information for a
single organization or organizational unit. [Source: RFC1208]
Directory User Agent (DUA)
The software that accesses the X.500 Directory Service on behalf of the directory user. The
directory user may be a person or another software element. [Source: RFC1208]
DISA
See: Defense Information Systems Agency
disassembling
Converting a binary program into human-readable machine language code. See also PAD.
Distributed Computing Environment (DCE)
An architecture of standard programming interfaces, conventions, and server functionalities
(e.g., naming, distributed file system, remote procedure call) for distributing applications
transparently across networks of heterogeneous computers. Promoted and controlled by the
Open Software Foundation (OSF), a consortium led by Digital, IBM and Hewlett Packard.
[Source: RFC1208]
distributed database
A collection of several different data repositories that looks like a single database to the user.
A prime example in the Internet is the Domain Name System. [Source: RFC1392]
DIX Ethernet
See: Ethernet
DNS
See: Domain Name System
Document Type Definition
Definition of a language built on eXtensible Markup Language (XML) or Standardized
General Markup Language (SGML).
domain
"Domain" is a heavily overused term in the Internet. It can be used in the Administrative
Domain context, or the Domain Name context. See also: Administrative Domain, Domain
Name System. [Source: RFC1392]
Domain Name System (DNS)
The DNS is a general purpose distributed, replicated, data query service. The principal use is
the lookup of host IP addresses based on host names. The style of host names now used in the
Internet is called "domain name", because they are the style of names used to look up
anything in the DNS. Some important domains are: .COM (commercial), .EDU (educational),
.NET (network operations), .GOV (U.S. government), and .MIL (U.S. military). Most
countries also have a domain. The country domain names are based on ISO 3166. For
example, .US (United States), .UK (United Kingdom), .AU (Australia). It is defined in STD
13, RFC 1034 and RFC 1035. See also: Fully Qualified Domain Name, Mail Exchange
Record. [Source: RFC1983]
dot address (dotted decimal notation)
Dot address refers to the common notation for IP addresses of the form A.B.C.D; where each
letter represents, in decimal, one byte of a four byte IP address. See also: IP address. [Source:
FYI4]
DPA
Data Protection Act.
DS1
A framing specification for T-1 synchronous lines. See also: T1 [Source: RFC1392]
DS3
A framing specification for T-3 synchronous lines. See also: T3 [Source: RFC1392]
DSA
See: Directory System Agent
DSU
Data Service Unit, a physical cable interface on a network link.
DTD
See: Document Type Definition
DTE
Data Terminal Equipment
DUA
See: Directory User Agent
dynamic adaptive routing
Automatic rerouting of traffic based on a sensing and analysis of current actual network
conditions. NOTE: this does not include cases of routing decisions taken on predefined
information. [Source: J. Postel]
DUL
Dial-up User List, which has entries for ranges of IP addresses used by Internet Service
Providers for modem users.
DWDM
Dense Wave Division Multiplexing, a technique for passing multiple data streams along an
optical fiber cable using different wavelengths as carriers.
Dynamic Host Configuration Protocol (DHCP)
A framework for passing configuration information to hosts on a TCP/IP network, using an
options field; a development from the BOOTP Bootstrap Protocol. Described in RFC 1533
and RFC 1534 and updated in RFC 2132. See also: BOOTP.
E1
The basic building block for European multi-megabit data rates, with a bandwidth of
2.048Mbps. See also: T1. [Source: RFC1983]
E3
A European standard for transmitting data at 57.344Mbps. See also: T3. [Source: RFC1983]
EARN
European Academic and Research Network. See: Trans-European Research and Education
Networking Association. [Source: RFC1983]
EaStMAN
Edinburgh and Stirling Metropolitan Area Network.
EastNet
East of England Regional Network.
EBCDIC
See: Extended Binary Coded Decimal Interchange Code
Ebone
A pan-European backbone service. [Source: RFC1392]
EFF
See: Electronic Frontier Foundation
EFLA
See: Extended Four Letter Acronym
EGP
See: Exterior Gateway Protocol
Electronic Frontier Foundation (EFF)
A foundation established to address social and legal issues arising from the impact on society
of the increasingly pervasive use of computers as a means of communication and information
distribution. [Source: RFC1392]
Electronic Mail (email)
A system whereby a computer user can exchange messages with other computer users (or
groups of users) via a communications network. Electronic mail is one of the most popular
uses of the Internet. [Source: NNSC]
email
See: Electronic mail
email address
The domain-based or UUCP address that is used to send electronic mail to a specified
destination. For example an editor's address is "gmalkin@xylogics.com". See also: bang path,
mail path, UNIX- to-UNIX CoPy. [Source: ZEN]
EMMAN
East Midlands Metropolitan Area Network.
encapsulation
The technique used by layered protocols in which a layer adds header information to the
protocol data unit (PDU) from the layer above. As an example, in Internet terminology, a
packet would contain a header from the physical layer, followed by a header from the datalink
layer (e.g. Ethernet), followed by a header from the network layer (IP), followed by a header
from the transport layer (TCP), followed by the application protocol data. [Source: RFC1208]
encryption
Encryption is the manipulation of a packet's data in order to prevent any but the intended
recipient from reading that data. There are many types of data encryption, and they are the
basis of network security. See also: Data Encryption Standard. [Source: RFC1392]
end system
An OSI system which contains application processes capable of communicating through all
seven layers of OSI protocols. Equivalent to Internet host. [Source: RFC1208]
entity
OSI terminology for a layer protocol machine. An entity within a layer performs the functions
of the layer within a single computer system, accessing the layer entity below and providing
services to the layer entity above at local service access points. [Source: RFC1208]
error checking
The examination of received data for transmission errors. See also: checksum, Cyclic
Redundancy Check. [Source: RFC1983]
ES-IS
End system to Intermediate system protocol. The OSI protocol by which end systems
announce themselves to intermediate systems. [Source: RFC1208]
ESMTP
Extended Simple Mail Transfer Protocol. See Simple Mail Transfer Protocol.
Ethernet
A 10-Mb/s standard for LANs, initially developed by Xerox, and later refined by Digital, Intel
and Xerox (DIX). All hosts are connected to a coaxial cable where they contend for network
access using a Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
paradigm. See also: 802.x, Local Area Network, token ring. [Source: RFC1392]
Ethernet meltdown
An event that causes saturation, or near saturation, on an Ethernet. It usually results from
illegal or misrouted packets and typically lasts only a short time. See also: broadcast storm.
[Source: COMER]
ETSI
See: European Telecommunications Standards Institute
EUNet
European UNIX Network, an Internet Service Provider. [Source: RFC1208]
European Telecommunications Standards Institute
A pan-European organization of administrations, network operators, manufacturers, service
providers, research bodies and users. ETSI develops standards and technical documentation in
telecommunications, broadcasting and information technology.
EUUG
European UNIX Users Group. [Source: RFC1208]
European Academic and Research Network (EARN)
European Academic and Research Network. See: Trans-European Research and Education
Networking Association. [Source: RFC1983]
EWOS
European Workshop for Open Systems. The OSI Implementors Workshop for Europe. See
OIW. [Source: RFC1208]
Extended Binary Coded Decimal Interchange Code (EBCDIC)
A standard character-to-number encoding used primarily by IBM computer systems. See also:
ASCII. [Source: RFC1392]
Extendable Markup Language (XML)
A subset of Standardized General Markup Language, for development of markup applications
using Document Type Definitions (DTDs) in areas such as database searches and information
interchange, in electronic business transactions and elsewhere.
Extended Four Letter Acronym (EFLA)
A recognition of the fact that there are far too many TLAs. See also: Three Letter Acronym.
[Source: K. Morgan]
Exterior Gateway Protocol (EGP)
A protocol which distributes routing information to the routers which connect autonomous
systems. The term "gateway" is historical, as "router" is currently the preferred term. There is
also a routing protocol called EGP defined in STD 18, RFC 904. See also: Autonomous
System, Border Gateway Protocol, Interior Gateway Protocol. [Source: RFC1392]
eXternal Data Representation (XDR)
A standard for machine independent data structures developed by Sun Microsystems and
defined in RFC 1014. It is similar to ASN.1. See also: Abstract Syntax Notation One.
[Source: RFC1208]
FARNET
A non-profit corporation, established in 1987, whose mission is to advance the use of
computer networks to improve research and education. [Source: RFC1392]
FAQ
Frequently Asked Question [Source: RFC1392]
FaTMAN
Fife and Tayside Metropolitan Area Network.
Fawn Book
the document produced for the JNT defining the Simple Screen Management Protocol
(SSMP).
FDDI
See: Fiber Distributed Data Interface
FEDA
Formerly Further Education Development Agency, now called Learning and Skills
Development Agency (LSDA).
FEFC
Formerly Further Education Funding Council, now called Learning and Skills Council (LSC).
Federal Information Exchange (FIX)
One of the connection points between the American governmental internets and the Internet.
[Source: SURA]
Federal Networking Council (FNC)
The coordinating group of representatives from those federal agencies involved in the
development and use of federal networking, especially those networks using TCP/IP and the
Internet. Current members include representatives from DOD, DOE, DARPA, NSF, NASA,
and HHS. See also: Defense Advanced Research Projects Agency, National Science
Foundation. [Source: RFC1392]
Fiber Distributed Data Interface (FDDI)
A high-speed (100Mb/s) LAN standard. The underlying medium is fiber optics, and the
topology is a dual-attached, counter- rotating token ring. See also: Local Area Network, token
ring. [Source: RFC1208]
file transfer
The copying of a file from one computer to another over a computer network. See also: File
Transfer Protocol, Kermit, Gopher, World Wide Web. [Source: RFC1983]
File Transfer Protocol (FTP)
A protocol which allows a user on one host to access, and transfer files to and from, another
host over a network. Also, FTP is usually the name of the program the user invokes to execute
the protocol. The IP version is defined in STD 9, RFC 959. See also: anonymous FTP,
FTAM. [Source: RFC1392]
Compare the Unix "Anonymous FTP" (see above) with the UK JNT Network Independent
File Transfer Protocol or NIFTP (now almost extinct), also known as "Blue Book" (see
above). The Unix commands are "ftp" and "hhcp" respectively.
finger
A protocol, defined in RFC 1288, that allows information about a system or user on a system
to be retrieved. Finger also refers to the commonly used program which retrieves this
information. Information about all logged in users, as well is information about specific users
may be retrieved from local or remote systems. Some sites consider finger to be a security risk
and have either disabled it, or replaced it with a simple message. [Source: RFC1983]
FIPS
Federal Information Processing Standard.
FIX
See: Federal Information Exchange
flame
A strong opinion and/or criticism of something, usually as a frank inflammatory statement, in
an electronic mail message. It is common to precede a flame with an indication of pending
fire (i.e., FLAME ON!). Flame Wars occur when people start flaming other people for
flaming when they shouldn't have. See also: Electronic Mail. [Source: RFC1392]
FLEA
See: Four Letter Extended Acronym
FNC
See: Federal Networking Council
For Your Information (FYI)
A sub series of RFCs that are not technical standards or descriptions of protocols. FYIs
convey general information about topics related to TCP/IP or the Internet. See also: Request
For Comments, STD. [Source: RFC1392]
FQDN
See: Fully Qualified Domain Name
fragment
A piece of a packet. When a router is forwarding an IP packet to a network that has a
maximum packet size smaller than the packet size, it is forced to break up that packet into
multiple fragments. These fragments will be reassembled by the IP layer at the destination
host. See also: Maximum Transmission Unit. [Source: RFC1392]
fragmentation
The IP process in which a packet is broken into smaller pieces to fit the requirements of a
physical network over which the packet must pass. See also: reassembly. [Source: RFC1392]
frame
A frame is a datalink layer "packet" which contains the header and trailer information
required by the physical medium. That is, network layer packets are encapsulated to become
frames. See also: datagram, encapsulation, packet. [Source: RFC1392]
freenet
Community-based bulletin board system with email, information services, interactive
communications, and conferencing. Freenets are funded and operated by individuals and
volunteers -- in one sense, like public television. They are part of the National Public
Telecomputing Network (NPTN), an organization based in Cleveland, Ohio, devoted to
making computer telecommunication and networking services as freely available as public
libraries. [Source: LAQUEY]
FTAM
File Transfer, Access, and Management. The OSI remote file service and protocol. [Source:
RFC1208]
FTP
See: File Transfer Protocol
Fully Qualified Domain Name (FQDN)
The FQDN is the full name of a system, rather than just its hostname. For example, "venera"
is a hostname and "venera.isi.edu" is an FQDN. See also: hostname, Domain Name System.
[Source: RFC1392]
FYI
See: For Your Information
G.703
ITU-T standard for physical and logical traits of transmissions over digital circuits, including
US 1.544Mbit/s and European 2.048Mbit/s (typically used to refer to the latter).
gated
Gatedaemon. A program which supports multiple routing protocols and protocol families. It
may be used for routing, and makes an effective platform for routing protocol research. The
software is freely available by anonymous FTP from "gated.cornell.edu". Pronounced "gate-
dee". See also: Exterior Gateway Protocol, Open Shortest Path First..., Routing Information
Protocol, routed. Source: RFC1983]
gateway
The term "router" is now used in place of the original definition of "gateway". Currently, a
gateway is a communications device/program which passes data between networks having
similar functions but dissimilar implementations. This should not be confused with a protocol
converter. By this definition, a router is a layer 3 (network layer) gateway, and a mail gateway
is a layer 7 (application layer) gateway. See also: mail gateway, router, protocol converter.
[Source: RFC1392]
Gbit/s
Gigabits (thousand million - or strictly 2 to the power 30 - bits) per second.
GÉANT
A development from the former TEN-155 pan-European research network, creating a core
network and access links to countries at Gigabit speeds.
General Packet Radio Service (GPRS)
An ETSI standard for packet-based wireless data communications at speeds up to a theoretical
171 kilobits per second, for continuous connection to the Internet, for portable computers and
mobile phones. Addition of Virtual Private Network facilities will allow a degree of security
for mobile access to important data. GPRS is based on the Global System for Mobile
infrastructure, using up to 8 time slots (provided for 8 voice calls on a given frequency) only
when there is information to transmit, rather than completely reserved as in a voice circuit.
GPRS is being developed into Enhanced Data GSM Environment (EDGE), using a new
modulation scheme for higher data rates up to 384 kilobits per second, as a step on the way to
Universal Mobile Telecommunications Service (UMTS). See also: Virtual Private Network.
Global System for Mobile communications
An ETSI standard for second generation digital cellular wireless voice and data
communications using time division multiple access transmission methods. Formerly known
as Groupe Spécial Mobile, which was the study group of the Conference of European Posts
and Telegraphs (CEPT) set up to develop a pan-European system for terrestrial mobiles.
Gopher
A distributed information service developed at the University of Minnesota, that makes
available hierarchical collections of information across the Internet. Gopher uses a simple
protocol, defined in RFC 1436, that allows a single Gopher client to access information from
any accessible Gopher server, providing the user with a single "Gopher space" of information.
Public domain versions of the client and server are available. See also: archie, archive site,
Prospero, Wide Area Information Servers. [Source: RFC1392]
GOSIP
See: Government OSI Profile
Government OSI Profile
A subset of OSI standards specific to U.S. Government procurements, designed to maximize
interoperability in areas where plain OSI standards are ambiguous or allow excessive options.
[Source: BIG-LAN]
GPRS
See: General Packet Radio Service
Green Book
the document listing recommendations on the use of Triple-X and the definition of the TS29
protocol, formerly used in UK Universities.
Grey Book
the document describing the JNT Interim Mail Protocol used in the UK for mail transfers.
Mostly superseded by Internet mail protocols such as SMTP (q.v.).
gross
A dozen dozen (144).
GSM
See: Global System for Mobile communications
GUI
Graphical User Interface, typically consisting of windows, menus and pointer (e.g. mouse)
hence WIMP.
hacker
A person who delights in having an intimate understanding of the internal workings of a
system, computers and computer networks in particular. The term is often misused in a
pejorative context, where "cracker" would be the correct term. See also: cracker. [Source:
RFC1392]
HDLC
High level Data Link Control, ISO standard for carrying data over a link with error and flow
control.
header
The portion of a packet, preceding the actual data, containing source and destination
addresses, and error checking and other fields. A header is also the part of an electronic mail
message that precedes the body of a message and contains, among other things, the message
originator, date and time. See also: Electronic Mail, packet, error checking. [Source:
RFC1392]
heterogeneous network
A network running multiple network layer protocols. See also: DECnet, IP, IPX, XNS,
homogeneous network. [Source: RFC1983]
hierarchical routing
The complex problem of routing on large networks can be simplified by reducing the size of
the networks. This is accomplished by breaking a network into a hierarchy of networks, where
each level is responsible for its own routing. The Internet has, basically, three levels: the
backbones, the mid-levels, and the stub networks. The backbones know how to route between
the mid-levels, the mid-levels know how to route between the sites, and each site (being an
autonomous system) knows how to route internally. See also: Autonomous System, Exterior
Gateway Protocol, Interior Gateway Protocol, stub network, transit network. [Source:
RFC1392]
High Performance Computing and Communications (HPCC)
High performance computing encompasses advanced computing, communications, and
information technologies, including scientific workstations, supercomputer systems, high
speed networks, special purpose and experimental systems, the new generation of large scale
parallel systems, and application and systems software with all components well integrated
and linked over a high speed network. [Source: HPCC]
High Performance Parallel Interface (HIPPI)
An emerging ANSI standard which extends the computer bus over fairly short distances at
speeds of 800 and 1600 Mb/s. HIPPI is often used in a computer room to connect a
supercomputer to routers, frame buffers, mass-storage peripherals, and other computers. See
also: American National Standards Institute [Source: MALAMUD]
HIPERLAN
High Performance radio Local Area Network, an ESTI standard EN 300 652 for high speed
data communications at 20Mbit/s in the 5GHz range, either between portable devices or as an
extension of a wired network infrastructure. There is a development to produce HIPERLAN2,
which can be used for 3G mobile phone core networks as well as 54Mbit/s data networks in
the 5GHz radio range. See also 802.11, Wireless Local Area Network.
HIPPI
See: High Performance Parallel Interface
homogeneous network
A network running a single network layer protocol. See also: DECnet, IP, IPX, XNS,
heterogeneous network. [Source: RFC1983]
hop
A term used in routing. A path to a destination on a network is a series of hops, through
routers, away from the origin. [Source: RFC1392]
host
A computer that allows users to communicate with other host computers on a network.
Individual users communicate by using application programs, such as electronic mail, Telnet
and FTP. [Source: NNSC]
host address
See: internet address
hostname
The name given to a machine. See also: Fully Qualified Domain Name. [Source: ZEN]
host number
See: host address
HPCC
See: High Performance Computing and Communications
HTML
See: Hypertext Markup Language
HTTP
See: Hypertext Transfer Protocol
hub
A device connected to several other devices. In ARCnet, a hub is used to connect several
computers together. In a message handling service, a hub is used for the transfer of messages
across the network. [Source: MALAMUD]
hyperlink
A pointer within a hypertext document which points (links) to another document, which may
or may not also be a hypertext document. See also: hypertext. [Source: RFC1983]
hypertext
A document, written in HTML, which contains hyperlinks to other documents, which may or
may not also be hypertext documents. Hypertext documents are usually retrieved using
WWW. See also: hyperlink, Hypertext Markup Language, World Wide Web. [Source:
RFC1983]
Hypertext Markup Language (HTML)
The language used to create hypertext documents. It is a subset of SGML and includes the
mechanisms to establish hyperlinks to other documents. See also: hypertext, hyperlink,
Standardized General Markup Language. [Source: RFC1983]
Hypertext Markup Protocol (HTTP)
The protocol used by WWW to transfer HTML files. A formal standard is still under
development in the IETF. See also: hyperlink, hypertext, Hypertext Markup Language, World
Wide Web. [Source: RFC1983]
I-D
See: Internet-Draft
IAB
See: Internet Architecture Board
IANA
See: Internet Assigned Numbers Authority
ICANN
See: Internet Corporation for Assigned Numbers and Names
ICMP
See: Internet Control Message Protocol
ICT
Information and Communications Technologies (or variations thereof, sometimes CIT).
IEAK
Internet Explorer Administration Kit (Microsoft).
IEEE
Institute of Electrical and Electronics Engineers
IEEE 802
See: 802.x
IEN
See: Internet Experiment Note
IESG
See: Internet Engineering Steering Group
IETF
See: Internet Engineering Task Force
IINREN
See: Interagency Interim National Research and Education Network
IIS
Internet Information Service (Microsoft).
IGP
See: Interior Gateway Protocol
IGRP
Internet Gateway Routing Protocol. A proprietary IGP used by Cisco System's routers.
[Source: RFC1208]
IMAP
See: Internet Message Access Protocol
IMHO
"In My Humble Opinion"; usually accompanies a statement that may bring about personal
offense or strong disagreement. Rarely used in Yorkshire, where opinions are anything but
humble, especially about cricket or rugby.
IMR
See: Internet Monthly Report
INTAP
Interoperability Technology Association for Information Processing. The technical
organization which has the official charter to develop Japanese OSI profiles and conformance
tests. [Source: RFC1208]
Integrated Services Digital Network (ISDN)
An emerging technology which is beginning to be offered by the telephone carriers of the
world. ISDN combines voice and digital network services in a single medium, making it
possible to offer customers digital data services as well as voice connections through a single
"wire". The standards that define ISDN are specified by CCITT. See also: CCITT. [Source:
RFC1208]
Interagency Interim National Research and Education Network (IINREN)
An evolving operating network system. Near term (1992-1996) research and development
activities will provide for the smooth evolution of this networking infrastructure into the
future gigabit NREN. [Source: HPCC]
Interior Gateway Protocol (IGP)
A protocol which distributes routing information to the routers within an autonomous system.
The term "gateway" is historical, as "router" is currently the preferred term. See also:
Autonomous System, Exterior Gateway Protocol, Open Shortest Path First..., Routing
Information Protocol. [Source: RFC1392]
Intermediate System (IS)
An OSI system which performs network layer forwarding, i.e. not an end system. It is
analogous to an IP router. See also: Open Systems Interconnection, router. [Source:
RFC1392]
Intermediate System-Intermediate System (IS-IS)
The OSI IGP. See also: Open Systems Interconnection, Interior Gateway Protocol. [Source:
RFC1392]
International Organization for Standardization (ISO)
A voluntary, nontreaty organization founded in 1946 which is responsible for creating
international standards in many areas, including computers and communications. Its members
are the national standards organizations of the 89 member countries, including ANSI for the
U.S. See also: American National Standards Institute, Open Systems Interconnection.
[Source: TAN]
International Telecommunications Union (ITU)
An agency of the United Nations which coordinates the various national telecommunications
standards so that people in one country can communicate with people in another country.
[Source: RFC1983]
International Telecommunications Union - Telecommunications (ITU-T)
The new name for CCITT since the ITU reorganization. The function is the same; only the
name has been changed. [Source: RFC1983]
internet
While an internet is a network, the term "internet" is usually used to refer to a collection of
networks interconnected with routers. See also: network. [Source: RFC1392]
Internet
(note the capital "I") The Internet is the largest internet in the world. Is a three level hierarchy
composed of backbone networks (e.g., Ultranet), mid-level networks (e.g., NEARnet) and
stub networks. The Internet is a multiprotocol internet. See also: backbone, mid-level
network, stub network, transit network, Internet Protocol. [Source: RFC1983]
internet address
A IP address that uniquely identifies a node on an internet. An Internet address (capital "I"),
uniquely identifies a node on the Internet. See also: internet, Internet, IP address. [Source:
RFC1392]
Internet Architecture Board (IAB)
The IAB has been many things over the years. Originally the Internet Activities Board, it was
responsible for the development of the protocols which make up the Internet. It later changed
its name and charter to become the group most responsible for the architecture of the Internet,
leaving the protocol details to the IESG. In June of 1992, it was chartered as a component of
the Internet Society; this is the charter it holds today. The IAB is responsible for approving
nominations to the IESG, architectural oversight for Internet Standard Protocols, IETF
standards process oversight and appeals, IANA and RFC activities, and liaison to peer
standards groups (e.g., ISO). See also: Internet Engineering Task Force, Internet Research
Task Force, Internet Engineering Steering Group, Internet Assigned Numbers Authority,
Request for Comments. [Source: RFC1983]
Internet Assigned Numbers Authority (IANA)
The central registry for various Internet protocol parameters, such as port, protocol and
enterprise numbers, and options, codes and types. The currently assigned values are listed in
the "Assigned Numbers" document [STD2]. To request a number assignment, contact the
IANA at "iana@isi.edu". Now superseded by ICANN. See also: assigned numbers, STD.
[Source: RFC1983]
Internet Corporation for Assigned Numbers and Names (ICANN)
Successor to Internet Assigned Numbers Authority for Internet management functions
performed under contract to US Government.
Internet Control Message Protocol (ICMP)
ICMP is an extension to the Internet Protocol. It allows for the generation of error messages,
test packets and informational messages related to IP. It is defined in STD 5, RFC 792.
[Source: FYI4]
Internet-Draft (I-D)
Internet-Drafts are working documents of the IETF, its Areas, and its Working Groups. As the
name implies, Internet-Drafts are draft documents. They are valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents at any time. Very
often, I-Ds are precursors to RFCs. See also: Internet Engineering Task Force, Request For
Comments. [Source: RFC1392]
Internet Engineering Planning Group (IEPG)
A group, primarily composed of Internet service operators, whose goal is to promote a
globally coordinated Internet operating environment. Membership is open to all. [Source:
RFC1983]
Internet Engineering Steering Group (IESG)
The IESG is composed of the IETF Area Directors and the IETF Chair. It provides the first
technical review of Internet standards and is responsible for day-to-day "management" of the
IETF. See also: Internet Engineering Task Force. [Source: RFC1392]
Internet Engineering Task Force (IETF)
The IETF is a large, open community of network designers, operators, vendors, and
researchers whose purpose is to coordinate the operation, management and evolution of the
Internet, and to resolve short-range and mid-range protocol and architectural issues. It is a
major source of proposals for protocol standards which are submitted to the IAB for final
approval. The IETF meets three times a year and extensive minutes are included in the IETF
Proceedings. See also: Internet, Internet Architecture Board. [Source: FYI4]
Internet Experiment Note (IEN)
A series of reports pertinent to the Internet. IENs were published in parallel to RFCs and were
intended to be "working documents." They have been replaced by Internet-Drafts and are
currently of historic value only. See also: Internet-Draft, Request For Comments. [Source:
RFC1392]
Internet Message Access Protocol (IMAP)
A protocol defined by RFC2060 and others, allowing a client to read and manipulate
electronic mail messages and message folders (mailboxes) on a server.
Internet Monthly Report (IMR)
Published monthly, the purpose of the Internet Monthly Reports is to communicate to the
Internet Research Group the accomplishments, milestones reached, or problems discovered by
the participating organizations. [Source: RFC1392]
internet number
See: internet address
Internet Protocol (IP, IPv4)
The Internet Protocol (version 4), defined in RFC 791, is the network layer for the TCP/IP
Protocol Suite. It is a connectionless, best-effort packet switching protocol. See also: packet
switching, TCP/IP Protocol Suite, Internet Protocol Version 6. [Source: RFC1983]
Internet Protocol security (IPSec)
A packet layer security standard consisting of Authentication Header (AH) and Encapsulating
Security Payload (ESP) elements, defined in RFC 2402 and RFC 2406 respectively. Useful
for Virtual Private Networks.
Internet Protocol Version 6 (IPng, IPv6)
IPv6 (version 5 is a stream protocol used for special applications) is a new version of the
Internet Protocol which is designed to be an evolutionary step from its predecessor, version 4.
There are many RFCs defining various portions of the protocol, its auxiliary protocols, and
the transition plan from IPv4. The core RFCs are 1883, 1884, 1885 and 1886; also updated at
RFC2460. The name IPng (IP next generation) is a nod to STNG (Star Trek Next Generation).
[Source: RFC1392]
Internet Registry (IR)
The IANA has the discretionary authority to delegate portions of its responsibility and, with
respect to network address and Autonomous System identifiers, has lodged this responsibility
with an IR. The IR function is performed by the DDN NIC. See also: Autonomous System,
network address, Defense Data Network..., Internet Assigned Numbers Authority. [Source:
RFC1392]
Internet Relay Chat (IRC)
A world-wide "party line" protocol that allows one to converse with others in real time. IRC is
structured as a network of servers, each of which accepts connections from client programs,
one per user. See also: talk. [Source: HACKER]
Internet Research Steering Group (IRSG)
The "governing body" of the IRTF. See also: Internet Research Task Force. [Source:
MALAMUD]
Internet Research Task Force (IRTF)
The IRTF is chartered by the IAB to consider long-term Internet issues from a theoretical
point of view. It has Research Groups, similar to IETF Working Groups, which are each
tasked to discuss different research topics. Multi-cast audio/video conferencing and privacy
enhanced mail are samples of IRTF output. See also: Internet Architecture Board, Internet
Engineering Task Force, Privacy Enhanced Mail. [Source: RFC1392]
Internet Society (ISOC)
The Internet Society is a non-profit, professional membership organization which facilitates
and supports the technical evolution of the Internet, stimulates interest in and educates the
scientific and academic communities, industry and the public about the technology, uses and
applications of the Internet, and promotes the development of new applications for the system.
The Society provides a forum for discussion and collaboration in the operation and use of the
global Internet infrastructure. The Internet Society publishes a quarterly newsletter, the
Internet Society News, and holds an annual conference, INET. The development of Internet
technical standards takes place under the auspices of the Internet Society with substantial
support from the Corporation for National Research Initiatives under a cooperative agreement
with the US Federal Government. [Source: V. Cerf]
Internetwork Packet eXchange (IPX)
Novell's protocol used by Netware. A router with IPX routing can interconnect LANs so that
Novell Netware clients and servers can communicate. See also: Local Area Network. [Source:
RFC1392]
InterNIC
A five year project, partially supported by the National Science Foundation, to provide
network information services to the networking community. The InterNIC began operations
in April of 1993 and is now a collaborative project of two organizations: AT&T, which
provides Directory and Database Services from South Plainsfield, NJ; and Network Solutions,
Inc., which provides Registration Services from their headquarters in Herndon, VA. Services
are provided via the Internet, and by telephone, FAX, and hardcopy. [Source: RFC1983]
interoperability
The ability of software and hardware on multiple machines from multiple vendors to
communicate meaningfully. [Source: RFC1392]
IONL
Internal Organization of the Network Layer. The OSI standard for the detailed architecture of
the Network Layer. Basically, it partitions the Network layer into subnetworks interconnected
by convergence protocols (equivalent to internetworking protocols), creating what Internet
calls a catenet or internet. [Source: RFC1208]
IP (IPv4)
See: Internet Protocol
IP address
The 32-bit address defined by the Internet Protocol in RFC 791. It is usually represented in
dotted decimal notation. See also: dot address, internet address, Internet Protocol, network
address, subnet address, host address. [Source: RFC1392]
IP datagram
See: datagram
IPng (IPv6)
See: Internet Protocol Version 6
IPSec
See: Internet Protocol security
IPX
See: Internetwork Packet eXchange
IR
See: Internet Registry
IRC
See: Internet Relay Chat
IRSG
See: Internet Research Steering Group
IRTF
See: Internet Research Task Force
IS
See: Intermediate System
IS-IS
See: Intermediate System-Intermediate System
ISDN
See: Integrated Services Digital Network
ISO
See: International Organization for Standardization
ISO Development Environment (ISODE)
Software that allows OSI services to use a TCP/IP network. Pronounced eye-so-dee-eee. See
also: Open Systems Interconnection, TCP/IP Protocol Suite. [Source: RFC1392]
ISOC
See: Internet Society
ISODE
See: ISO Development Environment
ISP
Internet Service Provider, a purveyor of access to the Internet.
JANET
Formerly Joint Academic Network. The United Kingdom education and research network.
See also SUPERJANET.
JANET-CERT
JANET Computer Emergency Response Team. See also: Computer Emergency Response
Team.
JANET National User Group (JNUG)
The JANET National User Group (JNUG) represents the views and concerns of people who
use the national academic network, JANET, to those who are responsible for its funding. The
Group encompasses representatives from Regional User Groups and Special Interest Groups.
JANET User Group for Administration (JUGA)
The JANET User Group for Administration (JUGA) exists to promote the use of information
technology, primarily via JANET by administrators in Higher Education. JUGA is a Special
Interest Group of the JANET National User Group, through which the views of the users on
JANET and UKERNA services are presented to the JISC Committee on Networking. See
also: JANET National User Group.
JANET User Group for Libraries (JUGL)
The JANET User Group for Libraries (JUGL) supports Library and Information Professionals
in the use and development of Electronic Networking for information provision. JUGL is a
Special Interest Group of the JANET National User Group, through which the views of the
users on JANET and UKERNA services are presented to the JISC Committee on Networking.
See also: JANET National User Group.
JANET Yorkshire and Northumbria Regional User Group (JYNRUG)
The JANET Yorkshire and Northumbria Regional User Group represents the views of users
of JANET within the ancient regions of Yorkshire and Northumbria, plus any modern
additions. See also: JANET National User Group.
JCALT
JISC Committee for Awareness, Liaison and Training, promoting use and effectiveness of
ICT in post-16 education.
JCCS
JISC Committee for Content and Services, to identify, procure and deliver content for all
sectors of further and higher education, within a content management structure, for maximum
uptake of resources.
JCLT
JISC Committee for Learning and Teaching, to facilitate coordination and effectiveness of
Information Learning Technologies (ILT) in learning and teaching in UK colleges and
universities.
JCIE
JISC Committee for Information Environment, build on existing strategies, to create a
common information environment, with mechanisms for access and delivery of resources and
finding quality information of relevance.
JCN
JISC Committee for Networking, which oversees JISC-funded networking and networked
services, including JANET.
JCP
JANET Connection Point.
JCS
JANET Customer Service, at UKERNA.
JCSR
JISC Committee for Support of Research, to identify requirements of the research community
which can be met from the JISC budget, and work with the Research Grid community e.g. on
e-science programmes.
JCUR
JANET Connection and Upgrade Form, from UKERNA.
JIPS
The JANET Internet Protocol Service (JIPS) was the IP service on JANET, in its X.25
network days, using the technique of "IP tunneling" - ie encapsulation of the X.25 packets
into TCP/IP packets. The result was that UK institutions could connect to hosts on the world
wide Internet with programs such as telnet, anonymous ftp, gopher and World Wide Web
browsers, before JANET became a fully IP network.
JISC
Joint Information Systems Committee, consisting of representatives of UK Funding Councils
and other stakeholders, for controlling budgets on networking and other information systems
projects. There are six subcommittees as constituted in February 2002, JCALT, JCCS, JCLT,
JCIE, JCN and JCSR.
JISC Assist
JISC Activities, Services and Special Initiatives Support Team, which is the awareness-raising
unit for better understanding of the role of information systems and information technology in
further and higher education institutions.
JISCMail
The National Academic Mailing List Service, based at the Rutherford Appleton Laboratory.
JISC Technology Applications Programme
iA programme of over 100 projects to develop and demonstrate applications of Information
and Communication Technology, produce technology reviews and establish four clearing
houses to promote use of ICT to support staff and students in HIgher Education.
JKREY
Joyce K. Reynolds
JNT
the former UK Joint Network Team; sponsored by the Computer Board and SERC to manage
academic network developments. Now known as UKERNA.
JNUG
See: JANET National User Group
JOD
JANET Operations Desk, based in London.
JTAP
See: JISC Technology Allicationa Programme
JTMP
Job Transfer and Manipulation Protocol; a protocol designed to allow jobs to be sent from one
computer to another to be executed, and to allow specifications of output handling. See also
Red Book.
JUGA
See: JANET User Group for Administration
JUGL
See: JANET User Group for Libraries
JUNET
Japan UNIX Network. [Source: RFC1208]
JWCS
JANET Web Cache Service, also known as the National Cache.
JYNRUG
See: JANET Yorkshire and Northumbria Regional User Group
KA9Q
A popular implementation of TCP/IP and associated protocols for amateur packet radio
systems. See also: TCP/IP Protocol Suite. [Source: RFC1208]
kbit/s
Kilobits (thousand - or strictly 2 to the power 10 - bits) per second.
Kentish MAN
Metropolitan Area Network for Kent (there is no MAN of Kent).
Kerberos
Kerberos is the security system of MIT's Project Athena. It is based on symmetric key
cryptography. See also: encryption. [Source: RFC1392]
Kermit
A popular file transfer protocol developed by Columbia University. Because Kermit runs in
most operating environments, it provides an easy method of file transfer. Kermit is NOT the
same as FTP. See also: File Transfer Protocol [Source: MALAMUD]
kernel
The level of an operating system or networking system that contains the system-level
commands or all of the functions hidden from the user. In a Unix system, the kernel is a
program that contains the device drivers, the memory management routines, the scheduler,
and system calls. This program is always running while the system is operating.
Knowbot
A "Knowledge Robot" is a program which seeks out information based on specified criteria.
"Knowbot," as trademarked by CNRI, refers specifically to the search engine for Knowbot
Information Services. See also: Corporation for National Research Initiatives, X.500, white
pages, whois, netfind. [Source: RFC1983]
Knowbot Information Services
An experimental directory service. See also: white pages, WHOIS, X.500. [Source:
RFC1983]
LAN
See: Local Area Network
layer
Communication networks for computers may be organized as a set of more or less
independent protocols, each in a different layer (also called level). The lowest layer governs
direct host-to-host communication between the hardware at different hosts; the highest
consists of user applications. Each layer builds on the layer beneath it. For each layer,
programs at different hosts use protocols appropriate to the layer to communicate with each
other. TCP/IP has five layers of protocols; OSI has seven. The advantages of different layers
of protocols is that the methods of passing information from one layer to another are specified
clearly as part of the protocol suite, and changes within a protocol layer are prevented from
affecting the other layers. This greatly simplifies the task of designing and maintaining
communication programs. See also: Open Systems Interconnection, TCP/IP Protocol Suite.
[Source: RFC1392]
LDAP
See: Lightweight Directory Access Protocol.
learndirect
The learning services for Ufi are delivered through learndirect, which provides information
and advice on high quality courses.
LeNSE
Learning Network for the South East.
Lightweight Directory Access Protocol
This protocol provides access for management and browser applications that provide
read/write interactive access to the X.500 Directory. See also: X.500. [Source: RFC1983]
link
A pointer which may be used to retrieve the file or data to which the pointer points. [Source:
RFC1983]
LINX
London InterNet eXchange, an interconnection point for Internet Service providers in the UK
(and elsewhere).
list server
An automated mailing list distribution system. List servers handle the administrivia of mailing
list maintenance, such as the adding and deleting of list members. See also: mailing list.
[Source: RFC1983]
listserv
An automated mailing list distribution system originally designed for the Bitnet/EARN
network. See also: mailing list. [Source: RFC1392]
little-endian
A format for storage or transmission of binary data in which the least significant byte (bit)
comes first. See also: big-endian. [Source: RFC1208]
LJUG
See: London JANET User Group
LLC
See: Logical Link Control
LMN
London Metropolitan Network.
Local Area Network (LAN)
A data network intended to serve an area of only a few square kilometers or less. Because the
network is known to cover only a small area, optimizations can be made in the network signal
protocols that permit data rates up to 100Mb/s. See also: Ethernet, Fiber Distributed Data
Interface, token ring, Metropolitan Area Network, Wide Area Network, Wireless Local Area
Network. [Source: NNSC]
Logical Link Control (LLC)
The upper portion of the datalink layer, as defined in IEEE 802.2. The LLC sublayer presents
a uniform interface to the user of the datalink service, usually the network layer. Beneath the
LLC sublayer is the MAC sublayer. See also: 802.x, layer, Media Access Control. [Source:
RFC1392]
London JANET User Group (LJUG)
The London JANET User Group presents the views of the users on JANET and UKERNA
services to the JISC Committee on Networking through the JANET National User Group. See
LSC
Learning and Skills Council, successor to FEFC.
LSDA
Learning and Skills Development Agency, successor to FEDA.
Lurking
No active participation on the part of a subscriber to an mailing list or USENET newsgroup.
A person who is lurking is just listening to the discussion. Lurking is encouraged for
beginners who need to get up to speed on the history of the group. See also: Electronic Mail,
mailing list, Usenet. [Source: LAQUEY]
Lycos
Lycos, Inc. is a new venture formed in late June 1995, to develop and market the Lycos
technology originally developed under the direction of Dr. Michael ("Fuzzy") Mauldin at
Carnegie Mellon University. The part of Lycos you see when you do a search is the search
engine. "Lycos" comes from Lycosidae, a cosmopolitan family of relatively large active
ground spiders (Wolf Spiders) that catch their prey by pursuit, rather than in a web. [Source:
Lycos's FAQ]
MAC
See: Media Access Control
MAC address
The hardware address of a device connected to a shared media. See also: Media Access
Control, Ethernet, token ring. [Source: MALAMUD]
mail bridge
A mail gateway that forwards electronic mail between two or more networks while ensuring
that the messages it forwards meet certain administrative criteria. A mail bridge is simply a
specialized form of mail gateway that enforces an administrative policy with regard to what
mail it forwards. See also: Electronic Mail, mail gateway. [Source: NNSC]
Mail Exchange Record (MX Record)
A DNS resource record type indicating which host can handle mail for a particular domain.
See also: Domain Name System, Electronic Mail. [Source: MALAMUD]
mail exploder
Part of an electronic mail delivery system which allows a message to be delivered to a list of
addresses. Mail exploders are used to implement mailing lists. Users send messages to a
single address and the mail exploder takes care of delivery to the individual mailboxes in the
list. See also: Electronic Mail, email address, mailing list. [Source: RFC1208]
mail gateway
A machine that connects two or more electronic mail systems (including dissimilar mail
systems) and transfers messages between them. Sometimes the mapping and translation can
be quite complex, and it generally requires a store-and-forward scheme whereby the message
is received from one system completely before it is transmitted to the next system, after
suitable translations. See also: Electronic Mail. [Source: RFC1208]
mail path
A series of machine names used to direct electronic mail from one user to another. This
system of email addressing has been used primarily in UUCP networks which are trying to
eliminate its use altogether. See also: bang path, email address, UNIX-to-UNIX CoPy.
[Source: RFC1392]
mail server
A software program that distributes files or information in response to requests sent via email.
Internet examples include Almanac and netlib. Mail servers have also been used in Bitnet to
provide FTP-like services. See also: Bitnet, Electronic Mail, FTP. [Source: NWNET]
mailing list
A list of email addresses, used by a mail exploder, to forward messages to groups of people.
Generally, a mailing list is used to discuss certain set of topics, and different mailing lists
discuss different topics. A mailing list may be moderated. This means that messages sent to
the list are actually sent to a moderator who determines whether or not to send the messages
on to everyone else. Requests to subscribe to, or leave, a mailing list should ALWAYS be
sent to the list's "-request" address (e.g., ietf-request@cnri.reston.va.us for the IETF mailing
list) or majordomo server. See also: Electronic Mail, mail exploder, email address, moderator,
majordomo. [Source: RFC1983]
majordomo
A program which handles mailing list maintenance (affectionately known as administrivia)
such as adding and removing addresses from mailing lists. See also: email address, mailing
list. [Source: RFC1983]
MAN
See: Metropolitan Area Network
Management Information Base (MIB)
The set of parameters an SNMP management station can query or set in the SNMP agent of a
network device (e.g., router). Standard, minimal MIBs have been defined, and vendors often
have Private enterprise MIBs. In theory, any SNMP manager can talk to any SNMP agent
with a properly defined MIB. See also: client-server model, Simple Network Management
Protocol, SMI. [Source: BIG-LAN]
MAPS
Mail Abuse Prevention System.
Martian
A humorous term applied to packets that turn up unexpectedly on the wrong network because
of bogus routing entries. Also used as a name for a packet which has an altogether bogus
(non-registered or ill-formed) internet address. [Source: RFC1208]
MAU (1)
Multistation Access Unit, for connection and control of Token Ring network stations in a star
arrangement. Also known as MSAU.
MAU (2)
Monitoring and Advisory Unit, a JISC-sponsored service to manage contracts between JISC
and several JISC-funded services.
Maximum Transmission Unit (MTU)
The largest frame length which may be sent on a physical medium. See also: frame,
fragmentation, frame. [Source: RFC1392]
Mbit/s
Megabits (million - or strictly 2 to the power 20 - bits) per second.
mbone
The Multicast Backbone is based on IP multicasting using class-D addresses. The mbone
concept was adopted at the March 1992 IETF in San Diego, during which it was used to
audiocast to 40 people throughout the world. At the following meeting, in Cambridge, the
name mbone was adopted. Since then the audiocast has become full two-way audio/video
conferencing using two video channels, four audio channels, and involving hundreds of
remote users. See also: multicast, Internet Engineering Task Force. [Source: RFC1983]
MD-2, MD-4, MD-5
See: Message Digest.
Media Access Control (MAC)
The lower portion of the datalink layer. The MAC differs for various physical media. See
also: MAC Address, Ethernet, Logical Link Control, token ring. [Source: RFC1392]
medium
The material used to support the transmission of data. This can be copper wire, coaxial cable,
optical fiber, or electromagnetic wave (as in microwave).
Message Digest (MD-2, MD-4, MD-5)
Message digests are algorithmic operations, generally performed on text, which produce a
unique signature for that text. MD-2, described in RFC 1319; MD-4, described in RFC 1320;
and MD-5, described in RFC 1321 all produce a 128-bit signature. They differ in their
operating speed and resistance to crypto-analytic attack. Generally, one must be traded off for
the other. [Source: RFC1983]
message switching
See: packet switching
Metropolitan Area Network (MAN)
A data network intended to serve an area approximating that of a large city. Such networks
are being implemented by innovative techniques, such as running fiber cables through subway
tunnels. A popular example of a MAN is SMDS. See also: Local Area Network, Switched
Multimegabit Data Service, Wide Area Network. [Source: NNSC]
MHS
Message Handling System. The system of message user agents, message transfer agents,
message stores, and access units which together provide OSI electronic mail. MHS is
specified in the CCITT X.400 series of Recommendations. [Source: RFC1208]
MIB
See: Management Information Base
Microcom Networking Protocol (MNP)
A series of protocols built into most modems which error-check or compress data being
transmitted over a phone line. [Source: RFC1983]
MidJUG
See: Midlands JANET User Group
Midlands JANET User Group (MidJUG)
The Midlands JANET User Group presents the views of the users on JANET and UKERNA
services to the JISC Committee on Networking through the JANET National User Group. See
mid-level network
Mid-level networks (a.k.a. regionals) make up the second level of the Internet hierarchy. They
are the transit networks which connect the stub networks to the backbone networks. See also:
backbone, Internet, stub network, transit network. [Source: RFC1392]
MidMAN
Midlands Metropolitan Area Network.
MILNET
MILitary NETwork. Originally part of the ARPANET, MILNET was partitioned in 1984 to
make it possible for military installations to have reliable network service, while the
ARPANET continued to be used for research. See DDN. [Source: RFC1208]
MIME
See: Multipurpose Internet Mail Extensions
MMC
Microsoft Management Console.
MNP
See: Microcom Networking Protocol.
moderator
A person, or small group of people, who manage moderated mailing lists and newsgroups.
Moderators are responsible for determining which email submissions are passed on to list. See
also: Electronic Mail, mailing list, Usenet. [Source: RFC1392]
MOSPF
Multicast Open Shortest-Path First. See: Open Shortest-Path First. [Source: RFC1983]
MSC
Monitoring SubCommittee, a subcommittee of JCN to monitor the performance of JANET,
now superseded by SPAG.
MTA
Message Transfer Agent. An OSI application process used to store and forward messages in
the X.400 Message Handling System. Equivalent to Internet mail agent. [Source: RFC1208]
MTU
See: Maximum Transmission Unit
MUD
See: Multi-User Dungeon
multicast
A packet with a special destination address which multiple nodes on the network may be
willing to receive. See also: broadcast, unicast. [Source: RFC1208]
multihomed host
A host which has more than one connection to a network. The host may send and receive data
over any of the links but will not route traffic for other nodes. See also: host, router. [Source:
MALAMUD]
multiplex
The division of a single transmission medium into multiple logical channels supporting many
simultaneous sessions. For example, one network may have simultaneous FTP, telnet, rlogin,
and SMTP connections, all going at the same time.
Multipurpose Internet Mail Extensions (MIME)
An extension to Internet email which provides the ability to transfer non-textual data, such as
graphics, audio and fax. It is defined in RFC 1341. See also: Electronic Mail. [Source:
RFC1392]
Multi-User Dungeon (MUD)
Adventure, role playing games, or simulations played on the Internet. Devotees call them
"text-based virtual reality adventures". The games can feature fantasy combat, booby traps
and magic. Players interact in real time and can change the "world" in the game as they play
it. Most MUDs are based on the Telnet protocol. See also: Telnet. [Source: LAQUEY]
MX Record
See: Mail Exchange Record
NAK
See: Negative Acknowledgment
NAT
See: Network Address Translation.
name resolution
The process of mapping a name into its corresponding address. See also: Domain Name
System. [Source: RFC1208]
Name Registration Scheme
All sites connected to JANET via X25 were expected to register with the national 'Name
Registration Scheme' (NRS). The NRS maintained a database which recorded, for each
service on each site (such as X29 or Coloured Book mail), a 'standard' name and an
'abbreviated name' for that service, together with its numeric JANET address. The full form of
identification using an NRS name was: UK.AC.. . With the replacement of X25 by IP
services, the NRS did not last usefully beyond mid-1997.
name resolution
The process of mapping a name into the corresponding address. See also: DNS. [Source:
RFC1208]
Name Server
software which matches mnemonic names to raw addresses. This might be a Campus Name
Server for local PCs (using a JNT protocol called Name Lookup Protocol or NLP), or a
Domain Name Server for local hosts on an Internet site - such as the Bradford campus
network.
Name Server record
A DNS resource record type indicating which host can provide the Domain Name Service
facilities for a particular domain. See also: Domain Name System.
namespace
A commonly distributed set of names in which all names are unique. [Source: MALAMUD]
National Institute of Standards and Technology (NIST)
United States governmental body that provides assistance in developing standards. Formerly
the National Bureau of Standards. [Source: MALAMUD]
National Research and Education Network (NREN)
The NREN is the realization of an interconnected gigabit computer network devoted to Hign
Performance Computing and Communications. See also: HPPC, IINREN. [Source: HPCC]
National Science Foundation (NSF)
A U.S. government agency whose purpose is to promote the advancement of science. NSF
funds science researchers, scientific projects, and infrastructure to improve the quality of
scientific research. The NSFNET, funded by NSF, was once an essential part of academic and
research communications. It was a high speed "network of networks" which is hierarchical in
nature. At the highest level, it had a backbone network of nodes, interconnected with T3
(45Mbps) facilities which spanned the continental United States. Attached to that were mid-
level networks and attached to the mid-levels were campus and local networks. See also:
backbone network, mid- level network. [Source: RFC1983]
Negative Acknowledgment (NAK)
Response to receipt of a corrupted packet of information. See also: Acknowledgement.
[Source: RFC1392]
NetBIOS
Network Basic Input Output System. The standard interface to networks on IBM PC and
compatible systems before the rise of TCP/IP.
net.citizen
An inhabitant of Cyberspace. One usually tries to be a good net.citizen, lest one be flamed.
netfind
A research prototype to provide a simple Internet "white pages" user directory. Developed at
the University of Colorado, Boulder, it tries to locate telephone and email information given a
person's name and a rough description of where the person works. See also: Knowbot, whois,
white pages, X.500. [Source: Ryan Moats]
netiquette
A pun on "etiquette" referring to proper behavior on a network. RFC 1855 (FYI 28) contains a
netiquette guide produced by the User Services area of the IETF. See also: Acceptable Use
Policy, Internet Engineering Task Force. [Source: RFC1983]
Netnews
See: Usenet
network
A computer network is a data communications system which interconnects computer systems
at various different sites. A network may be composed of any combination of LANs, MANs
or WANs. See also: Local Area Network, Metropolitan Area Network, Wide Area Network,
internet. [Source: RFC1392]
network address
The network portion of an IP address. For a class A network, the network address is the first
byte of the IP address. For a class B network, the network address is the first two bytes of the
IP address. For a class C network, the network address is the first three bytes of the IP
address. In each case, the remainder is the host address. In the Internet, assigned network
addresses are globally unique. See also: Internet, IP address, subnet address, host address,
Internet Registry, OSI Network Address. [Source: RFC1392]
Network Address Translation (NAT)
A method of converting between a range of IP addresses on the public side of a routing
device, and a (typically smaller) range of IP addresses on the private side. Often used as to
conserve IP addresses, since the private side can use "unrouteable" ranges of IP numbers,
which can be safely re-used in many such locations. Also used to conceal identities of private
hosts when implemented as part of a firewall. See also: Unrouteable Address, IP Address.
Network File System (NFS)
A protocol developed by Sun Microsystems, and defined in RFC 1094, which allows a
computer system to access files over a network as if they were on its local disks. This protocol
has been incorporated in products by more than two hundred companies, and is now a de facto
Internet standard. [Source: NNSC]
Network Information Center (NIC)
A NIC provides information, assistance and services to network users. See also: Network
Operations Center. [Source: RFC1392]
Network Information Services (NIS)
A set of services, generally provided by a NIC, to assist users in using the network. Also a
service used by UNIX administrators to manage databases distributed across a network (a
product of Sun Microsystems(R) - formerly known as Yellow Pages). See also: Network
Information Center. [Source: RFC1392]
Network Layer
The OSI layer that is responsible for routing, switching, and subnetwork access across the
entire OSI environment. [Source: RFC1208]
network mask
See: address mask
Network News Transfer Protocol (NNTP)
A protocol, defined in RFC 977, for the distribution, inquiry, retrieval, and posting of news
articles. See also: Usenet. [Source: RFC1392]
network number
See: network address
Network Operations Center (NOC)
A location from which the operation of a network or internet is monitored. Additionally, this
center usually serves as a clearinghouse for connectivity problems and efforts to resolve those
problems. See also: Network Information Center. [Source: NNSC]
Network Time Protocol (NTP)
A protocol that assures accurate local timekeeping with reference to radio and atomic clocks
located on the Internet. This protocol is capable of synchronizing distributed clocks within
milliseconds over long time periods. It is defined in STD 12, RFC 1119 (POSTSCRIPT
format) and updated in RFC 1305. See also: Internet. [Source: NNSC]
NFS
See: Network File System
NGfL
National Grid for Learning.
NIC (1)
See: Network Information Center
NIC (2)
Network Interface Card.
NIC.DDN.MIL
This is the domain name of the DDN NIC. See also: Defense Data Network..., Domain Name
System, Network Information Center. [Source: RFC1983]
NIFTP
Network Independent File Transfer Protocol. See Blue Book and FTP.
NILTA
National Information and Learning Technology Association.
NIS
See: Network Information Services
NISS
National Information Services and Systems. A JISC service carrying professionally
maintained online information services for and about the education sector.
NIST
See: National Institute of Standards and Technology
nln
National Learning Network.
NMS
Network Management Station. The system responsible for managing a (portion of a) network.
The NMS talks to network management agents, which reside in the managed nodes, via a
network management protocol. See agent. [Source: RFC1208]
NNTP
See: Network News Transfer Protocol
NNW
Network North West, a Metropolitan Area Network for Manchester and environs.
NOC
See: Network Operations Center
Nodal Switching System (NSS)
Main routing nodes in the NSFnet backbone. See also: backbone, National Science
Foundation. [Source: MALAMUD]
node
An addressable device attached to a computer network. See also: host, router. [Source:
RFC1392]
NorMAN
North East Metropolitan Area Network.
North West JANET Regional User Group (NWJRUG)
The North West JANET Regional User Group represents the views of users of JANET within
the ancient regions of Staffordshire, Cheshire, Lancashire and Cumbria, plus any modern
additions. See also: JANET National User Group.
NOSC
Network Operations and Service Centre.
NREN
See: National Research and Education Network
NRS
see Name Registration Scheme.
NS
See: Name Server record
NSAP
Network Service Access Point. The point at which the OSI Network Service is made available
to a Transport entity. The NSAPs are identified by OSI Network Addresses. [Source:
RFC1208]
NSF
See: National Science Foundation
NSS
See: Nodal Switching System
NT
New Technology, a version of Microsoft Windows operating system. The initials WNT bear
the same relationship to VMS as IBM does to HAL. I'm sorry Dave...
NTP
Network Time Protocol, defined by RFC 958, and updated to version 3 in RFC 1305,
provides the mechanisms to synchronize hosts and coordinate time distribution in a large
diverse internet.
NTU
Network Termination Unit
NWJRUG
See: North West JANET Regional User Group
OCLC
See: Online Computer Library Catalog
octet
An octet is 8 bits. This term is used in networking, rather than byte, because some systems
have bytes that are not 8 bits long. [Source: RFC1392]
ODBC
Open DataBase Connectivity. An application programming interface to allow programs to use
databases, using Structured Query Language as its database access language.
OIW
Workshop for Implementors of OSI. Frequently called NIST OIW or the NIST Workshop,
this is the North American regional forum at which OSI implementation agreements are
decided. It is equivalent to EWOS in Europe and AOW in the Pacific. [Source: RFC1208]
ONC(tm)
Open Network Computing. A distributed applications architecture promoted and controlled by
a consortium led by Sun Microsystems. [Source: RFC1208]
Online Computer Library Catalog
OCLC is a nonprofit membership organization offering computer- based services to libraries,
educational organizations, and their users. The OCLC library information network connects
more than 10,000 libraries worldwide. Libraries use the OCLC System for cataloging,
interlibrary loan, collection development, bibliographic verification, and reference searching.
[Source: OCLC]
Open Shortest-Path First (OSPF)
A link state, as opposed to distance vector, routing protocol. It is an Internet standard IGP
defined in RFC 1583 and RFC 1793. The multicast version, MOSPF, is defined in RFC 1584.
See also: Interior Gateway Protocol, Routing Information Protocol. [Source: RFC1392]
Open Systems Interconnection (OSI)
A suite of protocols, designed by ISO committees, to be the international standard computer
network architecture. See also: International Organization for Standardization. [Source:
RFC1392]
OSI
See: Open Systems Interconnection
OSI Network Address
The address, consisting of up to 20 octets, used to locate an OSI Transport entity. The address
is formatted into an Initial Domain Part which is standardized for each of several addressing
domains, and a Domain Specific Part which is the responsibility of the addressing authority
for that domain. [Source: RFC1208]
OSI Presentation Address
The address used to locate an OSI Application entity. It consists of an OSI Network Address
and up to three selectors, one each for use by the Transport, Session, and Presentation entities.
[Source: RFC1208]
OSI Reference Model
A seven-layer structure designed to describe computer network architectures and the way that
data passes through them. This model was developed by the ISO in 1978 to clearly define the
interfaces in multivendor networks, and to provide users of those networks with conceptual
guidelines in the construction of such networks. See also: International Organization for
Standardization. [Source: NNSC]
OSPF
See: Open Shortest-Path First
packet
The unit of data sent across a network. "Packet" a generic term used to describe unit of data at
all levels of the protocol stack, but it is most correctly used to describe application data units.
See also: datagram, frame. [Source: RFC1392]
Packet InterNet Groper (PING)
A program used to test reachability of destinations by sending them an ICMP echo request
and waiting for a reply. The term is used as a verb: "Ping host X to see if it is up!" See also:
Internet Control Message Protocol. [Source: RFC1208]
Packet Switch Node (PSN)
A dedicated computer whose purpose is to accept, route and forward packets in a packet
switched network. See also: packet switching, router. [Source: NNSC]
packet switching
A communications paradigm in which packets (messages) are individually routed between
hosts, with no previously established communication path. See also: circuit switching,
connection- oriented, connectionless. [Source: RFC1392]
PAD
Packet Assembler Disassembler; the hardware or software interface between a user's terminal
and a packet-switching network. A PAD assembles the user's input characters into packets for
network transmission, and disassembles packets of output characters into their component
characters for output on the terminal. The PAD facility may run on a host computer or on a
dedicated processor (such as the JNT-PAD).
Particle Physics Network Co-ordinating Group (PPNCG)
The Particle Physics Network Co-ordinating Group (PPNCG) is responsible for the
networking interests of the UK particle physics community. Formally it is a sub-committee of
the Particle Physics Committee (PPC) of the Particle Physics and Astronomy Research
Council (PPARC). PPNCG is also a Special Interest Group of the JANET National User
Group, through which the views of the users on JANET and UKERNA services are presented
to the JISC Committee on Networking. See also: JANET National User Group.
PCI
Protocol Control Information. The protocol information added by an OSI entity to the service
data unit passed down from the layer above, all together forming a Protocol Data Unit (PDU).
[Source: RFC1208]
PD
Public Domain
PDU
See: Protocol Data Unit
PEM
See: Privacy Enhanced Mail
PGP
See: Pretty Good Privacy
PHP
PHP: Hypertext Processor. An HTML-embedded scripting language used to create dynamic
web pages by running scripts on the web server and embedding the results in web pages.
Available from www.php.net.
Physical Layer
The OSI layer that provides the means to activate and use physical connections for bit
transmission. In plain terms, the Physical Layer provides the procedures for transferring a
single bit across a Physical Media. [Source: RFC1208]
Physical Media
Any means in the physical world for transferring signals between OSI systems. Considered to
be outside the OSI Model, and therefore sometimes referred to as "Layer 0." The physical
connector to the media can be considered as defining the bottom interface of the Physical
Layer, i.e., the bottom of the OSI Reference Model. [Source: RFC1208]
PING
See: Packet INternet Groper
Pink Book
the document describing the implementation of X25 protocol level 3 over a Connection
Orientated Network Service based on lower layers of Ethernet protocol. This enables
interconnectivity between e.g. Ethernet based PCs and X25 based hosts, and supports
Coloured Book protocols for file transfer and terminal access, e.g. with the Rainbow package.
Since it is based on ISO standards, Pink Book is not strictly a "Coloured Book" in the JANET
usage.
Point Of Presence (POP)
A site where there exists a collection of telecommunications equipment, usually digital leased
lines and multi-protocol routers. [Source: RFC1392]
Point-to-Point Protocol (PPP)
The Point-to-Point Protocol, defined in RFC 1661, provides a method for transmitting packets
over serial point-to-point links. There are many other RFCs which define extensions to the
basic protocol. See also: Serial Line IP. [Source: FYI4]
polling
Connecting to another system to check for things like mail or news.
POP
See: Post Office Protocol and Point Of Presence
port
A port is a transport layer demultiplexing value. Each application has a unique port number
associated with it. See also: Transmission Control Protocol, User Datagram Protocol. [Source:
RFC1392]
Portal
A web site integrating many facilities within one user interface. Only of value if the
infrastructure for personal information databases, authentication and authorization methods,
group communication, business processes and timely content have already been engineered
for harmonious web access. Driver software to address a multiplicity of browser devices, from
PCs and personal digital assistants to mobile phones and interactive TV, should make content
available in many environments.
POSI
Promoting Conference for OSI. The OSI "800-pound gorilla" in Japan. Consists of executives
from the six major Japanese computer manufacturers and Nippon Telephone and Telegraph.
They set policies and commit resources to promote OSI. [Source: RFC1208]
Post Office Protocol (POP)
A protocol designed to allow single user hosts to read mail from a server. Version 3, the most
recent and most widely used, is defined in RFC 1725. See also: Electronic Mail. [Source:
RFC1983]
Postal Telegraph and Telephone (PTT)
Outside the USA, PTT refers to a telephone service provider, which is usually a monopoly, in
a particular country. [Source: RFC1392]
postmaster
The person responsible for taking care of electronic mail problems, answering queries about
users, and other related work at a site. See also: Electronic Mail. [Source: ZEN]
PPNCG
See: Particle Physics Network Co-ordinating Group
PPP
See: Point-to-Point Protocol
Presentation Address
See OSI Presentation Address.
Presentation Layer
The OSI layer that determines how Application information is represented (i.e., encoded)
while in transit between two end systems. [Source: RFC1208]
Pretty Good Privacy (PGP)
A program, developed by Phil Zimmerman, which cryptographically protects files and
electronic mail from being read by others. It may also be used to digitally sign a document or
message, thus authenticating the creator. See also: encryption, Data Encryption Standard,
RSA. [Source: RFC1983]
Privacy Enhanced Mail (PEM)
Internet email which provides confidentiality, authentication and message integrity using
various encryption methods. See also: Electronic Mail, encryption. [Source: RFC1392]
PRMD
Private Management Domain. An X.400 Message Handling System private organization mail
system. Example:- NASAmail. See ADMD. [Source: RFC1208]
Prospero
A distributed file system which provides the user with the ability to create multiple views of a
single collection of files distributed across the Internet. Prospero provides a file naming
system, and file access is provided by existing access methods (e.g., anonymous FTP and
NFS). The Prospero protocol is also used for communication between clients and servers in
the archie system. See also: anonymous FTP, archie, archive site, Gopher, Network File
System, Wide Area Information Servers. [Source: RFC1392]
protocol
A formal description of message formats and the rules two computers must follow to
exchange those messages. Protocols can describe low-level details of machine-to-machine
interfaces (e.g., the order in which bits and bytes are sent across a wire) or high-level
exchanges between allocation programs (e.g., the way in which two programs transfer a file
across the Internet). [Source: MALAMUD]
protocol converter
A device/program which translates between different protocols which serve similar functions
(e.g., TCP and TP4). [Source: RFC1392]
Protocol Data Unit (PDU)
"PDU" is international standards committee speak for packet. See also: packet. [Source:
RFC1392]
protocol stack
A layered set of protocols which work together to provide a set of network functions. See
also: layer, protocol. [Source: RFC1392]
proxy
The mechanism whereby one system "fronts for" another system in responding to protocol
requests. Proxy systems are used in network management to avoid having to implement full
protocol stacks in simple devices, such as modems. [Source: RFC1208]
proxy ARP
The technique in which one machine, usually a router, answers ARP requests intended for
another machine. By "faking" its identity, the router accepts responsibility for routing packets
to the "real" destination. Proxy ARP allows a site to use a single IP address with two physical
networks. Subnetting would normally be a better solution. See also: Address Resolution
Protocol [Source: RFC1208]
PSN
See: Packet Switch Node.
PSS
the Packet SwitchStream of British Telecom. PSS includes a UK packet-switching network
service as well as a set of PADs in various cities. Now part of Global Network Services.
PTT
See: Postal, Telegraph and Telephone
PTO
Public Telecommunications Operator. See also: Postal, Telegraph and Telephone.
PTR
Name record for a host of given address, for reverse lookup, in Domain Name Service.
QoS
Quality of Service, a measure of the priority of packets in a shared network, principally in
terms of latency in transmission. Of interest in real-time applications e.g. video.
queue
A backup of packets awaiting processing. [Source: RFC1392]
RADIUS
Remote Authentication Dial In User Service is a protocol which allows an Authentication
Server to authenticate, authorize and carry configuration information for one or more Network
Access servers. These have links, typically for dialup access clients, that need authentication.
This allows username and password information to be held in one place for many access lines.
The current definition of RADIUS is in RFC 2865 and RFC 2866 for accounting (originally
in RFC 2058 and RFC 2059 respectively) with several others for extensions, such as IP
Version 6 at RFC 3162.
Rainbow
a package for the PC allowing file transfer and terminal access between Ethernet based PCs
and Ethernet or X25 based hosts, via Coloured Book protocols, running over Pink Book
protocol. Written by Edinburgh University. Of historical interest.
RARE
See: Reseaux Associes pour la Recherche Europeenne
RARP
See: Reverse Address Resolution Protocol
RBL
Real-time Blackhole List, a MAPS service for blocking electronic mail from rogue mail
relays.
RBOC
Regional Bell Operating Company [Source: RFC1392]
RCP
See: Remote copy program
RDN
Regional Distribution Network, a sort of organization for a Metropolitan Area Network. See
also RPAN.
Read the Fine Manual (RTFM)
This acronym is often used when someone asks a simple or common question. Replace "Fine"
with a more vulgar word if desired.
Read the Source Code (RTSC)
This acronym is often used when a software developer asks a question about undocumented
code. [Source: RFC1983]
reassembly
The IP process in which a previously fragmented packet is reassembled before being passed
to the transport layer. See also: fragmentation. [Source: RFC1392]
recursion
The facility of a programming language to be able to call functions from within themselves.
recursive
See: recursive [Source: RFC1392]
Red Book
Red Book Job Transfer and Manipulation Protocol; a JTMP used in the UK academic and
research community. See also JTMP.
regional
See: mid-level network. [Source: RFC1392]
remote login
Operating on a remote computer, using a protocol over a computer network, as though locally
attached. See also: Telnet. [Source: RFC1392]
Remote Procedure Call (RPC)
An easy and popular paradigm for implementing the client-server model of distributed
computing. In general, a request is sent to a remote system to execute a designated procedure,
using arguments supplied, and the result returned to the caller. There are many variations and
subtleties in various implementations, resulting in a variety of different (incompatible) RPC
protocols. [Source: RFC1208]
repeater
A device which propagates electrical signals from one cable to another. See also: bridge,
gateway, router. [Source: RFC1392]
Request For Comments (RFC)
The document series, begun in 1969, which describes the Internet suite of protocols and
related experiments. Not all (in fact very few) RFCs describe Internet standards, but all
Internet standards are written up as RFCs. The RFC series of documents is unusual in that the
proposed protocols are forwarded by the Internet research and development community,
acting on their own behalf, as opposed to the formally reviewed and standardized protocols
that are promoted by organizations such as CCITT and ANSI. See also: BCP, For Your
Information, STD. [Source: RFC1392]
Reseaux Associes pour la Recherche Europeenne (RARE)
European association of research networks. [Source: RFC1208]
Reseaux IP Europeenne (RIPE)
A collaboration between European networks which use the TCP/IP protocol suite. [Source:
RFC1392]
resolve
Translate an Internet name into its equivalent IP address or other DNS information.
Reverse Address Resolution Protocol (RARP)
A protocol, defined in RFC 903, which provides the reverse function of ARP. RARP maps a
hardware (MAC) address to an internet address. It is used primarily by diskless nodes when
they first initialize to find their internet address. See also: Address Resolution Protocol,
BOOTP, internet address, MAC address. [Source: RFC1392]
RFC
See: Request For Comments
RFC 822
The Internet standard format for electronic mail message headers. Mail experts often refer to
"822 messages". The name comes from "RFC 822", which contains the specification (STD
11, RFC 822). 822 format was previously known as 733 format. See also: Electronic Mail.
[Source: COMER]
RFD (Request For Discussion)
Usually a two- to three-week period in which the particulars of newsgroup creation are battled
out.
RIP
See: Routing Information Protocol
RIPA
Regulation of Investigatory Powers Act.
RIPE
See: Reseaux IP Europeenne
RJE
Remote Job Entry.
rlogin
A service offered by Berkeley UNIX which allows users of one machine to log into other
UNIX systems (for which they are authorized) and interact as if their terminals were
connected directly. Similar to Telnet. [Source: RFC1208]
ROSE
Remote Operations Service Element. A lightweight RPC protocol, used in OSI Message
Handling, Directory, and Network Management application protocols. [Source: RFC1208]
Round-Trip Time (RTT)
A measure of the current delay on a network. [Source: MALAMUD]
route
The path that network traffic takes from its source to its destination. Also, a possible path
from a given host to another host or destination. [Source: RFC1392]
routed
Route Daemon. A program which runs under 4.2BSD/4.3BSD UNIX systems (and derived
operating systems) to propagate routes among machines on a local area network, using the
RIP protocol. Pronounced "route-dee". See also: Routing Information Protocol, gated.
[Source: RFC1392]
router
A device which forwards traffic between networks. The forwarding decision is based on
network layer information and routing tables, often constructed by routing protocols. See also:
bridge, gateway, Exterior Gateway Protocol, Interior Gateway Protocol. [Source: RFC1392]
routing
The process of selecting the correct interface and next hop for a packet being forwarded. See
also: hop, router, Exterior Gateway Protocol, Interior Gateway Protocol. [Source: RFC1392]
routing domain
A set of routers exchanging routing information within an administrative domain. See also:
Administrative Domain, router. [Source: RFC1392]
Routing Information Protocol (RIP)
A distance vector, as opposed to link state, routing protocol. It is an Internet standard IGP
defined in STD 34, RFC 1058 (updated by RFC 1388). See also: Interior Gateway Protocol,
Open Shortest Path First.... [Source: RFC1392]
RPAN
Regional Partner Academic Network - a sort of organization for a Metropolitan Area
Network. See also RDN.
RPC
See: Remote Procedure Call
RSA
A public-key cryptographic system which may be used for encryption and authentication. It
was invented in 1977 and named for its inventors: Ron Rivest, Adi Shamir, and Leonard
Adleman. See also: encryption, Data Encryption Standard, Pretty Good Privacy. [Source:
RFC1983]
RSC
Regional Support Centre, a JISC-sponsored service to further (and higher) education
institutions.
RSS
Relay Spam Stopper, a method of rejecting electronic mail from rogue mail relays.
RTFM
See: Read the Fine Manual
RTSC
See: Read the Source Code
RTSE
Reliable Transfer Service Element. A lightweight OSI application service used above X.25
networks to handshake application PDUs across the Session Service and TP0. Not needed
with TP4, and not recommended for use in the U.S. except when talking to X.400 ADMDs.
[Source: RFC1208]
RTT
See: Round-Trip Time
SAP
Service Access Point. The point at which the services of an OSI layer are made available to
the next higher layer. The SAP is named according to the layer providing the services, e.g.,
Transport services are provided at a Transport SAP (TSAP) at the top of the Transport Layer.
[Source: RFC1208]
Scottish and Northern Ireland JANET User Group (SNIJUG)
The Scottish and Northern Ireland JANET User Group (SNIJUG) presents the views of the
users on JANET and UKERNA services to the JISC Committee on Networking through the
JANET National User Group. See also: JANET National User Group.
SDH
See: Synchronous Digital Hierarchy
selector
The identifier used by an OSI entity to distinguish among multiple SAPs at which it provides
services to the layer above. See port. [Source: RFC1208]
Serial Line IP (SLIP)
A protocol used to run IP over serial lines, such as telephone circuits or RS-232 cables,
interconnecting two systems. SLIP is defined in RFC 1055. See also: Point-to-Point Protocol.
[Source: RFC1392]
SERJUG
See: South East JANET Regional User Group
server
A provider of resources (e.g., file servers and name servers). See also: client, Domain Name
System, Network File System. [Source: RFC1392]
Service Level Agreement
A contractual agreement between a service provider and a service user about the level of
performance of the service, and indeed the provider. An example is the SLA between JISC
and UKERNA for the JANET service.
Session Layer
The OSI layer that provides means for dialogue control between end systems. [Source:
RFC1208]
SGMP
Simple Gateway Management Protocol. The predecessor to SNMP. See SNMP. [Source:
RFC1208]
SGML
See: Standardized Generalized Markup Language
SIG
Special Interest Group [Source: RFC1392]
signal-to-noise ratio
When used in reference to Usenet activity, signal-to-noise ratio describes the relation between
amount of actual information in a discussion, compared to their quantity. More often than not,
there's substantial activity in a newsgroup, but a very small number of those articles actually
contain anything useful.
signature
The three or four line message at the bottom of a piece of email or a Usenet article which
identifies the sender. Large signatures (over five lines) are generally frowned upon. See also:
Electronic Mail, Usenet. [Source: RFC1392]
Simple Mail Transfer Protocol (SMTP)
A protocol, defined in RFC 821, used to transfer electronic mail between computers, with
extensions specified in many other RFCs. It is a server to server protocol, so other protocols
are used to access the messages. See also: Electronic Mail, Post Office Protocol, RFC 822.
[Source: RFC1392]
Simple Network Management Protocol (SNMP)
The Internet standard protocol developed to manage nodes on an IP network. The first version
is defined in RFC 1157 (STD 15). SNMPv2 (version 2) is defined in too many RFCs to list. It
is currently possible to manage wiring hubs, toasters, jukeboxes, etc. See also: Management
Information Base. [Source: RFC1392]
SLA
See: Service Level Agreement
SLIP
See: Serial Line IP
SMDS
See: Switched Multimegabit Data Service
SMI
See: Structure of Management Information
SMTP
See: Simple Mail Transfer Protocol
SNA
See: Systems Network Architecture
snail mail
A pejorative term referring to the U.S. postal service.
SNIJUG
See: Scottish and Northern Ireland JANET User Group
SNMP
See: Simple Network Management Protocol
SOA
See: Start of Authority Record
SONET
See: Synchronous Optical NETwork
South East JANET Regional User Group (SERJUG)
The South East JANET Regional User Group (SERJUG) presents the views of the users on
JANET and UKERNA services to the JISC Committee on Networking through the JANET
National User Group. See also: JANET National User Group.
South West JANET Regional User Group (SWJRUG)
The South West JANET Regional User Group (SWJRUG) presents the views of the users on
JANET and UKERNA services to the JISC Committee on Networking through the JANET
National User Group. See also: JANET National User Group.
SPAG (1)
Standards Promotion and Application Group. A group of European OSI manufacturers which
chooses option subsets and publishes these in a "Guide to the Use of Standards" (GUS).
[Source: RFC1208]
SPAG (2)
Service Performance Advisory group, formerly MSC, a subgroup of JISC, responsible for
development and trend analysis of JANET.
spam
send an email message or news message to large numbers of email distribution lists or Usenet
newsgroups, to the annoyance of most recipients, and contrary to Netiquette.
Spread Spectrum
Transmission of a signal using a carrier whose frequency spectrum varies over a wide range in
a pseudo random manner. Detection and interception are difficult as transmissions appear
similar to background noise. Reception is done by cross correlation of the wide band signal
with a replica of the spectrum of the sender, synchronized between sender and receiver.
The two main methods are Frequency Hopping (FH or FHSS) and Direct Sequence (DS or
DSSS). In FH the output frequencies hop around the desired range according to a pseudo
random sequence of numbers fed into the frequency synthesizer. In DS a narrow band signal
is spread into a wideband signal using a pseudo random chipping code sequence (a rather
higher data rate bit sequence) which determines the spreading ratio. This is also known as
Phase Shift Keying or phase modulation. For 802.11b Wireless Local Area Networks the
modulation scheme is known as Complementary Code Keying (CCK) and for 802.11a it is
known as Orthogonal Frequency Division Multiplexing (OFDM). The signal is despread at
the receiver with the same code sequence, using the redundant information in the code
sequence to aid error correction in case of interference. See also: 802.11, Wireless Local Area
Network.
SQL
Structured Query Language. The international standard language for defining and accessing
relational databases. [Source: RFC1208]
Squid
A Web proxy cache package.
SSH
Secure Shell, a package for eliciting secure (i.e. encrypted) interactive connections across a
public network such as the Internet.
SSL
Secure Socket Layer protocol, a method for eliciting secure (i.e. encrypted) connections (e.g.
to web services) across a public network such as the Internet. Now extended as Transport
Layer Security (TLS).
STAN
JANET Spam-relay Tester And Notification system, for checking electronic mail servers for
weaknesses which might promote spam.
Standardized Generalized Markup Language (SGML)
An international standard for the definition of system- independent, device-independent
methods of representing text in electronic form. Different applications can be developed using
Document Type Definitions (DTDs) e.g. HTML. See also: Hypertext Markup Language.
[Source: RFC1983]
Start of Authority Record (SOA Record)
A DNS resource record type indicating which host is authorative for a particular domain. See
also: Domain Name System.
STD
A sub series of RFCs that specify Internet standards. The official list of Internet standards is
in STD 1. See also: For Your Information, Request For Comments. [Source: RFC1392]
stream-oriented
A type of transport service that allows its client to send data in a continuous stream. The
transport service will guarantee that all data will be delivered to the other end in the same
order as sent and without duplicates. See also: Transmission Control Protocol. [Source:
MALAMUD]
Structure of Management Information (SMI)
The rules used to define the objects that can be accessed via a network management protocol.
This protocol is defined in STD 16, RFC 1155. See also: Management Information Base.
[Source: RFC1208]
stub network
A stub network only carries packets to and from local hosts. Even if it has paths to more than
one other network, it does not carry traffic for other networks. See also: backbone, transit
network. [Source: RFC1392]
subnet
A portion of a network, which may be a physically independent network segment, which
shares a network address with other portions of the network and is distinguished by a subnet
number. A subnet is to a network what a network is to an internet. See also: internet, network.
[Source: FYI4]
subnet address
The subnet portion of an IP address. In a subnetted network, the host portion of an IP address
is split into a subnet portion and a host portion using an address (subnet) mask. See also:
address mask, IP address, network address, host address. [Source: RFC1392]
subnet mask
See: address mask
subnet number
See: subnet address
subnetwork
A collection of OSI end systems and intermediate systems under the control of a single
administrative domain and utilizing a single network access protocol. Examples:- private X.25
networks, collection of bridged LANs. [Source: RFC1208]
SUfi
Scottish University for industry.
summarize
To encapsulate a number of responses into one coherent, usable message. Often done on
controlled mailing lists or active newsgroups, to help reduce bandwidth.
SuperJANET
SuperJANET 4 is a very high performance backbone network based on optical fiber
technology, offering up to 2.5 Gigabits/sec transmission rates in April 2001. This new
network is needed to support advanced applications requiring a mixture of voice, data, image
and video communications. The network is designed to use the most up-to-date
communications technology - synchronous digital hierarchy (SDH) access - within the
backbone between Core Points of Presence (C-PoPs) and to Backbone Access Routers
(BARs) at the boundary of each regional MAN. A testbed network using DWDM is also in
use.
SWERN
South West England Regional Network.
Switched Multimegabit Data Service (SMDS)
An emerging high-speed datagram-based public data network service developed by Bellcore
and expected to be widely used by telephone companies as the basis for their data networks.
See also: Metropolitan Area Network. [Source: RFC1208]
SWJRUG
See: South West JANET Regional User Group
synchronous
Data communications in which transmissions are sent at a fixed rate, with the sending and
receiving devices synchronized.
Synchronous Digital Hierarchy (SDH)
The European standard for high-speed data communications over fiber-optic media. The
transmission rates range from 155.52Mbps to 2.5Gbps. [Source: RFC1983]
Synchronous Optical NETwork (SONET)
SONET is an international standard for high-speed data communications over fiber-optic
media. The transmission rates range from 51.84Mbps to 2.5Gbps. [Source: RFC1983]
Systems Network Architecture (SNA)
A proprietary networking architecture used by IBM and IBM- compatible mainframe
computers. [Source: NNSC]
T1
A term for a digital carrier facility used to transmit a DS-1 formatted digital signal at 1.544
megabits per second. [Source: RFC1392]
T3
A term for a digital carrier facility used to transmit a DS-3 formatted digital signal at 44.746
megabits per second. [Source: FYI4]
TAC
See: Terminal Access Controller (TAC)
TAU
Technical Advisory Unit, a JISC sponsored service, performs regular monitoring of JANET,
JISCMail and the National Cache, and advises JISC on technical matters.
talk
A protocol which allows two people on remote computers to communicate in a real-time
fashion. See also: Internet Relay Chat. [Source: RFC1392]
TCP
See: Transmission Control Protocol
TCP/IP Protocol Suite
Transmission Control Protocol over Internet Protocol. This is a common shorthand which
refers to the suite of transport and application protocols which runs over IP. See also: IP,
ICMP, TCP, UDP, FTP, Telnet, SMTP, SNMP. [Source: RFC1392]
TechDis
JISC funded Technology for Disabilities information service.
TELENET
A public packet switched network using the CCITT X.25 protocols. It should not be confused
with Telnet. [Source: RFC1392]
Telnet
Telnet is the Internet standard protocol for remote terminal connection service. It is defined in
STD 8, RFC 854 and extended with options by many other RFCs. [Source: RFC1392]
TEN-155
Trans European Network at 155Mbit/s, now replaced by GÉANT.
TERENA
See: Trans-European Research and Education Networking Association
Terminal Access Controller (TAC)
A device which was once used to connect terminals to the Internet, usually using dialup
modem connections and the TACACS protocol. While the device is no longer in use,
TACACS+ is a protocol in current use. [Source: RFC1983]
terminal emulator
A program that allows a computer to emulate a terminal. The workstation thus appears as a
terminal to the remote host. [Source: MALAMUD]
terminal server
A device which connects many terminals to a LAN through one network connection. A
terminal server can also connect many network users to its asynchronous ports for dial-out
capabilities and printer access. See also: Local Area Network. [Source: RFC1392]
TeX
A free typesetting system by Donald Knuth.
Three Letter Acronym (TLA)
A tribute to the use of acronyms in the computer field. See also: Extended Four Letter
Acronym. [Source: RFC1392]
three-way-handshake
The process whereby two protocol entities synchronize during connection establishment.
[Source: RFC1208]
Time to Live (TTL)
A field in the IP header which indicates how long this packet should be allowed to survive
before being discarded. It is primarily used as a hop count. See also: Internet Protocol.
[Source: MALAMUD]
TLA
See: Three Letter Acronym
TN3270
A variant of the Telnet program that allows one to attach to IBM mainframes and use the
mainframe as if you had a 3270 or similar terminal. [Source: BIG-LAN]
token ring
A token ring is a type of LAN with nodes wired into a ring. Each node constantly passes a
control message (token) on to the next; whichever node has the token can send a message.
Often, "Token Ring" is used to refer to the IEEE 802.5 token ring standard, which is the most
common type of token ring. See also: 802.x, Local Area Network. [Source: RFC1392]
topology
A network topology shows the computers and the links between them. A network layer must
stay abreast of the current network topology to be able to route packets to their final
destination. [Source: MALAMUD]
TP0
OSI Transport Protocol Class 0 (Simple Class). This is the simplest OSI Transport Protocol,
useful only on top of an X.25 network (or other network that does not lose or damage data).
[Source: RFC1208]
TP4
OSI Transport Protocol Class 4 (Error Detection and Recovery Class). This is the most
powerful OSI Transport Protocol, useful on top of any type of network. TP4 is the OSI
equivalent to TCP. [Source: RFC1208]
traceroute
A program available on many systems which traces the path a packet takes to a destination. It
is mostly used to debug routing problems between hosts. There is also a traceroute protocol
defined in RFC 1393. [Source: RFC1983]
transceiver
Transmitter-receiver. The physical device that connects a host interface to a local area
network, such as Ethernet. Ethernet transceivers contain electronics that apply signals to the
cable and sense collisions. [Source: RFC1208]
transit network
A transit network passes traffic between networks in addition to carrying traffic for its own
hosts. It must have paths to at least two other networks. See also: backbone, stub network.
[Source: RFC1392]
Transmission Control Protocol (TCP)
An Internet Standard transport layer protocol defined in RFC 793. It is connection-oriented
and stream-oriented, as opposed to UDP. See also: connection-oriented, stream-oriented, User
Datagram Protocol. [Source: RFC1392]
Transport Layer
The OSI layer that is responsible for reliable end- to-end data transfer between end systems.
[Source: RFC1208]
Transport Layer Security (TLS)
An IETF standard in RFC 2246 for eliciting secure (i.e. encrypted) connections (e.g. to web
services) across a public network such as the Internet. Formerly known as Secure Sockets
Layer (SSL).
Trojan Horse
A computer program which carries within itself a means to allow the creator of the program
access to the system using it. See also: virus, worm. See RFC 1135. [Source: RFC1392]
TS29
a network independent version of X29. The dependency of X29 on X25 is removed. See also
Green Book.
TSI
The MAPS Transport Security Initiative.
TTFN
Ta-Ta For Now [Source: RFC1392]
TTL
See: Time to Live
tunneling
Tunneling refers to encapsulation of protocol A within protocol B, such that A treats B as
though it were a datalink layer. Tunneling is used to get data between administrative domains
which use a protocol that is not supported by the internet connecting those domains. See also:
Administrative Domain. [Source: RFC1392]
TVN
Thames Valley Network.
twisted pair
A type of cable in which pairs of conductors are twisted together to produce certain electrical
properties. [Source: RFC1392]
UA
User Agent. An OSI application process that represents a human user or organization in the
X.400 Message Handling System. Creates, submits, and takes delivery of messages on the
user's behalf. [Source: RFC1208]
UBE
Unsolicited Bulk Email.
UCE
Unsolicited Commercial Email.
UCISA
Universities and Colleges Information Systems Association, with several subgroups,
including UCISA-NG, the Networking Group.
UDP
See: User Datagram Protocol
Ufi
University for industry, not strictly a University, nor for Industry.
UHI Network
University of Highlands and Islands Network.
UKERNA
the UK Education and Research Networking Association; funded by the Joint Information
Systems Committee of the Higher Education Funding Councils and others to manage the
academic network and its developments. Formerly the JNT.
ULCC
University of London Computer Centre, home of various networking facilities.
unicast
An address which only one host will recognize. See also: broadcast, multicast. [Source:
RFC1983]
Uniform Resource Locator (URL)
A URL is a compact (most of the time) string representation for a resource available on the
Internet. URLs are primarily used to retrieve information using WWW. The syntax and
semantics for URLs are defined in RFC 1738. See also: World Wide Web. [Source:
RFC1983]
Universal Time Coordinated (UTC)
This is Greenwich Mean Time. [Source: MALAMUD]
UNIX-to-UNIX CoPy (UUCP)
This was initially a program run under the UNIX operating system that allowed one UNIX
system to send files to another UNIX system via dial-up phone lines. Today, the term is more
commonly used to describe the large international network which uses the UUCP protocol to
pass news and electronic mail. See also: Electronic Mail, Usenet. [Source: RFC1392]
Unrouteable Address
Certain ranges of IP addresses are designated in RFC 1918 as exclusively for internal use.
These are 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.16.255.255, and 192.168.0.0 to
192.168.255.255. A correctly configured router will not allow packets from any of these
addresses through to the Internet. The only way that information can pass between hosts with
any of these IP addresses and the outside world is to have a device (typically a firewall) that
translates between these internal addresses and a specific collection of IP addresses that are
assigned in the normal way. The internal IP addresses can be safely re-used in many such
locations. See also: Network Address Translation, IP Address.
urban legend
A story, which may have started with a grain of truth, that has been embroidered and retold
until it has passed into the realm of myth. It is an interesting phenomenon that these stories
get spread so far, so fast and so often. Urban legends never die, they just end up on the
Internet! Some legends that periodically make their rounds include "The Infamous Modem
Tax," "Craig Shergold/Brain Tumor/Get Well Cards," and "The $250 Cookie Recipe".
[Source: LAQUEY]
URL
See: Uniform Resource Locator
Usenet
A collection of thousands of topically named newsgroups, the computers which run the
protocols, and the people who read and submit Usenet news. Not all Internet hosts subscribe
to Usenet and not all Usenet hosts are on the Internet. See also: Network News Transfer
Protocol, UNIX-to-UNIX CoPy. [Source: NWNET]
User Datagram Protocol (UDP)
An Internet Standard transport layer protocol defined in STD 6, RFC 768. It is a
connectionless protocol which adds a level of reliability and multiplexing to IP. See also:
connectionless, Transmission Control Protocol. [Source: RFC1392]
UTC
See: Universal Time Coordinated
UUCP
See: UNIX-to-UNIX CoPy
uudecode
A program which reverses the effect of uuencode. See also: uuencode. [Source: RFC1983]
uuencode
A program which reversibly converts a binary file in ASCII. It is used to send binary files via
email, which generally does not allow (or garbles) the transmission of binary information. The
original binary can be restored with uudecode. The encoding process generally creates an
ASCII file larger than the original binary, so compressing the binary before running uuencode
is highly recommended. [Source: RFC1983]
VBS
Visual Basic Scriplet (Microsoft).
Veronica
A Gopher utility which effectively searches Gopher servers based on a user's list of keywords.
The name was chosen to be a "mate" to another utility named "Archie." It later became an
acronym for Very Easy Rodent Oriented Netwide Index to Computer Archives. See also:
archie, Gopher. [Source: RFC1983]
virtual circuit
A network service which provides connection-oriented service regardless of the underlying
network structure. See also: connection-oriented. [Source: RFC1392]
Virtual Private Network (VPN)
A client across a public network such as the Internet may appear to be part of a private
network by encapsulating the private packets inside public packets which are routed in the
normal way to a device (typically a firewall) on the private network which unpacks them and
sends them on the private network, a process known as tunneling. The tunnel can exist at the
data link layer using Point to Point Tunneling Protocol (PPTP) or the IETF standard Layer 2
Tunneling Protocol (L2TP) from RFC 2661, or at the IP layer using IETF-defined IP Security
(IPsec) protocol extensions from RFC 2402 and RFC 2406. There should also be some form
of authentication and authorization, and encryption of at least the authentication process (and
preferably data transfers too) so IPsec is the most desirable method.
virus
A program which replicates itself on computer systems by incorporating itself into other
programs which are shared among computer systems. See also: Trojan Horse, worm. [Source:
RFC1392]
VPN
See: Virtual Private Network
VTAS
Video Technology Advisory Service, a UKERNA service.
W3
See: World Wide Web
W3C
World Wide Web Consortium, a governing body for web standards.
WAIS
See: Wide Area Information Servers
WAE
See: Wireless Application Environment
WAN
See: Wide area network
WAP
See: Wireless Application Protocol
WDP
See: Wireless Datagram Protocol
WEP
See: Wired Equivalent Privacy
WLAN
See: Wireless Local Area Network
WML
See: Wireless Markup Language
WSP
See: Wireless Session Protocol
WTA
See: Wireless Telephony Application
WTLS
See: Wireless Transport Layer Security protocol
WTP
See: Wireless Transaction Protocol
WebCrawler
A WWW search engine. The aim of the WebCrawler Project is to provide a high-quality, fast,
and free Internet search service. The WebCrawler may be reached at
"http://webcrawler.com/". [Source: WebCrawler's "WebCrawler Facts"]
WG
See: Working Group
White Book
a document produced for the JNT setting out the strategy to be adopted by the Academic
Community in its transition from interim standards (Coloured Books) to ISO standards.
Overtaken by history - an IP.
white pages
The Internet supports several databases that contain basic information about users, such as
email addresses, telephone numbers, and postal addresses. These databases can be searched to
get information about particular individuals. Because they serve a function akin to the
telephone book, these databases are often referred to as "white pages. See also: Knowbot,
netfind, whois, X.500. [Source: RFC1392]
Wireless Application Protocol (WAP)
A stack of protocols, akin to the OSI model or the TCP/IP stack, to implement the layers
needed for communication with wireless devices, security, applications, etc, promoted as an
open standard by the WAP Forum www.wapforum.org.
Wireless Application Protocol Gateway
A WAP client may receive documents from an ordinary WWW server via a WAP gateway, a
proxy which converts between WAP requests and HTTP requests (including CGI programs)
and converts the output to WAP formats (e.g. WML or WMLScript) followed by compression
to binary for sending to the client. WWW pages may also be coded directly in WML on the
WWW server before receipt by the gateway.
Wireless Application Environment (WAE)
WAE is the programming environment for WAP. WAE is handled by a browser program in
the device, and consists of Wireless Markup Language (WML), WMLScript and Wireless
Telephony Application (WTA).
Wireless Datagram Protocol (WDP)
The transport layer of WAP, which transforms datagrams from upper layer protocols into the
formats specific to datapaths, bearers and devices, e.g. GSM or SMS or GPRS. Thus upper
layers have no need to program for the physical layer of communication such as air interface.
Wired Equivalent Privacy (WEP)
A security protocol within IEE standard 802.11b intended to give Wireless Local Area
Networks the degree of privacy expected of fixed LANs. Encryption over air between the
devices and fixed access points (rather than end to end) goes part way towards countering the
eavesdropping risk of signals spilling out of buildings. However, the length of the key may be
only 40 bits (up to 128 bits is allowed) even if WEP is turned on, and the encryption method
produces some predictable sequences, so it is prone to statistical analysis to recover keys.
Also the Service Set Identifier (SSID) is broadcast in clear in probes from the access point
(unless turned off); this is used as a "password" for packets sent between members of specific
LANs, so is useful for eavesdroppers to acquire, especially if obvious names are chosen e.g.
10Downing.
As an interim solution, the IEE 802.1x standard is available for port-level authentication and
key management i.e. rapid changes and secure key delivery. This incorporates Extensible
Authentication Protocol (EAP) from RFC 2284. This was first designed for wired (e.g. dialup)
links, and is not itself a cipher standard, so the first version authenticates the MAC address
rather than the user. The authentication is passed through from the fixed access point to an
authentication server such as RADIUS or Kerberos. However, there are no checks that an
access point is what it claims to be, so there is a way of masquerading or intercepting the
authentication process.
Work on the 802.11i standard is ongoing at March 2002, but this addresses such issues as
mutual and per-packet authentication, and could incorporate Advanced Encryption Standard
(AES).
It is imperative that further security measures are taken on top of WEP and its immediate
successors, such as Virtual Private Network schemes, although Network Layer solutions such
as IPsec are tricky when roaming devices use DHCP for dynamic IP addresses, and products
orientated to wireless working are necessary. See also: 802.11, Kerberos, RADIUS, Wireless
Local Area Network.
Wireless Local Area Network (WLAN)
A data network intended to serve an area of only a few hundred square meters or less, using
radio communications between mobile computers and (typically) a fixed access point which
provides onward connections to fixed networks such as the Internet. There are several
competing technologies such as HIPERLAN in Europe and the 802.11 series in the USA. This
is the next level up in distance from Personal Area Networks such as Bluetooth. See also:
Bluetooth, 802.11, HIPERLAN.
Wireless Markup Language (WML)
The markup language for WAP, a tag-based language like HTML. Strictly, WML is a
Document Type Definition (DTD) of eXtendable Markup Language, which implied a
relationship with the DTD for (strictly defined) HTML.
Wireless Session Protocol (WSP)
The session layer of WAP, handling the interface between the application layer WAE and the
transaction layer WTP. Sessions can be connection-orientated or connectionless, and can be
suspended and resumed on demand.
Wireless Telephony Application (WTA)
The telephony interface for WAP, part of Wireless Application Environment (WAE). WTA
can control telephony functions of the device from WML or WMLScript, or from requests
from the network.
Wireless Transport Layer Security protocol (WTLS)
WTLS handles security for WAP, i.e. encryption, decryption, user authentication and data
integrity checking of datagrams from upper layer protocols before passing to the transport
layer WDP. It is based on the fixed network Transport Layer Security (TLS) protocol,
formerly Secure Sockets Layer.
Wireless Transaction Protocol (WTP)
WTP is the transaction layer of WAP, which takes data packets from the session layer WSP
and chops them into lower layer datagrams to pass to the security layer WTLS, or reassembles
them at the far end. WTP also tracks sequences of sent and received packets, handling
retransmissions or acknowledgements as required.
whois
An Internet program which allows users to query a database of people and other Internet
entities, such as domains, networks, and hosts, kept at the DDN NIC. The information for
people shows a person's company name, address, phone number and email address. See also:
Defense Data Network Network ..., white pages, Knowbot, X.500. [Source: FYI4]
Wide Area Information Servers (WAIS)
A distributed information service which offers simple natural language input, indexed
searching for fast retrieval, and a "relevance feedback" mechanism which allows the results of
initial searches to influence future searches. Public domain implementations are available. See
also: archie, Gopher, Prospero. [Source: RFC1392]
Wide Area Network (WAN)
A network, usually constructed with serial lines, which covers a large geographic area. See
also: Local Area Network, Metropolitan Area Network. [Source: RFC1392]
WML
See: Wireless Markup Language
WMLScript
A scripting language for WML, akin to Javascript or ECMAScript for HTML, which can
control functions in the browser or the phone, using scripts downloaded from the server.
Working Group (WG)
A working group, within the IETF, is a group of people who work under a charter to achieve a
certain goal. That goal may be the creation of an Informational document, the creation of a
protocol specification, or the resolution of problems in the Internet. Most working groups
have a finite lifetime. That is, once a working group has achieved its goal, it disbands. There
is no official membership for a working group. Unofficially, a working group member is
somebody who is on that working group's mailing list; however, anyone may attend a
working group meeting. See also: Internet Engineering Task Force, Birds Of a Feather.
[Source: RFC1983]
World Wide Web (WWW or W3)
A hypertext-based, distributed information system created by researchers at CERN in
Switzerland. Users may create, edit or browse hypertext documents. The clients and servers
are freely available. [Source: RFC1392]
workstation
A networked personal computing device with more power than a standard IBM PC or
Macintosh. Typically, a workstation has an operating system such as Unix that is capable of
running several tasks at the same time. It has several megabytes of memory and a large, high-
resolution display. Examples are Sun SPARCstation and Digital Alpha stations.
worm
A computer program which replicates itself and is self- propagating. Worms, as opposed to
viruses, are meant to spawn in network environments. Network worms were first defined by
Shoch & Hupp of Xerox in ACM Communications (March 1982). The Internet worm of
November 1988 is perhaps the most famous; it successfully propagated itself on over 6,000
systems across the Internet. See also: Trojan Horse, virus. [Source: RFC1392]
WRT
With Respect To [Source: RFC1392]
WWW
See: World Wide Web
WYSIWYG
What You See is What You Get [Source: RFC1392]
X
X is the name for TCP/IP based network-oriented window systems. Network window systems
allow a program to use a display on a different computer. The most widely-implemented
window system is X11 - a component of MIT's Project Athena. [Source: RFC1392]
X.21
An interface for synchronous operation on public data networks, a successor for V.24 and
V.25 definitions, from ITU-T. Data rates can be up to 2Mbits/s.
X.25
A data communications interface specification developed to describe how data passes into and
out of public data communications networks. The CCITT and ISO approved protocol suite
defines protocol layers 1 through 3. [Source: RFC1392]
X.29
a protocol defining the control packet format between the PAD and remote host regarding the
virtual terminal parameters (the X3 parameters) and changes in their values. X29 uses packets
defined by X25.
X.400
The CCITT and ISO standard for electronic mail. It is widely used in Europe and Canada. See
also: MHS. [Source: RFC1392]
X.500
The CCITT and ISO standard for electronic directory services. See also: DSA, white pages,
Knowbot, WHOIS. [Source: RFC1392]
XDR
See: eXternal Data Representation
XDSL
A Digital Subscriber Line similar to ISDN.
Xerox Network System (XNS)
A network developed by Xerox corporation. Implementations exist for both 4.3BSD derived
systems, as well as the Xerox Star computers. [Source: RFC1392]
XHTML
Extensible Hypertext Markup Language.
XML
See: Extendable Markup Language.
XNS
See: Xerox Network System
X/Open
A group of computer manufacturers that promotes the development of portable applications
based on UNIX. They publish a document called the X/Open Portability Guide.
X Recommendations
The CCITT documents that describe data communication network standards. Well-known
ones include:- X.25 Packet Switching standard, X.400 Message Handling System, and X.500
Directory Services.
Yahoo!
Yahoo! is a hierarchical subject-oriented guide for the World Wide Web and Internet. Yahoo!
lists sites and categorizes them into appropriate subject categories. Yahoo! may be reached at
"http://www.yahoo.com/". [Source: Yahoo's "What is Yahoo?"]
Yellow Book or YBTS
Yellow Book Transport Service; a transport service protocol now rarely used by the UK
academic and research community.
Yellow Pages (YP)
YHMAN
Yorkshire and Humberside Metropolitan Area Network.
YP
zone
A logical group of network devices (AppleTalk). [Source: RFC1392]
References:
BIG-LAN "BIG-LAN Frequently Asked Questions Memo", BIG-LAN DIGEST, V4:I8, February 14, 1992.
COMER Comer, D., "Internetworking with TCP/IP: Principles, Protocols and Architecture", Prentice Hall,
Englewood Cliffs, NJ, 1991.
FYI4 Malkin, G., and A. Marine, "FYI on Questions and Answers: Answers to Commonly asked "New Internet
User" Questions", FYI 4, RFC 1325, Xylogics, SRI, May 1992.
HACKER "THIS IS THE JARGON FILE", Version 2.9.8, January 1992.
HPCC "Grand Challenges 1993: High Performance Computing and Communications", Committee on Physical,
Mathmatical and Engineering Sciences of the Federal Coordinating Council for Science, Engineering and
Technology.
MALAMUD Malamud, C., "Analyzing Sun Networks", Van Nostrand Reinhold, New York, NY, 1992.
NNSC "NNSC's Hypercard Tour of the Internet".
LAQUEY LaQuey, T. (with J. Ryer), "The Internet Companion: A Beginner's Guide to Global Networking",
Addison-Wesley, Reading, MA, 1992.
NWNET Kochmer, J., and NorthWestNet, "The Internet Passport: NorthWestNets Guide to Our World Online",
NorthWestNet, Bellevue, WA, 1992.
RFC1208 Jacobsen, O., and D. Lynch, "A Glossary of Networking Terms",

RFC 1208, Interop, Inc., March 1991.
STD1 Postel, J., "IAB Official Protocol Standards", STD 1, RFC

1360, Internet Architecture Board, September 1992.
STD2 Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC

1340, USC/Information Sciences Institute, July 1992.
TAN Tanenbaum, A., "Computer Networks; 2nd ed.", Prentice Hall,

Englewood Cliffs, NJ, 1989.
ZEN Kehoe, B., "Zen and the Art of the Internet", February 1992.
Security Considerations:
While security is not explicitly discussed in this document, some of the glossary's entries are security related.
See the entries for Access Control List (ACL), authentication, Computer Emergency Response Team (CERT),
cracker, Data Encryption Key (DEK), Data Encryption Standard (DES), encryption, Kerberos, Message Digest
(MD-2, MD-4, MD-5), Pretty Good Privacy (PGP), Privacy Enhanced Mail (PEM), Trojan Horse, virus, and
worm.
Authors' Addresses:
Gary Scott Malkin
Xylogics, Inc. 53 Third Avenue, Burlington, MA 01803 Phone: (617) 238-6237
EMail: gmalkin@Xylogics.COM
Tracy LaQuey Parker

University of Texas at Austin, Computation Center, Austin, TX 78712 Phone: (512) 471-2444
EMail: tracy@utexas.edu
*** The copyright to this document remains with myself and the University
of Bradford, subject to the terms of the original documents quoted
within. You may make the copies requested for internal company use. The up-to-
date URL is http://www.et.brad.ac.uk/help/.xferfile/.glossary.html
Please be aware that this glossary is meant for a UK academic audience so there
are many UK-specific terms and items of historical interest (since we cover the
development of networking in our Telecommunications-related degrees). If UK
engineers are included, this may be of benefit. They're on their own with Aloha,
however! :-)
David Loomes
A P P E N D I X C
Organizationally Unique Identifiers (OUI)

Current as of May 2, 2002
To find a more current list, just enter “OUI table IEEE” into your favorite online search engine and
you should be able to locate several links to this information…
Manufacturer OUI Code Manufacturer OUI Code

Xerox .......................... 00:00:00 Prodigy Sys..................... 00:00:28
Xerox .......................... 00:00:01 Imc Net......................... 00:00:29
Xerox .......................... 00:00:02 TRW-Sedd/Inp.................... 00:00:2A
Xerox .......................... 00:00:03 Crisp Auto...................... 00:00:2B
Xerox .......................... 00:00:04 Autotote........................ 00:00:2C
Xerox .......................... 00:00:05 Chromatics...................... 00:00:2D
Xerox .......................... 00:00:06 Societe Evira................... 00:00:2E
Xerox .......................... 00:00:07 Timeplex........................ 00:00:2F
Xerox .......................... 00:00:08 VG Laboratory Sys............... 00:00:30
Xerox .......................... 00:00:09 QPSX Comm....................... 00:00:31
Omron Tateisi Elec ............. 00:00:0A Marconi......................... 00:00:32
Matrix ......................... 00:00:0B Egan Mach....................... 00:00:33
Cisco .......................... 00:00:0C Network Resources............... 00:00:34
Fibronics ...................... 00:00:0D Spectragraphics................. 00:00:35
Fujitsu ........................ 00:00:0E Atari........................... 00:00:36
Next ........................... 00:00:0F Oxford Metrics.................. 00:00:37
Sytek .......................... 00:00:10 CSS Labs........................ 00:00:38
Normerel Sys ................... 00:00:11 Toshiba......................... 00:00:39
Info Tech ...................... 00:00:12 Chyron.......................... 00:00:3A
Camex .......................... 00:00:13 I Ctls.......................... 00:00:3B
Netronix ....................... 00:00:14 Auspex Sys...................... 00:00:3C
Datapoint ...................... 00:00:15 Unisys.......................... 00:00:3D
Du Pont Pixel Sys .............. 00:00:16 Simpact......................... 00:00:3E
Tekelec ........................ 00:00:17 Syntrex......................... 00:00:3F
Webster Comp ................... 00:00:18 Applicon........................ 00:00:40
Applied Dyn Intl ............... 00:00:19 ICE ............................ 00:00:41
Adv Micro Dev .................. 00:00:1A Metier Management Sys........... 00:00:42
Novell ......................... 00:00:1B Micro Tech...................... 00:00:43
Bell Tech ...................... 00:00:1C Castelle........................ 00:00:44
Cabletron Sys .................. 00:00:1D Ford Aerospace & Comm....... 00:00:45
Telsist Ind Elec ............... 00:00:1E Olivetti........................ 00:00:46
Telco Sys ...................... 00:00:1F Nicolet Inst.................... 00:00:47
Dataindustrier Diab ............ 00:00:20 Seiko Epson..................... 00:00:48
Sureman Comp & Comm ........ 00:00:21 Apricot Comp.................... 00:00:49
Visual Tech .................... 00:00:22 Adc Codenoll Tech............... 00:00:4A
Abb Ind Sys .................... 00:00:23 ICL Data........................ 00:00:4B
Connect As ..................... 00:00:24 NEC ............................ 00:00:4C
Ramtek ......................... 00:00:25 Dci ............................ 00:00:4D
Sha-ken ........................ 00:00:26 Ampex........................... 00:00:4E
Japan Radio Co ................. 00:00:27 Logicraft....................... 00:00:4F
Radisys ........................ 00:00:50 Datahouse Info Sys.............. 00:00:8A
Hob Elec ....................... 00:00:51 Infotron........................ 00:00:8B
Intrusion.com .................. 00:00:52 Alloy Comp Prod................. 00:00:8C
Compucorp ...................... 00:00:53 Verdix.......................... 00:00:8D
Modicon ........................ 00:00:54 Solbourne Comp.................. 00:00:8E
Commissariat Atom .............. 00:00:55 Raytheon Company................ 00:00:8F
Dr B Struck .................... 00:00:56 Microcom........................ 00:00:90
Scitex ......................... 00:00:57 Anritsu......................... 00:00:91
Racore Comp Prod ............... 00:00:58 Cogent Data Tech................ 00:00:92
Hellige ........................ 00:00:59 Proteon......................... 00:00:93
SysKonnect ..................... 00:00:5A Asante.......................... 00:00:94
Eltec Elektronik ............... 00:00:5B Sony Tektronix.................. 00:00:95
Telematics Intl ................ 00:00:5C Marconi Elec.................... 00:00:96
CS Telecom ..................... 00:00:5D Epoch Sys....................... 00:00:97
USC ............................ 00:00:5E Crosscomm....................... 00:00:98
Sumitomo Elec Ind .............. 00:00:5F MTX............................. 00:00:99
Kontron Elek ................... 00:00:60 RC Comp......................... 00:00:9A
Gateway Comm ................... 00:00:61 Info Intl....................... 00:00:9B
Bull Hn Info Sys ............... 00:00:62 Rolm Mil-Spec Comp.............. 00:00:9C
Dr.ing.seufert ................. 00:00:63 Locus Comp...................... 00:00:9D
Yokogawa ....................... 00:00:64 Marli........................... 00:00:9E
Network Assoc .................. 00:00:65 Ameristar Tech.................. 00:00:9F
Talaris Sys .................... 00:00:66 Tokyo Sanyo Elec................ 00:00:A0
Soft*Rite ...................... 00:00:67 Marquette Elec.................. 00:00:A1
Rosemount Ctls ................. 00:00:68 Bay Net......................... 00:00:A2
Concord Comm ................... 00:00:69 Network App Tech................ 00:00:A3
Comp Consoles .................. 00:00:6A Acorn........................... 00:00:A4
Silicon Graphics ............... 00:00:6B Compatible Sys.................. 00:00:A5
Cray Comm ...................... 00:00:6D Network General................. 00:00:A6
Artisoft ....................... 00:00:6E Network Comp Dev................ 00:00:A7
Madge .......................... 00:00:6F Stratus Comp.................... 00:00:A8
HCL ............................ 00:00:70 Network Sys..................... 00:00:A9
Adra Sys ....................... 00:00:71 Xerox........................... 00:00:AA
Miniware Tech .................. 00:00:72 Logic Modeling.................. 00:00:AB
Siecor ......................... 00:00:73 Conware Comp Cons............... 00:00:AC
Ricoh Company .................. 00:00:74 Bruker Inst..................... 00:00:AD
Nortel ......................... 00:00:75 Dassault Elec................... 00:00:AE
Abekas Video Sys ............... 00:00:76 Nuclear Data Inst............... 00:00:AF
Interphase ..................... 00:00:77 Rnd-Rad Net Dev................. 00:00:B0
Labtam ......................... 00:00:78 Alpha Micro..................... 00:00:B1
Networth ....................... 00:00:79 Televideo Sys................... 00:00:B2
Dana Comp ...................... 00:00:7A Cimlinc......................... 00:00:B3
Research Machines .............. 00:00:7B Edimax Comp..................... 00:00:B4
Ampere ......................... 00:00:7C Datability Soft Sys............. 00:00:B5
Sun Micro ...................... 00:00:7D Micro-matic Res................. 00:00:B6
Clustrix ....................... 00:00:7E Dove Comp....................... 00:00:B7
Linotype-Hell .................. 00:00:7F Seikosha........................ 00:00:B8
Cray Comm ...................... 00:00:80 McDonnell Douglas Comp Sys...... 00:00:B9
Bay Net ........................ 00:00:81 Siig............................ 00:00:BA
Lectra Sys ..................... 00:00:82 Tri-data........................ 00:00:BB
Tadpole Tech ................... 00:00:83 Allen-Bradley................... 00:00:BC
Supernet ....................... 00:00:84 Mitsubishi Cable Company........ 00:00:BD
Canon .......................... 00:00:85 NTI Group....................... 00:00:BE
Megahertz ...................... 00:00:86 Symmetric Comp Sys.............. 00:00:BF
Hitachi ........................ 00:00:87 Western Digital................. 00:00:C0
Comp Net Tech .................. 00:00:88 Madge........................... 00:00:C1
Cayman Sys ..................... 00:00:89 Info Pres Tech.................. 00:00:C2
Harris Corp Comp Sys Div ....... 00:00:C3 Meiko........................... 00:00:FC
Waters Div Millipore ........... 00:00:C4 High Level Hardware............. 00:00:FD
Farallon ....................... 00:00:C5 Annapolis Micro Sys............. 00:00:FE
Eon Sys ........................ 00:00:C6 Camtec Elec..................... 00:00:FF
Arix ........................... 00:00:C7 Equip'trans................ 00:01:00
Altos Comp Sys ................. 00:00:C8 3Com............................ 00:01:02
Emulex ......................... 00:00:C9 3Com............................ 00:01:03
Applitek ....................... 00:00:CA Dvico........................... 00:01:04
Compu-Shack Elec ............... 00:00:CB Beckhoff........................ 00:01:05
Densan ......................... 00:00:CC Tews Datentechnik............... 00:01:06
Centrecom Sys .................. 00:00:CD Leiser.......................... 00:01:07
Megadata ....................... 00:00:CE Avlab Tech...................... 00:01:08
Hayes Microcomp Prod ........... 00:00:CF Nagano Japan Radio.............. 00:01:09
Develcon Elec .................. 00:00:D0 Cis Tech........................ 00:01:0A
Adaptec ........................ 00:00:D1 Space Cyberlink................. 00:01:0B
SBE ............................ 00:00:D2 System Talks.................... 00:01:0C
Wang Lab ....................... 00:00:D3 Coreco.......................... 00:01:0D
Pure Data ...................... 00:00:D4 Bri-link Tech................... 00:01:0E
Micrognosis Intl ............... 00:00:D5 Nishan Sys...................... 00:01:0F
Punch Line Holding ............. 00:00:D6 Gotham Net...................... 00:01:10
Dartmouth ...................... 00:00:D7 Idigm........................... 00:01:11
Novell ......................... 00:00:D8 Shark Multimedia................ 00:01:12
Nippon T&T ................. 00:00:D9 Olympus Optical................. 00:01:13
Atex ........................... 00:00:DA Kanda Tsushin Kogyo............. 00:01:14
British Telecomm ............... 00:00:DB Extratech....................... 00:01:15
Hayes Microcomp Prod ........... 00:00:DC Netspect Tech................... 00:01:16
TCL ............................ 00:00:DD Canal........................... 00:01:17
Cetia .......................... 00:00:DE Ez Digital...................... 00:01:18
Bell & Howell Pub Sys Div .. 00:00:DF Action Ctls..................... 00:01:19
Quadram ........................ 00:00:E0 Eeh Datalink.................... 00:01:1A
Grid Sys ....................... 00:00:E1 Unizone Tech.................... 00:01:1B
Acer Tech ...................... 00:00:E2 Universal Talkware.............. 00:01:1C
Integrated Micro Prod .......... 00:00:E3 Centillium Comm................. 00:01:1D
IN2 Groupe Intertech ........... 00:00:E4 Precidia Tech................... 00:01:1E
Sigmex ......................... 00:00:E5 RC Net.......................... 00:01:1F
Aptor Prod De Comm Ind ......... 00:00:E6 Oscilloquartz................... 00:01:20
Star Gate Tech ................. 00:00:E7 Rapidstream..................... 00:01:21
Accton Tech .................... 00:00:E8 Trend Comm...................... 00:01:22
Isicad ......................... 00:00:E9 Digital Elec.................... 00:01:23
Upnod .......................... 00:00:EA Acer............................ 00:01:24
Matsushita Comm Ind ............ 00:00:EB Yaesu Musen..................... 00:01:25
Microprocess ................... 00:00:EC Pac Labs........................ 00:01:26
April .......................... 00:00:ED Open Group...................... 00:01:27
Network Designers .............. 00:00:EE Enjoyweb........................ 00:01:28
Kti ............................ 00:00:EF Dfi ............................ 00:01:29
Samsung Elec ................... 00:00:F0 Telematica Sistems Intel........ 00:01:2A
Magna Comp ..................... 00:00:F1 Telenet......................... 00:01:2B
Spider Comm .................... 00:00:F2 Aravox Tech..................... 00:01:2C
Gandalf Data ................... 00:00:F3 Komodo Tech..................... 00:01:2D
Allied Telesyn Intl ............ 00:00:F4 PC Partner...................... 00:01:2E
Diamond Sales .................. 00:00:F5 Twinhead Intl................... 00:01:2F
Applied Micro .................. 00:00:F6 Extreme Net..................... 00:01:30
Youth Keep Ent ................. 00:00:F7 Detection Sys................... 00:01:31
DEC ............................ 00:00:F8 Dranetz - Bmi................... 00:01:32
Quotron Sys .................... 00:00:F9 Kyowa Elec Inst................. 00:01:33
Microsage Comp Sys ............. 00:00:FA Sig Positec Sys................. 00:01:34
Rechner Zur Kommunikation ...... 00:00:FB KDC ............................ 00:01:35
Cybertan Tech .................. 00:01:36 Haitai Elec..................... 00:01:6F
IT Farm ........................ 00:01:37 Ese Embedded Sys Eng............ 00:01:70
Xavi Tech ...................... 00:01:38 Allied Data Tech................ 00:01:71
Point Multimedia Sys ........... 00:01:39 Technoland...................... 00:01:72
Shelcad Comm ................... 00:01:3A Jni............................. 00:01:73
Bna Sys ........................ 00:01:3B Cyberoptics..................... 00:01:74
Tiw Sys ........................ 00:01:3C Radiant Comm.................... 00:01:75
Riscstation .................... 00:01:3D Orient Silver Ent............... 00:01:76
Ascom Tateco ................... 00:01:3E Edsl............................ 00:01:77
Neighbor World ................. 00:01:3F Margi Sys....................... 00:01:78
Sendtek ........................ 00:01:40 Wireless Tech................... 00:01:79
Cable Print .................... 00:01:41 Chengdu Maipu Elec Ind.......... 00:01:7A
Cisco .......................... 00:01:42 Heidelberger Druckmaschinen..... 00:01:7B
Cisco .......................... 00:01:43 AG-E............................ 00:01:7C
Cereva Net ..................... 00:01:44 Thermoquest..................... 00:01:7D
Winsystems ..................... 00:01:45 Adtek Sys Sci................... 00:01:7E
Tesco Ctls ..................... 00:01:46 Experience Music Proj........... 00:01:7F
Zhone Tech ..................... 00:01:47 Aopen........................... 00:01:80
X-traweb ....................... 00:01:48 Nortel.......................... 00:01:81
TDT Transfer Data Test ......... 00:01:49 Dica Tech....................... 00:01:82
Sony Comp Science Labs ......... 00:01:4A Anite Telecoms.................. 00:01:83
Ennovate Net ................... 00:01:4B Sieb & Meyer................ 00:01:84
Berkeley Process Ctl ........... 00:01:4C Aloka........................... 00:01:85
Shin Kin Ent ................... 00:01:4D Disch........................... 00:01:86
Win Ent ........................ 00:01:4E I2SE............................ 00:01:87
Luminous Net ................... 00:01:4F LXCO Tech....................... 00:01:88
Gilat Comm ..................... 00:01:50 Refraction Tech................. 00:01:89
Ensemble Comm .................. 00:01:51 Roi Comp........................ 00:01:8A
Chromatek ...................... 00:01:52 Netlinks........................ 00:01:8B
Archtek Telecom ................ 00:01:53 Mega Vision..................... 00:01:8C
G3M ............................ 00:01:54 Audesi Tech..................... 00:01:8D
Promise Tech ................... 00:01:55 Logitec......................... 00:01:8E
Firewiredirect.com ............. 00:01:56 Kenetec......................... 00:01:8F
Syswave ........................ 00:01:57 SMK-M........................... 00:01:90
Electro Ind/Gauge Tech ......... 00:01:58 Syred Data Sys.................. 00:01:91
S1 ............................. 00:01:59 Texas Digital Sys............... 00:01:92
Digital Video Broad ............ 00:01:5A Hanbyul Telecom................. 00:01:93
Italtel ........................ 00:01:5B Capital Equip................... 00:01:94
Cadant ......................... 00:01:5C Sena Tech....................... 00:01:95
Pirus Net ...................... 00:01:5D Cisco........................... 00:01:96
Best Tech ...................... 00:01:5E Cisco........................... 00:01:97
Digital Design ................. 00:01:5F Darim Vision.................... 00:01:98
Elmex .......................... 00:01:60 Heisei Elec..................... 00:01:99
Meta Machine Tech .............. 00:01:61 Leunig.......................... 00:01:9A
Cygnet Tech .................... 00:01:62 Kyoto Micro..................... 00:01:9B
Cisco .......................... 00:01:63 JDS Uniphase.................... 00:01:9C
Cisco .......................... 00:01:64 E-Control Sys................... 00:01:9D
Airswitch ...................... 00:01:65 ESS Tech........................ 00:01:9E
TC Group ....................... 00:01:66 Phonex Broadband................ 00:01:9F
Hioki EE ....................... 00:01:67 Infinilink...................... 00:01:A0
Vitana ......................... 00:01:68 Mag-tek......................... 00:01:A1
Celestix Net ................... 00:01:69 Logical......................... 00:01:A2
Alitec ......................... 00:01:6A Genesys Logic................... 00:01:A3
Lightchip ...................... 00:01:6B Microlink....................... 00:01:A4
Foxconn ........................ 00:01:6C Nextcomm........................ 00:01:A5
Triton Net Sys ................. 00:01:6D Scientific-Atlanta Arcodan...... 00:01:A6
Conklin ........................ 00:01:6E Unex Tech....................... 00:01:A7
Welltech Comp .................. 00:01:A8 Kinpo Elec...................... 00:01:E1
Bmw ............................ 00:01:A9 Ando Elec....................... 00:01:E2
Airspan Comm ................... 00:01:AA Siemens......................... 00:01:E3
Main Street Net ................ 00:01:AB Sitera.......................... 00:01:E4
Sitara Net ..................... 00:01:AC Supernet........................ 00:01:E5
Coach Master Intl .............. 00:01:AD Hewlett Packard................. 00:01:E6
Trex Ent ....................... 00:01:AE Hewlett Packard................. 00:01:E7
Motorola Comp Group ............ 00:01:AF Force10 Net..................... 00:01:E8
Fulltek Tech ................... 00:01:B0 Litton Marine Sys............... 00:01:E9
General Bandwidth .............. 00:01:B1 Cirilium........................ 00:01:EA
Digital Proc Sys ............... 00:01:B2 C-com........................... 00:01:EB
Precision Elec Mfg ............. 00:01:B3 Ericsson........................ 00:01:EC
Wayport ........................ 00:01:B4 Seta............................ 00:01:ED
Turin Net ...................... 00:01:B5 Comtrol Europe.................. 00:01:EE
Saejin T&M ................. 00:01:B6 Camtel Tech..................... 00:01:EF
Centos ......................... 00:01:B7 Tridium......................... 00:01:F0
Netsensity ..................... 00:01:B8 Innovative Concepts............. 00:01:F1
Skf Condition Monitoring ....... 00:01:B9 QPS ............................ 00:01:F3
IC-Net ......................... 00:01:BA Enterasys Net................... 00:01:F4
Frequentis ..................... 00:01:BB Erim............................ 00:01:F5
Brains ......................... 00:01:BC Assoc Mus Elec Ind.............. 00:01:F6
Peterson Electro-Musical Prod .. 00:01:BD Image Display Sys............... 00:01:F7
Gigalink ....................... 00:01:BE Adherent Sys.................... 00:01:F8
Teleforce ...................... 00:01:BF Teraglobal Comm................. 00:01:F9
Compulab ....................... 00:01:C0 Horoscas........................ 00:01:FA
Exbit Tech ..................... 00:01:C1 Dotop Tech...................... 00:01:FB
Ark Res ........................ 00:01:C2 Keyence......................... 00:01:FC
Acromag ........................ 00:01:C3 Digital Voice Sys............... 00:01:FD
Neowave ........................ 00:01:C4 DEC ............................ 00:01:FE
Simpler Net .................... 00:01:C5 Data Direct Net................. 00:01:FF
Quarry Tech .................... 00:01:C6 Net & Sys................... 00:02:00
Cisco .......................... 00:01:C7 IFM Elec........................ 00:02:01
Thomas Conrad .................. 00:01:C8 Amino Comm...................... 00:02:02
Cisco .......................... 00:01:C9 Woonsang Telecom................ 00:02:03
Geocast Net Sys ................ 00:01:CA Bodmann Ind Elek................ 00:02:04
Netgame ........................ 00:01:CB Hitachi Denshi.................. 00:02:05
Japan Total Des Comm ........... 00:01:CC Telital R&D Denmark......... 00:02:06
Artem .......................... 00:01:CD Unify Net....................... 00:02:08
Custom Micro Prod .............. 00:01:CE Shenzhen Sed Info Tech.......... 00:02:09
Alpha Data Parallel Sys ........ 00:01:CF Gefran.......................... 00:02:0A
Vitalpoint ..................... 00:01:D0 Native Net...................... 00:02:0B
Conet Comm ..................... 00:01:D1 Metro-optix..................... 00:02:0C
Macpower Periph ................ 00:01:D2 Micronpc.com.................... 00:02:0D
Paxcomm ........................ 00:01:D3 Laurel Net...................... 00:02:0E
Leisure Time ................... 00:01:D4 AATR............................ 00:02:0F
Haedong Info & Comm ........ 00:01:D5 Fenecom......................... 00:02:10
Man Roland Druckmaschinen ...... 00:01:D6 Nature Worldwide Tech........... 00:02:11
F5 Net ......................... 00:01:D7 Sierracom....................... 00:02:12
Teltronics ..................... 00:01:D8 SDEL............................ 00:02:13
Sigma .......................... 00:01:D9 Dtvro........................... 00:02:14
Wincomm ........................ 00:01:DA Cotas Comp Tech................. 00:02:15
Freecom Tech ................... 00:01:DB Cisco........................... 00:02:16
Activetelco .................... 00:01:DC Cisco........................... 00:02:17
Avail Net ...................... 00:01:DD Adv Sci Corp.................... 00:02:18
Trango Sys ..................... 00:01:DE Paralon Tech.................... 00:02:19
Isdn Comm ...................... 00:01:DF Zuma Net........................ 00:02:1A
Fast Sys ....................... 00:01:E0 Kollmorgen-Servotronix.......... 00:02:1B
Network Elements ............... 00:02:1C IBM............................. 00:02:55
Data General Comm .............. 00:02:1D Alpha Processor................. 00:02:56
Simtel ......................... 00:02:1E Microcom........................ 00:02:57
Aculab ......................... 00:02:1F Flying Packets Comm............. 00:02:58
Canon Aptex .................... 00:02:20 Tsann Kuen...................... 00:02:59
DSP App ........................ 00:02:21 Catena Net...................... 00:02:5A
Chromisys ...................... 00:02:22 Cambridge Silicon Radio......... 00:02:5B
Clicktv ........................ 00:02:23 Sci Sys (kunshan)............... 00:02:5C
Lantern Comm ................... 00:02:24 High Tech....................... 00:02:5E
Certus Tech .................... 00:02:25 Nortel.......................... 00:02:5F
Xesystems ...................... 00:02:26 Accordion Net................... 00:02:60
Esd ............................ 00:02:27 I3 Micro Tech................... 00:02:61
Necsom ......................... 00:02:28 Soyo Group Soyo Com Tech........ 00:02:62
Adtec .......................... 00:02:29 UPS Mfg......................... 00:02:63
Asound Elec .................... 00:02:2A Audioramp.com................... 00:02:64
Tamura Elec Works .............. 00:02:2B Virditech....................... 00:02:65
Abb Bomem ...................... 00:02:2C Thermalogic..................... 00:02:66
Agere .......................... 00:02:2D Node Runner..................... 00:02:67
Teac R& D .................. 00:02:2E Harris Government Comm.......... 00:02:68
P-cube ......................... 00:02:2F Nadatel......................... 00:02:69
Intersoft Elec ................. 00:02:30 Cocess Telecom.................. 00:02:6A
Ingersoll-Rand ................. 00:02:31 Bcm Comp........................ 00:02:6B
Avision ........................ 00:02:32 Philips Cft..................... 00:02:6C
Mantra Comm .................... 00:02:33 Adept Telecom................... 00:02:6D
Imperial Tech .................. 00:02:34 Negen Access.................... 00:02:6E
Paragon Net Intl ............... 00:02:35 Senao Intl...................... 00:02:6F
Init ........................... 00:02:36 Crewave......................... 00:02:70
Cosmo Res ...................... 00:02:37 Vpacket Comm.................... 00:02:71
Serome Tech .................... 00:02:38 Cc&c Tech................... 00:02:72
Visicom ........................ 00:02:39 Coriolis Net.................... 00:02:73
ZSK Stickmaschinen ............. 00:02:3A Tommy Tech...................... 00:02:74
Redback Net .................... 00:02:3B Smart Tech...................... 00:02:75
Creative Tech .................. 00:02:3C Primax Elec..................... 00:02:76
Nuspeed ........................ 00:02:3D Cash Sys Ind.................... 00:02:77
Selta Telematica ............... 00:02:3E Samsung Electro-mech............ 00:02:78
Compal Elec .................... 00:02:3F Control App..................... 00:02:79
Seedek ......................... 00:02:40 IOI Tech........................ 00:02:7A
Amer.com ....................... 00:02:41 Amplify Net..................... 00:02:7B
Videoframe Sys ................. 00:02:42 Trilithic....................... 00:02:7C
Raysis ......................... 00:02:43 Cisco........................... 00:02:7D
Surecom Tech ................... 00:02:44 Cisco........................... 00:02:7E
Lampus ......................... 00:02:45 ask-technologies.com............ 00:02:7F
All-win Tech ................... 00:02:46 Mu Net.......................... 00:02:80
Great Dragon Info Tec .......... 00:02:47 Red-M........................... 00:02:81
Pila ........................... 00:02:48 Viaclix......................... 00:02:82
Aviv Infocom ................... 00:02:49 Spectrum Ctls................... 00:02:83
Cisco .......................... 00:02:4A Alstom T&D P&C.......... 00:02:84
Cisco .......................... 00:02:4B Riverstone Net.................. 00:02:85
Sibyte ......................... 00:02:4C Occam Net....................... 00:02:86
Mannesman Dematic Colby ........ 00:02:4D Adapcom......................... 00:02:87
Datacard Group ................. 00:02:4E Global Village.................. 00:02:88
IPM Datacom .................... 00:02:4F Dne Tech........................ 00:02:89
Geyser Net ..................... 00:02:50 Ambit Micro..................... 00:02:8A
Soma Net ....................... 00:02:51 VDSL Sys........................ 00:02:8B
Carrier ........................ 00:02:52 Micrel-Synergy Semi............. 00:02:8C
Televideo ...................... 00:02:53 Movita Tech..................... 00:02:8D
Worldgate ...................... 00:02:54 Rapid 5 Net..................... 00:02:8E
Globetek ....................... 00:02:8F Mellanox Tech................... 00:02:C9
Woorigisool .................... 00:02:90 Endpoints....................... 00:02:CA
Open Net ....................... 00:02:91 Tristate........................ 00:02:CB
Logic Innov .................... 00:02:92 MCCI............................ 00:02:CC
Solid Data Sys ................. 00:02:93 Teledream....................... 00:02:CD
Tokyo Sokushin ................. 00:02:94 Foxjet.......................... 00:02:CE
Ip.access ...................... 00:02:95 Zygate Comm..................... 00:02:CF
Lectron ........................ 00:02:96 Comdial......................... 00:02:D0
C-cor.net ...................... 00:02:97 Vivotek......................... 00:02:D1
Broadframe ..................... 00:02:98 Workstation..................... 00:02:D2
Apex ........................... 00:02:99 NetBotz......................... 00:02:D3
Storage Apps ................... 00:02:9A Pda Peripherals................. 00:02:D4
Kreatel Comm ................... 00:02:9B Acr ............................ 00:02:D5
Merix .......................... 00:02:9D Nice Sys........................ 00:02:D6
Info Equip ..................... 00:02:9E Empeg........................... 00:02:D7
L-3 Comm Aviation Recorders .... 00:02:9F Brecis Comm..................... 00:02:D8
Flatstack ...................... 00:02:A0 Reliable Ctls................... 00:02:D9
World Wide Packets ............. 00:02:A1 Exio Comm....................... 00:02:DA
Hilscher ....................... 00:02:A2 Netsec.......................... 00:02:DB
Abb Power Auto ................. 00:02:A3 Fujitsu General................. 00:02:DC
Addpac Tech .................... 00:02:A4 Bromax Comm..................... 00:02:DD
Compaq ......................... 00:02:A5 Astrodesign..................... 00:02:DE
Effinet Sys .................... 00:02:A6 Net Com Sys..................... 00:02:DF
Vivace Net ..................... 00:02:A7 Etas............................ 00:02:E0
Air Link Tech .................. 00:02:A8 Integrated Net.................. 00:02:E1
Racom .......................... 00:02:A9 Ndc Infared Eng................. 00:02:E2
Plcom .......................... 00:02:AA Lite-On Comm.................... 00:02:E3
CTC Union Tech ................. 00:02:AB JC Hyun Sys..................... 00:02:E4
3Par Data ...................... 00:02:AC Timeware........................ 00:02:E5
Asahi Optical .................. 00:02:AD Gould Inst Sys.................. 00:02:E6
Scannex Elec ................... 00:02:AE Cab & Co Kg................. 00:02:E7
Telecruz Tech .................. 00:02:AF ED&A........................ 00:02:E8
Hokubu Comm & Ind .......... 00:02:B0 CS Sys De Sec................... 00:02:E9
Anritsu ........................ 00:02:B1 Videonics....................... 00:02:EA
Cablevision .................... 00:02:B2 Easent Comm..................... 00:02:EB
Intel .......................... 00:02:B3 Maschoff Des Eng................ 00:02:EC
Daphne ......................... 00:02:B4 DXO Telecom..................... 00:02:ED
Avnet .......................... 00:02:B5 Nokia Danmark................... 00:02:EE
Acrosser Tech .................. 00:02:B6 Ccc Net Sys Group............... 00:02:EF
Watanabe Elec Ind .............. 00:02:B7 Ame Optimedia Tech.............. 00:02:F0
Whi Konsult .................... 00:02:B8 Pinetron........................ 00:02:F1
Cisco .......................... 00:02:B9 edevice......................... 00:02:F2
Cisco .......................... 00:02:BA Media Serve..................... 00:02:F3
Continuous Comp ................ 00:02:BB PCTel........................... 00:02:F4
Lvl 7 Sys ...................... 00:02:BC Vive Synergies.................. 00:02:F5
Bionet ......................... 00:02:BD Equipe Comm..................... 00:02:F6
Totsu Eng ...................... 00:02:BE Arm ............................ 00:02:F7
dotrocket ...................... 00:02:BF Seakr Eng....................... 00:02:F8
Bencent Tzeng Ind .............. 00:02:C0 Mimos Semi Sdn Bhd.............. 00:02:F9
Innovative Elec Des ............ 00:02:C1 DX Antenna...................... 00:02:FA
Net Vision Telecom ............. 00:02:C2 Baumuller Aulugen-sys........... 00:02:FB
Arelnet ........................ 00:02:C3 Cisco........................... 00:02:FC
Vector Intl Buba ............... 00:02:C4 Cisco........................... 00:02:FD
Evertz Micro ................... 00:02:C5 Viditec......................... 00:02:FE
Data Track Tech ................ 00:02:C6 Handan Broad Infocom............ 00:02:FF
Alps Elec ...................... 00:02:C7 Netcontinuum.................... 00:03:00
Technocom Comm Tech ............ 00:02:C8 Avantas Net..................... 00:03:01
Oasys Telecom .................. 00:03:02 Tami Tech....................... 00:03:3B
Jama Elec ...................... 00:03:03 Daiden.......................... 00:03:3C
Pacific Broadband Comm ......... 00:03:04 Ilshin Lab...................... 00:03:3D
Smart Net Dev .................. 00:03:05 Tateyama Sys Lab................ 00:03:3E
Fusion In Tech ................. 00:03:06 Bigband Net..................... 00:03:3F
Secure Works ................... 00:03:07 Floware Wireless Sys............ 00:03:40
Am Comm ........................ 00:03:08 Axon Dig Design................. 00:03:41
Texcel Tech .................... 00:03:09 Nortel.......................... 00:03:42
Argus Tech ..................... 00:03:0A Martin Prof..................... 00:03:43
Hunter Tech .................... 00:03:0B Tietech......................... 00:03:44
Telesoft Tech .................. 00:03:0C Routrek Net..................... 00:03:45
Uniwill Comp ................... 00:03:0D Hitachi Kokusai Elec............ 00:03:46
Core Comm ...................... 00:03:0E Intel........................... 00:03:47
Legend Dig ..................... 00:03:0F Norscan Inst.................... 00:03:48
Link Evolution ................. 00:03:10 Vidicode Datacomm............... 00:03:49
Micro Tech ..................... 00:03:11 Rias............................ 00:03:4A
TR-Systemtechnik ............... 00:03:12 Nortel.......................... 00:03:4B
Access Media ................... 00:03:13 Shanghai Digivision Tech........ 00:03:4C
Teleware Net Sys ............... 00:03:14 Chiaro Net...................... 00:03:4D
Cidco .......................... 00:03:15 Pos Data........................ 00:03:4E
Nobell Comm .................... 00:03:16 Sur-Gard Sec.................... 00:03:4F
Merlin Sys ..................... 00:03:17 Bticino......................... 00:03:50
Cyras Sys ...................... 00:03:18 Diebold......................... 00:03:51
Infineon ....................... 00:03:19 Colubris Net.................... 00:03:52
Beijing Broad Telecom China .... 00:03:1A Mitac........................... 00:03:53
Cellvision Sys ................. 00:03:1B Fiber Log Comm.................. 00:03:54
Svenska Hardvarufabriken ....... 00:03:1C Terabeam Internet Sys........... 00:03:55
Taiwan Commate Comp ............ 00:03:1D Wincor Nixdorf.................. 00:03:56
Optranet ....................... 00:03:1E Intervoice-Brite................ 00:03:57
Condev ......................... 00:03:1F Icable Sys...................... 00:03:58
Xpeed .......................... 00:03:20 Digitalsis...................... 00:03:59
Reco Res ....................... 00:03:21 Phototron....................... 00:03:5A
Idis ........................... 00:03:22 Bridge Wave Comm................ 00:03:5B
Cornet Tech .................... 00:03:23 Saint Song...................... 00:03:5C
Tottori Sanyo Elec ............. 00:03:24 Bosung Hi-net................... 00:03:5D
Arima Comp ..................... 00:03:25 Metropolitan Area Net........... 00:03:5E
Iwasaki Info Sys ............... 00:03:26 Schuehle Mess & Kont........ 00:03:5F
Act'l ..................... 00:03:27 Pac Interactive Tech............ 00:03:60
Mace Group ..................... 00:03:28 Widcomm......................... 00:03:61
F3 ............................. 00:03:29 Vodtel Comm..................... 00:03:62
Unidata Comm Sys ............... 00:03:2A Miraesys........................ 00:03:63
Gai Datenfunksysteme ........... 00:03:2B Scenix Semi..................... 00:03:64
Abb Ind ........................ 00:03:2C Kira Info & Comm............ 00:03:65
IBase Tech ..................... 00:03:2D Asm Pacific Tech................ 00:03:66
Scope Info Mgmt ................ 00:03:2E Jasmine Net..................... 00:03:67
Global Sun Tech ................ 00:03:2F Embedone........................ 00:03:68
Imagenics ...................... 00:03:30 Nippon Antenna.................. 00:03:69
Cisco .......................... 00:03:31 Mainnet......................... 00:03:6A
Cisco .......................... 00:03:32 Cisco........................... 00:03:6B
Digitel ........................ 00:03:33 Cisco........................... 00:03:6C
Newport Elec ................... 00:03:34 Runtop.......................... 00:03:6D
Mirae Tech ..................... 00:03:35 Nicon Sys....................... 00:03:6E
Zetes Tech ..................... 00:03:36 Telsey.......................... 00:03:6F
Vaone .......................... 00:03:37 Nxtv............................ 00:03:70
Oak Tech ....................... 00:03:38 Acomz Net....................... 00:03:71
Eurologic Sys .................. 00:03:39 ULan............................ 00:03:72
Silicon Wave ................... 00:03:3A Aselsan......................... 00:03:73
Hunter Watertech ............... 00:03:74 Xsense Tech..................... 00:03:B0
Netmedia ....................... 00:03:75 Abbott Lab...................... 00:03:B1
Graphtec Tech .................. 00:03:76 Radware......................... 00:03:B2
Gigabit Wireless ............... 00:03:77 IA Link Sys..................... 00:03:B3
Humax .......................... 00:03:78 Macrotek Intl................... 00:03:B4
Proscend Comm .................. 00:03:79 Entra Tech...................... 00:03:B5
Taiyo Yuden .................... 00:03:7A Qsi ............................ 00:03:B6
Idec Izumi ..................... 00:03:7B Zaccess Sys..................... 00:03:B7
Coax Media ..................... 00:03:7C Netkit Soln..................... 00:03:B8
Stellcom ....................... 00:03:7D Hualong Telecom................. 00:03:B9
Portech Comm ................... 00:03:7E Sun Micro....................... 00:03:BA
Atheros Comm ................... 00:03:7F Signal Comm..................... 00:03:BB
Ingenico Intl .................. 00:03:81 Cot ............................ 00:03:BC
A-One .......................... 00:03:82 Omnicluster Tech................ 00:03:BD
Metera Net ..................... 00:03:83 Netility........................ 00:03:BE
Aeta ........................... 00:03:84 Centerpoint Broadband Tech...... 00:03:BF
Actelis Net .................... 00:03:85 Rftnc........................... 00:03:C0
Ho Net ......................... 00:03:86 Packet Dynamics................. 00:03:C1
Blaze Net Prod ................. 00:03:87 Solphone........................ 00:03:C2
Fastfame Tech .................. 00:03:88 Micronik Multimedia............. 00:03:C3
Plantronics .................... 00:03:89 Tomra Sys....................... 00:03:C4
America Online ................. 00:03:8A Mobotix......................... 00:03:C5
Plus-one I&T ............... 00:03:8B Icue Sys........................ 00:03:C6
Total Impact ................... 00:03:8C Hopf Elektronik................. 00:03:C7
PCS Revenue Ctl Sys ............ 00:03:8D Cml Emergency Serv.............. 00:03:C8
Atoga Sys ...................... 00:03:8E Tecom........................... 00:03:C9
Weinschel ...................... 00:03:8F MTS Sys......................... 00:03:CA
Digital Video Comm ............. 00:03:90 Nippon Sys Dev.................. 00:03:CB
Hyundai Teletek ................ 00:03:92 Momentum Comp................... 00:03:CC
Apple .......................... 00:03:93 Clovertech...................... 00:03:CD
Connect One .................... 00:03:94 Eten Tech....................... 00:03:CE
California Amp ................. 00:03:95 Muxcom.......................... 00:03:CF
Ez Cast ........................ 00:03:96 Koankeiso....................... 00:03:D0
Watchfront Elec ................ 00:03:97 Takaya.......................... 00:03:D1
Wisi ........................... 00:03:98 Crossbeam Sys................... 00:03:D2
Dongju Info & Comm ......... 00:03:99 Internet Energy Sys............. 00:03:D3
nSine .......................... 00:03:9A Alloptic........................ 00:03:D4
Netchip Tech ................... 00:03:9B Adv Comm........................ 00:03:D5
Optimight Comm ................. 00:03:9C Radvision....................... 00:03:D6
Acer Comm & Multi .......... 00:03:9D Nextnet Wireless................ 00:03:D7
Tera Sys ....................... 00:03:9E impath Net...................... 00:03:D8
Cisco .......................... 00:03:9F Secheron Sa..................... 00:03:D9
Cisco .......................... 00:03:A0 Takamisawa Cybernetics.......... 00:03:DA
Hiper Info & Comm .......... 00:03:A1 Apogee Elec..................... 00:03:DB
Catapult Comm .................. 00:03:A2 Lexar Media..................... 00:03:DC
Mavix .......................... 00:03:A3 Comark.......................... 00:03:DD
Data Storage & Info Mgmt ... 00:03:A4 OTC Wireless.................... 00:03:DE
Medea .......................... 00:03:A5 Desana Sys...................... 00:03:DF
Unixtar Tech ................... 00:03:A7 Radioframe Net.................. 00:03:E0
Idot Comp ...................... 00:03:A8 Winmate Comm.................... 00:03:E1
Axcent Media ................... 00:03:A9 Comspace........................ 00:03:E2
Watlow ......................... 00:03:AA Cisco........................... 00:03:E3
Bridge Info Sys ................ 00:03:AB Cisco........................... 00:03:E4
Fronius Schweissmaschinen ...... 00:03:AC Hermstedt....................... 00:03:E5
Emerson Energy Sys ............. 00:03:AD Entone Tech..................... 00:03:E6
Allied Adv Mfg ................. 00:03:AE Logostek........................ 00:03:E7
Paragea Comm ................... 00:03:AF Wavelength Dig.................. 00:03:E8
Akara Canada ................... 00:03:E9 Gordon Kapes.................... 00:04:22
Mega Sys Tech .................. 00:03:EA Intel........................... 00:04:23
Atrica ......................... 00:03:EB TMC............................. 00:04:24
ICG Res ........................ 00:03:EC Atmel........................... 00:04:25
Shinkawa Elec .................. 00:03:ED Autosys......................... 00:04:26
Mknet .......................... 00:03:EE Cisco........................... 00:04:27
Oneline ........................ 00:03:EF Cisco........................... 00:04:28
Redfern Broadband Net .......... 00:03:F0 Pixord.......................... 00:04:29
Cicada Semi .................... 00:03:F1 Wireless Net.................... 00:04:2A
Seneca Net ..................... 00:03:F2 IT Access....................... 00:04:2B
Dazzle Multi ................... 00:03:F3 Minet........................... 00:04:2C
Netburner ...................... 00:03:F4 Sarian Sys...................... 00:04:2D
Chip2chip ...................... 00:03:F5 Netous Tech..................... 00:04:2E
Allegro Net .................... 00:03:F6 International Comm Prod......... 00:04:2F
Plast-control .................. 00:03:F7 Netgem.......................... 00:04:30
Sancastle Tech ................. 00:03:F8 Play Ind........................ 00:04:31
Pleiades Comm .................. 00:03:F9 Voyetra Turtle Beach............ 00:04:32
Timetra Net .................... 00:03:FA Cyberboard...................... 00:04:33
Toko Seiki ..................... 00:03:FB Accelent Sys.................... 00:04:34
Intertex Data .................. 00:03:FC Comptek Intl.................... 00:04:35
Cisco .......................... 00:03:FD Elansat Tech.................... 00:04:36
Cisco .......................... 00:03:FE Powin Info Tech................. 00:04:37
Connectix ...................... 00:03:FF Nortel.......................... 00:04:38
Lexmark Intl ................... 00:04:00 Rosco Entertainment Tech........ 00:04:39
Osaki Elec ..................... 00:04:01 Intelligent Telecomm............ 00:04:3A
Nexsan Tech .................... 00:04:02 Lava Comp Mfg................... 00:04:3B
Nexsi .......................... 00:04:03 Sonos........................... 00:04:3C
Makino Milling Mach ............ 00:04:04 Indel........................... 00:04:3D
Acn Tech ....................... 00:04:05 Telencomm....................... 00:04:3E
FA Metabox ..................... 00:04:06 Elec Sys Tech................... 00:04:3F
Topcon Posit Sys ............... 00:04:07 cyberpixie...................... 00:04:40
Sanko Elec ..................... 00:04:08 Half Dome Sys................... 00:04:41
Cratos Net ..................... 00:04:09 Nact............................ 00:04:42
Sage Sys ....................... 00:04:0A Agilent Tech.................... 00:04:43
3Com ........................... 00:04:0B Wireless Home................... 00:04:44
Kanno Works .................... 00:04:0C Lms Skalar Inst................. 00:04:45
Avaya .......................... 00:04:0D Cyzentech....................... 00:04:46
Avm ............................ 00:04:0E Acrowave Sys.................... 00:04:47
Asus Net Tech .................. 00:04:0F Polaroid Prof Imag.............. 00:04:48
Spinnaker Net .................. 00:04:10 Mapletree Net................... 00:04:49
Inkra Net ...................... 00:04:11 ipolicy Net..................... 00:04:4A
Wavesmith Net .................. 00:04:12 Nvidia.......................... 00:04:4B
Snom Tech ...................... 00:04:13 Jenoptik........................ 00:04:4C
Umezawa Musen Denki ............ 00:04:14 Cisco........................... 00:04:4D
Rasteme Sys .................... 00:04:15 Cisco........................... 00:04:4E
Parks .......................... 00:04:16 Leukhardt Sys................... 00:04:4F
Elau ........................... 00:04:17 Dmd Comp Srl.................... 00:04:50
Teltronic ...................... 00:04:18 Medrad.......................... 00:04:51
Fibercycle Net ................. 00:04:19 Rocketlogix..................... 00:04:52
INES ........................... 00:04:1A Yotta Yotta..................... 00:04:53
Digital Interfaces ............. 00:04:1B Quadriga........................ 00:04:54
ipdialog ....................... 00:04:1C Antara.net...................... 00:04:55
Corega of Amer ................. 00:04:1D Pipinghot Net................... 00:04:56
Shikoku Inst ................... 00:04:1E Universal Access Tech........... 00:04:57
Sony Comp Entertainment ........ 00:04:1F Fusion X........................ 00:04:58
Slim Dev ....................... 00:04:20 Veristar........................ 00:04:59
Ocular Net ..................... 00:04:21 Linksys Group................... 00:04:5A
Techsan Elec ................... 00:04:5B Breezecom....................... 00:04:94
Mobiwave ....................... 00:04:5C Tejas Net....................... 00:04:95
Beka Elek ...................... 00:04:5D Extreme Net..................... 00:04:96
Poly Trax Info Tech ............ 00:04:5E Macrosystem Dig Video........... 00:04:97
Evalue Tech .................... 00:04:5F Chino........................... 00:04:99
Knilink Tech ................... 00:04:60 Cisco........................... 00:04:9A
Epox Comp ...................... 00:04:61 Cisco........................... 00:04:9B
Dakos Data & Comm .......... 00:04:62 Surgient Net.................... 00:04:9C
Philips Comm Sec & Imag .... 00:04:63 Ipanema Tech.................... 00:04:9D
Fantasma Net ................... 00:04:64 Wirelink........................ 00:04:9E
ist isdn support tecknik ....... 00:04:65 Metrowerks...................... 00:04:9F
Armitel ........................ 00:04:66 Verity Inst..................... 00:04:A0
Wuhan Res Inst ................. 00:04:67 Pathway Connectivity............ 00:04:A1
Vivity ......................... 00:04:68 LSI Japan....................... 00:04:A2
Innocom ........................ 00:04:69 Microchip Tech.................. 00:04:A3
Navini Net ..................... 00:04:6A Netenabled...................... 00:04:A4
Palm Wireless .................. 00:04:6B Barco Proj Sys.................. 00:04:A5
Cyber Tech ..................... 00:04:6C Saf Tehnika..................... 00:04:A6
Cisco .......................... 00:04:6D Fabiatech....................... 00:04:A7
Cisco .......................... 00:04:6E Broadmax Tech................... 00:04:A8
Digitel Ind Eletr .............. 00:04:6F Sandstream Tech................. 00:04:A9
ipunplugged .................... 00:04:70 Jetstream Comm.................. 00:04:AA
Iprad .......................... 00:04:71 Comverse Net Sys................ 00:04:AB
Telelynx ....................... 00:04:72 IBM ............................ 00:04:AC
Photonex ....................... 00:04:73 Malibu Net...................... 00:04:AD
Legrand ........................ 00:04:74 Liquid Metronics................ 00:04:AE
3Com ........................... 00:04:75 Digital Fountain................ 00:04:AF
3Com ........................... 00:04:76 Elesign......................... 00:04:B0
e-appliance .................... 00:04:77 Signal Tech..................... 00:04:B1
G Star Tech .................... 00:04:78 Essegi Srl...................... 00:04:B2
Radius ......................... 00:04:79 Videotek........................ 00:04:B3
Axxessit ....................... 00:04:7A Ciac............................ 00:04:B4
Schlumberger ................... 00:04:7B Equitrac........................ 00:04:B5
Skidata ........................ 00:04:7C Tellumat........................ 00:04:B6
Pelco .......................... 00:04:7D Amb IT Holding.................. 00:04:B7
NKF Elec ....................... 00:04:7E Kumahira........................ 00:04:B8
Chr Mayr & Kg .............. 00:04:7F SI Soubou....................... 00:04:B9
Foundry Net .................... 00:04:80 KDD Media Will.................. 00:04:BA
Econolite Ctl Prod ............. 00:04:81 Bardac.......................... 00:04:BB
Medialogic ..................... 00:04:82 Giantec......................... 00:04:BC
Deltron Tech ................... 00:04:83 Motorola........................ 00:04:BD
Amann .......................... 00:04:84 OptXCon......................... 00:04:BE
Picolight ...................... 00:04:85 Versa Logic..................... 00:04:BF
Ittc Univ Kansas ............... 00:04:86 Cisco........................... 00:04:C0
Cogency Semi ................... 00:04:87 Cisco........................... 00:04:C1
Eurotherm Act .................. 00:04:88 Magnipix........................ 00:04:C2
Yafo Net ....................... 00:04:89 Castor.......................... 00:04:C3
Temia Vertriebs ................ 00:04:8A Allen & Health.............. 00:04:C4
Poscon ......................... 00:04:8B ASE Tech........................ 00:04:C5
Nayna Net ...................... 00:04:8C Yamaha.......................... 00:04:C6
Tone Commander Sys ............. 00:04:8D NetMount........................ 00:04:C7
Ohm Tech Labs .................. 00:04:8E LIBA Maschinefabrik............. 00:04:C8
TD Sys ......................... 00:04:8F Micro Electron.................. 00:04:C9
Optical Access ................. 00:04:90 FreeMs.......................... 00:04:CA
Technovision ................... 00:04:91 Tdsoft Comm..................... 00:04:CB
Hive Internet .................. 00:04:92 Peek Traffic.................... 00:04:CC
Tsinghua Unisplendour .......... 00:04:93 Informedia Res Grp.............. 00:04:CD
Patria Ailon ................... 00:04:CE Fine Appliance.................. 00:05:07
Seagate ........................ 00:04:CF Inetcam......................... 00:05:08
Softlink ....................... 00:04:D0 AVOC Nishimura.................. 00:05:09
Drew Tech ...................... 00:04:D1 ICS............................. 00:05:0A
Adcon Telemtry ................. 00:04:D2 SICOM Sys....................... 00:05:0B
Toyokeiki ...................... 00:04:D3 Network Photonics............... 00:05:0C
Proview Elect .................. 00:04:D4 Midstream Tech.................. 00:05:0D
Hitachi ........................ 00:04:D5 3ware........................... 00:05:0E
Takagi Ind ..................... 00:04:D6 Tanaka.......................... 00:05:0F
Omitec Instr ................... 00:04:D7 Infinite Shanghai Comm.......... 00:05:10
IPWireless ..................... 00:04:D8 Complementaty Tech.............. 00:05:11
Titan Elect .................... 00:04:D9 MeshNetworks.................... 00:05:12
Relax Tech ..................... 00:04:DA VTLinx Multimedia Sys........... 00:05:13
Tellus Group ................... 00:04:DB KDT Sys......................... 00:05:14
Nortel ......................... 00:04:DC Nuark........................... 00:05:15
Cisco .......................... 00:04:DD SMART Modular Tech.............. 00:05:16
Cisco .......................... 00:04:DE Shellcomm....................... 00:05:17
Teracom Telematica ............. 00:04:DF Jupiters Tech................... 00:05:18
Procket Net .................... 00:04:E0 Siemens Build Tech.............. 00:05:19
Infinior Microsys .............. 00:04:E1 3Com Europe..................... 00:05:1A
SMC Net ........................ 00:04:E2 Magic Control Tech.............. 00:05:1B
Accton Tech .................... 00:04:E3 Xnet Tech....................... 00:05:1C
Daeryung Ind ................... 00:04:E4 Airocon......................... 00:05:1D
Glonet Sys ..................... 00:04:E5 Rhapsody Net.................... 00:05:1E
Banyan Net ..................... 00:04:E6 Taijin Media.................... 00:05:1F
Lightpointe Comm ............... 00:04:E7 Smartronix...................... 00:05:20
IER ............................ 00:04:E8 Control Microsys................ 00:05:21
Infiniswitch ................... 00:04:E9 LEA*D Corp...................... 00:05:22
HP ............................. 00:04:EA AVL List........................ 00:05:23
Paxonet Comm ................... 00:04:EB BTL Sys......................... 00:05:24
Memobox ........................ 00:04:EC Puretek Ind..................... 00:05:25
Billion Elect .................. 00:04:ED IPAS............................ 00:05:26
Lincoln Elect .................. 00:04:EE SJ Tek.......................... 00:05:27
Polestar ....................... 00:04:EF New Focus....................... 00:05:28
International Comp ............. 00:04:F0 Shanghai Broadan Comm........... 00:05:29
WhereNet ....................... 00:04:F1 Ikegami Tsushinki............... 00:05:2A
Circa Comm ..................... 00:04:F2 HORIBA.......................... 00:05:2B
FS Forth-Sys ................... 00:04:F3 Supreme Magic................... 00:05:2C
Infinite Elect ................. 00:04:F4 Zoltrix Intl.................... 00:05:2D
SnowShore Net .................. 00:04:F5 Cinta Net....................... 00:05:2E
Amphus ......................... 00:04:F6 Leviton Voice & Data........ 00:05:2F
Omega Band ..................... 00:04:F7 Andiamo Sys..................... 00:05:30
Qualicable TV Ind .............. 00:04:F8 Cisco........................... 00:05:31
Xtera Comm ..................... 00:04:F9 Cisco........................... 00:05:32
MIST ........................... 00:04:FA Sanera Sys...................... 00:05:33
Commtech ....................... 00:04:FB Northstar Eng................... 00:05:34
Stratus Comp ................... 00:04:FC Chip PC......................... 00:05:35
Japan Control Eng .............. 00:04:FD Danam Comm...................... 00:05:36
Pelago Net ..................... 00:04:FE Nets Tech....................... 00:05:37
Acronet ........................ 00:04:FF Merilus......................... 00:05:38
Cisco .......................... 00:05:00 A Brand New World in Sweden..... 00:05:39
Cisco .......................... 00:05:01 Willowglen Serv................. 00:05:3A
Apple .......................... 00:05:02 Harbour Net..................... 00:05:3B
ICONAG ......................... 00:05:03 Xircom.......................... 00:05:3C
Naray Inf & Comm ........... 00:05:04 Agere........................... 00:05:3D
Sys Integ Solns ................ 00:05:05 KID Sys......................... 00:05:3E
Reddo Net ...................... 00:05:06 VisionTek....................... 00:05:3F
FAST Corp ...................... 00:05:40 RCO Security.................... 00:05:7C
Advanced Sys ................... 00:05:41 Sun Comm........................ 00:05:7D
Otari .......................... 00:05:42 Eckelmann Steuerungstechnik..... 00:05:7E
IQ Wireless .................... 00:05:43 Acqis Tech...................... 00:05:7F
Valley Tech .................... 00:05:44 Fibrolan........................ 00:05:80
Internet Photonics ............. 00:05:45 Snell & Wilcox.............. 00:05:81
KDD Net Sys .................... 00:05:46 ClearCube Tech.................. 00:05:82
Starent Net .................... 00:05:47 ImageCom........................ 00:05:83
Disco Corp ..................... 00:05:48 AbsoluteValue Sys............... 00:05:84
Salira Opt Net Sys ............. 00:05:49 Juniper Net..................... 00:05:85
Ario Data Net .................. 00:05:4A Lucent.......................... 00:05:86
Micro Innov .................... 00:05:4B Locus........................... 00:05:87
RF Innov ....................... 00:05:4C Sensoria........................ 00:05:88
Brans Tech ..................... 00:05:4D National Datacomputer........... 00:05:89
Philips Components ............. 00:05:4E Netcom.......................... 00:05:8A
Digi-Tech Comm ................. 00:05:50 IPmental........................ 00:05:8B
F&S Elekt Sys .............. 00:05:51 Opentech........................ 00:05:8C
Xycotec Comp ................... 00:05:52 Lynx Photonic Net............... 00:05:8D
DVC Company .................... 00:05:53 Ahead Comm Sys.................. 00:05:8E
Rangestar Wireless ............. 00:05:54 CLCsoft......................... 00:05:8F
Japan Cash Machine ............. 00:05:55 Ascom Bus Sys................... 00:05:90
360 Sys ........................ 00:05:56 Active Silicon.................. 00:05:91
Agile TV ....................... 00:05:57 Pultex.......................... 00:05:92
Synchronous .................... 00:05:58 Grammar Engine.................. 00:05:93
Intracom ....................... 00:05:59 IXXAT Automation................ 00:05:94
Power Dsine .................... 00:05:5A Alesis.......................... 00:05:95
Charles Ind .................... 00:05:5B Genotech........................ 00:05:96
Kowa Company ................... 00:05:5C Eagle Traffic Ctrl Sys.......... 00:05:97
D-Link Sys ..................... 00:05:5D CRONOS.......................... 00:05:98
Cisco .......................... 00:05:5E PEI Elect....................... 00:05:99
Cisco .......................... 00:05:5F Cisco........................... 00:05:9A
Leader Comm .................... 00:05:60 Cisco........................... 00:05:9B
nac Image Tech ................. 00:05:61 Kleinknecht..................... 00:05:9C
Digital View ................... 00:05:62 Daniel Comp Sys................. 00:05:9D
J-Works ........................ 00:05:63 Zinwell......................... 00:05:9E
Tsinghua Bitway ................ 00:05:64 Yotta Net....................... 00:05:9F
Tailyn Comm .................... 00:05:65 MOBILINE........................ 00:05:A0
Secui.com ...................... 00:05:66 Zenocom......................... 00:05:A1
Etymonic Design ................ 00:05:67 CELOX Net....................... 00:05:A2
Piltofish Net .................. 00:05:68 QEI ............................ 00:05:A3
VMWARE ......................... 00:05:69 Lucid Voice..................... 00:05:A4
CP Tech ........................ 00:05:6B KOTT............................ 00:05:A5
Hung Chang ..................... 00:05:6C Extron Elect.................... 00:05:A6
Pacific Corp ................... 00:05:6D Hyperchip....................... 00:05:A7
National Enhance Tech .......... 00:05:6E Wyle Elec....................... 00:05:A8
Innomedia Tech ................. 00:05:6F Princeton Net................... 00:05:A9
Baydel ......................... 00:05:70 Moore Ind....................... 00:05:AA
Seiwa Elect .................... 00:05:71 Cyber Fone...................... 00:05:AB
Deonet ......................... 00:05:72 Northern Digital................ 00:05:AC
Cisco .......................... 00:05:73 Topspin Comm.................... 00:05:AD
Cisco .......................... 00:05:74 Mediaport....................... 00:05:AE
CDS-Elect ...................... 00:05:75 InnoScan Comp................... 00:05:AF
NSM Tech ....................... 00:05:76 Korea Comp Tech................. 00:05:B0
SM Info & Comm ............. 00:05:77 ASB Tech........................ 00:05:B1
Universal Ctrl Solns ........... 00:05:79 Medison......................... 00:05:B2
Hatteras Net ................... 00:05:7A Asahi-Engineering............... 00:05:B3
Chung Nam Elect ................ 00:05:7B Aceex........................... 00:05:B4
Broadcom Tech .................. 00:05:B5 ADOIR Dig Tech.................. 00:05:EF
INSYS Microelect ............... 00:05:B6 SATEC........................... 00:05:F0
Arbor Tech ..................... 00:05:B7 VRcom........................... 00:05:F1
Electronic Design Assoc ........ 00:05:B8 Power R......................... 00:05:F2
Airvana ........................ 00:05:B9 Weboyn.......................... 00:05:F3
Area Netwoeks .................. 00:05:BA SystemBase...................... 00:05:F4
Resorsys ....................... 00:05:BC OYO Geospace.................... 00:05:F5
ROAX ........................... 00:05:BD Young Chang..................... 00:05:F6
Kongsberg Seatex ............... 00:05:BE Analog Devices.................. 00:05:F7
JustEzy Tech ................... 00:05:BF Real Time Access................ 00:05:F8
Digital Net Alacarte ........... 00:05:C0 Diva Sys........................ 00:05:F9
A-Kyung Motion ................. 00:05:C1 IPOptical....................... 00:05:FA
Digital Archway ................ 00:05:C2 Sharegate....................... 00:05:FB
Pacific Inst ................... 00:05:C3 Schenck Pegasus................. 00:05:FC
Telect ......................... 00:05:C4 PacketLight Net................. 00:05:FD
Flaga .......................... 00:05:C5 Traficon........................ 00:05:FE
Triz Comm ...................... 00:05:C6 SNS Solns....................... 00:05:FF
I/F-COM ........................ 00:05:C7 Tokyo Elect Ind................. 00:06:00
VERYTECH ....................... 00:05:C8 Otanikeiki...................... 00:06:01
LG Innotek ..................... 00:05:C9 Cirkitech Elect................. 00:06:02
Hitron Tech .................... 00:05:CA Baker Hughes.................... 00:06:03
ROIS Tech ...................... 00:05:CB @Track Comm..................... 00:06:04
Sumtel Comm .................... 00:05:CC Inncom Intl..................... 00:06:05
Nippon Columbia ................ 00:05:CD RapidWan........................ 00:06:06
Prolink Microsys ............... 00:05:CE Omni-Directional Ctrl Tech...... 00:06:07
Thunder River Tech ............. 00:05:CF At-Sky.......................... 00:06:08
Solinet Sys .................... 00:05:D0 Crossport Sys................... 00:06:09
Metavector Tech ................ 00:05:D1 Blue2space.com.................. 00:06:0A
DAP Tech ....................... 00:05:D2 Paceline Sys.................... 00:06:0B
CAC ............................ 00:05:D3 Melco Ind....................... 00:06:0C
FutureSmart Net ................ 00:05:D4 Wave7 Optics.................... 00:06:0D
Speedcom Wireless .............. 00:05:D5 IGSYS Sys....................... 00:06:0E
Titan Wireless ................. 00:05:D6 Narad Net....................... 00:06:0F
Vista Imaging .................. 00:05:D7 Abeona Net...................... 00:06:10
Arescom ........................ 00:05:D8 Zeus Wireless................... 00:06:11
Techno Valley .................. 00:05:D9 Accusys......................... 00:06:12
Apex Automationstechnik ........ 00:05:DA Kawasaki Steel Corp............. 00:06:13
Nentec ......................... 00:05:DB Prism Holdings.................. 00:06:14
Cisco .......................... 00:05:DC Kimoto Elect.................... 00:06:15
Cisco .......................... 00:05:DD Tel Net......................... 00:06:16
Gi Fone Korea .................. 00:05:DE Redswitch....................... 00:06:17
Electronic Innov ............... 00:05:DF DigiPower Mfg................... 00:06:18
Empirix ........................ 00:05:E0 Connection Tech Sys............. 00:06:19
Trellis Photonics .............. 00:05:E1 Zetari.......................... 00:06:1A
Creativ Net Tech ............... 00:05:E2 Portable Sys.................... 00:06:1B
LightSand Comm ................. 00:05:E3 Hoshino Metal Ind............... 00:06:1C
Red Lion Ctrls ................. 00:05:E4 MIP Telecom..................... 00:06:1D
Renishaw ....................... 00:05:E5 Maxan Sys....................... 00:06:1E
Egenera ........................ 00:05:E6 Vision Components............... 00:06:1F
Netrake ........................ 00:05:E7 Serial Sys...................... 00:06:20
TurboWave ...................... 00:05:E8 Hinox........................... 00:06:21
Unicess Net .................... 00:05:E9 Chung Fu Chen Yeh Ent........... 00:06:22
Viewcast ....................... 00:05:EA MGE UPS Sys..................... 00:06:23
Blue Ridge Net ................. 00:05:EB Gentner Comm.................... 00:06:24
Mosaic Sys ..................... 00:05:EC Linksys Group................... 00:06:25
Technikum Joanneaum ............ 00:05:ED MWE............................. 00:06:26
BEWATOR Group .................. 00:05:EE Uniwide Tech.................... 00:06:27
Cisco .......................... 00:06:28 NIA Home Tech................... 00:06:61
IBM ............................ 00:06:29 MBM Tech........................ 00:06:62
Cisco .......................... 00:06:2A Human Tech...................... 00:06:63
Intraserver Tech ............... 00:06:2B Fostex.......................... 00:06:64
Network Robots ................. 00:06:2C Summy Gikem..................... 00:06:65
TouchStar Tech ................. 00:06:2D Roving Net...................... 00:06:66
Aristos Logic .................. 00:06:2E Tripp Lite...................... 00:06:67
Pivotech Sys ................... 00:06:2F Vicon Ind....................... 00:06:68
Adtranz ........................ 00:06:30 Datasound Labs.................. 00:06:69
Optical Solns .................. 00:06:31 InfiniCon Sys................... 00:06:6A
Mesco Eng ...................... 00:06:32 Sysmex.......................... 00:06:6B
Heimann Biometric Sys .......... 00:06:33 Robinson........................ 00:06:6C
GTE Airfone .................... 00:06:34 Compuprint...................... 00:06:6D
PacketAir Net .................. 00:06:35 Delta Elect..................... 00:06:6E
Jedai Bband Net ................ 00:06:36 Korea Data Sys.................. 00:06:6F
Toptrend-Meta Info ............. 00:06:37 Upponetti....................... 00:06:70
Sungjin C&C ................ 00:06:38 Softing......................... 00:06:71
Newtec ......................... 00:06:39 Netezza......................... 00:06:72
Dura Micro ..................... 00:06:3A Optelecom....................... 00:06:73
Lineo Canada ................... 00:06:3B Spectrum Ctrl................... 00:06:74
NMI Elect ...................... 00:06:3C Banderacom...................... 00:06:75
Microwave Data Sys ............. 00:06:3D Novra Tech...................... 00:06:76
Opthos ......................... 00:06:3E SICK............................ 00:06:77
Everex Comm .................... 00:06:3F Marantz Japan................... 00:06:78
White Rock Net ................. 00:06:40 Konami.......................... 00:06:79
ITCN ........................... 00:06:41 JMP Sys......................... 00:06:7A
Genetel Sys .................... 00:06:42 Toplink C&C................. 00:06:7B
SONO Comp ...................... 00:06:43 Cisco........................... 00:06:7C
NEIX ........................... 00:06:44 Takasago........................ 00:06:7D
Meisei Elect ................... 00:06:45 Cisco........................... 00:06:C1
ShenZhen XunBao Net Tech ....... 00:06:46 Racal-Datacom................... 00:07:01
Etrali ......................... 00:06:47 Multitech Sys................... 00:08:00
Seedsware ...................... 00:06:48 Compaq.......................... 00:08:C7
Quante ......................... 00:06:49 Apple........................... 00:0A:27
Honeywell ...................... 00:06:4A Cable Tele...................... 00:10:00
Alexon ......................... 00:06:4B MCK Comm........................ 00:10:01
Invicta Net .................... 00:06:4C Actia........................... 00:10:02
Sencore ........................ 00:06:4D Imatron......................... 00:10:03
Broad Net Tech ................. 00:06:4E Brantley Coile.................. 00:10:04
PRO-NETS Tech .................. 00:06:4F UEC Commercial.................. 00:10:05
Tiburon Net .................... 00:06:50 Racal Recorders................. 00:10:06
Aspen Net ...................... 00:06:51 Cisco........................... 00:10:07
Cisco .......................... 00:06:52 Vienna Sys...................... 00:10:08
Cisco .......................... 00:06:53 Horo Quartz..................... 00:10:09
Maxxio Tech .................... 00:06:54 Williams Comm Group............. 00:10:0A
Yipee .......................... 00:06:55 Cisco........................... 00:10:0B
Tactel ......................... 00:06:56 Ito ............................ 00:10:0C
Market Central ................. 00:06:57 Cisco........................... 00:10:0D
Helmut Fischer ................. 00:06:58 Micro Linear.................... 00:10:0E
EAL ............................ 00:06:59 Industrial Cpu Sys.............. 00:10:0F
Strix Sys ...................... 00:06:5A Initio.......................... 00:10:10
Dell Comp ...................... 00:06:5B Cisco........................... 00:10:11
Malachite Tech ................. 00:06:5C Processor Sys................... 00:10:12
Heidelberg Web Sys ............. 00:06:5D Industrial Comp Source.......... 00:10:13
Photuris ....................... 00:06:5E Cisco........................... 00:10:14
ECI Telecom - NGTS ............. 00:06:5F Oomon........................... 00:10:15
NADEX .......................... 00:06:60 T.Sqware........................ 00:10:16
Micos .......................... 00:10:17 Rion............................ 00:10:50
Broadcom ....................... 00:10:18 Cmicro.......................... 00:10:51
Sirona Dental Sys .............. 00:10:19 Mettler-Toledo.................. 00:10:52
Picturetel ..................... 00:10:1A Comp Tech....................... 00:10:53
Cornet Tech .................... 00:10:1B Cisco........................... 00:10:54
Ohm Tech Intl .................. 00:10:1C Fujitsu Microelec............... 00:10:55
Winbond Elec ................... 00:10:1D Sodick.......................... 00:10:56
Matsushita Elec ................ 00:10:1E Rebel.com....................... 00:10:57
Cisco .......................... 00:10:1F Arrowpoint Comm................. 00:10:58
Welch Allyn Data Col ........... 00:10:20 Diablo Res...................... 00:10:59
Encanto Net .................... 00:10:21 3Com............................ 00:10:5A
Satcom Media ................... 00:10:22 Net Insight..................... 00:10:5B
Flowwise Net ................... 00:10:23 Quantum Designs................. 00:10:5C
Nagoya Elec Works .............. 00:10:24 Drager Bus Unit................. 00:10:5D
Grayhill ....................... 00:10:25 Hekimian Lab.................... 00:10:5E
Accelerated Net ................ 00:10:26 In-snec......................... 00:10:5F
L-3 Comm East .................. 00:10:27 Billionton Sys.................. 00:10:60
Comp Technica .................. 00:10:28 Hostlink........................ 00:10:61
Cisco .......................... 00:10:29 NX Server....................... 00:10:62
Zf Micro ....................... 00:10:2A Starguide Dig Net............... 00:10:63
Umax Data Sys .................. 00:10:2B DEC............................. 00:10:64
Lasat Net ...................... 00:10:2C Radyne.......................... 00:10:65
Hitachi Soft Eng ............... 00:10:2D Adv Ctl Sys..................... 00:10:66
Network Sys & Tech ......... 00:10:2E Redback Net..................... 00:10:67
Cisco .......................... 00:10:2F Comos Telecom................... 00:10:68
WI-Lan ......................... 00:10:30 Helioss Comm.................... 00:10:69
Objective Comm ................. 00:10:31 Digital Microwave............... 00:10:6A
Alta Tech ...................... 00:10:32 Sonus Net....................... 00:10:6B
Accesslan Comm ................. 00:10:33 Infratec Plus................... 00:10:6C
GNP Comp ....................... 00:10:34 Integrity Comm.................. 00:10:6D
Elitegroup Comp ................ 00:10:35 Tadiran Com..................... 00:10:6E
Inter-Tel Integ Sys ............ 00:10:36 Trenton Tech.................... 00:10:6F
Cyq've Tech ............... 00:10:37 Caradon Trend................... 00:10:70
Micro Res Inst ................. 00:10:38 Advanet......................... 00:10:71
Vectron Sys .................... 00:10:39 GVN Tech........................ 00:10:72
Diamond Net Tech ............... 00:10:3A Technobox....................... 00:10:73
Hippi Net Forum ................ 00:10:3B Aten Intl....................... 00:10:74
IC Ensemble .................... 00:10:3C Maxtor.......................... 00:10:75
Phasecom ....................... 00:10:3D Eurem........................... 00:10:76
Netschools ..................... 00:10:3E Saf Drive Sys................... 00:10:77
Tollgrade Comm ................. 00:10:3F Nuera Comm...................... 00:10:78
Intermec ....................... 00:10:40 Cisco........................... 00:10:79
Bristol Babcock ................ 00:10:41 Ambicom......................... 00:10:7A
Alacritech ..................... 00:10:42 Cisco........................... 00:10:7B
A2 ............................. 00:10:43 P-com........................... 00:10:7C
Innolabs ....................... 00:10:44 Aurora Comm..................... 00:10:7D
Nortel ......................... 00:10:45 Bachmann Elec................... 00:10:7E
Alcorn Mcbride ................. 00:10:46 Crestron Elec................... 00:10:7F
Echo Eletric ................... 00:10:47 Metawave Comm................... 00:10:80
HTRC Auto ...................... 00:10:48 Dps............................. 00:10:81
Shoreline Teleworks ............ 00:10:49 Jna Telecomm.................... 00:10:82
Parvuc ......................... 00:10:4A Hewlett Packard................. 00:10:83
3Com ........................... 00:10:4B K-bot Comm...................... 00:10:84
Comp Access Tech ............... 00:10:4C Polaris Comm.................... 00:10:85
Surtec Ind ..................... 00:10:4D Atto Tech....................... 00:10:86
Ceologic ....................... 00:10:4E Xstreamis....................... 00:10:87
Storage Tech ................... 00:10:4F American Net.................... 00:10:88
Websonic ....................... 00:10:89 Willnet......................... 00:10:C2
Teralogic ...................... 00:10:8A CSI-Control Sys................. 00:10:C3
Laseranimation Sollinger ....... 00:10:8B Media Links..................... 00:10:C4
Fujitsu Telecomm ............... 00:10:8C Protocol Tech................... 00:10:C5
Johnson Ctls ................... 00:10:8D USI ............................ 00:10:C6
Hugh Symons Concept ............ 00:10:8E Data Trans Net.................. 00:10:C7
Raptor Sys ..................... 00:10:8F Comm Elec....................... 00:10:C8
Cimetrics ...................... 00:10:90 Mitsubishi Elec................. 00:10:C9
No Wires Needed ................ 00:10:91 Integral Access................. 00:10:CA
Netcore ........................ 00:10:92 Facit........................... 00:10:CB
Cms Comp ....................... 00:10:93 Clp Comp Log.................... 00:10:CC
Adtech ......................... 00:10:94 Interface Concept............... 00:10:CD
Thomson Consumer Elec .......... 00:10:95 Volamp.......................... 00:10:CE
Tracewell Sys .................. 00:10:96 Fiberlane Comm.................. 00:10:CF
Winnet Metro ................... 00:10:97 Witcom.......................... 00:10:D0
Starnet Tech ................... 00:10:98 Top Layer Net................... 00:10:D1
Innomedia ...................... 00:10:99 Nitto Tsushinki................. 00:10:D2
Netline ........................ 00:10:9A Grips Elec...................... 00:10:D3
Vixel .......................... 00:10:9B Storage Comp.................... 00:10:D4
M-System ....................... 00:10:9C Imasde Canarias................. 00:10:D5
Clarinet Sys ................... 00:10:9D Itt A/cd........................ 00:10:D6
Aware .......................... 00:10:9E Argosy Res...................... 00:10:D7
Pavo ........................... 00:10:9F Calista......................... 00:10:D8
Innovex Tech ................... 00:10:A0 IBM Japan....................... 00:10:D9
Kendin Semi .................... 00:10:A1 Motion Eng...................... 00:10:DA
TNS ............................ 00:10:A2 Netscreen Tech.................. 00:10:DB
Omnitronix ..................... 00:10:A3 Micro-star Intl................. 00:10:DC
Xircom ......................... 00:10:A4 Enable Semi..................... 00:10:DD
Oxford Inst .................... 00:10:A5 International Datacasting....... 00:10:DE
Cisco .......................... 00:10:A6 Rise Comp....................... 00:10:DF
Unex Tech ...................... 00:10:A7 Cobalt Microserver.............. 00:10:E0
Reliance Comp .................. 00:10:A8 SI Tech......................... 00:10:E1
Adhoc Tech ..................... 00:10:A9 Arraycomm....................... 00:10:E2
Media4 ......................... 00:10:AA Compaq.......................... 00:10:E3
Koito Ind ...................... 00:10:AB NSI ............................ 00:10:E4
Imci Tech ...................... 00:10:AC Solectron Texas................. 00:10:E5
Softronics Usb ................. 00:10:AD Applied Intel................... 00:10:E6
Shinko Elec Ind ................ 00:10:AE Breezecom....................... 00:10:E7
TAC Sys ........................ 00:10:AF Telocity........................ 00:10:E8
Meridian Tech .................. 00:10:B0 Raidtec......................... 00:10:E9
For-a .......................... 00:10:B1 Adept Tech...................... 00:10:EA
Coactive Aesthetics ............ 00:10:B2 Selsius Sys..................... 00:10:EB
Nokia Multimedia Term .......... 00:10:B3 Rpcg............................ 00:10:EC
Atmos Net ...................... 00:10:B4 Sundance Tech................... 00:10:ED
Accton Tech .................... 00:10:B5 CTI Prod........................ 00:10:EE
Entrata Comm ................... 00:10:B6 Db Net.......................... 00:10:EF
Coyote Tech .................... 00:10:B7 Rittal-werk Rudolf Loh.......... 00:10:F0
Ishigaki Comp Sys .............. 00:10:B8 I-O ............................ 00:10:F1
Maxtor ......................... 00:10:B9 Antec........................... 00:10:F2
Martinho-Davis Sys ............. 00:10:BA Nexcom Intl..................... 00:10:F3
Data & Info Tech ........... 00:10:BB Vertical Net.................... 00:10:F4
Nortel ......................... 00:10:BC Amherst Sys..................... 00:10:F5
Telecommunication .............. 00:10:BD Cisco........................... 00:10:F6
Telexis ........................ 00:10:BE Iriichi Tech.................... 00:10:F7
Inter Air Wireless ............. 00:10:BF Kenwood Tmi..................... 00:10:F8
Arma ........................... 00:10:C0 Unique Sys...................... 00:10:F9
OI Elec ........................ 00:10:C1 Zayante......................... 00:10:FA
Zida Tech ...................... 00:10:FB Synapse Tech.................... 00:20:33
Broadband Net .................. 00:10:FC Rotec Ind....................... 00:20:34
Cocom .......................... 00:10:FD IBM............................. 00:20:35
DEC ............................ 00:10:FE Bmc Soft........................ 00:20:36
Cisco .......................... 00:10:FF Seagate Tech.................... 00:20:37
Perq Sys ....................... 00:1C:7C Vme Micro Intl.................. 00:20:38
Lexmark Intl ................... 00:20:00 Scinets......................... 00:20:39
DSP Soln ....................... 00:20:01 Digital Bio..................... 00:20:3A
Seritech Ent ................... 00:20:02 Wisdm........................... 00:20:3B
Pixel Power .................... 00:20:03 Eurotime........................ 00:20:3C
Yamatake-Honeywell ............. 00:20:04 Novar Elec...................... 00:20:3D
Simple Tech .................... 00:20:05 Logican Tech.................... 00:20:3E
Garrett Comm ................... 00:20:06 Juki............................ 00:20:3F
Sfa ............................ 00:20:07 Motorola Bband Comm............. 00:20:40
Cable & Comp Tech .......... 00:20:08 Data Net........................ 00:20:41
Packard Bell Elec .............. 00:20:09 Datametrics..................... 00:20:42
Source-Comm .................... 00:20:0A Neuron.......................... 00:20:43
Octagon Sys .................... 00:20:0B Genitech........................ 00:20:44
Adastra Sys .................... 00:20:0C Ion Net......................... 00:20:45
Carl Zeiss ..................... 00:20:0D Ciprico......................... 00:20:46
Satellite Tech Mgmt ............ 00:20:0E Steinbrecher.................... 00:20:47
Tanbac ......................... 00:20:0F Marconi Comm.................... 00:20:48
Jeol Sys Tech .................. 00:20:10 Comtron......................... 00:20:49
Canopus ........................ 00:20:11 Pronet.......................... 00:20:4A
Camtronics Med Sys ............. 00:20:12 Autocomputer.................... 00:20:4B
Diversified Tech ............... 00:20:13 Mitron Comp..................... 00:20:4C
Global View .................... 00:20:14 Inovis.......................... 00:20:4D
Actis Comp ..................... 00:20:15 Network Sec Sys................. 00:20:4E
Showa Elec Wire & Cable Co . 00:20:16 Deutsche Aerospace.............. 00:20:4F
Orbotech ....................... 00:20:17 Korea Comp...................... 00:20:50
Cis Tech ....................... 00:20:18 Phoenix Data Comm............... 00:20:51
Ohler .......................... 00:20:19 Ragula Sys...................... 00:20:52
N-Base Switch Comm ............. 00:20:1A Huntsville Micro................ 00:20:53
Northern Telecom/Net ........... 00:20:1B Eastern Res..................... 00:20:54
Excel .......................... 00:20:1C Altech.......................... 00:20:55
Katana Prod .................... 00:20:1D Neoproducts..................... 00:20:56
Netquest ....................... 00:20:1E Titze Datentechnik.............. 00:20:57
Best Power Tech ................ 00:20:1F Allied Signal................... 00:20:58
Megatron Comp Ind .............. 00:20:20 Miro Comp Prod.................. 00:20:59
Algorithms Soft ................ 00:20:21 Comp Identics................... 00:20:5A
Teknique ....................... 00:20:22 Skyline Tech.................... 00:20:5B
TC Tech ........................ 00:20:23 Internet Sys/Florida............ 00:20:5C
Pacific Comm Sciences .......... 00:20:24 Nanomatic....................... 00:20:5D
Control Tech ................... 00:20:25 Castle Rock..................... 00:20:5E
Amkly Sys ...................... 00:20:26 Gammadata Comp.................. 00:20:5F
Ming Fortune In ................ 00:20:27 Alcatel Italia.................. 00:20:60
West Egg Sys ................... 00:20:28 Dynatech Comm................... 00:20:61
Teleprocessing Prod ............ 00:20:29 Scorpion Logic.................. 00:20:62
NV Dzine ....................... 00:20:2A Wipro Infotech.................. 00:20:63
Adv Telecomm ................... 00:20:2B Protec Micro.................... 00:20:64
Welltronix ..................... 00:20:2C Supernet Net.................... 00:20:65
Taiyo .......................... 00:20:2D General Magic................... 00:20:66
Daystar Dig .................... 00:20:2E Isdyne.......................... 00:20:68
Zeta Comm ...................... 00:20:2F Isdn Sys........................ 00:20:69
Analog & Dig Sys ........... 00:20:30 Osaka Comp...................... 00:20:6A
Ertec .......................... 00:20:31 Minolta......................... 00:20:6B
Alcatel Taisel ................. 00:20:32 Evergreen Tech.................. 00:20:6C
Data Race ...................... 00:20:6D Proxim.......................... 00:20:A6
Xact ........................... 00:20:6E Pairgain Tech................... 00:20:A7
Flowpoint ...................... 00:20:6F SAST Tech....................... 00:20:A8
Hynet .......................... 00:20:70 White Horse Ind................. 00:20:A9
Ibr ............................ 00:20:71 Digimedia Vision................ 00:20:AA
Worklink Innov ................. 00:20:72 Micro Ind....................... 00:20:AB
Fusion Sys ..................... 00:20:73 Interflex Datensys.............. 00:20:AC
Sungwoon Sys ................... 00:20:74 Linq Sys........................ 00:20:AD
Motorola Comm Israel ........... 00:20:75 Ornet Data Comm Tech............ 00:20:AE
Reudo .......................... 00:20:76 3Com............................ 00:20:AF
Kardios Sys .................... 00:20:77 Gateway Dev..................... 00:20:B0
Runtop ......................... 00:20:78 Comtech Res..................... 00:20:B1
Mikron ......................... 00:20:79 GKD Gesellschaft................ 00:20:B2
Wise Comm ...................... 00:20:7A Scltec Comm Sys................. 00:20:B3
Level One Comm ................. 00:20:7B Terma Elektronik................ 00:20:B4
Autec .......................... 00:20:7C Yaskawa Elec.................... 00:20:B5
Adv Comp App ................... 00:20:7D Agile Net....................... 00:20:B6
Finecom ........................ 00:20:7E Namaqua Compware................ 00:20:B7
Kyoei Sangyo ................... 00:20:7F Prime Option.................... 00:20:B8
Synergy (uk) ................... 00:20:80 Metricom........................ 00:20:B9
Titan Elec ..................... 00:20:81 Center For High Performance..... 00:20:BA
Oneac .......................... 00:20:82 ZAX ............................ 00:20:BB
Presticom ...................... 00:20:83 JTEC............................ 00:20:BC
Oce Printing Sys ............... 00:20:84 Niobrara R&D................ 00:20:BD
Exide Elec ..................... 00:20:85 Lan Access...................... 00:20:BE
Microtech Elec ................. 00:20:86 Aehr Test Sys................... 00:20:BF
Memotec Comm ................... 00:20:87 Pulse Elec...................... 00:20:C0
Global Village ................. 00:20:88 Taiko Elec Works................ 00:20:C1
T3plus Net ..................... 00:20:89 Texas Memory Sys................ 00:20:C2
Sonix Comm ..................... 00:20:8A Counter Soln.................... 00:20:C3
Lapis Tech ..................... 00:20:8B INET............................ 00:20:C4
Galaxy Net ..................... 00:20:8C Eagle Tech...................... 00:20:C5
Cmd Tech ....................... 00:20:8D Nectec.......................... 00:20:C6
Chevin Soft Eng ................ 00:20:8E Akai Prof....................... 00:20:C7
Eci Telecom .................... 00:20:8F Larscom......................... 00:20:C8
Adv Compression ................ 00:20:90 Victron......................... 00:20:C9
J125 NSA ....................... 00:20:91 Digital Ocean................... 00:20:CA
Chess Eng ...................... 00:20:92 Pretec Elec..................... 00:20:CB
Landings Tech .................. 00:20:93 Digital Services................ 00:20:CC
Cubix .......................... 00:20:94 Hybrid Net...................... 00:20:CD
Riva Elec ...................... 00:20:95 Logical Des Group............... 00:20:CE
Siebe Env Ctls ................. 00:20:96 Test & Meas Sys............. 00:20:CF
Applied Sig Tech ............... 00:20:97 Versalynx....................... 00:20:D0
Hectronic ...................... 00:20:98 Microcomputer Sys............... 00:20:D1
Bon Elec ....................... 00:20:99 Rad Data Comm................... 00:20:D2
3DO ............................ 00:20:9A OST ............................ 00:20:D3
Ersat Elec ..................... 00:20:9B Cabletron - Zeittnet............ 00:20:D4
Primary Access ................. 00:20:9C Vipa............................ 00:20:D5
Lippert Auto ................... 00:20:9D Breezecom....................... 00:20:D6
Brown's OS ................ 00:20:9E Japan Minicomp Sys.............. 00:20:D7
Mercury Comp Sys ............... 00:20:9F Netwave Tech.................... 00:20:D8
OA Lab ......................... 00:20:A0 Panasonic Tech.................. 00:20:D9
Dovatron ....................... 00:20:A1 Xylan........................... 00:20:DA
Galcom Net ..................... 00:20:A2 XNet Tech....................... 00:20:DB
Divicom ........................ 00:20:A3 Densitron Taiwan................ 00:20:DC
Multipoint Net ................. 00:20:A4 Awa ............................ 00:20:DD
API Eng ........................ 00:20:A5 Japan Digital Lab............... 00:20:DE
Kyosan Elec Mfg ................ 00:20:DF Jetway Info..................... 00:30:18
Premax Elec .................... 00:20:E0 Cisco........................... 00:30:19
Alamar Elec .................... 00:20:E1 Smartbridges.................... 00:30:1A
Info Resource .................. 00:20:E2 Shuttle......................... 00:30:1B
Mcd Kencom ..................... 00:20:E3 Altvater Airdata Sys............ 00:30:1C
Hsing Tech Ent ................. 00:20:E4 Skystream....................... 00:30:1D
Apex Data ...................... 00:20:E5 3Com............................ 00:30:1E
Lidkoping Mach Tools ........... 00:20:E6 Optical Net..................... 00:30:1F
B&W Nuclear Serv ........... 00:20:E7 Tsi............................. 00:30:20
Datatrek ....................... 00:20:E8 Hsing Tech Ent.................. 00:30:21
Dantel ......................... 00:20:E9 Fong Kai Ind.................... 00:30:22
Efficient Net .................. 00:20:EA Cogent Comp Sys................. 00:30:23
Cincinnati Microwave ........... 00:20:EB Cisco........................... 00:30:24
Techware Sys ................... 00:20:EC Checkout Comp Sys............... 00:30:25
Giga-byte Tech ................. 00:20:ED Heitel.......................... 00:30:26
GTech .......................... 00:20:EE Kerbango........................ 00:30:27
USC ............................ 00:20:EF Fase Saldatura srl.............. 00:30:28
Universal Microelec ............ 00:20:F0 Opicom.......................... 00:30:29
Altos India .................... 00:20:F1 Southern Info................... 00:30:2A
Sun Micro ...................... 00:20:F2 Inalp Net....................... 00:30:2B
Raynet ......................... 00:20:F3 Sylantro Sys.................... 00:30:2C
Spectrix ....................... 00:20:F4 Quantum Bridge Comm............. 00:30:2D
Pandatel ....................... 00:20:F5 Hoft & Wessel............... 00:30:2E
Net Tek & Karlnet .......... 00:20:F6 Smiths Ind...................... 00:30:2F
Cyberdata ...................... 00:20:F7 Harmonix........................ 00:30:30
Carrera Comp ................... 00:20:F8 Lightwave Comm.................. 00:30:31
Paralink Net ................... 00:20:F9 Magicram........................ 00:30:32
GDE Sys ........................ 00:20:FA Orient Telecom.................. 00:30:33
Octel Comm ..................... 00:20:FB RMP Elek........................ 00:30:36
Matrox ......................... 00:20:FC Packard Bell Nec Services....... 00:30:37
Itv Tech ....................... 00:20:FD XCP............................. 00:30:38
Topware/Grand Comp ............. 00:20:FE Softbook Press.................. 00:30:39
Symmetrical Tech ............... 00:20:FF Maatel.......................... 00:30:3A
Allwell Tech ................... 00:30:00 Powercom Tech................... 00:30:3B
SMP ............................ 00:30:01 Onnto........................... 00:30:3C
Expand Net ..................... 00:30:02 Iva............................. 00:30:3D
Phasys ......................... 00:30:03 Radcom.......................... 00:30:3E
Leadtek Res .................... 00:30:04 Turbocomm Tech.................. 00:30:3F
Fujitsu Siemens Comp ........... 00:30:05 Cisco........................... 00:30:40
Superpower Comp ................ 00:30:06 Saejin T&M.................. 00:30:41
Opti ........................... 00:30:07 Detewe-Deutsche Tele............ 00:30:42
Avio Dig ....................... 00:30:08 Idream Tech..................... 00:30:43
Tachion Net .................... 00:30:09 Portsmith....................... 00:30:44
Aztech Sys ..................... 00:30:0A Village Net..................... 00:30:45
mphase Tech .................... 00:30:0B Controlled Elec Mgmt............ 00:30:46
Congruency ..................... 00:30:0C Nissei Elec..................... 00:30:47
MMC Tech ....................... 00:30:0D Supermicro Comp................. 00:30:48
Klotz Digital .................. 00:30:0E Bryant Tech..................... 00:30:49
Imt-Info Mgmt .................. 00:30:0F Fraunhofer Inst Ims............. 00:30:4A
Visionetics Intl ............... 00:30:10 Orbacom Sys..................... 00:30:4B
Hms Fieldbus Sys ............... 00:30:11 Appian Comm..................... 00:30:4C
Digital Eng .................... 00:30:12 ESI............................. 00:30:4D
NEC ............................ 00:30:13 Bustec Prod..................... 00:30:4E
Divio .......................... 00:30:14 Planet Tech..................... 00:30:4F
CP Clare ....................... 00:30:15 Versa Tech...................... 00:30:50
Ishida ......................... 00:30:16 Orbit Avionic & Comm........ 00:30:51
Terastack ...................... 00:30:17 Elastic Net..................... 00:30:52
Basler ......................... 00:30:53 Adv Digital Info................ 00:30:8C
Castlenet Tech ................. 00:30:54 Pinnacle Sys.................... 00:30:8D
Hitachi Semi America ........... 00:30:55 Cross Match Tech................ 00:30:8E
Beck Ipc ....................... 00:30:56 Micrilor........................ 00:30:8F
E-Tel .......................... 00:30:57 Cyra Tech....................... 00:30:90
API Motion ..................... 00:30:58 Taiwan First Line Elec.......... 00:30:91
Digital-Logic .................. 00:30:59 Modunorm........................ 00:30:92
Telgen ......................... 00:30:5A Sonnet Tech..................... 00:30:93
Module DepT .................... 00:30:5B Cisco........................... 00:30:94
Smar Lab ....................... 00:30:5C Procomp Info.................... 00:30:95
Digitra Sys .................... 00:30:5D Cisco........................... 00:30:96
Abelko Innov ................... 00:30:5E Exomatic........................ 00:30:97
Imacon Aps ..................... 00:30:5F Global Converging Tech.......... 00:30:98
Starmatix ...................... 00:30:60 Boenig Und Kallenbach Ohg....... 00:30:99
Mobytel ........................ 00:30:61 Astro Terra..................... 00:30:9A
Path 1 Net Tech ................ 00:30:62 Smartware....................... 00:30:9B
Santera Sys .................... 00:30:63 Timing App...................... 00:30:9C
Adlink Tech .................... 00:30:64 Nimble Micro.................... 00:30:9D
Apple .......................... 00:30:65 Workbit......................... 00:30:9E
Digital Wireless ............... 00:30:66 Amber Net....................... 00:30:9F
Biostar Micro Intl ............. 00:30:67 Tyco Submarine Sys.............. 00:30:A0
Cybernetics Tech ............... 00:30:68 Opti Tech....................... 00:30:A1
Impacct Tech ................... 00:30:69 Lightner Eng.................... 00:30:A2
Penta Media .................... 00:30:6A Cisco........................... 00:30:A3
Cmos Sys ....................... 00:30:6B Woodwind Comm Sys............... 00:30:A4
Hitex Holding .................. 00:30:6C Active Power.................... 00:30:A5
Lucent ......................... 00:30:6D Vianet Tech..................... 00:30:A6
Hewlett Packard ................ 00:30:6E Schweitzer Eng.................. 00:30:A7
Seyeon Tech .................... 00:30:6F Ol'e Comm.................. 00:30:A8
1Net ........................... 00:30:70 Netiverse....................... 00:30:A9
Cisco .......................... 00:30:71 Axus Micro...................... 00:30:AA
Intellibyte .................... 00:30:72 Delta Net....................... 00:30:AB
International Micro ............ 00:30:73 Systeme Lauer &............. 00:30:AC
Equiinet ....................... 00:30:74 Shanghai Comm................... 00:30:AD
Adtech ......................... 00:30:75 Times N Sys..................... 00:30:AE
Akamba ......................... 00:30:76 Honeywell Reqelsysteme.......... 00:30:AF
Onprem Net ..................... 00:30:77 Convergenet Tech................ 00:30:B0
Cisco .......................... 00:30:78 GOC Gesellschaft................ 00:30:B1
Cqos ........................... 00:30:79 Wescam - Healdsburg............. 00:30:B2
Adv Tech & Sys ............. 00:30:7A San Valley Sys.................. 00:30:B3
Cisco .......................... 00:30:7B Intersil........................ 00:30:B4
Adid Sa ........................ 00:30:7C Tadiran Microwave Net........... 00:30:B5
Gre America .................... 00:30:7D Cisco........................... 00:30:B6
Redflex Comm Sys ............... 00:30:7E Teletrol Sys.................... 00:30:B7
Irlan .......................... 00:30:7F Riverdelta Net.................. 00:30:B8
Cisco .......................... 00:30:80 Ectel........................... 00:30:B9
Altos C&C .................. 00:30:81 AC&T Sys.................... 00:30:BA
Taihan Elec Wire ............... 00:30:82 Cacheflow....................... 00:30:BB
Ivron Sys ...................... 00:30:83 Optronic........................ 00:30:BC
Allied Telesyn Intl ............ 00:30:84 Belkin Components............... 00:30:BD
Cisco .......................... 00:30:85 City-net Tech................... 00:30:BE
Transistor Dev ................. 00:30:86 Multidata....................... 00:30:BF
Vega Grieshaber ................ 00:30:87 Lara Tech....................... 00:30:C0
Siara Sys ...................... 00:30:88 Hewlett Packard................. 00:30:C1
Spectrapoint Wireless .......... 00:30:89 Comone.......................... 00:30:C2
Nicotra Sistemi ................ 00:30:8A Flueckiger Elek................. 00:30:C3
Brix Net ....................... 00:30:8B Niigata Canotec................. 00:30:C4
Cadence Des Sys ................ 00:30:C5 Datafab Sys..................... 00:30:FF
Control Soln ................... 00:30:C6 PCI Componentes Da Amzonia...... 00:40:00
Macromate ...................... 00:30:C7 Zyxel Comm...................... 00:40:01
Gad Line ....................... 00:30:C8 Perle Sys....................... 00:40:02
Luxn N ......................... 00:30:C9 Westinghouse Proc Ctl........... 00:40:03
Discovery Com .................. 00:30:CA ICM............................. 00:40:04
Omni Flow Comp ................. 00:30:CB Ani Comm........................ 00:40:05
Tenor Net ...................... 00:30:CC Sampo Tech...................... 00:40:06
Conexant Sys ................... 00:30:CD Telmat Info..................... 00:40:07
Zaffire ........................ 00:30:CE A Plus Info..................... 00:40:08
Two Tech ....................... 00:30:CF Tachibana Tectron............... 00:40:09
Inova .......................... 00:30:D1 Pivotal Tech.................... 00:40:0A
Win Tech ....................... 00:30:D2 Cisco........................... 00:40:0B
Agilent Tech ................... 00:30:D3 General Micro Sys............... 00:40:0C
Comtier ........................ 00:30:D4 Lannet Data Comm................ 00:40:0D
Dresearch ...................... 00:30:D5 Memotec Comm.................... 00:40:0E
MSC Vertriebs .................. 00:30:D6 Datacom Tech.................... 00:40:0F
Innovative Sys ................. 00:30:D7 Sonic Sys....................... 00:40:10
Sitek .......................... 00:30:D8 Andover Ctls.................... 00:40:11
Datacore Soft .................. 00:30:D9 Windata......................... 00:40:12
Comtrend ....................... 00:30:DA NTT Data Comm Sys............... 00:40:13
Mindready Solns ................ 00:30:DB Comsoft......................... 00:40:14
Rightech ....................... 00:30:DC Ascom Infrasys.................. 00:40:15
Indigita ....................... 00:30:DD Hadax Elec...................... 00:40:16
Wago Kontakttechnik ............ 00:30:DE XCD............................. 00:40:17
KB/Tel Telecom ................. 00:30:DF Adobe Sys....................... 00:40:18
Oxford Semi .................... 00:30:E0 Aeon Sys........................ 00:40:19
Acrotron Sys ................... 00:30:E1 Fuji Elec....................... 00:40:1A
Garnet Sys ..................... 00:30:E2 Printer Sys..................... 00:40:1B
Sedona Net ..................... 00:30:E3 Ast Res......................... 00:40:1C
Chiyoda Sys Riken .............. 00:30:E4 Invisible Soft.................. 00:40:1D
Amper Datos .................... 00:30:E5 ICC............................. 00:40:1E
Siemens Med Sys ................ 00:30:E6 Colorgraph...................... 00:40:1F
Cnf Mobile Soln ................ 00:30:E7 Pinacl Comm..................... 00:40:20
Ensim .......................... 00:30:E8 Raster Graphics................. 00:40:21
GMA Comm Mfg ................... 00:30:E9 Klever Comp..................... 00:40:22
TeraForce Tech ................. 00:30:EA Logic........................... 00:40:23
Turbonet Comm .................. 00:30:EB Compac.......................... 00:40:24
Borgardt ....................... 00:30:EC Molecular Dyn................... 00:40:25
Expert Magnetics ............... 00:30:ED Melco........................... 00:40:26
DSG Tech ....................... 00:30:EE SMC............................. 00:40:27
Neon Tech ...................... 00:30:EF Netcomm......................... 00:40:28
Uniform Ind .................... 00:30:F0 Compex.......................... 00:40:29
Accton Tech .................... 00:30:F1 Canoga-Perkins.................. 00:40:2A
Cisco .......................... 00:30:F2 Trigem Comp..................... 00:40:2B
At Work Comp ................... 00:30:F3 Isis Dist Sys................... 00:40:2C
Stardot Tech ................... 00:30:F4 Harris Adacom................... 00:40:2D
Wild Lab ....................... 00:30:F5 Precision Soft.................. 00:40:2E
Securelogix .................... 00:30:F6 Xlnt Designs.................... 00:40:2F
Ramix .......................... 00:30:F7 GK Comp......................... 00:40:30
Dynapro Sys .................... 00:30:F8 Kokusai Elec.................... 00:40:31
Sollae Sys ..................... 00:30:F9 Digital Comm.................... 00:40:32
Telica ......................... 00:30:FA Addtron Tech.................... 00:40:33
Azs Tech ....................... 00:30:FB Bustek.......................... 00:40:34
Terawave Comm .................. 00:30:FC Opcom........................... 00:40:35
Integrated Sys Design .......... 00:30:FD Tribe Comp Works................ 00:40:36
DSA ............................ 00:30:FE Sea-Ilan........................ 00:40:37
Talent Elec .................... 00:40:38 Atm Comp........................ 00:40:71
Optec Daiichi Denko ............ 00:40:39 Applied Innov................... 00:40:72
Impact Tech .................... 00:40:3A Bass Assoc...................... 00:40:73
Synerjet Intl .................. 00:40:3B Cable & Wireless............ 00:40:74
Forks .......................... 00:40:3C M-Trade......................... 00:40:75
Teradata ....................... 00:40:3D Sun Conversion Tech............. 00:40:76
Raster Ops ..................... 00:40:3E Maxton Tech..................... 00:40:77
Ssangyong Comp Sys ............. 00:40:3F Wearnes Auto.................... 00:40:78
Ring Access .................... 00:40:40 Juko Manuf Co................... 00:40:79
Fujikura ....................... 00:40:41 Societe D'exp Du Cnit...... 00:40:7A
NAT ............................ 00:40:42 Scientific Atlanta.............. 00:40:7B
Nokia Telecomm ................. 00:40:43 Qume............................ 00:40:7C
Qnix Comp ...................... 00:40:44 Extension Tech.................. 00:40:7D
Twinhead ....................... 00:40:45 Evergreen Sys................... 00:40:7E
UDC Res ........................ 00:40:46 Agema Infrared Sys.............. 00:40:7F
Wind River Sys ................. 00:40:47 Athenix......................... 00:40:80
SMD Info ....................... 00:40:48 Mannesmann Scangraphic.......... 00:40:81
Tegimenta ...................... 00:40:49 Laboratory Equip................ 00:40:82
West Australian Dept ........... 00:40:4A TDA Ind De Prod................. 00:40:83
Maple Comp Sys ................. 00:40:4B Honeywell....................... 00:40:84
Hypertec ....................... 00:40:4C Saab Inst....................... 00:40:85
Telecomm Tech .................. 00:40:4D Michels & Kleberhoff........ 00:40:86
Fluent ......................... 00:40:4E Ubitrex......................... 00:40:87
Space & Naval Warfare Sys .. 00:40:4F Mobius Tech..................... 00:40:88
Ironics ........................ 00:40:50 Meidensha....................... 00:40:89
Gracilis ....................... 00:40:51 Tps Teleprocessing Sys.......... 00:40:8A
Star Tech ...................... 00:40:52 Raylan.......................... 00:40:8B
Ampro Comps .................... 00:40:53 Axis Comm....................... 00:40:8C
Connection Mach Serv ........... 00:40:54 Goodyear Tire & Rubber...... 00:40:8D
Metronix ....................... 00:40:55 Digilog......................... 00:40:8E
MCM Japan ...................... 00:40:56 Wm-data Minfo................... 00:40:8F
Lockheed-Sanders ............... 00:40:57 Ansel Comm...................... 00:40:90
Kronos ......................... 00:40:58 Procomp Ind Eletr............... 00:40:91
Yoshida Kogyo .................. 00:40:59 Asp Comp Prod................... 00:40:92
Goldstar Info & Comm ....... 00:40:5A Paxdata Net..................... 00:40:93
Funasset ....................... 00:40:5B Shographics..................... 00:40:94
Future Sys ..................... 00:40:5C RPT Intergroups Intl............ 00:40:95
Star-Tek ....................... 00:40:5D Aironet......................... 00:40:96
North Hills Israel ............. 00:40:5E Datex........................... 00:40:97
AFE Comp ....................... 00:40:5F Dressler........................ 00:40:98
Comendec ....................... 00:40:60 Newgen Sys...................... 00:40:99
Datatech Ent ................... 00:40:61 Network Express................. 00:40:9A
E-Systems ...................... 00:40:62 Hal Comp Sys.................... 00:40:9B
Via Tech ....................... 00:40:63 Transware....................... 00:40:9C
Kla Inst ....................... 00:40:64 Digiboard....................... 00:40:9D
GTE Spacenet ................... 00:40:65 Concurrent Tech ................ 00:40:9E
Hitachi Cable .................. 00:40:66 Lancast/Casat Tech.............. 00:40:9F
Omnibyte ....................... 00:40:67 Goldstar........................ 00:40:A0
Extended Sys ................... 00:40:68 Ergo Comp....................... 00:40:A1
Lemcom Sys ..................... 00:40:69 Kingstar Tech................... 00:40:A2
Kentek Info Sys ................ 00:40:6A Microunity Sys Eng.............. 00:40:A3
Sysgen ......................... 00:40:6B Rose Elec....................... 00:40:A4
Copernique ..................... 00:40:6C Clinicomp Intl.................. 00:40:A5
Lanco .......................... 00:40:6D Cray............................ 00:40:A6
Corollary ...................... 00:40:6E Itautec Philco.................. 00:40:A7
Sync Res ....................... 00:40:6F Imf Intl........................ 00:40:A8
Interware ...................... 00:40:70 Datacom......................... 00:40:A9
Valmet Auto .................... 00:40:AA Quin Sys........................ 00:40:E3
Roland Dg ...................... 00:40:AB E-M Tech........................ 00:40:E4
Super Workstation .............. 00:40:AC Sybus........................... 00:40:E5
SMA Regelsysteme ............... 00:40:AD CAEN............................ 00:40:E6
Delta Ctls ..................... 00:40:AE Arnos Inst & Comp........... 00:40:E7
Digital Prod ................... 00:40:AF Charles River Data Sys.......... 00:40:E8
Bytex Eng ...................... 00:40:B0 Accord Sys...................... 00:40:E9
Codonics ....................... 00:40:B1 Plain Tree Sys.................. 00:40:EA
Systemforschung ................ 00:40:B2 Martin Marietta................. 00:40:EB
Par Micro ...................... 00:40:B3 Mikasa Sys Eng.................. 00:40:EC
Nextcom ........................ 00:40:B4 Network Ctls Intl............... 00:40:ED
Video Tech Comp ................ 00:40:B5 Optimem......................... 00:40:EE
Computerm ..................... 00:40:B6 Hypercom........................ 00:40:EF
Stealth Comp Sys ............... 00:40:B7 Micro Sys....................... 00:40:F0
Idea Assoc ..................... 00:40:B8 Chuo Elec....................... 00:40:F1
Macq Elec ...................... 00:40:B9 Janich & Klass Comp......... 00:40:F2
Alliant Comp Sys ............... 00:40:BA Netcor.......................... 00:40:F3
Goldstar Cable ................. 00:40:BB Cameo Comm...................... 00:40:F4
Algorithmics ................... 00:40:BC Oem Engines..................... 00:40:F5
Starlight Net .................. 00:40:BD Katron Comp..................... 00:40:F6
Boeing Defense & Space ..... 00:40:BE Polaroid Med Imag Sys........... 00:40:F7
Channel Sys Intl ............... 00:40:BF Systemhaus Discom............... 00:40:F8
Vista Ctls ..................... 00:40:C0 Combinet........................ 00:40:F9
Bizerba-werke Wilheim Kraut .... 00:40:C1 Microboards..................... 00:40:FA
Applied Comp Dev ............... 00:40:C2 Cascade Comm.................... 00:40:FB
Fischer & Porter ........... 00:40:C3 Ibr Comp Technik................ 00:40:FC
Kinkei Sys ..................... 00:40:C4 LXE............................. 00:40:FD
Micom Comm ..................... 00:40:C5 Symplex Comm.................... 00:40:FE
Fibernet Res ................... 00:40:C6 Telebit......................... 00:40:FF
Ruby Tech ...................... 00:40:C7 Nexo Comm....................... 00:50:00
Milan Tech ..................... 00:40:C8 Yamashita Sys................... 00:50:01
NCube .......................... 00:40:C9 Omnisec......................... 00:50:02
First Intl Comp ................ 00:40:CA Gretag Macbeth.................. 00:50:03
Lanwan Tech .................... 00:40:CB 3Com............................ 00:50:04
Silcom Mfg Tech ................ 00:40:CC TAC............................. 00:50:06
Tera Micro ..................... 00:40:CD Siemens Telecomm................ 00:50:07
Net-Source ..................... 00:40:CE Tiva Micro...................... 00:50:08
Strawberry Tree ................ 00:40:CF Philips Broadband Net........... 00:50:09
Mitac Intl ..................... 00:40:D0 Iris Tech....................... 00:50:0A
Fukuda Denshi .................. 00:40:D1 Cisco........................... 00:50:0B
Pagine ......................... 00:40:D2 Etek Labs....................... 00:50:0C
Kimpsion Intl .................. 00:40:D3 Satori Elec..................... 00:50:0D
Gage Talker .................... 00:40:D4 Chromatis Net................... 00:50:0E
Sartorius ...................... 00:40:D5 Cisco........................... 00:50:0F
Locamation ..................... 00:40:D6 Novanet Learning................ 00:50:10
Studio Gen ..................... 00:40:D7 Cbl............................. 00:50:12
Ocean Office Auto .............. 00:40:D8 Chaparral Tech.................. 00:50:13
American Megatrends ............ 00:40:D9 Cisco........................... 00:50:14
Telspec ........................ 00:40:DA Bright Star Eng................. 00:50:15
Adv Tech Soln .................. 00:40:DB SST/Woodhead Ind................ 00:50:16
Tritec Elec .................... 00:40:DC RSR............................. 00:50:17
Hong Tech ...................... 00:40:DD Adv Multi Internet.............. 00:50:18
Elettronica San Giorgio ........ 00:40:DE Spring Tide Net................. 00:50:19
Digalog Sys .................... 00:40:DF Uisiqn.......................... 00:50:1A
Atomwide ....................... 00:40:E0 Abl Canada...................... 00:50:1B
Marner Intl .................... 00:40:E1 Jatom Sys....................... 00:50:1C
Mesa Ridge Tech ................ 00:40:E2 Miranda Tech.................... 00:50:1E
MRG Sys ........................ 00:50:1F Digitek Micrologic.............. 00:50:5E
Mediastar ...................... 00:50:20 Brand Innovators................ 00:50:5F
EIS Intl ....................... 00:50:21 Tandberg Telecom................ 00:50:60
Zonet Tech ..................... 00:50:22 Kouwell Elec.................... 00:50:62
PG Des Elec .................... 00:50:23 Oy Comsel Sys................... 00:50:63
Navic Sys ...................... 00:50:24 Cae Elec........................ 00:50:64
Cosystems ...................... 00:50:26 Densei-Lambad................... 00:50:65
Genicom ........................ 00:50:27 Atecom Adv...................... 00:50:66
Aval Comm ...................... 00:50:28 Aerocomm........................ 00:50:67
1394 Print WG .................. 00:50:29 Elec Ind........................ 00:50:68
Cisco .......................... 00:50:2A Pixstream....................... 00:50:69
Genrad ......................... 00:50:2B Edeva........................... 00:50:6A
Soyo Comp ...................... 00:50:2C Spx-Ateg........................ 00:50:6B
Accel .......................... 00:50:2D G&L Beijer Elec............. 00:50:6C
Cambex ......................... 00:50:2E Videojet Sys.................... 00:50:6D
Tollbridge Tech ................ 00:50:2F Corder Eng...................... 00:50:6E
Future Plus Sys ................ 00:50:30 G-Connect....................... 00:50:6F
Aeroflex Lab ................... 00:50:31 Chaintech Comp.................. 00:50:70
Picazo Comm .................... 00:50:32 Aiwa............................ 00:50:71
Mayan Net ...................... 00:50:33 Corvis.......................... 00:50:72
Netcam ......................... 00:50:36 Cisco........................... 00:50:73
Koga Elec ...................... 00:50:37 Adv Hi-tech..................... 00:50:74
Dain Telecom ................... 00:50:38 Kestrel Soln.................... 00:50:75
Mariner Net .................... 00:50:39 IBM ............................ 00:50:76
Datong Elec .................... 00:50:3A Prolific Tech................... 00:50:77
Mediafire ...................... 00:50:3B Megaton House................... 00:50:78
Tsinghua Novel Elec ............ 00:50:3C Xpeed........................... 00:50:7A
Cisco .......................... 00:50:3E Merlot Comm..................... 00:50:7B
Anchor Games ................... 00:50:3F Videocon........................ 00:50:7C
Emware ......................... 00:50:40 IFP ............................ 00:50:7D
CTX Opto Elec .................. 00:50:41 Newer Tech...................... 00:50:7E
Sci Mfg ........................ 00:50:42 Draytek......................... 00:50:7F
Marvell Semi ................... 00:50:43 Cisco........................... 00:50:80
Asaca .......................... 00:50:44 Murata Machinery................ 00:50:81
Rioworks Soln .................. 00:50:45 Foresson........................ 00:50:82
Menicx Intl .................... 00:50:46 Gilbarco........................ 00:50:83
Infolibria ..................... 00:50:48 ATL Prod........................ 00:50:84
Ellacoya Net ................... 00:50:49 Telkom.......................... 00:50:86
Elteco ......................... 00:50:4A Terasaki Elec................... 00:50:87
Barconet ....................... 00:50:4B Amano........................... 00:50:88
Galil Motion Ctl ............... 00:50:4C Safety Mgmt Sys................. 00:50:89
Tokyo Elec Dev ................. 00:50:4D Compaq.......................... 00:50:8B
Sierra Monitor ................. 00:50:4E RSI Sys......................... 00:50:8C
Olencom Elec ................... 00:50:4F Abit Comp....................... 00:50:8D
Cisco .......................... 00:50:50 Optimation...................... 00:50:8E
Iwatsu Elec .................... 00:50:51 Asita Tech Intl................. 00:50:8F
Tiara Net ...................... 00:50:52 Dctri........................... 00:50:90
Cisco .......................... 00:50:53 Netaccess....................... 00:50:91
Cisco .......................... 00:50:54 Rigaku Ind...................... 00:50:92
Doms ........................... 00:50:55 Boeing.......................... 00:50:93
Vmware ......................... 00:50:56 Pace Micro Tech................. 00:50:94
Broadband Access Sys ........... 00:50:57 Peracom Net..................... 00:50:95
Vegastream ..................... 00:50:58 Salix Tech...................... 00:50:96
Suite Tech Sys ................. 00:50:59 MMC-Embedded.................... 00:50:97
Network Alchemy ................ 00:50:5A Globaloop....................... 00:50:98
Kawasaki Lsi ................... 00:50:5B 3Com............................ 00:50:99
Tundo .......................... 00:50:5C Tag Elec Sys.................... 00:50:9A
Switchcore ..................... 00:50:9B Atlas Copco Tools............... 00:50:D6
Beta Res ....................... 00:50:9C Telstrat........................ 00:50:D7
Industree ...................... 00:50:9D Unicorn Comp.................... 00:50:D8
Les Tech ....................... 00:50:9E Engetron-Engenharia Elet........ 00:50:D9
Horizon Comp ................... 00:50:9F 3Com............................ 00:50:DA
Delta Comp Sys ................. 00:50:A0 Contemporary Ctl................ 00:50:DB
Carlo Gavazzi .................. 00:50:A1 Tas Telefonbau A Schwabe........ 00:50:DC
Cisco .......................... 00:50:A2 Serra Soldadura................. 00:50:DD
Transmedia Comm ................ 00:50:A3 Signum Sys...................... 00:50:DE
IO Tech ........................ 00:50:A4 Airfiber........................ 00:50:DF
Capitol Bus Sys ................ 00:50:A5 NS Tech Elec.................... 00:50:E1
Optronics ...................... 00:50:A6 Cisco........................... 00:50:E2
Cisco .......................... 00:50:A7 Telegate........................ 00:50:E3
Opencon Sys .................... 00:50:A8 Apple........................... 00:50:E4
Moldat Wireless Tech ........... 00:50:A9 Hakusan......................... 00:50:E6
Konica ......................... 00:50:AA Paradise Innov.................. 00:50:E7
Naltec ......................... 00:50:AB Nomadix......................... 00:50:E8
Maple Comp ..................... 00:50:AC Xel Comm........................ 00:50:EA
Comm Wireless .................. 00:50:AD Alpha-top....................... 00:50:EB
Iwaki Elec ..................... 00:50:AE Olicom.......................... 00:50:EC
Intergon ....................... 00:50:AF Anda Net........................ 00:50:ED
Technology Atlanta ............. 00:50:B0 Tek Digitel..................... 00:50:EE
Giddings & Lewis ........... 00:50:B1 SPE Systemhaus.................. 00:50:EF
Brodel Auto .................... 00:50:B2 Cisco........................... 00:50:F0
Voiceboard ..................... 00:50:B3 Libit Signal Proc............... 00:50:F1
Satchwell Ctl Sys .............. 00:50:B4 Microsoft....................... 00:50:F2
Fichet-Bauche .................. 00:50:B5 Global Net Info................. 00:50:F3
Good Way Ind ................... 00:50:B6 Sigmatek & Kg............... 00:50:F4
Boser Tech ..................... 00:50:B7 Pan-Intl........................ 00:50:F6
Inova Comp & Kg ............ 00:50:B8 Venture Mfg..................... 00:50:F7
Xitron Tech .................... 00:50:B9 Entrega Tech.................... 00:50:F8
D-link ......................... 00:50:BA Oxtel........................... 00:50:FA
Cms Tech ....................... 00:50:BB VSK Elec........................ 00:50:FB
Hammer Storage Soln ............ 00:50:BC Edimax Tech..................... 00:50:FC
Cisco .......................... 00:50:BD Isioncomm....................... 00:50:FD
Fast Multimedia ................ 00:50:BE Pctvnet Asa..................... 00:50:FE
Mototech ....................... 00:50:BF Hakko Elec...................... 00:50:FF
Gatan .......................... 00:50:C0 Xycom........................... 00:60:00
Gemflex Net .................... 00:50:C1 Innosys......................... 00:60:01
IEEE Reg Auth .................. 00:50:C2 Screen Subtitling Sys........... 00:60:02
Imd ............................ 00:50:C4 Teraoka Weigh Sys............... 00:60:03
Ads Tech ....................... 00:50:C5 Computadores Modulares.......... 00:60:04
Loop Telecomm .................. 00:50:C6 Feedback Data................... 00:60:05
Addonics Comm .................. 00:50:C8 Sotec........................... 00:60:06
Maspro Denkoh .................. 00:50:C9 Acres Gaming.................... 00:60:07
Net To Net Tech ................ 00:50:CA 3Com............................ 00:60:08
Jetter ......................... 00:50:CB Cisco........................... 00:60:09
Xyratex ........................ 00:50:CC Sord Comp....................... 00:60:0A
Digianswer ..................... 00:50:CD Logware......................... 00:60:0B
Lg Intl ........................ 00:50:CE Applied Data Sys................ 00:60:0C
Vanlink Comm ................... 00:50:CF Microdesign..................... 00:60:0D
Minerva Sys .................... 00:50:D0 Wavenet Intl.................... 00:60:0E
Cisco .......................... 00:50:D1 Westell......................... 00:60:0F
Bae Sys Canada ................. 00:50:D2 Network Mach.................... 00:60:10
Digital Audio .................. 00:50:D3 Crystal Semi.................... 00:60:11
Joohong Info ................... 00:50:D4 Power Comp...................... 00:60:12
Ad Sys ......................... 00:50:D5 Netstal Maschinen............... 00:60:13
Edec ........................... 00:60:14 MMC Net......................... 00:60:4D
Net2net ........................ 00:60:15 Cycle Comp...................... 00:60:4E
Clariion ....................... 00:60:16 Suzuki Mfg...................... 00:60:4F
Tokimec ........................ 00:60:17 Internix........................ 00:60:50
Stellar One .................... 00:60:18 Quality Semi.................... 00:60:51
Boehringer Mannheim ............ 00:60:19 Peripherals Ent................. 00:60:52
Keithley Inst .................. 00:60:1A Toyoda Machine Works............ 00:60:53
Mesa Elec ...................... 00:60:1B Controlware..................... 00:60:54
Telxon ......................... 00:60:1C Cornell Univ.................... 00:60:55
Lucent ......................... 00:60:1D Network Tools................... 00:60:56
Softlab ........................ 00:60:1E Murata Mfg...................... 00:60:57
Stallion Tech .................. 00:60:1F Copper Mountain................. 00:60:58
Pivotal Net .................... 00:60:20 Technical Comm.................. 00:60:59
DSC ............................ 00:60:21 Celcore......................... 00:60:5A
Vicom Sys ...................... 00:60:22 Intraserver Tech................ 00:60:5B
Pericom Semi ................... 00:60:23 Cisco........................... 00:60:5C
Gradient Tech .................. 00:60:24 Scanivalve...................... 00:60:5D
Active Imaging ................. 00:60:25 Liberty Tech Net................ 00:60:5E
Viking Components .............. 00:60:26 Nippon Unisoft.................. 00:60:5F
Superior Modular Prod .......... 00:60:27 Dawning Tech.................... 00:60:60
Macrovision .................... 00:60:28 Whistle Comm.................... 00:60:61
Cary Periph .................... 00:60:29 Telesync........................ 00:60:62
Symicron Comp .................. 00:60:2A Psion Dacom..................... 00:60:63
Peak Audio ..................... 00:60:2B Netcomm......................... 00:60:64
Linx Data Term ................. 00:60:2C Bernecker & Rainer.......... 00:60:65
Alerton Tech ................... 00:60:2D Lacroix Tech.................... 00:60:66
Cyclades ....................... 00:60:2E Acer Netxus..................... 00:60:67
Cisco .......................... 00:60:2F Eicon Tech...................... 00:60:68
Village Tronic ................. 00:60:30 Brocade Comm Sys................ 00:60:69
Hrk Sys ........................ 00:60:31 Mitsubishi Wireless Comm........ 00:60:6A
I-Cube ......................... 00:60:32 Aichi Elec...................... 00:60:6B
Acuity Imag .................... 00:60:33 Arescom......................... 00:60:6C
Robert Bosch ................... 00:60:34 DEC ............................ 00:60:6D
Dallas Semi .................... 00:60:35 Davicom Semi.................... 00:60:6E
Austrian Res Cntr .............. 00:60:36 Clarion Of Amer................. 00:60:6F
Philips Semi ................... 00:60:37 Cisco........................... 00:60:70
Nortel ......................... 00:60:38 Midas Lab....................... 00:60:71
Sancom Tech .................... 00:60:39 VXL Inst........................ 00:60:72
Quick Ctls ..................... 00:60:3A Redcreek Comm................... 00:60:73
Amtec .......................... 00:60:3B Qsc Audio Prod.................. 00:60:74
Hagiwara Sys-Com ............... 00:60:3C Pentek.......................... 00:60:75
3CX ............................ 00:60:3D Schlumberger Tech............... 00:60:76
Cisco .......................... 00:60:3E Prisa Net....................... 00:60:77
Patapsco Des ................... 00:60:3F Power Meas...................... 00:60:78
Netro .......................... 00:60:40 Wavephore Net................... 00:60:79
Yokogawa Elect ................. 00:60:41 DVS ............................ 00:60:7A
Tks (usa) ...................... 00:60:42 Fore Sys........................ 00:60:7B
Comsoft Sys .................... 00:60:43 Waveaccess...................... 00:60:7C
Litton/poly-scientific ......... 00:60:44 Sentient Net.................... 00:60:7D
Pathlight Tech ................. 00:60:45 Gigalabs........................ 00:60:7E
Vmetro ......................... 00:60:46 Aurora Tech..................... 00:60:7F
Cisco .......................... 00:60:47 Microtronix Datacom............. 00:60:80
EMC ............................ 00:60:48 TV/Com Intl..................... 00:60:81
Vina Tech ...................... 00:60:49 Novalink Tech................... 00:60:82
Saic Ideas Group ............... 00:60:4A Cisco........................... 00:60:83
Biodata ........................ 00:60:4B Digital Video................... 00:60:84
SAT ............................ 00:60:4C Storage Concepts................ 00:60:85
Logic Repl Tech ................ 00:60:86 Macraigor Sys................... 00:60:BF
Kansai Elec .................... 00:60:87 Nera............................ 00:60:C0
White Mountain Dsp ............. 00:60:88 Wavespan........................ 00:60:C1
Xata ........................... 00:60:89 MPL............................. 00:60:C2
Citadel Comp ................... 00:60:8A Netvision....................... 00:60:C3
Confertech Intl ................ 00:60:8B Soliton Sys..................... 00:60:C4
3Com ........................... 00:60:8C Ancot........................... 00:60:C5
Unipulse ....................... 00:60:8D Dcs............................. 00:60:C6
HE Elec Tech ................... 00:60:8E Amati Comm...................... 00:60:C7
Tekram Tech .................... 00:60:8F Kuka Welding Sys & Robots... 00:60:C8
Able Comm ...................... 00:60:90 Controlnet...................... 00:60:C9
First Pacific Net .............. 00:60:91 Harmonic Sys.................... 00:60:CA
Micro/Sys ...................... 00:60:92 Hitachi Zosen................... 00:60:CB
Varian ......................... 00:60:93 Emtrak.......................... 00:60:CC
IBM ............................ 00:60:94 Videoserver..................... 00:60:CD
Accu-time Sys .................. 00:60:95 Acclaim Comm.................... 00:60:CE
TS Microtech ................... 00:60:96 Alteon Net...................... 00:60:CF
3Com ........................... 00:60:97 Snmp Res........................ 00:60:D0
HT Comm ........................ 00:60:98 Cascade Comm.................... 00:60:D1
Lan Media ...................... 00:60:99 Lucent.......................... 00:60:D2
NJK Techno ..................... 00:60:9A AT&T........................ 00:60:D3
Astro-Med ...................... 00:60:9B Eldat Comm...................... 00:60:D4
Perkin-Elmer ................... 00:60:9C Miyachi Technos................. 00:60:D5
PMI Food Equip Group ........... 00:60:9D Novatel Wireless Tech........... 00:60:D6
X3 - Info Tech ................. 00:60:9E Ecole Polytech Fed.............. 00:60:D7
Phast .......................... 00:60:9F Elmic Sys....................... 00:60:D8
Switched Net ................... 00:60:A0 Transys Net..................... 00:60:D9
Vpnet .......................... 00:60:A1 JBM Elec........................ 00:60:DA
Nihon Unisys ................... 00:60:A2 NTP Elek........................ 00:60:DB
Continuum Tech ................. 00:60:A3 Toyo Comm Equip................. 00:60:DC
Grinaker Sys Tech .............. 00:60:A4 Myricom......................... 00:60:DD
Performance Telecom ............ 00:60:A5 Kayser-Threde................... 00:60:DE
Particle Meas Sys .............. 00:60:A6 Inrange Tech.................... 00:60:DF
Microsens & Kg ............. 00:60:A7 Axiom Tech...................... 00:60:E0
Tidomat ........................ 00:60:A8 Orckit Comm..................... 00:60:E1
Gesytec ........................ 00:60:A9 Quest Eng & Dev............. 00:60:E2
Intelligent Dev ................ 00:60:AA Arbin Inst...................... 00:60:E3
Larscom ........................ 00:60:AB Compuserve...................... 00:60:E4
Resilience ..................... 00:60:AC Fuji Auto....................... 00:60:E5
Megachips ...................... 00:60:AD Shomiti Sys..................... 00:60:E6
Trio Info Sys .................. 00:60:AE Randata......................... 00:60:E7
Pacific Micro Data ............. 00:60:AF Hitachi Comp Prod............... 00:60:E8
Hewlett Packard ................ 00:60:B0 Atop Tech....................... 00:60:E9
Input/Output ................... 00:60:B1 Streamlogic..................... 00:60:EA
Process Ctl .................... 00:60:B2 Fourthtrack Sys................. 00:60:EB
Z-Com .......................... 00:60:B3 Hermary Opto Elec............... 00:60:EC
Glenayre R&d ............... 00:60:B4 Ricardo Test Auto............... 00:60:ED
Keba ........................... 00:60:B5 Apollo.......................... 00:60:EE
Land Comp ...................... 00:60:B6 Flytech Tech.................... 00:60:EF
Channelmatic ................... 00:60:B7 Johnson & Johnson Med....... 00:60:F0
Corelis ........................ 00:60:B8 Exp Comp........................ 00:60:F1
Nitsuko ........................ 00:60:B9 Lasergraphics................... 00:60:F2
Sahara Net ..................... 00:60:BA Netcom Sys...................... 00:60:F3
Cabletron - Netlink ............ 00:60:BB Adv Comp Soln................... 00:60:F4
Keunyoung Elec ................. 00:60:BC Icon West....................... 00:60:F5
Hubbell-Pulsecom ............... 00:60:BD Nextest Comm.................... 00:60:F6
Webtronics ..................... 00:60:BE Datafusion Sys.................. 00:60:F7
Loran Intl Techn ............... 00:60:F8 National Inst................... 00:80:2F
Diamond Lane Comm .............. 00:60:F9 Nexus Elec...................... 00:80:30
Edu Tech ....................... 00:60:FA Basys........................... 00:80:31
Packeteer ...................... 00:60:FB Access.......................... 00:80:32
Conservation Through ........... 00:60:FC Formation....................... 00:80:33
Netics ......................... 00:60:FD SMT Goupil...................... 00:80:34
Lynx Sys Dev ................... 00:60:FE Technology Works................ 00:80:35
Quvis .......................... 00:60:FF Reflex Mfg Sys.................. 00:80:36
M/A-Com ........................ 00:70:B0 Ericsson........................ 00:80:37
Data Recall .................... 00:70:B3 Data Res & App.............. 00:80:38
Multitech Sys .................. 00:80:00 Alcatel Stc Aus................. 00:80:39
Periphonics .................... 00:80:01 Varityper....................... 00:80:3A
Satelcom ....................... 00:80:02 Apt Comm........................ 00:80:3B
Hytec Elec ..................... 00:80:03 TVS Elec........................ 00:80:3C
Antlow Comm .................... 00:80:04 Surigiken ...................... 00:80:3D
Cactus Comp .................... 00:80:05 Synernetics..................... 00:80:3E
Compuadd ....................... 00:80:06 Tatung.......................... 00:80:3F
Dlog Nc-Sys .................... 00:80:07 John Fluke Mfg.................. 00:80:40
Dynatech Comp Sys .............. 00:80:08 Veb Kombinat Robotron........... 00:80:41
Jupiter Sys .................... 00:80:09 Force Comp...................... 00:80:42
Japan Comp ..................... 00:80:0A Networld........................ 00:80:43
CSK ............................ 00:80:0B Systech Comp.................... 00:80:44
Videcom ........................ 00:80:0C Matsushita Elec Ind............. 00:80:45
Vosswinkel ..................... 00:80:0D Univ Toronto.................... 00:80:46
Atlantix ....................... 00:80:0E In-net.......................... 00:80:47
Standard Micro ................. 00:80:0F Compex.......................... 00:80:48
Commodore Intl ................. 00:80:10 Nissin Elec..................... 00:80:49
Digital Sys Intl ............... 00:80:11 Pro-log......................... 00:80:4A
Integrated Meas Sys ............ 00:80:12 Eagle Tech...................... 00:80:4B
Thomas Conrad .................. 00:80:13 Contec.......................... 00:80:4C
Esprit Sys ..................... 00:80:14 Cyclone Micro................... 00:80:4D
Seiko Sys ...................... 00:80:15 Apex Comp....................... 00:80:4E
Wandel & Goltermann ........ 00:80:16 Daikin Ind...................... 00:80:4F
PFU ............................ 00:80:17 Ziatech......................... 00:80:50
Kobe Steel ..................... 00:80:18 Fibermux........................ 00:80:51
Dayna Comm ..................... 00:80:19 Technically Elite Concepts...... 00:80:52
Bell Atlantic .................. 00:80:1A Intellicom...................... 00:80:53
Kodiak Tech .................... 00:80:1B Frontier Tech................... 00:80:54
Newport Sys Soln ............... 00:80:1C Fermilab........................ 00:80:55
Integrated Inference Mach ...... 00:80:1D Sphinx Elek..................... 00:80:56
Xinetron ....................... 00:80:1E Adsoft.......................... 00:80:57
Krupp Atlas Elec ............... 00:80:1F Printer Sys..................... 00:80:58
Network Prod ................... 00:80:20 Stanley Elec.................... 00:80:59
Newbridge Res .................. 00:80:21 Tulip Comp Intl................. 00:80:5A
Scan-Optics .................... 00:80:22 Condor Sys...................... 00:80:5B
Integrated Bus Net ............. 00:80:23 Agilis.......................... 00:80:5C
Kalpana ........................ 00:80:24 Canstar......................... 00:80:5D
Stollmann ...................... 00:80:25 LSI Logic....................... 00:80:5E
Network Prod ................... 00:80:26 Compaq.......................... 00:80:5F
Adaptive Sys ................... 00:80:27 Network Interface............... 00:80:60
Tradpost ....................... 00:80:28 Litton Sys...................... 00:80:61
Eagle Tech ..................... 00:80:29 Interface ...................... 00:80:62
Test Sys & Sim ............. 00:80:2A Richard Hirschmann.............. 00:80:63
Integrated Marketing ........... 00:80:2B Wyse Tech....................... 00:80:64
Sage Group ..................... 00:80:2C Cybergraphic Sys................ 00:80:65
Xylogics ....................... 00:80:2D Arcom Ctl Sys................... 00:80:66
Castle Rock Comp ............... 00:80:2E Square D........................ 00:80:67
Yamatech Scientific ............ 00:80:68 Microtest....................... 00:80:A1
Computone Sys .................. 00:80:69 Creative Elec Sys............... 00:80:A2
Eri (Empac Res) ................ 00:80:6A Lantronix....................... 00:80:A3
Schmid Telecomm ................ 00:80:6B Liberty Elec.................... 00:80:A4
Cegelec Proj ................... 00:80:6C Speed Intl...................... 00:80:A5
Century Sys .................... 00:80:6D Republic Tech................... 00:80:A6
Nippon Steel ................... 00:80:6E Measurex........................ 00:80:A7
Onelan ......................... 00:80:6F Vitacom......................... 00:80:A8
Computadoras Micron ............ 00:80:70 Clearpoint Res.................. 00:80:A9
SAI Tech ....................... 00:80:71 Maxpeed......................... 00:80:AA
Microplex Sys .................. 00:80:72 Dukane Net Integ................ 00:80:AB
DWB Assoc ...................... 00:80:73 Imlogix......................... 00:80:AC
Fisher Ctls .................... 00:80:74 Cnet Tech....................... 00:80:AD
Parsytec ....................... 00:80:75 Hughes Net Sys.................. 00:80:AE
MCNC ........................... 00:80:76 Allumer......................... 00:80:AF
Brother Ind .................... 00:80:77 Adv Info........................ 00:80:B0
Practical Periph ............... 00:80:78 Softcom......................... 00:80:B1
Microbus Des ................... 00:80:79 Network Equip Tech.............. 00:80:B2
Aitech Sys ..................... 00:80:7A Aval Data....................... 00:80:B3
Artel Comm ..................... 00:80:7B Sophia Sys...................... 00:80:B4
Fibercom ....................... 00:80:7C United Net...................... 00:80:B5
Equinox Sys .................... 00:80:7D Themis Comp..................... 00:80:B6
Southern Pacific ............... 00:80:7E Stellar Comp.................... 00:80:B7
DY-4 ........................... 00:80:7F Bug............................. 00:80:B8
Datamedia ...................... 00:80:80 Arche Tech...................... 00:80:B9
Kendall Square Res ............. 00:80:81 Specialix....................... 00:80:BA
Pep Modular Comp ............... 00:80:82 Hughes Lan Sys.................. 00:80:BB
Amdahl ......................... 00:80:83 Hitachi Eng..................... 00:80:BC
Cloud .......................... 00:80:84 Furukawa Elec................... 00:80:BD
H-Three Sys .................... 00:80:85 Aries Res....................... 00:80:BE
Comp Generation ................ 00:80:86 Takaoka Elec Mfg................ 00:80:BF
OKI Elec Ind ................... 00:80:87 Penril Datacomm................. 00:80:C0
Victor Co Japan ................ 00:80:88 Lanex........................... 00:80:C1
Tecnetics ...................... 00:80:89 IEEE 802 Committee.............. 00:80:C2
Summit Micro ................... 00:80:8A Bicc Info Sys & Svc......... 00:80:C3
Dacoll ......................... 00:80:8B Document Tech................... 00:80:C4
NetScout Sys ................... 00:80:8C Novellco De Mexico.............. 00:80:C5
Westcoast Tech ................. 00:80:8D National Datacomm............... 00:80:C6
Radstone Tech .................. 00:80:8E Xircom.......................... 00:80:C7
C Itoh Elec .................... 00:80:8F D-link Sys...................... 00:80:C8
Microtek Intl .................. 00:80:90 Alberta Micro................... 00:80:C9
Tokyo Elec ..................... 00:80:91 Netcom Res...................... 00:80:CA
Japan Comp Ind ................. 00:80:92 Falco Data Prod................. 00:80:CB
Xyron .......................... 00:80:93 Microwave Bypass Sys............ 00:80:CC
Alfa Laval Auto ................ 00:80:94 Micronics Comp.................. 00:80:CD
Basic Merton Handelsges ........ 00:80:95 Broadcast Tele Sys.............. 00:80:CE
Human Des Sys .................. 00:80:96 Embedded Perf................... 00:80:CF
Centralp Auto .................. 00:80:97 Comp Periph..................... 00:80:D0
TDK ............................ 00:80:98 Kimtron......................... 00:80:D1
Klockner Moeller ............... 00:80:99 Shinnihondenko.................. 00:80:D2
Novus Net ...................... 00:80:9A Shiva........................... 00:80:D3
Justsystem ..................... 00:80:9B Chase Res....................... 00:80:D4
Luxcom ......................... 00:80:9C Cadre Tech...................... 00:80:D5
Commscraft ..................... 00:80:9D Nuvotech........................ 00:80:D6
Datus .......................... 00:80:9E Fantum Eng...................... 00:80:D7
Alcatel Bus Sys ................ 00:80:9F Network Periph.................. 00:80:D8
Edisa HP ....................... 00:80:A0 Emk Elektronik.................. 00:80:D9
Bruel & Kjaer .............. 00:80:DA Samsan.......................... 00:90:13
Graphon ........................ 00:80:DB Rotork Inst..................... 00:90:14
Picker Intl .................... 00:80:DC Centigram Comm.................. 00:90:15
GMX ............................ 00:80:DD ZAC ............................ 00:90:16
Gipsi .......................... 00:80:DE Zypcom.......................... 00:90:17
Adc Codenoll Tech .............. 00:80:DF Ito Elec Ind.................... 00:90:18
XTP Sys ........................ 00:80:E0 Hermes Elec..................... 00:90:19
Stmicroelectronics ............. 00:80:E1 Unisphere Soln.................. 00:90:1A
TDI ............................ 00:80:E2 Digital Ctls.................... 00:90:1B
Coral Net ...................... 00:80:E3 MPS Soft........................ 00:90:1C
Northwest Digital Sys .......... 00:80:E4 PEC ............................ 00:90:1D
Mylex .......................... 00:80:E5 Selesta Ingegne Ria............. 00:90:1E
Peer Net ....................... 00:80:E6 Adtec Prod...................... 00:90:1F
Lynwood Sci Dev ................ 00:80:E7 Philips Analytical X-Ray........ 00:90:20
Cumulus ........................ 00:80:E8 Cisco........................... 00:90:21
Madge .......................... 00:80:E9 Ivex............................ 00:90:22
Adva Opt Net ................... 00:80:EA Zilog........................... 00:90:23
Compcontrol .................... 00:80:EB Pipelinks....................... 00:90:24
Supercomputing Soln ............ 00:80:EC Vision Sys...................... 00:90:25
Iq Tech ........................ 00:80:ED Adv Switching................... 00:90:26
Thomson Csf .................... 00:80:EE Intel........................... 00:90:27
Rational ....................... 00:80:EF Nippon Signal................... 00:90:28
Kyushu Matsushita Elec ......... 00:80:F0 Crypto.......................... 00:90:29
Opus Sys ....................... 00:80:F1 Comm Dev........................ 00:90:2A
Raycom Sys ..................... 00:80:F2 Cisco........................... 00:90:2B
Sun Elec ....................... 00:80:F3 Data & Ctl Equip............ 00:90:2C
Telemecanique Elec ............. 00:80:F4 Data Elec....................... 00:90:2D
Quantel ........................ 00:80:F5 Namco........................... 00:90:2E
Synergy Micro .................. 00:80:F6 Netcore Sys..................... 00:90:2F
Zenith Elec .................... 00:80:F7 Honeywell-Dating................ 00:90:30
Mizar .......................... 00:80:F8 Mysticom........................ 00:90:31
Heurikon ....................... 00:80:F9 Pelcombe Group.................. 00:90:32
RWT ............................ 00:80:FA Innovaphone..................... 00:90:33
BVM ............................ 00:80:FB Imagic.......................... 00:90:34
Avatar ......................... 00:80:FC Alpha Telecom................... 00:90:35
Exsceed ........................ 00:80:FD ENS ............................ 00:90:36
Azure Tech ..................... 00:80:FE Acucomm......................... 00:90:37
Soc De Teleinfo ................ 00:80:FF Fountain Tech................... 00:90:38
Diamond Multi .................. 00:90:00 Shasta Net...................... 00:90:39
Nishimu Elec Ind ............... 00:90:01 Nihon Media Tool................ 00:90:3A
Allgon ......................... 00:90:02 Triems Res Lab.................. 00:90:3B
Aplio .......................... 00:90:03 Atlantic Net Sys................ 00:90:3C
3Com ........................... 00:90:04 Biopac Sys...................... 00:90:3D
Protech Sys .................... 00:90:05 NV Philips Ind.................. 00:90:3E
Hamamatsu Photonics ............ 00:90:06 Aztec Radiomedia................ 00:90:3F
Domex Tech ..................... 00:90:07 Castle Net...................... 00:90:40
Han A Sys ...................... 00:90:08 Applied Dig Access.............. 00:90:41
I Ctls ......................... 00:90:09 Eccs............................ 00:90:42
Proton Elec Ind ................ 00:90:0A Nichibei Denshi................. 00:90:43
Lanner Elec .................... 00:90:0B Assured Dig..................... 00:90:44
Cisco .......................... 00:90:0C Mariposa Tech................... 00:90:45
Overland Data .................. 00:90:0D Dexdyne......................... 00:90:46
Handlink Tech .................. 00:90:0E Giga Fast....................... 00:90:47
Kawasaki Heavy Ind ............. 00:90:0F Zeal............................ 00:90:48
Simulation Lab ................. 00:90:10 Entridia........................ 00:90:49
Wavtrace ....................... 00:90:11 Concur Sys Tech................. 00:90:4A
Globespan Semi ................. 00:90:12 Gemtek Tech..................... 00:90:4B
Epigram ........................ 00:90:4C Golden Ent...................... 00:90:85
Spec ........................... 00:90:4D Cisco........................... 00:90:86
Delem .......................... 00:90:4E Itis............................ 00:90:87
Abb Power T&D .............. 00:90:4F Baxall Sec...................... 00:90:88
Teleste ........................ 00:90:50 Softcom Micro................... 00:90:89
Ultimate Tech .................. 00:90:51 Bayly Comm...................... 00:90:8A
Selcom Elet .................... 00:90:52 Cell Comp....................... 00:90:8B
Daewoo Elec .................... 00:90:53 Etrend Elec..................... 00:90:8C
Innovative Semi ................ 00:90:54 Vickers Elec Sys................ 00:90:8D
Parker Hannifin ................ 00:90:55 Nortel.......................... 00:90:8E
Telestream ..................... 00:90:56 Audiocodes...................... 00:90:8F
Aanetcom ....................... 00:90:57 I-Bus........................... 00:90:90
Ultra Elec ..................... 00:90:58 Digitalscape.................... 00:90:91
Telecom Dev .................... 00:90:59 Cisco........................... 00:90:92
Dearborn Group ................. 00:90:5A Nanao........................... 00:90:93
Raymond & Lae Eng .......... 00:90:5B Osprey Tech..................... 00:90:94
Edmi ........................... 00:90:5C Universal Avionics.............. 00:90:95
Netcom Sicherheitstechnik ...... 00:90:5D Askey Comp...................... 00:90:96
Rauland-Borg ................... 00:90:5E Sycamore Net.................... 00:90:97
Cisco .......................... 00:90:5F Sbc Designs..................... 00:90:98
System Create .................. 00:90:60 Allied Telesis.................. 00:90:99
Pacific Res & Eng .......... 00:90:61 One World Sys................... 00:90:9A
Icp Vortex Comp ................ 00:90:62 Markpoint....................... 00:90:9B
Coherent Comm .................. 00:90:63 Combox.......................... 00:90:9C
Thomson Broadcast Sys .......... 00:90:64 GSE Sys......................... 00:90:9D
Finisar ........................ 00:90:65 Delphi Eng Group................ 00:90:9E
Troika Net ..................... 00:90:66 Digi-data....................... 00:90:9F
Walkabout Comp ................. 00:90:67 8x8............................. 00:90:A0
DVT ............................ 00:90:68 Flying Pig Sys.................. 00:90:A1
Juniper Net .................... 00:90:69 Cybertan Tech................... 00:90:A2
Turnstone Sys .................. 00:90:6A Medialincs...................... 00:90:A3
Applied Res .................... 00:90:6B Altiga Net...................... 00:90:A4
GWT Global Weighing ............ 00:90:6C Spectra Logic................... 00:90:A5
Cisco .......................... 00:90:6D Cisco........................... 00:90:A6
Praxon ......................... 00:90:6E Clientec........................ 00:90:A7
Cisco .......................... 00:90:6F Ninetiles Net................... 00:90:A8
Neo Net ........................ 00:90:70 Western Digital................. 00:90:A9
Badger Tech .................... 00:90:71 Indigo Active Vision............ 00:90:AA
Simrad ......................... 00:90:72 Cisco........................... 00:90:AB
Gaio Tech ...................... 00:90:73 Optivision...................... 00:90:AC
Argon Net ...................... 00:90:74 Aspect Elec..................... 00:90:AD
Nec Do Brasil .................. 00:90:75 Italtel......................... 00:90:AE
Fmt Aircraft Gate Support ...... 00:90:76 J Morita Mfg.................... 00:90:AF
Adv Fibre Comm ................. 00:90:77 Vadem........................... 00:90:B0
Mer Telemanagement ............. 00:90:78 Cisco........................... 00:90:B1
Clearone ....................... 00:90:79 Avici Sys....................... 00:90:B2
Spectralink .................... 00:90:7A Agranat Sys..................... 00:90:B3
E-Tech ......................... 00:90:7B Willowbrook Tech................ 00:90:B4
Digitalcast .................... 00:90:7C Nikon........................... 00:90:B5
Home Wireless Net .............. 00:90:7D Fibex Sys....................... 00:90:B6
Vetronix ....................... 00:90:7E Digital Lightwave............... 00:90:B7
Watchguard Tech ................ 00:90:7F Rohde & Schwarz & Kg.... 00:90:B8
Not Limited .................... 00:90:80 Beran Inst...................... 00:90:B9
Aloha Net ...................... 00:90:81 Valid Net....................... 00:90:BA
Force Inst ..................... 00:90:82 Tainet Comm Sys................. 00:90:BB
Turbo Comm ..................... 00:90:83 Telemann........................ 00:90:BC
Atech Sys ...................... 00:90:84 Omnia Comm...................... 00:90:BD
IBC/Integrated Bus ............. 00:90:BE Nbase Comm...................... 00:90:F7
Cisco .......................... 00:90:BF Mediatrix Telecom............... 00:90:F8
KJ Law Eng ..................... 00:90:C0 Leitch.......................... 00:90:F9
EDA Ind ........................ 00:90:C1 Giganet......................... 00:90:FA
Jk Micro ....................... 00:90:C2 Portwell........................ 00:90:FB
Topic Semi ..................... 00:90:C3 Network Comp Dev................ 00:90:FC
Javelin Sys .................... 00:90:C4 Coppercom....................... 00:90:FD
Internet Magic ................. 00:90:C5 Elecom.......................... 00:90:FE
Optim Sys ...................... 00:90:C6 Tellus Tech..................... 00:90:FF
ICOM ........................... 00:90:C7 Cardiac Rec..................... 00:9D:8E
Waverider Comm ................. 00:90:C8 Centillion Net.................. 00:A0:00
Productivity Enhancement ....... 00:90:C9 Watkins-Johnson Co.............. 00:A0:01
Accord Video ................... 00:90:CA Leeds & Northrup Aus........ 00:A0:02
Wireless Online ................ 00:90:CB Staefa Ctl Sys.................. 00:A0:03
Planex Comm .................... 00:90:CC Netpower........................ 00:A0:04
Ent-Empresa Nac ................ 00:90:CD Daniel Inst..................... 00:A0:05
Tetra .......................... 00:90:CE Image Data Proc................. 00:A0:06
Nortel ......................... 00:90:CF Apexx Tech...................... 00:A0:07
Alcatel Bell ................... 00:90:D0 Netcorp......................... 00:A0:08
Leichu Ent ..................... 00:90:D1 Whitetree Net................... 00:A0:09
Artel Video Sys ................ 00:90:D2 RDC Comm........................ 00:A0:0A
Giesecke & Devrient ........ 00:90:D3 Computex........................ 00:A0:0B
Bindview Dev ................... 00:90:D4 Kingmax Tech.................... 00:A0:0C
Euphonix ....................... 00:90:D5 Panda Project................... 00:A0:0D
Crystal Group .................. 00:90:D6 Visual Net...................... 00:A0:0E
Netboost ....................... 00:90:D7 Broadband Tech.................. 00:A0:0F
Whitecross Sys ................. 00:90:D8 Syslogic Datentechnik........... 00:A0:10
Cisco .......................... 00:90:D9 Mutoh Ind....................... 00:A0:11
Dynarc ......................... 00:90:DA BATM Adv Tech................... 00:A0:12
Next Level Comm ................ 00:90:DB Teltrend........................ 00:A0:13
Teco Info Sys .................. 00:90:DC CSIR............................ 00:A0:14
Miharu Comm .................... 00:90:DD Wyle............................ 00:A0:15
Cardkey Sys .................... 00:90:DE Micropolis...................... 00:A0:16
Mitsubishi Chem ................ 00:90:DF JBM ............................ 00:A0:17
Systran ........................ 00:90:E0 Creative Controllers............ 00:A0:18
Telena ......................... 00:90:E1 Nebula Consultants.............. 00:A0:19
Distributed Proc ............... 00:90:E2 Binar Elek...................... 00:A0:1A
Avex Elec ...................... 00:90:E3 Premisys Comm................... 00:A0:1B
NEC America .................... 00:90:E4 Nascent Net..................... 00:A0:1C
Teknema ........................ 00:90:E5 Sixnet.......................... 00:A0:1D
Acer Lab ....................... 00:90:E6 EST ............................ 00:A0:1E
Horsch Elek .................... 00:90:E7 Tricord Sys..................... 00:A0:1F
Moxa Tech ...................... 00:90:E8 Citicorp/tti.................... 00:A0:20
Janz Comp ...................... 00:90:E9 General Dynamics................ 00:A0:21
Alpha Tech ..................... 00:90:EA Centre For Dev.................. 00:A0:22
Sentry Telecom Sys ............. 00:90:EB Applied Creative Tech........... 00:A0:23
Pyrescom ....................... 00:90:EC 3Com............................ 00:A0:24
Central Sys Res ................ 00:90:ED Redcom Labs..................... 00:A0:25
Personal Comm .................. 00:90:EE Teldat.......................... 00:A0:26
Integrix ....................... 00:90:EF Firepower Sys................... 00:A0:27
Harmonic Lightwaves ............ 00:90:F0 Conner Periph................... 00:A0:28
Dot Hill Sys ................... 00:90:F1 Coulter......................... 00:A0:29
Cisco .......................... 00:90:F2 Trancell Sys.................... 00:A0:2A
Aspect Comm .................... 00:90:F3 Transitions Res................. 00:A0:2B
Lightning Inst ................. 00:90:F4 Interwave Comm.................. 00:A0:2C
Clevo .......................... 00:90:F5 1394 Trade Assoc................ 00:A0:2D
Escalate Net ................... 00:90:F6 Brand Comm...................... 00:A0:2E
Pirelli Cavi ................... 00:A0:2F TrueTime........................ 00:A0:69
Captor ......................... 00:A0:30 Verilink........................ 00:A0:6A
Hazeltine MS 1-17 .............. 00:A0:31 Dms Dorsch Mikrosys............. 00:A0:6B
Ges Singapore .................. 00:A0:32 Shindengen Elec Mfg............. 00:A0:6C
Imc Mess-Sys ................... 00:A0:33 Mannesmann Tally................ 00:A0:6D
Axel ........................... 00:A0:34 Austron......................... 00:A0:6E
Cylink ......................... 00:A0:35 Appcon Group.................... 00:A0:6F
Applied Net Tech ............... 00:A0:36 Coastcom........................ 00:A0:70
Datascope ...................... 00:A0:37 Video Lottery Tech.............. 00:A0:71
Email Elec ..................... 00:A0:38 Ovation Sys..................... 00:A0:72
Ross Tech ...................... 00:A0:39 Com21........................... 00:A0:73
Kubotek ........................ 00:A0:3A Perception Tech................. 00:A0:74
Toshin Elec .................... 00:A0:3B Micron Tech..................... 00:A0:75
EG&G Nuclear Inst .......... 00:A0:3C Cardware Lab.................... 00:A0:76
Opto-22 ........................ 00:A0:3D Fujitsu Nexion.................. 00:A0:77
Atm Forum ...................... 00:A0:3E Marconi Comm.................... 00:A0:78
Comp Society Micro ............. 00:A0:3F Alps Elec....................... 00:A0:79
Apple .......................... 00:A0:40 Adv Periph...................... 00:A0:7A
Leybold-Inficon ................ 00:A0:41 Dawn Comp....................... 00:A0:7B
Spur Prod ...................... 00:A0:42 Tonyang Nylon................... 00:A0:7C
American Tech Labs ............. 00:A0:43 Seeq Tech....................... 00:A0:7D
NTT Intelligent Tech ........... 00:A0:44 Avid Tech....................... 00:A0:7E
Phoenix Contact ................ 00:A0:45 GSM-syntel...................... 00:A0:7F
Scitex ......................... 00:A0:46 Antares Micro................... 00:A0:80
Integrated Fitness ............. 00:A0:47 Alcatel Data Net................ 00:A0:81
Questech ....................... 00:A0:48 NKT Elek........................ 00:A0:82
Digitech Ind ................... 00:A0:49 Asimmphony Turkey............... 00:A0:83
Nisshin Elec ................... 00:A0:4A Dataplex........................ 00:A0:84
TFL Lan ........................ 00:A0:4B Amber Wave Sys.................. 00:A0:86
Innovative Sys & Tech ...... 00:A0:4C Mitel Semi...................... 00:A0:87
EDA Inst ....................... 00:A0:4D Essential Comm.................. 00:A0:88
Voelker Tech ................... 00:A0:4E Xpoint Tech..................... 00:A0:89
Ameritec ....................... 00:A0:4F Brooktrout Tech................. 00:A0:8A
Cypress Semi ................... 00:A0:50 Aston Elec Designs.............. 00:A0:8B
Angia Comm ..................... 00:A0:51 Multimedia Lans................. 00:A0:8C
Stanilite Elec ................. 00:A0:52 Jacomo.......................... 00:A0:8D
Compact Dev .................... 00:A0:53 Nokia Internet Comm............. 00:A0:8E
Linktech ....................... 00:A0:55 Desknet Sys..................... 00:A0:8F
Micropross ..................... 00:A0:56 Timestep........................ 00:A0:90
Elsa ........................... 00:A0:57 Applicom Intl................... 00:A0:91
Glory .......................... 00:A0:58 H Bollmann Manuf................ 00:A0:92
Hamilton Hallmark .............. 00:A0:59 B/E Aerospace................... 00:A0:93
Kofax Image Prod ............... 00:A0:5A Comsat.......................... 00:A0:94
Marquip ........................ 00:A0:5B Acacia Net...................... 00:A0:95
Inventory Conv ................. 00:A0:5C Mitsumi Elec.................... 00:A0:96
CS Comp Sys .................... 00:A0:5D JC Info Sys..................... 00:A0:97
Myriad Logic ................... 00:A0:5E Network Appliance............... 00:A0:98
Btg Eng ........................ 00:A0:5F K-net........................... 00:A0:99
Acer Periph .................... 00:A0:60 Nihon Kohden America............ 00:A0:9A
Puritan Bennett ................ 00:A0:61 QPSX Comm....................... 00:A0:9B
Aes Prodata .................... 00:A0:62 Xyplex.......................... 00:A0:9C
JRL Sys ........................ 00:A0:63 Johnathon Freeman Tech.......... 00:A0:9D
KVB/Analect .................... 00:A0:64 Ictv............................ 00:A0:9E
Nexland ........................ 00:A0:65 Commvision...................... 00:A0:9F
ISA ............................ 00:A0:66 Compact Data.................... 00:A0:A0
Network Serv Group ............. 00:A0:67 Epic Data....................... 00:A0:A1
BHP ............................ 00:A0:68 Digicom......................... 00:A0:A2
Reliable Power Meters .......... 00:A0:A3 ON Elec......................... 00:A0:DC
Micros Sys ..................... 00:A0:A4 Azonix.......................... 00:A0:DD
Teknor Microsys ................ 00:A0:A5 Yamaha.......................... 00:A0:DE
MI Sys ......................... 00:A0:A6 Sts Tech........................ 00:A0:DF
Vorax .......................... 00:A0:A7 Tennyson Tech................... 00:A0:E0
Renex .......................... 00:A0:A8 Westport Res.................... 00:A0:E1
GN Nettest (canada) ............ 00:A0:A9 Keisoku Giken................... 00:A0:E2
Spacelabs Med .................. 00:A0:AA XDL Sys......................... 00:A0:E3
Netcs Info ..................... 00:A0:AB Optiquest....................... 00:A0:E4
Gilat Sat Net .................. 00:A0:AC Nhc Comm........................ 00:A0:E5
Marconi ........................ 00:A0:AD Dialogic........................ 00:A0:E6
Nucom Sys ...................... 00:A0:AE Central Data.................... 00:A0:E7
Wms Ind ........................ 00:A0:AF Reuters Holdings................ 00:A0:E8
I-O Data Dev ................... 00:A0:B0 Elec Retailing Sys.............. 00:A0:E9
First Virtual .................. 00:A0:B1 Ethercom........................ 00:A0:EA
Shima Seiki .................... 00:A0:B2 Fastcomm Comm................... 00:A0:EB
Zykronix ....................... 00:A0:B3 Transmitton..................... 00:A0:EC
Texas Micro .................... 00:A0:B4 Pri Auto........................ 00:A0:ED
3H Tech ........................ 00:A0:B5 Nashoba Net..................... 00:A0:EE
Sanritz Auto ................... 00:A0:B6 Lucidata........................ 00:A0:EF
Cordant ........................ 00:A0:B7 Toronto Microelec............... 00:A0:F0
Symbios Logic .................. 00:A0:B8 MTI ............................ 00:A0:F1
Eagle Tech ..................... 00:A0:B9 Infotek Comm.................... 00:A0:F2
Patton Elec .................... 00:A0:BA Staubli......................... 00:A0:F3
Hilan .......................... 00:A0:BB GE ............................. 00:A0:F4
Viasat ......................... 00:A0:BC Radguard........................ 00:A0:F5
I-tech ......................... 00:A0:BD Autogas Sys..................... 00:A0:F6
Integrated Circuit Sys ......... 00:A0:BE VI Comp......................... 00:A0:F7
Wireless Data Group Motorola ... 00:A0:BF Symbol.......................... 00:A0:F8
Digital Link ................... 00:A0:C0 Bintec Comm..................... 00:A0:F9
Ortivus Medical ................ 00:A0:C1 Marconi Comm.................... 00:A0:FA
RA Sys ......................... 00:A0:C2 Toray Eng....................... 00:A0:FB
Unicomputer .................... 00:A0:C3 Image Sci....................... 00:A0:FC
Cristie Elec ................... 00:A0:C4 Scitex Digital Printing......... 00:A0:FD
Zyxel Comm ..................... 00:A0:C5 Boston Tech..................... 00:A0:FE
Qualcomm ....................... 00:A0:C6 Tellabs Operations.............. 00:A0:FF
Tadiran Telecomm ............... 00:A0:C7 Intel........................... 00:AA:00
Adtran ......................... 00:A0:C8 Intel........................... 00:AA:01
Intel-HF1-06 ................... 00:A0:C9 Intel........................... 00:AA:02
Fujitsu Denso .................. 00:A0:CA Olivetti........................ 00:AA:3C
Ark Telecomm ................... 00:A0:CB Grass Valley Group.............. 00:B0:09
Lite-On Comm ................... 00:A0:CC Infogear Tech................... 00:B0:17
Dr Johannes Heidenhain ......... 00:A0:CD Casi-rusco...................... 00:B0:19
Astrocom ....................... 00:A0:CE Westport Tech................... 00:B0:1C
Sotas .......................... 00:A0:CF Rantic Labs..................... 00:B0:1E
Ten X Tech ..................... 00:A0:D0 Orsys........................... 00:B0:2A
Inventec ....................... 00:A0:D1 Viagate Tech.................... 00:B0:2D
Allied Telesis Intl ............ 00:A0:D2 Hiq Net......................... 00:B0:3B
Instem Comp Sys ................ 00:A0:D3 Marconi Comm.................... 00:B0:48
Radiolan ...................... 00:A0:D4 Cisco........................... 00:B0:4A
Sierra Wireless ................ 00:A0:D5 Intellon........................ 00:B0:52
SBE ............................ 00:A0:D6 Cisco........................... 00:B0:64
Kasten Chase Appl Res .......... 00:A0:D7 Honewell Oy..................... 00:B0:69
Spectra-Tek .................... 00:A0:D8 Jones Futurex................... 00:B0:6D
Convex Comp .................... 00:A0:D9 Mannesmann Ipulsys.............. 00:B0:80
Integrated Sys ................. 00:A0:DA Locsoft......................... 00:B0:86
Fisher & Paykel Prod ....... 00:A0:DB Cisco........................... 00:B0:8E
Transmeta ...................... 00:B0:91 Dataproducts.................... 00:C0:25
Alaris ......................... 00:B0:94 Lans Tech....................... 00:C0:26
Morrow Tech .................... 00:B0:9A Cipher Sys...................... 00:C0:27
Point Grey Res ................. 00:B0:9D Jasco........................... 00:C0:28
Siae-microelettronica .......... 00:B0:AC Kabel Rheydt.................... 00:C0:29
Symmetricom .................... 00:B0:AE Ohkura Elec..................... 00:C0:2A
Xstreamis ...................... 00:B0:B3 Gerloff......................... 00:C0:2B
Cisco .......................... 00:B0:C2 Centrum Comm.................... 00:C0:2C
Tellabs Operations ............. 00:B0:C7 Fuji Photo Film................. 00:C0:2D
Tech Rescue .................... 00:B0:CE Netwiz.......................... 00:C0:2E
Dell Comp ...................... 00:B0:D0 Okuma........................... 00:C0:2F
Nextcell ....................... 00:B0:DB Integrated Eng.................. 00:C0:30
Reliable Data Tech ............. 00:B0:DF Design Res Sys.................. 00:C0:31
British Federal ................ 00:B0:E7 I-Cubed......................... 00:C0:32
Eacem .......................... 00:B0:EC Telebit Comm Aps................ 00:C0:33
Ajile Sys ...................... 00:B0:EE Transaction Net................. 00:C0:34
Caly Net ....................... 00:B0:F0 Quintar......................... 00:C0:35
Networth Tech .................. 00:B0:F5 Raytech Elec.................... 00:C0:36
Octothorpe ..................... 00:BB:01 Dynatem......................... 00:C0:37
Ungermann-Bass ................. 00:BB:F0 Raster Image Proc Sys........... 00:C0:38
Lanoptics ...................... 00:C0:00 TDK Semi........................ 00:C0:39
Diatek Patient Mgmt ............ 00:C0:01 Men-Mikro Elek.................. 00:C0:3A
Sercomm ........................ 00:C0:02 Multiaccess Comp................ 00:C0:3B
Globalnet Comm ................. 00:C0:03 Tower Tech...................... 00:C0:3C
Japan Bus Comp ................. 00:C0:04 Wiesemann & Theis........... 00:C0:3D
Livingston Ent ................. 00:C0:05 FA Gebr Heller.................. 00:C0:3E
Nippon Avionics ................ 00:C0:06 Stores Auto Sys................. 00:C0:3F
Pinnacle Data Sys .............. 00:C0:07 Ecci............................ 00:C0:40
Seco Srl ....................... 00:C0:08 Digital Trans Sys............... 00:C0:41
Kt Tech ........................ 00:C0:09 Datalux......................... 00:C0:42
Micro Craft .................... 00:C0:0A Stratacom....................... 00:C0:43
Norcontrol ..................... 00:C0:0B Emcom........................... 00:C0:44
Relia Tech ..................... 00:C0:0C Isolation Sys................... 00:C0:45
Adv Logic Res .................. 00:C0:0D Kemitron........................ 00:C0:46
Psitech ........................ 00:C0:0E Unimicro Sys.................... 00:C0:47
Quantum Soft Sys ............... 00:C0:0F Bay Tech Assoc.................. 00:C0:48
Hirakawa Hewtech ............... 00:C0:10 US Robotics..................... 00:C0:49
Interactive Comp Dev ........... 00:C0:11 Group 2000...................... 00:C0:4A
Netspan ........................ 00:C0:12 Creative Micro.................. 00:C0:4B
Netrix ......................... 00:C0:13 Dept Foreign Affairs............ 00:C0:4C
Telematics Calabasas Intl ...... 00:C0:14 Mitec........................... 00:C0:4D
New Media ...................... 00:C0:15 Comtrol......................... 00:C0:4E
Elec Theatre Ctlss ............. 00:C0:16 Dell Comp....................... 00:C0:4F
Forte Net ...................... 00:C0:17 Toyo Denki Seizo................ 00:C0:50
Lanart ......................... 00:C0:18 Adv Integ Res................... 00:C0:51
Leap Tech ...................... 00:C0:19 Burr-brown...................... 00:C0:52
Corometrics Med Sys ............ 00:C0:1A Davox........................... 00:C0:53
Socket Comm .................... 00:C0:1B Network Periph.................. 00:C0:54
Interlink Comm ................. 00:C0:1C Modular Comp Tech............... 00:C0:55
Grand Junction Net ............. 00:C0:1D Somelec......................... 00:C0:56
La Francaise Des Jeux .......... 00:C0:1E Myco Elec....................... 00:C0:57
SERCEL ......................... 00:C0:1F Dataexpert...................... 00:C0:58
Arco Elec Ctl .................. 00:C0:20 Nippon Denso.................... 00:C0:59
Netexpress ..................... 00:C0:21 Semaphore Comm.................. 00:C0:5A
Lasermaster Tech ............... 00:C0:22 Networks Northwest.............. 00:C0:5B
Tutankhamon Elec ............... 00:C0:23 Elonex.......................... 00:C0:5C
Eden ........................... 00:C0:24 L&N Tech.................... 00:C0:5D
Vari-lite ...................... 00:C0:5E Archipel........................ 00:C0:97
Fine-Pal ....................... 00:C0:5F Chuntex Elec.................... 00:C0:98
ID Scand ....................... 00:C0:60 Yoshiki Ind..................... 00:C0:99
Solectek ....................... 00:C0:61 Photonics....................... 00:C0:9A
Impulse Tech ................... 00:C0:62 Reliance Comm/Tec R-Tec......... 00:C0:9B
Morning Star Tech .............. 00:C0:63 Toa Elec........................ 00:C0:9C
General Datacomm Ind ........... 00:C0:64 Distributed Sys Intl............ 00:C0:9D
Scope Comm ..................... 00:C0:65 Cache Comp...................... 00:C0:9E
Docupoint ...................... 00:C0:66 Quanta Comp..................... 00:C0:9F
United Barcode Ind ............. 00:C0:67 Adv Micro Res................... 00:C0:A0
Philip Drake Elec .............. 00:C0:68 Tokyo Denshi Sekei.............. 00:C0:A1
Adaptive Broadband ............. 00:C0:69 Intermedium..................... 00:C0:A2
Zahner-Elek .................... 00:C0:6A Dual Ent........................ 00:C0:A3
Osi Plus ....................... 00:C0:6B Unigraf Oy...................... 00:C0:A4
Svec Comp ...................... 00:C0:6C Dickens Data Sys................ 00:C0:A5
Boca Res ....................... 00:C0:6D Exicom Aus...................... 00:C0:A6
Haft Tech ...................... 00:C0:6E Seel............................ 00:C0:A7
Komatsu ........................ 00:C0:6F GVC ............................ 00:C0:A8
Sectra Secure-Trans ............ 00:C0:70 Barron Mccann................... 00:C0:A9
Areanex Comm ................... 00:C0:71 Silicon Valley Comp............. 00:C0:AA
KNX ............................ 00:C0:72 Telco Sys....................... 00:C0:AB
Xedia .......................... 00:C0:73 Gambit Comp Comm................ 00:C0:AC
Toyoda Auto Loom ............... 00:C0:74 Marben Comm Sys................. 00:C0:AD
Xante .......................... 00:C0:75 Towercom Dba PC House........... 00:C0:AE
I-Data Intl A-s ................ 00:C0:76 Teklogix........................ 00:C0:AF
Daewoo Telecom ................. 00:C0:77 GCC Tech........................ 00:C0:B0
Comp Sys Eng ................... 00:C0:78 Genius Net...................... 00:C0:B1
Fonsys ......................... 00:C0:79 Norand.......................... 00:C0:B2
Priva .......................... 00:C0:7A Comstat Datacomm................ 00:C0:B3
Ascend Comm .................... 00:C0:7B Myson Tech...................... 00:C0:B4
Hightech Info .................. 00:C0:7C Corporate Net Sys............... 00:C0:B5
Risc Dev ....................... 00:C0:7D Meridian Data................... 00:C0:B6
Kubota Elec .................... 00:C0:7E American Power Conv Corp........ 00:C0:B7
Nupon Comp ..................... 00:C0:7F Frasers Hill.................... 00:C0:B8
Netstar ........................ 00:C0:80 Funk Soft....................... 00:C0:B9
Metrodata ...................... 00:C0:81 Netvantage...................... 00:C0:BA
Moore Prod ..................... 00:C0:82 Forval Creative................. 00:C0:BB
Trace Mountain Prod ............ 00:C0:83 Telecom Aus/CSSC................ 00:C0:BC
Data Link ...................... 00:C0:84 Inex Tech....................... 00:C0:BD
Elec For Imaging ............... 00:C0:85 Alcatel - Sel................... 00:C0:BE
Lynk ........................... 00:C0:86 Technology Concepts............. 00:C0:BF
Uunet Tech ..................... 00:C0:87 Shore Micro..................... 00:C0:C0
EKF Elektronik ................. 00:C0:88 Quad/Graphics................... 00:C0:C1
Telindus Dist .................. 00:C0:89 Infinite Net.................... 00:C0:C2
Lauterbach Datentechnik ........ 00:C0:8A Acuson Comp Sono................ 00:C0:C3
Risq Modular Sys ............... 00:C0:8B Comp Operational................ 00:C0:C4
Performance Tech ............... 00:C0:8C Sid Info........................ 00:C0:C5
Tronix Prod Dev ................ 00:C0:8D Personal Media.................. 00:C0:C6
Network Info Tech .............. 00:C0:8E Sparktrum Micro................. 00:C0:C7
Matsushita Elec Works .......... 00:C0:8F Micro Byte...................... 00:C0:C8
Praim .......................... 00:C0:90 Elsag Bailey Proc............... 00:C0:C9
Jabil Circuit .................. 00:C0:91 Alfa............................ 00:C0:CA
Mennen Med ..................... 00:C0:92 Control Tech.................... 00:C0:CB
Alta Res ....................... 00:C0:93 Telesciences Co Sys............. 00:C0:CC
VMX ............................ 00:C0:94 Comelta......................... 00:C0:CD
Znyx ........................... 00:C0:95 Cei Sys & Eng............... 00:C0:CE
Tamura ......................... 00:C0:96 Imatran Voima................... 00:C0:CF
Ratoc Sys ...................... 00:C0:D0 Mic Assoc....................... 00:D0:07
Comtree Tech ................... 00:C0:D1 Mactell......................... 00:D0:08
Syntellect ..................... 00:C0:D2 Hsing Tech Ent.................. 00:D0:09
Olympus Image Sys .............. 00:C0:D3 Lanaccess Telecom............... 00:D0:0A
Axon Net ....................... 00:C0:D4 Rhk Tech........................ 00:D0:0B
Quancom Elec ................... 00:C0:D5 Snijder Micro Sys............... 00:D0:0C
J1 Sys ......................... 00:C0:D6 Micromeritics Inst.............. 00:D0:0D
Taiwan Trading Center .......... 00:C0:D7 Pluris.......................... 00:D0:0E
Universal Data Sys ............. 00:C0:D8 Speech Design................... 00:D0:0F
Quinte Net Confid .............. 00:C0:D9 Convergent Net.................. 00:D0:10
Nice Sys ....................... 00:C0:DA Prism Video..................... 00:D0:11
IPC ............................ 00:C0:DB Gateworks....................... 00:D0:12
Eos Tech ....................... 00:C0:DC Primex Aerospace................ 00:D0:13
QLogic ......................... 00:C0:DD Root............................ 00:D0:14
Zcomm .......................... 00:C0:DE Univex Microtech................ 00:D0:15
KYE Sys ........................ 00:C0:DF Scm Micro....................... 00:D0:16
DSC Comm ....................... 00:C0:E0 Syntech Info.................... 00:D0:17
Sonic Soln ..................... 00:C0:E1 Qwes Com........................ 00:D0:18
Calcomp ........................ 00:C0:E2 Dainippon Screen................ 00:D0:19
Ositech Comm ................... 00:C0:E3 Urmet Sud....................... 00:D0:1A
Siemens Building ............... 00:C0:E4 Mimaki Eng...................... 00:D0:1B
Gespac ......................... 00:C0:E5 SBS Tech........................ 00:D0:1C
Verilink Corp .................. 00:C0:E6 Furuno Elec..................... 00:D0:1D
Fiberdata ...................... 00:C0:E7 Pingtel......................... 00:D0:1E
Plexcom ........................ 00:C0:E8 CTAM............................ 00:D0:1F
Oak Soln ....................... 00:C0:E9 Aim Sys......................... 00:D0:20
Array Tech ..................... 00:C0:EA Regent Elec..................... 00:D0:21
Seh Comptechnik ................ 00:C0:EB Incredible Tech................. 00:D0:22
Dauphin Tech ................... 00:C0:EC Infortrend Tech................. 00:D0:23
US Army Elec ................... 00:C0:ED Cognex.......................... 00:D0:24
Kyocera ........................ 00:C0:EE Xrosstech....................... 00:D0:25
Abit ........................... 00:C0:EF Hirschmann Aus.................. 00:D0:26
Kingston Tech .................. 00:C0:F0 Applied Auto.................... 00:D0:27
Shinko Elec .................... 00:C0:F1 Omneon Video Net................ 00:D0:28
Transition Net ................. 00:C0:F2 Wakefern Food................... 00:D0:29
Network Comm ................... 00:C0:F3 Flexion Sys..................... 00:D0:2A
Interlink Sys .................. 00:C0:F4 Jetcell......................... 00:D0:2B
Metacomp ....................... 00:C0:F5 Campbell Sci.................... 00:D0:2C
Celan Tech ..................... 00:C0:F6 Ademco.......................... 00:D0:2D
Engage Comm .................... 00:C0:F7 Comm Auto....................... 00:D0:2E
About Comp ..................... 00:C0:F8 Vlsi Tech....................... 00:D0:2F
Harris & Jeffries .......... 00:C0:F9 Safetran Sys.................... 00:D0:30
Canary Comm .................... 00:C0:FA Industrial Logic................ 00:D0:31
Adv Tech Labs .................. 00:C0:FB Yano Elec....................... 00:D0:32
Elastic Reality ................ 00:C0:FC Dalian Daxian Net............... 00:D0:33
Prosum ......................... 00:C0:FD Ormec Sys....................... 00:D0:34
Aptec Comp Sys ................. 00:C0:FE Behavior Tech Comp.............. 00:D0:35
Dot Hill Sys ................... 00:C0:FF Technology Atlanta.............. 00:D0:36
Cambridge Bband ................ 00:CB:BD Philips-DVS-LO.................. 00:D0:37
Comm Mach ...................... 00:CF:1C Fivemere........................ 00:D0:38
Ferran Sci ..................... 00:D0:00 Utilicom........................ 00:D0:39
VST Tech ....................... 00:D0:01 Zoneworx........................ 00:D0:3A
Ditech ......................... 00:D0:02 Vision Prod..................... 00:D0:3B
Comda Ent ...................... 00:D0:03 Vieo............................ 00:D0:3C
Pentacom ....................... 00:D0:04 Rocketchips..................... 00:D0:3E
ZHS Zeitmanagementsysteme ...... 00:D0:05 American Comm................... 00:D0:3F
Cisco .......................... 00:D0:06 Sysmate......................... 00:D0:40
Amigo Tech ..................... 00:D0:41 Amaquest Comp................... 00:D0:7A
Mahlo & Ug ................. 00:D0:42 Comcam Intl..................... 00:D0:7B
Zonal Retail Data Sys .......... 00:D0:43 Koyo Elec....................... 00:D0:7C
Alidian Net .................... 00:D0:44 Cosine Comm..................... 00:D0:7D
Kvaser ......................... 00:D0:45 Keycorp......................... 00:D0:7E
Dolby Lab ...................... 00:D0:46 Strategy & Tech............. 00:D0:7F
XN Tech ........................ 00:D0:47 Exabyte......................... 00:D0:80
Ecton .......................... 00:D0:48 Real Time Dev................... 00:D0:81
Impresstek ..................... 00:D0:49 Iowave.......................... 00:D0:82
Presence Tech .................. 00:D0:4A Invertex........................ 00:D0:83
La Cie Group ................... 00:D0:4B Nexcomm Sys..................... 00:D0:84
Eurotel Telecom ................ 00:D0:4C Otis Elevator................... 00:D0:85
Div Res & Stat ............. 00:D0:4D Foveon.......................... 00:D0:86
Logibag ........................ 00:D0:4E Microfirst...................... 00:D0:87
Bitronics ...................... 00:D0:4F Mainsail Net.................... 00:D0:88
Iskratel ....................... 00:D0:50 Dynacolor....................... 00:D0:89
O2 Micro ....................... 00:D0:51 Photron......................... 00:D0:8A
Ascend Comm .................... 00:D0:52 ADVA............................ 00:D0:8B
Connected Sys .................. 00:D0:53 Genoa Tech...................... 00:D0:8C
SAS Inst ....................... 00:D0:54 Phoenix Group................... 00:D0:8D
Kathrein-Werke ................. 00:D0:55 Nvision......................... 00:D0:8E
Somat .......................... 00:D0:56 Ardent Tech..................... 00:D0:8F
Ultrak ......................... 00:D0:57 Cisco........................... 00:D0:90
Cisco .......................... 00:D0:58 Smartsan Sys.................... 00:D0:91
Ambit Micro .................... 00:D0:59 Glenayre Western Multiplex...... 00:D0:92
Symbionics ..................... 00:D0:5A TQ-Components................... 00:D0:93
Acroloop Motion Ctl ............ 00:D0:5B Timeline Vista.................. 00:D0:94
Technotrend Sys ................ 00:D0:5C Xylan........................... 00:D0:95
Intelliworx .................... 00:D0:5D 3Com............................ 00:D0:96
Stratabeam Tech ................ 00:D0:5E Cisco........................... 00:D0:97
Valcom ......................... 00:D0:5F Ips Auto........................ 00:D0:98
Panasonic European ............. 00:D0:60 Elcard Oy....................... 00:D0:99
Tremon Ent ..................... 00:D0:61 Filanet......................... 00:D0:9A
Digigram ....................... 00:D0:62 Spectel......................... 00:D0:9B
Cisco .......................... 00:D0:63 Kapadia Comm.................... 00:D0:9C
Multitel ....................... 00:D0:64 Veris Ind....................... 00:D0:9D
Toko Elec ...................... 00:D0:65 2Wire........................... 00:D0:9E
Wintriss Eng ................... 00:D0:66 Novtek Test Sys................. 00:D0:9F
Campio Comm .................... 00:D0:67 Mips Denmark.................... 00:D0:A0
Iwill .......................... 00:D0:68 Oskar Vierling.................. 00:D0:A1
Technologic Sys ................ 00:D0:69 Integrated Dev.................. 00:D0:A2
Linkup Sys ..................... 00:D0:6A Vocal Data...................... 00:D0:A3
Sr Telecom ..................... 00:D0:6B Alantro Comm.................... 00:D0:A4
Sharewave ...................... 00:D0:6C American Arium.................. 00:D0:A5
Acrison ........................ 00:D0:6D Lanbird Tech.................... 00:D0:A6
Trendview Rec .................. 00:D0:6E Tokyo Sokki Kenkyujo............ 00:D0:A7
Kmc Ctls ....................... 00:D0:6F Network Engines................. 00:D0:A8
Long Well Elec ................. 00:D0:70 Shinano Kenshi.................. 00:D0:A9
Echelon ........................ 00:D0:71 Chase Comm...................... 00:D0:AA
Broadlogic ..................... 00:D0:72 Deltakabel Telecom.............. 00:D0:AB
Acn Adv Comm ................... 00:D0:73 Grayson Wireless................ 00:D0:AC
Taqua Sys ...................... 00:D0:74 Tl Ind.......................... 00:D0:AD
Alaris Med Sys ................. 00:D0:75 Oresis Comm..................... 00:D0:AE
Merrill Lynch .................. 00:D0:76 Cutler-Hammer................... 00:D0:AF
Lucent ......................... 00:D0:77 Bitswitch....................... 00:D0:B0
Eltex Sweden ................... 00:D0:78 Omega Elec Sa................... 00:D0:B1
Cisco .......................... 00:D0:79 Xiotech......................... 00:D0:B2
Drs Flight Safety .............. 00:D0:B3 Nakayo Telecomm................. 00:D0:EC
Katsujima ...................... 00:D0:B4 Xiox............................ 00:D0:ED
Dotcom ......................... 00:D0:B5 Dictaphone...................... 00:D0:EE
Crescent Net ................... 00:D0:B6 IGT............................. 00:D0:EF
Intel .......................... 00:D0:B7 Convision Tech.................. 00:D0:F0
Iomega ......................... 00:D0:B8 Sega Ent........................ 00:D0:F1
Microtek Intl .................. 00:D0:B9 Monterey Net.................... 00:D0:F2
Cisco .......................... 00:D0:BA Solari Di Udine................. 00:D0:F3
Cisco .......................... 00:D0:BB Carinthian Tech Inst............ 00:D0:F4
Cisco .......................... 00:D0:BC Orange Micro.................... 00:D0:F5
Sican .......................... 00:D0:BD Northchurch Comm................ 00:D0:F6
Emutec ......................... 00:D0:BE Next Nets....................... 00:D0:F7
Pivotal Tech ................... 00:D0:BF Fujian Star Term................ 00:D0:F8
Cisco .......................... 00:D0:C0 Acute Comm...................... 00:D0:F9
Harmonic Data Sys .............. 00:D0:C1 Racal Guardata.................. 00:D0:FA
Balthazar Tech ................. 00:D0:C2 Tek Micro....................... 00:D0:FB
Vivid Tech ..................... 00:D0:C3 Granite Micro................... 00:D0:FC
Teratech ....................... 00:D0:C4 Optima Tele.com................. 00:D0:FD
Computational Sys .............. 00:D0:C5 Astral Point.................... 00:D0:FE
Thomas & Betts ............. 00:D0:C6 Cisco........................... 00:D0:FF
Pathway ........................ 00:D0:C7 Ungermann-Bass.................. 00:DD:00
I/O Consulting ................. 00:D0:C8 Ungermann-Bass.................. 00:DD:01
Advantech ...................... 00:D0:C9 Ungermann-Bass.................. 00:DD:02
Intrinsyc Soft ................. 00:D0:CA Ungermann-Bass.................. 00:DD:03
Dasan .......................... 00:D0:CB Ungermann-Bass.................. 00:DD:04
Technologies Lyre .............. 00:D0:CC Ungermann-Bass.................. 00:DD:05
Atan Tech ...................... 00:D0:CD Ungermann-Bass.................. 00:DD:06
Asyst Elec ..................... 00:D0:CE Ungermann-Bass.................. 00:DD:07
Moreton Bay .................... 00:D0:CF Ungermann-Bass.................. 00:DD:08
Zhongxing Telecom .............. 00:D0:D0 Ungermann-Bass.................. 00:DD:09
Sirocco Sys .................... 00:D0:D1 Ungermann-Bass.................. 00:DD:0A
Epilog ......................... 00:D0:D2 Ungermann-Bass.................. 00:DD:0B
Cisco .......................... 00:D0:D3 Ungermann-Bass.................. 00:DD:0C
V-Bits ......................... 00:D0:D4 Ungermann-Bass.................. 00:DD:0D
Grundig ........................ 00:D0:D5 Ungermann-Bass.................. 00:DD:0E
Aethra Telecom ................. 00:D0:D6 Ungermann-Bass.................. 00:DD:0F
B2c2 ........................... 00:D0:D7 Fujitsu......................... 00:E0:00
3Com ........................... 00:D0:D8 Strand Lighting................. 00:E0:01
Dedicated Micro ................ 00:D0:D9 Crossroads Sys.................. 00:E0:02
Taicom Data Sys ................ 00:D0:DA Nokia Wireless Bus Comm......... 00:E0:03
McQuay Intl .................... 00:D0:DB PMC-Sierra...................... 00:E0:04
Modular Mining Sys ............. 00:D0:DC Technical....................... 00:E0:05
Sunrise Telecom ................ 00:D0:DD Silicon Integrated Sys.......... 00:E0:06
Philips Multimedia Net ......... 00:D0:DE Network Alchemy................. 00:E0:07
Kuzumi Elec .................... 00:D0:DF Amazing Ctls!................... 00:E0:08
Dooin Elec ..................... 00:D0:E0 Marathon Tech................... 00:E0:09
Avionitek Israel ............... 00:D0:E1 Diba............................ 00:E0:0A
MRT Micro ...................... 00:D0:E2 Rooftop Comm.................... 00:E0:0B
Ele-Chem Eng ................... 00:D0:E3 Motorola........................ 00:E0:0C
Cisco .......................... 00:D0:E4 Radiant Sys..................... 00:E0:0D
Solidum Sys .................... 00:D0:E5 Avalon Imag Sys................. 00:E0:0E
Ibond .......................... 00:D0:E6 Shanghai Baud Data.............. 00:E0:0F
VCon Telecomm .................. 00:D0:E7 Hess SB-Auto.................... 00:E0:10
Mac Sys ........................ 00:D0:E8 Uniden San Diego................ 00:E0:11
Advantage Cent ................. 00:D0:E9 Pluto Tech...................... 00:E0:12
Nextone Comm ................... 00:D0:EA Eastern Elec.................... 00:E0:13
Lightera Net ................... 00:D0:EB Cisco........................... 00:E0:14
Heiwa .......................... 00:E0:15 Sanyo Denki..................... 00:E0:4E
Rapid City Comm ................ 00:E0:16 Cisco........................... 00:E0:4F
Exxact ......................... 00:E0:17 Executone Info.................. 00:E0:50
Asustek Comp ................... 00:E0:18 Talx............................ 00:E0:51
Ing Giordano Elet .............. 00:E0:19 Foundry Net..................... 00:E0:52
Comtec Sys ..................... 00:E0:1A Cellport Labs................... 00:E0:53
Sphere Comm .................... 00:E0:1B Kodai Hitec..................... 00:E0:54
Mobility Elecy ................. 00:E0:1C Ingenieria Elec................. 00:E0:55
WebTV Net ...................... 00:E0:1D Holontech....................... 00:E0:56
Cisco .......................... 00:E0:1E Han Micro....................... 00:E0:57
Avidia Sys ..................... 00:E0:1F Phase One Denmark............... 00:E0:58
Tecnomen ....................... 00:E0:20 Controlled Env.................. 00:E0:59
Freegate ....................... 00:E0:21 Galea Net Sec................... 00:E0:5A
Medialight ..................... 00:E0:22 West End Sys.................... 00:E0:5B
Telrad ......................... 00:E0:23 Matsushita Kotobuki............. 00:E0:5C
Gadzoox Net .................... 00:E0:24 Unitec.......................... 00:E0:5D
Dit ............................ 00:E0:25 Japan Aviation Elec............. 00:E0:5E
Eastman Kodak .................. 00:E0:26 E-Net........................... 00:E0:5F
Dux ............................ 00:E0:27 Sherwood........................ 00:E0:60
Aptix .......................... 00:E0:28 Edgepoint Net................... 00:E0:61
Standard Micro ................. 00:E0:29 Host Eng........................ 00:E0:62
Tandberg Television ............ 00:E0:2A Cabletron - Yago Sys............ 00:E0:63
Extreme Net .................... 00:E0:2B Samsung Elec.................... 00:E0:64
Ast Comp ....................... 00:E0:2C Optical Access Intl............. 00:E0:65
Innomedialogic ................. 00:E0:2D Promax Sys...................... 00:E0:66
SPC Elec ....................... 00:E0:2E EAC Auto-Cons................... 00:E0:67
MCNS Holdings .................. 00:E0:2F Merrimac Sys.................... 00:E0:68
Melita Intl .................... 00:E0:30 Jaycor Net...................... 00:E0:69
Hagiwara Elec .................. 00:E0:31 Kapsch.......................... 00:E0:6A
Misys Financial Sys ............ 00:E0:32 W&G Special Prod............ 00:E0:6B
EEPD ........................... 00:E0:33 Baltimore Tech.................. 00:E0:6C
Cisco .......................... 00:E0:34 Compuware....................... 00:E0:6D
Loughborough Sound Images ...... 00:E0:35 Far Sys......................... 00:E0:6E
Pioneer ........................ 00:E0:36 Terayon......................... 00:E0:6F
Century ........................ 00:E0:37 DH Tech......................... 00:E0:70
Proxima ........................ 00:E0:38 Epis Micro...................... 00:E0:71
Paradyne ....................... 00:E0:39 Lynk............................ 00:E0:72
Cabletron Sys .................. 00:E0:3A National Amusement.............. 00:E0:73
Prominet ....................... 00:E0:3B Tiernan Comm.................... 00:E0:74
Advansys ....................... 00:E0:3C Atlas Comp Equip................ 00:E0:75
Focon Elec Sys ................. 00:E0:3D Development Concepts............ 00:E0:76
Alfatech ....................... 00:E0:3E Webgear......................... 00:E0:77
Jaton .......................... 00:E0:3F Berkeley Net.................... 00:E0:78
Deskstation Tech ............... 00:E0:40 ATNR............................ 00:E0:79
CSPI ........................... 00:E0:41 Mikrodidakt..................... 00:E0:7A
Pacom Data ..................... 00:E0:42 Bay Net......................... 00:E0:7B
Vitalcom ....................... 00:E0:43 Mettler-Toledo.................. 00:E0:7C
Lsics .......................... 00:E0:44 Netronix........................ 00:E0:7D
Touchwave ...................... 00:E0:45 Walt Disney Imagineering........ 00:E0:7E
Bently Nevada .................. 00:E0:46 Logististem..................... 00:E0:7F
Infocus Sys .................... 00:E0:47 Control Resources............... 00:E0:80
SDL Comm ....................... 00:E0:48 Tyan Comp....................... 00:E0:81
Microwi Elec ................... 00:E0:49 Anerma.......................... 00:E0:82
Enhanced Mess Sys .............. 00:E0:4A Jato Tech....................... 00:E0:83
Jump Ind ....................... 00:E0:4B Compulite....................... 00:E0:84
Realtek Semi ................... 00:E0:4C Global Maintech................. 00:E0:85
Internet Initiative Japan ...... 00:E0:4D Cybex Comp Prod................. 00:E0:86
Lecroy ......................... 00:E0:87 Seiwa Elec Mfg.................. 00:E0:C0
LTX ............................ 00:E0:88 Memorex Telex Japan............. 00:E0:C1
Ion Net ........................ 00:E0:89 Necsy........................... 00:E0:C2
GEC Avery ...................... 00:E0:8A Sakai Sys Dev................... 00:E0:C3
QLogic ......................... 00:E0:8B Horner Elec..................... 00:E0:C4
Neoparadigm Labs ............... 00:E0:8C Bcom Elec....................... 00:E0:C5
Pressure Sys ................... 00:E0:8D Link2it......................... 00:E0:C6
Utstarcom ...................... 00:E0:8E Eurotech........................ 00:E0:C7
Cisco .......................... 00:E0:8F Virtual Access.................. 00:E0:C8
Beckman Lab Auto Div ........... 00:E0:90 Automatedlogic.................. 00:E0:C9
Lg Elec ........................ 00:E0:91 Best Data Prod.................. 00:E0:CA
Admtek ......................... 00:E0:92 Reson........................... 00:E0:CB
Ackfin Net ..................... 00:E0:93 Hero Sys........................ 00:E0:CC
Osai Srl ....................... 00:E0:94 Sensis.......................... 00:E0:CD
Adv-Vision Tech ................ 00:E0:95 Arn............................. 00:E0:CE
Shimadzu ....................... 00:E0:96 Integrated Dev.................. 00:E0:CF
Carrier Access ................. 00:E0:97 Netspeed........................ 00:E0:D0
Abocom Sys ..................... 00:E0:98 Telsis.......................... 00:E0:D1
Samson ......................... 00:E0:99 Versanet Comm................... 00:E0:D2
Positron Ind ................... 00:E0:9A Datentechnik.................... 00:E0:D3
Engage Net ..................... 00:E0:9B Excellent Comp.................. 00:E0:D4
Mii ............................ 00:E0:9C Arcxel Tech..................... 00:E0:D5
Sarnoff ........................ 00:E0:9D Comp & Comm................. 00:E0:D6
Quantum ........................ 00:E0:9E Sunshine Elec................... 00:E0:D7
Pixel Vision ................... 00:E0:9F Lanbit Comp..................... 00:E0:D8
Wiltron ........................ 00:E0:A0 Tazmo........................... 00:E0:D9
Hima Paul Hildebrandt .......... 00:E0:A1 Assured Access.................. 00:E0:DA
Microslate ..................... 00:E0:A2 Viavideo Comm................... 00:E0:DB
Cisco .......................... 00:E0:A3 Nexware......................... 00:E0:DC
Esaote ......................... 00:E0:A4 Zenith Elec..................... 00:E0:DD
Comcore Semi ................... 00:E0:A5 Datax Nv........................ 00:E0:DE
Telogy Net ..................... 00:E0:A6 KE Kommunikations-elec.......... 00:E0:DF
IPC Info Sys ................... 00:E0:A7 Si Elec......................... 00:E0:E0
SAT Aus ........................ 00:E0:A8 G2 Net.......................... 00:E0:E1
Funai Elec ..................... 00:E0:A9 Innova.......................... 00:E0:E2
Electrosonic ................... 00:E0:AA SK-Elektronik................... 00:E0:E3
Dimat .......................... 00:E0:AB Fanuc Robotics NA............... 00:E0:E4
Midsco ......................... 00:E0:AC Cinco Net....................... 00:E0:E5
Ees Tech ....................... 00:E0:AD Incaa Datacom................... 00:E0:E6
Xaqti .......................... 00:E0:AE Raytheon E-Sys.................. 00:E0:E7
General Dynamics Info .......... 00:E0:AF Gretacoder Data Sys............. 00:E0:E8
Cisco .......................... 00:E0:B0 Data Labs....................... 00:E0:E9
Packet Engines ................. 00:E0:B1 Innovat Comm.................... 00:E0:EA
Telmax Comm .................... 00:E0:B2 Digicom Sys..................... 00:E0:EB
Etherwan Sys ................... 00:E0:B3 Celestica....................... 00:E0:EC
Techno Scope ................... 00:E0:B4 Silicom......................... 00:E0:ED
Ardent Comm .................... 00:E0:B5 Marel Hf........................ 00:E0:EE
Entrada Net .................... 00:E0:B6 Dionex.......................... 00:E0:EF
Pi Group ....................... 00:E0:B7 Abler Tech...................... 00:E0:F0
Gateway 2000 ................... 00:E0:B8 That Corp....................... 00:E0:F1
Byas Sys ....................... 00:E0:B9 Arlotto Comnet.................. 00:E0:F2
Berghof Auto ................... 00:E0:BA Websprint Comm.................. 00:E0:F3
NBX ............................ 00:E0:BB Inside Tech..................... 00:E0:F4
Symon Comm ..................... 00:E0:BC Teles........................... 00:E0:F5
Interface Sys .................. 00:E0:BD Decision Europe................. 00:E0:F6
Genroco Intl ................... 00:E0:BE Cisco........................... 00:E0:F7
Torrent Net .................... 00:E0:BF Diana Ctl....................... 00:E0:F8
Cisco .......................... 00:E0:F9 Pirelli Focom Net............... 08:00:18
Trl Tech ....................... 00:E0:FA General Elec.................... 08:00:19
Leightronix .................... 00:E0:FB Tiara/10net..................... 08:00:1A
Huawei Tech .................... 00:E0:FC Data General.................... 08:00:1B
A-Trend Tech ................... 00:E0:FD KDD-Kokusai Debnsin Denwa....... 08:00:1C
Cisco .......................... 00:E0:FE Able Comm....................... 08:00:1D
Security Dyn Tech .............. 00:E0:FF Apollo Comp..................... 08:00:1E
Nixdorf Comp ................... 00:E6:D3 Sharp........................... 08:00:1F
Mcast Cisco Discovery . 01:00:0C:CC:CC:CC Sun Micro....................... 08:00:20
McastCabletron ................. 01:00:1D 3M ............................. 08:00:21
McastDoD RFC 1112 .............. 01:00:5E NBI ............................ 08:00:22
McastSynoptics ................. 01:00:81 Matsuhita Graphic Comm Sys...... 08:00:23
McastKalpana ................... 01:80:24 10net Comm...................... 08:00:24
McastOSI/802.1 ................. 01:80:C2 Control Data.................... 08:00:25
Mcast ANSI FDDI ....... 01:80:C2:00:01:00 Norsk Data...................... 08:00:26
Mcast ANSI FDDI ....... 01:80:C2:00:01:10 Cadmus Comp Sys................. 08:00:27
Mcast ANSI FDDI ....... 01:80:C2:00:01:20 Texas Inst...................... 08:00:28
Racal-Datacom .................. 02:07:01 Megatek......................... 08:00:29
Perq Sys ....................... 02:1C:7C Mosaic Tech..................... 08:00:2A
3Com ........................... 02:60:60 DEC ............................ 08:00:2B
Logic Repl Tech ................ 02:60:86 DEC ..................... 08:00:2B:20:*:*
3Com ........................... 02:60:8C DEC ................ 08:00:2B:(23-2F):*:*
Racal-Datacom .................. 02:70:01 DEC VAXFT................ 08:00:2B:E0:*:*
M/A-Com ........................ 02:70:B0 DEC VAXFT................ 08:00:2B:F0:*:*
Data Recall .................... 02:70:B3 Britton Lee..................... 08:00:2C
Cardiac Rec .................... 02:9D:8E Lan-Tec......................... 08:00:2D
Olivetti ....................... 02:AA:3C Metaphor Comp Sys............... 08:00:2E
Octothorpe ..................... 02:BB:01 Prime Comp...................... 08:00:2F
3Com ........................... 02:C0:8C Royal Melbourne Inst Tech....... 08:00:30
Comm Mach ...................... 02:CF:1C Little Machines................. 08:00:31
Nixdorf Comp ................... 02:E6:D3 Tigan........................... 08:00:32
OS/2CM ................ 03:00:00:00:00:10 Bausch & Lomb............... 08:00:33
OS/2CM ................ 03:00:00:00:00:40 Filenet......................... 08:00:34
Xmit Comp Net .................. 04:0A:E0 Microfive....................... 08:00:35
Triumph-adler .................. 04:E0:C4 Intergraph...................... 08:00:36
Computervision ................. 08:00:01 Fuji-xerox...................... 08:00:37
Bridge Comm .................... 08:00:02 Cii Honeywell Bull.............. 08:00:38
Adv Comp Comm .................. 08:00:03 Spider Sys...................... 08:00:39
Cromemco ....................... 08:00:04 Orcatech........................ 08:00:3A
Symbolics ...................... 08:00:05 Torus Sys....................... 08:00:3B
Siemens ........................ 08:00:06 Schlumberger Well Serv.......... 08:00:3C
Apple .......................... 08:00:07 Cadnetixs....................... 08:00:3D
Bolt Beranek & Newman ...... 08:00:08 Codex........................... 08:00:3E
Hewlett Packard ................ 08:00:09 Fred Koschara Ent............... 08:00:3F
Nestar Sys ..................... 08:00:0A Ferranti Comp Sys............... 08:00:40
Unisys ......................... 08:00:0B Racal-Milgo Info Sys............ 08:00:41
Miklyn Dev ..................... 08:00:0C Japan Macnics................... 08:00:42
International Comp ............. 08:00:0D Pixel Comp...................... 08:00:43
NCR ............................ 08:00:0E David Sys....................... 08:00:44
Mitel .......................... 08:00:0F Concurrent Comp................. 08:00:45
Tektronix ...................... 08:00:11 Sony............................ 08:00:46
Bell Atlantic Integ Sys ........ 08:00:12 Sequent Comp Sys................ 08:00:47
Exxon .......................... 08:00:13 Eurotherm Gauging Sys........... 08:00:48
Excelan ........................ 08:00:14 Univation....................... 08:00:49
STC Bus Sys .................... 08:00:15 Banyan Sys...................... 08:00:4A
Barrister Info Sys ............. 08:00:16 Planning Res.................... 08:00:4B
National Semi .................. 08:00:17 Hydra Comp Sys.................. 08:00:4C
Corvus Sys ..................... 08:00:4D Imagen.......................... 08:00:86
3Com ........................... 08:00:4E Xyplex.......................... 08:00:87
Cygnet Sys ..................... 08:00:4F Mcdata.......................... 08:00:88
Daisy Sys ...................... 08:00:50 Kinetics........................ 08:00:89
Experdata ...................... 08:00:51 Performance Tech................ 08:00:8A
Insystec ....................... 08:00:52 Pyramid Tech.................... 08:00:8B
Middle East Tech Univ .......... 08:00:53 Network Res..................... 08:00:8C
Stanford Telecomm .............. 08:00:55 Xyvision........................ 08:00:8D
Stanford Linear Accel .......... 08:00:56 Tandem Comp..................... 08:00:8E
Evans & Sutherland ......... 08:00:57 Chipcom......................... 08:00:8F
Systems Concepts ............... 08:00:58 Sonoma Sys...................... 08:00:90
A/S Mycron ..................... 08:00:59 Ak-Nord Edv Vertriebsges........ 08:BB:CC
IBM ............................ 08:00:5A McastVitaLink................... 09:00:02
VTA Tech ....................... 08:00:5B McastHPProbe........... 09:00:09:00:00:01
Four Phase Sys ................. 08:00:5C McastHPDTC............. 09:00:09:00:00:05
Gould .......................... 08:00:5D McastICL........................ 09:00:0D
Counterpoint Comp .............. 08:00:5E McastApollo DOMAIN.............. 09:00:1E
Saber Tech ..................... 08:00:5F McastVitaLink................... 09:00:26
Industrial Net ................. 08:00:60 Mcast DEC LAST........... 09:00:2B:04:*:*
Jarogate ....................... 08:00:61 McastSpider Sys................. 09:00:39
General Dynamics ............... 08:00:62 McstBICC........................ 09:00:4C
Plessey ........................ 08:00:63 McastNovell/BICC................ 09:00:4E
Autophon ....................... 08:00:64 McastStanford................... 09:00:56
Genrad ......................... 08:00:65 McastRetix...................... 09:00:77
Agfa ........................... 08:00:66 McastVitaLink................... 09:00:7C
Comdesign ...................... 08:00:67 McastXyplex..................... 09:00:87
Ridge Comp ..................... 08:00:68 McastHewlett-Packard............ 0D:1E:15
Silicon Graphics ............... 08:00:69 IBM............................. 10:00:5A
ATT Bell Lab ................... 08:00:6A DEC............................. 10:00:5D
Accel Tech ..................... 08:00:6B National Semi................... 10:00:E8
Suntek Tech Intl ............... 08:00:6C Mcast UB-Boot.......... 10:DD:00:FF:FF:FF
Whitechapel Comp Works ......... 08:00:6D Mcast UB-Span.......... 10:DD:01:00:00:00
Masscomp ....................... 08:00:6E Microsoft Dialup................ 44:45:53
Philips Apeldoorn .............. 08:00:6F Novell.......................... 52:54:4C
Mitsubishi Elec ................ 08:00:70 ATT Bell Lab.................... 80:00:10
Matra .......................... 08:00:71 Verilink........................ A0:6A:00
Xerox Corp Univ Grant .......... 08:00:72 DEC............................. AA:00:00
Tecmar ......................... 08:00:73 DEC............................. AA:00:01
Casio Comp ..................... 08:00:74 DEC............................. AA:00:02
Dansk Data Elec ................ 08:00:75 DEC............................. AA:00:03
PC Lan Tech .................... 08:00:76 DEC UNA.................. AA:00:03:00:*:*
TSL Comm ....................... 08:00:77 DEC PROM AA.............. AA:00:03:01:*:*
Accell ......................... 08:00:78 DEC Misc................. AA:00:03:02:*:*
Droid Works .................... 08:00:79 DEC NI20................. AA:00:03:03:*:*
Indata ......................... 08:00:7A DEC............................. AA:00:04
Sanyo Elec ..................... 08:00:7B DEC PhIV................. AA:00:04:00:*:*
Vitalink Comm .................. 08:00:7C DEC Old LAT............ AB:00:03:00:00:00
Amalgamated Wireless ........... 08:00:7E DEC Multicast............ AB:00:04:00:*:*
Carnegie-Mellon Univ ........... 08:00:7F DECnet LAVC.............. AB:00:04:01:*:*
Aes Data ....................... 08:00:80 Loopback............... CF:00:00:00:00:00
Astech ......................... 08:00:81 McastLANtastic.................. FF:FF:00
Veritas Soft ................... 08:00:82 McastLANtastic.................. FF:FF:01
Seiko Inst & Elec .......... 08:00:83
Tomen Elec ..................... 08:00:84
Elxsi .......................... 08:00:85
A P P E N D I X D
Networking Parts Display
This appendix contains photographs of Philips Nuclear networking-related parts that you
would typically find onsite or have to order from the Field Service Parts department. They are shown
either in their open or shipped condition, where appropriate.
Some of these parts are very old and are shown for historical reasons only. Many being
obsolete, they can no longer be ordered, but it is likely you could run across them in the field. This
appendix might assist you in identifying such a rare find.
2141-0747 CBLE,BNC/BNC,RG58 50 OHM 5 FT 2141-1001 CBLE,ETHERNET,15P,M-F 10 FT
2150-5616 CBLE,CAT5 ETHER,36IN STRAIGHT 2150-5619 CBLE,CAT5 ETHER,48IN,CROSSOVER
2152-3318 KIT,ATLAS UNIV NETWORK UPGRADE 2152-3329 FSKIT, LINKSYS PNP SW UPGD
2152-3329 LINKSYS PNP 5200-3558 NON-PNP

(LEFT) (RIGHT)
Note: PNP has no chips in circled area and fully populated ISA connector contacts while the
Non-PNP does have chips in the circled area and is missing the back half of the ISA contacts.
5090-1157 BNC"T" UG274A/U AMPH 31-208 5090-3001 BNC UG914/U AMPH 31-219
5090-9251 TERMINATOR CAP 50 OHM 46650-51 5090-9643 CONN,MODJACK COUPLER 8PIN
5101-8448 HUB,EHTERNET,STB,10/100MPS,24P
(FRONT VIEW) (BACK VIEW)
5200-1196 CONTROLLER CARD,ETHERNET/AT 5200-1785 PASY,ETHERNET XCVR, THIN-NET
5200-1785 (SAMPLE DEPT OR IMAGE ENET NETWORK) 5200-1624 PASY,ETHERNET XCVR (ST500) THICK
5200-1887 PASY,THINNET REPEATER MR2000C (OLD VERSION)

(FRONT) (BACK)
5200-1887 PASY,THINNET REPEATER (NEW VERSION)

(FRONT) (BACK)
5200-3001 PASY,TWISTED PAIR-THIN ADAPTER
(FRONT) (BACK)
5200-3008 MILAN 4-PORT HUB W/10BASE2 BNC

(FRONT) (BACK)
5200-3009 PASY,MILAN THIN TWIST CONVERTER

(FRONT) (BACK)
5200-3011 PASY,MILAN MICRO MAU XCVR
(FRONT) (BACK)
5200-3282 ALLI TELESYN RJ45 AT-210TS

(FRONT) (BACK)
5200-3224 100 BT ETHER CARD,MCD,ULT1,PEG 5200-3310 PASY,SBUS SCSI CARD X1053A
5200-3509 PASY,10MB 8 PORT HUB,TWST PAIR
(FRONT) (BACK)
5200-3541 BD,ETHERNET,PCI,10/100,U60/10
(FRONT) (BACK)
5200-3558 LINKSYS ETHER LAN CARD,W/PROMS 5200-3352 SIIG ETHERNET (OBSOLETE)
5200-3657 SW,ETHERNET,FAST,10/100,8-PORT
(FRONT) (BACK)
5200-3679 SW,ETHERNET,UNMGD,10/100,24P
(FRONT) (BACK)
5200-3680 ROUTER,ETHERNET,10/100,2NIC,2P
(FRONT) (BACK)
5200-3681 SW,ETHERNET,10/100,MNGBLE,24P
(FRONT) (BACK)
5200-3765 PASY,CABLE/DSL ROUTER,8PORT SW
A P P E N D I X E
Filtering-Bridge Access-List Format
The format of the Access-List statements for our complex Filtering-Bridge

configuration can be quite intricate and involved. Through this annotated example we
hope to illustrate the types of statements required for the different network components
and explanations of the fields that make up those statements.
Each target within the local subnet, between the filtering-bridge and the
1 encapsulating router, requires two statements to handle the “regular” and ARP
traffic. The Source MAC Address will be that of the target itself.
Each target beyond the encapsulating router requires one statement to allow for
2 the “regular” traffic from that target. The Source MAC Address will always be
that of the interface on our side of the encapsulating router.
Each interface of the encapsulating router requires a statement to allow traffic

3 directly from the IP address of those interfaces. This allows them their ping
responses to get through to us.
Each Pegasys will require 3 statements. One for incoming ARP requests and
4 two to handle outgoing “regular” and ARP traffic.

Networking Reference Guide

Uploaded by

Copyright:

Available Formats

You might also like

Networking Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Networking Reference Guide

Uploaded by

Copyright:

Available Formats

Networking Guide for

Nuclear Medicine Products

Philips Medical Systems

About This Manual

Before starting, you should have the following computer media:

Special Notes / Conventions

Chapter 1: Network Configuration Overview............................................................................ 19

Chapter 3: Network Hardware Overview and Installation...................................................... 119

Chapter 4: Network Peripherals Hardware and Software ...................................................... 237

Chapter 5: ADAC Network Troubleshooting .......................................................................... 301

Chapter 6: Network File Structures......................................................................................... 379

Chapter 7: File Editors ............................................................................................................. 433

Decimal / Hexadecimal / Binary Conversion Table ................................................................. 441

Glossary of Networking Terms ................................................................................................ 443

Organizationally Unique Identifiers (OUI)................................................................................ 509

Networking Parts Display ......................................................................................................... 553

Filtering-Bridge Access-List Format........................................................................................ 563

This chapter covers planning and implementation of different types of network

I. Information for Using this Chapter

Note: A more comprehensive glossary can be found in Appendix B of this manual.

OSI REFERENCE MODEL

EXAMPLES OF COMMONLY KNOWN PROTOCOLS

• Application - programs & data presentation

PACKETS ON THE WIRE

PACKET (OR DATA FRAME) FORMAT

Preamble Destination Source Length “Information” FCS checksum

SITE SURVEY HIGHLIGHTS

CUSTOM NAMING SUGGESTIONS

Pegasys Networking General Guidelines

• A Pegasys network, or cluster, consists of a Master (NIS, DB, shared-directories) and a

REASONS TO CUSTOM NETWORK

FUNDAMENTAL SITE INFORMATION

CABLE RUNS AND EQUIPMENT

PLANNING AND ASSISTANCE FROM THE CUSTOM NETWORKING GROUP

CUSTOM NETWORK GUIDELINES

Standalone PegUltra/Atlas Concepts

2. In the above configuration, the Atlas interfaces to a Philips/ADAC camera. An Atlas

Standalone PegUltra/Atlas Networking Guide

2. Do not install any peripheral network devices or systems prior to running

3. Follow the instructions in the 9202-0142* (FSM, PEGULT SW INSTAL/CONFIG )

7. Install any optional software and peripherals on this standalone network.

Networked PegUltra and Atlas Systems, Concepts

2. In the above configuration, the Atlas interfaces to a Philips/ADAC camera. An Atlas

4. This Networked cluster configuration can support:

Networking Guide - Networked PegUltra/Atlas Systems

Item #19: RJ-45 Twisted Pair coupler (5090-9643)

Twisted Pair Mixed Environment Network Concepts

Twisted Pair Mixed Environment Networking Guide

REMEMBER: The PegX must be configured as the network master.

11. Repeat Step 10 for each Atlas being added.

Item #3: Thinnet to 15 pin AUI Transceiver (5200-3011).

Item #8: 15 pin AUI cable (2141-10xx).

Item #23: Thinnet-Twisted Pair Transceiver (5200-3001).

Thinnet-Only Mixed Environment Networking Concepts

3. In a mixed (PegX and Ultra-Atlas) environment, a Peg X computer must be the

Thinnet-Only Mixed Environment Networking Guide

Item #1: 10/100 Switch - 24 port (5200-3679) or 8 port (5200-3657)

Item #4: 50 ohm RG-58 Coaxial cable (2141-07xx)

Item #10: 10/100bT Crossover Cable (2150-561x)