LAN Configuration and Management Manual

SLSA Subsystem Installation and Configuration

LAN Configuration and Management Manual—520469-012

3-2

SLSA Subsystem Configuration

Your Integrity NonStop NS-series or NonStop S-series server is shipped with a generic

preconfiguration of the SLSA subsystem, which you can modify. However, changes

made to the configuration might also influence the placement and configuration of the

connections to any ServerNet wide area network (SWAN) concentrators you plan to

attach to your servers.

HP Manufacturing Naming Conventions

(G06.26 and Earlier RVUs)

For G06.26 and earlier RVUs, HP manufacturing uses a naming convention for

processes and devices that relates logical names to the physical location of devices.

processorid

specifies the processor in which the LANMON process is running. For example,

#ZLM01 specifies the LANMON in processor 1.

Note. HP recommends that all SLSA objects comply with the following naming specification:

eight alphanumeric characters, with the first character being a letter.

Table 3-1. Naming Convention for SLSA Subsystem and Related Processes

(G06.26 and Earlier RVUs)

Process or Device Type Convention Example

LAN Manager (LANMAN) process Must be $ZZLAN $ZZLAN

LAN Monitor (LANMON) process $ZZLAN.#ZLMprocessorid $ZZLAN.#ZLM01

Logical interface (LIF) $ZZLAN.Lcabid-portid $ZZLAN.L018

LAN adapters (E4SA, FESA,

GESA, G4SA, CCSA, or TRSA)

(See Suggested Naming

Conventions for Adapters on

page 3-7 for details.)

$ZZLAN.Ecabid-slot

For G4SAs, see G4SA Naming

Conventions (G06.24, G06.25,

and G06.26 RVUs) on page 3-4.

$ZZLAN.E0153

Processor multifunction (PMF) or

I/O multifunction (IOMF) CRU

$ZZLAN.MIOEprocessorid $ZZLAN.MIOE1

NonStop TCP/IP process $ZBcabid-portid $ZB018

SWAN or SWAN 2 concentrator Sconcnum S01