Sun Microsystems 1.0 Adapter User Manual

SunFDDI/P™1.0AdapterUser’sGuide

Sun Microsystems Computer Company

A Sun Microsystems, Inc. Business 2550 Garcia Avenue Mountain View, CA 94043 USA 415 960-1300 fax 415 969-9131

Part No.: 805-0809-10 Revision A, May 1997

Copyright 1997 Sun Microsystems,Inc. 2550 Garcia Avenue,Mountain View, California 94043-1100U.S.A. All rights reserved.This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution,

and decompilation. No part of this productor document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.

Portions of this productmay be derived from the UNIX®system and fromthe Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registeredtrademark in the United States and in other countries and is exclusively licensed by X/Open Company Ltd. Third-partysoftware, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers.

RESTRICTEDRIGHTSLEGEND: Use, duplication, or disclosure by the government issubjectto restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Softwareclause at DFARS 252.227-7013 and FAR52.227-19.

Sun, Sun Microsystems,the Sun logo, Solaris, SunOS, SunFDDI/P,and SunNet Manager are trademarks or registeredtrademarks of Sun Microsystems,Inc. in the United States and in other countries. All SPARCtrademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and in other countries. Productsbearing SPARCtrademarks are based upon an architecturedeveloped by Sun Microsystems, Inc. Netware®is a registeredtrademark of Novell, Inc. in the United States and other countries.

The OPEN LOOK®and Sun™ Graphical User Interfaces weredeveloped by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges thepioneeringefforts of Xerox Corporation in researchingand developing the concept of visual or graphical user interfaces for the computer industry.Sun holds a nonexclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.

X WindowSystem is a trademark of X Consortium, Inc. THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,

BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

Copyright 1997 Sun Microsystems,Inc., 2550 Garcia Avenue,Mountain View, Californie 94043-1100U.S.A. Tous droitsréservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignentl’utilisation, la copie

et la décompilation. Aucune partie de ce produitou de sa documentation associée nepeut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’ilyena.

Des parties de ce produitpourront être derivées du système UNIX®et du système Berkeley 4.3 BSD licencié par l’Université de Californie. UNIX est unemarqueenregistrée aux Etats-Unis et dans d’autres pays, et licenciée exclusivement par X/Open CompanyLtd.Lelogiciel détenu par des tiers, et qui comprendla technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Sun, Sun Microsystems,le logo Sun, Solaris, SunOS, SunFDDI/P,et SunNet Manager sont des marques déposées ou enregistrées de Sun Microsystems,Inc. aux Etats-Unis et dans d’autres pays. Toutesles marques SPARC,utilisées sous licence, sont des marques déposées ou enregistréesde SPARCInternational, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARCsont basés sur une architecturedéveloppée par Sun Microsystems, Inc. Netware®est une marqueenregistrée de Novell, Inc. aux Etats-Unis et dans d’autres pays.

Les utilisateurs d’interfaces graphiques OPEN LOOK®et Sun™ ont été développés de Sun Microsystems,Inc. pour ses utilisateurs et licenciés. Sun reconnaîtles efforts de pionniers de Xerox Corporation pour la rechercheet le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xeroxsur l’interface d’utilisation graphique, cette licence couvrant aussi les licenciés de Sun qui mettent en place les utilisateurs d’interfaces graphiques OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

Le système X Windowest un produit du X Consortium, Inc. CETTE PUBLICATION EST FOURNIE "EN L’ETAT" SANS GARANTIE D’AUCUNE SORTE, NI EXPRESSE NI IMPLICITE, Y COMPRIS, ET

SANS QUE CETTE LISTE NE SOIT LIMITATIVE, DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DES PRODUITS A REPONDRE A UNE UTILISATIONPARTICULIERE OU LE FAITQU’ILS NE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS.

Please

Recycle

Regulatory Compliance Statements

Your Sun product is marked to indicate its compliance class:

• Federal Communications Commission (FCC) — USA

• Department of Communications (DOC) — Canada

• Voluntary Control Council for Interference (VCCI) — Japan

Please read the appropriate section that corresponds to the marking on your Sun product before attempting to install the product.

FCC Class ANotice

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.

These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interferenceto radiocommunications. Operationof thisequipment in a residential area is likelyto cause harmful interference in which case the user will be required to correct the interference at his own expense.

Shielded Cables: Connections between the workstation and peripherals must be made using shielded cables in order to maintain compliance with FCC radio frequency emission limits. Networking connections can be made using unshielded twisted-pair (UTP) cables.

Modifications: Any modifications made to this device that are not approved by Sun Microsystems, Inc. may void the authority granted to the user by the FCC to operate this equipment.

FCC Class BNotice

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules.

These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/television technician for help.

Modifications: Any modifications made to this device that are not approved by Sun Microsystems, Inc. may void the authority granted to the user by the FCC to operate this equipment.

DOC Class ANotice-Avis DOC, ClasseA

This Class A digital apparatus meets all of requirements the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

DOC Class BNotice-Avis DOC, ClasseB

This Class B digital apparatus meets all of requirements the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

Declaration of Conformity

Compliance ID: PCI-S10-100

Product Name: SunFDDI/P SAS Adapter

This equipment complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1) This equipment may not cause harmful interference and 2) This equipment must accept any interference that may cause undesired operation.

In addition this equipment complies with the following requirements of the EMC Directive 89/336/EEC and Low Voltage Directive 73/23/EEC;

EMC: EN55022 / CISPR22 (1991) Class B

EN50082-1 IEC801-2 (1991) 4 kV (Direct), 8 kV (Air)

IEC801-3 (1984) 3 V/m IEC801-4 (1988) 1.0 kV Power Lines, 0.5 kV Signal Lines

EN61000-3-2/IEC1000-3-2(1994) Pass (Class D)

Supplementary Information:

This product was tested and complies with all the requirements for the CE Mark.

_________/ S /_______________ ______/ S /_________________ Dennis P. Symanski DATE Stephen McGoldrick DATE Manager, Product Compliance Quality Assurance Manager

Sun Microsystems Computer Company Sun Microsystems Limited 2550 Garcia Avenue, M/S UMPK15-102 Springﬁeld, Linlithgow Mt. View, CA 94043, USA West Lothian, EH49 7LR Tel: 415-786-3255 Scotland, United Kingdom Fax: 415-786-3723 Tel: 0506 670000

Fax: 0506 760011

Declaration of Conformity

Compliance ID: PCI-D10-100

Product Name: SunFDDI/P DAS Adapter

In addition this equipment complies with the following requirements of the EMC Directive 89/336/EEC and Low Voltage Directive 73/23/EEC;

EMC: EN55022 / CISPR22 (1991) Class B

EN50082-1 IEC801-2 (1991) 4 kV (Direct), 8 kV (Air)

IEC801-3 (1984) 3 V/m IEC801-4 (1988) 1.0 kV Power Lines, 0.5 kV Signal Lines

EN61000-3-2/IEC1000-3-2(1994) Pass (Class D)

Supplementary Information:

This product was tested and complies with all the requirements for the CE Mark.

_________/ S /_______________ ______/ S /_________________ Dennis P. Symanski DATE Stephen McGoldrick DATE Manager, Product Compliance Quality Assurance Manager

Fax: 0506 760011

Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Part 1 —Installing and Configuring SunFDDI/P

1. SunFDDI/P Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Feature Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

FDDI Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Device Instances and Device Names. . . . . . . . . . . . . . . . . . . . . . 4

Installation Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing SunFDDI/P Adapter Cards. . . . . . . . . . . . . . . . . . . . . 5

Connecting Fiber Optic Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . 5

▼ To Connect the Fiber Optic Cable . . . . . . . . . . . . . . . . . . 6

MIC-to-MIC Coupler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Cleaning the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . 7

▼ To Clean the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . 8

Link Status Indicator (Diagnostic LED) . . . . . . . . . . . . . . . . . . . 9

vii

3. Installing SunFDDI/P Software . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Declaring IP Addresses for SunFDDI/P. . . . . . . . . . . . . . . . . . . 12

Installing and Configuring SunFDDI/P . . . . . . . . . . . . . . . . . . . 13

▼ To Load and Mount the CD-ROM. . . . . . . . . . . . . . . . . . 13

▼ To Install SunFDDI/P Using pkgadd. . . . . . . . . . . . . . . 13

▼ To Finish the Installation . . . . . . . . . . . . . . . . . . . . . . . . . 17

▼ To Check the Installation . . . . . . . . . . . . . . . . . . . . . . . . . 18

▼ Unloading Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing SunNet Manager Agents for SunFDDI/P . . . . . . . . . 20

▼ To Use pf_install_agents . . . . . . . . . . . . . . . . . . . . . 20

Removing SunFDDI/P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

▼ To Remove SunFDDI/P . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4. Improving Network Performance . . . . . . . . . . . . . . . . . . . . . . . 23

High Performance FDDI Networks. . . . . . . . . . . . . . . . . . . . . . . 24

Ring Latency Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Data Throughput Improvement. . . . . . . . . . . . . . . . . . . . . . . . . . 25

Send and Receive Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Performance Across Bridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Target Token Rotation Time (TTRT). . . . . . . . . . . . . . . . . . . . . . . 26

Improving Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Changing the High and Low Water Marks. . . . . . . . . . . . . . 27

▼ To Tune the High Water Mark . . . . . . . . . . . . . . . . . . . . . 27

▼ To Tune the Low Water Mark. . . . . . . . . . . . . . . . . . . . . . 28

viii SunFDDI/P 1.0 Adapter User’sGuide—May 1997

Tuning the High and Low Water Marks at Boot Time. . . . . 29

Tuning the Socket Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

MTU Path Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

▼ To Tune the Maximum Transfer Unit (MTU) . . . . . . . . . 30

▼ To Disable MTU Path Discovery . . . . . . . . . . . . . . . . . . . 31

▼ To Tune the Target Token Rotation Time (TTRT). . . . . . 31

5. Troubleshooting and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . 33

Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

▼ To Check the Connection to the Station . . . . . . . . . . . . . 34

▼ To Check the Connections Between Stations . . . . . . . . . 34

▼ To Check the Link Status Indicator. . . . . . . . . . . . . . . . . 34

Checking the MAC Address. . . . . . . . . . . . . . . . . . . . . . . . . . 35

▼ To Check the SunFDDI/P Driver. . . . . . . . . . . . . . . . . . . 36

▼ To Check the IP Addresses. . . . . . . . . . . . . . . . . . . . . . . . 36

▼ To Check the IP Routing. . . . . . . . . . . . . . . . . . . . . . . . . . 37

▼ To Check the Protocol Statistics. . . . . . . . . . . . . . . . . . . . 37

▼ To Check the SMT Traffic . . . . . . . . . . . . . . . . . . . . . . . . . 38

Solving Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Running the Hardware Self-Test Program . . . . . . . . . . . . . . . . . 44

▼ To Run the Hardware Self-Test . . . . . . . . . . . . . . . . . . . . 44

Loading the Device Driver Manually . . . . . . . . . . . . . . . . . . . . . 45

▼ To Configure and Load the Device Driver . . . . . . . . . . . 45

Part 2 —Planning and Implementing SunFDDI Networks

6. FDDI Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents ix

FDDI Network Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Physical Medium Dependent (PMD) Layer . . . . . . . . . . . . . 51

Physical (PHY) Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Media Access Control (MAC) Layer . . . . . . . . . . . . . . . . . . . 52

Station Management (SMT) Layer. . . . . . . . . . . . . . . . . . . . . 52

Communication Between FDDI Layers . . . . . . . . . . . . . . . . 53

FDDI Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

FDDI Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

FDDI Concentrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

FDDI Failure Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Station Wrapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Optical Bypass Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

FDDI Ring Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Unrestricted Asynchronous Transmission . . . . . . . . . . . . . . 65

FDDI Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

7. FDDI Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Basic Dual-Ring Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Standalone Concentrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Concentrators with Dual-Homing. . . . . . . . . . . . . . . . . . . . . . . . 74

Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

x SunFDDI/P 1.0 Adapter User’sGuide—May 1997

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Tree of Concentrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Ring of Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Mixed FDDI/Ethernet Networks . . . . . . . . . . . . . . . . . . . . . . . . . 79

FDDI/Ethernet IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

A Tree of Concentrators in an Ethernet Network . . . . . . . . 80

A Ring of Trees in an Ethernet Network. . . . . . . . . . . . . . . . 81

Routes in Mixed FDDI/Ethernet Networks. . . . . . . . . . . . . 81

8. Using the SunFDDI

Network Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Changing the Default MAC Address (pf_macid) . . . . . . . . . 86

▼ To Change the Default MAC Address with pf_macid 86

Displaying SunFDDI/P Statistics (pf_stat). . . . . . . . . . . . . . 87

Displaying Local Interface Statistics . . . . . . . . . . . . . . . . . . . 88

Displaying Statistics from Neighboring Stations . . . . . . . . . 94

Monitoring SMT Frames (pf_smtmon). . . . . . . . . . . . . . . . . . . 98

SMT Frame Classes and Types. . . . . . . . . . . . . . . . . . . . . . . . 100

Filtering Output from pf_smtmon . . . . . . . . . . . . . . . . . . . . 101

9. Managing FDDI Stations

Using SunNet Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Installing the SunNet Manager Agents. . . . . . . . . . . . . . . . . . . . 104

Contents xi

▼ To Install the Standard SNM Agents on a Client. . . . . . 104

▼ To Install the FDDI Schemas on a Client . . . . . . . . . . . . 105

Installing the FDDI Schemas on the Console . . . . . . . . . . . . 106

▼ To Share pf_install_agents From a Client . . . . . . . 107

Managing FDDI Networks with SunNet Manager . . . . . . . . . . 109

▼ To Set Up the SunNet Manager Console. . . . . . . . . . . . . 109

Using the SunFDDI/P Local Agent (pf_fddi) . . . . . . . . . 110

▼ To Use the SunFDDI/P Proxy Agent (pf_fddismt7_2)112

Interpreting Traps and Errors . . . . . . . . . . . . . . . . . . . . . . . . . 114

MAC Address Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

10. Developing Applications that

Run over SunFDDI/P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Developing Applications with DLPI . . . . . . . . . . . . . . . . . . . . . . 120

DLPI Connectionless Service Primitives. . . . . . . . . . . . . . . . 121

DLPI Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

11. Setting Up Servers

and Diskless Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Setting Up a Server and Diskless Clients . . . . . . . . . . . . . . . . . . 126

▼ To Set Up a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

▼ To Introduce Diskless Clients to a Server. . . . . . . . . . . . 127

▼ To Update the NIS Server. . . . . . . . . . . . . . . . . . . . . . . . . 132

Installing the SunFDDI/P Driver for a Diskless Client . . . 133

Booting a Diskless Client Over SunFDDI/P. . . . . . . . . . . . . . . . 133

▼ To Boot a Diskless Client . . . . . . . . . . . . . . . . . . . . . . . . . 133

A. Frequently Asked Questions About SunFDDI . . . . . . . . . . . . 135

xii SunFDDI/P 1.0 Adapter User’sGuide—May 1997

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Contents xiii

xiv SunFDDI/P 1.0 Adapter User’sGuide—May 1997

Figures

Figure 2-1 Aligning SC-Type Fiber Optic Cable Connectors. . . . . . . . . . . 6

Figure 2-2 Cleaning the End of a Fiber Optic Cable . . . . . . . . . . . . . . . . . . 8

Figure 6-1 FDDI Architectural Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 6-2 Communication Between FDDI Layers . . . . . . . . . . . . . . . . . . . 54

Figure 6-3 Basic FDDI Network Architecture . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 6-4 Single-Attached Station (SAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 6-5 Dual-Attached Station (DAS). . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 6-6 Single-Attached Concentrator (SAC) . . . . . . . . . . . . . . . . . . . . . 58

Figure 6-7 Dual-Attached Concentrator (DAC). . . . . . . . . . . . . . . . . . . . . . 59

Figure 6-8 Isolating a Single Station Failure. . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 6-9 Isolating a Single Cable Failure . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 6-10 Dual-Attached Station in Wrap Mode . . . . . . . . . . . . . . . . . . . . 62

Figure 6-11 Dua-Ring Network Divided by Two Faults . . . . . . . . . . . . . . . 63

Figure 6-12 Optical Bypass Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Figure 6-13 Optical Bypass Switches used in a Network . . . . . . . . . . . . . . . 64

Figure 7-1 Basic Dual-Ring Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 7-2 Basic Dual-Ring Network with Two Faults. . . . . . . . . . . . . . . . 71

Figure 7-3 Standalone Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 7-4 Standalone Concentrator With Dual-Homing . . . . . . . . . . . . . 74

Figure 7-5 Hierarchical Tree of Concentrators. . . . . . . . . . . . . . . . . . . . . . . 76

Figure 7-6 Ring of Trees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 7-7 Basic Mixed FDDI/Ethernet Topology . . . . . . . . . . . . . . . . . . . 80

Figure 7-8 Tree of Concentrators Attached to an Ethernet Network . . . . 80

Figure 7-9 Ring of Trees Attached to an Ethernet Network. . . . . . . . . . . . 81

Figure 7-10 Routing in an FDDI/Ethernet Internetwork . . . . . . . . . . . . . . . 82

Figure 8-1 Normal Sequence of PCM States. . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 9-1 Quick Dump (Local Statistics) . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Figure 9-2 Quick Dump (Neighbor Statistics) . . . . . . . . . . . . . . . . . . . . . . . 111

Figure 9-3 SunFDDI/P Proxy Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Figure 9-4 Specifying the Target Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Figure 9-5 Quick Dump (SMT Frames). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Figure 9-6 Single-Attached Station Disconnected . . . . . . . . . . . . . . . . . . . . 114

Figure 9-7 Single-Attached Station Reconnected. . . . . . . . . . . . . . . . . . . . . 115

Figure 9-8 Dual-Attached Station Halted . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Figure 9-9 Dual-Attached Station Restarted. . . . . . . . . . . . . . . . . . . . . . . . . 116

Figure 10-1 DLPI Access to FDDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Figure 10-2 DLPI Request/Response Negotiation . . . . . . . . . . . . . . . . . . . . 121

Figure 10-3 SunFDDI/P DLSAP Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

xvi SunFDDI/P 1.0 Adapter User’s Guide—May 1997

Tables

Table 5-1 Problems Installing SunFDDI/P. . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 5-2 Problems Running SunFDDI/P. . . . . . . . . . . . . . . . . . . . . . . . . . 40

Table 5-3 Problems Using the SNM Agents for SunFDDI/P. . . . . . . . . . 43

Table 8-1 pf_stat States Under the ECM Heading. . . . . . . . . . . . . . . . . 90

Table 8-2 pf_stat States Under the RMT Heading. . . . . . . . . . . . . . . . . 90

Table 8-3 pf_stat States Under the PCM Heading. . . . . . . . . . . . . . . . . 91

Table 10-1 DL_INFO_REQ Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

xvii

xviii SunFDDI/P 1.0 Adapter User’s Guide—May 1997

Preface

The SunFDDI/P™ 1.0 Adapter User’s Guide describes how to turn your system into an FDDI station attached to an FDDI network. It is intended for experienced network administrators who are familiar with the Solaris 2.5.1 Hardware: 4/97 operating environment. The SunFDDI/P 1.0 Adapter is supported on Sun-4u PCI-based system architectures.

How this Book is Organized

The SunFDDI/P™ 1.0 Adapter User’s Guide is divided into two parts: If you are unfamiliar with FDDI network terminology, or if you are

implementing an FDDI network for the first time, read Part 2 first.

• Part 1 — “Installing and Configuring SunFDDI/P,” describes how to turn your

machine into a SunFDDI/P station. It tells you how to install and configure the SunFDDI/P device driver, and how to tune your FDDI station to get the best performance. It also includes troubleshooting advice to help you detect and resolve problems with your FDDI network.

• Part 2 — “Planning and Implementing SunFDDI Networks,” includes a brief

overview of the FDDI protocols, and describes common FDDI network topologies. It tells you how to use the SunFDDI/P network utilities, how to use a SunNet Manager™ console to manage your SunFDDI/P stations, how to develop applications over SunFDDI/P, and how to boot a diskless station across an FDDI connection.

xix

The connector type has been changed for SunFDDI/P to an SC-type connector. If you are connecting the SunFDDI/P card to a network that has a MIC connector, an SC-MIC converter cable is required.

Part 1 — “Installing and Conﬁguring SunFDDI/P”

Chapter 1, “SunFDDI/P Overview,” describes the SunFDDI/P 1.0 implementation of the FDDI protocols and includes a list of the specifications to which it conforms.

Chapter 2, “Hardware Installation,” tells you where to find detailed instructions on how to install your SunFDDI/P PCI card in your machine and describes how to connect the FDDI cable.

Chapter 3, “Installing SunFDDI/P Software,” describes how to install the SunFDDI/P device driver and utilities on machines running a Solaris™ 2.5.1 Hardware: 97 environment. It includes a description of the post-installation scripts that configure your machine as an FDDI station.

Chapter 4, “Improving Network Performance,” describes the configurable network parameters and provides general advice on how to obtain the best performance from your network.

Chapter 5, “Troubleshooting and Diagnostics,” tells you how to detect and resolve problems with your FDDI network.

Part 2 — “Planning and Implementing SunFDDINetworks”

Chapter 6, “FDDI Network Architecture,” provides an overview of the FDDI network model and describes how FDDI networks operate.

Chapter 7, “FDDI Network Topologies,” describes various pure FDDI network topologies and discusses their relative strengths and weaknesses. It also describes how to implement routing between mixed FDDI and Ethernet networks.

Chapter 8, “Using the SunFDDI Network Utilities,” describes the network utilities delivered with SunFDDI/P and tells you how to use them to recover network statistics.

xx SunFDDI/P 1.0 Adapter User’sGuide—May 1997

UNIX Commands

Chapter 9, “Managing FDDI Stations Using SunNet Manager,” describes how to install the SunNet Manager agents for SunFDDI/P and how to set up the SunNet Manager console to manage them.

Chapter 10, “Developing Applications that Run over SunFDDI/P,” describes how to create applications that run over SunFDDI/P, using the DLPI interface for a Solaris 2.x environment.

Chapter 11, “Setting Up Servers and Diskless Clients,” describes how to set up a server so that you can boot and run diskless clients over an FDDI network.

Appendix A, “Frequently Asked Questions About SunFDDI,” contains a list of common questions and their responses.

This document may not include specific software commands or procedures. Instead, it may name software tasks and refer you to operating system documentation or the handbook that was shipped with your new hardware.

The type of information that you might need to use references for includes:

• Shutting down the system

• Booting the system

• Configuring devices

• Other basic software procedures

See one or more of the following:

• Solaris 2.x Handbook for SMCC Peripherals contains Solaris™ 2.x software

commands.

• Online AnswerBook™ for the complete set of documentation supporting

the Solaris 2.x software environment.

• Other software documentation that you received with your system.

Preface xxi

Typographic Conventions

The following table describes the typographic changes used in this book.

Typeface or Symbol Meaning Example

Shell Prompts

AaBbCc123 The names of commands,

files, and directories; on-screen computer output

AaBbCc123 What you type, contrasted

with on-screen computer output

AaBbCc123 Command-line placeholder:

replace with a real name or value

AaBbCc123 Book titles, new words or

terms, or words to be emphasized

Edit your .login file. Use ls -a to list all files.

machine_name% You have mail.

machine_name% su Password:

To delete a file, type rm filename.

Read Chapter 6 in the User’s Guide. These are called class options. You must be root to do this.

The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.

Shell Prompt

C shell machine_name% C shell superuser machine_name# Bourne shell and Korn shell $ Bourne shell and Korn shell

superuser

xxii SunFDDI/P 1.0 Adapter User’sGuide—May 1997

FeatureSummary

SunFDDI/POverview

Feature Summary page 1 FDDI Conformance page 2

This chapter describes the Sun FDDI (Fiber Distributed Data Interface) implementation of the FDDI protocols, including a list of the ANSI/FDDI standards to which it conforms. See Chapter 6, “FDDI Network Architecture” for more information on FDDI architecture.

The SunFDDI/P 1.0 product is a combination of hardware and software that turns your system into an FDDI station. There are two hardware options:

• SunFDDI/P SAS — single attached station on fiber

• SunFDDI/P DAS — dual attached station on fiber

SunFDDI/P is a high-speed networking product that provides significantly greater bandwidth (up to 10 times) compared to 10-megabit Ethernet networks. It is designed for Sun-4u PCI-based system architectures running Solaris 2.5.1 Hardware: 97.

SunFDDI/P provides the following capabilities:

• Implements FDDI single-attached station (SunFDDI/P) and FDDI

dual-attached station (SunFDDI/P Dual)

• Provides connection to multimode fiber (SunFDDI/P and SunFDDI/P Dual)

networks

• Supports data transfer rates of up to 100 Mbps

• Provides power-up self test and system diagnostic tests

• Provides high reliability and availability through distributed, automatic

recovery (DAS adapter only)

• Supports up to four SunFDDI/P PCI cards installed in one PCI bus and up

to eight SunFDDI/P PCI cards installed in one machine

• Conforms to the 32-bit Peripheral Component Interconnect (PCI)

specification for short form adapter cards

• Supports 33 MHz operating frequency and 5.0 volt I/O signaling

• Supports 62.5/125 micrometer, multimode fiber (MMF)

• Provides SunNet Manager™ agents for the effective management of FDDI

stations and networks from a centralized SunNet Manager console; (requires SunNet Manager 2.2 or later in addition to SunFDDI/P)

• Complies with the ANSI X3T9.5 standard for single-attached LAN fiber

rings and with revision 7.3 of the ANSI/FDDI SMT specification

FDDI Conformance

SunFDDI/P conforms to the following standards and specifications:

• ANSI/FDDI Media Access Control (MAC) X.3.139-1987

• ANSI/FDDI physical sublayer (PHY) X3.148-1988

• ANSI/FDDI physical medium dependent (PMD) X3.166-1990

• ANSI/FDDI Station Management (SMT) X3.299 R7.3 (formally R7.2.99)

• PCI Spec. Rev 2.1 (Part Number 802-2387-02)

2 SunFDDI/P 1.0 Adapter User’sGuide—May 1997

HardwareInstallation

Device Instances and Device Names page 4 Installing SunFDDI/P Adapter Cards page 5 Connecting Fiber Optic Cables page 5 Link Status Indicator (Diagnostic LED) page 9

This chapter tells you where to find step-by-step procedures for installing PCI cards. It describes the convention used to assign device names to SunFDDI/P adapter cards, and tells you how to connect fiber optic cables.

Caution – For your personal safety and to protect your machine, please

observe the following precautions when you install an PCI card in a SPARC™ workstation or server:

Before opening your machine, always ensure that the power switch is off (O position). When the power is off, the green light on the front of the machine is unlit and the fan in the power supply is not running. Always take care to protect your equipment from the effects of static electricity.

A lithium battery is molded into the NVRAM—TOD chip on the main logic board. This battery is not a customer-replaceable part. Do not attempt to disassemble it or recharge it.

Device Instances and Device Names

You can install a SunFDDI/P PCI card in any available master PCI slot. SunFDDI/P supports up to four SunFDDI/P PCI cards installed in one PCI, and up to eight SunFDDI/P PCI cards installed in one machine.

SunFDDI/P 1.0 PCI cards are assigned device names of the form pf<inst>, where the instance number <inst> is determined by the number and relative positions of the cards installed. When you install a SunFDDI/P card in your machine for the first time, it has instance number 0 and a device name pf0.If multiple cards are installed, the device name pf0 is associated with the card in the lowest numbered slot, the device name pf1 is associated with the card in the next highest numbered slot, and so on.

Refer to the hardware installation manual that came with your system for instructions on how to identify the PCI slots in your machine.

Note – For machines running Solaris 2.5.1: If a SunFDDI/P PCI card is moved from its initial slot to a different one, the operating system will find the device in the new slot and assume that it is a new instance of the device. As a result, the operating system will assign the next instance number to it and two devices will appear to be installed in the machine.

Installation Items

Before proceeding with the installation, make sure you have the following items. Contact your sales representative if any of these items are missing.

• SAS or DAS SunFDDI PCI adapter

• FDDI converter cable

• MIC (Media Interface Connector) coupler

• Disposable grounding wrist strap

• CD-ROM containing SunFDDI/P 1.0 Adapter software

• SunFDDI/P 1.0 Adapter User’s Guide

4 SunFDDI/P 1.0 Adapter User’sGuide—May 1997

+ 152 hidden pages