Replacing a TRSA CRU

Identifying the Communications Lines That
Use a TRSA CRU
The ServerNet LAN Access Method (SLSA) subsystem provides access to the
Token-Ring ServerNet adapter (TRSA) CRU. The following NonStop subsystems and
applications may be configured to access a TRSA CRU through the SLSA subsystem:
The Port Access method (PAM) subsystem, which can interface to the SLSA
subsystem to provide an independent interface to Token-Ring networks, and the
user applications written using the PAM subsystem port interface. The following
NonStop subsystems can interface to the PAM subsystem to use a TRSA CRU:
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 TCP/IP subsystem, 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 IPX/SPX subsystem, which can interface to the SLSA subsystem to provide
connectivity to Novell NetWare networks. The following NonStop utilities and
subsystems can interface to the IPX/SPX subsystem to use a TRSA CRU:
Telserv and the FTP, which use the socket library to establish remote
connections through the IPX/SPX subsystem.
●
NonStop subsystems, such as Remote Server Call (RSC), that can be
configured to establish connections through the IPX/SPX subsystem.
❍
●
Note: SNAX/XF and SNAX/APN lines that use token-ring connections are referred
to as SNAX/TR lines in the following procedure.
The figure illustrates how these subsystems and utilities use the SLSA subsystem to
access a TRSA CRU.
The following procedure should help you identify the NonStop subsystems and utilities
that are configured to use a TRSA CRU. Specific instructions are provided for
identifying SNAX/TR lines.
Tip: You will need to make a note of the information you obtain during this