Before you power up for the first time, you should you fill out the information required for the Appendix B, “Network Connectivity Worksheet”.
Immediately after you power up for the first time, you will be asked if you want to run Linuxconf to set up your networking. You should answer Yes. The curses-based interface to Linuxconf will be invoked.
To use Linuxconf to enter the network connectivity information, do the following:
Press the Tab and Enter keys to quit out of the initial help screen.
Using the arrow keys and the Enter key, open the following tabs in succession:
Config -> Networking -> Client tasks -> Basic host configuration
Enter in the appropriate information from your Appendix B, “Network Connectivity Worksheet”.
Note: You must indicate a fully qualified domain name hostname when entering the Host Name field in Linuxconf. This is needed to properly launch the Linuxconf HTTP interface from the Web administration graphical user interface. The following is an example for a system with two network interfaces, eth0 and eth1. The latter will be used for private networking. The example shows user input in bold; when performing your own configuration, please remember to substitute your own names and IP addresses.
Note: If you have decided to mount and cable up the system in your production rack, ensure that no one can access eth0 until you are ready to bring the system into full production. The safest ways to do that are as follows: Do not to plug in eth0.
Do not enable the interface at this time. You can enable eth0 later.
+--------------------------------------------------+ | -------- Host Name -------- | |Host Name foo.bar.com | | -------- Adapter 1 -------- | | [ ] Enabled | |Config mode (o)Manual ( )Dhcp ( )Bootp | |Primary name + domain foo-eth0.bar.com | |Aliases (opt) www.yourcorp.com foo-pub | |IP address 1.2.3.4 | |Netmask (opt) 255.255.255.0 | |Net device eth0 | |Kernel module eepro100 | | -------- Adapter 2 -------- | | [X] Enabled | |Config mode (o)Manual ( )Dhcp ( )Bootp | |Primary name + domain foo-eth1.bar.com | |Aliases (opt) foo-priv foo | |IP address 1.2.100.4 | |Netmask (opt) 255.255.255.0 | |Net device eth1 | |Kernel module eepro100 | +--------------------------------------------------+
Press the Tab key to navigate to the Accept button and then press the Enter key.
Specify the plain host name (up to but not including the first ".") as an alias to your private interface eth1. This enables you to launch the Linuxconf HTTP interface directly from the Web administration graphical user interface (GUI).
Open the following tabs:
Config -> Networking -> Client tasks -> Name server specification (DNS)
Enter in the SGI server IP addresses from your Appendix B, “Network Connectivity Worksheet”.
For example:
+--------------------------------------------------+ |DNS usage [X] DNS is required ... | |Default domain | |Nameserver 1 127.0.0.1 | |Nameserver 2 | +--------------------------------------------------+
There is a default cache-DNS server configured on this system. For it to work properly, the address 127.0.0.1 must be the first Nameserver listed in the /etc/resolv.conf file.
Accept your settings by pressing Tab to move to the Accept button and then pressing Enter.
Open the following tabs:
Config -> Networking -> Client tasks -> Routing and gateways -> Defaults
Enter in the gateway IP address from your Appendix B, “Network Connectivity Worksheet”. Do not enable routing; there is normally no reason for a front-end production system to route or forward packets.
For example:
+--------------------------------------------------+ |Default gateway 1.2.3.1 | |Enable routing [ ] | +--------------------------------------------------+
Accept your settings.
Quit Linuxconf by using the Tab key to navigate to the Quit button.
 | Warning: This software product is highly dependent on the hostname, domain name, and IP address of the system. Any change of these parameters will require a reinstallation as described in Appendix C, “Reinstalling from CD-ROM”. |