Platform Notes: SPARCstation Voyager Software Guide

Using the SPARCstation Voyager in Nomadic Mode

Once you have configured it, you can disconnect your SPARCstation Voyager by simply unplugging the Ethernet cable. You can avoid reconfiguring and rebooting, as you would in a deskbound system, by configuring the Solaris 2, Edition II (or later) operating system environment in nomadic mode. Refer to Chapter 6, Configuring for Point-to-Point Protocol Connections for a detailed discussion of the procedures you need to perform after you install the operating system.

The nomadic operating mode allows SPARCstation Voyager to be connected to an IP network that provides ONC+ (NFS, NIS, NIS+, etc.) and Internet services (mail, ftp, rlogin, etc.), and also to be disconnected from the network and operated for extended periods of time with no network connection.

It is not possible to achieve this kind of connection flexibility without some constraints, but they are minimal.

The system will not be able to access all the data kept in distributed NIS/NIS+ databases
The system will not be able to provide ONC+ or Internet services to other machines, even when connected to a network.

Basic Considerations for Disconnected Operation

After you have made your SPARCstation Voyager disconnectable, you have to use it a little differently.

Creating and using a local home directory on your SPARCstation Voyager can make using your system in nomadic mode easier. Refer to "Creating a Local Home Environment" of Chapter 5, Configuring for Disconnected Operation for instructions.

Always start OpenWindows from a shell whose current working directory is contained on the local SPARCstation Voyager file system, such as your local home directory. Otherwise, when SPARCstation Voyager is disconnected, OpenWindows stops functioning.

When you operate a SPARCstation Voyager disconnected from the network, remote services are not available. NIS and NIS+ databases, such as hosts, and NFS mounted directories cannot be accessed. Refer to "Name Service Configuration" in Chapter 5, Configuring for Disconnected Operation for a complete list.

Before you disconnect the system from the network:

cd out of all NFS mounted directories.

Terminate any remote login sessions such as rlogin, telnet, or ftp.

Terminate any remote clients that display windows on the local Xsun (X11) server.

Wait about five minutes for the automounter to unmount all directories you cd'd out of in Step 1. Or, as root, type unmountall -F nfs.

If you cannot follow the above disconnection guidelines (you are late for a meeting and you want to pull the plug, for example), the system will continue to operate. Minor inconveniences may occur.

For example, it is possible to be in a working directory that is contained on a remote file system or to execute a command, such as ls or cd, that accesses a remote file system. If this happens, the command you executed will appear to stop and not return, and probably the shell that you executed it in will not process further commands.

If you do not want to wait for the system to notice the error and recover by itself (it could take a long time), you can terminate the command (by typing Control-c, for example) or change the working directory back to the home directory. If necessary, quit the window in which the command or shell is running.

Any client/server application with a remote component will not continue to work when the network is disconnected. Those that are stopped may fail when the network is reconnected, or if they are "touched," although it is usually safe to iconize them.

Any remote login sessions in effect at the time of disconnection will stop processing commands. You can leave them alone or terminate them. Few sessions will persist over long periods of disconnection.

While all OpenWindows deskset applications will survive across network transitions from connected to disconnected states, some of them may not operate as well while disconnected.

Occasionally, other problems occur if the Ethernet interface (le0) is not left UP at disconnection. If the interface is DOWN, you cannot open Calendar Manager, nor can you invoke admintool. The solution to these problems is to bring the interface UP using ifconfig. See the man page for information on how to manipulate the state of the interface.