LAN Configuration and Management Manual

SLSA Subsystem Installation and Configuration
LAN Configuration and Management Manual—520469-012
3-8
Suggested Naming Conventions for Adapters

Add the slot number and module number that the adapter is in to the adapter
name. For example, a G4SA that is in slot 3 of module 2 of IOAM Group 111,
would have the name G11123.
Suggested Naming Conventions for ATMSAP Object
$ZZLAN.adapter-id.sac-id.pif-id.atmsap-id
adapter-id
is a 1 to 8-character alpha-numeric string, beginning with an alpha character,
that uniquely identifies the target SLSA ADAPTER object. Wildcard characters
are allowed.
sac-id
is a number that identifies the target SAC object. The only valid sac-id for the
ATM3SA adapter is the number “0.” Wildcard characters are allowed.
pif-id
is an alpha character that identifies the target PIF object. The only valid pif-id
for the ATM3SA adapter is the letter “A.” Wildcard characters are allowed.
atmsap-id
is a 1 to 8-character alpha-numeric string that identifies the target ATMSAP
object. Wildcard characters are allowed.
An example of an ATMSAP object name is:
$ZZLAN.ATM01.0.A.ATMSAP01
Suggested Naming Conventions for LIFs
A LIF name begins with the letter L followed by the adapter’s physical location (for
example, group, module, slot) and the port identifier to indicate the physical port on the
adapter or in slot 6 or 7 of the VIO enclosure with which the LIF corresponds.
Depending on your RVU and adapter type, use one of these port identifier methods.

For NonStop systems not accessing G4SAs or running G06.23 and earlier RVUs,
see portid on page 3-3.

For NonStop systems and IOAM enclosures using G4SAs and running G06.24
through G06.26 RVUs, see portid on page 3-6.

For NonStop systems and IOAM enclosures using G4SAs and running G06.27 and
later RVUs or H06.03 and later RVUs or J06.03 and later RVUs, see port
on
page 3-7.

For the VIO enclosure, see port on page 3-7.