1. I tried burning the PortServer II's firmware image into flash and it failed, now what do I do?


If the boot load= command failed, do NOT reboot the PSII. Try re-running boot load= a few times to see if it eventually succeeds. You should have first made sure you were able to remotely boot from the firmware image! If you cannot successfully burn it (success means you got the message "The image in flash now appears valid") into flash, when you reboot it will fail and show an "E9" in the display window. It will not boot until the corrupted flash image is fixed. To fix:

1. Hook a terminal up to port 1 set to 9600-8N1-vt100
2. Reboot the PSII
3. Immediately hit the "v" key on the terminal.
A lot of boot info will show on the screen, if it hangs during any of these tests hit "ctrl-c" you should then be prompted with:
1. Press ? for diagnostics menu -- hit "?"
2. The diagnostics menu should show -- hit "C"
Use the default for all questions asked except:
• Should a tftpboot be tried = smart
• IP Address for Server = "tftpboot_server_IP_Address"
This will equal the actual IP address of the tftpboot server.
• tftp filename:"401260F.bin"
• Reboot the PortServer II
You still have corrupted flash but it will boot up. If you have a different boot image burn it (boot load=) otherwise get "401260F.bin" (filename may change) from our server and burn this in.


2. I tried booting the PortServer II from a firmware image and it continually recycles, how do I correct this?


If the boot from a new firmware image failed, and the LED keeps recycling, this would be a good indication that there is not a sufficient amount of ROM in the PortServer II.

To restore to the original firmware image, simply hold down both arrows on the PortServer II for about 10-20 seconds.


3. When inserting the following comand "set ports range=1-7 uid=2 auto=on dport=1500 dest=205.215.203.174" I continually get the error: uid does not correspond to valid user name.
   
   Go to Set User and make sure you have an indx 2.
   If not, you will need to configure a user using the Set User Name=xxxx command.
   
   
   
4. I am having problems removing ALTIP Address.
   
   In firmware version 3.1.9 the command structure was slightly modified.  To remove an altip address use the following command:

   set altip ra=(index number/ip address) rm

   
   

5. How I add more RAM? This should be considered for sites with heavy traffic on serial ports or with full 64 port expansion.

How to install more RAM into your Portserver II:
- Turn off the Portserver II, and unplug it from the power supply.

- Flip the Portserver II over, and remove the 6 screws. You will need
   a Philips screwdriver to do this.

- Turn the box back over, and pop the cover off.

- You will find the one RAM slot towards the front of the Portserver II,
  you will need to remove the RAM that is currently there. To do this, find
  the 2 metal clasps on each side of the RAM slot and pull each to the side.
  This will cause the RAM chip to push backwards. At that point just remove
  the RAM chip from the slot.

- Now we will need to insert the new RAM. To do this, come in at an angle
  with the RAM, and ensure that it lines up with the slot. If it doesn't line
  up, try flipping the RAM around and try it again. Once its lined up
  correctly, pull the chip towards you until it *clicks* into place. Ensure that
  the metal brackets hold the chip on each side correctly.

- We now have to adjust 2 jumpers to let the Portserver II know exactly how
  much RAM we have installed.  Find J4 and J5, and adjust them according
  to the following grid.

 Amount of RAM:                   J4              J5

4 Meg or 8 Meg                    2 & 3           1 & 2
16 Meg                                 1 & 2           2 & 3

  NOTE: The number 3 pins is closest to the front panel.

- Put the cover back on, and put the 6 screws back in.
- Plug it back in, and turn the Portserver II back on. Ensure that it comes
   back to AC.

    10. When I attempt to telnet from a PortserverII to a Georgia Softworks Telnet
          Server for Windows NT, I can't log in.