ChorusOS 4.0.1 Simulator for the Solaris Operating Environment (SPARC Platform Edition) User's Guide

Getting Started Quickly

Follow the procedure below to get quickly up and running with one or more simulators on a single host. References to later sections provide links to further information about each step.

Create a file called site_number.conf in the /usr/local/chorus/simu_admin directory with the following lines:
```
   1    hostname    2052    2.1.1.2
2    hostname    2053    2.1.1.3
```
hostname is the name of your Solaris host.

See "Enabling Dynamic Configuration" for more information.

Create a file called simudrv.conf also in the /usr/local/chorus/simu_admin directory with the following line:
```
   2.1.1.1    hostname
```
hostname is the name of your Solaris host.

See "Configuring the Solaris Ethernet Pseudo-driver" for more information.

Within the sysadm.ini file in the build_dir/conf directory:
- Find the comment # Using ifconfig then add the following line on the next line:
```
   ifconfig ifeth0 TAG.TGT.IPA.TAG netmask 0xff000000 broadcast 2.255.255.255
```
  See "Configuring the Simulator IP Address" for more information.
- Add the following line on the line after:
```
   route add default 2.1.1.1
```
  See "Configuring the Gateway for the Simulator" for more information.
- Find the line rarp ifeth0 then comment out the rarp command by adding a hash to the beginning of the line:
```
   #rarp ifeth0
```

If you wish to communicate with your simulator remotely from another machine, configure IP forwarding by entering the following command on your Solaris host with super-user privileges:
# ndd -set /dev/ip ip_forwarding 1
See "Configuring IP Forwarding for Your Host" for more information.

Change to the Solaris Ethernet pseudo-driver sub-directory:
$ cd install_dir/tools/host/simu_drv
Launch the Solaris pseudo-driver by entering the following command on your Solaris host with super-user privileges:
# sh simudrv start
See "Running the Solaris Ethernet Pseudo-driver" for more information.

Change to your build directory and build a simulator system image:
$ make chorus

Start the simulator using the loader command:
$ loader chorus.RAM 1
See "Booting the Simulator System Image" for more information.

You can run a second simulator with the following command:
$ loader chorus.RAM 2
You can run additional simulators by adding entries to site_number.conf and using the loader command to start each simulator.

Test that the simulator can be reached from the supporting Solaris host with the ping command:
$ ping 2.1.1.2
You should receive the message 2.1.1.2 is alive.

Test that the supporting Solaris host can be reached from the simulator with the ping command:
$ rsh 2.1.1.2 ping 2.1.1.1
If you receive the message 2.1.1.1 is alive, you can start developing applications on the simulator as you would on a physical target.