|
 |
|
Sharing Hard Disks between two VCS systems.
With two VCS systems, a mini-network can be created to share (or store) files
between the systems.
This document describes the procedure for using a simple network to connect
two VCS systems in order to share files on the hard disks. Example values
are used and identified with italic font.
-
Hardware You Need First
-
Two un-networked VCS system(s) running.
-
One 10BaseT Ethernet cables with RJ45 connectors (purchased from Sun or your
local computer store).
-
Decisions to Make First
-
Each system must have a unique host name and Internet Protocol (IP)
address.
-
Note: when selecting a host name for each system, select names with which
you can quickly identify each system. (example: SD2552-8 and SD2552-4
are two host names identifying an eight channel system and a four channel
system)
Note: when selecting an Internet Protocol (IP) address, chose a Class C network.
Class C network addresses are 3 decimal numbers in the range 0-255 and separated
by dots and starting at 192.0.0 and extending to 223.255.255. The host number
on the network is a decimal number in the range 1-254 and is appended to
the network address. (example: Class C network 192.193.194 has two hosts
with host numbers, 8 and 4. Therefore, the IP address of each host is:
192.193.194.8 and 192.193.194.4)
-
Note: Your 192.193.194 network may be only used internally without problems,
but before you can connect your network to the outside world (i.e. the Internet),
you must request an official registered network number from the following
location:
-
Procedure to Network the VCS systems
-
All systems
-
Physical network connection.
-
Connect the10baseT cable to the RJ45 Ethernet receptacle on the rear of each
Sun workstation. The RJ45 Ethernet receptacle is identified with the label:
-
Reconfigure each workstation for network application.
-
Open an Xterm window (Workspace | Xterm) and enter the following commands:
-
% su
# sys-unconfig
yes
-
(messages at bottom of white screen)
ok boot
Host name: SD2552-8 (and SD2552-4)
Networked: Yes
-
(press 'down arrow' or 'up arrow' until 'Yes' is bolded and press 'Return')
-
press the F2 key
IP address: 192.193.194.8 (and
192.193.194.4)
Confirmation Information
Name Service: None
-
(press 'down arrow' or 'up arrow' until 'None' is bolded and press 'Return')
-
press the F2 key
Confirmation Information
Subnets: No
-
(press 'down arrow' or 'up arrow' until 'No' is bolded and press 'Return')
-
press the F2 key
Time Zone:
-
(press 'down arrow' or 'up arrow' until correct region is bolded and press
'Return')
-
press the F2 key
Time Zone:
-
(press 'down arrow' or 'up arrow' until correct time zone is bolded and press
'Return')
-
press the F2 key
Date and Time:
-
(enter the correct date and time)
-
press the F2 key
Confirmation Information
Root Password:
-
(Enter twice) (the factory default is 'manager')
-
(more boot messages)
(Login to 'vcs' as usual)
-
Configure network files.
-
Open an Xterm window (Workspace | Xterm) and enter the following commands:
The 'Admintool' window appears. Make the following selections and entries:
-
Browse | Hosts
(for each system, add the Host Name and IP Address of the other system.)
Edit | Add …
-
Host Name: SD2552-4
IP Address: 192.193.194.4
(press OK)
File | Exit
Note: The IP address 127.0.0.1 for 'localhost' is called the "loopback" address
and is used by Sun Solaris systems to send messages to itself. This scheme
is used in Solaris Operating System inter-process communications, such as
sockets.
-
The Shared System (system that shares its files, eg SD2552-4)
-
The Reading System (system that reads files from the shared system.
eg SD255-8)
-
Open an Xterm window and enter the following commands:
% su
# mkdir /4chan
# mount SD2552-4:/usr/home/vcs /4chan
-
The files on the 4 channel system at the '/usr/home/vcs' directory are now
accessed at the '/4chan' directory.
-
-
Testing the Network
-
From each system, open an Xterm window and contact all other systems on the
network with the following command: (example: on SD2552-4)
-
% ping SD2552-8
SD2552-8 is alive
If the message 'unknown host SD2552-8' appears, then the host name
cannot be resolved into an IP address. Use admintool to verify the correct
host names. Try to 'ping' the IP address.
If the message 'network unreachable' appears, the local system does
not have a route to the remote system. Check cable connections.
If the message 'no answer from SD2552-8' appears, the remote system
did not respond. Check the power switch on the remote host. Also, use 'admintool'
to verify the correct host names.
-
From each system, open an Xterm window and enter the following commands:
-
% su
# ifconfig le0
le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
inet 192.193.194.4 netmask ffffff00 broadcast 192.193.194.255
ether 8:0:20:xx:xx:xx
The 'ifconfig' command checks the network interface configuration, in this
case, le0 is the Ethernet interface. Look for the flags 'UP' and 'RUNNING'.
If there is no 'UP' flag, enter the following commands:
-
# ifconfig le0 up
# ifconfig le0
Also, check the IP address for accuracy.
-
You can also view the network traffic as it occurs. On the 'SD2552-4' system,
open an Xterm window and enter the following commands:
-
% su
# snoop SD2552-4
where: SD2552-4 is the host name of the local workstation.
This command will print network traffic to and from the local workstation.
Open another Xterm window and enter the following commands:
-
% ping SD2552-8
where: SD2552-8 is the host name of a remote workstation.
On the 'snoop' window you should see the following message;
-
SD2552-4 -> SD2552-8 ICMP Echo request
SD2552-8 -> SD2552-4 ICMP Echo reply
If this network traffic does not occur, use 'admintool' to check for correct
host names and IP addresses.
-
Returning to Un-networked Configuration
-
On each workstation, open an Xterm window (Workspace | Xterm) and enter the
following commands:
-
Unplug the Ethernet cable from the back of each workstation.
|
|
