Software development, photography, jokes, ....

Sites by me

 
tas-logoTransportation Administration System
snoezelkussen-logo-kleinstSnoezelkussens voor verstandelijk gehandicapten
ikzoekeenbegeleider-logoBegeleiders voor gehandicapten
Laat uw hond het jaarlijkse vuurwerk overwinnen
logo 50x50Hey Vos! Je eigen naam@vos.net emailadres?
Kunst in huis? Nicole Karrèr maakt echt bijzonder mooie dingen
nettylogo2Kunst in huis? Netty Franssen maakt ook bijzonder mooie dingen
Salarisadministratie en belastingadvies bij De Zaak Loont
Zutphense Bomenstichting

Hosting Favorites

 
ANU Internet Services
XelMedia .internet Services
register.com

Blogroll

 
Bomenstichting
LassoSoft
MacFreak
Quality that computes
The Economy of Motion
Wheel 2.0
IntrAktv



Website Hosting bij Xel Media

Marc's Place

1 LANCP

You can use the LANCP utility to: o Set LAN parameters to customize your LAN environment. o Display LAN settings and counters. o Provide MOP downline load support for devices such as terminal servers, x-terms, and LAN-based printers, and for booting satellites in an OpenVMS Cluster environment. This provides an alternative to the traditional method of using DECnet software. Format LANCP [command] 2 Parameter command Specifies a LANCP command. This parameter is optional. If no command is specified, the utility displays its prompt and waits for command input. 2 Usage_Summary To invoke LANCP, enter the following command at the DCL command prompt: $ RUN SYS$SYSTEM:LANCP The LANCP utility responds by displaying the LANCP> prompt, at which you can enter any LANCP command described in this chapter. You can also invoke LANCP by using the MCR command or by defining LANCP as a foreign command. To use the MCR command, at the DCL command prompt, enter: $ MCR LANCP To define LANCP as a foreign command, either at the DCL prompt or in a startup or login command file, enter: $ LANCP :== $SYS$SYSTEM:LANCP Then you can enter the LANCP command at the DCL prompt to invoke the utility and enter LANCP commands. When you enter the LANCP or MCR LANCP command: o Without specifying any command qualifiers, the LANCP utility displays the LANCP> prompt, at which you can enter commands. o With command qualifiers, the LANCP utility terminates after it executes the command and returns you to the DCL command prompt. NOTE Some LANCP commands require special privileges. To exit from the LANCP utility, enter the EXIT command at the LANCP> prompt or press Ctrl/Z. For information about the LANCP utility, enter the HELP command at the LANCP> prompt. 2 Commands This section describes and provides examples of the LANCP commands. The following table summarizes the LANCP commands. Command Function @ (Execute Procedure) Executes a command procedure. CLEAR DLL Same as the CLEAR MOPDLL command. Clears MOP downline load counters for all nodes and devices. CLEAR DEVICE Deletes a device from the LAN volatile device database. CLEAR MOPDLL Clears MOP downline load counters for all nodes and devices. CLEAR NODE Deletes a node from the LAN volatile node database. CONNECT NODE Connects to a LAN device, such as a terminal server, that implements a management interface using the MOP console carrier protocol. CONVERT DEVICE_ Converts an OpenVMS V6.2 format device DATABASE database to an OpenVMS V7.1 format device database. CONVERT NODE_DATABASE Converts an OpenVMS V6.2 format node database to an OpenVMS V7.1 format node database. DEFINE DEVICE Enters a device into the LAN permanent device database or modifies an existing entry. DEFINE NODE Enters a node into the LAN permanent node database or modifies an existing entry. EXIT Stops execution of LANCP and returns control to the DCL command level. HELP Provides online help information about the LANCP utility. LIST DEVICE Displays information in the LAN permanent device database. LIST NODE Displays information in the LAN permanent node database. PURGE DEVICE Deletes a device from the LAN permanent device database. PURGE NODE Deletes a node from the LAN permanent node database. SET ACP Modifies the operation of the LANACP LAN Server process. SET DEVICE Modifies device parameters. (parameters) SET DEVICE (volatile Enters a device into the LAN volatile device database) device database or modifies an existing entry. SET NODE Enters a node into the LAN volatile node database or modifies an existing entry. SHOW CONFIGURATION Displays a list of LAN devices on the system. SHOW DEVICE Displays information in the LAN volatile device database. SHOW DLL Displays the current state of MOP downline load services. SHOW LOG Displays recent downline load activity. SHOW MOPDLL Displays the current state of MOP downline load services. SHOW NODE Displays information in the LAN volatile node database. SPAWN Creates a subprocess of the current process. TRIGGER NODE Issues a request to reboot to a remote node. UPDATE DEVICE Updates firmware image for a device. 2 LANACP The LANACP Server process provides the following services: o Maintenance of the LAN volatile node database o Maintenance of the LAN volatile device database o MOP downline load To start the LANACP LAN Server process, type @SYS$STARTUP:LAN$STARTUP at the DCL prompt, or include this line in the SYS$MANAGER:SYSTARTUP_VMS.COM command file to start LANACP automatically at system startup. The following shows the command line as it appears in SYS$MANAGER:SYSTARTUP_VMS.COM: $! $! To start the LANACP LAN server application, remove the comment delimiter $! from the command line below. $! $! @SYS$STARTUP:LAN$STARTUP $! To stop the LANACP LAN Server process, enter the SET ACP/STOP command at the LANCP utility prompt. 3 Logical_names LANACP uses the following system logical names: Component Description LAN$DLL system logical Defines the location of downline load name files, where the location of the file is not provided in the load request or explicitly defined in the LAN volatile node database. By default, this will be defined as SYS$SYSROOT:[MOM$SYSTEM]. LAN$NODE_DATABASE Defines the name of the LAN permanent system logical name node database. By default, this is defined as SYS$COMMON:[SYSEXE]LAN$NODE_ DATABASE.DAT. LAN$DEVICE_DATABASE Defines the name of the LAN system logical name permanent device database. By default, this is defined as SYS$SPECIFIC:[SYSEXE]LAN$DEVICE_ DATABASE.DAT. LAN$ACP system logical Defines the name of the LANACP LAN name Server process log file, containing entries describing changes to the LAN permanent device and node databases, and load request and load status information. By default, this is defined as SYS$SPECIFIC:[SYSMGR]LAN$ACP.LOG. 2 @ Executes a command procedure or requests the command interpreter to read subsequent command input from a specific file or device. Format @ file-spec 3 Parameter file-spec Specifies either the input device or the file for the preceding command, or the command procedure to be executed. 3 Qualifiers None. 3 Example $ CREATE COUNT.COM SHOW DEVICE/COUNTERS SPAWN WAIT 00:01:00 @COUNT <Ctrl/Z> $ RUN SYS$SYSTEM:LANCP LANCP> @COUNT Device Counters EXA0: Value Counter ----- ------- 4294967295 Seconds since last zeroed 38731696 Data blocks received 28378137 Multicast blocks received 2621447 Receive failure 4294967295 Bytes received 3203299230 Multicast bytes received 1 Data overrun 13771761 Data blocks sent 672064 Multicast packets transmitted 662415 Blocks sent, multiple collisions 502863 Blocks sent, single collision 1056303 Blocks sent, initially deferred 1462759444 Bytes sent 76562996 Multicast bytes transmitted 40042529 Send failure 0 Collision detect check failure 0 Unrecognized frame destination 0 System buffer unavailable 0 User buffer unavailable This example creates and runs a command procedure, COUNT.COM, that displays device counters once every minute. 2 CLEAR 3 DEVICE Deletes a device from the LAN volatile device database. Requires SYSPRV privilege. Format CLEAR DEVICE device-name 4 Parameter device-name Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. For example, you can specify a DEMNA controller as either EXA, EXA0, or EXA0:. To select all LAN devices, omit the device name and include the /ALL qualifier. 4 Qualifier /ALL Deletes all LAN devices in the LAN volatile device database. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. 4 Example LANCP> CLEAR DEVICE EXA0 This command deletes device EXA0 from the LAN volatile device database. 3 DLL This command is the same as the CLEAR MOPDLL command. 3 MOPDLL This command clears MOP downline load counters from the LAN volatile device and node databases for all nodes and devices. Requires SYSPRV privilege. Format CLEAR MOPDLL 4 Parameters None. 4 Qualifiers None. 4 Example LANCP> CLEAR MOPDLL This command clears MOP downline load counters from the LAN volatile device and node databases for all nodes and devices. 3 NODE Deletes a node from the LAN volatile node database. Requires SYSPRV privilege. Format CLEAR NODE node-name 4 Parameter node-name Supplies the name of a node in the LAN volatile node database. 4 Qualifier /ALL Deletes all LAN nodes in the LAN volatile node database. If you specify a node name, all matching nodes are selected; for example, A/ALL deletes all nodes whose name begins with A. 4 Example LANCP> CLEAR NODE VAXSYS This command deletes the node VAXSYS from the LAN volatile node database. 2 CONNECT 3 NODE Opens a MOP console carrier connection to the specified node. This allows a local terminal to act as the console for a remote system. Format CONNECT NODE node-specification 4 Parameter node-specification Supplies either the node name or the node address of the target node. If you supply the node name, the node address is obtained by looking up the node name in the LAN volatile node database. If you supply the node address, the corresponding node need not be defined in the LAN volatile node database. The canonical form of the address consists of 6 hexadecimal byte characters separated by hyphens. Use a colon as the separator character to indicate the bit-reversed form of the address. 4 Qualifiers /DEVICE /DEVICE=device-name Specifies the LAN controller device name to be used for the connection. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. /DISCONNECT /DISCONNECT=disconnect-character Specifies a character that you can use to terminate the connection to the remote node. To terminate a connection, press Ctrl/disconnect-character. You can select any ASCII character from @ through Z, except C, M, Q, S, Y; the default disconnect character is D. /PASSWORD /PASSWORD=16hexdigits Supplies the password to be used when the connection is initiated, in hexadecimal (for example, /PASSWORD=0123456789ABCDEF). The default password is zero. You can omit leading zeros. /V3 Indicates that MOP Version 3 formatted messages are to be used to make the connection. By default, LANCP determines the format by sending MOP Request ID messages to the remote node first in MOP Version 4 format, then in Version 3 format, repeating this process until a response is received or timeout occurs. You can specify the format: o To allow connection to nodes that do not support Request ID messages o As a means of getting around implementation problems with one of the formats /V4 Indicates that MOP Version 4 formatted messages are to be used to make the connection. By default, LANCP determines the format by sending MOP Request ID messages to the remote node first in MOP Version 4 format, then in Version 3 format, repeating this process until a response is received or timeout occurs. You can specify the format: o To allow connection to nodes that do not support Request ID messages o As a means of getting around implementation problems with one of the formats 4 Examples 1.CONNECT NODE GALAXY/DEVICE=EWA0 This command attempts a console-carrier connection to node GALAXY using the Ethernet device EWA0. 2.CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789AB This command attempts a console-carrier connection to the given node address using the Ethernet device EWA0, with the specified password. 2 CONVERT 3 DEVICE_DATABASE Converts an OpenVMS V6.2 format device database to an OpenVMS 7.1 format device database. Requires SYSPRV privilege. Format CONVERT DEVICE_DATABASE device_database 4 Parameters None. 4 Qualifiers None. 3 NODE_DATABASE Converts an OpenVMS V6.2 format node database to an OpenVMS V7.1 format node database. Requires SYSPRV privilege. Format CONVERT NODE_DATABASE node_database 4 Parameters None. 4 Qualifiers None. 2 DEFINE 3 DEVICE Enters a device into the LAN permanent device database or modifies an existing entry. Requires SYSPRV privilege. Format DEFINE DEVICE device-name 4 Parameter device-name Supplies the name of a device to be added to the LAN permanent device database or an entry to be modified. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. 4 Qualifiers /ALL Defines data for all LAN devices in the LAN permanent device database. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. /ATMADDRESS /ATMADDRESS=LES On Alpha systems, defines the LAN emulation server (LES) address for asynchronous transfer mode (ATM). Usually the address is not user specified; this qualifier is used only if you want a specific address. By default the address is determined by software from the configuration server for the LES. The /ATMADDRESS=LES qualifier's syntax is as follows: DEFINE DEVICE/ATMADDRESS = ([NO]LES=the ATM server) /ATMADDRESS /ATMADDRESS=ARP On Alpha systems, defines the LAN address resolution protocol (ARP) server address for ATM. This qualifier is required before a logical IP subnet (LIS) is enabled if the local host is not the ARP server. The /ATMADDRESS=ARP qualifier's syntax is as follows: DEFINE DEVICE/ATMADDRESS = (ARP=atm_arp_server) /CLIP On Alpha systems, the Classical Internet Protocol (CLIP) qualifier defines a device with the TCP/IP protocol that enables it to see a network as being configured as one or more logical IP subnets (LIS), which allows the Alpha system to transmit Ethernet frames over the ATM network. The /CLIP = ENABLE command causes the system to join the LIS when LANCP initializes. The /CLIP = DISABLE command causes the client to leave the logical IP subnet. Note that a LIS requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. Also, there can only be one client for each ATM adapter. The /CLIP qualifier's syntax with standard Internet dotted notation is as follows: DEFINE DEVICE/CLIP =(ip_subnet=a.b.c.d, ip_addr=a.b.c.d, parent=devnam, name="ip subnet name", enable, disable mode = client|server) The meanings for the syntax for /CLIP are as follows: Keyword /Sub- Keyword Meaning Enable Joins the logical IP subnet. Disable Causes a client to leave the logical IP subnet. ip_ Specifies the IP address of the CLIP client. address= subnet_ Specifies the subnet mask of the CLIP client. mask= name= Specifies a name for the LIS to aid in operations and diagnostics. mode=clientStarts up a classical IP only. This is the default. mode=serverStarts up a classical IP server and client. Allows only one node for each LIS when specified. /DLL On Alpha systems, same as the /MOPDLL qualifier. /ELAN On Alpha systems, the /ELAN qualifier has two values: enable and disable. With /ELAN=ENABLE along with the keyword STARTUP, the LAN emulation is loaded when LANCP starts. With /ELAN=DISABLE, the same parameters used with ENABLE can be invoked. The /ELAN qualifier's syntax is as follows: DEFINE DEVICE/ELAN =([parent=parent device,].. [name="ELAN NAME to join",]... [size=1516]...[type=CSMACD]...[Enable,] ...[Disable,]...[Enable=startup,] ...[Disable=startup,]... [description = "description string,"]) The meaning of the syntax for /ELAN are as follows: Option Meaning parent The ATM adapter device name. An example of the parent device for ATMworks 350 is: HCn0, where n is the controller number. An example of the parent device for ATMworks 750 is: HWn0, where n is the controller number. name Optionally specified if you want to join a specific ELAN. The default is null. size Maximum frame size of the LAN you want to join. Valid sizes are 1516, 4544, 9234, or 18,190 bytes. The default is 1516. type Support currently only for CSMACD, which is the default. descriptionA method of describing the ELAN for display purposes only. Keywords and their meanings for /ELAN are as follows: Keyword Meaning Enable Begins a join on a specified emulated LAN. It also loads the driver, if not already loaded. Disable Causes a client to leave the emulated LAN. /MOPDLL /MOPDLL=(enable-option, exclusive-option, size-option, knownclientsonly-option) Provides the MOP downline load service settings for the device. Note that defaults apply to creation of an entry in the device database. If an existing entry is being modified, fields not specified remain unchanged. You can specify the following keywords with this qualifier: o enable-option ENABLE DISABLE (default) Specify ENABLE or DISABLE to indicate that MOP downline load service should be enabled or disabled for the device. o exclusive-option EXCLUSIVE NOEXCLUSIVE (default) Specify EXCLUSIVE to indicate that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP. Specify NOEXCLUSIVE to indicate that the LAN MOP downline load service can coexist with other implementations (in particular, the DECnet Phase IV implementation that operates the MOP protocol in shared mode). o size-option SIZE=value Use SIZE=value to specify the size in bytes of the file data portion of each downline load message. The permitted range is 246 to 1482 bytes. The default value is 246 bytes, which should allow any client to load properly. Note that some clients may not support the larger size. The recommended size for better load performance and less server overhead is the largest size that results in successful loads of all clients. The 1482 value is derived from the maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less the 802e header and CRC (26 bytes) and MOP protocol overhead (10 bytes). You can override the size on a per-node basis. See DEFINE NODE and NODE for details. o knownclientsonly-option KNOWNCLIENTSONLY NOKNOWNCLIENTSONLY (default) Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN permanent node database. When NOKNOWNCLIENTSONLY is selected, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN permanent node database. /UPDATE Adds LAN devices that are not currently in the LAN permanent device database to that database. The initial entry for the device uses default values for all parameters. To update the permanent database with current information from the volatile database, use the DEFINE DEVICE command with the /VOLATILE_ DATABASE qualifier. You can combine the /UPDATE and /VOLATILE_ DATABASE qualifiers in a single DEFINE DEVICE command. /VOLATILE_DATABASE Updates the device entries in the LAN permanent device database with any data currently set in the volatile database. This allows you to update the permanent database after changing data in the volatile database, rather than repeating the commands for each updated entry to apply the changes to the permanent database. 4 Examples 1.LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE) This command defines LAN device EXA0 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/MOPDLL=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. 3 NODE Enters a node into the LAN permanent node database or modifies an existing entry. Requires SYSPRV privilege. Format DEFINE NODE node-name 4 Parameter node-name Supplies the name of a node to be added to the LAN permanent node database or an entry to be modified. Typically, the node name is the same as that given in the system parameter SCSNODE, but it does not need to be. The node name is limited to 63 characters in length. 4 Qualifiers /ADDRESS /ADDRESS=node-address /NOADDRESS (default) Associates a LAN address with the node name. Specify the address as 6 bytes in hexadecimal notation, separated by hyphens. The address does not have to be unique (as might be the case when the address is not known, so a nonexistent address is specified). If multiple node addresses are to be associated with a node name, each combination may be given as a node name with an extension, for example, VAXSYS.EXA for the EXA device on node VAXSYS, or VAXSYS_1 for the first LAN device on node VAXSYS. If you do not specify the /ADDRESS qualifier, the setting remains unchanged. The /NOADDRESS qualifier clears the field. /ALL Defines data for all nodes in the LAN permanent node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A. /BOOT_TYPE /BOOT_TYPE=boot-option /NOBOOT_TYPE Indicates the type of processing required for downline load requests. You can specify one of the following keywords with this qualifier: o VAX_SATELLITE-an OpenVMS Cluster VAX satellite boot o ALPHA_SATELLITE-an OpenVMS Cluster Alpha satellite boot o OTHER-the specified image; a noncluster satellite load that does not require additional data The distinction is necessary, because OpenVMS Cluster satellite loads require additional cluster-related data be appended to the load image given by the /FILE qualifier. The default value is OTHER. If you do not specify the /BOOT_TYPE qualifier, the setting remains unchanged. The /NOBOOT_TYPE qualifier clears the field. /FILE /FILE=file-spec /NOFILE Supplies the file name of a boot file to be used when the downline load request does not include a file name (for example, with OpenVMS Cluster satellite booting). The file specification is limited to 127 characters. If no file name is specified, OpenVMS Cluster satellite loads default to APB.EXE where the boot type is set to ALPHA and NISCS_ LOAD.EXE where the boot type is set to VAX. If you do not specify the /FILE qualifier, the setting remains unchanged. The /NOFILE qualifier clears the field. /ROOT /ROOT=directory-specification /NOROOT Supplies the directory specification to be associated with the file name. For cluster satellite service, the /ROOT qualifier specifies the satellite root directory. For noncluster service, this qualifier specifies the location of the file. If the file specification or the file name given in the boot request includes the directory name, this qualifier is ignored. The directory specification is limited to 127 characters. If you do not specify the /ROOT qualifier, the setting remains unchanged. The /NOROOT qualifier clears the field. /SIZE /SIZE=value /NOSIZE Specifies the size in bytes of the file data portion of each downline load message. The default is the load data size specified for the device. The permitted range is 246 to 1482 bytes. Use a larger size for better load performance and less server overhead. If you do not specify the /SIZE qualifier, the setting remains unchanged. The /NOSIZE qualifier clears the setting. /V3 /V3 /NOV3 Indicates that only MOP Version 3 formatted messages are to be used for downline load purposes, regardless of the requested format. This allows systems that have a problem with MOP Version 4 booting to load. This qualifier causes the requesting node to fail over from MOP Version 4 to MOP Version 3 when no response has been made to a MOP Version 4 load request. If you do not specify the /V3 qualifier, the setting remains unchanged. The /NOV3 qualifier clears the setting. /VOLATILE_DATABASE Updates the node entries in the LAN permanent node database with any data currently set in the volatile database. This allows you to update the permanent database after changing data in the volatile database, rather than repeating the commands for each updated entry to apply the changes to the permanent database. 4 Examples 1.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 on $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.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 on $64$DIA14: <SYS10.SYSCOMMON.SYSEXE>. Note that the <SYSCOMMON.SYSEXE> is supplied by the LANACP LAN Server process and is not included in the root definition. 3.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 where to locate the file. You could give directory specification using 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. 2 EXIT Stops execution of LANCP and returns control to the DCL command level. You can also enter Ctrl/Z at any time to exit. Format EXIT 3 Parameters None. 3 Qualifiers None. 3 Example LANCP> EXIT $ This command stops execution of LANCP and returns control to the DCL command level. 2 HELP Provides online help information about the LANCP utility. Format HELP [topic] 3 Parameter topic Specifies a subject for which you want information-a LANCP command or LANCP command and command keyword. If you enter the HELP command with a command name only, such as HELP SET, LANCP displays a list of all of the command keywords used with the SET command. 3 Qualifiers None. 3 Example LANCP> HELP DEFINE DEVICE DEFINE DEVICE DEVICE device-name/qualifiers DEVICE/ALL/qualifiers Sets device specific parameters for the specified LAN devices. Requires SYSPRV privilege. Additional information available: Parameters Qualifiers /ALL /ATMADDRESS /DLL /ELAN /MOPDLL /VOLATILE_ DATABASE /UPDATE Examples DEFINE DEVICE Subtopic? This command provides online help for the LANCP command DEFINE DEVICE. 2 LIST 3 DEVICE Displays information in the LAN permanent device database. Format LIST DEVICE device-name 4 Parameter device-name Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. This refers to the LAN template device, for which is maintained most of the device parameters and counters. Also, the device name can refer to a device unit representing an actual user or protocol. For example, the cluster protocol can be started on a device as EWA1. You can specify a device unit to view unit-specific parameter information. If you do not specify a device name, all devices are displayed. If you specify a device name, all matching LAN devices are displayed, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. NOTE If you do not specify a qualifier, the utility displays the matching devices without additional information. 4 Qualifiers /ALL On Alpha systems, lists all devices in the LAN permanent device database. /CHARACTERISTICS On Alpha systems, lists status and related information about the device. It is the same as /PARAMETERS qualifier. /DLL Same as /MOPDLL qualifier. It shows downline load characteristics. /MAP Lists the current configuration of the functional address mapping table. /MOPDLL Displays MOP downline load information. Devices: Token Ring devices /PARAMETERS On Alpha systems, lists status and related information about the device. /SR_ENTRY On Alpha systems, lists the contents of the current source routing cache table. 4 Examples 1.LANCP> LIST DEVICE/MOPDLL Device Listing, permanent database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes FXA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes This command displays MOP downline load information in the LAN permanent device database for all known devices. 2.LANCP> LIST DEVICE/MOPDLL EXA0 Device Listing, permanent database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes This command displays MOP downline load information in the LAN permanent device database for device EXA0. 3 NODE Displays information in the LAN permanent node database, especially MOP downline load information. Format LIST NODE node-name 4 Parameter node-name Specifies the node name. The name can include up to 63 characters associated with the node address. If no node name is given, all nodes are displayed. 4 Qualifiers /ALL Displays data for all nodes in the LAN permanent node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A. /OUTPUT /OUTPUT=command-file-name Creates the specified file and directs output there in the form of a list of DEFINE NODE or SET NODE commands. The resulting command file can be used to create the LAN node databases. 4 Example LANCP> LIST NODE Node Listing: GALAXY (08-00-2B-2C-51-28): MOP DLL: Load file: APB.EXE Load root: $64$DIA24:<SYS11.> Boot type: Alpha satellite ZAPNOT (08-00-2B-18-7E-33): MOP DLL: Load file: NISCS_LOAD.EXE Load root: LAVC$SYSDEVICE:<SYS10.> Boot type: VAX satellite CALPAL (08-00-2B-08-9F-4C): MOP DLL: Load file: READ_ADDR.SYS Last file: LAN$DLL:APB_X5WN.SYS Boot type: Other 2 loads requested, 1 volunteered 1 succeeded, 0 failed Last request was for a system image, in MOP V4 format Last load initiated 30-OCT-1994 09:11:17 on EXA0 for 00:00:06.65 527665 bytes, 4161 packets, 0 transmit failures Unnamed (00-00-00-00-00-00): Totals: Requests received 2 Requests volunteered 1 Successful loads 1 Failed loads 0 Packets sent 2080 Packets received 2081 Bytes sent 523481 Bytes received 4184 Last load CALPAL at 10-JUN-1996 09:11:17.29 This example shows output from a LIST NODE command issued on a local node on which there are three nodes defined (GALAXY, ZAPNOT, and CALPAL). CALPAL has issued two load requests: o The first request is the multicast request from CALPAL that the local node volunteered to accept. o The second request is the load request sent directly to the local node by CALPAL for the actual load data. The elapsed time from the second load request to completion of the load was 6.65 seconds. 2 PURGE 3 DEVICE Deletes a device from the LAN permanent device database. Requires SYSPRV privilege. Format PURGE DEVICE device-name 4 Parameter device-name Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. To select all LAN devices, omit the device name and include the /ALL qualifier. 4 Qualifier /ALL Deletes all LAN devices in the LAN permanent device database. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. 4 Example LANCP> PURGE DEVICE/ALL This command deletes all devices from the LAN permanent device database. 3 NODE Deletes a node from the LAN permanent node database. Requires SYSPRV privilege. Format PURGE NODE node-name 4 Parameter node-name Supplies the name of a node in the LAN permanent node database. 4 Qualifier /ALL Deletes all LAN nodes in the LAN permanent node database. If you specify a node name, all matching nodes are selected; for example, A/ALL deletes all nodes whose name begins with A. 4 Example LANCP> PURGE NODE/ALL This command deletes all nodes from the LAN permanent node database. 2 SET 3 ACP Modifies the operation of the LANACP LAN Server process. Requires SYSPRV privilege. Format SET ACP 4 Parameters None. 4 Qualifiers /ECHO /ECHO /NOECHO (default) Enables partial tracing of received and transmitted downline load messages (the first 32 bytes of the data portion of each message). Note that the last one or two MOP messages are displayed in full: the memory load message with cluster parameters, and the parameter load with transfer address message, where present in the load. The data is written to a log file SYS$MANAGER:LAN$node-name.LOG. To obtain the entire contents of each message, use the /FULL qualifier as follows: SET ACP/ECHO/FULL /FULL /FULL /NOFULL (default) When /ECHO is enabled, displays the entire contents of received and transmitted downline load messages. /OPCOM /OPCOM (default) /NOOPCOM Enables OPCOM messages from LANACP LAN Server process. Messages are generated by the LANACP LAN Server process when a device status changes, load requests are received, and loads complete. These messages are displayed on the operator's console and included in the log file written by LANACP, SYS$MANAGER:LAN$ACP.LOG. /STOP Stops the LANACP process. It can be restarted by reexecuting the SYS$STARTUP:LAN$STARTUP command file. 4 Example LANCP> SET ACP/ECHO/FULL This command enables tracing of received and transmitted downline load messages. The /FULL qualifier displays the entire contents of received and transmitted downline load messages. 3 DEVICE_parameters Alpha only. On Alpha systems, sets or modifies LAN device parameters. Requires PHY_IO privilege. Format SET DEVICE device-name 4 Parameter device-name Specifies a device to be entered in the LAN volatile device database, or whose parameters are to be modified. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. 4 Qualifiers /AGING_TIMER /AGING_TIMER=value Sets the amount of time in seconds to age source routing cache entries before marking them stale. This timer expires when no traffic is sent to or received from the remote node in this amount of time. The default value is 60 seconds. Increase this value when idle connections bounce between the stale and known states. Setting this value too low may cause unnecessary explorer traffic to traverse the LAN. Devices: Token Ring devices /ALL Sets data for all LAN devices. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. /ATMADDRESS /ATMADDRESS=LES On Alpha systems, sets the LAN emulation server (LES) address for asynchronous transfer mode (ATM). Usually the address is not user specified, and this qualifier is used only if you want a specific address. By default the address is determined by software from the configuration server for the LES. The /ATMADDRESS=LES qualifier's syntax is as follows: SET DEVICE/ATMADDRESS = ([NO]LES=the ATM server) /ATMADDRESS /ATMADDRESS=ARP On Alpha systems, sets the address resolution protocol (ARP) server address for ATM. This qualifier is required before a LIS is enabled if the local host is not the ARP server. The /ATMADDRESS=ARP qualifier's syntax is as follows: SET DEVICE/ATMADDRESS = (ARP=atm_arp_server) /CACHE_ENTRIES /CACHE_ENTRIES=value Sets the number of entries to reserve for caching source routing address entries. The default value is 200 entries. If your system directly communicates to a large number of systems, you may want to increase this number. Devices: Token Ring devices /CLIP On Alpha systems, the classical internet protocol (CLIP) qualifier sets a device with the TCP/IP protocol enabling it to see a network as being configured as one or more logical IP subnets (LIS), which allows it to transmit Ethernet (802.3) frames over the ATM network. The /CLIP = ENABLE command causes the the system to join the logical IP subnet when LANCP initializes. The /CLIP = DISABLE command causes the client to leave the logical IP subnet. Note that a logical IP subnet requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. Also, there can only be one client for each ATM adapter. The /CLIP qualifier's syntax with standard Internet dotted notation is as follows: DEFINE DEVICE/CLIP =(ip_subnet=a.b.c.d, ip_addr=a.b.c.d, parent=devnam, name="ip subnet name", enable, disable mode = client|server) The meanings for the syntax for /CLIP are as follows: Keyword /Sub- Keyword Meaning Create Loads the classical IP driver but does not start it. Enable Joins the logical IP subnet. Disable Causes the node to leave the logical IP subnet. ip_ Specifies the IP address of the CLIP client address= subnet_ Specifies the subnet mask of the CLIP client mask= name= Specifies a name for the LIS to aid in operations and diagnostics. mode=clientStarts up a classical IP only. This is the default. mode=serverStarts up a classical IP server and client. Allows only one node for each LIS when specified. /CONTENDER /CONTENDER /NOCONTENDER (default) Specifies that the device is to participate in the Monitor Contention process when it joins the ring. The /NOCONTENDER qualifier, directs the device not to challenge the current ring server. Devices: Token Ring devices /DISCOVERY_TIMER /DISCOVERY_TIMER=value Sets the number of seconds to wait for a reply from a remote node when performing the source routing route discovery process. The default value is 2 seconds. If you have nodes that respond slowly on your extended LAN, you may need to increase this number to reduce the amount of explorer traffic that traverses your LAN. Devices: Token Ring devices /DLL On Alpha systems, same as /MOPDLL qualifier. They set downline load characteristics. /EARLY /EARLY (default) /NOEARLY Enables Early Token Release on the device. The /NOEARLY qualifier, disables Early Token Release. Devices: Token Ring devices operating on 16-megabit rings /ELAN On Alpha systems, the /ELAN qualifier has two values: enable and disable. With /ELAN=ENABLE along with the keyword STARTUP, the LAN emulation is loaded when LANCP starts. With /ELAN=DISABLE, the same parameters used with ENABLE can be invoked. The /ELAN qualifier's syntax is as follows: SET DEVICE/ELAN =([parent=parent device,]..[name="ELAN NAME to join",]... [size=1516]...[type=CSMACD]...[Enable,] ...[Disable,]...[Enable=startup,] ...[Disable=startup,]... [description = "description string,"]) The meaning of the syntax for /ELAN are as follows: Option Meaning parent The ATM adapter device name. An example of the parent device for ATMworks 350 is: HCn0, where n is the controller number. An example of the parent device for ATMworks 750 is: HWn0, where n is the controller number. name Optionally specified if you want to join a specific ELAN. The default is null. size Maximum frame size of the LAN you want to join. Valid sizes are 1516, 4544, 9234, or 18,190 bytes. The default is 1516. type Support currently only for CSMACD, which is the default. descriptionA method of describing the ELAN for display purposes only. Keywords and their meanings for /ELAN are as follows: Keyword Meaning Create Loads the emulation driver SYS$ELDRIVER.EXE, but does not start it. Enable Begins a join on a specified emulated LAN. It also loads the driver, if not already loaded. Disable Causes a client to leave the emulated LAN. /FULL_DUPLEX /FULL_DUPLEX /NOFULL_DUPLEX (default) Enables full-duplex operation of a LAN device. Before full-duplex operation results from the use of this qualifier, additional device or network hardware setup may be required. Some devices may be enabled for full-duplex operation by default. Some devices may not allow the setting to be changed. The /NOFULL_DUPLEX qualifier, disallows full-duplex operation regardless of the hardware configuration. Devices: Devices that support full-duplex operation /MAP /MAP=(MULTICAST_ADDRESS=address, FUNCTIONAL_ADDRESS=address) /NOMAP=(MULTICAST_ADDRESS=address) Maps a standard multicast address to a functional address. Token ring devices do not support IEEE 802 standard globally defined group addresses. They do support functional addresses. A functional address is a locally administered group address that has 31 possible values. Each functional address sets one bit in the third through sixth byte of the address and bytes 1 and 2 are 03-00 (C0:00 in bit reversed format). The /NOMAP=(MULTICAST_ADDRESS=address) qualifier, clears the mapping established for the specified address. Specify the functional address as follows: o The MULTICAST_ADDRESS argument requires a standard 6-byte multicast address. o The FUNCTIONAL_ADDRESS argument requires only the last 4 bytes of the functional address (the preceding 03-00 bytes are automatically prefixed). o The address variable, given as hexadecimal byte characters separated by hyphens, specifies the canonical form of the address. Use a colon as the separator character to indicate the bit-reversed form of the address. For example, to map the multicast address CB-00-01-02-03-04 to the functional address 03-00-00-80-00-00 on the Token Ring device IRA0, enter the following command: SET DEVICE IRA0/MAP=(MULTI=CB-00-01-02-03-04,FUNCT=00:01:00:00) For the default address mapping, see the following table or issue the command SHOW DEVICE/MAP device-name. Functional Multicast Address Address Description 09-00-2B-00-00-04 03-00-00-00-02-00 ISO ALL ES 09-00-2B-00-00-05 03-00-00-00-01-00 ISO ALL IS CF-00-00-00-00-00 03-00-00-08-00-00 Loopback Assistant AB-00-00-01-00-00 03-00-02-00-00-00 DNA MOP Dump/Load AB-00-00-02-00-00 03-00-04-00-00-00 DNA MOP Remote Console AB-00-00-03-00-00 03-00-08-00-00-00 DNA L1 Routers 09-00-2B-02-00-00 03-00-08-00-00-00 DNA L2 Routers 09-00-2B-02-01-0A 03-00-08-00-00-00 DNA Phase IV Primary Router AB-00-00-04-00-00 03-00-10-00-00-00 DNA Endnodes 09-00-2B-02-01-0B 03-00-10-00-00-00 DNA Phase IV Prime Unknown Destination 09-00-2B-00-00-07 03-00-20-00-00-00 PCSA NETBIOS Emulation 09-00-2B-00-00-0F 03-00-40-00-00-00 LAT Service Advertisement 09-00-2B-02-01-04 03-00-80-00-00-00 LAT Service Solicit 09-00-2B-02-01-07 03-00-00-02-00-00 LAT Xwindown Service Solicit 09-00-2B-04-00-00 03-00-00-04-00-00 LAST 09-00-2B-02-01-00 03-00-00-00-08-00 DNA Name Service Advertisement 09-00-2B-02-01-01 03-00-00-00-10-00 DNA Name Service Solicit 09-00-2B-02-01-02 03-00-00-00-20-00 DNA Time Service 03-00-00-00-00-01 03-00-00-00-00-01 NETBUI Emulation 03-00-02-00-00-00 03-00-02-00-00-00 RIPL Devices: Token Ring devices /MAX_BUFFERS /MAX_BUFFERS=value Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device. The value must be within the range 4 to 32. The value cannot be less than the minimum number of receive buffers. The default value is 32. Devices: All LAN devices /MEDIA /MEDIA=value o For Token Ring devices: Selects the type of cable media used to connect the adapter to the Token Ring Media Access Unit (MAU) for devices that do not automatically detect this. Acceptable values for this are either UTP (unshielded twisted pair) or STP (shielded twisted pair). The default value is STP. o For Ethernet devices: Selects the cable connection. Normally, the selection is made during device initialization using a limited autosensing algorithm that selects twisted pair, but fails over to AUI (Attachment Unit Interface) if twisted pair does not appear to be functional. Thereafter, a cabling change would require a reboot of the system to take effect. This command allows you to change the selection without rebooting. Acceptable values are AUI (10Base2, 10Base5), TWISTEDPAIR (10BaseT), and AUTOSENSE (reperform the limited autosense algorithm). The default value is AUTOSENSE. Some devices, such as the DE435, require a jumper change on the Ethernet card to switch between 10Base2 and 10Base5 (thinwire and thickwire). Other devices, such as the DE434, DE436, and DE500, have only twisted pair connections. Devices: Any LAN device that has software-settable media selection /MIN_BUFFERS /MIN_BUFFERS=value Sets the minimum number of receive buffers to be allocated and used by the LAN driver for the LAN device. The value must be within the range 4 to 32. The value cannot exceed the maximum number of receive buffers. The default value is 32. Devices: All LAN devices /PERMANENT On Alpha systems, reads the permanent database and creates device entries in the volatile database. /RING_PURGER On Alpha systems, enables ring purging on Token Ring devices. /SOURCE_ROUTING /SOURCE_ROUTING (default) /NOSOURCE_ROUTING Enables source routing on the Token Ring device. If you only have one ring in your LAN or you use transparent bridging, use the /NOSOURCE_ROUTING qualifier to turn off source routing. Devices: Token Ring devices /SPEED /SPEED=value Sets the speed of the LAN. For Token Ring, valid values are either 4 or 16, indicating 4 megabits per second or 16 megabits per second. The default value for Token Ring is 16, unless the LAN adapter supports a nonvolatile mechanism for setting this parameter (as does the DEC Token Ring Controller 700). For Ethernet, valid values are either 10 or 100, which selects the 10 megabits per second Ethernet port or the 100 megabits per second Fast Ethernet port. The default for Ethernet is to sense automatically which type of port is connected and select the appropriate speed. Devices: Token Ring devices and the DE500 Ethernet/Fast Ethernet device /SR_ENTRY /SR_ENTRY=(LAN_ADDRESS=address, RI=routing-information) /NOSR_ENTRY=(LAN_ADDRESS=address) Statically defines a specific source-routed route for a specific node. The default value is no routes specified. This caching remains valid while used or until the aging timer expires. Use this qualifier only as a last resort when isolating communication failures on extended LAN topologies. The /NOSR_ENTRY=(LAN_ADDRESS=address) qualifier, clears the previously defined static source routed route. The address is a standard 6-byte LAN address (given as hexadecimal byte characters separated by hyphens), which specifies the canonical form of the address. Using a colon as the separator character indicates the bit-reversed form of the address. The routing-information is the source routing field, specified as a series of two-byte hexadecimal characters (each byte separated by a hyphen). The field consists of a two-byte routing control field followed by up to 14 two-byte segment identifiers, each containing the ring number and the bridge number used in the hop. Devices: Token Ring devices /TOKEN_ROTATION On Alpha systems, sets the token rotation time. /TOKEN_TIMEOUT On Alpha systems, sets the token ring timeout. /TRANSMIT_TIMEOUT On Alpha systems, sets the timeout on the Token Ring adapter. /UPDATE On Alpha systems, sets volatile device parameter according to permanent device database parameters. 4 Examples 1.LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0 Enables monitor contention, UTP cable media, source routing and disables early token release for Token Ring device ICA0. 2.LANCP> SET DEVICE/MEDIA=TWI EWB0 Sets the media type to twisted pair for the second Tulip Ethernet device, EWB0. 3 DEVICE_volatile_device_database Enters a device into the LAN volatile device database or modifies an existing entry. Requires SYSPRV privilege. Format SET DEVICE device-name 4 Parameter device-name Specifies a device to be entered in the LAN volatile device database or an entry to be modified. 4 Qualifiers /ALL Defines data for all LAN devices in the LAN volatile device database. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. /MOPDLL /MOPDLL=(enable-option, exclusive-option, size-option, knownclientsonly-option) Provides the MOP downline load service settings for the device. Note that defaults apply to creation of an entry in the device database. If an existing entry is being modified, fields not specified remain unchanged. You can specify the following keywords with this qualifier: o enable-option ENABLE DISABLE (default) Specify ENABLE or DISABLE to indicate that MOP downline load service should be enabled or disabled for the device. o exclusive-option EXCLUSIVE NOEXCLUSIVE (default) Specify EXCLUSIVE to indicate that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP. Specify NOEXCLUSIVE to indicate that the LAN MOP downline load service can coexist with other implementations (in particular, the DECnet Phase IV implementation that operates the MOP protocol in shared mode). o knownclientsonly-option KNOWNCLIENTSONLY NOKNOWNCLIENTSONLY (default) Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN volatile node database. When NOKNOWNCLIENTSONLY is selected, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN volatile node database. o size-option SIZE=value Use SIZE=value to specify the size in bytes of the file data portion of each downline load message. The permitted range is 246 to 1482 bytes. The default value is 246 bytes, which should allow any client to load properly. Note that some clients may not support the larger size. The recommended size for better load performance and less server overhead is the largest size that results in successful loads of all clients. The 1482 value is derived from the maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less the 802e header and CRC (26 bytes) and MOP protocol overhead (10 bytes). You can override the size on a per-node basis. See DEFINE NODE and NODE for details. /PERMANENT_DATABASE Updates the device entries in the LAN volatile device database with any data currently set in the permanent database. This allows you to update the volatile database after changing data in the permanent database, rather than repeating the commands for each updated entry to apply the changes to the volatile database. /UPDATE Adds LAN devices that are not currently in the LAN volatile device database to that database. The initial entry for the device uses default values for all parameters. To update the volatile database with current information from the permanent database, use the SET DEVICE command with the /PERMANENT_DATABASE qualifier. You can combine the /UPDATE and /PERMANENT_DATABASE qualifiers in a single SET DEVICE command. 4 Examples 1.LANCP> SET DEVICE EXA0/MOPDLL=ENABLE Enables MOP downline load service for device EXA0, leaving the remaining MOPDLL parameters unchanged. 2.LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE,SIZE=1482) Enables MOP downline load service for device EXA0, in exclusive mode with the data transfer size of 1482 bytes, leaving the remaining MOPDLL parameters unchanged. 3.LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE) LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN) These commands enable LANACP MOP downline load service for: o LAN device EXA0 in nonexclusive mode o LAN device FXB0 in exclusive mode for only known clients 3 NODE Enters a node into the LAN volatile node database or modifies an existing entry. Requires SYSPRV privilege. Format SET NODE node-name 4 Parameter node-name Supplies the name of a node to be added to the LAN volatile node database or an entry to be modified. Typically, the node name is the same as that given in the system parameter SCSNODE, but it does not need to be. The node name is limited to 63 characters in length. 4 Qualifiers /ADDRESS /ADDRESS=node-address /NOADDRESS (default) Associates a LAN address with the node name. Specify the address as 6 bytes in hexadecimal notation, separated by hyphens. The address does not have to be unique (as might be the case when the address is not known, so a nonexistent address is specified). If multiple node addresses are to be associated with a node name, each combination may be given as a node name with an extension, for example, VAXSYS.EXA for the EXA device on node VAXSYS, or VAXSYS_1 for the first LAN device on node VAXSYS. If you do not specify the /ADDRESS qualifier, the setting remains unchanged. The /NOADDRESS qualifier clears the field. /ALL Defines data for all nodes in the LAN volatile node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A. /BOOT_TYPE /BOOT_TYPE=boot-option /NOBOOT_TYPE Indicates the type of processing required for downline load requests. You can specify one of the following keywords with this qualifier: o VAX_SATELLITE-a VAX satellite cluster boot o ALPHA_SATELLITE-an Alpha satellite cluster boot o OTHER-the specified image; noncluster satellite loads that do not require additional data The distinction is necessary, because OpenVMS Cluster satellite loads require additional cluster-related data be appended to the load image given by the /FILE qualifier. The default value is OTHER. If you do not specify the /BOOT_TYPE qualifier, the setting remains unchanged. The /NOBOOT_TYPE qualifier clears the field. /FILE /FILE=file-spec /NOFILE Supplies the file name of a boot file to be used when the downline load request does not include a file name (for example, OpenVMS Cluster satellite booting). The file specification is limited to 127 characters. If no file name is specified, OpenVMS Cluster satellite loads default to APB.EXE where the boot type is set to ALPHA and NISCS_ LOAD.EXE where the boot type is set to VAX. If you do not specify the /FILE qualifier, the setting remains unchanged. The /NOFILE qualifier clears the field. /PERMANENT_DATABASE Updates the node entries in the LAN volatile node database with any data currently set in the permanent database. This allows you to update the volatile database after changing data in the permanent database, rather than repeating the commands for each updated entry to apply the changes to the volatile database. /ROOT /ROOT=directory-specification /NOROOT Supplies the directory specification to be associated with the file name. For cluster satellite service, the /ROOT qualifier specifies the satellite root directory. For noncluster service, this qualifier specifies the location of the file. If the file specification or the file name given in the boot request includes the directory name, this qualifier is ignored. The directory specification is limited to 127 characters. If you do not specify the /ROOT qualifier, the setting remains unchanged. The /NOROOT qualifier clears the field. /SIZE /SIZE=value /NOSIZE Specifies the size in bytes of the file data portion of each downline load message. The default is the load data size specified for the device. The permitted range is 246 to 1482 bytes. Use a larger size for better load performance and less server overhead. If you do not specify the /SIZE qualifier, the setting remains unchanged. The /NOSIZE qualifier clears the setting. /V3 /V3 /NOV3 Indicates that only MOP Version 3 formatted messages are to be used for downline load purposes, regardless of the requested format. This allows systems to load that have a problem with MOP Version 4 booting. This qualifier causes the requesting node to fail over from MOP Version 4 to MOP Version 3 when no response has been made to a MOP Version 4 load request. If you do not specify the /V3 qualifier, the setting remains unchanged. The /NOV3 qualifier clears the setting. 4 Examples 1.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 - /FILE=APB.EXE - /ROOT=$64$DIA14:<SYS10.> - /BOOT_TYPE=ALPHA_SATELLITE This command sets up node VAXSYS for booting as an Alpha satellite into the cluster. The APB.EXE file is actually located on $64$DIA14: <SYS10.SYSCOMMON.SYSEXE>. Note that the <SYSCOMMON.SYSEXE> is supplied by the LANACP LAN Server process and is not included in the root definition. 2.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 - /FILE=NISCS_LOAD.EXE - /ROOT=$64$DIA14:<SYS10.> - /BOOT_TYPE=VAX_SATELLITE This command sets up node VAXSYS for booting as a VAX satellite into the OpenVMS Cluster. The NISCS_LOAD.EXE file is actually located on $64$DIA14: <SYS10.SYSCOMMON.SYSLIB>. The <SYSCOMMON.SYSLIB> is supplied by the LANACP LAN Server process and is not included in the root definition. 3.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33/NOROOT This command changes the LAN address associated with node VAXSYS and clears the current root specification. 4.SET 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 file name is received from node CALPAL. Because the file does not include a directory specification, the logical name LAN$DLL defines where to locate the file. You could give directory specification using 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. 2 SHOW 3 CONFIGURATION Displays a list of LAN devices and characteristics on the system. Format SHOW CONFIGURATION 4 Parameters None. 4 Qualifier /USERS On Alpha systems, shows which protocols are using which template device. 4 Example LANCP> SHOW CONFIGURATION LAN Configuration: Device Medium Default LAN Address Version ------ ------ ------------------- ------- EWA0 CSMA/CD 08-00-2B-E4-00-BF 02000023 EWB0 CSMA/CD 08-00-2B-92-A4-0D 02000023 IRA0 Token Ring 00-00-93-58-5D-32 20000223 This example shows the output from a SHOW CONFIGURATION command that was entered on a node that has three LAN devices, two DE435s, and a DETRA. The version is the device-specific representation of the actual (hardware or firmware) version. In this example, for two devices on the PCI bus, the actual version is in the low byte (2.3 for the DE435 adapters). A device that does not have a readable version is shown as version zero. Consult your device-specific documentation to correlate the version returned with a particular hardware or firmware implementation of the device. 3 DEVICE Displays information in the volatile device database. If the LANACP process is not running, displays a list of current LAN devices. Format SHOW DEVICE device-name 4 Parameter device-name Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. This refers to the LAN template device, for which is maintained most of the device parameters and counters. Also, the device name can refer to a device unit representing an actual user or protocol. For example, the cluster protocol can be started on a device as EWA1. You can specify specific device units to view unit-specific parameter information. If you do not specify a device name, all devices are displayed. If you specify a device name, all matching LAN devices are displayed, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. NOTE If you do not specify a qualifier, the utility displays the matching devices without additional information. 4 Qualifiers /ALL Shows all devices which match device name. /CHARACTERISTICS On Alpha systems, same as the /PARAMETERS qualifier. /COUNTERS Displays device counters. Devices: All LAN devices; template devices only. /DLL On Alpha systems, same as the /MOPDLL qualifer. They show downline load characteristics. /MAP Displays the current configuration of the functional address mapping table. Devices: Token Ring devices; template devices only. /MOPDLL Displays LAN volatile device database information related to MOP downline load for the device. /PARAMETERS Displays status and related information about the device. Devices: All LAN devices /REVISION Displays the current firmware revision of the device, if available or applicable. Not all LAN devices return revision information. LAN devices that do not have a revision display a revision of zero. Devices: LAN devices; template devices only. /SR_ENTRY Displays the contents of the current source routing cache table. Devices: Token Ring devices; template devices only. 4 Examples 1.LANCP> SHOW DEVICE/COUNTERS EXA0 Device Counters EXA0: Value Counter ----- ------- 259225 Seconds since last zeroed 5890496 Data blocks received 4801439 Multicast blocks received 131074 Receive failure 764348985 Bytes received 543019961 Multicast bytes received 3 Data overrun 1533610 Data blocks sent 115568 Multicast packets transmitted 122578 Blocks sent, multiple collisions 86000 Blocks sent, single collision 189039 Blocks sent, initially deferred 198120720 Bytes sent 13232578 Multicast bytes transmitted 7274529 Send failure 0 Collision detect check failure 0 Unrecognized frame destination 0 System buffer unavailable 0 User buffer unavailable This command displays counters for Ethernet device EXA0. 2.LANCP> SHOW DEVICE/MAP ICA0 Multicast to Functional Address Mapping ICA0: Multicast address Functional Address Bit-Reversed ----------------- ------------------ ------------ 09-00-2B-00-00-04 03-00-00-00-02-00 C0:00:00:00:40:00 09-00-2B-00-00-05 03-00-00-00-01-00 C0:00:00:00:80:00 CF-00-00-00-00-00 03-00-00-08-00-00 C0:00:00:10:00:00 AB-00-00-01-00-00 03-00-02-00-00-00 C0:00:40:00:00:00 AB-00-00-02-00-00 03-00-04-00-00-00 C0:00:20:00:00:00 AB-00-00-03-00-00 03-00-08-00-00-00 C0:00:10:00:00:00 09-00-2B-02-00-00 03-00-08-00-00-00 C0:00:10:00:00:00 09-00-2B-02-01-0A 03-00-08-00-00-00 C0:00:10:00:00:00 AB-00-00-04-00-00 03-00-10-00-00-00 C0:00:08:00:00:00 09-00-2B-02-01-0B 03-00-10-00-00-00 C0:00:08:00:00:00 09-00-2B-00-00-07 03-00-20-00-00-00 C0:00:04:00:00:00 09-00-2B-00-00-0F 03-00-40-00-00-00 C0:00:02:00:00:00 09-00-2B-02-01-04 03-00-80-00-00-00 C0:00:01:00:00:00 09-00-2B-02-01-07 03-00-00-02-00-00 C0:00:00:40:00:00 09-00-2B-04-00-00 03-00-00-04-00-00 C0:00:00:20:00:00 09-00-2B-02-01-00 03-00-00-00-08-00 C0:00:00:00:10:00 09-00-2B-02-01-01 03-00-00-00-10-00 C0:00:00:00:08:00 09-00-2B-02-01-02 03-00-00-00-20-00 C0:00:00:00:04:00 03-00-00-00-00-01 03-00-00-00-00-01 C0:00:00:00:00:80 03-00-02-00-00-00 03-00-02-00-00-00 C0:00:40:00:00:00 This command displays mapping information for Token Ring device ICA0. 3.LANCP> SHOW DEVICE/MOPDLL Device Listing, volatile database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes FXA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes This command displays MOP downline load information in the LAN volatile device database for all known devices. 4.LANCP> SHOW DEVICE/MOPDLL EXA0 Device Listing, volatile database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes This command displays MOP downline load information in the LAN volatile device database for device EXA0. 5.LANCP> SHOW DEVICE/PARAMETERS IRA0 Device Parameters IRA0: Value Parameter ----- --------- Normal Controller mode External Internal loopback mode 00-00-93-58-5D-32 Hardware LAN address Token Ring Communication medium Enabled Functional address mode No Full duplex enable No Full duplex operational 16 Line speed (megabits/second) 16 Mbps Ring speed STP Line media Enabled Early token release Disabled Monitor contender 200 SR cache entries 2 SR discovery timer 60 SR Aging Timer Enabled Source routing 3 Authorized access priority AA-00-04-00-92-FF Upstream neighbor 0 Ring number This command displays status and parameters information for Token ring device IRA0. 6.LANCP> SHOW DEVICE/REVISION FXA0 Device revision FXA0: 05140823 This command displays revision information for FDDI device FXA0. 7.LANCP> SHOW DEVICE/SR_ENTRY ICA0 Source Routing Cache Table ICA0: LAN address State XmtTmo RcvTmo StaleTmo DiscvTmo ----------------- ----- -------- -------- -------- -------- AA-00-04-00-92-FF LOCAL 00000028 00000028 00000245 00000000 This command displays source routing entry information for Token Ring device ICA0. 3 DLL This command is the same as the SHOW MOPDLL. 3 LOG Displays recent downline load activity (the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG). Format SHOW LOG 4 Parameters None. 4 Qualifiers None. 4 Example LANCP> SHOW LOG This command displays the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG. 3 MOPDLL Displays the current state of MOP downline load services for the system, including devices for which MOP loading is enabled and counters information. Format SHOW MOPDLL 4 Parameters None. 4 Qualifiers None. 4 Example LANCP>SHOW MOPDLL LAN MOP DLL Status: EXA enabled in exclusive mode for known nodes only, data size 1482 bytes FXA disabled #Loads Packets Bytes Last load time Last loaded ------ ------- ----- -------------------- ------------ EXA 5 1675 4400620 23-SEP-1994 10:27.51 GALAXY FXA 0 0 0 On this node, there are two LAN devices, EXA (DEMNA) and FXA (DEMFA). MOP downline load service is enabled on EXA in exclusive mode. Requests are answered only for nodes that are defined in the LANACP node database. The image data size in the load messages is 1482 bytes. There have been five downline loads, the last one occurring on node GALAXY at 10:27. Finally, there are no recorded downline loads for FXA, which is currently disabled for downline load service. 3 NODE Displays information in the LAN volatile node database. Format SHOW NODE node-name 4 Parameter node-name Specifies the name of a node in the LAN volatile node database. The name can include up to 63 characters associated with the node address. If you do not specify a node name, all nodes are displayed. 4 Qualifiers /ALL Displays information for all nodes in the LAN volatile node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A. /OUTPUT /OUTPUT=command-file-name Creates the specified file and directs output there in the form of a list of DEFINE NODE or SET NODE commands. The resulting command file can be used to create the LAN node databases. /TOTAL Display counter totals only, for the nodes selected. 4 Examples 1.LANCP> SHOW NODE Node Listing: GALAXY (08-00-2B-2C-51-28): MOP DLL: Load file: APB.EXE Load root: $64$DIA24:<SYS11.> Boot type: Alpha satellite ZAPNOT (08-00-2B-18-7E-33): MOP DLL: Load file: NISCS_LOAD.EXE Load root: LAVC$SYSDEVICE:<SYS10.> Boot type: VAX satellite CALPAL (08-00-2B-08-9F-4C): MOP DLL: Load file: READ_ADDR.SYS Last file: LAN$DLL:APB_X5WN.SYS Boot type: Other 2 loads requested, 1 volunteered 1 succeeded, 0 failed Last request was for a system image, in MOP V4 format Last load initiated 10-JUN-1996 09:11:17 on EXA0 for 00:00:06.65 527665 bytes, 4161 packets, 0 transmit failures Unnamed (00-00-00-00-00-00): Totals: Requests received 2 Requests volunteered 1 Successful loads 1 Failed loads 0 Packets sent 2080 Packets received 2081 Bytes sent 523481 Bytes received 4184 Last load CALPAL at 10-JUN-1996 09:11:17.29 This example shows output from a command issued on a local node on which there are three nodes defined (GALAXY, ZAPNOT, and CALPAL). CALPAL has issued two load requests: o The first request is the multicast request from CALPAL that the local node volunteered to accept. o The second request is the load request sent directly to the local node by CALPAL for the actual load data. The elapsed time from the second load request to completion of the load was 6.65 seconds. 2.LANCP> SHOW NODE VAXSYS Displays node characteristics and counters information from the LAN volatile node database for node VAXSYS. 3.LANCP> SHOW NODE/ALL VAX Displays node characteristics and counters information from the LAN volatile node database for all nodes whose name begins with VAX. 4.LANCP> SHOW NODE/ALL Displays node characteristics and counters information from the LAN volatile node database for all nodes. 5.LANCP> SHOW NODE/ALL/OUTPUT=TMP.INI Writes a list of all nodes to the file TMP.INI. 2 SPAWN Creates a subprocess of the current process. The SPAWN command copies the context of the subprocess from the current process. Format SPAWN [command-string] 3 Parameter command-string A string of commands to be executed in the context of the created subprocess. After the command string is executed, control returns to LANCP. 3 Qualifiers None. 3 Example LANCP> SPAWN $ MC LANCP LANCP> DEFINE NODE BOOM/ROOT=LAVC$SYSDEVICE:<SYS22.> LANCP> SPAWN SEARCH LAVC$SYSDEVICE:[*.SYSEXE]MOD*.DAT BOOM ****************************** LAVC$SYSDEVICE:[SYS1A.SYSEXE]MODPARAMS.DAT;1 SCSNODE="BOOM " LANCP> DEFINE NODE BOOM/ROOT=LAVC$SYSDEVICE:<SYS1A.> In this example, you enter the node information for a node, but are unsure of the root, so you spawn to search MODPARAMS.DAT for the node name and then correct the root. 2 TRIGGER 3 NODE Issues a request to reboot to a remote node. Rather than specify the format to send MOP Version 3 or 4, the LANCP utility sends one message in each format to the target node. Format TRIGGER NODE node-specification 4 Parameter node-specification Supplies either the node name or the node address of the target node. If you supply the node name, the node address is obtained by looking up the node name in the LAN volatile node database. If you supply the node address, the corresponding node need not be defined in the LAN volatile node database. The canonical form of the address consists of 6 hexadecimal byte characters separated by hyphens. Use a colon as the separator character to indicate the bit-reversed form of the address. 4 Qualifiers /DEVICE /DEVICE=device-name Specifies the LAN controller device name to be used for sending the trigger boot messages. For example, you can specify a DEMNA controller as EXA, EXA0 or EXA0:. /PASSWORD /PASSWORD=16hexdigits Supplies the password to be used when the connection is initiated, in hexadecimal (for example, /PASSWORD=0123456789ABCDEF). The default password is zero. You can omit leading zeros. 4 Examples 1.TRIGGER NODE GALAXY/DEVICE=EWA0 This command sends MOP trigger boot messages to node GALAXY using Ethernet device EWA0. 2.TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789AB This command sends MOP trigger boot messages to the given node address using the Ethernet device EWA0, with indicated password. 2 UPDATE 3 DEVICE Alpha only. On Alpha systems, updates firmware image for a device. Requires SYSPRV privilege. Format UPDATE DEVICE device-name 4 Parameter device-name Specifies a device whose firmware is to be updated. The device name has the form ddcu where dd is the device code, 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 DE435 Ethernet device is specified as EWA0, the second as EWB0. 4 Qualifiers /FILE /FILE = filename Specifies the name of the file that is to be loaded into the EEPROM of the LAN device. /RESET /RESET (default) /NORESET Specifies whether the device is to be reset after it has been updated. Normally, a reset is done to get the device to begin running the new firmware. 4 Example LANCP> UPDATE DEVICE FAA0/FILE=FBUS_MAIN.SYS Updates FDDI device FAA0 with the firmware file FBUS_MAIN.SYS followed by a reset.

© 1997- Marc Vos (and others) Contact Me