Token-Ring Adapter
Installation and Support
Guide
Abstract
This guide provides step-by-step procedures for installing, replacing and relocating Token-Ring
ServerNet adapters on Compaq NonStop™ Himalaya S-series servers. This guide is intended
for anyone who installs or maintains TRSAs on NonStop™ Himalaya S-series servers.
Product Version
N/A
Supported Releases
This guide supports G06.08 and all subsequent G-series releases until otherwise indicated in a
new edition
Part Number
Published
426955-001
August 2000
Document History
Part Number
Product Version
Published
137174
G05
February 1998
420094-001
G05
December 1998
426955-001
G06.08
August 2000
Ordering Information
For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact
your local sales representative.
Document Disclaimer
Information contained in a manual is subject to change without notice. Please check with your authorized
representative to make sure you have the most recent information.
Export Statement
Export of the information contained in this manual may require authorization from the U.S. Department of
Commerce.
Examples
Examples and sample programs are for illustration only and may not be suited for your particular purpose. The
inclusion of examples and sample programs in the documentation does not warrant, guarantee, or make any
representations regarding the use or the results of the use of any examples or sample programs in any
documentation. You should verify the applicability of any example or sample program before placing the software
into productive use.
U.S. Government Customers
FOR U.S. GOVERNMENT CUSTOMERS REGARDING THIS DOCUMENTATION AND THE ASSOCIATED
SOFTWARE:
These notices shall be marked on any reproduction of this data, in whole or in part.
NOTICE: Notwithstanding any other lease or license that may pertain to, or accompany the delivery of, this
computer software, the rights of the Government regarding its use, reproduction and disclosure are as set forth in
Section 52.227-19 of the FARS Computer Software—Restricted Rights clause.
RESTRICTED RIGHTS NOTICE: Use, duplication, or disclosure by the Government is subject to the
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 52.227-7013.
RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictions
as set forth in paragraph (b)(3)(B) of the rights in Technical Data and Computer Software clause in
DAR 7-104.9(a). This computer software is submitted with “restricted rights.” Use, duplication or disclosure is
subject to the restrictions as set forth in NASA FAR SUP 18-52 227-79 (April 1985) “Commercial Computer
Software—Restricted Rights (April 1985).” If the contract contains the Clause at 18-52 227-74 “Rights in Data
General” then the “Alternate III” clause applies.
U.S. Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule
Contract.
Unpublished — All rights reserved under the Copyright Laws of the United States.
Token-Ring Adapter Installation
and Support Guide
Glossary
Index
Examples
Figures
Tables
What’s New in This Guide vii
Guide Information vii
New and Changed Information vii
About This Guide
ix
Who Should Use This Guide
What’s in This Guide
ix
ix
Where to Get More Information
ix
Your Comments Invited x
Notation Conventions x
1. Introduction to the Token-Ring SeverNet Adapter (TRSA)
Overview of the TRSA
TRSA Features:
1-2
1-2
External Connectors and Indicators 1-2
TRSA System Connections 1-5
Data Transfer Interface
1-5
Diagnostic Subsystem Interface (Serial Maintenance Bus)
Power Interface
1-6
Relationship to the SLSA Subsystem
1-6
Accessing a TRSA through the SLSA Subsystem
Manufacturing Naming Conventions
1-7
1-9
2. Installing the TRSA
Prepare to Install a New TRSA 2-2
2-2
Plan the Local Area Network (LAN)
Complete the Configuration Form
Gather the Proper Tools
2-3
2-7
Review Standard Operating Practices
2-7
Compaq Computer Corporation —426955-001
i
1-5
2. Installing the TRSA (continued)
Contents
2. Installing the TRSA (continued)
Install the New TRSA
2-8
Unpack and Install the New TRSA 2-8
Check the Installation of the New TRSA 2-13
Add and Start the TRSA Using SCF 2-15
3. Replacing a TRSA
Prepare to Replace a TRSA
3-2
Gather the Proper Tools
3-2
Print the TRSA Planning Worksheet
3-3
Identify Any Communications Lines Using the TRSA
3-4
Redirect or Stop Any Customer Applications Using the TRSA
Stop the Communications Lines Using the TRSA
3-8
3-9
Determine the Physical Location of the TRSA 3-11
Abort the TRSA
3-12
Label the Communications Cable Connected to the TRSA
Replace the TRSA
3-13
3-15
3-15
Review Standard Operating Practices
Remove the Adapter
3-17
Inspect the New TRSA and Backplane
3-19
Unpack and Install the New TRSA 3-19
Check the Installation of the New TRSA 3-23
Resume Operations 3-25
Start the New TRSA
3-25
Restart the Communications Lines
3-28
Verify That the Communications Lines Are Started
3-29
Troubleshooting: If an Object is Not in the STARTED State
Resume Customer Applications
3-30
3-30
4. Relocating a TRSA
Prepare to Relocate the TRSA 4-2
Gather the Proper Tools
4-2
Print the TRSA Planning Worksheet
4-3
Identify Any Communications Lines Using the TRSA
4-4
Token-Ring Adapter Installation and Support Guide —426955-001
ii
4. Relocating a TRSA (continued)
Contents
4. Relocating a TRSA (continued)
Redirect or Stop Any Customer Applications Using the TRSA
Stop the Communications Lines Using the TRSA
4-9
4-9
Determine the Physical Location of the TRSA 4-11
Stop the TRSA 4-12
Locate the New Slot
4-14
Label the Communications Cable Connected to the TRSA
Remove and Install the TRSA
4-14
4-16
Review Standard Operating Practices
4-16
Remove and Install the Adapter 4-18
Check the Installation of the Relocated TRSA 4-22
Resume Operations 4-24
Complete the TRSA Configuration Form
Add the TRSA Using SCF
4-24
4-26
A. TRSA Configuration Form
B. Preparing a TRSA for PMF or IOMF CRU Replacement
Safety and Compliance
Glossary
Index
Token-Ring Adapter Installation and Support Guide —426955-001
iii
Examples
Contents
Examples
Example 2-1.
SCF STATUS Commands
2-16
Example 3-1.
SCF INFO LIF Command
3-4
Example 3-2.
SCF INFO SUBNET Command
Example 3-3.
SCF NAMES Command
Example 3-4.
SCF INFO LINE Command 3-6
Example 3-5.
SCF LISTDEVCommand
Example 3-6.
SCF INFO LINE Command with SUB PU and ASSOCIATESUBDEV
Options 3-7
Example 3-7.
SCF NAMES SUBSYS Command
Example 3-8.
SCF INFO PROCESS
Example 3-9.
SCF STATUS LINE Command 3-9
Example 3-10.
SCF STATUS PROCESS Command
Example 3-11.
SCF STATUS LINE Command 3-10
Example 3-12.
SCF STATUS SUBNET Command
Example 3-13.
SCF INFO ADAPTER Command
Example 3-14.
SCF STATUS LIF Command
Example 3-15.
SCF STATUS ADAPTER Command
3-13
Example 3-16.
SCF STATUS ADAPTER Command
3-26
Example 3-17.
SCF STATUS SAC Command
Example 3-18.
SCF STATUS PIF Command
Example 3-19.
SCF STATUS LIF Command 3-27
Example 3-20.
SCF STATUS SUBNET Command 3-29
Example 3-21.
SCF STATUS PROCESS Command 3-29
Example 3-22.
SCF STATUS LINE Command
3-29
Example 3-23.
SCF STATUS LINE Command
3-30
Example 4-1.
SCF INFO LIF Command
Example 4-2.
SCF INFO SUBNET Command
Example 4-3.
SCF NAMES Command
Example 4-4.
SCF INFO LINE Command
Example 4-5.
SCF LISTDEV Command
Example 4-6.
SCF INFO LINE Command with SUB PU and ASSOCIATESUBDEV
Options 4-7
3-5
3-6
3-6
3-8
3-8
3-10
3-11
3-11
3-12
3-26
3-26
4-4
4-5
4-6
4-6
4-6
Token-Ring Adapter Installation and Support Guide —426955-001
iv
Examples (continued)
Contents
Examples (continued)
Example 4-7.
SCF NAMES SUBSYS Command
4-8
Example 4-8.
SCF INFO PROCESS Command
Example 4-9.
SCF STATUS LINE Command
Example 4-10.
SCF STATUS PROCESS Command 4-10
Example 4-11.
SCF STATUS LINE Command
Example 4-12.
SCF STATUS SUBNET Command 4-11
Example 4-13.
SCF INFO ADAPTER Command
Example 4-14.
SCF INFO LIF Command
Example 4-15.
SCF STATUS LIF Command 4-13
Example 4-16.
SCF STATUS ADAPTER Command
Example 4-17.
SCF STATUS Commands
4-8
4-9
4-11
4-12
4-12
4-14
4-27
Figures
Figure 1-1.
Token-Ring ServerNet Adapter (TRSA)
1-4
Figure 1-2.
How Compaq Subsystems and Utilities Use the SLSA Subsystem to
Access a TRSA 1-8
Figure 2-1.
Completed TRSA Configuration Form 2-4
Figure 2-2.
TRSA Slot Locations 2-5
Figure 2-3.
TRSA Installed 2-6
Figure 2-4.
ESD Protected Environment 2-9
Figure 2-5.
Grounding Clip 2-10
Figure 2-6.
Ejector Shown in Full-Open Position 2-11
Figure 2-7.
Installing an New TRSA
Figure 2-8.
TRSA External Indicators 2-14
Figure 3-1.
TRSA Planning Worksheet 3-3
Figure 3-2.
TRSA Slot Locations 3-14
Figure 3-3.
ESD Protected Environment 3-16
Figure 3-4.
Grounding Clip 3-17
Figure 3-5.
Removing a TRSA 3-18
Figure 3-6.
Ejector Shown in Full-Open Position 3-20
Figure 3-7.
Installing a TRSA
Figure 3-8.
TRSA Hardware Connection
Figure 3-9.
TRSA External Indicators 3-24
2-12
3-21
3-22
Token-Ring Adapter Installation and Support Guide —426955-001
v
Figures (continued)
Contents
Figures (continued)
Figure 4-1.
TRSA Planning Worksheet 4-3
Figure 4-2.
TRSA Slot Locations 4-15
Figure 4-3.
ESD Protected Environment 4-17
Figure 4-4.
Grounding Clip 4-18
Figure 4-5.
Removing a TRSA 4-19
Figure 4-6.
Ejector Shown in Full-Open Position 4-20
Figure 4-7.
Installing a TRSA
Figure 4-8.
TRSA External Indicators 4-23
Figure 4-9.
Completed TRSA Configuration Form 4-25
4-21
Tables
Table i.
Summary of Contents ix
Table 1-1.
Naming Convention for LAN Subsystem and Related Processes 1-9
Table 2-1.
Preparation Checklist 2-2
Table 3-1.
Preparation Checklist 3-2
Table 3-2.
Replacement Checklist
Table 3-3.
Resuming Operations Checklist
Table 4-1.
Preparation Checklist 4-2
Table 4-2.
Replacement Checklist
Table 4-3.
Resuming Operations Checklist
3-15
3-25
4-16
4-24
Token-Ring Adapter Installation and Support Guide —426955-001
vi
What’s New in This Guide
Guide Information
Token-Ring Adapter Installation and Support Guide
Abstract
This guide provides step-by-step procedures for installing, replacing and relocating
Token-Ring ServerNet adapters on Compaq NonStop™ Himalaya S-series servers. This
guide is intended for anyone who installs or maintains TRSAs on NonStop™ Himalaya
S-series servers.
Product Version
N/A
Supported Releases
This guide supports G06.08 and all subsequent G-series releases until otherwise
indicated in a new edition
Part Number
Published
426955-001
August 2000
Document History
Part Number
Product Version
Published
137174
G05
February 1998
420094-001
G05
December 1998
426955-001
G06.08
August 2000
New and Changed Information
This guide has been updated as follows:
Section 4, Relocating an E4SA has been added to this guide and provides instructions
about relocating an E4SA.
Appendix B, Preparing an E4SA for PMF or IOMF CRU Replacement describes
checking the fault tolerance of an E4SA.
The ESD protection kit part number has been corrected to T99247-A00.
References to the TCP/IP (Parallel Library) Configuration and Management Manual
have been added where appropriate.
The manufacturing naming conventions subsection has been updated.
The glossary has been updated.
Token-Ring Adapter Installation and Support Guide —426955-001
vii
What’s New in This Guide
New and Changed Information
The guide’s title has been changed from Token-Ring Installation and Support Guide to
Token-Ring Adapter Installation and Support Guide.
Token-Ring Adapter Installation and Support Guide —426955-001
viii
About This Guide
This guide provides step-by-step procedures for adding, removing, and moving TokenRing ServerNet adapters (TRSAs).
Who Should Use This Guide
This guide is intended for anyone who installs or maintains TRSAs on Compaq
NonStop™ Himalaya S-series servers. This guide assumes you have experience in the
following:
•
•
•
Compaq TSM Service Application
Compaq SNAX/XF, SNAX/APN, and SNAX/APC products
ServerNet LAN Access System (SLSA)
What’s in This Guide
Table i summarizes the contents of this manual.
Table i. Summary of Contents
Section
Title
This secton...
1
Introduction to the Token-Ring
SeverNet Adapter (TRSA)
Describes the components of the
TRSA.
2
Installing the TRSA
Describes how to install a new TRSA.
3
Replacing a TRSA
Describes removal and replacement of
a TRSA.
4
Relocating a TRSA
Describes how to relocate a TRSA.
A
TRSA Configuration Form
Provides a blank configuration form.
B
Preparing a TRSA for PMF or IOMF
CRU Replacement
Describes how to verify the fault
tolerance of a TRSA before replacing a
PMF or IOMF CRU.
Where to Get More Information
Manuals describing the NonStop™ Himalaya S-series servers are organized into several
sets of manuals, which are fully described in the Himalaya S-Series Planning and
Configuration Guide.
Token-Ring Adapter Installation and Support Guide —426955-001
ix
Other Manuals
About This Guide
Other Manuals
Depending on the tasks you are performing, you might also need the following manuals:
•
•
•
•
•
•
•
LAN Configuration and Management Manual
TCP/IP (Parallel Library) Configuration and Management Manual
TCP/IP Configuration and Management Manual
IPX/SPX Configuration and Management Manual
PAM Configuration and Management Manual
SNAX/XF and SNAX/APN Configuration and Management Manual
SNAX/APC Configuration and Management Manual
Your Comments Invited
After using this manual, please take a moment to send us your comments. You can do
this by returning a Reader Comment Card or by sending an Internet mail message.
A Reader Comment Card is located at the back of printed manuals and as a separate file
on the User Documentation disc. You can either fax or mail the card to us. The fax
number and mailing address are provided on the card.
Also provided on the Reader Comment Card is an Internet mail address. When you
send an Internet mail message to us, we immediately acknowledge receipt of your
message. A detailed response to your message is sent as soon as possible. Be sure to
include your name, company name, address, and phone number in your message. If
your comments are specific to a particular manual, also include the part number and title
of the manual.
Many of the improvements you see in manuals are a result of suggestions from our
customers. Please take this opportunity to help us improve future manuals.
Notation Conventions
Hypertext Links
Blue underline is used to indicate a hypertext link within text. By clicking a passage of
text with a blue underline, you are taken to the location described. For example:
This requirement is described under Backup DAM Volumes and Physical Disk
Drives on page 3-2.
General Syntax Notation
The following list summarizes the notation conventions for syntax presentation in this
manual.
Token-Ring Adapter Installation and Support Guide —426955-001
x
General Syntax Notation
About This Guide
UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter
these items exactly as shown. Items not enclosed in brackets are required. For example:
MAXATTACH
lowercase italic letters. Lowercase italic letters indicate variable items that you supply.
Items not enclosed in brackets are required. For example:
file-name
[ ] Brackets. Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
INT[ERRUPTS]
A group of items enclosed in brackets is a list from which you can choose one item or
none. The items in the list may be arranged either vertically, with aligned brackets on
each side of the list, or horizontally, enclosed in a pair of brackets and separated by
vertical lines. For example:
FC [ num ]
[ -num]
[ text]
K [ X | D ] address-1
{ } Braces. A group of items enclosed in braces is a list from which you are required to
choose one item. The items in the list may be arranged either vertically, with aligned
braces on each side of the list, or horizontally, enclosed in a pair of braces and separated
by vertical lines. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
INSPECT { OFF | ON | SAVEABEND }
… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you
can repeat the enclosed sequence of syntax items any number of times. For example:
M address-1 [ , new-value ]...
[ - ] {0|1|2|3|4|5|6|7|8|9}...
An ellipsis immediately following a single syntax item indicates that you can repeat that
syntax item any number of times. For example:
"s-char..."
Token-Ring Adapter Installation and Support Guide —426955-001
xi
Notation for Messages
About This Guide
Punctuation. Parentheses, commas, semicolons, and other symbols not previously described
must be entered as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must enter as shown. For example:
"[" repetition-constant-list "]"
Item Spacing. Spaces shown between items are required unless one of the items is a
punctuation symbol such as a parenthesis or a comma. For example:
CALL STEPMOM ( process-id ) ;
If there is no space between two items, spaces are not permitted. In the following
example, there are no spaces permitted between the period and any other items:
$process-name.#su-name
Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation
line is indented three spaces and is separated from the preceding line by a blank line.
This spacing distinguishes items in a continuation line from items in a vertical list of
selections. For example:
ALTER [ / OUT file-spec / ] CONTROLLER
[ , attribute-spec ]...
Notation for Messages
The following list summarizes the notation conventions for the presentation of displayed
messages in this manual.
Bold Text. Bold text in an example indicates user input entered at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED:
123.00
The user must press the Return key after typing the input.
Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or
returned exactly as shown. For example:
Backup Up.
lowercase italic letters. Lowercase italic letters indicate variable items whose values are
displayed or returned. For example:
p-register
process-name
Token-Ring Adapter Installation and Support Guide —426955-001
xii
Notation for Management Programming Interfaces
About This Guide
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be displayed,
of which one or none might actually be displayed. The items in the list might be
arranged either vertically, with aligned brackets on each side of the list, or horizontally,
enclosed in a pair of brackets and separated by vertical lines. For example:
proc-name trapped [ in SQL | in SQL file system ]
{ } Braces. A group of items enclosed in braces is a list of all possible items that can be
displayed, of which one is actually displayed. The items in the list might be arranged
either vertically, with aligned braces on each side of the list, or horizontally, enclosed in
a pair of braces and separated by vertical lines. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown.
}
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
%þnotation precedes an octal number. The %Bþnotation precedes a binary number.
The %Hþnotation precedes a hexadecimal number. For example:
%005400
P=%p-register E=%e-register
Notation for Management Programming Interfaces
The following list summarizes the notation conventions used in the boxed descriptions
of programmatic commands, event messages, and error lists in this manual.
UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these
names exactly as shown. For example:
ZCOM-TKN-SUBJ-SERV
lowercase letters. Words in lowercase letters are words that are part of the notation,
including Data Definition Language (DDL) keywords. For example:
token-type
Token-Ring Adapter Installation and Support Guide —426955-001
xiii
Change Bar Notation
About This Guide
!r.
The !r notation following a token or field name indicates that the token or field is
required. For example:
ZCOM-TKN-OBJNAME
!o.
token-type ZSPI-TYP-STRING.
!r
The !o notation following a token or field name indicates that the token or field is
optional. For example:
ZSPI-TKN-MANAGER
token-type ZSPI-TYP-FNAME32.
!o
Change Bar Notation
Change bars are used to indicate substantive differences between this edition of the
manual and the preceding edition. Change bars are vertical rules placed in the right
margin of changed portions of text, figures, tables, examples, and so on. Change bars
highlight new or revised information. For example:
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for old
message types. In the CRE, the message type SYSTEM includes all messages
except LOGICAL-CLOSE and LOGICAL-OPEN.
Token-Ring Adapter Installation and Support Guide —426955-001
xiv
1
Introduction to the Token-Ring
SeverNet Adapter (TRSA)
This section provides an introduction to the Token-Ring ServerNet Adapter (TRSA) for
the Compaq NonStop™ Himalaya S-series servers.
Overview of the TRSA
Page 1-2
TRSA System Connections
Page 1-5
Relationship to the SLSA Subsystem
Page 1-6
Manufacturing Naming Conventions
Page 1-9
Token-Ring Adapter Installation and Support Guide —426955-001
1 -1
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
Overview of the TRSA
Overview of the TRSA
The Token-Ring ServerNet adapter (TRSA) is one of several supported ServerNet
adapters available for use on a NonStop™ Himalaya S-series server. The TRSA
provides connectivity between the server and other nodes on a token-ring network. The
TRSA is a hardware component known as a customer replaceable unit (CRU).
Most often, the TRSA is used together with the SNAX family of SNA-based software
products. Other uses of the adapter include Expand over Token Ring, and TCP/IP over
Token Ring.
TRSA Features:
The features of the TRSA are as follows:
•
Supports a network speed of either 16 Mbps or 4 Mbps, configurable through the
Subsystem Control Facility (SCF). The default speed is 16Mpbs.
Note. In K-series servers running C- and D-series software, the Token-Ring adapter has a
default sped of 4 Mbps. (Note that only D30.nn and later releases are now supported. If
you are running a network of mixed series, be sure that your rings are set to the same
speed.
•
•
•
•
Operates with your existing NonStop™ Himalaya S-series network infrastructure,
including cabling (customer-supplied), protocol stacks, and user-written application
code.
Retains the knowledge base of Compaq network administrators and users.
Is fully fault-tolerant with two-channel (ServerNet X and Y fabric) connections for
each adapter.
Supported by Tandem Service Management (TSM) client software to facilitate
diagnostics and maintenance.
External Connectors and Indicators
The adapter provides a single token-ring interface that is IEEE 802.5 and IBM TokenRing compliant and that has a software configurable network speed of either 4 or 16
Mbps. The single connection can be configured for either the shielded twisted pair
(STP) or the unshielded twisted pair (UTP) token-ring networks. The connection to STP
media is through a 9-pin D connector (DB-9), whereas UTP connection is achieved
through an RJ-45 connector. Both these connectors are available on the front panel but
only one can be active at a time.
Figure 1-1 shows a front panel layout of the TRSA.
Cables that attach the adapter to the network must be ordered separately. Choose only
one of the media, STP or UTP.
Caution. If you attempt to connect both cables, the TRSA will fail.
Token-Ring Adapter Installation and Support Guide —426955-001
1 -2
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
External Connectors and Indicators
The external indicators consist of two status LEDs for the TRSA, and four status LEDs.
The two TRSA status LEDs, which are controlled by the Service Processor (SP),
indicate the state of the TRSA as follows:
LED
TRSA State
Green
Power-on
Amber
Fault condition
Four LEDs indicate activity or the condition of the TRSA:
LED
Indication when ON
16 Mbs Speed Indicator
Data transfer rate is 16 Mbps (when OFF the transfer rate is
4 Mbs.)
Ready
The TRSA is ready for data transfer.
Activity
Token-Ring activity exists.
Wire Fault
Wire fault condition
Token-Ring Adapter Installation and Support Guide —426955-001
1 -3
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
External Connectors and Indicators
Figure 1-1. Token-Ring ServerNet Adapter (TRSA)
Power-ON LED
(green)
Fault LED
(amber)
The top two ports are non-functional
in this release of the hardware and
software.
Only early versions of the adapter have
these ports.
Token Ring Connector UTP (RJ-45)
16Mbps Speed Indicator
Activity
Ready
Wire Fault
Token Ring Connector STP(DB-9)
CDT010.CDD
Token-Ring Adapter Installation and Support Guide —426955-001
1 -4
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
TRSA System Connections
TRSA System Connections
The TRSA has three primary connections:
•
•
•
Data transfer interface
Diagnostic interface
Power interface
Data Transfer Interface
The TRSA provides two supported interfaces: one to ServerNet and one to Token Ring.
The TRSA is attached to the ServerNet System Area Network (SAN) and provides a
connection to a Token-Ring LAN. ServerNet is a full-duplex, parallel bus that transfers
data and commands between endpoints at a 50-Mbyte rate. Physically, ServerNet is a
point-to-point connection consisting of two 9-bit buses and a 50MHz clock for each bus.
Each bus is unidirectional. The buses, known as X and Y fabrics, are duplicated for
redundancy,
The Token-Ring data transfer interface consists of ports for the X and Y fabrics. The
ports attach to a single ServerNet addressable controller (SAC).
Diagnostic Subsystem Interface (Serial Maintenance Bus)
The maintenance subsystem contains the circuitry required to meet the maintenancesystem requirements of an active-logic CRU. It is the maintenance subsystem which
provides the Maintenance and Diagnostic System (MDS) with the following
capabilities:
•
•
•
•
•
Powering the adapter on and off
Identifying the type, configuration, and revision of the adapter
Running scan diagnostics on JTAG components.
Initializing the adapter for access to or from the ServerNet
Controlling the adapter’s standard LEDs
The maintenance subsystem includes:
•
•
•
Two serial buses that have been multiplexed to form a single serial maintenance bus
(SMB).
An MROUTER, which provides redundant access to the maintenance-system
features of the CRU. The maintenance and diagnostic system provides the following
capabilities:
A serial EEPROM (SEEROM) that provides:
•
•
Hardware identification (part number and revision)
Manufacturing tracking (serial) number.
Token-Ring Adapter Installation and Support Guide —426955-001
1 -5
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
•
•
Power Interface
CRU visual indicators
Power control to the TRSA.
Power Interface
The TRSA receives power through a shielded high-density, metric connector module.
The connector module consists of two 72-in block and a blade power block.
Relationship to the SLSA Subsystem
The ServerNet LAN Systems Access (SLSA) subsystem supports parallel I/O to LANs
linked to the ServerNet SAN. Thus, multiple LANs, using different protocols can all
access the processors (NonStop™ Himalaya S-series servers) attached to the ServerNet.
For example, TCP/IP, IPX/SPX, Expand, and SNA (Token-Ring) protocols may all be
communicating through the SAN, all simultaneously performing I/O with the processors
attached to the SAN.
The application process using the Token-Ring protocol, most probably SNAX/TR,
communicates with the port access method (PAM) process through a message system
interface (MSAP). The PAM process communicates with SLSA through a logical
interface (LIF). There is also a physical interface (PIF).
SNAX does not directly control the TRSA. SNAX communicates with the PAM
message interface, which provides an LLC2 port interface for token-ring
communications. The PAM process uses services provided by the SLSA subsystem.
SLSA is used to configure and control the TRSA.
Token-Ring Adapter Installation and Support Guide —426955-001
1 -6
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
Accessing a TRSA through the SLSA Subsystem
Accessing a TRSA through the SLSA Subsystem
The SLSA subsystem provides access to the TRSA. The following subsystems and
utilities may be configured to access a TRSA through the SLSA subsystem:
•
•
The conventional TCP/IP and the Parallel Library TCP/IP Subsystems, which can
interface to the SLSA subsystem to provide connectivity to TCP/IP networks.
Telserv and the File Transfer Protocol (FTP) can use the socket library to establish
remote connections through the TCP/IP subsystem.
The Port Access method (PAM) subsystem, which can interface to the SLSA
subsystem to provide an independent interface to Token-Ring networks, and userwritten applications written that use the PAM subsystem port interface. The
following subsystems can interface to the PAM subsystem to use a TRSA:
•
•
•
The SNAX/XF subsystem, which can be configured to provide connections to
Token-Ring networks.
The SNAX/APN subsystem, which can be configured to provide
connections to Token-Ring networks.
The IPX/SPX subsystem, which can interface to the SLSA subsystem to provide
connectivity to Novell NetWare networks. The following Compaq utilities and
subsystems can interface to the IPX/SPX subsystem to use a TRSA:
•
•
•
Telserv and FTP, which use the socket library to establish remote connections
through the IPX/SPX subsystem.
Subsystems, such as Remote Server Call (RSC), that can be configured to
establish connections and communicate through the IPX/SPX subsystem.
Compaq subsystems, such as Remote Server Call (RSC) that can be configured
to establish connections through the IPX/SPX subsystem.
Figure 1-2 illustrates how Compaq subsystems and utilities use the SLSA subsystem to
access a TRSA.
Token-Ring Adapter Installation and Support Guide —426955-001
1 -7
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
Accessing a TRSA through the SLSA Subsystem
Figure 1-2. How Compaq Subsystems and Utilities Use the SLSA Subsystem to
Access a TRSA
Processor
User Applications
File System
Interface
Socket Lib
SNAX/TR
QIO Shared Memory
Segment
TCP/IP
IPX/SPX
PAM
SLSA
Processes
LIF
LAN Drivers and Interrupt Handlers
Y Fabric
X Fabric
TRSA
Legend
SLSA Subsystem
CDT 005.CDD
Token-Ring Adapter Installation and Support Guide —426955-001
1 -8
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
Manufacturing Naming Conventions
Manufacturing Naming Conventions
Compaq manufacturing uses a naming convention for processes and devices that relates
logical names to the physical location of devices. Table 1-1 describes the naming
conventions used for SLSA subsystem processes and other processes and devices
required by the SLSA subsystem.
Table 1-1. Naming Convention for LAN Subsystem and Related Processes
Process or Device Type
Convention
Example
LAN Manager (LANMAN)
process
Must be $ZZLAN
$ZZLAN
Logical interface (LIF)
$ZZLAN.Lcabid-portid
$ZZLAN.L018
Token-Ring ServerNet
adapter (TRSA)
$ZZLAN.Ecabid-slot
$ZZLAN.E0153
cabid
is the two-digit number that identifies the enclosure; cabid is also the group
number.
cabid
Description
Range of Values
0n
The object is in processor enclosure n.
01-08
n1
The object is in I/O enclosure 1 attached
to processor enclosure n.
11, 21, 31, 41, 51, 61, 71, or
81
n2
The object is in I/O enclosure 2 attached
to processor enclosure n.
12, 22, 32, 42, 52, 62, 72, or
82
n3
The object is in I/O enclosure 3 attached
to processor enclosure n.
13, 23, 33, 43, 53, 63, 73, or
83
slot
is the physical slot number in the enclosure for the TRSA.
Number
Enclosure
53 to 54
processor enclosure
51 to 54
I/O enclosure
portid
is the combination of the slot number and port number for the TRSA. The port
number for the TRSA is always 0; thus, the portid is mapped in the following way:
Token-Ring Adapter Installation and Support Guide—426955-001
1-9
Introduction to the Token-Ring SeverNet Adapter
(TRSA)
Slot
Number
Port
Number
portid
51
0
0
52
0
4
53
0
8
54
0
C
Manufacturing Naming Conventions
For more information on suggested naming conventions, refer to the LAN Configuration
and Management Manual.
Token-Ring Adapter Installation and Support Guide—426955-001
1-10
2
Installing the TRSA
This section describes how to configure and install a new Token-Ring ServerNet adapter
(TRSA) in a Compaq NonStop™ Himalaya S-series enclosure. When a new system is
shipped, Compaq manufacturing has already installed and configured two TRSAs.
Additional TRSAs can be installed and configured by following the procedures outlined
in this section.
Note. A TRSA can be installed without shutting down the system.
This section covers the following topics:
Prepare to Install a New TRSA
Page 2-2
Install the New TRSA
Page 2-8
Token-Ring Adapter Installation and Support Guide—426955-001
2-1
Installing the TRSA
Prepare to Install a New TRSA
Prepare to Install a New TRSA
This section describes those tasks you should perform before installing or configuring
the TRSA. Table 2-1 summarizes the steps.
Table 2-1. Preparation Checklist
Step
Description
1.
Plan the Local Area Network (LAN)
2.
Complete the Configuration Form
3.
Gather the Proper Tools
4.
Review Standard Operating Practices
Comments
A sample form is provided. See
Figure 2-1 on page 2-4. See also
Appendix A, TRSA
Configuration Form.
Plan the Local Area Network (LAN)
For information about planning your LAN and about network addresses, review the LAN
Configuration and Management Manual, and refer, if necessary, to the following manuals:
•
•
•
•
•
•
TCP/IP Configuration and Management Manual
TCP/IP (Parallel Library) Configuration and Management Manual
PAM Configuration and Management Manual
IPX/SPX Configuration and Management Manual
SNAX/XF and SNAX/APN Configuration and Management Manual
SNAX/APC Configuration and Management Manual
SNAX does not directly control the TRSA. SNAX communicates with the PAM
message interface, which provides an LLC2 port interface for token-ring
communications. The PAM process uses services provided by the ServerNet LAN
Systems Access (SLSA) subsystem. SLSA is used to configure and control the TRSA.
See Relationship to the SLSA Subsystem on page 1-6 for more information.
The recommended configuration route through the levels of the system is as follows:
1. Configure the ADAPTER, SAC, PIF, and LIF to SLSA.
2. Configure the use of PAM for SNAX.
3. Configure the LINE, PU and LU to SNAX/XF or SNAX/APN.
4. Configure TCP/IP, if desired, or IPXPROTO, if desired.
Token-Ring Adapter Installation and Support Guide—426955-001
2-2
Installing the TRSA
Complete the Configuration Form
Complete the Configuration Form
Complete an TRSA Configuration Form for each TRSA you are adding to your system.
Figure 2-1 on page 2-4 shows an example of a completed Token-Ring ServerNet
Adapter (TRSA) Configuration Form.
When you add an adapter to a NonStop™ Himalaya S-series system, you specify:
•
•
•
The name you want to use to identify the adapter; for example, E0153 for a TokenRing adapter in slot 53 of the first system enclosure.
The location of the adapter within the system cabinet (group, module, and slot).
The processors that have access to the SACs on the adapter.
Before you begin the hardware installation, you should complete a TRSA configuration
form. Obtain the form from Appendix A, TRSA Configuration Form, and enter the
following information:
•
•
•
•
•
•
The name of the system in the System Name field.
The group number for this enclosure in the Group Number field.
The slot number of this TRSA in the Slot Number field. TRSAs can be installed
in slots 51, 52, 53 and 54 of an I/O enclosure (expansion) but only 53 and 54 of
a processor enclosure. Figure 2-2 on page 2-5 shows the possible slot locations
for the TRSA.
Note that because there is exactly one module in a system or I/O enclosure, the
module number, 1, is already indicated on the form.
Enter the remaining information needed to install the TRSA:
•
•
•
•
•
The IP address.
The adapter name (See Manufacturing Naming Conventions on page 1-8).
The numbers of the processors that will have access to the SAC in the SAC
Access List field. The first processor listed is the preferred processor.
The PIF name associated with the SAC in the PIF Name field.
The LIF name associated with the PIF in the LIF Name field.
When you have completed this form, enter today’s date in the Date field.
Figure 2-1 shows a completed TRSA configuration form.
Token-Ring Adapter Installation and Support Guide—426955-001
2-3
Installing the TRSA
Complete the Configuration Form
Figure 2-1. Completed TRSA Configuration Form
Date
Group
SAC 1
ENET 1A:
\COWBOY
System Name
Token-RingServerNet Adapter (TRSA)
Configuration Form
01
IP Address:
Module
01
07
/
Slot
21
/
00
53
172.16.35.15
Adapter Name: E0153
SAC Name:
E0153 .0
SAC Access List: (1,0)
PIF Name:
E0153 .0.A
LIF Name:
L018
CDT 235
Token-Ring Adapter Installation and Support Guide—426955-001
2-4
Installing the TRSA
Complete the Configuration Form
Figure 2-2. TRSA Slot Locations
Himalaya S-Series I/O Enclosures
(Service Side)
50
55
Himalaya S-Series Processor Enclosure
(Service Side)
50
55
51 52 53 54
51 52 53 54
56
I/O enclosures can use slots
51 through 54 for a TRSA.
56
Processor enclosures can only use
slots 53 and 54 for aTRSA.
CDT 057.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
2-5
Installing the TRSA
Complete the Configuration Form
Figure 2-3 shows the TRSA installed in a system enclosure.
Figure 2-3. TRSA Installed
AA
AA
AA
CDT 021.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
2-6
Installing the TRSA
Gather the Proper Tools
Gather the Proper Tools
You will need the following tools to install an adapter:
Tool
Used to. . .
Electrostatic discharge (ESD)
wriststrap with grounding clip
Protect the adapter from damage caused by electrostatic
discharge.
Antistatic mat (recommended)
Provide a static-free environment for removal and
installation of an adapter.
Flashlight
Check the connectors for bent or broken pins.
Note. An ESD protection kit can be purchased from Compaq using the following order number
and part number:
Order Number: ESD-Kit
Part Number: T99247-A00
Once you have completed the form and gathered the proper tools, you are ready to
install the new TRSA.
Review Standard Operating Practices
Standard operating practices include the following:
•
•
•
•
Work in an electrostatic discharge (ESD)protected environment.
Remove all metal accessories before working with electrical equipment.
Restrain any dangling items that can get caught in equipment.
Obtain an ESD protection kit and follow the directions that come with the kit.
Figure 2-4 illustrates an ESD protected environment.
Token-Ring Adapter Installation and Support Guide—426955-001
2-7
Installing the TRSA
Install the New TRSA
Install the New TRSA
You should perform the hardware installation first and then add the adapter using the
Subsystem Control Facility (SCF). You can use SCF to add the adapter first and then
insert the hardware. Whichever installation method you choose, the state of a logical
interface (LIF) is not affected by the physical presence, or absence, of an adapter. If you
decide to configure the adapter and its LIF before the TRSA is inserted into the
enclosure, the ServerNet addressable controller (SAC) and physical interface (PIF) of
the adapter will remain in the starting state; the LIF will be in the started state, but its
access state will be down until its associated PIF is started. The following subtopics
describe the tasks associated with physically inserting the TRSA into a NonStop™
Himalaya S-series system enclosure and using the SLSA subsystem to logically add and
start the TRSA:
•
•
•
Unpack and Install the New TRSA
Check the Installation of the New TRSA
Add and Start the TRSA Using SCF
Unpack and Install the New TRSA
The following paragraphs describe how to unpack and install the new TRSA.
Note. Whenever you handle a TRSA, you should follow standard operating practices to avoid
damage to the equipment. See Review Standard Operating Practices on page 2-7.
Unpack the TRSA
The following steps explain how to unpack the TRSA:
1. Put on the electrostatic discharge (ESD) wriststrap and attach the grounding clip to
the antistatic mat.
2. Place the package containing the TRSA on the antistatic mat.
3. Open the packing container and remove the TRSA.
Caution. When
protective bag.
opening the packing container, be careful not to cut into the ESD
4. Disconnect the grounding clip of your ESD wriststrap from the antistatic mat and
connect it to an exposed, unpainted metal surface on the TRSA.
5. Grasp the TRSA by its ejector in one hand, support the bottom edge of the TRSA
with the other hand, and carry the TRSA to the service side of the system enclosure
and set it down.
Note. The TRSA weights 6.75 pounds (3 kilograms)
Token-Ring Adapter Installation and Support Guide—426955-001
2-8
Installing the TRSA
Unpack and Install the New TRSA
6. Disconnect the grounding clip of your ESD wriststrap from the TRSA and connect it
to an exposed, unpainted, metal surface on the service side of the system enclosure,
such as the processor multifunction (PMF) adapter or I/O multifunction (IOMF)
adapter ventilation holes.
Figure 2-4. ESD Protected Environment
System Enclosure (Appearance Side)
ESD wriststrap clipped to
door latch stud (or to any
exposed, unpainted, metal
surface on the enclosure
frame.)
ESD wriststrap
with clip
ESD floor mats
ESD antistatic table mat.
Mat should be connected to a soft ground
(1 megohm min. to 10 megohm max.)
Clip 15 inch straight
ground cord to screw
on grounded outlet
cover.
CDT 002.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
2-9
Installing the TRSA
Unpack and Install the New TRSA
Figure 2-5 shows how to connect the grounding clip to the ventilation holes on the
PMF adapter or IOMF adapter.
Figure 2-5. Grounding Clip
Processor Multifunction (PMF) CRU or
I/O Multifunction (IOMF) CRU
Grounding
Clip
To Grounding
Wriststrap
CDT 081.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
2-10
Installing the TRSA
Unpack and Install the New TRSA
Install the TRSA
The following steps explain how to insert the TRSA into the system enclosure.
1. With the ejector on the TRSA in the full-open position (Figure 2-6), grasp the TRSA
by the ejector with one hand and support the bottom edge of the TRSA with the
other hand (Figure 2-7 on page 2-12). Hold the adapter so that its ejector is at the
top, as shown in Figure 2-6, and insert the adapter into the upper part of the carrier.
Figure 2-6. Ejector Shown in Full-Open Position
CDT500.CDD
2. Push the TRSA to the rear of the slot, but don't force it.
Caution. Apply equal pressure to both the top and bottom of the TRSA when pushing it into
the slot to avoid damaging the connector pins. If pins are damaged, both the TRSA and the
backplane (or enclosure) must be replaced.
3. Press the blue-green tab on the TRSA ejector and latch the ejector to seat the TRSA
against the backplane.
Token-Ring Adapter Installation and Support Guide—426955-001
2-11
Installing the TRSA
Unpack and Install the New TRSA
Figure 2-7. Installing an New TRSA
CDT 058.CDD
4. Disconnect the grounding clip of your ESD wriststrap from the enclosure.
5. Connect the communications cable to the TRSA. You can connect an RJ-45
connector to the Token-Ring Connector UTP port or a DB-9 connector to the
Token-Ring Connector STP port.
Token-Ring Adapter Installation and Support Guide—426955-001
2-12
Installing the TRSA
Check the Installation of the New TRSA
Check the Installation of the New TRSA
To check the installation of the TRSA:
1. Make sure that the power-on LED (green light) is on.
Note. When the adapter is inserted, the fault LED (yellow) remains on until the service
processor has completed its start-up configuration; the fault LED also turns on when a
POST failure is detected.
Figure 2-8 shows the location of the power-on LED and fault LED.
2. If the power-on LED (green light) does not come on, do one or both of the
following:
•
•
Reseat the TRSA.
Check the TRSA and backplane connector for damaged pins.
Note the Following Error Conditions
Note the possible error conditions:
•
•
If the power-on LED does not come on after you reseat the TRSA, you must replace
the TRSA.
If the TRSA or backplane connector has damaged pins, both the TRSA and
backplane (or enclosure) must be replaced. For backplane replacement instructions,
refer to the Himalaya S-Series Service Provider Supplement.
Token-Ring Adapter Installation and Support Guide—426955-001
2-13
Installing the TRSA
Check the Installation of the New TRSA
Figure 2-8. TRSA External Indicators
Power-ON LED
(green)
Fault LED
(amber)
The top two ports are non-functional
in this release of the hardware and
software.
Only early versions of the adapter
have these ports.
CDT091.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
2-14
Installing the TRSA
Add and Start the TRSA Using SCF
Add and Start the TRSA Using SCF
Using the completed TRSA configuration form as a guide, use the SCF interface to the
SLSA subsystem to add and start the newly installed TRSA.
Note. Refer to the LAN Configuration and Management Manual for detailed information about
the SLSA subsystem SCF commands.
Adding and Starting the TRSA
The following steps outline adding and starting the TRSA.
1. Add the TRSA by using the SLSA subsystem SCF ADD ADAPTER command as
follows:.
->ASSUME PROCESS $ZZLAN
->ADD ADAPTER $ZZLAN.E1053, TYPE TRSA, LOCATION (1,1,53),
ACCESSLIST (0,1,2,3)
SCF adds an TRSA to slot 53, group 1, module 1, and gives processor 0 primary
access to the ServerNet addressable controller (SAC). Processors 1 through 3 are
assigned secondary access.
2. Use the SLSA subsystem SCF NAMES command to display the names assigned to
the SAC and PIF of the adapter you added in Step 1.
->NAMES PIF $ZZLAN.E0153*
SLSA Names PIF \SYS.$ZZLAN.E0153
PIF
$ZZLAN.E0153.0.A
3. Assign logical interface (LIF) to the PIF on the TRSA added in Step 1 by using the
SLSA subsystem SCF ADD LIF command. Use the name of the PIF returned from
the NAMES command in Step 2.
->ADD LIF $ZZLAN.L018, PIF E0153.0.A
4. Start the LIF by using the SLSA subsystem START LIF command.
->START LIF $ZZLAN.L018
5. Start the TRSA and its subordinate SAC and PIF objects by using the SLSA
subsystem SCF START ADAPTER command with the SUB ALL option as shown
in the following example. The SUB ALL option starts the ADAPTER object and its
subordinate objects:
->START ADAPTER $ZZLAN.E1053, SUB ALL
Note. You can also use the TSM Service Application to start an adapter. Refer to Using the
TSM Service Application to Start the FESA on page 3-29.
Token-Ring Adapter Installation and Support Guide—426955-001
2-15
Installing the TRSA
Add and Start the TRSA Using SCF
6. Use the SLSA subsystem SCF STATUS commands to check that the adapter, SAC,
PIF, and LIF have started as shown in Example 2-1.
Example 2-1. SCF STATUS Commands
->STATUS ADAPTER $ZZLAN.E0153
SLSA Status ADAPTER
Name
State
$ZZLAN.E1053
STARTED
-> STATUS SAC $ZZLAN.E1053.*
SLSA Status SAC
Name
Owner
State
$ZZLAN.E1053.
0 0
STARTED
-> STATUS PIF $ZZLAN.E1053.*
SLSA Status PIF
Name
$ZZLAN.E1053.0.A
State
STARTED
-> STATUS LIF $ZZLAN.L01*
SLSA Status LIF
Name
$ZZLAN.L018
State
STARTED
Access State
UP
Note. There are many attributes for the SCF objects at this level. For example, the TokenRing speed could be 4 MB or 16 MB, and the node MAC address might be set as part of the
PIF configuration. You can use the SCF ALTER PIF command to change the PIF defaults.
Troubleshooting: If the TRSA SAC Object Is Still in the
STARTING State
If the SCF STATUS SAC command shows that the TRSA SAC object is still in the
STARTING state after a few minutes or if the TSM Service Application indicates that
the resource needs attention, do the following:
1. Check for event messages in the Event Message Service (EMS) log. Use the TSM
EMS Event Viewer Application to view the EMS log:
a. From the File menu, select Log on.
b. Select the system.
c. Type the Compaq NonStop™ Kernel user name and password.
d. Click OK.
e. From the Setup menu, set up Timeframe, Source, or Subsystem criteria.
Refer to the Operator Messages Manual for cause, effect, and recovery information
for event messages.
2. Check the firmware version of the new TRSA and update it. (When the
AUTOFIRMUP attribute is set to ON, which is the default, the firmware file is
automatically downloaded to the SAC when the SAC is started. Although the
Token-Ring Adapter Installation and Support Guide—426955-001
2-16
Installing the TRSA
Add and Start the TRSA Using SCF
firmware version is automatically updated by the system, you should verify the
firmware version.)
Use the TSM Service Application to check the firmware version:
a. Log on to the TSM Service Application.
b. From the Display menu, choose Firmware Update.
c. From the Resource type pull-down menu, select resource type.
d. From the Display pull-down menu, select Down-rev only.
A list of resources whose firmware is older than the version of the SYSnn is
displayed in the Available list box. Do the following:
e. Double-click on the resource. The resource is displayed in the Selected list box.
f.
Click Perform action to initiate the firmware update.
For information about configuring the conventional TCP/IP, Parallel Library TCP/IP,
IPX/SPX, or Port Access Method (PAM) subsystems to access the TRSA through the
SLSA subsystem, refer to the following manuals:
•
•
•
•
•
LAN Configuration and Management Manual
TCP/IP Configuration and Management Manual
TCP/IP (Parallel Library) Configuration and Management Manual
PAM Configuration and Management Manual
IPX/SPX Configuration and Management Manual
Token-Ring Adapter Installation and Support Guide—426955-001
2-17
Installing the TRSA
Add and Start the TRSA Using SCF
Token-Ring Adapter Installation and Support Guide—426955-001
2-18
3
Replacing a TRSA
This procedure section describes how to perform online replacement of a Token-Ring
ServerNet adapter (TRSA) in a Compaq NonStop™ Himalaya S-series server. You
might need to replace the TRSA if it has failed or partially failed. If POST fails and if
there is an alarm generated by the TSM package on the SAC TRSA, the TRSA must be
replaced.
Note. A TRSA can be installed without shutting down the system.
Caution. If a previously installed TRSA and backplane connector have damaged pins, remove
the TRSA and install a filler panel in the vacant slot. Attach red tags to the filler panel to identify
the slot. Do not move the damaged TRSA to a different, undamaged slot. Both the TRSA and
backplane (or enclosure) must be replaced. For backplane replacement, refer to the backplane
replacement section of the Himalaya S-Series Service Provider Supplement available in
G-series Total Information Manager (TIM) collections.
Removal and replacement of the TRSA is described in the following subsections:
Prepare to Replace a TRSA
Page 3-2
Replace the TRSA
Page 3-15
Resume Operations
Page 3-25
Note. Whenever you handle the TRSA, you should follow standard operating practices to
avoid damage to the equipment. See Review Standard Operating Practices on page 3-15.
Token-Ring Adapter Installation and Support Guide—426955-001
3-1
Replacing a TRSA
Prepare to Replace a TRSA
Prepare to Replace a TRSA
TRSAs can be installed in slots 53 and 54 of a processor enclosure and in slots 51, 52,
53, and 54 of an I/O enclosure. See Figure 3-2 on page 3-14. When no TRSA is installed
in a slot, a ServerNet adapter filler panel occupies the empty slot. (Therefore, a
ServerNet adapter filler panel might occupy slots 53 and 54 of a processor enclosure or
slots 51 through 54 of an I/O enclosure.) The filler panel maintains proper air flow and
reduces electromagnetic interference (EMI).
Table 3-1 summarizes the important steps for preparing to replace a TRSA.
Table 3-1. Preparation Checklist
Step
Description
Comments
1.
Gather the Proper Tools
2.
Print the TRSA Planning Worksheet
3.
Identify Any Communications Lines Using the TRSA
4.
Redirect or Stop Any Customer Applications Using the
TRSA
5.
Determine the Physical Location of the TRSA
6.
Abort the TRSA
7.
Stop the Communications Lines Using the TRSA
8.
Label the Communications Cable Connected to the TRSA
See Figure 3-1 on
page 3-3.
Gather the Proper Tools
You will need the following tools to replace an adapter:
Tool
Used to. . .
Electrostatic discharge (ESD)
wriststrap with grounding clip
Protect the adapter from damage caused by electrostatic
discharge.
Antistatic mat (recommended)
Provide a static-free environment for removal and
installation of an adapter.
Flashlight
Check the connectors for bent or broken pins.
Note. An ESD protection kit can be purchased from Compaq using the following order number
and part number:
Order Number: ESD-Kit
Part Number: T99247-A00
Token-Ring Adapter Installation and Support Guide—426955-001
3-2
Replacing a TRSA
Print the TRSA Planning Worksheet
Print the TRSA Planning Worksheet
Make a copy of Figure 3-1, TRSA Planning Worksheet and use it to record information
about the TRSA.
Figure 3-1. TRSA Planning Worksheet
TRSA Planning Worksheet
Print this worksheet and use it to record information about a Token-Ring ServerNet adapter (TRSA).
Logical interface (LIF) and Physical Interface (LIF):
LIF:
PIF:
TCP/IP Process, Subnet, and Internet Protocol (IP) Address
TCP/IP Process:
Subnet:
IP Address:
Port Access Method (PAM) Line:
PAM Line:
SNAX/TR Line:
PAM Line:
SNAX/TR Line:
IPXPROTO Process :
IPXPROTO Process:
CDT040.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
3-3
Replacing a TRSA
Identify Any Communications Lines Using the TRSA
Identify Any Communications Lines Using the TRSA
The subsystems and utilities that use the SLSA subsystem to access a TRSA are
illustrated in Figure 1-2.
Note. SNAX/XF and SNAX/APN lines that use token-ring connections are referred to as
SNAX/TR lines in the following procedure.
Use the following procedure to help you identify the subsystems and utilities that are
configured to use a TRSA. Specific instructions are provided for identifying SNAX/TR
lines.
Note. Make a note of the information you obtain during this procedure. You can record this
information on the planning worksheet provided or you can use the SCF LOG command to
capture both the command and the display to a file. To start logging, type LOG logfilename
at the SCF prompt. To stop logging, type LOG at the SCF prompt.
Perform the following steps:
1. Determine the name of the logical interface (LIF) and physical interface (PIF)
associated with the TRSA to be replaced.
a. Use the SCF INFO LIF command:
->SCF INFO LIF $ZZLAN.*
b. Scan the output of the command for the name of the TRSA to be replaced. Make
a note of the LIF name and PIF name.
Example 3-1 shows the output of this command. The Logical interface (LIF)
name is shown in the Name column and the physical interface (PIF) name is
shown in the PIF column. The name of the Token-Ring ServerNet adapter
(TRSA) CRU is the first part of the PIF name (for example, E0153).
The PIF name indicates the physical port on the TRSA. For example, the PIF
named E0153.1.A. identifies the UTP (RJ-45) port on the TRSA named E0153.
In this example, the LIF associated with the TRSA named E0153 is named
L018.
Example 3-1. SCF INFO LIF Command
-->INFO LIF $ZZLAN.*
SLSA info LIF
Name
$ZZLAN
PIF
E0153.1.A
MAC Address
08:00:8E:00:5C:85
Type
Token Ring
2. Determine the TCP/IP processes, subnets, and Internet Protocol (IP) addresses
associated with the LIF for the TRSA to be replaced.
a.
Use the SCF INFO SUBNET command:
->INFO SUBNET $*.*
b. Scan the output of the command for the LIF you identified in Step 1 and then
find the associated TCP/IP process, subnet, and IP address. Make a note of this
Token-Ring Adapter Installation and Support Guide—426955-001
3-4
Replacing a TRSA
Identify Any Communications Lines Using the TRSA
information on the Record this information on the TRSA Planning Worksheet
on page 3-3.
c. Example 3-2 shows the output of this command. Use the following information
to help interpret the display:
The TCP/IP process name is displayed in the first line of output (for example,
$ZTC01).
The subnet name is displayed in the Name column (for example, #SN1).
The logical interface (LIF) name is displayed in the Devicename column (for
example, $L018).
The Internet Protocol (IP) address is displayed in the *IPADDRESS column
(for example, 172.16.35.15).
Note. You can easily check for Token-Ring ServerNet adapter (TRSA) CRU subnets by
looking in the TYPE column. The TRSA subnets are displayed as type SNAP.
In Example 3-2, which is partial output, the TRSA LIF named L018 is associated
with the subnet named #SN1 on the TCP/IP process named $ZTC01 and has the IP
address 172.16.35.15.
Example 3-2. SCF INFO SUBNET Command
->INFO SUBNET $*.*
TCPIP Info SUBNET \JULIE.$ZTC01.*
Name
Devicename
#LOOP0 \NOSYS.$NOIOP
#SN1
\JULIE.$L018
*IPADDRESS
127.0.0.1
172.16.35.15
TYPE
*SUBNETMASK
SuName QIO *R
LOOP-BACK %HFF000000
SNAP
%HFFFFFF00
OFF
ON
N
N
3. Identify the PAM lines configured on the system. Use the SCF NAMES command:
NAMES $ZZPAM
Example 3-3 on page 3-6 shows the output of this command. Port Access Method
(PAM) line names are shown under the LINE heading. In this example, which is
partial output, one PAM line is configured named $TOK1.
Token-Ring Adapter Installation and Support Guide—426955-001
3-5
Replacing a TRSA
Identify Any Communications Lines Using the TRSA
Example 3-3. SCF NAMES Command
->NAMES $ZZPAM
PAM Names PROCESS \SAMCAT.$ZZPAM
PROCESS
$TOK1 $ZZPAM
LINE
$TOK1
PORT
$TOK1.#L1P0002
$TOK1.#L1P0004
MSAP
$TOK1.#SNATR
4. Determine the PAM lines associated with the LIF on the TRSA to be replaced.
a. Use the SCF INFO LINE command for each PAM line you identified in Step 3:
INFO LINE $line-name
b. Check the output for the LIF on the TRSA to be replaced. On the TRSA
Planning Worksheet on page 3-3, record the PAM lines associated with the LIF
on the TRSA.
Example 3-4 shows the output of this command. The LIF name is shown in the
LIF NAME column. The type of CRU is shown in the LIF TYPE column. The
LIF type is TR. In this example, the TRSA LIF named L01C is associated with
the PAM line named $TOK1.
Example 3-4. SCF INFO LINE Command
->SCF INFO LINE $TOK1
PAM Info LINE
Name
$TOK1
MAXREQUESTSIZE
3200
LIF NAME
L01C
LIF TYPE
TR
LIF MAC ADDRESS
08:00:8E:00:D1:95
5. Identify the SNAX/TR lines configured on the system. Use the following SCF
LISTDEV command to display the SNAX/TR lines:
LISTDEV TYPE 58,4
In Example 3-5, two SNAX/TR lines, one named $TRS1 and one named $TRS2, are
configured on the system.
Example 3-5. SCF LISTDEV Command
->LISTDEV TYPE 58,4
LDev Name PPID
109 $TRS1 3,9
159 $TRS2 0,16
BPID
2,7
1,15
Type Rsize Pri
(58,4)
3 199
(58,4)
3 199
Program
\COWBOY.$DATA00.T9057ADJ.SNATSOBJ
\COWBOY.$DATA00.T9057ADJ.SNATSOBJ
Token-Ring Adapter Installation and Support Guide—426955-001
3-6
Replacing a TRSA
Identify Any Communications Lines Using the TRSA
6. Determine if any SNAX/TR lines configured on the system use the TRSA to be
replaced.
a.
Use the SCF INFO LINE command with the SUB PU and
ASSOCIATESUBDEV options for each SNAX/TR line you identified in Step
5:
INFO LINE $line-name, SUB PU, ASSOCIATESUBDEV
b. Scan the output of the command for the names of the PAM lines you identified
in Step 4. On the TRSA Planning Worksheet on page 3-3, record the SNAX/TR
lines that use the PAM lines.
Example 3-6 shows the output of this command. The AssociateSubDev
attribute shows the name of the PAM line associated with the SNAX/TR line. The
SNAX/TR line named $TRS1 is associated with the PAM line named $TOK1.
Example 3-6. SCF INFO LINE Command with SUB PU and ASSOCIATESUBDEV
Options
->INFO LINE $TRS1, SUB PU, ASSOCIATESUBDEV
SNAX Detailed Info PU \CHIP.$TRS1.#P041
AssociateSubDev.. \CHIP.$TOK1.#PO41
SNAX Detailed Info PU \CHIP.TRS1.#P042
AssociateSubDev.. \CHIP.$TOK1.#P042
SNAX Detailed Info PU \CHIP.TRS1.#P083
AssociateSubDev.. \CHIP.$TOK1.#P083
SNAX Detailed Info PU \CHIP.TRS1.#P084
AssociateSubDev.. \CHIP.$TOK1.#P084
7. Identify the IPXPROTO processes configured on the system.
Use the SCF NAMES SUBSYS command:
NAMES SUBSYS $ZMGR
Example 3-7 on page 3-8 shows the output of this command. IPXPROTO
process names are shown under the PROCESS heading. The two configured
IPXPROTO processes are named $ZNV0 and $ZNV1.
Token-Ring Adapter Installation and Support Guide—426955-001
3-7
Replacing a TRSA
Redirect or Stop Any Customer Applications Using
the TRSA
Example 3-7. SCF NAMES SUBSYS Command
->NAMES SUBSYS $ZMGR
IPXSPX Names SUBSYS \HIMA.$ZMGR
SUBSYS
$ZMGR
PROCESS
$ZNV0
SERVER
$ZNV0.#SAP
PROCESS
$ZNV1
SERVER
$ZNV1.#SAP
8. Determine the IPXPROTO processes associated with the LIF on the TRSA to be
replaced.
Note. The usual form for IPXPROTO process names is $ZNVn, where n is an
alphanumeric character from 0 through 9 or A through Z.
a. Use the SCF INFO PROCESS command for each IPXPROTO process you
identified in Step 7:
INFO PROCESS $process-name
b. SCAN the output for the LIF you identified in step 1, then find the associated
IPXPROTO processes. Make a note of the !PXPROTO process name associated
with the LIF on the TRSA.
Example 3-8 on page 3-8 shows the output of this command. The LIF name is
shown in the I/O Port Name column. In this example, the LIF named L018
is associated with the IPXPROTO process named $ZNV1.
Example 3-8. SCF INFO PROCESS
->SCF INFO PROCESS $ZNV1
IPXSPX Info PROCESS
Process Name
$ZNV1
Primary CPU
2
Backup CPU
3
*I/O Port Name
L018 IPXSNAP
I/O Port Type
802.3
Redirect or Stop Any Customer Applications Using the TRSA
To redirect or stop customer applications, perform the following steps:
1. Notify end users that applications will be temporarily unavailable.
Token-Ring Adapter Installation and Support Guide—426955-001
3-8
Replacing a TRSA
Stop the Communications Lines Using the TRSA
2. Perform any actions necessary to redirect or stop customer applications.
Note. The actions required to perform this step depend on your application.
Stop the Communications Lines Using the TRSA
To stop the communications lines that use the TRSA, perform the following steps:
To Stop a SNAX/TR Line
The following steps describe stopping a SNAX/TR line.
1. Abort the SNAX/TR line.
Use the SCF ABORT LINE command:
ABORT LINE $line-name
2. Verify that the SNAX/TR line is in the STOPPED state.
Use the SCF STATUS LINE command:
STATUS LINE $line-name
Example 3-9 on page 3-9 shows the output of this command. Note that the
SNAX/TR ($TRS1) line is in the STOPPED state.
Example 3-9. SCF STATUS LINE Command
->STATUS LINE $TRS1
SNAX Status LINE
Name
$TRS1
State
STOPPED
Inuse
OFF
LinState
INACTIV
3. Stop the WAN IOP.
Use the SCF STOP DEVICE command:
STOP DEVICE $ZZWAN.#line-name
4. Verify that the WAN subsystem IOP is stopped.
Use the SCF STATUS DEVICE command:
STATUS DEVICE $ZZWAN.#line-name
To Stop an IPXPROTO Process
The following describes stopping an IPXPROTO process.
1. Stop the IPXPROTO process.
Token-Ring Adapter Installation and Support Guide—426955-001
3-9
Replacing a TRSA
Stop the Communications Lines Using the TRSA
a. If the IPXPROTO process is configured as a generic process, use the Kernel
subsystem SCF ABORT PROCESS command:
ABORT PROCESS $ZZKRN.#gpname
b. If the IPXPROTO process is not configured as a generic process, use the SLSA
subsystem SCF STOP PROCESS command:
STOP PROCESS $process-name
2. Verify that the IPXPROTO process is in the STOPPED state.
Use the SCF STATUS PROCESS command:
STATUS PROCESS $process-name
Example 3-10 shows the output of this command. Note that the IPXPROTO
process is in the STOPPED state.
Example 3-10. SCF STATUS PROCESS Command
->STATUS PROCESS $ZNV2
IPXSPX Status PROCESS
Process Name
$ZNV2
State
STOPPED
Diagnostic State
NORMAL
Trace
OFF
To Stop a Port Access Method (PAM) Line
The following describes stopping a PAM line.
1. Stop the PAM line.
Use the SCF STOP command with the SUB ALL option. The SUB ALL option
aborts the LINE object and all subordinate objects.
STOP LINE $line-name, SUB ALL
2. Verify that the PAM line is in the STOPPED state.
Use the SCF STATUS LINE command.
STATUS LINE $line-name
Example 3-11 shows the output of this command. Note that the PAM line
($TOK1) is in the STOPPED state.
Example 3-11. SCF STATUS LINE Command
-->STATUS LINE $TOK1
PAM Status LINE
Name
$TOK1
Primary
State CPU
PIN
STOPPED
1
278
CPU
Backup
PIN
-1
-1
Trace
OFF
Token-Ring Adapter Installation and Support Guide—426955-001
3-10
Replacing a TRSA
Determine the Physical Location of the TRSA
To Stop a TCP/IP Subnet
Caution. Make sure that the TACL session from which you are issuing SCF commands is not
running on the subnet that you are about to stop.
Note. To stop and verify a TCP/IP subnet that is configured using Parallel Library TCP/IP, refer
to the TCP/IP (Parallel Library) Configuration and Management Manual.
1. Stop the TCP/IP subnet.
Use the SCF STOP SUBNET command:
STOP SUBNET $tcpip-process-name.#subnet-name
2. Verify that the TCP/IP subnet is in the STOPPED state.
Use the SCF STATUS SUBNET command:
STATUS SUBNET $tcpip-process-name.#subnet-name
Example 3-12 shows the output of this command. Note that the subnet is in the
STOPPED state.
Example 3-12. SCF STATUS SUBNET Command
TCPIP Status SUBNET \COWBOY.$ZTC01.#SN2
Name
#SN2
Status
STOPPED
Determine the Physical Location of the TRSA
To determine the physical location of the a TRSA
1. Use the SCF INFO ADAPTER command:
INFO ADAPTER $ZZLAN.adapter-name
Example 3-13 shows the output of this command. Note that, for this example,
the Token-Ring ServerNet adapter (TRSA) CRU named E0153 is located in
group 1, module 1, slot 53.
2. Scan the output of the command for the group, module, and slot location.
Example 3-13. SCF INFO ADAPTER Command
--> INFO ADAPTER $ZZLAN.E0153
SLSA info ADAPTER
Name
$ZZLAN.E0153
Group
1
Module
1
Slot
53
Token-Ring Adapter Installation and Support Guide—426955-001
3-11
Type
TRSA
Replacing a TRSA
Abort the TRSA
.
Note. If Token-Ring ServerNet adapters (TRSAs) are named using the Compaq
Manufacturing naming convention, you can easily identify the physical location of the TRSA by
its name as follows:
$ZZLAN.Ecabid-slot
where cabid is the two-digit number that identifies the enclosure and slot is the actual
physical slot number in the enclosure. For example, the TRSA named E0153 is located in
enclosure 01, slot 53. (See Manufacturing Naming Conventions on page 1-9.)
Abort the TRSA
To abort a TRSA, perform the following steps:
1. Stop access to the logical interface (LIF) associated with the Token-Ring ServerNet
adapter (TRSA) CRU to be replaced.
Use the SCF ABORT LIF command:
ABORT LIF $ZZLAN.lif-name
2. Verify that the LIF associated with the TRSA to be replaced is in the STOPPED
state.
Use the SCF STATUS LIF command:
STATUS LIF $ZZLAN.lif-name
Example 3-14 shows the output of this command. Note that the logical interface
(LIF) is in the STOPPED state.
Example 3-14. SCF STATUS LIF Command
->STATUS LIF $ZZLAN.L018
SLSA Status LIF
Name
$ZZLAN.L018
State
STOPPED
Access State
UP
3. Abort the TRSA object and its subordinate objects. You can use either SCF or the
TSM Service Application to perform this step.
a. Use the SCF ABORT ADAPTER command with the SUB ALL option to abort
the adapter:
ABORT ADAPTER $ZZLAN.adapter-name, SUB ALL
The SUB ALL option stops the ADAPTER object and its subordinate objects.
a. Using the TSM Service Application to Abort the adapter:
1. Log on to the TSM Service Application
2. In the Tree view, select the TRSA.
Token-Ring Adapter Installation and Support Guide—426955-001
3-12
Replacing a TRSA
Label the Communications Cable Connected to the
TRSA
3. From the Display menu, choose Actions.
4. Select Abort.
5.
Click Perform action.
1. Verify that the TRSA ADAPTER object is in the STOPPED state.
Use the SCF STATUS ADAPTER command:
STATUS ADAPTER $ZZLAN.adapter-name
Example 3-15 shows the output of this command. Note that the ADAPTER (EO153)
is in the STOPPED state.
Example 3-15. SCF STATUS ADAPTER Command
-->STATUS ADAPTER $ZZLAN.E0153
SLSA
Status
ADAPTER
Name
$ZZLAN.E0153
State
STOPPED
Label the Communications Cable Connected to the TRSA
To label the communication cable for a TRSA:
1. Find group, module, and slot in which the Token-Ring ServerNet adapter (TRSA) is
installed.
Figure 3-2 shows the TRSA slot locations.
Token-Ring Adapter Installation and Support Guide—426955-001
3-13
Replacing a TRSA
Label the Communications Cable Connected to the
TRSA
Figure 3-2. TRSA Slot Locations
Himalaya S-Series I/O Enclosures
(Service Side)
50
55
Himalaya S-Series Processor Enclosure
(Service Side)
50
55
51 52 53 54
51 52 53 54
56
I/O enclosures can use slots
51 through 54 for a TRSA.
56
Processor enclosures can only use
slots 53 and 54 for aTRSA.
CDT 057.CDD
2. Tag the communications cable connected to the TRSA with a label, preferably at
both ends. The label should include the following information:
•
•
•
The physical interface (PIF) name assigned to the line. For example, E0153.0.A.
A description of the equipment and connector to which the cable is to be
connected.
The slot location of the TRSA to which the cable is connected.
Token-Ring Adapter Installation and Support Guide—426955-001
3-14
Replacing a TRSA
Replace the TRSA
Replace the TRSA
The following paragraphs explain how to replace the TRSA. You must remove the
adapter, then replace it.
Table 3-2. Replacement Checklist
Step
Description
1.
Review Standard Operating Practices
2.
Remove the Adapter
3.
Inspect the New TRSA and Backplane
4.
Unpack and Install the New TRSA
5.
Check the Installation of the New TRSA
Note. Whenever you handle an Token-Ring ServerNet adapter (TRSA), you should
follow
standard operating practices to avoid damage to the equipment.
Review Standard Operating Practices
Standard operating practices include the following:
•
•
•
•
Work in an electrostatic discharge (ESD)protected environment.
Remove all metal accessories before working with electrical equipment.
Restrain any dangling items that can get caught in equipment.
Obtain an ESD protection kit and follow the directions that come with the kit.
Figure 3-3 illustrates an ESD protected environment.
Token-Ring Adapter Installation and Support Guide—426955-001
3-15
Replacing a TRSA
Review Standard Operating Practices
Figure 3-3. ESD Protected Environment
System Enclosure (Appearance Side)
ESD wriststrap clipped to
door latch stud (or to any
exposed, unpainted, metal
surface on the enclosure
frame.)
ESD wriststrap
with clip
ESD floor mats
ESD antistatic table mat.
Mat should be connected to a soft ground
(1 megohm min. to 10 megohm max.)
Clip 15 inch straight
ground cord to screw
on grounded outlet
cover.
CDT 002.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
3-16
Replacing a TRSA
Remove the Adapter
Remove the Adapter
The following steps describe how to remove the adapter:
1. Disconnect the communications cables from the TRSA.
2. Put on your electrostatic discharge (ESD) wriststrap and connect the grounding clip
securely to an exposed, unpainted, metal surface on the service side of the system
enclosure, such as the processor multifunction (PMF) adapter or I/O multifunction
(IOMF) adapter ventilation holes
Figure 3-4 on page 3-17 shows how to connect the grounding clip to the ventilation
holes on the PMF adapter or IOMF adapter.
Figure 3-4. Grounding Clip
Processor Multifunction (PMF) CRU or
I/O Multifunction (IOMF) CRU
Grounding
Clip
To Grounding
Wriststrap
CDT 081.CDD
3. Unlatch the ejector on the TRSA by pressing the blue-green tab on the ejector and
pulling the ejector outward to unseat the TRSA from the backplane.
4. Grasp the TRSA by its ejector in one hand and slowly pull the TRSA out of the slot
while supporting the bottom edge of the TRSA with the other hand.
Note. The TRSA weighs 6.75 pounds (3 kilograms).
Figure 3-5 shows how to pull the adapter out of the slot.
Token-Ring Adapter Installation and Support Guide—426955-001
3-17
Replacing a TRSA
Remove the Adapter
Figure 3-5. Removing a TRSA
CDT 059.CDD
5. Place the TRSA in an ESD protective bag and return it to its original packing
container.
Token-Ring Adapter Installation and Support Guide—426955-001
3-18
Replacing a TRSA
Inspect the New TRSA and Backplane
Inspect the New TRSA and Backplane
To inspect a TRSA:
Visually inspect the TRSA and the backplane connector for damage. Use a flashlight, if
necessary, to check for bent or broken pins. You can damage pins by bumping or
jamming the TRSA's shell against a surface, which can partially close the hole in the
connector-pin socket. If the TRSA has a damaged connector-pin socket, do not install it.
Caution. If you plug the TRSA that has a damaged socket into a slot, that TRSA's backplane
pins and the connectors on other adapter boards that are plugged into that slot can be
damaged. Moving a damaged board from slot to slot can damage other slots and other adapter
boards.
Unpack and Install the New TRSA
The following paragraphs describe how to unpack and install the new TRSA.
Unpack the TRSA
Note. Whenever you handle a TRSA, you should follow standard operating practices to avoid
damage to the equipment.
1. Put on the electrostatic discharge (ESD) wriststrap and attach the grounding clip to
the antistatic mat.
2. Place the package containing the TRSA on the antistatic mat.
3. Open the packing container and remove the TRSA
Caution. When
protective bag.
opening the packing container, be careful not to cut into the ESD
4. Disconnect the grounding clip of your ESD wriststrap from the antistatic mat and
connect it to an exposed, unpainted metal surface on the TRSA.
5. Grasp the TRSA by its ejector in one hand, support the bottom edge of the TRSA
with the other hand, and carry the TRSA to the service side of the system enclosure
and set it down.
Note. The TRSA weighs 6.75 pounds (3 kilograms).
6. Disconnect the grounding clip of your ESD wriststrap from the TRSA and connect it
to an exposed, unpainted, metal surface on the service side of the system enclosure,
such as the ventilation holes on the processor multifunction (PMF) adapter or I/O
multifunction (IOMF) CRU.
Figure 3-4 on page 3-17 shows how to connect the grounding clip to the ventilation
holes on the PMF adapter or IOMF adapter.
Token-Ring Adapter Installation and Support Guide—426955-001
3-19
Replacing a TRSA
Unpack and Install the New TRSA
Install the TRSA
The following explains how to insert the TRSA into the system enclosure.
1. With the ejector on the TRSA in the full-open position (Figure 3-6), grasp the TRSA
by the ejector with one hand and support the bottom edge of the TRSA with the
other hand (Figure 3-7 on page 3-21). Hold the TRSA so that its ejector is at the top
and insert the TRSA into the upper part of the carrier.
Figure 3-6. Ejector Shown in Full-Open Position
CDT500.CDD
2. Push the TRSA to the rear of the slot, but don't force it.
Caution. Apply equal pressure to both the top and bottom of the TRSA when pushing it into
the slot to avoid damaging the connector pins. If pins are damaged, both the TRSA and the
backplane (or enclosure) must be replaced.
Token-Ring Adapter Installation and Support Guide—426955-001
3-20
Replacing a TRSA
Unpack and Install the New TRSA
Figure 3-7. Installing a TRSA
CDT 058.CDD
3. Press the blue-green tab on the TRSA ejector and latch the ejector to seat the TRSA
against the backplane.
4. Disconnect the grounding clip of your ESD wriststrap from the enclosure.
5. Connect the communications cable to the TRSA. You can connect an RJ-45
connector to the Token-Ring Connector UTP port or a DB-9 connector to the
Token-Ring Connector STP port. See Figure 3-8 for connections.
Token-Ring Adapter Installation and Support Guide—426955-001
3-21
Replacing a TRSA
Unpack and Install the New TRSA
Figure 3-8. TRSA Hardware Connection
Power-ON LED
(green)
Fault LED
(amber)
The top two ports are non-functional
in this release of the hardware and
software.
Only early versions of the adapter
have these ports.
Token Ring Connector UTP (RJ-45)
Token Ring Connector STP (DB-9)
CDT090.CDD
Note. You can use only one connector at a time. The top two ports are non-functional for
the G05 and G06 releases of the hardware and software.
Token-Ring Adapter Installation and Support Guide—426955-001
3-22
Replacing a TRSA
Check the Installation of the New TRSA
Check the Installation of the New TRSA
To check the installation of a TRSA:
1. Make sure that the power-on LED (green light) is on.
Note. When the adapter is inserted, the fault LED (yellow) remains on until the service
processor has completed its start-up configuration; the fault LED also turns on when a
POST failure is detected.
Figure 3-9 on page 3-24 shows the location of the power-on LED and fault LED.
2. If the power-on LED (green light) does not come on, do one or both of the following
steps:
a. Reseat the TRSA.
b. Check the TRSA and backplane connector for damaged pins.
Note the Following Error Conditions
•
•
If the power-on LED does not come on after you reseat the TRSA, you must replace
the TRSA
If the TRSA or backplane connector have damaged pins, both the TRSA and
backplane (or enclosure) must be replaced. For backplane replacement instructions,
refer to the Himalaya S-Series Service Provider Supplement.
Token-Ring Adapter Installation and Support Guide—426955-001
3-23
Replacing a TRSA
Check the Installation of the New TRSA
Figure 3-9. TRSA External Indicators
Power-ON LED
(green)
Fault LED
(amber)
The top two ports are non-functional
in this release of the hardware and
software.
Only early versions of the adapter
have these ports.
CDT091.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
3-24
Replacing a TRSA
Resume Operations
Resume Operations
The following paragraphs describe starting the new TRSA:
Table 3-3. Resuming Operations Checklist
Step
Description
1.
Start the New TRSA
2.
Restart the Communications Lines
3.
Verify That the Communications Lines Are Started
4.
Resume Customer Applications
Start the New TRSA
Start the Token-Ring ServerNet adapter (TRSA) ADAPTER object and its subordinate
SAC and PIF objects.
You can use either SCF or the TSM Service Application to start the TRSA.
Using SCF to Start the TRSA
Use the SCF START ADAPTER command with the SUB ALL option. The SUB ALL
option starts the ADAPTER object and its subordinate objects.
START ADAPTER $ZZLAN.adapter-name, SUB ALL
Using the TSM Service Application to Start the TRSA
To use the TSM Service Application to start the adapter, do the following:
1.
Log on to the TSM Service Application.
2.
In the Tree view, select TRSA.
3.
From the Display menu, choose Actions.
4.
Select Start.
5.
Click Perform action.
Token-Ring Adapter Installation and Support Guide—426955-001
3-25
Replacing a TRSA
Start the New TRSA
Verify that Objects Are in the Started State
Use the following SCF STATUS commands:.
1. Verify that the TRSA object is in the STARTED state.
Use the SCF STATUS ADAPTER command:
STATUS ADAPTER $ZZLAN.adapter-name
Example 3-16 shows the output of the SCF STATUS ADAPTER command.Note
that the ADAPTER is in the STARTED state.
Example 3-16. SCF STATUS ADAPTER Command
-->STATUS ADAPTER $ZZLAN.E0153
SLSA Status ADAPTER
Name
$ZZLAN.E0153
State
STARTED
2. Verify that the ServerNet addressable controller (SAC) is in the STARTED state.
Use the SCF STATUS SAC command:
STATUS SAC $ZZLAN.adapter-name.*
Example 3-17 shows the output of the SCF STATUS SAC command. Note that the
ServerNet adressable controller (SAC) is in the STARTED state.
Example 3-17. SCF STATUS SAC Command
-> STATUS SAC $ZZLAN.E1053.*
SLSA Status SAC
Name
Owner
State
$ZZLAN.E1053.
0 0
STARTED
$ZZLAN.E1053.
1 0
STARTED
Trace Status
OFF
OFF
3. Verify that the physical interface (PIF) is in the STARTED state.
Use the SCF STATUS PIF command:
STATUS PIF $ZZLAN.adapter-name.*
Example 3-18 shows the output of the SCF STATUS PIF command. Note that the
physical interface (PIF) is in the STARTED state.
Example 3-18. SCF STATUS PIF Command
--> STATUS PIF $ZZLAN.E0153.*
SLSA Status PIF
Name
State
$ZZLAN.E0153.0.A
STARTED
Trace Status
OFF
Token-Ring Adapter Installation and Support Guide—426955-001
3-26
Replacing a TRSA
Start the New TRSA
4. Start the logical interface (LIF). Use the SCF START LIF command:
START LIF $ZZLAN.lif-name
5. Verify that the LIF is in the STARTED state.
Use the SCF STATUS LIF command:
STATUS LIF $ZZLAN.lif-name
Example 3-19 shows the output of the SCF STATUS LIF command. Note that the
logical interface (LIF) is in the STARTED state.
Example 3-19. SCF STATUS LIF Command
->STATUS LIF $ZZLAN.L018
SLSA Status LIF
Name
$ZZLAN.L018
State
STARTED
Access State
UP
Troubleshooting: If the TRSA SAC Object Remains in the
STARTING State
If the SCF STATUS SAC command shows that the TRSA SAC object is still in the
STARTING state after a few minutes or if the TSM Service Application indicates that
the resource needs attention, you should check for event messages in the Event
Management System (EMS) log. Perform the following steps:
1. Use the TSM EMS Event Viewer Application to view the EMS log:
a. From the File menu, select Log on.
b. Select the system.
c. Type the NonStop™ Kernel user name and password.
d. Click OK.
e. From the Setup menu, set up Timeframe, Source, or Subsystem criteria, or all
three.
Refer to the Operator Messages Manual for cause, effect, and recovery information
for event messages.
2. Check the firmware version of the new TRSA. (When the AUTOFIRMUP attribute
is set to ON, which is the default, the firmware file is automatically downloaded to
the SAC when the SAC is started. Although the firmware version is automatically
updated by the system, you should verify the firmware version.)
Use the TSM Service Application to check the firmware version:
a. Log on to TSM Service Application
b. From the Display menu, choose Firmware Update.
Token-Ring Adapter Installation and Support Guide—426955-001
3-27
Replacing a TRSA
Restart the Communications Lines
c. From the Resource type pull-down menu, select the resource type.
d. From the Display pull-down menu, select Down-rev only.
A list of resources whose firmware is older than the version of the SYSnn is
displayed in the Available list box. Do the following:
e. Double-click on the resource. The resource is displayed in the Selected list
box.Choose
f.
Perform action to update the firmware.
Restart the Communications Lines
Perform the following commands to start the communications lines.
1. Start the TCP/IP subnet.
Note. To start TCP/IP subnets that are configured using Parallel Library TCP/IP, refer to the
TCP/IP (Parallel Library) Configuration and Management Manual.
Use the SCF START SUBNET command:
START SUBNET $tcpip-process-name.#subnet-name
2. Start an IPXPROTO process.
Use the SCF START PROCESS command:
START PROCESS $process-name
3. Start a Port Access Method (PAM) line.
Use the SCF START LINE command with the SUB ALL option:
START LINE $line-name, SUB ALL
4. To start a SNAX/TR line, perform the following steps:
a. Start the WAN subsystem input/output process (IOP).
Use the SCF START DEVICE command:
START DEVICE $ZZWAN.#device-name
b. Start the SNAX/TR line.
Use the SCF START LINE command:
START LINE $line-name
Token-Ring Adapter Installation and Support Guide—426955-001
3-28
Replacing a TRSA
Verify That the Communications Lines Are Started
Verify That the Communications Lines Are Started
Perform the following steps to make sure that the communications lines that use the
TRSA are started
1.
Verify that the TCP/IP subnet is started.
Note. To verify a TCP/IP subnet that is configured using Parallel Library TCP/IP, refer to the
TCP/IP (Parallel Library) Configuration and Management Manual.
Use the SCF STATUS SUBNET command:
STATUS SUBNET $tcpip-process-name.#subnet-name
Example 3-19 shows the output of this command. Note that the TCP/IP subnet
(#SN2) is in the STARTED state.
Example 3-20. SCF STATUS SUBNET Command
->STATUS SUBNET $ZTC01.#SN2
TCPIP Status SUBNET \COWBOY.$ZTC01.#SN2
Name
#SN2
Status
STARTED
2. Verify that an IPXPROTO process is started,.
Use the SCF STATUS PROCESS command:
STATUS PROCESS $process-name
Example 3-21 shows the output of this command. Note that the IPXPROTO process
($ZNV2) is in the STARTED state.
Example 3-21. SCF STATUS PROCESS Command
->STATUS PROCESS $ZNV2
IPXSPX Status PROCESS
Process Name
State
$ZNV2
STARTED
Diagnostic State
NORMAL
Trace
OFF
3. Verify that a Port Access Method (PAM) line is started.
use the SCF STATUS LINE command:
STATUS LINE $line-name
Example 3-22 shows the output of this command. Note that the Port Access Method
(PAM) line ($TOK1) is in the STARTED state
Example 3-22. SCF STATUS LINE Command
->STATUS LINE $TOK1
Name
$TOK1
State
STARTED
Primary
CPU
1
PIN
278
Backup
CPU
-1
PIN
-1
TRACE
OFF
Token-Ring Adapter Installation and Support Guide—426955-001
3-29
Replacing a TRSA
Troubleshooting: If an Object is Not in the STARTED
State
4. Verify that the SNAX/TR line is in the STARTED state.
Use the SCF STATUS LINE command:
STATUS LINE $line-name
Example 3-23 shows the output of this command. Note that the SNAX/TR line
($TRS1) is in the STARTED state
Example 3-23. SCF STATUS LINE Command
->STATUS LINE $TRS1
SNAX Status LINE
Name
$TRS1
State
STARTED
Inuse
OFF
LinState
INACTIV
Troubleshooting: If an Object is Not in the STARTED State
If an object is not in the STARTED state, check for event messages in the Event
Message Service (EMS) log. Use the TSM EMS Event Viewer Application to view the
EMS log:
1. From the File menu, select Log on.
2.
Select the system.
3. Type the NonStop™ Kernel user name and password.
4. Click OK.
5. From the Setup menu, select Timeframe, Source, or Subsystem criteria, or all three.
Refer to the Operator Messages Manual for cause, effect, and recovery information for
event messages.
Resume Customer Applications
To resume customer applications, perform the following:
1. Perform any actions necessary to resume customer applications.
Note. The actions required to perform this step depend on the customer's application.
2. Notify end users that applications are now available.
Token-Ring Adapter Installation and Support Guide—426955-001
3-30
4
Relocating a TRSA
This section describes how to relocate a Token-Ring SeverNet adapter (TRSA) that has
been previously installed in a Compaq NonStop™ Himalaya S-series system enclosure.
Note. A TRSA can be relocated without shutting down the system.
Caution. If a previously installed TRSA and backplane connector have damaged pins, remove
the TRSA and install a filler panel in the vacant slot. Attach red tags to the filler panel to identify
the slot. Do not move the damaged TRSA to a different, undamaged slot. Both the TRSA and
backplane (or enclosure) must be replaced. For backplane replacement, refer to the backplane
replacement section of the Himalaya S-Series Service Provider Supplement available in
G-series Total Information Manager (TIM) collections.
Removal and relocation of the TRSA is described in the following subsections:
Prepare to Relocate the TRSA
Page 4-2
Remove and Install the TRSA
Page 4-16
Resume Operations
Page 4-24
Note. Whenever you handle the TRSA, you should follow standard operating practices to
avoid damage to the equipment. See Review Standard Operating Practices on page 4-16.
Token-Ring Adapter Installation and Support Guide—426955-001
4-1
Relocating a TRSA
Prepare to Relocate the TRSA
Prepare to Relocate the TRSA
TRSAs can be installed in slots 53 and 54 of a processor enclosure and in slots 51, 52,
53, and 54 of an I/O enclosure. See Figure 4-2 on page 4-15. When no TRSA is installed
in a slot, a ServerNet adapter filler panel occupies the empty slot. (Therefore, a
ServerNet adapter filler panel might occupy slots 53 and 54 of a processor enclosure or
slots 51 through 54 of an I/O enclosure.) The filler panel maintains proper air flow and
reduces electromagnetic interference (EMI).
Table 4-1 summarizes the important steps for preparing to relocate the TRSA.
Table 4-1. Preparation Checklist
Step
Description
Comments
1.
Gather the Proper Tools
2.
Print the TRSA Planning Worksheet
3.
Identify Any Communications Lines Using the TRSA
4.
Redirect or Stop Any Customer Applications Using the
TRSA
5.
Stop the Communications Lines Using the TRSA
6.
Determine the Physical Location of the TRSA
7.
Stop the TRSA
8.
Label the Communications Cable Connected to the TRSA
See Figure 4-1 on
page 4-3.
Gather the Proper Tools
You will need the following tools to remove and relocate an adapter:
Tool
Used to. . .
Electrostatic discharge (ESD)
wriststrap with grounding clip
Protect the adapter from damage caused by electrostatic
discharge.
Antistatic mat (recommended)
Provide a static-free environment for removal and
installation of an adapter.
Flashlight
Check the connectors for bent or broken pins.
Note. An ESD protection kit can be purchased from Compaq using the following order number
and part number:
Order Number: ESD-Kit
Part Number: T99247-A00
Token-Ring Adapter Installation and Support Guide—426955-001
4-2
Relocating a TRSA
Print the TRSA Planning Worksheet
Print the TRSA Planning Worksheet
Make a copy of Figure 4-1, TRSA Planning Worksheet and use it to record information
about the TRSA.
Figure 4-1. TRSA Planning Worksheet
TRSA Planning Worksheet
Print this worksheet and use it to record information about a Token-Ring ServerNet adapter (TRSA).
Logical interface (LIF) and Physical Interface (LIF):
LIF:
PIF:
TCP/IP Process, Subnet, and Internet Protocol (IP) Address
TCP/IP Process:
Subnet:
IP Address:
Port Access Method (PAM) Line:
PAM Line:
SNAX/TR Line:
PAM Line:
SNAX/TR Line:
IPXPROTO Process :
IPXPROTO Process:
CDT040.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
4-3
Relocating a TRSA
Identify Any Communications Lines Using the TRSA
Identify Any Communications Lines Using the TRSA
The subsystems and utilities that use the SLSA subsystem to access an TRSA are
illustrated in Figure 1-2.
Note. SNAX/XF and SNAX/APN lines that use token-ring connections are referred to as
SNAX/TR lines in the following procedure.
Use the following procedure to help you identify the subsystems and utilities that are
configured to use a TRSA. Specific instructions are provided for identifying SNAX/TR
lines.
Note. Make a note of the information you obtain during this procedure. You can record this
information on the planning worksheet provided or you can use the SCF LOG command to
capture both the command and the display to a file. To start logging, type LOG logfilename
at the SCF prompt. To stop logging, type LOG at the SCF prompt.
Perform the following steps:
1. Determine the name of the logical interface (LIF) and physical interface (PIF)
associated with the TRSA to be relocated.
a. Use the SCF INFO LIF command:
->SCF INFO LIF $ZZLAN.*
b. Scan the output of the command for the name of the TRSA to be relocated.
Make a note of the LIF name and PIF name.
Example 4-1 shows the output of this command. The Logical interface (LIF)
name is shown in the Name column and the physical interface (PIF) name is
shown in the PIF column. The name of the Token-Ring ServerNet adapter
(TRSA) CRU is the first part of the PIF name (for example, E0153).
The PIF name indicates the physical port on the TRSA. For example, the PIF
named E0153.1.A. identifies the UTP (RJ-45) port on the TRSA named E0153.
In this example, the LIF associated with the TRSA named E0153 is named
L018.
Example 4-1. SCF INFO LIF Command
-->INFO LIF $ZZLAN.*
SLSA info LIF
Name
$ZZLAN
PIF
E0153.1.A
MAC Address
08:00:8E:00:5C:85
Type
Token Ring
2. Determine the TCP/IP processes, subnets, and Internet Protocol (IP) addresses
associated with the LIF for the TRSA to be relocated.
a.
Use the SCF INFO SUBNET command:
->INFO SUBNET $*.*
b. Scan the output of the command for the LIF you identified in Step 1 and then
find the associated TCP/IP process, subnet, and IP address. Make a note of this
Token-Ring Adapter Installation and Support Guide—426955-001
4-4
Relocating a TRSA
Identify Any Communications Lines Using the TRSA
information on the Record this information on the TRSA Planning Worksheet
on page 4-3.
c. Example 4-2 shows the output of this command. Use the following information
to help interpret the display:
The TCP/IP process name is displayed in the first line of output (for example,
$ZTC01).
The subnet name is displayed in the Name column (for example, #SN1).
The logical interface (LIF) name is displayed in the Devicename column (for
example, $L018).
The Internet Protocol (IP) address is displayed in the *IPADDRESS column
(for example, 172.16.35.15).
Note. You can easily check for Token-Ring ServerNet adapter (TRSA) CRU subnets by
looking in the TYPE column. The TRSA subnets are displayed as type SNAP.
In Example 4-2, which is partial output, the TRSA LIF named L018 is associated
with the subnet named #SN1 on the TCP/IP process named $ZTC01 and has the IP
address 172.16.35.15.
Example 4-2. SCF INFO SUBNET Command
->INFO SUBNET $*.*
TCPIP Info SUBNET \JULIE.$ZTC01.*
Name
Devicename
#LOOP0 \NOSYS.$NOIOP
#SN1
\JULIE.$L018
*IPADDRESS
127.0.0.1
172.16.35.15
TYPE
*SUBNETMASK
SuName QIO *R
LOOP-BACK %HFF000000
SNAP
%HFFFFFF00
OFF
ON
N
N
3. Identify the PAM lines configured on the system. Use the SCF NAMES command:
NAMES $ZZPAM
Example 4-3 on page 4-6 shows the output of this command. Port Access Method
(PAM) line names are shown under the LINE heading. In this example, which is
partial output, one PAM line is configured named $TOK1.
Token-Ring Adapter Installation and Support Guide—426955-001
4-5
Relocating a TRSA
Identify Any Communications Lines Using the TRSA
Example 4-3. SCF NAMES Command
->NAMES $ZZPAM
PAM Names PROCESS \SAMCAT.$ZZPAM
PROCESS
$TOK1 $ZZPAM
LINE
$TOK1
PORT
$TOK1.#L1P0002
$TOK1.#L1P0004
MSAP
$TOK1.#SNATR
4. Determine the PAM lines associated with the LIF on the TRSA to be relocated.
a. Use the SCF INFO LINE command for each PAM line you identified in Step 3:
INFO LINE $line-name
b. Check the output for the LIF on the TRSA to be relocated. On the TRSA
Planning Worksheet on page 4-3, record the PAM lines associated with the LIF
on the TRSA.
Example 4-4 shows the output of this command. The LIF name is shown in the
LIF NAME column. The type of CRU is shown in the LIF TYPE column. The
LIF type is TR. In this example, the TRSA LIF named L01C is associated with
the PAM line named $TOK1.
Example 4-4. SCF INFO LINE Command
->SCF INFO LINE $TOK1
PAM Info LINE
Name
$TOK1
MAXREQUESTSIZE
3200
LIF NAME
L01C
LIF TYPE
TR
LIF MAC ADDRESS
08:00:8E:00:D1:95
5. Identify the SNAX/TR lines configured on the system. Use the following SCF
LISTDEV command to display the SNAX/TR lines:
LISTDEV TYPE 58,4
In Example 4-5, two SNAX/TR lines, one named $TRS1 and one named $TRS2, are
configured on the system.
Example 4-5. SCF LISTDEV Command
->LISTDEV TYPE 58,4
LDev Name PPID
109 $TRS1 3,9
159 $TRS2 0,16
BPID
2,7
1,15
Type Rsize Pri
(58,4)
3 199
(58,4)
3 199
Program
\COWBOY.$DATA00.T9057ADJ.SNATSOBJ
\COWBOY.$DATA00.T9057ADJ.SNATSOBJ
Token-Ring Adapter Installation and Support Guide—426955-001
4-6
Relocating a TRSA
Identify Any Communications Lines Using the TRSA
6. Determine if any SNAX/TR lines configured on the system use the TRSA to be
relocated.
a.
Use the SCF INFO LINE command with the SUB PU and
ASSOCIATESUBDEV options for each SNAX/TR line you identified in Step
5:
INFO LINE $line-name, SUB PU, ASSOCIATESUBDEV
b. Scan the output of the command for the names of the PAM lines you identified
in Step 4. On the TRSA Planning Worksheet on page 4-3, record the SNAX/TR
lines that use the PAM lines.
Example 4-6 shows the output of this command. The AssociateSubDev
attribute shows the name of the PAM line associated with the SNAX/TR line. The
SNAX/TR line named $TRS1 is associated with the PAM line named $TOK1.
Example 4-6. SCF INFO LINE Command with SUB PU and ASSOCIATESUBDEV
Options
->INFO LINE $TRS1, SUB PU, ASSOCIATESUBDEV
SNAX Detailed Info PU \CHIP.$TRS1.#P041
AssociateSubDev.. \CHIP.$TOK1.#PO41
SNAX Detailed Info PU \CHIP.TRS1.#P042
AssociateSubDev.. \CHIP.$TOK1.#P042
SNAX Detailed Info PU \CHIP.TRS1.#P083
AssociateSubDev.. \CHIP.$TOK1.#P083
SNAX Detailed Info PU \CHIP.TRS1.#P084
AssociateSubDev.. \CHIP.$TOK1.#P084
7. Identify the IPXPROTO processes configured on the system.
Use the SCF NAMES SUBSYS command:
NAMES SUBSYS $ZMGR
Example 4-7 on page 4-8 shows the output of this command. IPXPROTO
process names are shown under the PROCESS heading. The two configured
IPXPROTO processes are named $ZNV0 and $ZNV1.
Token-Ring Adapter Installation and Support Guide—426955-001
4-7
Relocating a TRSA
Identify Any Communications Lines Using the TRSA
Example 4-7. SCF NAMES SUBSYS Command
->NAMES SUBSYS $ZMGR
IPXSPX Names SUBSYS \HIMA.$ZMGR
SUBSYS
$ZMGR
PROCESS
$ZNV0
SERVER
$ZNV0.#SAP
PROCESS
$ZNV1
SERVER
$ZNV1.#SAP
8. Determine the IPXPROTO processes associated with the LIF on the TRSA to be
relocated.
Note. The usual form for IPXPROTO process names is $ZNVn, where n is an
alphanumeric character from 0 through 9 or A through Z.
a. Use the SCF INFO PROCESS command for each IPXPROTO process you
identified in Step 7:
INFO PROCESS $process-name
b. SCAN the output for the LIF you identified in step 1, then find the associated
IPXPROTO processes. Make a note of the !PXPROTO process name associated
with the LIF on the TRSA.
Example 4-8 on page 4-8 shows the output of this command. The LIF name is
shown in the I/O Port Name column. In this example, the LIF named L018
is associated with the IPXPROTO process named $ZNV1.
Example 4-8. SCF INFO PROCESS Command
->SCF INFO PROCESS $ZNV1
IPXSPX Info PROCESS
Process Name
$ZNV1
Primary CPU
2
Backup CPU
3
*I/O Port Name
L018 IPXSNAP
I/O Port Type
802.3
Token-Ring Adapter Installation and Support Guide—426955-001
4-8
Relocating a TRSA
Redirect or Stop Any Customer Applications Using
the TRSA
Redirect or Stop Any Customer Applications Using the TRSA
To redirect or stop customer applications, perform the following steps:
1. Notify end users that applications will be temporarily unavailable.
2. Perform any actions necessary to redirect or stop customer applications.
Note. The actions required to perform this step depend on the customer’s application.
Stop the Communications Lines Using the TRSA
To stop the communications lines that use the TRSA, perform the following steps:
To Stop a SNAX/TR Line
The following steps describe stopping a SNAX/TR line.
1. Abort the SNAX/TR line.
Use the SCF ABORT LINE command:
ABORT LINE $line-name
2. Verify that the SNAX/TR line is in the STOPPED state.
Use the SCF STATUS LINE command:
STATUS LINE $line-name
Example 4-9 shows the output of this command. Note that the SNAX/TR ($TRS1)
line is in the STOPPED state.
Example 4-9. SCF STATUS LINE Command
->STATUS LINE $TRS1
SNAX Status LINE
Name
$TRS1
State
STOPPED
Inuse
OFF
LinState
INACTIV
3. Stop the WAN IOP.
Use the SCF STOP DEVICE command:
STOP DEVICE $ZZWAN.#line-name
4. Verify that the WAN subsystem IOP is stopped.
Use the SCF STATUS DEVICE command:
STATUS DEVICE $ZZWAN.#line-name
Token-Ring Adapter Installation and Support Guide—426955-001
4-9
Relocating a TRSA
Stop the Communications Lines Using the TRSA
To Stop an IPXPROTO Process
The following describes stopping an IPXPROTO process.
1. Stop the IPXPROTO process.
a. If the IPXPROTO process is configured as a generic process, use the Kernel
subsystem SCF ABORT PROCESS command:
ABORT PROCESS $ZZKRN.#gpname
b. If the IPXPROTO process is not configured as a generic process, use the SLSA
subsystem SCF STOP PROCESS command:
STOP PROCESS $process-name
2. Verify that the IPXPROTO process is in the STOPPED state.
Use the SCF STATUS PROCESS command:
STATUS PROCESS $process-name
Example 4-10 shows the output of this command. Note that the IPXPROTO
process is in the STOPPED state.
Example 4-10. SCF STATUS PROCESS Command
->STATUS PROCESS $ZNV2
IPXSPX Status PROCESS
Process Name
$ZNV2
State
STOPPED
Diagnostic State
NORMAL
Trace
OFF
To Stop a Port Access Method (PAM) Line
The following describes stopping a PAM line.
1. Stop the PAM line.
Use the SCF STOP command with the SUB ALL option. The SUB ALL option
aborts the LINE object and all subordinate objects.
STOP LINE $line-name, SUB ALL
2. Verify that the PAM line is in the STOPPED state.
Use the SCF STATUS LINE command.
STATUS LINE $line-name
Example 4-11 shows the output of this command. Note that the PAM line
($TOK1) is in the STOPPED state.
Token-Ring Adapter Installation and Support Guide—426955-001
4-10
Relocating a TRSA
Determine the Physical Location of the TRSA
Example 4-11. SCF STATUS LINE Command
-->STATUS LINE $TOK1
PAM Status LINE
Name
$TOK1
Primary
State CPU
PIN
STOPPED
1
278
CPU
Backup
PIN
-1
-1
Trace
OFF
To Stop a TCP/IP Subnet
Caution. Make sure that the TACL session from which you are issuing SCF commands is not
running on the subnet that you are about to stop.
Note. To stop and verify a TCP/IP subnet that is configured using Parallel Library TCP/IP, refer
to the TCP/IP (Parallel Library) Configuration and Management Manual.
1. Stop the TCP/IP subnet.
Use the SCF STOP SUBNET command:
STOP SUBNET $tcpip-process-name.#subnet-name
2. Verify that the TCP/IP subnet is in the STOPPED state.
Use the SCF STATUS SUBNET command:
STATUS SUBNET $tcpip-process-name.#subnet-name
Example 4-12 shows the output of this command. Note that the subnet is in the
STOPPED state.
Example 4-12. SCF STATUS SUBNET Command
TCPIP Status SUBNET \COWBOY.$ZTC01.#SN2
Name
#SN2
Status
STOPPED
Determine the Physical Location of the TRSA
To determine the physical location of the a TRSA
1. Use the SCF INFO ADAPTER command:
INFO ADAPTER $ZZLAN.adapter-name
Example 4-13 shows the output of this command. Note that, for this example,
the Token-Ring ServerNet adapter (TRSA) CRU named E0153 is located in
group 1, module 1, slot 53.
2. Scan the output of the command for the group, module, and slot location.
Token-Ring Adapter Installation and Support Guide—426955-001
4-11
Relocating a TRSA
Stop the TRSA
Example 4-13. SCF INFO ADAPTER Command
--> INFO ADAPTER $ZZLAN.E0153
SLSA info ADAPTER
Name
$ZZLAN.E0153
Group
1
Module
1
Slot
53
Type
TRSA
When you know the physical location of the adapter, you can abort it by using SCF
commands.
Note. If Token-Ring ServerNet adapters (TRSAs) are named using the Compaq
Manufacturing naming convention, you can easily identify the physical location of the TRSA by
its name as follows:
$ZZLAN.Ecabid-slot
where cabid is the two-digit number that identifies the enclosure and slot is the actual
physical slot number in the enclosure. For example, the TRSA named E0153 is located in
enclosure 01, slot 53. (See Manufacturing Naming Conventions on page 1-9.)
Stop the TRSA
To stop an TRSA, perform the following:
1. Determine the name of the logical interface (LIF) associated with the TRSA to be
relocated.
Use the SCF INFO LIF command:
INFO LIF $ZZLAN.*
Example 4-14 shows the output of this command. The logical interface (LIF)
name is shown in the Name column and the physical interface (PIF) name is
shown in the PIF column. The name of the Token-Ring ServerNet adapter
(TRSA) CRU is the first part of the PIF name (for example, E0153).
The PIF name indicates the physical port on the TRSA. For example, the PIF
named E0153.0.A. identifies the UTP (RJ-45) port on the TRSA named E0153.
In this example, the LIF associated with the TRSA named E0153 is named
L018.
Example 4-14. SCF INFO LIF Command
->INFO LIF $ZZLAN.*
SLSA Info LIF
Name
$ZZLAN.L018
PIF
E0153.0.A
MAC Address
08:00:8E:00:5C:85
Type
Token Ring
Token-Ring Adapter Installation and Support Guide—426955-001
4-12
Relocating a TRSA
Stop the TRSA
2. Stop access to the logical interface (LIF) associated with the Token-Ring ServerNet
adapter (TRSA) to be relocated.
Use the SCF STOP LIF command for each LIF:
STOP LIF $ZZLAN.lif-name
If you receive a message that the LIF client is still active, use the SCF ABORT
LIF command to remove the LIF.
3. Verify that the LIF associated with the TRSA to be relocated is in the STOPPED
state.
Use the SCF STATUS LIF command:
STATUS LIF $ZZLAN.*
Example 4-15 shows the output of this command. Note that the logical interface
(LIF) is in the STOPPED state.
Example 4-15. SCF STATUS LIF Command
->STATUS LIF $ZZLAN.*
SLSA Status LIF
Name
$ZZLAN.L018
State
STOPPED
Access State
UP
4. Stop the TRSA object and its subordinate objects.
You can use either SCF or the TSM Service Application to perform this step.
a. Using SCF to Stop the Adapter:
Use the SCF STOP ADAPTER command with the SUB ALL option The SUB
ALL option stops the ADAPTER object and all its subordinate objects.
STOP ADAPTER $adapter-name, SUB ALL
b. Using the TSM Service Application to Stop the Adapter:
1. Log on to the TSM Service Application.
2. In the Tree view, select the TRSA.
3. From the Display menu, choose Actions.
4. Select Stop.
5. Click Perform action.
Token-Ring Adapter Installation and Support Guide—426955-001
4-13
Relocating a TRSA
Locate the New Slot
5. Verify that the TRSA ADAPTER object is in the STOPPED state.
Use the SCF STATUS ADAPTER command:
STATUS ADAPTER $adapter-name
Example 4-16 shows the output of this command. Note that the ADAPTER
(E0153) is in the STOPPED state.
Example 4-16. SCF STATUS ADAPTER Command
->STATUS ADAPTER $ZZLAN.E0153
SLSA Status ADAPTER
Name
$ZZLAN.E0153
State
STOPPED
Locate the New Slot
Find the group, module, and slot containing the TRSA you want to move and the empty
slot to which you want it moved. The empty slot contains a double-high filler panel.
(Figure 4-2 on page 4-15 shows the TRSA slot locations.)
Remove the double-high filler panel from the slot to which you want to move the TRSA.
Set the filler panel aside. You will reinstall the filler panel in the slot left vacant by the
TRSA you move.
Label the Communications Cable Connected to the TRSA
You now must label the communications cable for the TRSA. Perform the following
steps:
1. Use your worksheet with you to help find the physical locations of group, module,
and slot in which the TRSA is installed.
Figure 4-2 on page 4-15 shows the TRSA slot locations.
Token-Ring Adapter Installation and Support Guide—426955-001
4-14
Relocating a TRSA
Label the Communications Cable Connected to the
TRSA
Figure 4-2. TRSA Slot Locations
Himalaya S-Series I/O Enclosures
(Service Side)
50
55
Himalaya S-Series Processor Enclosure
(Service Side)
50
55
51 52 53 54
51 52 53 54
56
I/O enclosures can use slots
51 through 54 for a TRSA.
56
Processor enclosures can only use
slots 53 and 54 for aTRSA.
CDT 057.CDD
2. Tag the communications cable connected to the TRSA with a physical label,
preferably at both ends. The label should include the following information:
•
•
•
The physical interface (PIF) name assigned to the line. For example, E0153.0.A.
A description of the equipment and connector to which the cable is to be
connected.
The slot location of the TRSA to which the cable is connected.
Token-Ring Adapter Installation and Support Guide—426955-001
4-15
Relocating a TRSA
Remove and Install the TRSA
Remove and Install the TRSA
The following subsections explain how to remove the TSRA re-install it in a new slot.
Table 4-2. Replacement Checklist
Step
Description
1.
Review Standard Operating Practices
2.
Remove and Install the Adapter
3.
Check the Installation of the Relocated TRSA
Review Standard Operating Practices
Standard operating practices include the following:
•
•
•
•
Work in an electrostatic discharge (ESD)protected environment.
Remove all metal accessories before working with electrical equipment.
Restrain any dangling items that can get caught in equipment.
Obtain an ESD protection kit and follow the directions that come with the kit.
Figure 4-3 on page 4-17 illustrates an ESD protected environment.
Token-Ring Adapter Installation and Support Guide—426955-001
4-16
Relocating a TRSA
Review Standard Operating Practices
Figure 4-3. ESD Protected Environment
System Enclosure (Appearance Side)
ESD wriststrap clipped to
door latch stud (or to any
exposed, unpainted, metal
surface on the enclosure
frame.)
ESD wriststrap
with clip
ESD floor mats
ESD antistatic table mat.
Mat should be connected to a soft ground
(1 megohm min. to 10 megohm max.)
Clip 15 inch straight
ground cord to screw
on grounded outlet
cover.
CDT 002.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
4-17
Relocating a TRSA
Remove and Install the Adapter
Remove and Install the Adapter
The following steps describe how to remove a TRSA and then install it in a new
location.
1. Disconnect the communications cables from the TRSA.
2. Put on your electrostatic discharge (ESD) wriststrap and connect the grounding clip
securely to an exposed, unpainted, metal surface on the service side of the system
enclosure, such as the processor multifunction (PMF) adapter or I/O multifunction
(IOMF) adapter ventilation holes.
Figure 4-4 shows how to connect the grounding clip to the ventilation holes on the
PMF adapter or IOMF adapter.
Figure 4-4. Grounding Clip
Processor Multifunction (PMF) CRU or
I/O Multifunction (IOMF) CRU
Grounding
Clip
To Grounding
Wriststrap
CDT 081.CDD
3. Unlatch the ejector on the TRSA by pressing the blue-green tab on the ejector and
pulling the ejector outward to unseat the TRSA from the backplane.
4. Grasp the TRSA by its ejector in one hand and slowly pull the TRSA out of the slot
while supporting the bottom edge of the TRSA with the other hand.
Note. The TRSA weighs 6.75 pounds (3 kilograms).
Token-Ring Adapter Installation and Support Guide—426955-001
4-18
Relocating a TRSA
Remove and Install the Adapter
Figure 4-5 shows how to pull the adapter out of the slot.
Figure 4-5. Removing a TRSA
CDT 059.CDD
5. Move the TRSA to the new slot.
a. Disconnect the grounding clip of your ESD wriststrap from the system
enclosure and connect to an exposed, unpainted surface on the TRSA.
b. Grasp the TRSA by its ejector in one hand, support the bottom edge of the
TRSA with the other hand. Carry the TRSA to the slot where it is to be installed.
Note. The TRSA weights 6.75 pounds (3 kilograms)
Token-Ring Adapter Installation and Support Guide—426955-001
4-19
Relocating a TRSA
Remove and Install the Adapter
6. Disconnect the grounding clip of your ESD wriststrap from the TRSA and connect it
to an exposed, unpainted, metal surface on the service side of the system enclosure,
such as the ventilation holes on the processor multifunction (PMF) adapter or I/O
multifunction (IOMF) CRU.
Figure 4-4 on page 4-18 shows how to connect the grounding clip to the ventilation
holes on the PMF or IOMF CRU.
7. With the ejector on the TRSA in the full-open position (Figure 4-6), grasp the TRSA
by the ejector with one hand and support the bottom edge of the TRSA with the
other hand (Figure 4-7 on page 4-21). Hold the adapter so that its ejector is at the
top, as shown in Figure 4-6, and insert the adapter into the upper part of the carrier.
Figure 4-6. Ejector Shown in Full-Open Position
CDT500.CDD
8. Push the TRSA to the rear of the slot, but don't force it.
Caution. Apply equal pressure to both the top and bottom of the TRSA when pushing it into
the slot to avoid damaging the connector pins. If pins are damaged, both the TRSA and the
backplane (or enclosure) must be replaced.
Token-Ring Adapter Installation and Support Guide—426955-001
4-20
Relocating a TRSA
Remove and Install the Adapter
Figure 4-7. Installing a TRSA
CDT 058.CDD
9. Press the blue-green tab on the TRSA ejector and latch the ejector to seat the TRSA
against the backplane.
10. Disconnect the grounding clip of your ESD wriststrap from the enclosure.
11. Install the double-high filler panel in the slot left vacant by the TRSA you moved.
12. Connect the communications cable to the TRSA. You can connect an RJ-45
connector to the Token-Ring Connector UTP port or a DB-9 connector to the
Token-Ring Connector STP port.
Token-Ring Adapter Installation and Support Guide—426955-001
4-21
Relocating a TRSA
Check the Installation of the Relocated TRSA
Check the Installation of the Relocated TRSA
1. Make sure that the power-on LED (green light) is on.
Note. When the adapter is inserted, the fault LED (yellow) remains on until the service
processor has completed its start-up configuration; the fault LED also turns on when a
POST failure is detected.
Figure 4-8 shows the location of the power-on LED and fault LED.
2. If the power-on LED (green light) does not come on, do one or both of the
following:
•
•
Reseat the TRSA.
Check the TRSA and backplane connector for damaged pins.
Note the Following Error Conditions
•
•
If the power-on LED does not come on after you reseat the TRSA, you must replace
the TRSA
If the TRSA or backplane connector have damaged pins, both the TRSA and
backplane (or enclosure) must be replaced. For backplane replacement instructions,
refer to the Himalaya S-Series Service Provider Supplement.
Token-Ring Adapter Installation and Support Guide—426955-001
4-22
Relocating a TRSA
Check the Installation of the Relocated TRSA
Figure 4-8. TRSA External Indicators
Power-ON LED
(green)
Fault LED
(amber)
The top two ports are non-functional
in this release of the hardware and
software.
Only early versions of the adapter
have these ports.
CDT091.CDD
Token-Ring Adapter Installation and Support Guide—426955-001
4-23
Relocating a TRSA
Resume Operations
Resume Operations
The following sections describe starting the relocated TRSA:
Table 4-3. Resuming Operations Checklist
Step
Description
1.
Complete the TRSA Configuration Form
2.
Add the TRSA Using SCF
Complete the TRSA Configuration Form
Complete a new configuration form for the relocated TRSA. Figure 4-9 on page 4-25
shows an example of a completed Token-Ring ServerNet Adapter (TRSA)
Configuration Form.
Identify the following information for the relocated TRSA:
•
•
•
The name you want to use to identify the adapter; for example, E0153 for a TokenRing adapter in slot 53 of the first system enclosure.
The location of the adapter within the system cabinet (group, module, and slot).
The processors that have access to the SACs on the adapter.
Obtain the form from Appendix A, TRSA Configuration Form, and enter the following
information:
•
•
•
•
•
•
The name of the system in the System Name field.
The group number for this enclosure in the Group Number field.
The slot number of this TRSA in the Slot Number field. TRSAs can be installed
in slots 51, 52, 53 and 54 of an I/O enclosure (expansion) but only 53 and 54 of
a processor enclosure.
Note that because there is exactly one module in a system or I/O enclosure, the
module number, 1, is already indicated on the form.
Enter the remaining information needed to install the TRSA:
•
•
•
•
•
The IP address.
The adapter name (See Manufacturing Naming Conventions on page 1-8).
The numbers of the processors that will have access to the SAC in the SAC
Access List field. The first processor listed is the preferred processor.
The PIF name associated with the SAC in the PIF Name field.
The LIF name associated with the PIF in the LIF Name field.
When you have completed this form, enter today’s date in the Date field.
Token-Ring Adapter Installation and Support Guide—426955-001
4-24
Relocating a TRSA
Complete the TRSA Configuration Form
Figure 4-9. Completed TRSA Configuration Form
Date
Group
SAC 1
ENET 1A:
\COWBOY
System Name
Token-RingServerNet Adapter (TRSA)
Configuration Form
01
IP Address:
Module
01
07
/
Slot
21
/
00
53
172.16.35.15
Adapter Name: E0153
SAC Name:
E0153 .0
SAC Access List: (1,0)
PIF Name:
E0153 .0.A
LIF Name:
L018
CDT 235
Token-Ring Adapter Installation and Support Guide—426955-001
4-25
Relocating a TRSA
Add the TRSA Using SCF
Add the TRSA Using SCF
Using the TRSA configuration form as a guide, use the SCF interface to the SLSA
subsystem to add and start the newly installed TRSA.
Note. Refer to the LAN Configuration and Management Manual for detailed information on the
SLSA subsystem SCF commands
The following steps outline adding and starting the relocated TRSA
1. Add the TRSA by using the SLSA subsystem SCF ADD ADAPTER command as
follows:.
->ASSUME PROCESS $ZZLAN
->ADD ADAPTER $ZZLAN.E1053, TYPE TRSA, LOCATION (1,1,53),
ACCESSLIST (0,1,2,3)
SCF adds an TRSA to slot 53, group 1, module 1, and gives processor 0 primary
access to the ServerNet addressable controller (SAC). Processors 1 through 3 are
assigned secondary access.
2. Use the SLSA subsystem SCF NAMES command to display the names assigned to
the SAC and PIF of the adapter you added in step 1.
->NAMES PIF $ZZLAN.E0153*
SLSA Names PIF \SYS.$ZZLAN.E0153
PIF
$ZZLAN.E0153.0.A
3. Assign a logical interface (LIF) to the PIF on the TRSA added in step 1 by using the
SLSA subsystem SCF ADD LIF command. Use the name of the PIF returned from
the NAMES command in step 2.
->ADD LIF $ZZLAN.L018, PIF E0153.0.A
4. Start the LIF by using the SLSA subsystem START LIF command.
->START LIF $ZZLAN.L018
5. Start the TRSA and its subordinate SAC and PIF objects by using the SLSA
subsystem SCF START ADAPTER command with the SUB ALL option as shown
in the following example. The SUB ALL option starts the ADAPTER object and its
subordinate objects:
->START ADAPTER $ZZLAN.E1053, SUB ALL
Note. You can also use the TSM Service Application to start an adapter. Refer to Using the
TSM Service Application to Start the TRSA on page 3-25.
6. Use the SLSA subsystem SCF STATUS commands to check that the adapter, SAC,
PIF, and LIF have started as shown in Example 4-17.
Token-Ring Adapter Installation and Support Guide—426955-001
4-26
Relocating a TRSA
Add the TRSA Using SCF
Example 4-17. SCF STATUS Commands
->STATUS ADAPTER $ZZLAN.E0153
SLSA Status ADAPTER
Name
State
$ZZLAN.E1053
STARTED
-> STATUS SAC $ZZLAN.E1053.*
SLSA Status SAC
Name
Owner
State
$ZZLAN.E1053.
0 0
STARTED
-> STATUS PIF $ZZLAN.E1053.*
SLSA Status PIF
Name
$ZZLAN.E1053.0.A
State
STARTED
-> STATUS LIF $ZZLAN.L01*
SLSA Status LIF
Name
$ZZLAN.L018
State
STARTED
Access State
UP
Note. There are many attributes for the SCF objects at this level. For example, the TokenRing speed could be 4 MB or 16 MB, and the node MAC address might be set as part of the
PIF configuration. You can use the SCF ALTER PIF command to change the PIF defaults.
Troubleshooting: If the TRSA SAC Object Is Still in the
STARTING State
If the SCF STATUS SAC command shows that the TRSA SAC object is still in the
STARTING state after a few minutes or if the TSM Service Application indicates that
the resource needs attention, do the following:
1. Check for event messages in the Event Message Service (EMS) log. Use the TSM
EMS Event Viewer Application to view the EMS log:
a. From the File menu, select Log on.
b. Select the system.
c. Type the NonStop™ Kernel user name and password.
d. Click OK.
e. From the Setup menu, set up Timeframe, Source, or Subsystem criteria.
Refer to the Operator Messages Manual for cause, effect, and recovery information
for event messages.
2. Check the firmware version of the new TRSA and update it. (When the
AUTOFIRMUP attribute is set to ON, which is the default, the firmware file is
automatically downloaded to the SAC when the SAC is started. Although the
firmware version is automatically updated by the system, you should verify the
firmware version.)
Use the TSM Service Application to check the firmware version:
Token-Ring Adapter Installation and Support Guide—426955-001
4-27
Relocating a TRSA
Add the TRSA Using SCF
a. Log on to the TSM Service Application.
b. From the Display menu, choose Firmware Update.
c. From the Resource type pull-down menu, select resource type.
d. From the Display pull-down menu, select Down-rev only.
A list of resources whose firmware is older than the version of the SYSnn is
displayed in the Available list box. Do the following:
e. Double-click on the resource. The resource is displayed in the Selected list box.
f.
Click Perform action to initiate the firmware update.
For information about configuring the conventional TCP/IP, Parallel Library TCP/IP,
IPX/SPX, or Port Access Method (PAM) subsystems to access the TRSA through the
SLSA subsystem, refer to the following manuals:
•
•
•
•
•
LAN Configuration and Management Manual
TCP/IP Configuration and Management Manual
TCP/IP (Parallel Library) Configuration and Management Manual
PAM Configuration and Management Manual
IPX/SPX Configuration and Management Manual.
Token-Ring Adapter Installation and Support Guide—426955-001
4-28
A
TRSA Configuration Form
This appendix contains a blank Token-Ring ServerNet Adapter (TRSA) configuration
form. It is recommended that you make copies of this form because you will need
several copies of this form when planning for a new system or for additions to a system.
You are authorized to photocopy this form only for the purpose of installing and
configuring your Compaq system.
Token-Ring Adapter Installation and Support Guide—426955-001
A-1
TRSA Configuration Form
Date
Group
SAC 1
ENET 1A:
\Case1
System Name
Token-RingServerNet Adapter (TRSA)
Configuration Form
01
Module
01
07
/
Slot
21
/
96
53
IP Address:
Adapter Name:
SAC Name:
SAC Access List:
PIF Name:
LIF Name:
CDT 234
Token-Ring Adapter Installation and Support Guide—426955-001
A-2
B
Preparing a TRSA for PMF or
IOMF CRU Replacement
The TRSA depends on X-fabric or Y-fabric communication from the PMF or IOMF
CRUs in the group of enclosures where the TRSA is installed. The fault tolerance of an
TRSA must be verified prior to replacing a PMF or IOMF CRU.
Note. For Compaq NonStop™ Himalaya S-series servers, replacing a PMF or IOMF CRU
can result in loss of access to the TRSA unless fault tolerance is ensured.
Note. The Guided Replacement Toolkit (GRT) is now the only supported method for replacing
a PMF or IOMF CRU. To access the GRT, start from the toolbar located on the desktop of your
TSM console. Navigate to the menus as follows:
START > Programs > TSM Client > Guided Replacement Tools > Guided Replacement
Toolkit
For information about the GRT, refer to the Guided Replacement Toolkit User’s Guide located
in the Help menu of the GRT.
To verify the fault tolerance of an TRSA, use the SLSA SCF STATUS SAC command
with the DETAIL option to
•
•
Verify that the Current Access list indicates access to more than one processor.
Verify that both the X and Y fabrics are UP.
The following display is an example of that returned by the STATUS SAC command
with the DETAIL option.
-> STATUS SAC $ZZLAN.EE1.0 , DETAIL
SLSA Detailed Status SAC \ABBY.$ZZLAN.EE1.0
Current Access...........
Last Download Time.......
Last Error...............
Owner CPU................
State....................
Trace Filename...........
Trace Status.............
( 1, 2, 3 )
27 JAN 2000, 7:11:49:662
(0, 0, 0)
1
STARTED
OFF
Fabric Status
CPU Accesslist
-------------1
2
3
Fabric-X
-------UP-PRIMARY
UP-PRIMARY
UP-PRIMARY
Fabric-Y
-------UP
UP
UP
Token-Ring Adapter Installation and Support Guide—426955-001
B-1
Preparing a TRSA for PMF or IOMF CRU
Replacement
Token-Ring Adapter Installation and Support Guide—426955-001
B-2
Safety and Compliance
Regulatory Compliance Statements
The following warning and regulatory compliance statements apply to the products documented
by this manual.
Warning (FCC)
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 interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
The use of shielded cables is required in order for this equipment to meet the FCC emission
limits. Exceptions: Ethernet and EPO cables.
CISPR Compliance
This equipment complies with the requirements of CISPR 22 (EN 55 022) for Class A
Information Technology Equipment (ITE). In a domestic environment this product may cause
radio interference in which case the user may be required to take adequate measures.
Canadian Compliance
This class A digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulations.
Cet appareil numérique de la classe A respecte toutes les exigences du Règelment sur le
matériel brouilleur du Canada.
Declaration of UK Conformity
Compaq Computer Corporation declares sole responsibility for ensuring that the Compaq host
systems into which the Compaq controller boards are installed, are in conformance with the
terms of the UK General Approval NS/G/1234/10003 by way of obtaining third-party test
house approval to EN 60 950.
COMPAQ PRODUCT SAFETY, Manager
CSA Certified to Canadian and US safety requirements by Canadian Standards Association
TUV-GS approved by TUV Rheinland
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-1
Safety and Compliance
Regulatory Compliance Statements
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-2
Safety and Compliance
Regulatory Compliance Statements
DECLARATION OF CONFORMITY
Supplier Name:
Supplier Address:
COMPAQ COMPUTER CORP.,
TANDEM DIVISION
Compaq Computer Corporation,
Tandem Division
10300 North Tantau Ave
Cupertino, CA 95014, USA
Represented in the EU By:
Compaq Computer EMEA GmbH
P.O. Box 81 02 44
81902 Munich, Germany
declares under our sole responsibility that the following product
Product Name:
Product Model No:
COMPAQ Himalaya S-series server
COMPAQ Model 195x, 196x, or 197x series where x is any number
conforms to the following normative European and International Standards.
Product Safety:
EN 60 950:1995 (IEC 950 2nd Edition)
Radio Frequency
EN 55 022:1994 (CISPR 22)
Interference:
Electromagnetic
EN 50 082-1:1991 (IEC 801-2, IEC 801-3, IEC 801-4)
Immunity:
following the provisions of the normative European Council Directives:
EMC Directive 89/336/EEC (including amendments)
Low Voltage Directive 73/23/EEC (amended by 93/68/EEC)
Supplementary Information:
Safety:
Emissions:
Year of Conformity
Assessment:
Protection Class [I], Pollution Degree II
EMC Class [A]
1999
Product conformance to cited product specifications is based on sample (type) testing, evaluation, or assessment at COMPAQ’s compliance laboratories in Cupertino, CA and at accredited laboratories accepted by European Union Notified and
Competent Bodies.
Chan Moore
Manager, Product Regulations
Cupertino, CA, USA, 1999
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-3
Safety and Compliance
Consumer Safety Statements
Consumer Safety Statements
Customer Installation and Servicing of Equipment
The following statements pertain to safety issues regarding customer installation and
servicing of equipment described in this manual.
•
•
Keep door closed for normal operation.
The equipment must be installed near the receptacles for the power cords, and the
receptacles must be easily accessible to the user.
WARNING. Do not touch the DC power connector on the S7400/S7x0000 PMF CRU after you
have unplugged the DC power cable from the CRU. It is possible to incur a severe energy
hazard for as long as fifteen (15) seconds after unplugging the cable. You can make sure the
CRU is safe to remove by testing (by using a volt meter) before touching the pins on the DC
power connector.
Applicability of Procedures, Instructions, and Examples
WARNING. The procedures and instructions and the examples of procedures and instructions
found in this manual apply only to the system enclosures and components found in Himalaya
S-series servers which are described in the Himalaya S-series server documentation. Do not
attempt to use these instructions with any other Compaq NonStop™ system equipment. You
can determine that your system is a Himalaya S-series server by reading the label that
appears inside each system enclosure on the CRU in slot 50 or 55. The label includes the
product number, 195x, 196x, or 197x. Read the label before proceeding with any procedure or
instruction found in this manual.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-4
Safety and Compliance
Consignes de sécurité à l'intention du client
Consignes de sécurité à l'intention du client
Installation et entretien du système par le client
Les consignes de sécurité qui suivent concernent l'installation et l'entretien par le client
du système décrit dans le présent manuel.
•
•
Garder la porte fermée pendant le fonctionnement normal du système.
Installer le système à proximité des prises de courant nécessaires à son branchement.
Ces prises doivent être faciles d'accès.
MISE EN GARDE. Ne pas toucher au connecteur d'alimentation C.C. de l'unité PMF
remplaçable par le client du S7400/S7x0000 après avoir débranché le cordon d'alimentation
C.C. de cette unité. Des risques de chocs électriques dangereux peuvent subsister pendant
quinze (15) secondes après le débranchement du câble. Lors de la dépose de l'unité, on
pourra confirmer l'absence de danger avec un voltmètre avant de toucher les broches du
connecteur d'alimentation C.C.
Applicabilité des procédures, des directives et des exemples
MISE EN GARDE. Les procédures et directives ainsi que les exemples y afférents contenus
dans le présent manuel concernent uniquement les boîtiers et pièces des serveurs Himalaya
série S décrits dans la documentation connexe. Elles ne sont applicables à aucun autre
système Compaq NonStop™. Pour savoir si votre serveur est un Himalaya de la série S,
consultez l'étiquette figurant à l'intérieur du boîtier du système sur l'unité remplaçable par le
client installée dans l'emplacement 50 ou 55. Cette étiquette indique le nombre de produit,
195x, 196x, ou 197x. Consultez cette étiquette avant d'exécuter l'une quelconque des
procédures ou directives prescrites dans le présent manuel.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-5
Safety and Compliance
Verbraucher-Sicherheitsangaben
Verbraucher-Sicherheitsangaben
Geräteinstallation und -wartung durch den Kunden
Die folgenden Angaben betreffen Sicherheitsfragen in Hinsicht auf die
Geräteinstallation und -wartung durch den Kunden, wie sie in diesem Handbuch
beschrieben werden.
•
•
Tür für normalen Betrieb geschlossen lassen.
Die Geräte müssen in der Nähe der Steckdosen für die Netzanschlußkabel installiert
werden, und die Steckdosen müssen für den Benutzer leicht zugänglich sein.
WARNUNG. Den Gleichstrom-Steckverbinder an der vom Kunden austauschbaren PMFEinheit des S7400/S7x0000 nicht berühren, nachdem das Gleichstromkabel von der vom
Kunden austauschbaren Einheit abgezogen wurde. Bis zu fünfzehn (15) Sekunden nach
Abziehen des Kabels besteht starke Elektroschockgefahr. Durch Prüfen (mit einem
Spannungsmesser) läßt sich vor Berührung der Stifte am Gleichstrom-Steckverbinder
feststellen, ob die vom Kunden austauschbare Einheit gefahrlos entfernt werden kann.
Anwendbarkeit von Verfahren, Anleitungen und Beispielen
WARNUNG. Die in diesem Handbuch enthaltenen Verfahren und Anleitungen und die
Beispiele von Verfahren und Anleitungen gelten nur für die in den Himalaya-S-Serie-Servern
vorgefundenen Systemgehäuse und Komponenten, die in der Dokumentation der Himalaya-SSerie-Server beschrieben werden. Versuchen Sie nicht, diese Anleitungen mit anderen
Compaq-NonStop™-System-Geräten zu benutzen. Sie können feststellen, daß Ihr System ein
Himalaya-S-Serie-Server ist, indem Sie den Aufkleber lesen, der sich im Innern eines jeden
Systemgehäuses befindet in der vom Kunden austauschbaren Einheit in Steckplatz 50 oder
55. Der Aufkleber soll die Produktnummer 195x, 196x, oder 197x angeben. Lesen Sie den
Aufkleber, bevor Sie mit irgendeiner der in diesem Handbuch enthaltenen Verfahren oder
Anleitungen fortfahren.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-6
Safety and Compliance
Declaraciones sobre la seguridad del consumidor
Declaraciones sobre la seguridad del consumidor
Instalación y servicio al equipo por el consumidor
Las siguientes declaraciones tienen que ver con aspectos de seguridad relacionados con
la instalación y servicio al equipo por el consumidor, y que se describen en este manual.
•
•
Mantenga la puerta cerrada durante la operación normal del equipo.
El equipo tiene que estar instalado cerca de los receptáculos de los cordones de
alimentación eléctrica, y dichos receptáculos tienen que ser de fácil acceso para el
usuario.
ADVERTENCIA. No toque el conector de alimentación de corriente directa en la unidad
reemplazable por el cliente S7400/S7x0000 PMF después de haber desenchufado el cable de
alimentación de corriente directa de dicha unidad. Es posible incurrir en un peligro grave
debido a la energía eléctrica hasta por unos quince (15) segundos después de haber
desenchufado el cable. Usted puede asegurarse de que la unidad reemplazable por el cliente
ya se pueda quitar sin problema alguno probándola (con un voltímetro) antes de tocar las
clavijas del conector de alimentación de corriente directa.
Forbrugersikkerhedsmeddelelser
Installation og service af udstyr der udføres af kunden
De følgende meddelelser vedrører sikkerheden angående installation og service af
udstyr, der udføres af kunden, som beskrives i denne brugerhåndbog.
•
•
Hold lugen lukket under normal drift.
Udstyret skal installeres i nærheden af stikkontakterne til netledningerne, og
stikkontakterne skal være let tilgængelige for brugeren.
ADVARSEL! Berør ikke jævnstrøms forbindelsesstikket på S7400/S7x0000 PMF-enheden,
der kan udskiftes af kunden, når du har afbrudt jævnstrøms netkablet fra enheden, der kan
udskiftes af kunden. Der er risiko for alvorligt stød i op til 15 sekunder efter, at kablet afbrydes.
Du kan sikre dig, at det er sikkert at fjerne enheden, der kan udskiftes af kunden, ved at teste
den (med et voltmeter), før du berører stifterne på jævnstrøms forbindelsesstikket.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-7
Safety and Compliance
Veiligheidsinstructies voor de consument
Veiligheidsinstructies voor de consument
Installatie en onderhoud van apparatuur door de klant
De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de
klant van de in deze handleiding beschreven apparatuur.
•
•
Houd bij normaal bedrijf de deur gesloten.
De apparatuur moet nabij contactdozen voor stroomkabels worden geïnstalleerd en
de contactdozen moeten voor de gebruiker gemakkelijk bereikbaar zijn.
WAARSCHUWING. Raak de gelijkstroomconnector op het S7400/S7x0000 PMF apparaat dat
door de klant kan worden vervangen, niet aan nadat de gelijkstroomkabel is losgekoppeld van
het door de klant vervangbare apparaat. Een ernstig energierisico kan nog wel vijftien (15)
seconden nadat de kabel is losgekoppeld, aanwezig zijn. Controleer of het door de klant
vervangbare apparaat veilig kan worden verwijderd door (met een spanningsmeter) een test uit
te voeren voordat u de pennen op de gelijkstroomconnector aanraakt.
Käyttöturvaa koskevia huomautuksia
Asiakkaan suorittama laiteasennus ja huolto
Seuraavat huomautukset koskevat turvallisuusnäkökohtia, jotka asiakkaan täytyy ottaa
huomioon tässä käsikirjassa kuvattuja laiteasennuksia ja huoltotoimenpiteitä
suoritettaessa.
•
•
Kansi täytyy pitää suljettuna normaalin käytön aikana.
Laitteisto täytyy asentaa lähelle virtapistokkeita, ja pistokkeiden tulee olla helposti
käytettävissä.
VAARA. Älä kosketa S7400/S7x0000 PMF vaihto-osan virtaliitintä heti sen jälkeen kun olet
irrottanut vaihto-osan tasavirtakaapelin. Vaarallista jännitettä voi olla jäljellä vielä viidentoista
(15) sekunnin kuluttua kaapelin irrottamisesta. Jännitemittarilla on mahdollista testata, onko
vaihto-osan tasavirtaliittimen pistokkeiden koskettaminen turvallista.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-8
Safety and Compliance
Veiligheidsinstructies voor de consument
Veiligheidsinstructies voor de consument
Installatie en onderhoud van apparatuur door de klant
De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de
klant van de in deze handleiding beschreven apparatuur.
•
•
Houd bij normaal bedrijf de deur gesloten.
De apparatuur moet nabij contactdozen voor stroomkabels worden geïnstalleerd en
de contactdozen moeten voor de gebruiker gemakkelijk bereikbaar zijn.
WAARSCHUWING. Raak de gelijkstroomconnector op het S7400/S7x0000 PMF apparaat dat
door de klant kan worden vervangen, niet aan nadat de gelijkstroomkabel is losgekoppeld van
het door de klant vervangbare apparaat. Een ernstig energierisico kan nog wel vijftien (15)
seconden nadat de kabel is losgekoppeld, aanwezig zijn. Controleer of het door de klant
vervangbare apparaat veilig kan worden verwijderd door (met een spanningsmeter) een test uit
te voeren voordat u de pennen op de gelijkstroomconnector aanraakt.
Misure precauzionali per i cliente
Installazione e manutenzione del sistema da parte del cliente
Le seguenti misure precauzionali riguardano l’installazione e la manutenzione da parte
del cliente del sistema descritto nel presente manuale.
•
•
Mantenere la porta chiusa durante il funzionamento normale del sistema.
Il sistema deve essere installato vicino alle prese di corrente che saranno usate per il
collegamento alla rete. Tali prese devono essere facilmente accessibili.
ATTENZIONE. Non toccare il connettore di corrente continua sull’unità sostituibile dal cliente
S7400/S7x0000 PMF dopo aver disinserito il cavo di corrente continua dall’unità stessa. Un
serio rischio elettrico può perdurare fino a 15 secondi dopo aver disinserito il cavo. È possibile
controllare con un voltmetro che l’unità sostituibile dal cliente possa essere rimossa con
sicurezza prima di toccare i piedini del connettore di corrente continua.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-9
Safety and Compliance
Informações de segurança para os consumidores
Informações de segurança para os consumidores
Instalação e manutenção do equipamento pelo cliente
As seguintes informações se referem a questões de segurança relacionadas à instalação e
manutenção, pelo cliente, do equipamento descrito neste manual.
•
•
Para garantir o funcionamento normal, mantenha a porta fechada.
O equipamento deve ser instalado próximo das tomadas, e o usuário deve ter acesso
fácil às tomadas.
AVISO. Não toque no conector de alimentação DC da Unidade Substituível pelo Cliente
(USC) S7400/S7x0000 PMF logo após ter desligado o cabo de alimentação DC da USC.
Existe a possibilidade de ocorrer um acidente elétrico sério até quinze (15) segundos após o
desligamento do cabo. Assegure-se de que é seguro remover a USC testando-a (ou usando
um medidor de voltagem), antes de tocar nos pinos do conector de alimentação DC.
Informações de segurança para os consumidores
Instalação e manutenção do equipamento pelo cliente
As seguintes informações referem-se a questões de segurança relacionadas à instalação e
manutenção, pelo cliente, do equipamento descrito neste manual.
•
•
Para garantir o funcionamento normal, mantenha a porta fechada.
O equipamento deve ser instalado próximo das tomadas, e o utilizador deve ter
acesso fácil às tomadas.
AVISO. Não toque no conector de alimentação DC da Unidade Substituível pelo Cliente
(USC) S7400/S7x0000 PMF logo após ter desligado o cabo de alimentação DC da USC.
Existe a possibilidade de ocorrer um acidente eléctrico sério até quinze (15) segundos após o
desligamento do cabo. Assegure-se de que é seguro remover a USC testando-a (ou usando
um medidor de voltagem), antes de tocar nos pinos do conector de alimentação DC.
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-10
Safety and Compliance
Meddelanden beträffande konsumentsäkerhet
Meddelanden beträffande konsumentsäkerhet
Kundutförd installation och service
De följande meddelandena beskriver säkerhetsföreskrifter för kundutförd installation
och service av utrustning som beskrivs i denna manual:
•
•
Dörren skall vara stängd under normal drift.
Utrustningen bör monters nära eluttag för nätsladdar. Nätsladdarna måste vara
lättillgängliga.
VARNING! Likströmskontakten som är placerad på S7400/S7x0000 PMF-enheten är
strömförande upp till femton (15) sekunder efter att elkablen till enheten har blivit urkopplad.
Du skyddar dig från strömstötar genom att testa om likströmskontakten fortfarande är
strömförande (med hjälp av en voltmätare).
S7400/
S7x000
S7x000
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-11
Safety and Compliance
Kundutförd installation och service
S7400/
S7x000
S7x000
S7400/
S7x000
Token-Ring Adapter Installation and Support Guide—426955-001
Statements-12
Glossary
adapter. See ServerNet adapter.
attribute. (1) For the Subsystem Control Facility (SCF), a characteristic of an entity. For
example, two attributes of a process might be its program file and its user ID. An
attribute is sometimes called a modifier. (2) For the Compaq Tandem Service
Management (TSM) package, a data item associated with a resource. All attributes can
be viewed and some can be modified.
backup processor. A processor in the Compaq NonStop™ Kernel operating system that
communicates with the primary processor, allowing the processors to remain
independent. A component failure in one processor has no effect on any other processor.
Contrast with primary processor.
board. A frame on which computer circuitry is mounted.
command. A demand for action by or information from a subsystem or the operation
demanded by an operator or application. A command is typically conveyed as an
interprocess message from an application to a subsystem.
communications line. A two-way link consisting of processing equipment, I/O devices,
protocol conventions, and cables that connect a computer to other computers.
communications subsystem. The combination of data communications hardware and
software processes that function together as an integrated unit to provide services and
access to wide and local area networks.
Compaq NonStop Kernel. The operating system for Compaq NonStop™ Himalaya S-series
systems.
Compaq Tandem Service Management (TSM) package. A software product for
NonStop™ Himalaya S-series servers that provides the information needed to perform
functions such as querying resources and testing, provides notification of problems on
the system, and allows local or remote access to the system for service and maintenance.
TSM performs the same role as that of Tandem Maintenance and Diagnostic System
(TMDS), Syshealth, and Remote Maintenance Interface (RMI) on earlier systems.
CRU. See customer-replaceable unit (CRU).
customer-replaceable unit (CRU). A subset of field-replaceable units (FRUs) that can be
installed and serviced (replaced) by customers, without using special tools or special
Compaq training. CRUs can be replaced while the system is running.
Event Management Service (EMS). A part of the Distributed System Management (DSM)
package used to provide event collection, event logging, and event distribution facilities.
It provides different event descriptions for interactive and programmatic interfaces, lets
an operator or an application select specific event-message data, and allows for flexible
distribution of event messages within a system or a network. EMS has a Subsystem
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-1
Glossary
event message
Programmatic Interface (SPI)-based programmatic interface for both reporting and
retrieving events.
event message. The text intended for a system operator that describes a change in some
condition in the system or network, whether minor or serious. The change of condition
is called an event. Events can be operational errors, notifications of limits exceeded,
requests for action needed, and so on. Each event message, when displayed on an event
screen, is displayed as one line of text.
fabric. A simplified way of representing a complex set of interconnections through which
there can be multiple and (to the user) unknown paths from point to point. The term
fabric is used to refer to the X or Y portion of the ServerNet system area network
(ServerNet SAN), for example, the X-fabric.
fault tolerance. The ability of a NonStop™ Himalaya system to continue processing despite
the failure of any single software or hardware component within the system.
field-replaceable unit (FRU). (1) Any system component that can be serviced by customer
or system engineers trained by Compaq. See also “customer-replaceable unit (CRU).”
(2) A unit that can be replaced in the field only by qualified personnel. FRUs that are not
also CRUs cannot be replaced by customers.
file name. A unique name for a file. File names for disk files normally have at least two parts
(the disk name and the file name); an example of a file name on a PC is B:MYFILE. In
the Guardian environment on NonStop™ Himalaya S-series systems, disk file names
include a disk volume name, a subvolume name, and a file identifier. An example of a
file name on a NonStop™ Himalaya S-series system is $DISK.SUBVOL.MYFILE. For
files that are network accessible, the node name precedes the volume name:
\NODE.$DISK.SUBVOL.MYFILE.
firmware. Code in memory that is necessary for the power-up initialization and
communication with a host or device. The software for components of the ServerNet
architecture (for example, an adapter) is called firmware. Some firmware for ServerNet
components is downloaded when the system or component is loaded.
FRU. See also field-replaceable unit (FRU)
Guided Replacement Toolkit (GRT). A software product that guides you step-by-step
through online replacement of a processor multifunction (PMF) customer-replaceable
unit (CRU), I/O multifunction (IOMF) CRU, S7x000 power supply, or ServerNet device
adapter (ServerNet/DA) and automates many of the necessary tasks.
Internet Protocol (IP). The network protocol in the Internet suite of protocols. It defines the
internet datagram as the basic unit of information exchanged on an internet network, and
it provides the basis for a connectionless, best-effort packet delivery service. See also
Transmission Control Protocol (TCP).
LAN. See local area network (LAN).
LANMAN. See LAN Manager (LANMAN) process.
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-2
Glossary
LAN Manager (LANMAN) process.
LAN Manager (LANMAN) process. The LANMAN process is provided as part of the
SLSA subsystem. The NonStop™ Kernel persistence manager starts and manages the
LANMAN process, which it starts as a generic process that runs as a process pair in the
host system processors. The LANMAN process starts and manages the SLSA subsystem
objects and also starts the LAN monitor (LANMON) process, assigning ownership of
Ethernet ServerNet addressable controllers (SACs) to the LANMON processes in the
system through an access list. SCF commands are directed to the LANMAN processes
for configuring and managing the SLSA subsystem and the Ethernet adapters. The
LANMAN process is named $ZZLAN, which is built by $ZZKRN and maintained by
the $ZPM persistence manager. See also ServerNet LAN Systems Access (SLSA)
subsystem and LAN Monitor (LANMON) process.
LANMON. See LAN Monitor (LANMON) process.
LAN Monitor (LANMON) process. The LAN monitor process is provided as part of the
SLSA subsystem. It is started and managed by the LAN Manager (LANMAN) process
and started at cold load. One LAN monitor process runs in each processor of the host
system. Each LAN monitor process has ownership of the adapters controlled by the
SLSA subsystem. The LAN manager process assigns adapter ownership. See ServerNet
LAN Systems Access (SLSA) subsystem and LAN Manager (LANMAN) process.
LIF. See logical interface (LIF).
LED. See light-emitting diode (LED).
light-emitting diode (LED). A semiconductor device that emits light from its surface.
Indicator lights are composed of LEDs.
local area network (LAN). (1) The cables, electrical interfaces, workstations, and other
devices that are interconnected and that are physically located in close proximity to each
other. One or more LANs can be connected to the system such that the LAN users can
access the system as if their workstations were connected directly to it. (2) A network
that is located in a small geographical area, whose communications technology provides
a high-bandwidth, low-cost medium to which low-cost nodes can be connected.
logical interface (LIF). The interface that allows an application or another process to
communicate with data communications hardware.
MAC address. See media access control (MAC) address.
media access control (MAC) address. A MAC address is a value in the Medium Access
Control sublayer of the IEEE/ISO/ANSI LAN architecture, that uniquely identifies an
individual station that implements a single point of physical attachment to a LAN.
Mbps. See megabits per second (Mbps).
megabits per second (Mbps). A data rate equal to 1,048,576 bits per second.
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-3
Glossary
network
network. Two or more computer systems (nodes) connected so that they can exchange
information and share resources. See wide area network (WAN), and local area network
(LAN).
NonStop™ Himalaya S-series servers. The set of servers in the Himalaya range of servers
having product numbers beginning with the letter “S.” These servers implement the
ServerNet architecture and run the Compaq NonStop™ Kernel operating system.
operator message. A message, intended for an operator, that describes a significant event on
a NonStop™ Himalaya S-series system. An operator message is the displayed-text form
of an Event Management Service (EMS) event message. See also event message.
owner. In the SLSA subsystem, the LAN Monitor (LANMON) process that monitors and
manages a ServerNet addressable controller (SAC). See also ServerNet addressable
controller (SAC).
persistence. The capability of a generic process to restart automatically if it was stopped
abnormally.
physical interface (PIF). The hardware components that connect a system node to a
network.
PIF. See physical interface (PIF).
port. (1) A data channel that connects to other devices or computers. (2) A connector to
which a cable can be attached. The system transmits and receives data or requests
through ports on ServerNet adapters and processor multifunction customer-replaceable
units (PMF CRUs). A port is also called a connector. (3) The entrance or physical access
point (such as a connector) to a computer, multiplexer, device, or network where signals
are supplied, extracted, or observed.
primary processor. The processor that is designated at system generation time as “owning”
the controller connected to the two separate processors of a Compaq NonStop™ Kernel
operating system. The primary processor is the processor that has direct control over the
controller. See also backup processor.
protocol. A set of rules used by processes or devices for exchanging data.
SAC. See ServerNet addressable controller (SAC).
SCF. See Subsystem Control Facility (SCF).
server. (1) An implementation of a system used as a stand-alone system or as a node in an
Expand network. (2) A combination of hardware and software designed to provide
services in response to requests received from clients across a network. For example, the
NonStop™ Himalaya range of servers provides transaction processing, database access,
and other services. (3) A process or program that provides services to a client or a
requester. Servers are designed to receive request messages from clients or requesters;
perform the desired operations, such as database inquiries or updates, security
verifications, numerical calculations, or data routing to other computer systems; and
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-4
Glossary
ServerNet adapter
return reply messages to the clients or requesters. A server process is a running instance
of a server program.
ServerNet adapter. A customer-replaceable unit (CRU) that connects peripheral devices to
the rest of the system though a ServerNet bus interface (SBI). A ServerNet adapter is
similar in function to an I/O controller logic board (LB) and backplane interconnect card
(BIC) in other NonStop™ systems.
ServerNet addressable controller (SAC). A SAC corresponds to controller functionality
uniquely addressable within one or more ServerNet address domains through the node
ID and address fields in a request packet. A SAC is typically implemented on some
portion of a processor multifunction (PMF) CRU, an I/O multifunction CRU, or a
ServerNet adapter. Examples: Each of the controllers on a multifunction I/O board
(MFIOB) and Ethernet 4 ServerNet adapter (E4SA), and each of the controllers on a
device, connect to the ServerNet adapter.
ServerNet SAN. See ServerNet system area network (ServerNet SAN).
ServerNet system area network (ServerNet SAN). A wormhole-routed, full-duplex,
packet-switched, point-to-point network designed with special attention to reducing
latency and ensuring reliability. The ServerNet SAN provides the communication path
used for interprocessor messages and for communication between processors and I/O
devices.
ServerNet LAN Systems Access (SLSA) subsystem. The software that allows the protocol
I/O processes (IOPs) and drivers to access the ServerNet adapters.
ServerNet wide area network (SWAN) concentrator. The SWAN concentrator provides
data communications connectivity to a Himalaya S-series server system. The
concentrator supports both synchronous and asynchronous data over RS-232, RS-449,
X.21, and V.35 electrical and physical interfaces. Each SWAN concentrator has six
WAN ports. Traffic across these six ports is multiplexed over two 10-Mbps 10-baseT
ethernet connections.
service provider. (1) A person trained and qualified to service field-replaceable units
(FRUs). (2) An organization, such as the Global Customer Support Center (GCSC), that
helps you resolve problems with your NonStop™ Himalaya S-series server. The TSM
package allows you to use the help of a service provider by configuring TSM to support
remote notification and remote access.
slot. A physical, labeled space for a customer-replaceable unit (CRU) or field-replaceable
unit (FRU) that is part of a module. A module contains one or more slots.
slot location. A three-number identifier for a particular slot on a system that consists of the
group number, module number, and slot number. EXAMPLE: 02,01,08 (group 02,
module 01, slot 08).
SLSA subsystem. See ServerNet LAN Systems Access (SLSA) subsystem.
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-5
Glossary
state
state. (1)The current condition of a device or path to a device. (2) In SCF subsystems, one of
the generally defined possible conditions of an object with respect to the management of
that object, for example, DEFINED, STARTED, and STOPPED.
subsystem. (1) a secondary or subordinate system, usually capable of operating
independently of or asynchronously with a controlling system. (2) A program or set of
processes that manages a cohesive set of Subsystem Control Facility (SCF) objects.
Each subsystem has a manager through which applications can request services by
issuing commands defined by that subsystem. See also subsystem manager.
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and
collecting information from NonStop™ Himalaya S-series subsystems.
Subsystem Control Point (SCP). The management process for all Subsystem Control
Facility (SCF) subsystems. There can be several instances of this process. Using the
Subsystem Programmatic Interface, applications send each command for a subsystem to
an instance of this process, which in turn sends the command to the manager process of
the target subsystem. SCP also processes a few commands itself. It provides security
features, version compatibility, support for tracing, and support for applications
implemented as process pairs.
subsystem manager. A Subsystem Control Facility (SCF) process that performs
configuration and management functions for an SCF subsystem.
SWAN concentrator. See ServerNet wide area network (SWAN) concentrator.
TCP. See Transmission Control Protocol (TCP).
TCP/IP. See Transmission Control Protocol (TCP) and Internet Protocol (IP).
Token-Ring. A network with a ring topology that passes tokens from one attaching device to
another.
Token-Ring ServerNet Adapter (TRSA). The hardware used to connect an S-series server
to a Token-Ring network.
Transmission Control Protocol (TCP). A connection-oriented protocol that provides for the
reliable exchange of data between a sending and a receiving system. TCP implements
functions corresponding to the Open Systems Interconnections (OSI) Reference ModelLayer 4, the Transport Layer. See also Internet Protocol (IP).
TRSA. See Token-Ring ServerNet Adapter (TRSA).
TSM. See Compaq Tandem Service Management (TSM) package.
wide area network (WAN). A network that operates over a larger geographical area than
that provided by a local area network (LAN). The elements of a WAN may be separated
by distances great enough to require telephone communications. See also local area
network (LAN).
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-6
Glossary
$ZZLAN
$ZZLAN. The name of the ServerNet LAN Systems Access (SLSA) subsystem manager
process that is started by the $ZZKRN Kernel subsystem manager process and
maintained by the $ZPM persistence manager process. See also LAN Manager
(LANMAN) process.
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-7
Glossary
$ZZLAN
Token-Ring Adapter Installation and Support Guide—426955-001
Glossary-8
Index
A
G
Aborting, TRSA adapter 3-12, 4-12
Adapter slot locations 2-5, 3-14, 4-15
Antistatic mat 2-7
Assigning LIFs 2-15, 4-26
Grounding clip 2-10, 3-17, 4-18
C
Cables, customer-supplied 1-2
Checking
firmware version 2-17, 3-27, 4-27
for damaged pins 2-13, 3-23, 4-22
installation of the TRSA adapter 2-13,
3-23, 4-22
D
Damaged pins 3-1, 4-1
Determining
LIF associated with PIF 3-4, 4-4
PIF associated with LIF 3-4, 4-4
SNAX/TR lines 3-7, 4-7
TCP/IP processes 3-4, 4-4
E
EMS log 3-30
Error conditions 2-13, 3-23, 4-22
ESD protected environment
antistatic mat 2-8
ESD protection wriststrap 2-8
grounding clip, use of 2-10
illustration of 2-7, 3-15, 4-16
ESD protection kit 2-7
Event Message Service (EMS) log 2-16,
4-27
F
I
Identifying
Communications lines using the TRSA
adapter 3-4
IPXPROTO processes 3-7, 4-7
physical location of adapter 3-12, 4-12
SNAX/TR lines 3-4, 4-4
Installation
assign logical LIFs 2-15, 4-26
checking for damaged pins 2-13, 3-23,
4-22
Compaq manufacturing 2-1, 3-1, 4-1
overview of 2-8
Token-Ring connectors 4-21
TRSA configuration form
completed form 2-3, 4-24
unpacking the adapter 2-8
IOMF CRU Replacement
preparing a TRSA B-1
IPXPROTO process names 3-7, 3-8, 4-7,
4-8
IPX/SPX subsystem 1-7
L
Location of adapter 2-3, 4-24
logfilename 3-4, 4-4
M
MAC address 3-4, 4-4
Manufacturing naming conventions 3-12,
4-12
Message system interface 1-6
File Transfer Protocol (FTP) 1-7
Token-Ring Adapter Installation and Support Guide—426955-001
Index-1
Index
N
N
Naming conventions 1-9
Novell NetWare networks 1-7
P
PIF 1-6
PMF CRU Replacement
preparing a TRSA B-1
Port Access Method (PAM)
interface to SLSA 1-7
Preparing to install a new TRSA
adapter 2-1
Processor enclosure
filler panel 3-2, 4-2
slots 3-2, 4-2
R
Relocating a TRSA 4-1
Remote Server Call (RSC) 1-7
Resuming customer applications 3-30
S
SCF commands
ABORT LIF 4-13
ADD ADAPTER 2-15, 4-26
ADD LIF 2-15, 4-26
INFO ADAPTER 3-11, 4-11
INFO LIF 3-4, 4-4
INFO LINE 3-6, 4-6
INFO PROCESS 3-8, 4-8
INFO SUBNET 3-4, 4-4
LISTDEV 3-6, 4-6
NAMES 2-15, 4-26
NAMES SUBSYS 3-7, 4-7
SCF INFO LIF 3-4, 4-4
SCF NAMES 3-6, 4-6
START ADAPTER 2-15, 4-26
STATUS LIF 3-12, 4-13
STATUS LINE 3-9, 4-9
STOP DEVICE 3-9, 4-9
SCF log 3-4, 4-4
Slot numbers for TRSA 2-3, 4-24
SNAX/APN 1-7
SNAX/XF 1-7
SNA-based software products 1-2
Socket library 1-7
Standard operating procedures for hardware
installation 2-7, 3-15, 4-16
Starting
Communications lines 3-28
Stopping
a SNAX/TR line 3-9, 4-9
PAM line 3-10, 4-10
TCP/IP subnet 3-11, 4-11
SUB ALL option 3-12
T
Telserv 1-7
Token-Ring
adapter interface 1-2
Ports description 1-2
supported interfaces 1-5
Token-Ring ServerNet adapter (TRSA)
installing 2-1
preparing for PMF or IOMF CRU
replacement B-1
relationship to port access method
(PAM) 1-6
relationship to SLSA subsystem 1-6
relationship to SNAX 1-6
relocating 4-1
replacing 3-1
TRSA slot locations 2-5, 3-14, 4-15
Tools needed for installation 2-7, 3-2, 4-2
Troubleshooting 2-16, 3-30, 4-27
TRSA configuration form 2-3, 4-24
TSM EMS Event Viewer Application 2-16,
3-30, 4-27
Token-Ring Adapter Installation and Support Guide—426955-001
Index-2
Index
V
TSM Service Application 2-16, 3-25, 4-27
checking firmware version 2-16, 4-27
used to abort the adapter 4-13
V
Verifying
Adapter is in STOPPED state 3-13
IPXPROTO 3-29
TCP/IP subnet 3-29
Verifying SAC object 3-27
Special Characters
$ZZLAN 1-9
$ZZPAM 3-6, 4-6
Token-Ring Adapter Installation and Support Guide—426955-001
Index-3
Index
Special Characters
Token-Ring Adapter Installation and Support Guide—426955-001
Index-4