NAME | SYNOPSIS | DESCRIPTION | OPTIONS | USAGE | NOTES | ENVIRONMENT VARIABLES | SEE ALSO
The netcon command creates a remote connection to the domain host console program, making the SSP window in which the command is executed a Console Window for the domain specified by the SUNW_HOSTNAME environment variable. See also netcontool(1M), a menu-driven program that executes netcon.
Many Domain Console Windows (also called console sessions) can be open simultaneously on systems throughout the network, and all can read corresponding domain host output. But only one at a time can have write permission for a particular domain. Write permission is in either Unlocked or Locked mode.
Unlocked Write permission is not very secure, as it is taken away if another console session is started via netcon -g, netcon -l or netcon -f, or if ~@, ~& or ~* is executed in another Domain Console Window. (Tilde commands are described in the USAGE section, below.)
Locked Write permission is more secure. It can be taken away only if another console session is opened via netcon -f, or if ~* is executed in another Domain Console Window. In both cases, the new console session is an Exclusive Session, and all other sessions are killed.
If you execute netcon with no options at a time when no other console sessions for that domain have write permission, your Domain Console Window comes up with Unlocked Write permission. If another session already has write permission, your session comes up Read Only.
netcon can utilize either the standard network interface or the JTAG interface for Domain Console Window communication. You can manually toggle between these interfaces via the tilde-equals (~=) command.
All options are mutually exclusive except the -e, which can be used with any of the others. If you specify more than one of the other options, netcon uses the option that carries the highest precedence, in the following order: -f, -l, -g, then -r.
Turn on debug mode. Do not use this option without first consulting your service advisor.
Change the default escape character (~) to esc_char, where esc_char can be any character except the following: @ # ^ & * () = | ' [ ; " ' < > . ?
(Force option) Open a Domain Console Window with Locked Write permission, terminate all other open sessions, and prevent new sessions from being opened. This option starts Exclusive Session mode. Use it only when you need exclusive use of the console; for example, for a private debugging session.
Note: To restore multiple-session mode, either release the lock (by using ~^) or terminate the netcon -f session (by using ~.). See USAGE, below.
(Grab option) Open a Domain Console Window with Unlocked Write permission. If another session has Unlocked Write permission, the new Domain Console Window takes it away. If another session has Locked permission, this request is denied and a read-only session is started.
(Lock option) Open a Domain Console Window with Locked Write permission. If another session has Unlocked Write permission, the new Domain Console Window takes it away. If another session has Locked permission, this request is denied and a read-only session is started.
(Read Only option) Open a Domain Console Window with Read Only permission.
In a Domain Console Window, a tilde (~) that appears as the first character of a line is interpreted as an escape signal that directs netcon to perform some special action, as follows:
Break to OBP or kadb.
Disconnect and exit the netcon session.
Acquire Unlocked Write permission; see -g.
Release write permission.
Show status of all open console sessions and the communication path currently in use.
Toggle the communication path between the network and JTAG interfaces. You can use ~= only in private mode (by using ~*).
Acquire Locked Write permission; see -l. You may issue this signal during a read-only or Unlocked Write session.
Acquire Locked Write permission, terminate all other open sessions, and prevent new sessions from being opened; see -f. To restore multiple-session mode, either release the lock or terminate this session.
In the Domain Console Window, vi(1) runs properly and the escape sequences (tilde commands) work as intended only if the environment variable TERM has the same setting as that of the Netcon Window. For example, in the window in which the netcon command was run, TERM is set to xterm, TERM in the Domain Console Window must be set to xterm, too.
The following error message indicates that netcon_server(1M) has died or bringup(1M) has not been run on a domain:
netcon_server is not running for domain_name. |
If you get this error message, you can restart the netcon session by running netcon_server -r. If this does not work, run bringup(1M).
netcon session logging is enabled by default, and the output is recorded in the /var/opt/SUNWssp/adm/domain_name/netcon file.
If you use a kill -9 command to terminate a netcon console session, the window or terminal in which the netcon command was executed goes into raw mode, and appears hung. To escape this condition, type ^j, then stty sane, then ^j.
If you have a netcon session that cannot be toggled to network communication mode, do the following:
The environment variable SUNW_HOSTNAME must be set to the name of the domain.
boot(1M), cvcd(1M) in the Solaris Reference Manual
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | USAGE | NOTES | ENVIRONMENT VARIABLES | SEE ALSO