VMS Help LANCP, CONNECT *Conan The Librarian (sorry for the slow response - running on an old VAX) |
1 - 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
1.1 - 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.
1.2 - Qualifiers
1. 2.1 - /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:.
1. 2.2 - /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.
1. 2.3 - /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.
1. 2.4 - /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
1. 2.5 - /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
1.3 - Examples
1.LANCP> CONNECT NODE GALAXY/DEVICE=EWA0 This command attempts a console-carrier connection to node GALAXY using the Ethernet device EWA0. 2.LANCP> 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.
|