FAQ ¾¾
How to boot the Accelar
with the JVM/ORE boot image?
1. What are the licenses of the
Accelar JVM/ORE boot package?
2. How does the Accelar boot
with the JVM image?
4. What are included in the
Accelar boot package?
5. How can I setup a TFTP
server?
7. How can some services start
at the ORE startup?
8. If I have only one subnet,
how I can boot the Accelar JVM image and load the ORE?
9. I have two separated subnets
for management and experiment, how I can boot the Accelar?
10. How I can access the ORE
after the Accelar starts it?
At first you have to get the JVM/ORE boot package of the Accelar 1100B routing switch with particular licenses. This boot package (zipped) includes two software parts: the JVM boot image and the ORE release. Of them, the ORE is under the Nortel Networks (or Nortel) license and the JVM is under the license of a non-Nortel company.
You should put the JVM boot image on a TFTP server rather than on the Accelar itself. The ORE release can be stored on an HTTP or FTP server.
The Accelar boots the JVM boot image from a TFTP server, which provides the Accelar access to the boot image through the TFTP protocol. Any system supporting TFTP can be used as a TFTP server, e.g., Solaris and Linux. That image also contains an internal interface that is used to load the whole ORE.
When booting the Accelar is done, it is ready to load the ORE and related service codes using a URL (either HTTP or FTP). You can input it by “telnet <accelar> 1966”. Once the URL is inputted, the Accelar automatically download these codes from the downloading server specified by the URL.
If you receive a boot package from Nortel Networks, it is a zipped file “ore_acc1k.zip”. After unzipping it (you should receive an unzipping password too), you get the below major files.
acc-0.31.0:
the Accelar JVM boot image
ore-0.3.0.tar2.gz:
the ORE release 0.3.0 (gzipped)
ore.accelar1.txt:
info about the above two software
openetlab_license.pdf:
the Nortel Networks software license
As an example, if you have a Linux box, you need to start the TFTP daemon (tftpd) manually or add it in “/etc/inetd.conf” (by uncommenting the tftpd line) and re-initialize inetd. Then, copy the JVM image file “acc-0.31.0” to the TFTP root directory “/tftpboot”.
On a Linux box, you can set up an HTTP service using the Apache HTTP software. Then, uncompress the ORE release (using gunzip) in a local directory, and copy the sub-directory “jars/” to the HTML directory (e.g., /home/httpd/html). You thus have a new directory “/home/httpd/html/jars/” and make sure that it is accessible from the Internet browser. Now, the ORE URL is “http://<HTTP_SERVER_HOST>/jars”.
You can do it by changing the property of the ORE start service. In the ORE jar directory (e.g. /home/httpd/html/jars/), edit the file “start.properties” to add or remove those services at the ORE startup.
If you have only one subnet (e.g., 192.168.1.0) which comprises both TFTP (for JVM) and HTTP (for ORE) servers, wire the server box(es) to the front ports of the Accelar switch. Suppose that the TFTP server IP address is 192.168.1.1 and the HTTP one is 192.168.1.2, you can create a Vlan on the Accelar box to assign an IP address 192.168.1.254.
To specify the Accelar IP address, you firstly boot the Accelar using the built-in image (without the JVM support), and become the administrator (i.e., rwa) to type the below command.
Accelar-1100# config vlan 1
ip create 192.168.1.254/255.255.255.0
If the TFTP server is ready, you can boot the Accelar to use the JVM boot image. The boot command is below.
Accelar-1100# boot tftp ip
192.168.1.1 file acc-0.31.0
Booting the image is done if the Accelar console prints the below messages (it may take 2 or 3 minutes).
Startup: Java 32768, System
659456
CONSOLE: ORE
built Wed Feb 9 10:53:59 PST 2000
CONSOLE: Listening for
invocation parameters on:
ServerSocket[address=0.0.0.0/0.0.0.0,port=0,localport=1966]
Now, you can input the ORE URL on a host by typing
LINUX 1003> telnet
192.168.1.254 1966
Trying 192.168.1.254...
Connected to 192.168.1.254.
Escape character is '^]'.
Please give ORE invocation
parameters:
http://192.168.1.2/jars/start.jar
If you have two subnets separated, you can use additional Accelar management software (downloading from the Openetlab website) for managing your Accelar switches. Moreover, you can boot the JVM much faster (in less than 1 minute).
The management network comprising the TFTP and HTTP servers is connected to the Accelar through its unique back port (that is assigned with an IP address), while the experiment network uses the front ports to do your project work. The two networks should NOT be the same subnet! Otherwise, the Accelar detects (packet) frame collisions and aborts the booting.
Let’s suppose that the management network is similar to the network in Question 8, i.e., 192.168.1.0/24, and the experiment network is 10.0.1.0/24 or any else. When the Accelar boots and displays “Press any key to stop autoboot”, strike any key to stop the autoboot process. Now, you enter the Accelar monitor mode.
Accelar Monitor v2.0.5
CPU: 60Mhz PPC 403GCX Type 3 Rev
2 in Slot 4
DRAM: 32M
Chassis: 1100
Reason for Last Reset:
PWR/BUTTON/SOFT
Slot 3 is occupied
Power supply 2 not present
Here types “?” for a list of commands.
monitor> ?
boot boot an image from a device
choices change boot order
copy copy file to device
delete delete file from device
devices enable/disable boot devices
directory list files on device
flags change boot flags
format format device
help enter help <command> for additional information.
history list command history
ip change ip address information
log system log file information
ping ping an ip address on a networ
...
Firstly, change the primary boot choice to use “TFTP”, i.e., net.
monitor> choices
--- CHANGE BOOT CHOICES ---
Current Boot Choices :
Primary = flash
Secondary = flash:ac1a2055.img
Tertiary = net
Config = nvram
1 - Change primary bootsource
2 - Change secondary bootsource
3 - Change tertiary bootsource
4 - Change configuration bootsource
0 - cancel
select boot choice to change
[1]: 1
Boot Source Choices are -
flash(1), pcmcia(2), net(3), skip(4) nvram(5)
Enter new boot choice (You must
enter 1, 2, 3, 4, or 5) [1]: 3
Enter File Name []: acc-0.31.0
User Selected Boot Sources
---------------------------
Primary = net:acc-0.31.0
Secondary = flash:ac1a2055.img
Tertiary = net
Config = nvram
Autoboot is enabled
Factory defaults is disabled
Switch port isolation is
disabled
---------------------------
boot configuration has been
saved
Secondly, make the TFTP settings.
monitor> tftp
Enter tftp server address
[134.177.116.40]: 192.168.1.1
Enter tftp file [acc.isl.ore]: acc-0.31.0
boot configuration has been
saved
Thirdly, enable the back port (i.e., the management or debug port).
monitor> devices
--- ENABLE AND DISABLE BOOT DEVICES ---
Boot Devices:
------------------------------------------------------------------
0 Enabled System Memory [dram] addr:0x0 sz:0x2000000
1 Enabled on-board flash memory [flash]
vendor:unknown sz:0x400000 bsz:0x10000
5 Disabled Debug Ethernet [nic] hw=00:80:2d:65:ab:00
ip=192.168.0.254 netmask=0xffffff00
mgmt net=0.0.0.0 gateway=0.0.0.0
------------------------------------------------------------------
select device to change [5]: 5
[nic] boot is enabled
Boot Devices:
------------------------------------------------------------------
0 Enabled System Memory [dram] addr:0x0 sz:0x2000000
1 Enabled on-board flash memory [flash]
vendor:unknown sz:0x400000 bsz:0x10000
5 Enabled Debug Ethernet [nic] hw=00:80:2d:65:ab:00
ip=192.168.0.254 netmask=0xffffff00
mgmt net=0.0.0.0 gateway=0.0.0.0
------------------------------------------------------------------
boot configuration has been
saved
Fourthly, assign an IP address to the back port (i.e., the management or debug port).
monitor> ip 5
192.168.1.254
Enter netmask [255.255.255.0]:
Enter default gateway [0.0.0.0]:
192.168.1.2
Enter Mgmt Network [0.0.0.0]:
ip configuration has been saved
Finally, type “quit” to quit from the monitor mode and reboot the Accelar. Then, the Accelar boots the JVM boot image from the TFTP server. Later, starting ORE is similar to Question 8.
When the ORE starts on the Accelar (see the output on the Accelar console, e.g, “oplet started: http://192.168.1.2/jars/start.jar”), you can access to manage the ORE using the telnet-based commands.
LINUX 1008> telnet
192.168.1.254 1999
Trying 192.168.1.254...
Connected to 192.168.1.254.
Escape character is '^]'.
Welcome to the ORE shell
OpletShell> ls bin
cd* Change directory. Usage: "cd path"
install* Install an oplet: usage "install LOCATION"
load* Load (install and start) an oplet: usage
"load LOCATION"
ls* List objects in directory. Usage: "ls [path]"
mem* Show memory informatino: usage "mem"
mkdir* Make directory. Usage: "mkdir path"
oplets* Show the installed oplets
pwd* Print working directory. Usage: "pwd"
services* Show the registered services
showlog* Show the log: usage "showlog"
start* Starts an oplet: usage "start LOCATION"
stop* Stops an oplet: usage "stop LOCATION"
uninstall* Uninstall an oplet: usage
"install LOCATION"
unload* Unload (stop and uninstall) an oplet:
usage "install LOCATION"
OpletShell> oplets
http://192.168.1.2/jars/start.jar
http://192.168.1.2/jars/logger.jar
http://192.168.1.2/jars/shell.jar
http://192.168.1.2/jars/startupShell.jar
http://192.168.1.2/jars/logwriter.jar
http://192.168.1.2/jars/ahttp.jar
http://192.168.1.2/jars/oreservlets.jar
OpletShell> quit
Comments? Send
to Webmaster. Thanks.
End of this FAQ.