For a netcon session, typically you log in to the SSP machine as user ssp, and enter the netcon command in an SSP window. For example:
ssp% domain_switch domain_name
ssp% netcon
This action changes the window in which you run the netcon command into a netcon window for the domain specified by the domain_switch command. Multiple netcon windows can be opened simultaneously, but only one at a time can have write privileges to a specific domain. When a netcon window is in read-only mode, you can view messages from the netcon window, but you cannot enter any commands.
You can specify the netcon option -g for Unlocked Write permission, -l for Locked Write permission, -f to force Exclusive Session mode, or -r for read only mode. See the netcon man page for an explanation of how netcon behaves if you do not specify any of these arguments.
If you have write permission, you can enter commands. In addition, you can enter special commands prefixed by atilde (~) to perform the functions offered by the netcontool window.
The netcontool GUI program provides the buttons shown below:
The following table explains the netcontool buttons:
% xhost +
ssp% domain_switch domain_name
ssp% setenv DISPLAY 192.168.56.60:0
ssp% netcontool &
Click the Connect button in the netcontool window.
This displays the netcon window. Netcon attempts to connect to your chosen domain. If no error occurs, the netcon window is displayed directly beneath the netcontool window. Note that these are two separate windows, although they can affect each other. You can view messages in the console window and, if you have write permission, enter commands.
Log in to the SSP as user ssp.
Type:
ssp% domain_switch domain_name
ssp% netcon
For more information about the netcon command options, refer to the netcon man page.
Type the following escape sequence (tilde (~) followed by a full-stop) in the netcon window:
# ~.
If you enter the tilde full-stop sequence locally at the SSP workstation or remotely through a telnet session, your netcon session is terminated and the window returns to its previous state. However, if you enter the tilde full-stop sequence remotely through an rlogin session, the netcon session is terminated and the rlogin window is deleted as well. This is because the tilde full-stop sequence is recognized by rlogin as an exit command. If you want to avoid this behavior, you can use the sequence ~~., that is tilde tilde full-stop, to exit from a netcon window running inside of an rlogin session. For more information about escape sequences, see the netcon manual page.
Log in to the SSP as user ssp.
Type:
ssp% domain_switch domain_name
ssp% netcontool &
Select a board from the domain for which you want to display a netcontool window by clicking on that board with the left mouse button.
Select Terminal netcontool.
In the netcontool window, click the Connect button.
The netcontool window is displayed beneath the netcontool buttons.
Click the Configure button if you want to configure the netcontool window before you display a netcon window.
The Console Configuration window is displayed
netcontool Console Configuration Window
-
Select the session type in the left panel, and the terminal emulation type in the right panel.
-
When you are satisfied with the contents of the window, you click Done to accept the settings and dismiss the window, or click Apply to accept the settings without dismissing the window.
The following table contains the options in the Console Configuration. window.
netcon Communications
netcon uses two distinct paths for communicating console input/output between the SSP and a domain: the standard network interface and the CBE interface. Usually, when the domain is up and running, console traffic flows over the network. If the local network becomes inoperable, all interactive access to the domain is lost and, for example, telnet, rlogin, and netcon sessions hang. In this case, you can switch to the CBE interface and access the host's console window. To perform this switch, use the ~ = command in the netcon window.
netcon Message Logging
Certain messages sent from the kernel are not displayed in the syslog messages file, such as OpenBoot messages, panic messages, and some console messages. The reason for this is that syslogd must run on the host to log the messages, and this is not possible when a panic occurs, nor is it possible at certain times during the boot sequence. Moreover, panic dumps often fail, so these types of messages may not even appear in a dump file to help you determine the cause of the failure.
However, you can capture all output displayed on an active netcon console through the LOCAL1 facility of syslog and the SSP machine_server. This functionality is enabled through the /etc/syslog.conf and
$SSPLOGGER/.logger files. When enabled, netcon session output is recorded in file $SSPLOGGER/domain_name/netcon, where $SUNW_HOSTNAME is set to the hostname for the domain. By default, this functionality is disabled.
© Grenville Consulting Ltd.