1 – DEVICE
Enters a device into the LAN permanent device database or
modifies an existing device entry.
Requires SYSPRV privilege.
Format
DEFINE DEVICE device-name
QUALIFIERS
See the SET DEVICE command for a list of qualifiers and
the description of each. Except where noted, the only
difference is that DEFINE DEVICE applies to entries in
the LAN permanent device database rather than the volatile
device database.
1.1 – Parameter
device-name
Specifies the LAN device name. The device name has the form ddcu, where
dd is the device identifier, c is the controller designation, and u is
the unit number.
LAN devices are specified as the name of the template device, which is
unit 0. For example, the first EI Ethernet device is specified as EIA0,
the second as EIB0, and so on. You can specify the first EI device, for
example, as EIA, EIA0, or EIA0:.
A partial device name, accompanied by the /ALL qualifier, selects all
matching devices. For example: E to select all Ethernet devices, V for
VLAN devices, EI for Ethernet EI devices, no device name to select
all LAN devices.
1.2 – Examples
1 LANCP> DEFINE DEVICE EIA0/DLL=(ENABLE,EXCLUSIVE)
This command defines LAN device EIA0 to enable LANACP MOP
downline load service in exclusive mode. The setting of the
KNOWNCLIENTSONLY and SIZE characteristics are not changed. If
the device entry does not currently exist in the LAN permanent
device database, these settings are set to the defaults.
2 LANCP> DEFINE DEVICE/ALL/DLL=NOEXCLUSIVE
This command sets all LAN devices defined in the LAN permanent
device database to nonexclusive mode for LANACP MOP downline
load service.
3 LANCP> DEFINE DEVICE/ALL/UPDATE/VOLATILE_DATABASE
This command enters all Ethernet devices into the LAN permanent
device database and updates the entry to include the current
parameter values.
2 – NODE
Enters a node into the LAN permanent node database or modifies an
existing entry.
Requires SYSPRV privilege.
QUALIFIERS
See the SET NODE command for a list of qualifiers and the
description of each. Except where noted, the only difference
is that DEFINE NODE applies to entries in the LAN permanent
node database rather than the volatile node database.
Format
DEFINE NODE node-name
2.1 – Parameter
node-name
Specifies the node name in the LAN permanent node database.
When entering a new node, you can use the system node name recorded in
the system parameter SCSNODE, or another name limited to 63 characters
in length.
2.2 – Examples
1 LANCP> DEFINE NODE GALAXY/ADDRESS=08:00:2B:11:22:33 -
/FILE=NISCS_LOAD.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=VAX_SATELLITE
This command sets up node GALAXY in the LAN permanent node database
for booting as a VAX satellite into an OpenVMS Cluster.
The NISCS_LOAD.EXE file is actually located in the expanded directory
$64$DIA14:<SYS10.SYSCOMMON.SYSLIB>. The <SYSCOMMON.SYSLIB> is supplied
by the LANACP LAN Server process and is not included in the root
definition.
2 LANCP> DEFINE NODE ZAPNOT/ADDRESS=08:00:2B:11:22:33 -
/FILE=APB.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=ALPHA_SATELLITE
This command sets up node ZAPNOT for booting as an Alpha satellite
into an OpenVMS Cluster.
The APB.EXE file is actually located in the expanded directory
$64$DIA14:<SYS10.SYSCOMMON.SYSEXE>. The <SYSCOMMON.SYSEXE> is supplied
by the LANACP LAN Server process and is not included in the root
definition.
3 LANCP> DEFINE NODE CALPAL/ADDRESS=08:00:2B:11:22:33 -
/FILE=APB_061.EXE
This command sets up node CALPAL for booting an InfoServer image. It
defines the file that should be loaded when a load request without a
file name is received from node CALPAL.
Because the file does not include a directory specification, the
logical name LAN$DLL defines the location. You can include the
directory specification in the file name or by using the /ROOT
qualifier.
Note that specifying the file name explicitly in the boot command
overrides the file name specified in the node database entry.